Boards getting bricked

RE: Boards getting bricked

mathiaso — Wed, 03 Apr 2024 09:43:32 GMT

Hi, Niels.

Thank you for the log files.

It appears like you are using a DK as a debugger now. Do you power your custom board from the DK or externally? Could you try to power your custom board from the DK, as described here, if you haven't yet?

You can also try to run "nrfjprog --recover --clockspeed 10" to lower the frequency of SWDCLK in case there is an issue with long cables, etc.

Lastly, could you please upload the build/zephyr/.config folder? Then I'll be able to confirm if the DC/DC is enabled or not.

RE: Boards getting bricked

Niels Redegeld — Wed, 27 Mar 2024 15:31:27 GMT

I ended up getting a log file after a while, Ill add it below.devzone.nordicsemi.com/.../8267.log.log

RE: Boards getting bricked

Niels Redegeld — Wed, 27 Mar 2024 15:12:54 GMT

No it didn´t make any difference,

I don't think it was, cause for the custom board file it gave an error when i setted dc/dc to n in the config file.

RE: Boards getting bricked

mathiaso — Wed, 27 Mar 2024 13:36:54 GMT

[quote user="Niels Redegeld"]

If I run nrfjprog --recover --log I get the following error:

PS C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin> nrfjprog --recover --log
WARNING: Logging is unavailable. nrfjprog.exe does not have write
WARNING: permission for the log file
ERROR: Unable to connect to a debugger.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
PS C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>

[/quote]

So I didn't make a difference running it from an admin window?

[quote user="Niels Redegeld"]I can't upload to my boards so currently the DC/DC is not Disabled[/quote]

What I tried to ask was if it was enabled when you were able to flash them?

RE: Boards getting bricked

Niels Redegeld — Wed, 27 Mar 2024 07:39:41 GMT

If I run nrfjprog --recover --log I get the following error:

RE: Boards getting bricked

mathiaso — Mon, 25 Mar 2024 15:05:46 GMT

[quote user="Niels Redegeld"]PS C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin> nrfjprog --recover --log
WARNING: Logging is unavailable. nrfjprog.exe does not have write
WARNING: permission for the log file
ERROR: Unable to connect to a debugger.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
PS C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>[/quote]

Could you try running "nrfjprog --recover --log" from an admin window to see if this will let you provide some logs?

[quote user="Niels Redegeld"]The DC/DC was set automatically to yes in the config file, so I turned it off: CONFIG_BOARD_ENABLE_DCDC=n
The periods I could flash the chip was about a week to two weeks per chip,[/quote]

And in these periods the DC/DC was enabled?

RE: Boards getting bricked

Niels Redegeld — Fri, 22 Mar 2024 13:09:39 GMT

It did not make a difference no, I'll have to look in getting a shunt capacitor, but I dont think the problem relies here. I want to know how to unbrick the boards, before I can even test the solutions.

RE: Boards getting bricked

mathiaso — Fri, 22 Mar 2024 08:00:33 GMT

[quote user="Niels Redegeld"]The DC/DC was set automatically to yes in the config file, so I turned it off: CONFIG_BOARD_ENABLE_DCDC=n[/quote]

But it didn't make any difference disabling it?

Do you know if you have the internal pull-up on the reset pin active? I can see you have added an external one. It could also be an idea to add a shunt capacitor to the pin. There isn't a problem with the switch there?

RE: Boards getting bricked

Niels Redegeld — Fri, 22 Mar 2024 07:24:51 GMT

The DC/DC was set automatically to yes in the config file, so I turned it off: CONFIG_BOARD_ENABLE_DCDC=n
The periods I could flash the chip was about a week to two weeks per chip,

I know that its not the debugger, it works fine when I connect it to a DK.

They didn't work, I wouldn't know why cause I hadn't even flashed something to it yet.

RE: Boards getting bricked

mathiaso — Thu, 21 Mar 2024 08:59:01 GMT

Could you check that the DC/DC hasn't been set automatically?

For how long were you able to flash your boards before you lost communication with them?

Have you tried using a different cable? Or a different debugger?

Would you be able to see if you can communicate with the two remaining boards?

RE: Boards getting bricked

Niels Redegeld — Wed, 20 Mar 2024 13:48:12 GMT

I use the nRF Connect SDK, version 2.5.2.
Well the firmware is changing continuesly but when it stopped working I had not changed anything.
currently 3/5 units are bricked, but I haven't tried the other two yet.

RE: Boards getting bricked

mathiaso — Wed, 20 Mar 2024 13:43:17 GMT

Ok. Are you using nRF5 or nRF Connect SDK?

Has anything in the firmware changed since you were able to flash the boards? And how many boards have stopped being able to connect vs. still being able to connect to the debugger?

RE: Boards getting bricked

Niels Redegeld — Wed, 20 Mar 2024 09:59:12 GMT

I did not manually enable the DC/DC regulator in the firmware.

RE: Boards getting bricked

mathiaso — Wed, 20 Mar 2024 09:49:26 GMT

Thank you, Niels.

Do you know if you have enabled the DC/DC regulator in the firmware? If this is done without having included the necessary inductors in the schematic, the regulator may become unstable and not be able to deliver sufficient voltage to the SoC.

RE: Boards getting bricked

Niels Redegeld — Wed, 20 Mar 2024 07:27:58 GMT

I use version 10.24.0
The debugger I use is the J-link edu mini
I think it already has the latest firmware

The schematics are added as a pdf file.

PS C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin> nrfjprog --recover --log
WARNING: Logging is unavailable. nrfjprog.exe does not have write
WARNING: permission for the log file
ERROR: Unable to connect to a debugger.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
PS C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>

I dont think this helps much.

devzone.nordicsemi.com/.../BLE_5F00_BreadBoard_5F00_Schematic-_2800_2_2900_.pdf

RE: Boards getting bricked

mathiaso — Tue, 19 Mar 2024 08:53:23 GMT

Ok. Could you please provide some details on the following?

Version of nRF command line tools
What kind of debugger you are using
- It may be an idea to update the firmware version of your debugger.
Schematic of your custom board and the connection between your debugger and custom board
Output log (add --log at the end of the command)

RE: Boards getting bricked

Niels Redegeld — Mon, 18 Mar 2024 13:35:56 GMT

I have tried running that as well. It gave the same error unfortunatly.

Kind regards,

Niels.

RE: Boards getting bricked

mathiaso — Fri, 15 Mar 2024 09:30:47 GMT

Hi, Niels.

Have you tried running "nrfjprog --recover" instead of "nrfjprog --reset"?

Best regards,
Mathias