cpu info:nrf5340
software:nrf connect sdk 1.6.1
hi professor,
In the uart interrupt I call k_fifo_put to trigger rx process thread but it is not take effect.What person cause this question?


cpu info:nrf5340
software:nrf connect sdk 1.6.1
hi professor,
In the uart interrupt I call k_fifo_put to trigger rx process thread but it is not take effect.What person cause this question?


Hello,
Have you verified through debugging that k_fifo_put() actually gets called?
Thanks,
Vidar
I'm sure k_fifo_put was called.
typedef struct
{
void *fifo_reserved;
uint32_t uiSensorState;
}sensor_operate_t;
I'm unable to extract your *.rar file for some reason. Could you please try to upload it again and maybe as a .zip instead?
hi Vidar Berg,
Did you find any problems in my code?
Hi,
I have not found anything that could explain the error, but I notice you have changed the ID numbers you stored to the ucProcessChar[] array, which makes it more challenging to figure out what the original execution sequence was. I also noticed you have reverted back to using zero latency interrupts again. This is not recommended.
Could you try to use SEGGER SystemView as described in the link below to see whether the alg_thread is running after the UART event or not?
https://docs.zephyrproject.org/latest/guides/debug_tools/tracing/index.html
Thanks,
Vidar
Hi,
I have not found anything that could explain the error, but I notice you have changed the ID numbers you stored to the ucProcessChar[] array, which makes it more challenging to figure out what the original execution sequence was. I also noticed you have reverted back to using zero latency interrupts again. This is not recommended.
Could you try to use SEGGER SystemView as described in the link below to see whether the alg_thread is running after the UART event or not?
https://docs.zephyrproject.org/latest/guides/debug_tools/tracing/index.html
Thanks,
Vidar