• State Verified Answer
  • Replies 4 replies
  • Subscribers 73 subscribers
  • Views 4000 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 110612
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ATSAM3U4 bootloader problem

MC

I have somewhat unusual problem and I would appreciate your help on this topic.

So, to sum up my problem, I have NRF51-DK development kit and I accidentally "fried" the board when high voltage (12V) somehow got onto the SWD interface pins. I therefore un-soldered both the NRF51822 chip and interface MCU. I bought a new interface IC, the ATSAM3U4, which is basically the same as the original ATSAM3U2 which was originally on the board, except it has dual bank flash, but in my opinion, it shouldn't make any difference in operation.

And now for my question. I have downloaded CMSIS-DAP project from mbed's gitlab and I appear to be stuck ever since. How can I reflash the stock bootloader on the interface MCU from SAM-BA to mbed's MSD bootloader? I was trying to set the start and size of the flash and RAM in keil but with no success. I keep getting the 'No algorithm found for the range' error. Is there any documentation about flashing the MSD bootloader onto interface MCU? I don't seem to be able to find any and I am a bit confused by flashing procedure.

Thanks, Matic

Parents
  • 0

    Hi.

    The stock bootloader is made by Segger, and is not something i have access to unfortunately.

    You might make it work by flashing the mBed CMSIS-DAP firmware to the ATSAM chip. In order to flash anything to the ATSAM chip, you need a programmer/debugger compatible with it. I am not sure what interface it supports, but i am guessing JTAG or SWD. (You can not program it with the usb connector on the board).

    You could also try to connect directly to the nRF51 with an external JLINK adapter from Segger, or a cheaper CMSIS-DAP debugger.

    -Anders

  • 0 in reply to Anders Strand

    Hi, I have an Ulink 2 programmer with me, so there should be no problem regarding this. I can read device signature from Keil, so I know it works.

    The problem is more in terms of actual flashing procedure, i.e. to which address should I flash the CMSIS-DAP firmware and how can I erase the stock SAM-BA bootloader which is already on the ATSAM chip? Do I even need to erase it, or should I flash CMSIS-DAP "behind" the stock bootloader?

    -Matic

Reply
  • 0 in reply to Anders Strand

    Hi, I have an Ulink 2 programmer with me, so there should be no problem regarding this. I can read device signature from Keil, so I know it works.

    The problem is more in terms of actual flashing procedure, i.e. to which address should I flash the CMSIS-DAP firmware and how can I erase the stock SAM-BA bootloader which is already on the ATSAM chip? Do I even need to erase it, or should I flash CMSIS-DAP "behind" the stock bootloader?

    -Matic

Children
No Data
Related
Terms of service