nrf52840 going into fault continously

[Haseeb Zaib]

Hi, I am trying to run DHCP Client example using ethernet w5500 and my nrf is continously going into fault. sometimes it gets the ip correctly and goes into fault and other times when it starts immediately goes into fault. 

I have ran same code on nrf52832 and it works fine, even tries it on nrf9160 and works fine, the issue occur on this one 

any insights on this ?

This pictures shows it got the IP from router and went into fault 

This picture shows it went into fault in the start

I tried running mqtt with ethernet and was going into fault as well and mqtt with ethernet works fine on nrf52832 

Also I tried increasing stack size and also given alot of heap but same issue, so it is definitly not related to that.

[nordicator_prim3]

This whole lesson from DevAcademy would be beneficial. In your particular case, focus on the bit about the addr2line utility.

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-2-debugging/topic/exercise-2-11/

You dont have to do anything in firmware to use it, you basically just plug in those instruction addresses and it will take you to the line of code that is causing the issues. Just eyeballing it, the error is originating from the same line of code regardless of if it's happening on boot or later on after the IP is printed. Also, based on some of those other addresses, it is likely a function using a null pointer to try and do something.

Good luck!

[Haseeb Zaib]

Thanks alot for this. So I ran the addr2line command like this 

backtrace comes to internal library. 

Ima investigate it further.

[Håkon Alseth]

Hi,

 

No worries, update the case when you have the time.

Hope you have a great weekend!

 

Kind regards,

Håkon

[Haseeb Zaib]

Hi, So I stopped the nrf restarting by the following flag and then checked the map file there is no 200003a0 thread in that file, looked manually and as well as searched the whole file but nothing came up. Here is the file

4035.zephyr.map

[Haseeb Zaib]

This is call stack when I received the exception, Cant debug much from it as it shows same position what addr2line showed

can you deduce anything from it ? This time it went as far as trying to connect to mqtt but mostly it gets the IP from dhcp server and goes into fault or even during start.

[Haseeb Zaib]

got any idea ?

[Håkon Alseth]

Hi,

 

Haseeb Zaib said:

Hi, So I stopped the nrf restarting by the following flag and then checked the map file there is no 200003a0 thread in that file, looked manually and as well as searched the whole file but nothing came up. Here is the file

The assert output will change when you recompile/reflash the firmware.

Do you have the latest uart assert output ? I suspect that this address has now changed.

 

Kind regards,

Håkon

[Haseeb Zaib]

I deleted build file recreated it recompiled the code and uploaded again, The address change.But after constantly restarting the mcu, the address remained the same 0x20001080, but even then in zephyr.map file the address does not exists.

[Haseeb Zaib]

was manually restarting the mcu as I was turned automatic restart off.

[Håkon Alseth]

Hi,

 

Could you do the following?

1. flash the device

2. Share the assert output

3. share the .map file

 

Kind regards,

Håkon

[Haseeb Zaib]

1) Uploaded fresh code 

2) Here is assert output

3) .map file of latest flash, Uploading all 3 map files just incase

6864.zephyr.mapzephyr_pre0.mapzephyr_final.map

[Håkon Alseth]

Hi,

 

Thanks for sharing.

According to the .map, that area is within a dedicated RAM area for the w5500:

 .data.w5500_0_runtime
                0x0000000020000000     0x1780 zephyr/drivers/ethernet/libdrivers__ethernet.a(eth_w5500.c.obj)

 And looking at that structure, it points to this:

https://github.com/nrfconnect/sdk-zephyr/blob/v3.6.99-ncs2/drivers/ethernet/eth_w5500_priv.h#L93

 

Could you try to increase "CONFIG_ETH_W5500_RX_THREAD_STACK_SIZE" and see if the issue disappears?

 

Kind regards,

Håkon