Unknown error code (0xdeadbeef) - Thread CoAP application

[marmio]

Hi,

I' writing an app based on ble_thread_dynamic_template with added CoAP utils, but with a few changes. Program works fine, I am able to communicate over CoAP,  but after some time I get the deadbeef error. I tried to debug and it seems to come from thread timer (?), but I'm not sure, I will appreciate any bit of advice. I attach screen from debug session.

[Susheel Nuguru]

can you help me reproduce this error by giving details of your setup and zipped project for me to reproduce this.

[marmio]

Ok, I attached my project below. I use SES v.3.34 and Thread SDK 0.11. It may be hard to reproduce but I'll try to explain. This is one application for two boards: on top of main.c there's a macro defining which board it is: border_router or measuring_node (I switch between them by commenting macro BORDER_ROUTER). I added UARTE1 on pins 41(RX) and 32(TX) on border router. By sending 41\r\n to UARTE1 border router sends message to measuring node to start scanning. Then after sending 42\r\n to UARTE1 message is sent to measuring node to stop scanning. And then after few minutes I'm getting an error as you can see above.

zipped projectt

[Susheel Nuguru]

it is hard for me to be able to reproduce this error as I am getting multiple compilation errors. There must be something wrong with my setup and environment. 

I missed to see that you had a call stack visible here, timer_jitter_adjust is causing the assert. Can't you see exactly which line caused the assert?

[marmio]

Yes, it seems like it's line 259 in nrf_raal_softdevice.c:

rtc_ticks -= m_start_rtc_ticks;

And screen from debugging session showing this:

[Susheel Nuguru]

That should not have happened. raal module is relatively new for me. So I will contact the developer for it. Will update you soon when i get a response.

[marmio]

Hey Susheel Nuguru, do you have any update on this?

[marmio]

I investigated it once again and found out that previously I checked current openthread version, not the one used in SDK for Thread 0.11 (commit a89eb887). In this commit line 259 in nrf_raal_softdevice.c looks like that:

    // Adjust RTC0 ticks to TIMER0 resolution. RTC0 works with 32768kHz so first
    // multiply with 10^6 (microseconds) and divide by 32768Hz (2^15) to get microseconds.
    rtc_ticks = DIVIDE_AND_CEIL((rtc_ticks * US_PER_S), 32768);

 

[Susheel Nuguru]

Hi, Sorry for the late response. We had long easter holidays in Norway. The Thread team did not get time to look into this case, but they said they are about to release a new SDK where they refactored raal. So this problem could be fixed in the next release. Most likely the engineer will come back to this thread once he manages to find some time to analyse this.