• State Not Answered
  • Replies 18 replies
  • Subscribers 69 subscribers
  • Views 1301 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 323801
Options

Boards getting bricked

Niels Redegeld

Hello,

I am trying to develop using a custom pcb. And after some time my boards stop connecting to the debugger. How do I unbrick the boards? I have read multiple solutions like connecting pin 18 to vdd which did not work. When I run nrfjrog --reset I get the following error message: 

[error] [ Worker] - An unknown error.
[error] [ Client] - Encountered error -102: Command connect_to_emu_with_snr executed for 221 milliseconds with result -102
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.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
PS C:\Program Files\Nordic Semiconductor\nrf-command-line-tools\bin>

I know it has something to do with reset pins or something, so I will be defining the reset pin in my boardfile, but does that fix the issue or is there a better fix.

Kind regards,

Niels Redegeld

Parents Reply Children
  • 0 in reply to Niels Redegeld

    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?

  • 0 in reply to mathiaso

    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.

  • 0 in reply to Niels Redegeld
    Niels Redegeld said:
    The DC/DC was set automatically to yes in the config file, so I turned it off: CONFIG_BOARD_ENABLE_DCDC=n

    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?

  • 0 in reply to mathiaso

    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.

  • 0 in reply to Niels Redegeld
    Niels Redegeld said:
    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>

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

    Niels Redegeld said:
    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,

    And in these periods the DC/DC was enabled?

Related