usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsE320 not detecting any devices after power failure
Hello all,
I operate a USRP E320 using an externa battery. Usually I have time to shut it down in an orderly fashion before the battery is depleted.
On one occasion it happened that the battery was depleted before I had a chance to shut it down properly.
Since then when I run uhd_usrp_probe I get a message that no devices could be detected.
The E320 boots up normally and I can communicate with it using both serial console and LAN.
I initially suspected an SD card image corruption and I tried to rewrite the image using mender.
I tried the same version I am using (UHD 4.1.0.5) and I tried a newer version UHD 4.4.0.0 and and older version UHD 3.15.LTS.
Nothing seems to help. The E320 still reports "No devices found". I even tried uhd_usrp_probe with an argument of IP address. Nothing helps.
Here is a sample dump:
root@ni-e320:~# uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 9.2.0; Boost_107100; UHD_4.4.0.0-0-g5fac246b
[INFO] [MPMD FIND] Found MPM devices, but none are reachable for a UHD session. Specify find_all to find all devices.
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
Can someone help me fix this problem? Point me in the right direction?
Is it fixable by myself or do I have to return the unit to be serviced?
Thanks,
Ofer Saferman
On 29/07/2023 01:47, Ofer wrote:
Hello all,
I operate a USRP E320 using an externa battery. Usually I have time to
shut it down in an orderly fashion before the battery is depleted.
On one occasion it happened that the battery was depleted before I had
a chance to shut it down properly.
Since then when I run uhd_usrp_probe I get a message that no devices
could be detected.
The E320 boots up normally and I can communicate with it using both
serial console and LAN.
I initially suspected an SD card image corruption and I tried to
rewrite the image using mender.
I tried the same version I am using (UHD 4.1.0.5) and I tried a
newer version UHD 4.4.0.0 and and older version UHD 3.15.LTS.
Nothing seems to help. The E320 still reports "No devices found". I
even tried uhd_usrp_probe with an argument of IP address. Nothing helps.
Here is a sample dump:
root@ni-e320:~# uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 9.2.0; Boost_107100;
UHD_4.4.0.0-0-g5fac246b
[INFO] [MPMD FIND] Found MPM devices, but none are reachable for a UHD
session. Specify find_all to find all devices.
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
Can someone help me fix this problem? Point me in the right direction?
Is it fixable by myself or do I have to return the unit to be serviced?
Thanks,
Ofer Saferman
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-leave@lists.ettus.com
Are there any unusual messages during boot?
What about when you're on the device, is there anything in "dmesg" that
indicates a problem?
Hi Ofer, does the probe work if you specify the radio's IP address? e.g. something like:
uhd_usrp_probe --args addr=192.168.10.2
If that syntax works, then you might try switching between the SFP+ port (via copper adapter) and the native RJ45. My memory could be mistaken here, but I vaguely recall that MPM discovery for an E320 worked using one of those ports but not the other. However, if you specify the address, it would work with either port. Again, I'm working from fuzzy memory here..
Hope this helps,
David
From: Ofer ofer@navigicom.com
Sent: Saturday, July 29, 2023 1:47 AM
To: usrp-users@lists.ettus.com
Subject: [USRP-users] E320 not detecting any devices after power failure
Hello all,
I operate a USRP E320 using an externa battery. Usually I have time to shut it down in an orderly fashion before the battery is depleted.
On one occasion it happened that the battery was depleted before I had a chance to shut it down properly.
Since then when I run uhd_usrp_probe I get a message that no devices could be detected.
The E320 boots up normally and I can communicate with it using both serial console and LAN.
I initially suspected an SD card image corruption and I tried to rewrite the image using mender.
I tried the same version I am using (UHD 4.1.0.5) and I tried a newer version UHD 4.4.0.0 and and older version UHD 3.15.LTS.
Nothing seems to help. The E320 still reports "No devices found". I even tried uhd_usrp_probe with an argument of IP address. Nothing helps.
Here is a sample dump:
root@ni-e320:~# uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 9.2.0; Boost_107100; UHD_4.4.0.0-0-g5fac246b
[INFO] [MPMD FIND] Found MPM devices, but none are reachable for a UHD session. Specify find_all to find all devices.
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
Can someone help me fix this problem? Point me in the right direction?
Is it fixable by myself or do I have to return the unit to be serviced?
Thanks,
Ofer Saferman
Hello David and Rob,
Thank you for the suggestions.
I began my troubleshooting by pulling out the SD card and backing it up to a PC with an SD card reader using dd.
My initial thought was that the image was damaged because of the power failure.
I downloaded a fresh image using uhd_images_downloader and programmed it to the SD card using dd on the PC (UHD 4.1.0.5).
This image refused to boot. u-boot said it can't find the primary partition.
Looking at the image on the PC with various tools shows it is intact. It has the 4 partitions you would expect and the sizes seem to be OK.
I reprogrammed the SD card with my backup image and it booted normally but no devices detected.
I don't have an actual Linux system. I am working with WSL and Cygwin under Windows so I didn't have access to the other image writting method using bmaptool. It is not supported by Cygwin and WSL has no direct access to USB devices (my SD card reader) although it does has bmaptool.
Because of the failure to use dd with the original image provided by NI I switched to mender.
I tried to use a fresh mender image of the same UHD version I am using (4.1.0.5) and there was no change.
I tried using a mender image of a newer UHD version (4.4.0.0) and an older version (3.15.LTS) without any change.
No devices are detected.
To answer David's question: I did try with an IP address. I tried 127.0.0.1 and my assigned IP address 192.168.123.95. No change. No devices are detected.
BTW, after programming different images because I knew the IP address of the unit will change I switched to the USB serial console and did all my operations there. Still no change.
I am doing all operations on the actual E320 unit and not trying to use it remotely from PC although I initially did access it through SSH from a PC and it accessible this way because my original image uses a static IP address.
Could it be the EEPROM?
How to read the EEPROM?
What should be the correct values?
Where can I get the values to properly restore the EEPROM if indeed it is the one that was damaged?
What else could it be?
I don't think that a power failure can damage the hardware but how to diagnose it?
Regards,
Ofer Saferman
From: David Raeman david@SynopticEngineering.com
Sent: Saturday, July 29, 2023 5:51 PM
To: Ofer ofer@navigicom.com; usrp-users@lists.ettus.com usrp-users@lists.ettus.com
Subject: RE: E320 not detecting any devices after power failure
Hi Ofer, does the probe work if you specify the radio’s IP address? e.g. something like:
uhd_usrp_probe --args addr=192.168.10.2
If that syntax works, then you might try switching between the SFP+ port (via copper adapter) and the native RJ45. My memory could be mistaken here, but I vaguely recall that MPM discovery for an E320 worked using one of those ports but not the other. However, if you specify the address, it would work with either port. Again, I’m working from fuzzy memory here..
Hope this helps,
David
From: Ofer ofer@navigicom.com
Sent: Saturday, July 29, 2023 1:47 AM
To: usrp-users@lists.ettus.com
Subject: [USRP-users] E320 not detecting any devices after power failure
Hello all,
I operate a USRP E320 using an externa battery. Usually I have time to shut it down in an orderly fashion before the battery is depleted.
On one occasion it happened that the battery was depleted before I had a chance to shut it down properly.
Since then when I run uhd_usrp_probe I get a message that no devices could be detected.
The E320 boots up normally and I can communicate with it using both serial console and LAN.
I initially suspected an SD card image corruption and I tried to rewrite the image using mender.
I tried the same version I am using (UHD 4.1.0.5) and I tried a newer version UHD 4.4.0.0 and and older version UHD 3.15.LTS.
Nothing seems to help. The E320 still reports "No devices found". I even tried uhd_usrp_probe with an argument of IP address. Nothing helps.
Here is a sample dump:
root@ni-e320:~# uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 9.2.0; Boost_107100; UHD_4.4.0.0-0-g5fac246b
[INFO] [MPMD FIND] Found MPM devices, but none are reachable for a UHD session. Specify find_all to find all devices.
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
Can someone help me fix this problem? Point me in the right direction?
Is it fixable by myself or do I have to return the unit to be serviced?
Thanks,
Ofer Saferman
On 31/07/2023 00:30, Ofer wrote:
Hello David and Rob,
Thank you for the suggestions.
I began my troubleshooting by pulling out the SD card and backing it
up to a PC with an SD card reader using dd.
My initial thought was that the image was damaged because of the power
failure.
I downloaded a fresh image using uhd_images_downloader and programmed
it to the SD card using dd on the PC (UHD 4.1.0.5).
This image refused to boot. u-boot said it can't find the primary
partition.
Looking at the image on the PC with various tools shows it is intact.
It has the 4 partitions you would expect and the sizes seem to be OK.
I reprogrammed the SD card with my backup image and it booted normally
but no devices detected.
I don't have an actual Linux system. I am working with WSL and Cygwin
under Windows so I didn't have access to the other image writting
method using bmaptool. It is not supported by Cygwin and WSL has no
direct access to USB devices (my SD card reader) although it does has
bmaptool.
Because of the failure to use dd with the original image provided by
NI I switched to mender.
I tried to use a fresh mender image of the same UHD version I am using
(4.1.0.5) and there was no change.
I tried using a mender image of a newer UHD version (4.4.0.0) and an
older version (3.15.LTS) without any change.
No devices are detected.
To answer David's question: I did try with an IP address. I tried
127.0.0.1 and my assigned IP address 192.168.123.95. No change. No
devices are detected.
BTW, after programming different images because I knew the IP address
of the unit will change I switched to the USB serial console and did
all my operations there. Still no change.
I am doing all operations on the actual E320 unit and not trying to
use it remotely from PC although I initially did access it through SSH
from a PC and it accessible this way because my original image uses a
static IP address.
Could it be the EEPROM?
How to read the EEPROM?
What should be the correct values?
Where can I get the values to properly restore the EEPROM if indeed it
is the one that was damaged?
What else could it be?
I don't think that a power failure can damage the hardware but how to
diagnose it?
Regards,
Ofer Saferman
From: David Raeman david@SynopticEngineering.com
Sent: Saturday, July 29, 2023 5:51 PM
To: Ofer ofer@navigicom.com; usrp-users@lists.ettus.com
usrp-users@lists.ettus.com
Subject: RE: E320 not detecting any devices after power failure
Hi Ofer, does the probe work if you specify the radio’s IP address?
e.g. something like:
uhd_usrp_probe --args addr=192.168.10.2
If that syntax works, then you might try switching between the SFP+
port (via copper adapter) and the native RJ45. My memory could be
mistaken here, but I vaguely recall that MPM discovery for an E320
worked using one of those ports but not the other. However, if you
specify the address, it would work with either port. Again, I’m
working from fuzzy memory here..
Hope this helps,
David
From: Ofer ofer@navigicom.com
Sent: Saturday, July 29, 2023 1:47 AM
To: usrp-users@lists.ettus.com
Subject: [USRP-users] E320 not detecting any devices after power failure
Hello all,
I operate a USRP E320 using an externa battery. Usually I have time to
shut it down in an orderly fashion before the battery is depleted.
On one occasion it happened that the battery was depleted before I had
a chance to shut it down properly.
Since then when I run uhd_usrp_probe I get a message that no devices
could be detected.
The E320 boots up normally and I can communicate with it using both
serial console and LAN.
I initially suspected an SD card image corruption and I tried to
rewrite the image using mender.
I tried the same version I am using (UHD 4.1.0.5) and I tried a
newer version UHD 4.4.0.0 and and older version UHD 3.15.LTS.
Nothing seems to help. The E320 still reports "No devices found". I
even tried uhd_usrp_probe with an argument of IP address. Nothing helps.
Here is a sample dump:
root@ni-e320:~# uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 9.2.0; Boost_107100;
UHD_4.4.0.0-0-g5fac246b
[INFO] [MPMD FIND] Found MPM devices, but none are reachable for a UHD
session. Specify find_all to find all devices.
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address
Can someone help me fix this problem? Point me in the right direction?
Is it fixable by myself or do I have to return the unit to be serviced?
Thanks,
Ofer Saferman
USRP-users mailing list --usrp-users@lists.ettus.com
To unsubscribe send an email tousrp-users-leave@lists.ettus.com
If you use the serial console, during boot, does it issue any unusual
error messages? That can be a clue as to what's going
on. You might have to turn on recording on your terminal
application, because things scroll past fairly quickly.
Hi Marcus,
I am doing freq tuning in X310 USPR and find the description about sign may not be correct in the following page:
https://files.ettus.com/manual/structuhd_1_1tune__request__t.html
Note that the meaning of the DSP frequency's sign differs between TX and RX operations. The target frequency is the result of target_freq = rf_freq + sign * dsp_freq. For TX, sign is negative, and for RX, sign is positive. Example: If both RF and DSP tuning policies are set to manual, and rf_freq is set to 1 GHz, and dsp_freq is set to 10 MHz, the actual target frequency is 990 MHz for a TX tune request, and 1010 MHz for an RX tune request.
My results are as below (fs=200MHz):
Tx Tune Result:
Target RF Freq: 2080.000000 (MHz) Actual RF Freq: 2100.000000 (MHz) Target DSP Freq: -20.000000 (MHz) Actual DSP Freq: -20.000005 (MHz)Actual RF Freq + Actual DSP Freq = Target RF Freq
Rx Tune Result: Target RF Freq: 2120.000000 (MHz) Actual RF Freq: 2100.000000 (MHz) Target DSP Freq: -20.000000 (MHz) Actual DSP Freq: -20.000005 (MHz)Actual RF Freq - Actual DSP Freq = Target RF Freq
Kind regards,Hongwei