Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

Reprogramming the Interface MCU on nRF52 Dev Kit

I am trying to become familiar with nRF52 code by developing on the nRF52 Dev Kit.  However, I seem to have somehow "broken" the interface MCU code.  It stopped allowing me to transfer code to the nRF52832 chip (drag-n-drop). So I decided to reprogram the interface MCU (ATSAM3U2C) with the code I found here: nRF52 DK - Downloads - nordicsemi.com.  However, after flashing this with my JLink tool, it appears that I also need a bootloader for the iMCU as well and I haven't been able to find any binaries for this.  Am I correct that the mcu needs two binaries (j-link-ob-sam3u128-v2-nordicsemi-170724.bin & a bootloader)?  If so, where can I find the missing bootloader file?  If not, what else must I do?  Note that the "j-link-ob-sam3u128-v2-nordicsemi-170724.bin" flashes and verifies correctly.

Parents Reply
  • Progress!  After loading the .hex from your link, the functionality has returned such that the LED flashes and the board comes up as a USB drive when I power up with reset held.  However, now I am back to the original scenario where when I drag the "j-link-ob-sam3u128-v2-nordicsemi-170724.bin" file, Windows says that there is not enough room in the target to copy the file. Maybe I could load this file directly with the standalone JLink if I had the correct address?  The default address will overwrite the new code.

Children
  • Hi, 

    Do all other functions work? Do you see the derive come up as "BOOTLOADER" at this end? This is an important checkpoint. It must come up as "BOOTLOADER". if not, you programmed the actual nRF instead. 

    For the drag-and-drop, you can try to run "MSDDisable" via "J-Link Commander" on the kit. 

    Since the image is provided by my colleague instead of an official source, there are no guarantees. 

    -Amanda

Related