Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

PaKa — Tue, 28 Aug 2018 07:00:07 GMT

Hi,

if you get a SAM-BA bootloader running on the SAM device (it may report as whatever if you haven't installed the SW package so check what shows up when you plug in the USB Cable) then you don't need any HW, the protocol uses the USB interface on the SAM.

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

wanyancan — Mon, 27 Aug 2018 14:53:53 GMT

[quote userid="46557" url="~/f/nordic-q-a/37759/alternative-way-to-re-flash-interface-mcu-using-tc2050-j3-on-pca10040/145974"]If this is the case you need to use SAMBA (old Atmel program so should be available from the MCHP website) to upload the bootloader[/quote]

I guess SAM-BA won't allow me to use another N52 DK board to upload bootloader using SWD interface.

What hardware is required to upload bootloader with SAM-BA? Currently when I plug in the broken DK board with USB cable, nothing is recognized at all.

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

PaKa — Mon, 27 Aug 2018 14:47:51 GMT

Hi,

the Atmel device contains a ROM bootloader so if the flash is empty I do believe it will still show up as a USB device. If this is the case you need to use SAMBA (old Atmel program so should be available from the MCHP website) to upload the bootloader. Then the mass storage option should show up again.

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

wanyancan — Mon, 27 Aug 2018 14:15:26 GMT

Awesome! I'll give it a shot and let you know later!

THANK YOU!

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

bjorn-spockeli — Mon, 27 Aug 2018 14:09:53 GMT

It could be that the bootloader on the ATSAM3 has been erased and there is no firmware runing on the device that requires the external 12Mhz XTAL to run. I have attached both the JLINK firmware as well as the bootloader .bin files.

devzone.nordicsemi.com/.../JLINK-Restore.zip

Best regards

Bjørn

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

wanyancan — Mon, 27 Aug 2018 13:37:54 GMT

Sorry I didn't make the question clear.

The following picture is from nRF52 DK Hardware Files V1.2.1

The problem is as below:

In rectangle 1, the LD5 didn't light up no matter whether the DK board is in normal mode or bootloader refreshing mode (after holding reset during power on). The PC can't detect any mass storage device.

So I measure the XTAL(X3)'s XOUT pin with oscilloscope in rectangle 2. No clock running at all.

I want to buy JLink programmer with SWD debug cable connecting to J3 Interface MCU programming connector. I'm trying to write flash directlly to this SAM3U.

Now the question is, if the SAM3U chip is still fine, am I able to reprogram interface MCU using nRF5x-OB-JLink-IF (nRF5x-OB-mbed-IF as well) firmware ? Am I able to program it without its X3 crystal running?

Best Regards,

Leo

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

bjorn-spockeli — Mon, 27 Aug 2018 09:08:00 GMT

HI Shun, are you referring to the X20 crystal or are you referring to the SWDCLK pin of the ATSAM3U?

RE: Alternative way to re-flash Interface MCU using TC2050(J3) on PCA10040?

wanyancan — Sat, 25 Aug 2018 04:34:15 GMT

I found that the XTAL pin is not running at all. Does it mean that the Interface MCU SAM3U is already dead?

From DAPLink's source, usually the bootloader is always able to run no matter what flash is written. And the LED indicator is the first thing when the MCU boots.

I guess it's not possible to program it any more.