nRF9160 Hard fault on boot

RE: nRF9160 Hard fault on boot

Øyvind — Mon, 02 Dec 2019 08:26:21 GMT

Glad I could help to solve the issue! 🙂

RE: nRF9160 Hard fault on boot

Tron — Sun, 01 Dec 2019 20:46:11 GMT

I done what you asked, and enabled the watchdog the same way the wd was disabled, in the prj.conf file.

It runs now, thank you for all your effort, this is not too easy debug 🙂

RE: nRF9160 Hard fault on boot

Øyvind — Fri, 29 Nov 2019 14:41:07 GMT

I've spoken to my colleagues. We narrowed it down to the WDT configuration not executing. and the issue is most likely that the WDT is not enabled in SPM.

To solve this, you have to configure SPM.

Navigate to your CmakeLists.txt in your project, and the following line just below the “cmake_minimum_required(…)” and save the file:
```
set(spm_CONF_FILE
    prj.conf
    ${CMAKE_CURRENT_LIST_DIR}/spm.conf
    )
```
Next, you need to create the file spm.conf in your application folder
Add the following line to spm.conf:
CONFIG_SPM_NRF_WDT_NS=y

Let me know how that works for you.

Kind regards,
Øyvind

RE: nRF9160 Hard fault on boot

Tron — Fri, 29 Nov 2019 12:58:27 GMT

Yes, I need a watchdog timer; so it is enabled. Disabling it in the prj.conf file:

# Watchdog
CONFIG_WATCHDOG=n
#CONFIG_WDT_LOG_LEVEL_DBG=n

This makes the project to run. How to proceed on enabling the WDT?

RE: nRF9160 Hard fault on boot

Øyvind — Fri, 29 Nov 2019 12:37:37 GMT

Ok, this gives us something at least. Line 8 of your response, reent.c. What is this? It does not give any information about line number, so difficult to say what this is.

Line number 11 points to nrfx_wdt.c and line 90:

nrf_wdt_reload_value_set((p_config->reload_value * 32768) / 1000);

Is the WDT enabled in your system? If so, can you please try to disable this? To see if you are able to run.

RE: nRF9160 Hard fault on boot

Tron — Fri, 29 Nov 2019 12:12:46 GMT

I have the following addresses available:

[11.29 11.51.56.915][00:00:00.487,854] <err> os:   Precise data bus error
[11.29 11.51.56.915][00:00:00.487,854] <err> os:   BFAR Address: 0x4001850c
[11.29 11.51.56.915][00:00:00.487,884] <err> os: r0/a1:  0x00000009  r1/a2:  0x000208d5  r2/a3:  0x40018000
[11.29 11.51.56.948][00:00:00.487,884] <err> os: r3/a4:  0x00000009 r12/ip:  0x000217fc r14/lr:  0x0003cbf5
[11.29 11.51.56.948][00:00:00.487,915] <err> os:  xpsr:  0x40015000

I have the following responses:

C:\Users\tron>c:\gnuarmemb\bin\arm-none-eabi-addr2line.exe -e c:\nrfTest-1.1\ncs\nrf\samples\tron\udp_gps\build_01\zephyr\zephyr.elf 0x4001850c
??:0

C:\Users\tron>c:\gnuarmemb\bin\arm-none-eabi-addr2line.exe -e c:\nrfTest-1.1\ncs\nrf\samples\tron\udp_gps\build_01\zephyr\zephyr.elf 0x40018000
??:0

C:\Users\tron>c:\gnuarmemb\bin\arm-none-eabi-addr2line.exe -e c:\nrfTest-1.1\ncs\nrf\samples\tron\udp_gps\build_01\zephyr\zephyr.elf 0x00038f59
reent.c:?

C:\Users\tron>c:\gnuarmemb\bin\arm-none-eabi-addr2line.exe -e c:\nrfTest-1.1\ncs\nrf\samples\tron\udp_gps\build_01\zephyr\zephyr.elf 0x0003cbf5
C:/nrfTest-1.1/ncs/modules/hal/nordic/nrfx/drivers/src/nrfx_wdt.c:90

C:\Users\tron>c:\gnuarmemb\bin\arm-none-eabi-addr2line.exe -e c:\nrfTest-1.1\ncs\nrf\samples\tron\udp_gps\build_01\zephyr\zephyr.elf 0x40015000
??:0

I really hope this helps 🙂

RE: nRF9160 Hard fault on boot

Øyvind — Fri, 29 Nov 2019 11:21:16 GMT

Ok, then we need to move to the other addresses right after BUS FAULT:

