• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 74 subscribers
  • Views 3284 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 271333
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Requirements for re-flashing firmware on nRF52840

GriffinMeyer

Hello,

I have an nRF52840 on a custom board. The nRF52840 has been pre-flashed with the Adafruit UF2 bootloader for early development exploration. As the project moves forward, I'd like to use the Nordic SDK/Segger embedded studio to develop firmware to ensure performance and have access to encryption libraries.

Currently, the board is able to have new firmware flashed via the Arduino IDE. However, for obvious reasons, SEGGER Embedded Studio and the nRF Connect Programmer won't recognize the board. My assumption is that I will have to re-flash the bootloader to a Nordic provided one using a j-link in order to have the nRF Connect suite of tools properly recognize and program the board.

My questions are as follows:

1) Are my above assumptions correct?

2) What pins will I need to have access to in order to use a j-link to reflash the nRF52840's bootloader on my custom board

3) Would I be able to use an RF52840-DK to flash the nRF52840 bootloader on my custom board? Or would it be smarter to purchase a stand alone j-link?

4) Assuming I am able to flash a supported bootloader, would I still have access to a DFU mode that would allow firmware updates over USB?

Thanks in advance, I hope everything is clear!

Griffin

Parents
  • +1

    Hi Griffin

    1. I think you have misunderstood somewhat. You won't need a bootloader on your custom board SoCs if you have a debugger (or nRF52 DK) available and the SWD pins are available on your custom board(s). Connecting the J-Link debugger to the custom boards' SWD pins while powering the board should let you flash program and debug these devices as well. No bootloader needed. A bootloader will be necessary if you don't have access to the debug interface on the board or you don't have a debugger available.

    2. You will need access to the SWDIO and SWDCLK pins as well as VDD and GND to connect to a debugger/DK.

    3. Yes, you can use an nRF52840 DK to flash and debug custom board. Please see section 8.10 Debug output in the nRF52840 DK user guide for details.

    4. If you flash a bootloader supporting USB firmware updates onto your board, then yes. Here is a list of the DFU bootloader examples we provide.

    Best regards,

    Simon

Reply
  • +1

    Hi Griffin

    1. I think you have misunderstood somewhat. You won't need a bootloader on your custom board SoCs if you have a debugger (or nRF52 DK) available and the SWD pins are available on your custom board(s). Connecting the J-Link debugger to the custom boards' SWD pins while powering the board should let you flash program and debug these devices as well. No bootloader needed. A bootloader will be necessary if you don't have access to the debug interface on the board or you don't have a debugger available.

    2. You will need access to the SWDIO and SWDCLK pins as well as VDD and GND to connect to a debugger/DK.

    3. Yes, you can use an nRF52840 DK to flash and debug custom board. Please see section 8.10 Debug output in the nRF52840 DK user guide for details.

    4. If you flash a bootloader supporting USB firmware updates onto your board, then yes. Here is a list of the DFU bootloader examples we provide.

    Best regards,

    Simon

Children
No Data
Related
Terms of service