Post Go back to editing

Error after updating pluto firmware

Category: Hardware
Product Number: CN0566

I have been using the CN0566 for a phased array radar demo at work and out of the box was working well. I updated the pluto firmware from v0.38 to v0.39 to use the latest code that Jon Kraft has for range doppler plotting and now I am getting an error when I try to run it or any of the other example programs.

The error is thrown when trying to set the gain control mode on the SDR channels to ‘manual’.

It is throwing the error from the attribute.py script in /usr/local/lib/python3.9/dist-packages/adi,

line 69, in _set_iio_attr channel.attrs[attr_name].value = str(value)

AttributeError: ‘NoneType’ object has no attribute ‘attrs’

I had emailed Jon directly and he suggested that I post here and he thought that it might be that the pluto needs to be updated to allow the dual Rx/Tx mode.

I tried to ssh into the pluto to check what the "environmental variables" were and whether it was set up as an AD9361 and dual Rx/Tx but the password keeps getting denied. i had never changed the password but I tried editing the config.txt file to reset the password anyway, but that is not solving the issue. 

Any help would be appreciated.

Parents Reply Children
  • That worked, thank you for the assist.

    I'm not sure what was going on with the SSH, I was just using the command line interface on the Pi. I was using "ssh 192.168.2.1" and that still isn't working, but if I add the 'root' user name "ssh root@192.168.2.1" it worked.

    I'm not very adept with this sort of stuff, but I don't really see why that would change anything. 

  • In your original inquiry - were you able to log into the pluto at all? Depending on the SSH client, you may or may not get a prompt for a username. I just tried logging in with PuTTY from Windows, no username given, and I get a prompt for username. I can enter "root" and proceed. However if I run ssh 192.168.2.1 from PowerShell, it attempts to log into the Pluto with my current Windows username and fails. Adding root@ overrides this, and it works fine.

    Anyway sounds like you're up and running.

    -Mark

  • Before updating the firmware, yes I was able to log in. I never received a prompt for a username. After the firmware update, I think what you said is happening and it is trying to use the computer's login username, or something else. Adding the root@ worked.

    I'm not sure what I did to make it switch and use something other than 'root' as the username though.