[11.27 08.48.39.876][00:00:00.487,579] <err> os: BFAR Address: 0x4001850c
[11.27 08.48.39.876][00:00:00.487,609] <err> os: r0/a1: 0x00000009 r1/a2: 0x000202e5 r2/a3: 0x40018000
[11.27 08.48.39.876][00:00:00.487,609] <err> os: r3/a4: 0x00000009 r12/ip: 0x0002120c r14/lr: 0x00038f59

Let me know if you get anything from those.

RE: nRF9160 Hard fault on boot

Tron — Fri, 29 Nov 2019 10:56:18 GMT

I did recompile when issue #239969 was solved, and got a new failing address:

Now, the faulting instruction is 2002b280, and issuing your command I get the response

C:\Users\tron>c:\gnuarmemb\bin\arm-none-eabi-addr2line.exe -e c:\nrfTest-1.1\ncs\nrf\samples\tron\udp_gps\build_01\zephyr\zephyr.elf 0x2002b280
??:0

C:\Users\tron>

Not very informative, I'm afraid.

RE: nRF9160 Hard fault on boot

Øyvind — Fri, 29 Nov 2019 10:04:36 GMT

Can you please issue the following command in your command line:

<gnuarmemb root>/bin/arm-none-eabi-addr2line.exe -e <project build folder/zephyr/zephyr.elf> 0xADDRESSE

Where 0xADDRESSE is the Faulting instruction addres (r15/pc) 0x20029760

Please note that if you have recompiled your code lately, the address may have changed. Make sure to use the latest address from the output. The output should give an indication on the failing line and file.

RE: nRF9160 Hard fault on boot

Tron — Fri, 29 Nov 2019 09:37:03 GMT

Good, thanks for keeping me informed 👏

RE: nRF9160 Hard fault on boot

Øyvind — Fri, 29 Nov 2019 09:35:58 GMT

Thanks for the update on the other case, and on the "Heap & stack size".

I'm currently working to find a solution. Will get back to you asap.

RE: nRF9160 Hard fault on boot

Tron — Thu, 28 Nov 2019 10:57:29 GMT

Update: Case #239969 is now resolved, I'm able to compile and link, but the hard fault persists.

RE: nRF9160 Hard fault on boot

Tron — Thu, 28 Nov 2019 10:00:46 GMT

From my prj.conf:

# Heap and stacks
CONFIG_HEAP_MEM_POOL_SIZE=16384
CONFIG_MAIN_STACK_SIZE=8192
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

RE: nRF9160 Hard fault on boot

Øyvind — Thu, 28 Nov 2019 09:22:53 GMT

[quote user="tronwa"]Not sure what you're asking for on th device version, but looking at the device, I see BAA-E2.1.8 and 11STO (or maybe 11STQ, I'm getting old). [/quote]

Ok, thanks for the information!

In prj.conf of your project, can you confirm that the following are set to:

CONFIG_HEAP_MEM_POOL_SIZE=16384

CONFIG_MAIN_STACK_SIZE=8192

Kind regards,

Øyvind

RE: nRF9160 Hard fault on boot

Tron — Thu, 28 Nov 2019 08:30:31 GMT

Not sure what you're asking for on th device version, but looking at the device, I see BAA-E2.1.8 and 11STO (or maybe 11STQ, I'm getting old).

I've updated the nrfjprog to version to 10.5.0, but still iin the same quigmire.

It might be connected to #239969, this is something I don't know about. On the program I'm running on the device, I have the link problems commented out. If this might cause a problem, I'm not sure of. Initially it seemed like 2 independent issues to me.

RE: nRF9160 Hard fault on boot

Øyvind — Wed, 27 Nov 2019 14:41:02 GMT

Hi, I see you have an ongoing case #239969. Can this issue be related to that case? If so, I suggest continuing your support there.

Make sure to update your nrfjprog to the latest version 10.5.0, and retry last step. I know it's timeconsuming, but we are aware of some issues related to nrfjprog.

Can you also provide more information about your setup? What the device version are you working on (found physically on your device)?

Kind regards,
Øyvind

RE: nRF9160 Hard fault on boot

Tron — Wed, 27 Nov 2019 10:52:48 GMT

nrfjprog version:

nrfjprog version: 10.3.0
JLinkARM.dll version: 6.54c

nrfjprog -e and reprogramming the device didn't make any changes in the output.

RE: nRF9160 Hard fault on boot

Øyvind — Wed, 27 Nov 2019 08:54:38 GMT

Hello @tronwa,

can you please provide the version of nrfjprog? This can be found issuing nrfjprog --version

Before programming your device, can you please issue nrfjprog -e to erase your board. Then try to program your device again.

Kind regards,
Øyvind