Need interface MCU initial boot firmware

RE: Need interface MCU initial boot firmware

jeffd — Sun, 26 Sep 2021 10:38:06 GMT

to come full circle and close the issue... I received another board from a coworker that had not been used yet and that board was doing the same thing (windows detected plug in, rapidly flashing led5, no JLINK device). So, now i was on the track that it was something under windows that is causing the issue. apparently the rapidly flashing led5 indicates that USB enumeration isn't completed, I noticed in device manager under 'system devices' that there was a USB/IP device with the warning triangle. i uninstalled that driver and restarted the board and it enumerated correctly and the JLINK firmware came up completely. Same with my original board. a couple weeks ago when i first received the board i was working on a way to share the USB device with an Ubuntu install on WSL 2. I was using the USBIP project to do this. When I decided it was too much of a hassle to keep going with that effort for the time being (secure boot needed to be disabled, etc), I turned off the USBIP binding to the SEGGER USB device. At some point soon after i messed up the JLINK firmware as well. Nothing in any of the help searches turned up anything about making sure that there wasn't another driver trying to claim the device, and the blink codes for the SEGGER firmware were hard to figure out. At any rate, everything is working now and there should be some information in the Nordic docs that speak to the SAM-BA ROM monitor code in the SoC that can be used to recover the bootloader firmware and restore the operational JLINK firmware from there. Currently the documentation basically says you can't do anything if the bootloader is corrupted and that's absolutely not the case, and in reality there's really no reason that the SAM-BA recovery method wouldn't ever work that i can tell.

RE: Need interface MCU initial boot firmware

Einar Thorsrud — Thu, 23 Sep 2021 10:47:46 GMT

Not really, unfortunately. We are not experts on these details though, as this has been made by Segger. Perhaps it is worth asking them?

RE: Need interface MCU initial boot firmware

jeffd — Wed, 22 Sep 2021 13:04:35 GMT

this image will go into the bootloader with IF/BOOTRESET button, but after a little while, led5 goes from a slow blink to a 1Hz blink and USB disconnects. If i do a normal boot again after that, i get no USB connection (no bell from Windows) and no led.

with this bootloader i can drop the DAPLink FW onto the device and it boots into that normally as expected.

RE: Need interface MCU initial boot firmware

jeffd — Wed, 22 Sep 2021 12:54:40 GMT

any explanation why the DAPLink FW seems to work just fine? I'm able to download applications to the nrf52832 all day long no issue.

RE: Need interface MCU initial boot firmware

Einar Thorsrud — Wed, 22 Sep 2021 12:37:05 GMT

I see. In that case I suspect there may be some other issue on the board as well, as you should have the exact same firmware as the DKs are shipped with after doing that.

RE: Need interface MCU initial boot firmware

Einar Thorsrud — Wed, 22 Sep 2021 12:32:43 GMT

This is the entire flash image which needs to be flashed with the SAM-BA interface or JTAG. In production we get empty chips and flash this and only this image.

RE: Need interface MCU initial boot firmware

jeffd — Wed, 22 Sep 2021 12:18:52 GMT

no joy. flashing via SAM-BA gives the exact same results of a 10Hz flashing led5, no JLINK drive. Windows recognizes something is connected, but i don't see anything in device manager.

RE: Need interface MCU initial boot firmware

jeffd — Wed, 22 Sep 2021 12:15:18 GMT

so is the .bin file below the entire flash image (which would need to be flashed via the SAM-BA interface or JTAG)? or is it an encapsulated .bin that will be able to be downloaded by the currently installed bootloader and do a self-update?

i'm going to start with SAM-BA programming and see what happens.

RE: Need interface MCU initial boot firmware

Einar Thorsrud — Wed, 22 Sep 2021 10:48:19 GMT

I checked with the production guys, and they now use a single binary in production: devzone.nordicsemi.com/.../concat_5F00_mbed_5F00_170117_5F00_jlink_5F00_180712.bin. Can you try with this?

RE: Need interface MCU initial boot firmware

jeffd — Tue, 21 Sep 2021 12:23:33 GMT

what started this in the first place is the same problem lots of people have, when the firmware in the interface MCU is overwritten/corrupted somehow they are unable to restore it. I don't really know how it got corrupted though, i read something about how when the JLINK Commander/Configurator attaches it automatically attempts to update the JLINK FW to the latest? i didn't recall seeing any sort of popup asking if that's what I wanted, and if it just does it without asking i think that's poor user experience/expectations.

