Cannot ping device when booted in sd mode. (But can in qspi)

MicroPhase / antsdr_uhd

This repo contains both the uhd host driver and firmware for microphase antsdr devices.

GNU General Public License v3.0

46 stars 30 forks source link

Cannot ping device when booted in sd mode. (But can in qspi) #67

Open algwabah opened 5 months ago

algwabah commented 5 months ago

I have installed firmware to device and installed host drivers. When I start and connect e200 in in QSPI mode I am able to find the device by pinging 192.168.1.10 . However, if i start e200 in sd-mode ping doesn't work, and I also am unable to find the device with uhd_find devices. Is this intended? Am I missing something?

Appreciate any help, thanks.

algwabah commented 5 months ago

Ok, so after reinstalling firmware to sd card it seems I can now ping the e200 in sd-mode as well. Still the problem of not finding the e200 with uhd_find_devices persists. What could this be due to?

lone-boy commented 4 months ago

Qspi starts pluto's firmware. If you have not modified anything on the SD boot card, it is UHD firmware. To switch to different firmware, you need to turn a white DIP switch. If the DIP switch has been turned to SD card startup, but If the device still cannot be started normally, then the UHD firmware in the SD card may be damaged. Please download the latest firmware under release.

algwabah commented 3 months ago

I believed I had solved this but I now have a new form of this issue. On one device I can connect fully and run the AntSDR without issues, but on another pc, using the exact same settings I have the following issue:

When I connect AntSDR I can use ping 192.168.1.10
When I simply run (uhd_find_devices returns) it returns 'no uhd devices found'
If I run (uhd_find_devices --args="addr="192.168.1.10"") the AntSDR doe is found and shows up in terminal

How come I can find the device only when specifying which address to look at?