nRF9160dk onboard controller crash

RE: nRF9160dk onboard controller crash

Georgi Valkov — Wed, 04 Jan 2023 08:49:39 GMT

Now I'm getting a lot of errors trying to program nRF52840DK under macOS.
I also find it very inconvenient, that each time I need to program or debug the board, I need to disconnect the RTT terminal, and for some reason I can't have RTT and debugging at the same time in VS Code.

SEGGER J-Link Configuration V7.84

Product = J-Link OB-SAM3U128-V2-NordicSem V1.00
Nickname =
SN = 683315365
USB = SN 683315365
HostFW = 2022 Nov 7 16:21
EmuFW = 2022 Nov 7 16:21

VS Code 1.74.2

* Executing task: nRF Connect: Flash: connectivity_bridge_52840/build (active)

Flashing build to 683315365
west flash -d /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build --skip-rebuild -r nrfjprog --dev-id 683315365

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build/zephyr/zephyr.hex
[ #################### ] 7.417s | Erase file - Done erasing
[ #################### ] 3.460s | Program file - Done programming
[ #################### ] 3.400s | Verify file - Done verifying
[error] [ Client] - Worker process is dead, cannot execute command.
ERROR: An internal error has occurred, please try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 63: nrfjprog --pinresetenable -f NRF52 --snr 683315365

logs from yesterday

* Executing task: nRF Connect: Build: connectivity_bridge_52840/build (active)

Building connectivity_bridge_52840

west build --build-dir /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840

ninja: no work to do.

* Terminal will be reused by tasks, press any key to close it.

* Executing task: nRF Connect: Flash: connectivity_bridge_52840/build (active)

Flashing build to 683315365

west flash -d /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build --skip-rebuild -r nrfjprog --dev-id 683315365

-- west flash: using runner nrfjprog

-- runners.nrfjprog: Flashing file: /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build/zephyr/zephyr.hex

ERROR: Unable to connect to a debugger.

[error] [SeggerBackend] - JLinkARM.dll Open returned error 'Cannot connect to J-Link.'

ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.

ERROR: If the error condition persists, run the same command again with

ERROR: argument -- log, contact Nordic Semiconductor and provide the generated

ERROR: log.log file to them.

NOTE: For additional output, try running again with logging enabled (--log).

NOTE: Any generated log error messages will be displayed.

FATAL ERROR: command exited with status 35: nrfjprog --program /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build/zephyr/zephyr.hex --sectoranduicrerase --verify -f NRF52 --snr 683315365

* The terminal process terminated with exit code: 35.

* Terminal will be reused by tasks, press any key to close it.

* Executing task: nRF Connect: Build: connectivity_bridge_52840/build (active)

Building connectivity_bridge_52840

west build --build-dir /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840

ninja: no work to do.

* Terminal will be reused by tasks, press any key to close it.

* Executing task: nRF Connect: Flash: connectivity_bridge_52840/build (active)

Flashing build to 683315365

west flash -d /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build --skip-rebuild -r nrfjprog --dev-id 683315365

-- west flash: using runner nrfjprog

-- runners.nrfjprog: Flashing file: /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build/zephyr/zephyr.hex

[error] [ Client] - Worker process is dead, cannot execute command.

ERROR: An internal error has occurred, please try again.

NOTE: For additional output, try running again with logging enabled (--log).

NOTE: Any generated log error messages will be displayed.

FATAL ERROR: command exited with status 63: nrfjprog --program /opt/nordic/ncs/v2.2.0/nrf/applications/connectivity_bridge_52840/build/zephyr/zephyr.hex --sectoranduicrerase --verify -f NRF52 --snr 683315365

* The terminal process terminated with exit code: 63.

* Terminal will be reused by tasks, press any key to close it.

RE: nRF9160dk onboard controller crash

Georgi Valkov — Thu, 15 Dec 2022 23:59:04 GMT

I just updated J-Link-OB-K22-NordicSemi to 2022 Nov 7 16:21, and then reprogrammed the nRF52840 CPU on two nRF9160dk boards, while the USB UARTs were in use. So far no crashes were observed. Segger probably fixed the issue in Version V7.82b (2022-11-09). Thank you for your help, Sigurd!

https://www.segger.com/downloads/jlink/ReleaseNotes_JLink.html

J-Link-OB-K22-NordicSemi

Drag & Drop programming failed under macOS Ventura with error code 100093 (Operation can't be completed because an unexpected error occurred). Fixed.

RE: nRF9160dk onboard controller crash

Sigurd — Wed, 07 Dec 2022 12:10:10 GMT

Segger is working on it. A suggested temporarily workaround is to downgrade to J-Link 7.58b (and update J-Link OB)

RE: nRF9160dk onboard controller crash

Georgi Valkov — Tue, 06 Dec 2022 20:11:09 GMT

This is taking too long. Two months already! When is this issue going to be fixed?

RE: nRF9160dk onboard controller crash

Sigurd — Fri, 25 Nov 2022 14:46:40 GMT

I have pinged for an update. I will let you know when I know more.

RE: nRF9160dk onboard controller crash

Georgi Valkov — Fri, 25 Nov 2022 12:31:56 GMT

When is this issue going to be fixed?

RE: nRF9160dk onboard controller crash

Sigurd — Tue, 08 Nov 2022 11:30:59 GMT

It's still under investigation. I will let you know when there is an update.

RE: nRF9160dk onboard controller crash

Georgi Valkov — Mon, 07 Nov 2022 11:26:25 GMT

Any update from Segger?

RE: nRF9160dk onboard controller crash

Sigurd — Fri, 21 Oct 2022 14:49:05 GMT

Hi,

This issue is likely caused by overloading the J-Link OB, causing it to miss USB timings and crashing. We will report it to Segger.

RE: nRF9160dk onboard controller crash

Georgi Valkov — Fri, 21 Oct 2022 11:19:10 GMT

Hi Sigurd! Any updates from Nordic?

RE: nRF9160dk onboard controller crash

Sigurd — Fri, 14 Oct 2022 11:47:01 GMT

Hi,

I see it's crashing here as well. Simply opening 2 COM-ports, and doing 'nrfjprog --memrd 0 --n 8192' makes it crash. I have reported it internally. I will update the case here when I have more info to share.

BR,

Sigurd

RE: nRF9160dk onboard controller crash

Georgi Valkov — Thu, 13 Oct 2022 12:09:18 GMT

Hi Sigurd!

[quote userid="15146" url="~/f/nordic-q-a/92755/nrf9160dk-onboard-controller-crash/390527"]I will try to reproduce this.[/quote]

Also try this:

1. Connect the board
2. Open the UARTs which connect to nRF9160 and nRF52840 in KiTTY
3. Run J-Flash (I use V7.80d, though the version should not matter)
4. Create new project, Start J-Flash
5. Target device, ..., Device: nRF52840_xxAA, OK, OK
6. Target, Connect
7. Target, Manual Programming, Read Back, Entire chip (F10)
8. KiTTY shows the two UARTs as disconnected, and I get the following error in j-Flash

Or using J-Link

jlink
SEGGER J-Link Commander V7.80d (Compiled Oct 4 2022 16:42:18)
DLL version V7.80d, compiled Oct 4 2022 16:40:52

Connecting to J-Link via USB...O.K.
Firmware: J-Link OB-K22-NordicSemi compiled Dec 3 2021 15:46:55
Hardware version: V1.00
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 960061371
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.300V

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: NRF52840_XXAA
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF52840_XXAA" selected.

Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
DPIDR: 0x2BA01477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Cortex-M4 identified.
J-Link>mem
Syntax: mem <Addr>, <NumBytes>
J-Link>mem 0, 8192

****** Error: Communication timed out: Requested 8196 bytes, received 0 bytes !
Could not read memory.

I wonder if the MCU is running out of memory?

J-Link>mem 0, 2048

****** Error: Communication timed out: Requested 8196 bytes, received 0 bytes !
Could not read memory.

J-Link>mem 0, 1024
00000000 = 20 38 00 20 B5 20 00 00 05 67 00 00 89 20 00 00 8. . ...g... ..

If I close KiTTY to release the USB UARTs, I can ready 0x100000 bytes without any issues.

[quote userid="15146" url="~/f/nordic-q-a/92755/nrf9160dk-onboard-controller-crash/390527"]What DK version are you using?[/quote]

I have two boards, both of which experience the issue, and both had their firmware upgraded to 2021 Dec 3 15:46 using J-Link Configurator from Segger.

nRF9160dk, PCA10090, 1.0.0, 2021.6, 960061371
nRF9160dk, PCA10090, 0.9.0, 2019.21, 960094834

[quote userid="15146" url="~/f/nordic-q-a/92755/nrf9160dk-onboard-controller-crash/390527"]Are you referring to the on-board interface MCU, that provides the three virtual COM ports?[/quote]

Yes, the big chip which provides jTAG and three UARTs over USB. MK22FN128VLL10

[quote userid="15146" url="~/f/nordic-q-a/92755/nrf9160dk-onboard-controller-crash/390527"]1) Is it only this application you are having issues with? or could I try to flash any application?[/quote]

Any application. Attempting to read 8KB at address 0 also triggers a crash.

[quote userid="15146" url="~/f/nordic-q-a/92755/nrf9160dk-onboard-controller-crash/390527"]2) This is the connectivity_bridge application that you have modified so that it can run on the DK, instead of the Thingy:91 ?[/quote]

Correct. Suggestion: It would be nice if Nordic integrates my changes in the original connectivity_bridge. This would allow access to data from the nRF9160 chip over BLE. Having the nRF52840 on board without using BLE makes no sense. Nordic has my permission to use the code ttached here and integrate it in nRF Connect SDK.

RE: nRF9160dk onboard controller crash

Sigurd — Wed, 12 Oct 2022 22:24:22 GMT

Hi,

I will try to reproduce this. What DK version are you using?

[quote user=""]I've been experiencing a crash whenever I try to erase or program the nRF52840 chip, while the USB UART interfaces are in use[/quote]

Are you referring to the on-board interface MCU, that provides the three virtual COM ports?

[quote user=""]4b. Add Application:
nrf/Applications/connectivity_bridge_dk (see jlink-crash.7z)[/quote]

1) Is it only this application you are having issues with? or could I try to flash any application?

2) This is the connectivity_bridge application that you have modified so that it can run on the DK, instead of the Thingy:91 ?