This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bricked Sparkfun nRF52832?

I have the nRF52DK board and I am using that to reprogram the Sparkfun breakout. However, initially, I was using the Sparkfun Beefy UART device to flash the nRF52832 to begin my SPI project using BLE.

What happened: Firstly, I did something dumb.

Not getting the SPI example to work on the breakout board, I started diminishing the example's main loop to toggle an LED. This, of course, was being done at 3:30AM and I connected the LED to pin 8 and then the board can not be flashed.

In fact, the board does not acknowledge the initial transmission from the nrfutil.py utility.

Onto the nRF52 DK:

I can read the memory on the affected breakout board using the pin 19 interface of the evaluation board. I can erase the memory and write new memory. I even went so far to purchase another breakout board, savebin 512KB of working flash memeory and loadbin this file onto the affected board:

Nothing.

Failed to upgrade target. Error is: No data received on serial port. Not able to proceed.

Possible causes:

  • bootloader, SoftDevice or application on target does not match the requirements in the DFU package.
  • baud rate or flow control is not the same as in the target bootloader.
  • target is not in DFU mode. If using the SDK examples, press Button 4 and RESET and release both to enter DFU mode.

Question:

Is there a low level checksum I can obtain that would indicate whether the board has a hardware failure?

Is the board truly bricked or can it be jump started somehow - like setting a PC register?

Is there a known flash bin file that will do some HelloWorld dance?

Destination green recycle?

Thanks

Parents
  • Hi, have you checked similar questions on the forum, e.g. this one? It's almost impossible to completely "brick" nRF5x chips, they should always be able to "recover" through Nordic tools like nRFgo Studio or nrfjprog with JTAG/SWD programmer (e.g. any Nordic nRF5x DK with SEGGER J-Link on board).

  • Thanks for the input. The insistence on the UART is the setup I had just settled on. I use MacOS and I was able to get a script to compile any SDK example and flash it to the device using the nrfutil program. I am new to this type of activity, so I was elated that things were going so well.

    What is fantastic about this experience is I have a much deeper understanding than what the UART method would have brought. This is important as when I move onto my own circuit board using the nRF52832, I will need to program it somehow and this is where I shall be blessed to have had this experience.

    I anticipate I shall come to understand the system better to be able to explain with certainty why the board is exhibiting the behaviour it is.

    Until then, thank you.

Reply
  • Thanks for the input. The insistence on the UART is the setup I had just settled on. I use MacOS and I was able to get a script to compile any SDK example and flash it to the device using the nrfutil program. I am new to this type of activity, so I was elated that things were going so well.

    What is fantastic about this experience is I have a much deeper understanding than what the UART method would have brought. This is important as when I move onto my own circuit board using the nRF52832, I will need to program it somehow and this is where I shall be blessed to have had this experience.

    I anticipate I shall come to understand the system better to be able to explain with certainty why the board is exhibiting the behaviour it is.

    Until then, thank you.

Children
No Data
Related