07-15-2021 06:51 AM
As you suggested, I browse to this location:
C:\Program Files\National Instruments\LabVIEW 2020\vi.lib\LabVIEW Targets\FPGA\USRP
open the "niusrprio_tools.llb" in LV 2020 SP1 64bit, but could not find a vi called "initialize Examine Flash.vi" as you requested. But the vi that was highlight in your screenshot, "initialize Flash.vi" was there. I entered the VISA resource name, the device model, but did not know the serial numbers of the daughter boards, nor the hardware revision numbers: The vi runs without error:
I opened also the vi "Examine Flash.vi" and run it with strange results:
I doesn't really amuse me. But I hope this hints you toward the solution...
07-15-2021 07:11 AM
when I run the 2019 SP1 64 bit version, I get a green led but similar strange results:
07-16-2021 01:11 AM
Hi,
now it is clear the EEPROM is damaged.
you are trying to write the new image but it has the newest one i.e. the pointer is in the maximum value.
07-16-2021 07:13 AM
what should I do next?
I would like to highlight again the original problem which I think is not related to the firmware of the USRP:
We have two devices USRP 2945, one bought some years ago and one bought some month ago.
We use the devices in RIO mode, that means we have an own FPGA vi running on them.
With the older device we have the application running continously for months without problems. This is with LV 2019 64 bit (USRP 19.0). When I upgrade the USRP driver to 19.1 or newer I get the error message after about 30s that the acquire read regions cannot acquire more regions (see previous posts in this thread).
With the new device I cannot run the 19.0 version (too new hardware). With higher versions (19.1+) it shows the same error as the old device.
So we either need to fix this error with the acquire read regions or be able to downgrade the new device in order that it runs with the 19.0 driver.
I do not think this error has to do with the device but rather with the driver on the host. Could you please let me know that you understud my problem correctly and if your opinion is that this error is caused by the eeprom or firmware of the device?
In any case please let me know the strategy to pin down and solve the problem and let me know how to proceed.
PS.: I will send back the new device to NI for repair of the EEPROM. In the mean time we should make the old device to run on USRP 19.1 or higher. Please help.
08-10-2021 03:17 AM
Ok, on recommendation of NI over the phone, the device was sent to NI for repair. It came back with "no trouble found". Although it is stated that the firmware was reprogrammed.
Service request number: 3344042
Repair Order Number: 5344184
Part Number 156485G-21L
Serial Nr. 31FA23D
I run the tests that you recommended earlier:
C:\Program Files (x86)\National Instruments\NI-USRP\utilities>uhd_find_devices
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
serial: 31FA23D
fpga: HG
name:
product: X310
resource: RIO0
type: x300
C:\Program Files (x86)\National Instruments\NI-USRP\utilities>uhd_usrp_probe
_____________________________________________________
/
| Device: X-Series Device
| _____________________________________________________
| /
| | Mboard: X310
| | revision: 11
| | revision_compat: 7
| | product: 30959
| | mac-addr0: 00:80:2f:31:aa:1a
| | mac-addr1: 00:80:2f:31:aa:1b
| | gateway: 192.168.10.1
| | ip-addr0: 192.168.10.2
| | subnet0: 255.255.255.0
| | ip-addr1: 192.168.20.2
| | subnet1: 255.255.255.0
| | ip-addr2: 192.168.30.2
| | subnet2: 255.255.255.0
| | ip-addr3: 192.168.40.2
| | subnet3: 255.255.255.0
| | serial: 31FA23D
| | FW Version: 6.0
| | FPGA Version: 38.0
| | FPGA git hash: be53058
| |
| | Time sources: internal, external, gpsdo
| | Clock sources: internal, external, gpsdo
| | Sensors: ref_locked
| _____________________________________________________
| /
| | RFNoC blocks on this device:
| |
| | * 0/DDC#0
| | * 0/DDC#1
| | * 0/DUC#0
| | * 0/DUC#1
| | * 0/Radio#0
| | * 0/Radio#1
| | * 0/Replay#0
| _____________________________________________________
| /
| | Static connections on this device:
| |
| | * 0/SEP#0:0==>0/DUC#0:0
| | * 0/DUC#0:0==>0/Radio#0:0
| | * 0/Radio#0:0==>0/DDC#0:0
| | * 0/DDC#0:0==>0/SEP#0:0
| | * 0/Radio#0:1==>0/DDC#0:1
| | * 0/DDC#0:1==>0/SEP#1:0
| | * 0/SEP#2:0==>0/DUC#1:0
| | * 0/DUC#1:0==>0/Radio#1:0
| | * 0/Radio#1:0==>0/DDC#1:0
| | * 0/DDC#1:0==>0/SEP#2:0
| | * 0/Radio#1:1==>0/DDC#1:1
| | * 0/DDC#1:1==>0/SEP#3:0
| | * 0/SEP#4:0==>0/Replay#0:0
| | * 0/Replay#0:0==>0/SEP#4:0
| | * 0/SEP#5:0==>0/Replay#0:1
| | * 0/Replay#0:1==>0/SEP#5:0
| _____________________________________________________
| /
| | TX Dboard: dboard
| | ID: Unknown (0x0094)
| | Serial: 31DDBD8
| | _____________________________________________________
| | /
| | | TX Frontend: 0
| | | Name: Unknown (0x0094) - 0
| | | Antennas:
| | | Sensors:
| | | Freq range: 0.000 to 0.000 MHz
| | | Gain Elements: None
| | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz
| | | Connection Type: IQ
| | | Uses LO offset: No
| _____________________________________________________
| /
| | RX Dboard: dboard
| | ID: TwinRX Rev C (0x0095)
| | Serial: 31DDBD8
| | _____________________________________________________
| | /
| | | RX Frontend: 0
| | | Name: TwinRX RX0
| | | Antennas: RX1, RX2
| | | Sensors: lo_locked
| | | Freq range: 10.000 to 6000.000 MHz
| | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | Connection Type: II
| | | Uses LO offset: No
| | _____________________________________________________
| | /
| | | RX Frontend: 1
| | | Name: TwinRX RX1
| | | Antennas: RX1, RX2
| | | Sensors: lo_locked
| | | Freq range: 10.000 to 6000.000 MHz
| | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | Connection Type: QQ
| | | Uses LO offset: No
| _____________________________________________________
| /
| | TX Dboard: dboard
| | ID: Unknown (0x0094)
| | Serial: 31E086D
| | _____________________________________________________
| | /
| | | TX Frontend: 0
| | | Name: Unknown (0x0094) - 0
| | | Antennas:
| | | Sensors:
| | | Freq range: 0.000 to 0.000 MHz
| | | Gain Elements: None
| | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz
| | | Connection Type: IQ
| | | Uses LO offset: No
| _____________________________________________________
| /
| | RX Dboard: dboard
| | ID: TwinRX Rev C (0x0095)
| | Serial: 31E086D
| | _____________________________________________________
| | /
| | | RX Frontend: 0
| | | Name: TwinRX RX0
| | | Antennas: RX1, RX2
| | | Sensors: lo_locked
| | | Freq range: 10.000 to 6000.000 MHz
| | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | Connection Type: II
| | | Uses LO offset: No
| | _____________________________________________________
| | /
| | | RX Frontend: 1
| | | Name: TwinRX RX1
| | | Antennas: RX1, RX2
| | | Sensors: lo_locked
| | | Freq range: 10.000 to 6000.000 MHz
| | | Gain range all: 0.0 to 93.0 step 1.0 dB
| | | Bandwidth range: 80000000.0 to 80000000.0 step 0.0 Hz
| | | Connection Type: QQ
| | | Uses LO offset: No
Now I run the Examine Flash in LV 2020 64 Bit as reported in an earlier post in this thread:
But again it does not show resonable results. We are at the same point again.
Nevertheless, I try to update the update the Device with NI USRP Configuration Utility:
Please help!