On 08-06-2021 16:17, Michael Dickens wrote:
Hi Martin - Can you try manually applying this commit on your E310 SG1?
Thanks, this did the trick.
After a reboot the mpm is recognozed and uhd_find_devices and
uhd_usrp_probe seem to work.
Is this something that can/should be applied to the maintenance branch
of 3.15 in the git repository or does it have side effects for newer
usrps that have zero terminated strings?
Or alternatively, could/should the contents of the eeprom of my and
other older E310's be changed to have zero-terminated strings.
The patch did not apply cleanly. So I had to do some edits manually.
I created a new patch that should apply cleanly to the installed file on
the E310 filesystem with UHD_3.15.0.0-0-gaea0e2d
/usr/lib/python3.5/site-packages/usrp_mpm/e31x_legacy_eeprom.py
Best regards,
Martin
mpm_e31x_accept_FF_terminated_strings_in_eeprom__updated_patch_for_UHD_3.15.0.0-0-gaea0e2d.patch
Based on original patch be53058a47c6b2925103d44595f06fd6fb85e4be
From: Steven Koo <[email protected]>
Date: Thu, 3 Sep 2020 17:18:56 -0500
Subject: [PATCH] mpm: e31x: Accept FF terminated strings in eeprom
Older revisions of the e31x used FF terminated strings in the EEPROM.
The eeprom implementation didn't take this into account and would
fail on ascii conversion. This change resolves mpm bring up on the
older revisions by replacing FF with null. This didn't affect newer
revisions because they used null terminated strings.
Signed-off-by: Steven Koo <[email protected]>
Modified to apply cleanly on current usrp E310 sg1 filesystem image with
UHD_3.15.0.0-0-gaea0e2
by Martin Dudok van Heel <[email protected]>
--- a/usr/lib/python3.5/site-packages/usrp_mpm/e31x_legacy_eeprom.py
2020-01-01 07:01:29.000000000 +0000
+++ b/usr/lib/python3.5/site-packages/usrp_mpm/e31x_legacy_eeprom.py
2021-06-08 14:38:44.181516993 +0000
@@ -25,7 +25,7 @@
- 6 bytes MAC address
- 2 bytes hw_pid
- 2 bytes hw_rev
- - 8 bytes serial number (zero-terminated string of 7 characters)
+ - 8 bytes serial number (xFF or NULL terminated)
- 12 bytes padding
- 8 bytes user_name
@@ -35,7 +35,7 @@
"""
# Refer e300_eeprom_manager.hpp.
- eeprom_header_format = "<H H 6s H H 7s 12s 8s"
+ eeprom_header_format = "<H H 6s H H 8s 12s 8s"
eeprom_header_keys = ('data_version_major', 'data_version_minor',
'mac_address', 'pid', 'rev', 'serial', 'pad', 'user_name')
class DboardEEPROM(object):
@@ -49,12 +49,12 @@
- 2 bytes data_version_minor
- 2 bytes hw_pid
- 2 bytes hw_rev
- - 8 bytes serial number (zero-terminated string of 7 characters)
+ - 8 bytes serial number (xFF or NULL terminated)
- 12 bytes padding
"""
# Refer e300_eeprom_manager.hpp.
- eeprom_header_format = "<H H H H 7s 12s"
+ eeprom_header_format = "<H H H H 8s 12s"
eeprom_header_keys = ('data_version_major', 'data_version_minor',
'pid', 'rev', 'serial', 'pad')
def read_eeprom(
@@ -89,6 +89,10 @@
parsed_data_list = list(parsed_data)
parsed_data_list[3] = struct.unpack("<H", struct.pack(">H",
parsed_data_list[3]))[0]
parsed_data_list[4] = struct.unpack("<H", struct.pack(">H",
parsed_data_list[4]))[0]
+ # Some revisions use xFF terminated strings for serial and
user_name.
+ # Replace xFF with NULL to pass ascii conversion.
+ parsed_data_list[5] = parsed_data_list[5].replace(b'\xff',b'\x00')
+ parsed_data_list[7] = parsed_data_list[7].replace(b'\xff',b'\x00')
parsed_data = tuple(parsed_data_list)
else: # E310 DB.
@@ -97,7 +101,10 @@
parsed_data_list = list(parsed_data)
parsed_data_list[2] = struct.unpack("<H", struct.pack(">H",
parsed_data_list[2]))[0]
parsed_data_list[3] = struct.unpack("<H", struct.pack(">H",
parsed_data_list[3]))[0]
+ # Some revisions use xFF terminated strings for serial.
+ # Replace xFF with NULL to pass ascii conversion.
+ parsed_data_list[4] = parsed_data_list[4].replace(b'\xff',b'\x00')
parsed_data = tuple(parsed_data_list)
ret_val = (dict(list(zip(eeprom_keys, parsed_data))),data)
- return ret_val
\ No newline at end of file
+ return ret_val
I'll note that without it I can boot mine into UHD 3.15.0.0 release (or
LTS), but "find" fails & then nothing else works. At boot the USRP
hardware daemon doesn't start, because it can't detect the product info
(as shown by "systemctl status usrp-hwd"). This commit should fix the
issue. Once applied, you'll either want to reboot the USRP, or stop and
start the USRP HWD ("systemctl stop usrp-hwd" then "systemctl start
usrp-hwd"). Fingers crossed this works! - MLD
https://github.com/EttusResearch/uhd/commit/be53058a47c6b2925103d44595f06fd6fb85e4be
<https://github.com/EttusResearch/uhd/commit/be53058a47c6b2925103d44595f06fd6fb85e4be>
On Tue, Jun 8, 2021 at 9:03 AM Marcus D Leech <[email protected]
<mailto:[email protected]>> wrote:
None of us have been able to reproduce this
I have an SG1 device and can’t make this happen, but a later
hardware rev.
Sent from my iPhone
> On Jun 8, 2021, at 8:25 AM, Martin
<[email protected]
<mailto:[email protected]>> wrote:
>
> On 22-05-2021 15:18, Marcus D Leech wrote:
>> Martin:
>> I’m
>> I’m in discussions with Ettus R&D who are trying to reproduce.
> Any news on this?
>
> A working uhd 3.15 image on E310 sg1 would really be appreciated.
>
> Is there anything that I can do or test?
>
> My E310 has partno: 156333B-01L
> The exact hardware revision (B in my case) could be a clue.
>
> Thanks,
> Martin
>
>
>> I was unable with mine.
>> Sent from my iPhone
>>>> On May 20, 2021, at 1:23 PM, Marcus D Leech
<[email protected] <mailto:[email protected]>> wrote:
>>>
>>> FYI I see the same memory leak and PMU warnings on my SG1
hardware u der 3.15. So I assume that this is a side effect of the
move to MPM for E310 hardware.
>>>
>>>
>>>
>>> Sent from my iPhone
>>>
>>>> On May 20, 2021, at 12:05 PM, Martin
<[email protected]
<mailto:[email protected]>> wrote:
>>>>
>>>> I tried again with the UHD 4.0.0.0 sdimg
>>>> I get a lot of warnings, but with the uhd 4.0.0.0 sdimg the
uhd hardware is recognized.
>>>>
>>>> I ado see this error with uhd 4.0.0.0 <http://4.0.0.0>:
>>>> [ 50.716349] e31x-pmu: probe of fpga-full:pmu failed with
error -524
>>>> I'm not sure what this means.
>>>>
>>>> If needed, we could work with the uhd 4.0.0 sdimg, but we
would really like to be able to also keep using our uhd 3.15
development tree. Moving to uhd 4.0.0.0 would mean installing both
uhd 3.15 and uhd 4.0.0.0 trees on some of our deployment
host-machines. Which seems error-prone.
>>>>
>>>> Alchemy 2020.01 ni-e31x-F661C4 ttyPS0
>>>>
>>>> ni-e31x-F661C4 login: root
>>>> root@ni-e31x-F661C4:~# uhd_find_devices
>>>> [INFO] [UHD] linux; GNU C++ version 9.2.0; Boost_107100;
UHD_4.0.0.0-0-g90ce6062
>>>> No UHD Devices Found
>>>> root@ni-e31x-F661C4:~# [ 49.925787] fpga_manager fpga0:
writing e310_sg1_idle.bin to Xilinx Zynq FPGA Manager
>>>> [ 50.121918] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /fpga-full/firmware-name
>>>> [ 50.146427] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/devctrl
>>>> [ 50.156208] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/charger
>>>> [ 50.186332] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/battery
>>>> [ 50.716349] e31x-pmu: probe of fpga-full:pmu failed with
error -524
>>>>
>>>> root@ni-e31x-F661C4:~/logs# uhd_usrp_probe
>>>> [INFO] [UHD] linux; GNU C++ version 9.2.0; Boost_107100;
UHD_4.0.0.0-0-g90ce6062
>>>> [INFO] [MPMD] Initializing 1 device(s) in parallel with args:
mgmt_addr=127.0.0.1,type=e3xx,product=e310_sg1,serial=F661C4,claimed=
>>>> False
>>>> [ 649.706380] fpga_manager fpga0: writing e310_sg1.bin to
Xilinx Zynq FPGA Manager
>>>> [ 649.782720] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /fpga-full/firmware-name
>>>> [ 649.792926] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /amba/spi@e0006000/status
>>>> [ 649.803194] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /amba/spi@e0006000/cs-gpios
>>>> [ 649.813823] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/spidev0
>>>> [ 649.823667] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/devctrl
>>>> [ 649.833505] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/charger
>>>> [ 649.843335] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/battery
>>>> [ 649.853172] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/nixge_internal
>>>> [ 650.384737] e31x-pmu: probe of fpga-full:pmu failed with
error -524
>>>> [ 650.406779] nixge 40020000.ethernet int0: renamed from eth1
>>>> [ 650.584811] nixge 40020000.ethernet int0: Link is Up -
10Mbps/Half - flow control off
>>>> [INFO] [MPM.PeriphManager] Found 1 daughterboard(s).
>>>> [INFO] [MPM.PeriphManager] init() called with device args
`mgmt_addr=127.0.0.1,product=e310_sg1'.
>>>> [INFO] [0/Radio#0] Performing CODEC loopback test on channel 0 ...
>>>> [INFO] [0/Radio#0] CODEC loopback test passed
>>>> [INFO] [0/Radio#0] Performing CODEC loopback test on channel 1 ...
>>>> [INFO] [0/Radio#0] CODEC loopback test passed
>>>> _____________________________________________________
>>>> /
>>>> | Device: E300-Series Device
>>>> | _____________________________________________________
>>>> | /
>>>> | | Mboard: ni-e31x-F661C4
>>>> | | dboard_0_pid: 272
>>>> | | dboard_0_serial: F65275
>>>> | | fs_version: 20200914001743
>>>> | | mender_artifact: v4.0.0.0_e310_sg1
>>>> | | mpm_sw_version: 4.0.0.0-g90ce6062
>>>> | | pid: 30674
>>>> | | product: e310_sg1
>>>> | | rev: 0
>>>> | | rpc_connection: local
>>>> | | serial: F661C4
>>>> | | type: e3xx
>>>> | | MPM Version: 3.0
>>>> | | FPGA Version: 6.0
>>>> | | FPGA git hash: be53058.clean
>>>> | |
>>>> | | Time sources: internal, external, gpsdo
>>>> | | Clock sources: internal
>>>> | | Sensors: ref_locked, gps_locked, temp_fpga, temp_mb,
gps_gpgga, gps_sky, gps_time, gps_tpv
>>>> | /
>>>> | | RFNoC blocks on this device:
>>>> | |
>>>> | | * 0/Radio#0
>>>> | _____________________________________________________
>>>> | /
>>>> | | Static connections on this device:
>>>> | |
>>>> | | * 0/SEP#0:0==>0/Radio#0:0
>>>> | | * 0/SEP#1:0==>0/Radio#0:1
>>>> | | * 0/Radio#0:0==>0/SEP#0:0
>>>> | | * 0/Radio#0:1==>0/SEP#1:0
>>>> | _____________________________________________________
>>>> | /
>>>> | | TX Dboard: dboard
>>>> | | _____________________________________________________
>>>> | | /
>>>> | | | TX Frontend: 0
>>>> | | | Name: E3xx
>>>> | | | Antennas: TX/RX
>>>> | | | Freq range: 47.000 to 6000.000 MHz
>>>> | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB
>>>> | | | Bandwidth range: 20000000.0 to 40000000.0 step 0.0 Hz
>>>> | | | Connection Type: IQ
>>>> | | | Uses LO offset: No
>>>> | | _____________________________________________________
>>>> | | /
>>>> | | | TX Frontend: 1
>>>> | | | Name: E3xx
>>>> | | | Antennas: TX/RX
>>>> | | | Freq range: 47.000 to 6000.000 MHz
>>>> | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB
>>>> | | | Bandwidth range: 20000000.0 to 40000000.0 step 0.0 Hz
>>>> | | | Connection Type: IQ
>>>> | | | Uses LO offset: No
>>>> | _____________________________________________________
>>>> | /
>>>> | | RX Dboard: dboard
>>>> | | _____________________________________________________
>>>> | | /
>>>> | | | RX Frontend: 0
>>>> | | | Name: E3xx
>>>> | | | Antennas: RX2, TX/RX
>>>> | | | Freq range: 70.000 to 6000.000 MHz
>>>> | | | Gain range PGA: 0.0 to 76.0 step 1.0 dB
>>>> | | | Bandwidth range: 20000000.0 to 40000000.0 step 0.0 Hz
>>>> | | | Connection Type: IQ
>>>> | | | Uses LO offset: No
>>>> | _____________________________________________________
>>>> | | /
>>>> | | | RX Frontend: 1
>>>> | | | Name: E3xx
>>>> | | | Antennas: RX2, TX/RX
>>>> | | | Freq range: 70.000 to 6000.000 MHz
>>>> | | | Gain range PGA: 0.0 to 76.0 step 1.0 dB
>>>> | | | Bandwidth range: 20000000.0 to 40000000.0 step 0.0 Hz
>>>> | | | Connection Type: IQ
>>>> | | | Uses LO offset: No
>>>>
>>>> [ 658.474906] nixge 40020000.ethernet int0: Link is Down
>>>> [ 658.590581] fpga_manager fpga0: writing e310_sg1_idle.bin
to Xilinx Zynq FPGA Manager
>>>> [ 658.671152] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /fpga-full/firmware-name
>>>> [ 658.681463] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/devctrl
>>>> [ 658.691315] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/charger
>>>> [ 658.701150] OF: overlay: WARNING: memory leak will occur if
overlay removed, property: /__symbols__/battery
>>>> [ 659.219759] e31x-pmu: probe of fpga-full:pmu failed with
error -524
>>>>
>>>>
>>>>
>>>>>> On 20-05-2021 17:31, Martin wrote:
>>>>> I have still no idea why my E310 sg1 does not recognize its
own uhd hardware with uhd_find_devices.
>>>>> Can the exact hardware variant be of influence.
>>>>> Mine has partno: 156333B-01L
>>>>> The B in the partnumber seems to indicate the precise
hardware revision.
>>>>> The manual says:
>>>>>> The Release 4 image comes in two varieties. The variety that
you will need depends on the product number of your E310 or E312,
which is printed on the bottom of the device.
>>>>>> E310 (15633X-01L) X= A, B, C, D Ettus-e3xx-sg1
>>>>>> X= E or later Ettus-e3xx-sg3
>>>>>> E312 (140605X-01L) X = All Ettus-e3xx-sg3
>>>>> So I have a really early edition.
>>>>> Mine gives this:
>>>>>>>>> root@ni-e31x:~# uhd_find_devices
>>>>>>>>> [INFO] [UHD] linux; GNU C++ version 8.2.0; Boost_106800;
>>>>>>>>> UHD_3.15.0.0-0-gaea0e2de
>>>>>>>>> --------------------------------------------------
>>>>>>>>> -- UHD Device 0
>>>>>>>>> --------------------------------------------------
>>>>>>>>> Device Address:
>>>>>>>>> serial:
>>>>>>>>> claimed: False
>>>>>>>>> mgmt_addr: 127.0.0.1
>>>>>>>>> product:
>>>>>>>>> reachable: No
>>>>>>>>> type:
>>>>> Best regards,
>>>>> Martin
>>>>>> On 18-05-2021 14:33, Marcus D. Leech wrote:
>>>>>> On 05/18/2021 05:06 AM, Martin wrote:
>>>>>>> What does uhd_find_devices show on your system?
>>>>>>>
>>>>>>> Martin
>>>>>>>
>>>>>> Device Address:
>>>>>> serial: 30B0152
>>>>>> claimed: False
>>>>>> mgmt_addr: 127.0.0.1
>>>>>> product: e310_sg1
>>>>>> type: e3xx
>>>>>>>
>>>>>>> On 17-05-2021 23:09, Marcus D. Leech wrote:
>>>>>>>> On 05/17/2021 05:03 PM, Martin wrote:
>>>>>>>>> On 17-05-2021 00:10, Marcus D Leech wrote:
>>>>>>>>>> I’m currently trying to reproduce but on an sg3 system.
Having entirely different problems.
>>>>>>>>> Thank you for looking into this.
>>>>>>>>> I am looking forward to your findings.
>>>>>>>>> What issues do you have with sg3?
>>>>>>>>> Maybe I can help you with that ;-)
>>>>>>>> I mis-spoke as it turns out...
>>>>>>>>
>>>>>>>> My device is an SG1, and running uhd_usrp_probe produces:
>>>>>>>>
>>>>>>>> [INFO] [UHD] linux; GNU C++ version 8.2.0; Boost_106800;
UHD_3.15.0.0-0-gaea0e2e
>>>>>>>> [INFO] [MPMD] Initializing 1 device(s) in parallel with
args: mgmt_addr=127.0.0e
>>>>>>>> [ 63.396911] fpga_manager fpga0: writing e310_sg1.bin to
Xilinx Zynq FPGA Manr
>>>>>>>> [ 63.597426] OF: overlay: WARNING: memory leak will
occur if overlay removed,e
>>>>>>>> [ 63.607629] OF: overlay: WARNING: memory leak will
occur if overlay removed,s
>>>>>>>> [ 63.617856] OF: overlay: WARNING: memory leak will
occur if overlay removed,s
>>>>>>>> [ 63.629066] OF: overlay: WARNING: memory leak will
occur if overlay removed,0
>>>>>>>> [ 63.638894] OF: overlay: WARNING: memory leak will
occur if overlay removed,l
>>>>>>>> [ 63.648644] OF: overlay: WARNING: memory leak will
occur if overlay removed,r
>>>>>>>> [ 63.658443] OF: overlay: WARNING: memory leak will
occur if overlay removed,y
>>>>>>>> [ 63.668206] OF: overlay: WARNING: memory leak will
occur if overlay removed,0
>>>>>>>> [ 63.678010] OF: overlay: WARNING: memory leak will
occur if overlay removed,1
>>>>>>>> [ 63.687768] OF: overlay: WARNING: memory leak will
occur if overlay removed,2
>>>>>>>> [ 63.697568] OF: overlay: WARNING: memory leak will
occur if overlay removed,3
>>>>>>>> [ 63.707324] OF: overlay: WARNING: memory leak will
occur if overlay removed,0
>>>>>>>> [ 63.717127] OF: overlay: WARNING: memory leak will
occur if overlay removed,1
>>>>>>>> [ 63.726899] OF: overlay: WARNING: memory leak will
occur if overlay removed,2
>>>>>>>> [ 63.736704] OF: overlay: WARNING: memory leak will
occur if overlay removed,3
>>>>>>>> [ 63.746463] OF: overlay: WARNING: memory leak will
occur if overlay removed,0
>>>>>>>> [ 63.756698] OF: overlay: WARNING: memory leak will
occur if overlay removed,1
>>>>>>>> [ 63.766927] OF: overlay: WARNING: memory leak will
occur if overlay removed,2
>>>>>>>> [ 63.777182] OF: overlay: WARNING: memory leak will
occur if overlay removed,3
>>>>>>>> [ 63.787416] OF: overlay: WARNING: memory leak will
occur if overlay removed,0
>>>>>>>> [ 63.797648] OF: overlay: WARNING: memory leak will
occur if overlay removed,1
>>>>>>>> [ 63.807881] OF: overlay: WARNING: memory leak will
occur if overlay removed,2
>>>>>>>> [ 63.818115] OF: overlay: WARNING: memory leak will
occur if overlay removed,3
>>>>>>>> [ 63.828350] OF: overlay: WARNING: memory leak will
occur if overlay removed,0
>>>>>>>> [ 63.895829] rfnoc_crossbar crossbar0: NI Platform RFNoC
Crossbar registered
>>>>>>>> [ 64.419972] e31x-pmu: probe of fpga-full:pmu failed
with error -524
>>>>>>>> [ 64.485031] usrp-dma-core: Registered rx-dma0
>>>>>>>> [ 64.515301] usrp-dma-core: Registered rx-dma1
>>>>>>>> [ 64.531891] usrp-dma-core: Registered rx-dma2
>>>>>>>> [ 64.545275] usrp-dma-core: Registered rx-dma3
>>>>>>>> [ 64.560157] usrp-dma-core: Registered tx-dma0
>>>>>>>> [ 64.571785] usrp-dma-core: Registered tx-dma1
>>>>>>>> [ 64.585115] usrp-dma-core: Registered tx-dma2
>>>>>>>> [ 64.595584] usrp-dma-core: Registered tx-dma3
>>>>>>>> [INFO] [MPM.main] Launching USRP/MPM, version:
3.15.0.0-gaea0e2de
>>>>>>>> [INFO] [MPM.main] Spawning RPC process...
>>>>>>>> [WARNING] [MPM.PeriphManager] Skipping HW/SW compatibility
check!
>>>>>>>> [INFO] [MPM.PeriphManager] Device serial number: 30B0152
>>>>>>>> [WARNING] [MPM.GPSDIface] Could not connect to GPSd! None
of the GPS sensors wi!
>>>>>>>> [INFO] [MPM.RPCServer] RPC server ready!
>>>>>>>> [INFO] [MPM.RPCServer] Spawning watchdog task...
>>>>>>>> [INFO] [MPM.PeriphManager] Found 1 daughterboard(s).
>>>>>>>> [INFO] [0/Radio_0] Initializing block control (NOC ID:
0x12AD100000003310)
>>>>>>>> [INFO] [MPM.PeriphManager] init() called with device args
`product=e310_sg1,mgm.
>>>>>>>> [INFO] [0/DDC_0] Initializing block control (NOC ID:
0xDDC0000000000000)
>>>>>>>> [INFO] [0/DUC_0] Initializing block control (NOC ID:
0xD0C0000000000002)
>>>>>>>> [INFO] [0/Radio_0] Performing CODEC loopback test...
>>>>>>>> [INFO] [0/Radio_0] CODEC loopback test passed
>>>>>>>> [INFO] [0/Radio_0] Performing CODEC loopback test...
>>>>>>>> [INFO] [0/Radio_0] CODEC loopback test passed
>>>>>>>> _____________________________________________________
>>>>>>>> /
>>>>>>>> | Device: E300-Series Device
>>>>>>>> | _____________________________________________________
>>>>>>>> | /
>>>>>>>> | | Mboard: ni-e31x
>>>>>>>> | | mpm_version: 3.15.0.0-gaea0e2de
>>>>>>>> | | pid: 30674
>>>>>>>> | | product: e310_sg1
>>>>>>>> | | rev: 4
>>>>>>>> | | rpc_connection: local
>>>>>>>> | | serial: 30B0152
>>>>>>>> | | type: e3xx
>>>>>>>> | | MPM Version: 1.2
>>>>>>>> | | FPGA Version: 1.0
>>>>>>>> | | FPGA git hash: fde2a94.clean
>>>>>>>> | | RFNoC capable: Yes
>>>>>>>> | |
>>>>>>>> | | Time sources: internal, external, gpsdo
>>>>>>>> | | Clock sources: internal
>>>>>>>> | | Sensors: ref_locked, temp_fpga, temp_mb, gps_locked
>>>>>>>> | | _____________________________________________________
>>>>>>>> | | /
>>>>>>>> | | | RX Dboard: A
>>>>>>>> | | |
_____________________________________________________
>>>>>>>> | | | /
>>>>>>>> | | | | RX Frontend: 0
>>>>>>>> | | | | Name: E3xx
>>>>>>>> | | | | Antennas: RX2, TX/RX
>>>>>>>> | | | | Sensors: lo_locked, rssi, lo_lock,
ad9361_temperature
>>>>>>>> | | | | Freq range: 70.000 to 6000.000 MHz
>>>>>>>> | | | | Gain range PGA: 0.0 to 76.0 step 1.0 dB
>>>>>>>> | | | | Bandwidth range: 20000000.0 to 40000000.0
step 0.0 Hz
>>>>>>>> | | | | Connection Type: IQ
>>>>>>>> | | | | Uses LO offset: No
>>>>>>>> | | |
_____________________________________________________
>>>>>>>> | | | /
>>>>>>>> | | | | RX Frontend: 1
>>>>>>>> | | | | Name: E3xx
>>>>>>>> | | | | Antennas: RX2, TX/RX
>>>>>>>> | | | | Sensors: lo_locked, rssi, lo_lock,
ad9361_temperature
>>>>>>>> | | | | Freq range: 70.000 to 6000.000 MHz
>>>>>>>> | | | | Gain range PGA: 0.0 to 76.0 step 1.0 dB
>>>>>>>> | | | | Bandwidth range: 20000000.0 to 40000000.0
step 0.0 Hz
>>>>>>>> | | | | Connection Type: IQ
>>>>>>>> | | | | Uses LO offset: No
>>>>>>>> | | |
_____________________________________________________
>>>>>>>> | | | /
>>>>>>>> | | | | RX Codec: A
>>>>>>>> | | | | Name: AD9361 Dual ADC
>>>>>>>> | | | | Gain Elements: None
>>>>>>>> | | _____________________________________________________
>>>>>>>> | | /
>>>>>>>> | | | TX Dboard: A
>>>>>>>> | | |
_____________________________________________________
>>>>>>>> | | | /
>>>>>>>> | | | | TX Frontend: 0
>>>>>>>> | | | | Name: E3xx
>>>>>>>> | | | | Antennas: TX/RX
>>>>>>>> | | | | Sensors: lo_locked, ad9361_temperature
>>>>>>>> | | | | Freq range: 47.000 to 6000.000 MHz
>>>>>>>> | | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB
>>>>>>>> | | | | Bandwidth range: 20000000.0 to 40000000.0
step 0.0 Hz
>>>>>>>> | | | | Connection Type: IQ
>>>>>>>> | | | | Uses LO offset: No
>>>>>>>> | | |
_____________________________________________________
>>>>>>>> | | | /
>>>>>>>> | | | | TX Frontend: 1
>>>>>>>> | | | | Name: E3xx
>>>>>>>> | | | | Antennas: TX/RX
>>>>>>>> | | | | Sensors: lo_locked, ad9361_temperature
>>>>>>>> | | | | Freq range: 47.000 to 6000.000 MHz
>>>>>>>> | | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB
>>>>>>>> | | | | Bandwidth range: 20000000.0 to 40000000.0
step 0.0 Hz
>>>>>>>> | | | | Connection Type: IQ
>>>>>>>> | | | | Uses LO offset: No
>>>>>>>> | | |
_____________________________________________________
>>>>>>>> | | | /
>>>>>>>> | | | | TX Codec: A
>>>>>>>> | | | | Name: AD9361 Dual DAC
>>>>>>>> | | | | Gain Elements: None
>>>>>>>> | | _____________________________________________________
>>>>>>>> | | /
>>>>>>>> | | | RFNoC blocks on this device:
>>>>>>>> | | |
>>>>>>>> | | | * Radio_0
>>>>>>>> | | | * DDC_0
>>>>>>>> | | | * DUC_0
>>>>>>>>
>>>>>>>> [ 72.280024] usrp-dma-core: Deregistered tx-dma3
>>>>>>>> [ 72.293917] usrp-dma-core: Deregistered tx-dma2
>>>>>>>> [ 72.304477] usrp-dma-core: Deregistered tx-dma1
>>>>>>>> [ 72.316396] usrp-dma-core: Deregistered tx-dma0
>>>>>>>> [ 72.327630] usrp-dma-core: Deregistered rx-dma3
>>>>>>>> [ 72.339059] usrp-dma-core: Deregistered rx-dma2
>>>>>>>> [ 72.350350] usrp-dma-core: Deregistered rx-dma1
>>>>>>>> [ 72.360698] usrp-dma-core: Deregistered rx-dma0
>>>>>>>> [ 72.401639] fpga_manager fpga0: writing
e310_sg1_idle.bin to Xilinx Zynq FPGr
>>>>>>>> [ 72.501239] OF: overlay: WARNING: memory leak will
occur if overlay removed,e
>>>>>>>> [ 72.511488] OF: overlay: WARNING: memory leak will
occur if overlay removed,l
>>>>>>>> [ 72.521660] OF: overlay: WARNING: memory leak will
occur if overlay removed,r
>>>>>>>> [ 72.531642] OF: overlay: WARNING: memory leak will
occur if overlay removed,y
>>>>>>>> [ 73.064935] e31x-pmu: probe of fpga-full:pmu failed
with error -524
>>>>>>>> root@ni-e31x:~#
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> I will also tryout the latest uhd 4.0 sdimg for E310 sg1
as soon as I have the time. Maybe that has different results.
>>>>>>>>>
>>>>>>>>> I was wondering if the output of uhd_find_devices gives a
clue.
>>>>>>>>> Is this the normal expected output whne you run
uhd_find_devices on the E310.
>>>>>>>>>
>>>>>>>>> root@ni-e31x:~# uhd_find_devices
>>>>>>>>> [INFO] [UHD] linux; GNU C++ version 8.2.0; Boost_106800;
UHD_3.15.0.0-0-gaea0e2de
>>>>>>>>> --------------------------------------------------
>>>>>>>>> -- UHD Device 0
>>>>>>>>> --------------------------------------------------
>>>>>>>>> Device Address:
>>>>>>>>> serial:
>>>>>>>>> claimed: False
>>>>>>>>> mgmt_addr: 127.0.0.1
>>>>>>>>> product:
>>>>>>>>> reachable: No
>>>>>>>>> type:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Best regards,
>>>>>>>>> Martin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Sent from my iPhone
>>>>>>>>>>
>>>>>>>>>>> On May 16, 2021, at 5:33 PM, Martin
<[email protected]
<mailto:[email protected]>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> On 15-05-2021 18:33, Marcus D. Leech wrote:
>>>>>>>>>>>>> On 05/15/2021 10:19 AM, Martin wrote:
>>>>>>>>>>>>> On 14-05-2021 21:26, Marcus D Leech wrote:
>>>>>>>>>>>>>> What happens if you don’t specify any args at all?
>>>>>>>>>>>>> Then I also get No Device found.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Martin
>>>>>>>>>>>> Martin:
>>>>>>>>>>>> Where did you get your sdimg from?
>>>>>>>>>>>
>>>>>>>>>>> On a host system with UHD 3.15 installed I did:
>>>>>>>>>>>
>>>>>>>>>>> sudo uhd_images_downloader -t sdimg -t e310 -t sg1
>>>>>>>>>>>
>>>>>>>>>>> [INFO] Images destination: /usr/share/uhd/images
>>>>>>>>>>> The file size for this target (832.3 MiB) exceeds the
download limit (100.0 MiB). Continue downloading? [y/N]y
>>>>>>>>>>> [INFO] Downloading
e3xx_e310_sg1_sdimg_default-v3.15.0.0.zip, total size: 872729.93 kB
>>>>>>>>>>> [INFO] Images download complete.
>>>>>>>>>>>
>>>>>>>>>>> This seems to download this file and extracts it:
>>>>>>>>>>>
https://files.ettus.com/binaries/cache/e3xx/meta-ettus-v3.15.0.0/e3xx_e310_sg1_sdimg_default-v3.15.0.0.zip
<https://files.ettus.com/binaries/cache/e3xx/meta-ettus-v3.15.0.0/e3xx_e310_sg1_sdimg_default-v3.15.0.0.zip>
>>>>>>>>>>>
>>>>>>>>>>> I wrote the extracted image to a 8 GB sdcard with dd.
>>>>>>>>>>>
>>>>>>>>>>> I also tried downloading the above file by hand and and
extracing it to the sdcard. That has the exact same result.
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> USRP-users mailing list -- [email protected]
<mailto:[email protected]>
>>>>> To unsubscribe send an email to
[email protected]
<mailto:[email protected]>
>>>> _______________________________________________
>>>> USRP-users mailing list -- [email protected]
<mailto:[email protected]>
>>>> To unsubscribe send an email to
[email protected]
<mailto:[email protected]>
>
_______________________________________________
USRP-users mailing list -- [email protected]
<mailto:[email protected]>
To unsubscribe send an email to [email protected]
<mailto:[email protected]>
_______________________________________________
USRP-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
