My ADALM PLUTO, running on Windows, seems to be stuck in DFU mode with a dim LED showing. This LED bightens when connecting with a pin inserted in the small hole, but there is now flashing LED. The Device Manager simply shows ""USB download gadget", the properties of which are shown as "Pluto SDR DFU". I have tried the prescribed recovery method shown at this address: "https://wiki.analog.com/university/tools/pluto/users/firmware", but to no avail. it seemed to do all the right things under the Command Panel instructions, and showed % completion correctly, but remained (effectively) unresponsive.
Please, what do I do?
We added some documentation around updating the different boot components here: https://wiki.analog.com/university/tools/pluto/users/firmware#debugging_dfu
UPDATE.BAT will not update u-boot, which I believe…
After re-flashing with the UPDATE.BAT script, have you power cycled Pluto?
Hoping this isn't a foolish question, but by "power cycling" I presume you mean unplugging and re-plugging the USB cable? If so, yes - a number of times. All I get is a very dim LED1 light. However, if I apply power with a pin in the small hole (button) I get a continuous bright LED1 light, and I'm also able to see (in Device Manager) "USB download gadget" the properties of which are shown as "Pluto SDR DFU, but no other device on a COM port. Under File Manager there is no sign of the device. Very frustrating being unable to access or re-vitalise what is (hopefully) a viable device.
LED1 should only go into dim mode when in DFU mode. In DFU mode it will appear as a gadget device.
Have you been modifying the firmware or customizing the boot sectors or using Non-ADI firmware?
travisfcollins said:Have you been modifying the firmware or customizing the boot sectors or using Non-ADI firmware?
No, to the above - or at least not intentionally. I did however follow a well-used procedure with the potential to lift the upper frequency to 6GHz. I followed the well used instructions at "Signals Everywhere" https://www.youtube.com/watch?v=5V6CxTBDHVY&t=48s which I believed to be safe. This had worked successfully before, and there was no suggestion that this might put the unit into DFU mode.
If, as you suggest, it IS in DFU mode, is there a safe way to get it out? Or is it terminally bricked? Any guidance would be very greatly appreciated.
I think u-boot is just broken. We are working on a solution that hopefully does not require JTAG from windows. We should have something tomorrow.