Proper task state for UART reading

[akorud]

Hi, maybe this is really simple question, but:
what is the proper state for task that only read data from UART? UTASKER_GO or UTASKER_STOP?
The task function looks like

Code: [Select]

if (debug_task_state == STATE_INIT) {
debug_uart_init();
debug_task_state = STATE_RUN;
}
while (fnRead(PortIDInternal, ucInputMessage, HEADER_LENGTH)) {
fnRead(PortIDInternal, ucInputMessage, ucInputMessage[MSG_CONTENT_LENGTH]); // flush any unexpected messages (assuming they arrived from another task)
}

if (SerialPortID != 0 && (uart_rx_len = fnMsgs(SerialPortID))) {
while ((uart_rx_len = fnRead(SerialPortID, ucInputMessage, MEDIUM_MESSAGE)) != 0) {
console_cmd_receive((char*)ucInputMessage, uart_rx_len);
}
}
I'm not sure if data on UART will activate and schedule the task.

[mark]

Hi

UTASKER_GO is only used when a task should act as a polling task. It would however also receive UART messages since it would always check the UART input each time it runs.

Most task are mostly in the UTASKER_STOP state.
When UART data is received it will automatically be set to the UTASKER_ACTIVATE state so that it reads the data. The task will always return back to the UTASKER_STOP state after it has been run once.

Therefore the normal (and most logical) state for a task which only reacts to UART input is UTASKER_STOP.

Regards

Mark

[akorud]

Thanks, and can you please confirm that:

Code: [Select]

{ "app",       fnApplication,  SMALL_QUEUE, (DELAY_LIMIT)(0.1 * SEC), 0, UTASKER_STOP},task will be invoked in 0.1s by uTasker (single shot)

Code: [Select]

{ "maintenace",fnTaskDebug,    SMALL_QUEUE, (DELAY_LIMIT)(NO_DELAY_RESERVE_MONO), 0, UTASKER_ACTIVATE},task will be invoked immediately by uTasker (single shot)

Code: [Select]

{ "period",    fnTimer,        SMALL_QUEUE, (DELAY_LIMIT)(NO_DELAY_RESERVE_MONO), 0, UTASKER_STOP},task will not be invoked by uTasker at all util another task send event to it or change state with uTaskerStateChange() call

regards,
Andriy

[mark]

Hi Andriy

Yes, these tasks have the characteristics as you state.

Regards

Mark