Hi @Muhammad,
I saw your post about the USRP X310 issue you're experiencing, and I wanted to share some insights that might help you diagnose and potentially resolve the problem after doing some thorough research.
Understanding Your Symptoms:
The combination of symptoms you're describing is quite concerning: * LED at SFP 0 not blinking (this is the most critical symptom) * No response to ping requests * findsdru not detecting the device * Setup verification getting stuck
The LED not blinking is particularly significant because this typically indicates the device isn't properly booting or the FPGA isn't loading correctly.
Recommended Troubleshooting Steps:
Step 1: Verify Network Configuration Based on MathWorks documentation, subnet mismatches are a common cause of "not responding" errors. Please verify: * Set your PC's Ethernet adapter to IP: 192.168.10.1, Subnet: 255.255.255.0 * Try pinging the factory default: 192.168.10.2 * Temporarily disable Windows Firewall to rule out blocking issues
Step 2: Check Basic Hardware Status When you power on the X310: * Which LEDs light up (if any)? * Does the power LED stay on? * Do you hear any fans or feel any warmth indicating the device is powered?
Step 3: Try Direct UHD Commands From Command Prompt or PowerShell, run:
uhd_find_devices uhd_usrp_probe --args="addr=192.168.10.2"
Step 4: Physical Connection Checks
- Try a different Ethernet cable (CAT5e or better)
- Try a different Ethernet port on your PC
- Check if your network adapter shows "cable connected" in Windows Device Manager
Step 5: Check for Windows Updates Since the device worked before and stopped after a month of non-use, Windows 11 might have received updates that reset your network adapter settings. Check: * Windows Update history * Network adapter driver updates * Power management settings on the Ethernet adapter (disable "Allow the computer to turn off this device")
Critical Concern - The LED Issue: The fact that the SFP 0 LED isn't blinking at all suggests one of these possibilities:
1. FPGA image corruption - The firmware may have become corrupted 2. SD card failure - If your X310 uses an SD card for boot storage, it may be corrupted or unseated 3. Hardware failure - Possible Ethernet PHY or mainboard issue 4. Power supply problem - Insufficient or unstable power delivery
Next Steps I Recommend: 1. Power Cycle Test: Completely unplug the X310 from power, wait 60 seconds, reconnect, and carefully observe ALL LEDs during boot 2. Check SD Card (if applicable): Some X310 models use SD cards - check if it's properly seated 3. Test with UHD Utilities: Try the uhd_image_loader command to reflash the FPGA if the device can be detected at all
If Nothing Works: If the LED still doesn't blink and the device remains undetected after trying all of the above, you may be facing:
- Corrupted firmware that requires JTAG recovery (specialized equipment needed)
- Hardware failure requiring RMA/repair
I'd recommend reaching out to Ettus Research/National Instruments support if these steps don't resolve it. The lack of LED activity strongly suggests a hardware or firmware corruption issue that may be beyond user-level troubleshooting.
Information That Would Help Further Diagnosis:
If you could share the following, I or others might be able to provide more specific guidance: * What LEDs (if any) are active when powered on? * Does Device Manager show the Ethernet connection as "connected"? * Your UHD version and Communications Toolbox Support Package version * Whether anything unusual happened before you stopped using it (power loss, abrupt shutdown, etc.)
I hope this helps! Please let us know what you discover with these troubleshooting steps.
