Post Go back to editing

Problems with using the Pluto as a Standalone Device


I've managed to use my ADALM-PLUTO with Python, but I'm trying to get it to work standalone now and having issues.  Trying the shell script method:

Bash scripts don't seem to work, the LED blinks according to the wiki, but the file does not get created on the thumb drive.  I have checked:

  • thumb drive formatted as FAT32
  • script was made in Ubuntu using nano/terminal, and I have verified the EOL characters are "\n"
  • filename is "", so there is the .sh at the end as per:  RE: Adalm Pluto Standalone Executable using OTG

I gave up and tried following the C build steps here:

However, I had a few problems:

  • The wiki asks for the Linaro i686 package, but I needed to use the x86_64 package, or the terminal won't recognize the files
  • I upgraded to the 7.5.0 version instead of the 7.2.1 version, I don't remember my reasoning for this, but as I'm using firmware version 0.35, it seemed like the right thing to do

When I compile the example, I get an error that it can't find stdint.h, and if I compile with the -ffreestanding flag (a fix I found on Stack Overflow), it fails and can't find string.h, so obviously there is something else wrong here.  I'm using an Ubuntu VM host, so I'm using the command on the wiki page that starts with arm-linux-gnueabihf-gcc.  I also made sure that my sysroot download is 0.35.

I'm completely out of ideas, any pointers or recommendations would be greatly appreciated.

Parents Reply
  • So I managed to get past this by "sudo apt-get install gcc-multilib", and now running "arm-linux-gnueabihf --version" works, but running the compile command fails:

    I got around this by "sudo apt-get install  zlib1g:i386", which I realize might be dangerous, given the Pluto needs i686 not i386, but zlib1g:i686 didn't exist so I figured it was worth a shot.  The compile command now fails in a different way:

    I feel like I'm missing something simple and stupid here, any ideas?