Adalm Pluto
Rebuilding a Pluto
Despite AD revising the PCB to cure the earth problems, I am still becoming quite an expert in bringing Plutos back to life.
I know there has been a long thread on this but below is the short sequence I follow and I thought maybe useful for others at some point.
If your Pluto is not recognised over USB (not bing bong windows noise) and just LED1 glows dimly - press the reset button (pin hole next to the USB port) and whilst holding it in, plug the pluto in to the USB port of your PC.
Let go of the reset button and it should now be recognised by the PC and active LED glow brightly - it is now in DFU mode.
Download the latest AD firmware https://github.com/analogdevicesinc/plu ... -v0.33.zip
Unzip the file and save into a directory.
Download "update.bat" https://raw.githubusercontent.com/analo ... UPDATE.BAT and save in to the same directory.
Open up a command line (type cmd on the windows search bar) and navigate in to the directory where you saved the files.
Type
Code: Select all
update.bat pluto.dfu
and things will happen on the screen for about 30 seconds
When finished type
Code: Select all
update.bat uboot-env.dfu
and more things will happen on the screen for about 2 seconds.
Unplug the Pluto from the USB port, wait 5 secs and replug - it should be alive again!
Frequency extension
Now you need to do the frequency extension - the easy way is to run the marvellous spectrum analyser / tracking generator SATSAGEN program. This will do the frequency extension and dual core mod for you when first started with your "new Pluto".
Download it from here - you'll be glad yopu did! https://www.albfer.com/satsagen-download-page/#content
If you want to do it manually - log in to 192.168.2.1 via SSH (user root, p/w analog)
Type the following to check your unit is not extended:
Code: Select all
fw_printenv attr_name
- Error: "attr_name" not defined
fw_printenv attr_val
- Error: "attr_val" not defined
Now type the lines not starting with the # (lines with # are what the Pluto returns).
Code: Select all
fw_setenv attr_name compatible
- fw_setenv attr_val ad9364
If you have a REV D PCB and / or firmware revision v0.32 YOU MUST ADD AN ADDITIONAL COMMAND
Code: Select all
fw_setenv compatible ad9364
Then type
Code: Select all
reboot
DATV firmware
Finally, if you want to use it with Portsdown, you need to change the Firmware to F5OEO "only for the Brave" - (no other version works, so don't even try it!).
Download the firmware from the BATC wiki https://wiki.batc.org.uk/File:FIRM2101RC.zip - unzip and save the Pluto.frm (note you can not tell the difference between file versions) so save it somewhere special!
Plugin the Pluto which will open a window listing the files on the Pluto drive. Copy the Pluto.frm file in to the window.
Right click on the Pluto USB drive letter in the Windows listing on the lefthand side of the screen and select eject - DO NOT unplug the Pluto. The Pluto LED will flash quickly for about 2 minutes, after which it will reboot and open the window listing files on the Pluto drive.
Double click on info.html and it will show the F5OEO dashboard - and that's it done, until the next time!!