when i somehow lost the JLINK firmware (i did see it at least the first time i plugged it in), i tried the normal process of restoring as described for the typical usage model of drag/drop but that obviously wasn't working. because this issue has already cost me several days of possible development (i didn't even start yet) i didn't want to have to wait for a new DK to be sent to me and figured there must be a way to reflash it myself. so as I do, I dug into the documentation of the SAM3U part and figured out there's a (mask?) ROM'd monitor that can be used to recover so i did that.

So i'm guessing that the mbed bootloader that's linked on the nrf52 DK page is an updated bootloader with a flash progamming bit of code included because the bootloader can't do self-update (it's only XIP?). the bootloader that i got from the .zip file must just be the mbed bootloader itself with no flash progamming update code...

either way, i'm unable to recover the JLINK FW for some reason.

see my other post, i was able to install the DAPLink FW just fine using their bootloader.

RE: Need interface MCU initial boot firmware

Einar Thorsrud — Tue, 21 Sep 2021 11:52:22 GMT

Hi,

You are right that you can re-program the onboard debugger IC using the firmware (bootloader and J-Link application firmware) from the JLINK Restore.zip found in this post. You can also refer to the more extensive documentation from Segger. Based on what you have described you have done as explained in the document, and also installed the J-Link OB-SAM3U128-V2-NordicSemi 170213.bin via DFU, so it should be OK.

Regarding size that is no problem. You can fit both the bootloader and the application, and this is what is used in production of the DKs. If you do a flash erase of the debugger IC and programs the bootloader, you should then be able to install the J-Link firmware by drag-and-drop (USB DFU), and you would end up with the same configuration as the DKs are shipped with.

I am not sure what to make of the states described in your last post, to be honest. May I ask why you started endeavor this in the first place? Perhaps that can also give some hints on the issue you are seeing.

RE: Need interface MCU initial boot firmware

jeffd — Mon, 20 Sep 2021 22:26:23 GMT

it would seem that there's an issue with the size of the firmware for the interface MCU..... if they are intended to live together in the flash of this device, the MBED firmware binary from the Nordic download page is 35K, and the JLINK firmware binary is 108K, there's some overrun because there's only 128K of flash in this MCU. (verified by reading the CHIPID register and issuing the flash read descriptor.)

last thing i've tried today is concatenating the smaller mbed firmware with the JLINK firmware (padded to the next 1K boundary, i presume the bootloader starts scanning there) in a single file and sending that to the flash with the SAM-BA loader and rebooting. I get the same 10Hz flashing led5 as above, rather than the MBED bootloader led 1/2Hz flash. holding the IF/BOOTRESET and powering up give me the BOOTLOADER drive (as expected), which flashes at 1/2Hz for a bit and then disconnects from USB and then flashes at 1Hz. power cycling after that results in no led flashes, as though the JLINK firmware doesn't start at all...... maybe the MBED bootloader erases the application flash area? i'm able to go to BOOTLOADER again and drag/drop the JLINK FW again, a reboot gets the 10Hz flash.

RE: Need interface MCU initial boot firmware

jeffd — Mon, 20 Sep 2021 20:52:02 GMT

ok, for any subscribers of this issue, some further debug and i've gotten the mbed bootloader back installed and showing up as a drive. i actually found this link: https://devzone.nordicsemi.com/f/nordic-q-a/37759/alternative-way-to-re-flash-interface-mcu-using-tc2050-j3-on-pca10040 which describes exactly what i already figured out by reading the AT91SAM3U2 datasheet and the nRF52 DK schematic. (forgot to mention, applying VDD to the cut SB31 was simply a wire on one of the nRF current management pins to SB31 1/2 moon closest to the chip for a second while applying power).

when i used the 140828_MBED_bootloader.bin from the link above (scroll down to the bottom, file is JLINK Restore.zip) i'm able to get back to the BOOTLOADER drive with the IF/BOOTRESET button.

previously, the firmware i was trying to load was called nrf5x_atsam3u2c_if_mbed_V0221_11012017.bin (a 35K file), vs the 140828_MBED_bootloader.bin file which is 19K. The nrf5x_xxx file is what you get from the nRF52 DK downloads page.

please note that the above zip file has a guide in it that basically says that it may not work in all cases, so YMMV. If you have a new board like mine, be aware that the SB31 is shorted to GND, use a razor blade to cut the link. The MCU has a permanent pulldown already so it should work as normal without it.

i'm still not able to get the board to show up as a JLINK device though, but after sending the JLINK firmware to it and restarting, LED5 is flashing pretty fast, maybe 10Hz. windows recognizes *something* based on the sounds, but nothing shows up in device manager. i'm wondering if the security bit needs to be enabled for the JLINK firmware to boot. perhaps they are protecting it? well, just tried that and it didn't make a difference. continue digging.