nRF52 shows "unknown function at 0x00000A60" after 58 minute fix time

[Nik.P]

Hello Nordic Community,

I am using nRF52840 SDK 17.0.2.

I took examples\ble_peripheral\ble_app_beacon as reference and created mBeacon profile.

Then I created three different handler using timer.

First is beacon timer handler which starts advertising at every 20 second.

Second is sampling timer handler which occurs at every 60 second period and measures sensor values also updates these values in advertising.

Third is logging timer handler which logs sensor data on UART at every 60 second time period.

everything is working continuously for 58 minutes after that it shows "unknown function at 0x00000A60".

I haven't used and debug point in code. Debug is used for RTT logs only.

Can you tell me what is wrong going here?

Thanks in advance

Nikunj P. 

[Einar Thorsrud]

Hi,

Where do you see "unknown function at 0x00000A60"? If suddenly execution moves to somewhere invalid (I am not sure yet if that is the case), then it would indicate a memory corruption caused by for instance overwriting a pointer, stack overflow, etc. If this consistently happens after 58 minutes you should look at the code you regularly call, and see if that can have such an effect. I can look at it if you upload it here.

[Nik.P]

Hey Einar T.

Thanks for your quick reply.

I sent you code on private message.

Thanks,

Nikunj P.

[Einar Thorsrud]

Hi Nikunj,

I did not get a chance to look at it today, but I will attempt to do it tomorrow.

[Einar Thorsrud]

Hi,

To be honest the code is so large that it is difficult to spot any issue by simply browsing it. As this happens consistently for 58 minutes, and then fails, there must be something related to a task that is done regularly. Perhaps an overflow or something else that suddenly cause problems after x iterations. Can you try to comment out as much as possible while still being able to trigger the issue, so that there is a smaller piece of code to inspect? What I would be looking for first would be something that could cause memory corruption like tack overflow, write to array out of bond, dangling pointer, etc., as indicated in my initial reply.

[Nik.P]

Hi,

Thanks for your kind support and investing time in my code.

I will defiantly try to comment down as much as possible while it will still trigger issue.

Also, I will try to find it by myself.

Thanks, 

Nikunj 

[Nik.P]

Hello Einar,

After debugging I found that after commenting some part code works for longer time. I sent you private message of code can you look at it and find any memory leak for me?

Thanks,

Nikunj