Adalm Pluto+ bricked

    I have recently received a 'fresh" Adalm pluto+. I could not connect nor ping via the built internet adapter (RJ45) . I could however ssh via the USB-virtual LAN.
    In the process of updating the FW I apparently bricked the device. NO response any more, not even in DFU-mode.
    So now I will have to try JTAG ...


    I have a couple of questions:
    1)On my board the power supply on the JTAG connector on the PCB is marked 3.3V instead of 1.8V as I have seen on all photos in the internet.
    And yes, I do measure 3.3V. Does somebody know of such a board? I guess I will still need to interface the JATG pins with 1.8V, as they are directly connected to the Zynq?

    2)On the internet it is mentioned that in order to recover via JTAG an Analog board named ADALM-UARTJTAG is required. Why do I need this board? I have flashed the Zynq in a redpitaya using HS2 from Digilent. I would expect the JTAG to be identical.

    Any help is very welcome.

    73 Wolfgang

    Hello,


    if the hardware is not damaged, check on the site of Analog D. There are all instruction to recover from DFU.

    Any other method are useless, and more difficult.


    Search right information and retry the DFU procedure.


    Otherwise translate this link:

    Procedura di recovery Adalm Pluto - Modalità DFU
    IS0GRB atv antenne autocostruzione winlink winmor echolink proxy riparazioni radio navtex radioascolto comunicazioni digitali ripetitori Roberto abis
    www.is0grb.it




    Good luck.


    73

    • New

    I also got stuck within a day after uploading dirty pluto+ firmware for QO-100.

    Using a Raspberry pico and an article on github (https://github.com/plutoplus/plutoplus/issues/51) is was able to flash the pluto with the jtag bootstrap firmware and all went well and i was in DFU mode.

    However, i could not continue flashing firmware with DFU. The cmd box in windows told me:


    Match vendor ID from file: 0456

    Match product ID from file: b673

    No DFU capable USB device available.


    I detach the Pluto+ from the PC and reconnect, tthen he Pluto is not in the list of USB items anymore. Also not when holding the DFU button.


    What firmware did you use to unbrick via JTAG ?

    Matbe that's where i go wrong....

    I have the Pluto+version 2 with 3.3V - one week old.

    • New

    JP,


    Thanks for the boost of confidence.

    I found the serial port on the P+ and will hook it up to the Win11 with an usb-to-serial converter.

    I gues i have to use the power and not the data connector to power the P+

    I keep you informed and will write the whole procedure for others, once it is working.


    Erik, PA0ESH

    • New

    Yes Erik


    on the issues link you provided me, you see that the Pluto+ is at the same time connected to the serial port as the Xilinx Programmer


    take 115200 baud in putty or other, then you will see activity on the serial port


    just a simple usb-to-serial FTDI, or CP210x will do


    at the time I reflashed it, the RPI-Zero solution was not available.. I bought a DLC10 Xilinx programmer


    jtag doesn't flash but boots in RAM... so immediate flash is necessary DFU-util does the trick


    I suppose you know that..


    JP

    • New

    Erik


    That was indeed my procedure ! So I did not write down, since it is written there and exactly what to do !

    Thought you allready did this !


    1. Plug in JTAG as documented above into Pluto and verify you can connect with Vivado
    2. Download the JTAG bootstrap zip from the firmware release page (plutosdr-jtag-bootstrap-<Firmware Version>.zip)
    3. Unzip the zip then source the run.tcl inside with xmd from the Xilinx tools (xmd -tcl run.tcl). We are done with JTAG now
    4. Next plugin a USB cable to the UART port of the ADALM-UARTJTAG connector and open a serial session (Putty or screen or …)
    5. At this point you should have access to the u-boot menu. Directly from u-boot serial console type: run dfu_sf. This will put PlutoSDR into DFU mode.
    6. Now plugin PlutoSDR's data USB port to your PC and it should appear as a DFU device
    7. Flash the firmware as usual with the DFU utils as documented here


    Normally you have to see in STEP 4.. reaction on your serial port !


    JP

    • New

    JP,

    I succeeded in unbricking but it is still different that you wrote.

    Few things were bugging me.

    First of all you have to run xvcd-pico.exe from a CMD box which you opened as administrator. Even running xvcd-pico.exe as administrator did not always work.

    Secondly check your USB cables. Mine had a flaky one.


    The connections from P+ to my laptop are now as follows:

    USB data from P+ to laptop USB

    JTAG connector P+ to Raspberry PICO and Pico to Laptop. Flash the PICO with xvcPico.uf2

    Jumper P+ URST-MIO52


    Then on your laptop first start Vivado.

    Then plug in the Pico (if not already) and you should hear the connection sound.

    Then start the extracted xvcd-pico.exe file, which acts as a server for the Vivado application to communicate with the Pico.

    Now in Vivado you can open the hardware manager, click on auto connect, and right click on that --> Add Xilinx Virtual Cable (XVC)

    Follow the procedure here https://github.com/plutoplus/plutoplus/issues/51

    Now you'll hop over to the official plutosdr firmware page on Github (this is for the official Adalm Pluto but works fine) and download the plutosdr-jtag-bootstrap zip file.

    From this file, you'll need to extract the run-xsdb.tcl file to a folder you can easily access. I expanded all the file to c:\plutosdr-jtag-bootstrap-v0.39.

    Now in Vivado, you'll find a console on the bottom.

    In the console navigate to your folder, mine was c:\plutosdr-jtag-bootstrap-v0.39

    You can check you are in the right place by typing dir in the command box


    cd c:\ plutosdr-jtag-bootstrap-v0.39

    dir


    Now that we're in the folder containing the script, we will execute the script.

    Before that, make sure you have set your Jumper to URST-MIO52, then while holding the DFU button run it by executing:

    exec xsdb run-xsdb.tcl

    You should hear a USB connection sound if successful, you can now let go of the DFU button.

    You should find the "USB download gadget" in the Eject USB device list.

    Great, you've entered DFU! And it means that the data usb connector on the P+ is already active.


    Then open another cmd box on your laptop as administrator

    Navigate to the directory where the firmware files are and where dfu-util is (i put them all together in directory c:\dfu


    Since the P+ is still in DFU mode (you can still check the ejec list on your laptop) we can now direct start flashing the P+ with the DFU method:


    dfu-util -a firmware.dfu -D ./plutoplus.dfu. (takes the longest)

    dfu-util -a boot.dfu -D ./boot.dfu

    dfu-util -a uboot-env.dfu -D ./uboot-env.dfu


    After this is done, you can unplug the Pluto+ SDR, set the jumper back to URST-MIO46 and plug the Pluto+ SDR back in.

    It should now boot up with the new firmware.

    It did with mine. Now on to configure.


    Have a nice weekend and thanks for the support


    Erik, PA0ESH