board nrf52832 does not connect anymore

RE: board nrf52832 does not connect anymore

Håkon Alseth — Tue, 19 Sep 2023 14:19:28 GMT

Glad to hear that it worked out! :)

If the firmware asserts early in the process, and the default behavior is to reset, it can be problematic to recover the board, as the firmware will effectively be in a reset-loop. This could have happened in your firmware.

PS: I would still recommend that you get a newer DK version. It is OK to use for evaluation, but you want to use a production grade silicon for development.

Kind regards,

Håkon

RE: board nrf52832 does not connect anymore

jean-marc — Tue, 19 Sep 2023 12:32:22 GMT

Håkon Alseth you are the Boss :-D

I had to do both.

J-Link commander at connect was going thru well as listed in the example above up to the last line. But the last line rather to say "Cortex-M4 identifies it says "Could not connect".

Then I ran "nrfjprog --recover -f nrf52" and it did connect. (last time it did not work).

Now I am OK and VScode can see my board and flash.

Now i have to find out why my code or the code suggested by the course does not work.

When I flash it it goes again disconnect and then when I run connect with the J-Link commander it works, and all is fine.

In any cases I know how to recover and I appreciate your excellent help.

RE: board nrf52832 does not connect anymore

Håkon Alseth — Mon, 18 Sep 2023 14:00:49 GMT

Hi,

Given that one of the LEDs are turned on, it might indicate that there's firmware running on your device.

You can try two other options:

* Use J-Link Commander to recover the device

* Use a batch script that runs "nrfjprog --recover -f nrf52" in a loop

Here's a way to use J-Link Commander (search in the start meny for it):

device NRF52
si 1
speed 1000
connect

Here's an example of how it should look when it has been successfully found

Type "connect" to establish a target connection, '?' for help
J-Link>device nrf52
J-Link>si 1
Selecting SWD as current target interface.
J-Link>speed 1000
Selecting 1000 kHz as target interface speed
J-Link>connect
Device "NRF52" 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.

And here is a batch-script which will run recover continuously:

RE: nRF52832 not connected anymore after first trying to debug (Keil)

Kind regards,

Håkon

RE: board nrf52832 does not connect anymore

jean-marc — Mon, 18 Sep 2023 13:52:46 GMT

OK thank you. I am wonder why it worked up thru the course "nRfconnect sdk Fundamental" and now it does not work for the "BLE fundamental" course. Too bad I was using it to train me using Nordic products.

Is it possible to upgrade the board by the firmware? Or the softDevice?

RE: board nrf52832 does not connect anymore

Håkon Alseth — Mon, 18 Sep 2023 11:49:12 GMT

Hi,

You have an older engineering device, which is reflected by the <v1.0 version of the nRF52-DK. You should use a newer DK, ideally equal to the IC revision that you will go into production with, which is highly likely nRF52832 revision 3.

Kind regards,

Håkon

RE: board nrf52832 does not connect anymore

jean-marc — Fri, 15 Sep 2023 14:46:44 GMT

Thank you.

RE: board nrf52832 does not connect anymore

Håkon Alseth — Fri, 15 Sep 2023 12:32:23 GMT

Thanks for the log.

Unfortunately, it shows that there's no successful contact with the nRF-chip at all.

Could you share a picture of the nRF52-DK board? I just want to check all the switch positions and so forth, in case there's anything there.

Kind regards,

Håkon

RE: board nrf52832 does not connect anymore

jean-marc — Thu, 14 Sep 2023 16:47:29 GMT

Oh! I though it was only for URL upload, sorrydevzone.nordicsemi.com/.../5164.log.log

And yes I call "nrfjprog --recover -f nrf52"

Thanks again

RE: board nrf52832 does not connect anymore

Håkon Alseth — Thu, 14 Sep 2023 11:49:07 GMT

Hi,

The log file should be created in the folder where you ran the command from.

To insert the file here, you can drag-and-drop it into the reply box.

Or you can go to:

Insert -> Image/Video/file

Then press the "upload" button - which will effectively work as "browse" button, and you can navigate to the file you want to upload.

[quote user="jean-marc"]ERROR: Recover failed. Please make sure that the correct device family is given[/quote]

Did you call it with the "nrfjprog --recover -f nrf52" option?

Kind regards,

Håkon

RE: board nrf52832 does not connect anymore

jean-marc — Wed, 13 Sep 2023 14:58:55 GMT

Håkon Alseth thank you for your precious help.

--recover failed, here are the error on the vscode terminal:

[error] [ Worker] - An unknown error.
[error] [ Client] - Encountered error -21: Command recover executed for 152 milliseconds with result -21
ERROR: Recover failed. Please make sure that the correct device family is given
ERROR: and try again.

Sorry, no idea on how to attach a file :-(

RE: board nrf52832 does not connect anymore

Håkon Alseth — Wed, 13 Sep 2023 10:21:17 GMT

Hi,

[quote user="jean-marc"]Great you fixed my bootloader problem. [/quote]

Great to hear that the board is one step closer to working!

[quote user="jean-marc"]

I can connect thru TeraTerm.

I can see my board with nRFConnect, but cannot select it.

[/quote]

It is good that you can connect to the COM port, that means that the board itself works as intended.

[quote user="jean-marc"]With nRFConnect I get such messages: "Note: no pre-compiled firmware is available for the selected device."[/quote]

Which application within nrf connect for desktop is reporting this?

What we can try is to use nrfjprog, the command line tool, directly.

* Open up a cmd prompt

* write "nrfjprog --recover -f nrf52 --log"

If it fails, please attach the "log.log" file generated.

Kind regards,

Håkon

RE: board nrf52832 does not connect anymore

jean-marc — Tue, 12 Sep 2023 13:43:01 GMT

Great you fixed my bootloader problem. Thanks a lot Håkon Alseth

Now I am back to the original problem :-(

With nRFConnect I get such messages: "Note: no pre-compiled firmware is available for the selected device."

or also this message "Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device."

I can connect thru TeraTerm.

I can see my board with nRFConnect, but cannot select it.

With VSCode I cannot see anymore my board connected, which was working before with VSCode

RE: board nrf52832 does not connect anymore

Håkon Alseth — Tue, 12 Sep 2023 11:21:41 GMT

Hi,

[quote user=""]The board led flash every second for a while and is visible on the USB but then flash rapidly and disapear from the USB.[/quote]

Holding down this button and powering up will place the nRF52-DK in bootloader mode.

In this mode, where the X:\BOOTLOADER drive is enumerated, you shall not flash anything other than the jlink binary file, or the cmsis daplink binary.

Here's a direct link to the jlink recovery binary: https://nsscprodmedia.blob.core.windows.net/prod/software-and-other-downloads/dev-kits/nrf5x-dk-files/j-link-ob-sam3u128-v2-nordicsemi-170724.bin

Found on this site: https://www.nordicsemi.com/Products/Development-hardware/nRF52-DK/Download?lang=en#infotabs

If you flashed another file than the jlink/cmsis dap fw while the device is in bootloader state, you can brick the board.

Does your board enumerate as a usb device at all now?

Kind regards,

Håkon