NRF9160 SES 4.18 flash erase hanging

RE: NRF9160 SES 4.18 flash erase hanging

GJSea — Fri, 18 Oct 2019 15:52:34 GMT

I also get this everytime I do a Debug..Go in SES after rebuilding my firmware, 2nd time invariably succeeds. This is both on the 0.8.5 DK and our own custom board.

with this in the console:

Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: CPU may have not been reset (DHCSR.S_RESET_ST never gets set).
Reset: Using fallback: Reset pin.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via reset pin
Downloading ‘merged.hex’ to J-Link
Programming 33.1 KB of addresses 00000000 — 000084af
Programming 397.3 KB of addresses 0000c000 — 0006f537
Timeout while checking target RAM, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x61000007)!
Failed to prepare for programming.
Failed to execute RAMCode for RAM check!
CPU is not halted
Download failed

Then when it works I get the following:

Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘merged.hex’ to J-Link
Programming 33.1 KB of addresses 00000000 — 000084af
Programming 397.3 KB of addresses 0000c000 — 0006f537
J-Link: Flash download: Bank 2 @ 0x00000000: Skipped. Contents already match
Download successful

RE: NRF9160 SES 4.18 flash erase hanging

Jeff Seaman — Fri, 18 Oct 2019 15:44:54 GMT

Yes I still can not reprogram without a full erase.

I would like to save EE Data between debug sessions.

RE: NRF9160 SES 4.18 flash erase hanging

phipi — Thu, 17 Oct 2019 18:30:40 GMT

I'm still experiencing the same issue with SES V4.20 after installing the above nrfjprog

RE: NRF9160 SES 4.18 flash erase hanging

Bjørn Kvaale — Wed, 09 Oct 2019 10:17:19 GMT

The new release of nrfjprog v10.4.0 that came out today fixes this issue. You can download the new command line tools here.

Update: My bad, it seems this fix only fixed the command line flashing issue. If you are using Segger Embedded Studio, you'll have to wait for the new J-Link fix, which should be out soon. SES uses J-Link directly (not nrfjprog), so the fix needs to be implemented there by Segger first.

I will update this case once SES has been fixed.

RE: NRF9160 SES 4.18 flash erase hanging

Bjørn Kvaale — Tue, 10 Sep 2019 08:59:40 GMT

The issue has not been fixed yet (I will still update this thread once a fix is available), but what you can do instead is use the Segger IDE to write code & use the command line tools to build & flash. Or compile via SES & use west or nrfjprog to flash.

To build & flash using command line tools:

west build -b nrf9160_pca10090ns -d build1
west flash -d build1

where -b stands for board & -d stands for the build directory.

Otherwise, you can also use nrfjprog directly:

nrfjprog --program merged.hex --sectorerase -f nrf91 --verify

The merged hex file is located here e.g:

ncs\nrf\samples\nrf9160\http_application_update\build1\zephyr

You could also use Visual Studio Code or something similar if you prefer to do that.

RE: NRF9160 SES 4.18 flash erase hanging

Bjørn Kvaale — Wed, 17 Jul 2019 05:04:38 GMT

Another workaround is to just try flashing the merged hex multiple times. After one or two times, it should work. We should have a new version of SES out sometime soon, which will implement a fix for this.

RE: NRF9160 SES 4.18 flash erase hanging

rkguy — Fri, 12 Jul 2019 00:48:49 GMT

Yah. My workaround is to build in segger studio and sideload using the new nrfConnect app

RE: NRF9160 SES 4.18 flash erase hanging

Jeff Seaman — Thu, 11 Jul 2019 13:27:05 GMT

To reprogram the chip

1) in tools connect to target

2) erase all and wait for it to fail

3) program and debug as normal.

this does not seem to be needed if not running secure partition manager

RE: NRF9160 SES 4.18 flash erase hanging

GJSea — Tue, 09 Jul 2019 16:02:37 GMT

Thanks!

RE: NRF9160 SES 4.18 flash erase hanging

Bjørn Kvaale — Tue, 09 Jul 2019 12:42:43 GMT

It seems there is an issue with the J-Link driver. This has been reported internally. I will keep you updated as soon as we have a fix.