It is risky to have the ColdFire entering in low power mode while MQX is running. The worst of the scenarios is that the Kernel could be getting lost in the stack when it comes back from the low power mode. Since you are considering to perform a reset to wake up then I suggest to exit MQX with _mqx_exit ().This function returns back to the environment that called _mqx(). If your application has installed the MQX exit handler (_mqx_set_exit_handler), _mqx_exit() calls the MQX exit handler before it exits. By default, _bsp_exit_handler is installed as the MQX exit handler in each BSP.
Please have in mind that it is important to ensure that the environment (boot call stack) the MQX is returning to is in the consistent state. This is not provided by distributed MQX BSPs, because the boot stack is reused (rewritten) by MQX Kernel data. Set the boot stack outside of Kernel data section to support correct _mqx_exit functionality. So, if you are returning after calling _mqx() then you could perform a similar code as a stationary project where this is done.
Then you can configure and enter into low power mode and when you return you can perform a software reset which will cause to restart MQX.
I haven’t tested but in theory it is feasible.
Regards,
Garabo