Luos need to works with product that not always run the execution loop of a firmware.
In low consumption product at the end of a loop a "sleep function" can be call to stop the processor and enter in low consumption mode. Often the MCU is wake by a interruption provide from a peripheral like a timer, an IO, or a reception of a byte on usart.
Luos should have in the HAL, a function to start the sleep routine to put the MCU in sleep mode and the possibility to trigger an event to wake the MCU and start the routine of going out of the sleep mode.
At the end the loop, a luos API should be call by user. this function will block the loop process, finish to treat msg and message handling calling, send a message to all service to but them in sleep mode and enter in sleep mode.
The loop process can retrieve in by a timer to wake up periodically the MCU , with the PTP by poking nodes or directly with the reception of a byte on robus
Luos need to works with product that not always run the execution loop of a firmware.
In low consumption product at the end of a loop a "sleep function" can be call to stop the processor and enter in low consumption mode. Often the MCU is wake by a interruption provide from a peripheral like a timer, an IO, or a reception of a byte on usart.
Luos should have in the HAL, a function to start the sleep routine to put the MCU in sleep mode and the possibility to trigger an event to wake the MCU and start the routine of going out of the sleep mode.
At the end the loop, a luos API should be call by user. this function will block the loop process, finish to treat msg and message handling calling, send a message to all service to but them in sleep mode and enter in sleep mode.
The loop process can retrieve in by a timer to wake up periodically the MCU , with the PTP by poking nodes or directly with the reception of a byte on robus