This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unable to enter MCUboot mode: MCUboot DFU failed. Error: NMP timeout

Hello community... I was able to compile the GPS sample and flash an actinius icarus (nRF9160) using the Actinius Programmer once and it said successful. However, checking via terminal screen it appears it is stuck in a boot loop and I am no unable to enter MCUboot mode: MCUboot DFU failed. Error: NMP timeout

Is there a way I can reset all so I can write another hex to the device?

[terminal capture below -- it just keeps looping]

...

20 NRF_FPU Non-Secure OK
21 NRF_EGU1 Non-Secure OK
22 NRF_EGU2 Non-Secure OK
23 NRF_DPPIC Non-Secure OK
24 NRF_REGULATORS Non-Secure OK
25 NRF_PDM Non-Secure OK
26 NRF_I2S Non-Secure OK
27 NRF_GPIOTE1 Non-Secure OK

SPM: NS image at 0x18200
SPM: NS MSP at 0x2001c070
SPM: NS reset vector at 0x1c70d
SPM: prepare to jump to Non-Secure image.

E: Could not get GPIO Device Binding
*** Booting Zephyr OS build v2.6.99-ncs1 ***
Flash regions Domain Permissions
00 02 0x00000 0x18000 Secure rwxl
03 31 0x18000 0x100000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 2 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

Peripheral Domain Status
00 NRF_P0 Non-Secure OK
01 NRF_CLOCK Non-Secure OK
02 NRF_RTC0 Non-Secure OK
03 NRF_RTC1 Non-Secure OK
04 NRF_NVMC Non-Secure OK
05 NRF_UARTE1 Non-Secure OK
06 NRF_UARTE2 Secure SKIP
07 NRF_TWIM2 Non-Secure OK
08 NRF_SPIM3 Non-Secure OK
09 NRF_TIMER0 Non-Secure OK
10 NRF_TIMER1 Non-Secure OK
11 NRF_TIMER2 Non-Secure OK
12 NRF_SAADC Non-Secure OK
13 NRF_PWM0 Non-Secure OK
14 NRF_PWM1 Non-Secure OK
15 NRF_PWM2 Non-Secure OK
16 NRF_PWM3 Non-Secure OK
17 NRF_WDT Non-Secure OK
18 NRF_IPC Non-Secure OK
19 NRF_VMC Non-Secure OK
20 NRF_FPU Non-Secure OK
21 NRF_EGU1 Non-Secure OK
22 NRF_EGU2 Non-Secure OK
23 NRF_DPPIC Non-Secure OK
24 NRF_REGULATORS Non-Secure OK
25 NRF_PDM Non-Secure OK
26 NRF_I2S Non-Secure OK
27 NRF_GPIOTE1 Non-Secure OK

SPM: NS image at 0x18200
SPM: NS MSP at 0x2001c070
SPM: NS reset vector at 0x
...
..

Parents
  • Hi,

    - Keeping the button pushed and then resetting (while still keeping the button pressed on bootup) will get MCUboot activated _unless_ the nRF9160 has been flashed *using a JLink programmer* with a firmware image that doesn't include MCUboot. Did you upload the GPS sample using MCUboot or JLink? If you have only used MCUboot to upload firmware before, then the MCUboot itself is immutable and you should activate it with the buttons as mentioned above. Perhaps upload one of the pre-built samples that are included in the Actinius Programmer as a first step.

    - In the case of building your own firmware and if you are using the MCUboot that comes preinstalled with the board, please see https://docs.actinius.com/icarus/building/zephyr section "Different MCUboot versions / partitions" about how to have the firmware located to the right address. This is needed because the default partitioning changed at some point in nRF Connect. This is *not* needed if you have uploaded a new MCUboot or if you are not using MCUboot at all.

    Kind regards,

    Mike

Reply
  • Hi,

    - Keeping the button pushed and then resetting (while still keeping the button pressed on bootup) will get MCUboot activated _unless_ the nRF9160 has been flashed *using a JLink programmer* with a firmware image that doesn't include MCUboot. Did you upload the GPS sample using MCUboot or JLink? If you have only used MCUboot to upload firmware before, then the MCUboot itself is immutable and you should activate it with the buttons as mentioned above. Perhaps upload one of the pre-built samples that are included in the Actinius Programmer as a first step.

    - In the case of building your own firmware and if you are using the MCUboot that comes preinstalled with the board, please see https://docs.actinius.com/icarus/building/zephyr section "Different MCUboot versions / partitions" about how to have the firmware located to the right address. This is needed because the default partitioning changed at some point in nRF Connect. This is *not* needed if you have uploaded a new MCUboot or if you are not using MCUboot at all.

    Kind regards,

    Mike

Children
No Data
Related