Post Go back to editing

Unbricking ADALM1000 Rev D

Category: Hardware
Product Number: ADALM1000 Rev D Z
Software Version: Pixelpulse2 latest, ALICE latest

After I plugged in my new M1K to the PC and upgraded the firmware, as many tutorials suggest, I got a dead brick: it does not light up when connected and Windows does not recognize it at all.

This is very frustrating, as I didn't manage to do *anything* with the board, not even clicking the run button prior to upgrading. And now it's a brick.

I'm following this answer  ADALM1000 was not recognized by Pixelpulse2. 

I've already managed to solder the pins and now Windows recognizes it as "ADALM1000 SAM-BA WinUSB driver", and Pixelpulse shows it's in programming mode. But I don't see any corresponding COM port to be used in BOSSA. So I'm unable to flash the board.

Any hints on that? I also have Ubuntu 22.04. Perhaps, you have a remedy that could be used in Linux if Windows fails? Or maybe I'm missing some ADALM software installed? I've installed Pixelpulse2 , ALICE, and libsmu.

Thanks.

  • When you say "managed to solder the pins"

    to put it in the boot loader you just momentarily shorted them and not bridged across with solder. These pads need to be open for normal operation.

    Which USB port does the Windows device manager say it is connected to. Is the board connected to an internal USB port on the computer or through an external HUB. It might make a difference. If you can figure out which COM port Windows has assigned to the board BOSSA should be able to connect to it. Have you tried cycling the board power. Windows needs to re-enumerate what is connected.

  • to put it in the boot loader you just momentarily shorted them and not bridged across with solder. These pads need to be open for normal operation.

    I don't know *how long should I keep them soldered*, and my guess was "as long as I'm in the bootloader mode". I understand that they should be unsoldered after I successfully upgrade the firmware. Should they be shorted only once - momentarily - as you say and it is not necessary to keep them shorted for the entire process of un-bricking?

    Which USB port does the Windows device manager say it is connected to

    It appears under "Universal Serial Bus devices".

    Is the board connected to an internal USB port on the computer or through an external HUB

    Tried either way.

    Have you tried cycling the board power

    Do you mean unplugging and plugging it back? Yes, I did. I'm not aware of other options to "cycle the board power" for this specific device.

  • Oh God almighty, I managed to un-brick it.

    The trick was to choose BOSSA (not ADALM, as the tutorial suggests) in "Let me pick from a list of device drivers on my computer" while updating ADALM USB driver via the device manager. Then COM5 BOSSA port appeared and I managed to flash the latest m10k.bin version with BOSSA. I did NOT manage to update the firmware in any other way. Specifically, I was upset seeing "successfully upgraded" message when I was trying to flash the image with the "smu" command in a terminal: it showed as if everything went smoothly and the device was reflashed, when in fact it wasn't.

    Now the device appears as "ADALM1000" under Universal Serial Bus devices.

    I'd recommend putting this in the how-to.

  • You have the now long out of production Rev D version of the hardware and the only way to flash firmware on that (obsolete) version is with BOSSA. The boot loader code on the Micro has been up-dated in the Rev F version.

    And yes as I guess you surmised the pads should not be soldered, just momentarily shorted, less than 1 sec. The LED will go out almost immediately indicating that the firmware is no longer running and the boot loader is now running.