This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NCS Zigbee examples reach assert on debug

Hi, 

We are currently testing the zigbee_light example for nrf52840dk. Once in the debug stage, if we pause program execution and then resume it we find out that codes gets stucked at:

- nrf_raal_timeslot_us_left_get() -> m_assert_handler()

The m_assert_handlers specifies a problem at rem.c, line 2778

Is it an issue? Where is rem.c located? How can this be fixed?

Thanks in advance,

Santiago

  • Hello,

    Are you using BLE with this example, or only zigbee? It looks like you have lost some timeslot where the CPU was supposed to move on. I know that at least if you are working with a BLE stack, you need to reset after a breakpoint, but I thought that if you were using Zigbee only, that you would be able to stop and resume (within reasonable time). However, I have not tested this in NCS (only nRF5 SDK). Perhaps the zigbee stack here is a bit more time sensitive. 

     

    We are currently testing the zigbee_light example for nrf52840dk

     Where exactly did you find this example? Did you mean the example: NCS\nrf\samples\zigbee\light_bulb? (at least that is the name in v1.5.0. What version are you using?).

    Best regards,

    Edvin

Related