I'm encountering a critical issue while attempting to initialize an X410 USRP device. The device is detected correctly using uhd_find_devices, but fails to initialize with uhd_usrp_probe. Below is a summary of the setup and the error messages:

Environment:

• USRP Model: X410

• UHD Version: 4.7.0 (HEAD-0-ga5ed1872)

• MPM Version: 4.8.0.0-g308126a4

• OS: [Ubuntu 22.04]

• Device IP: 192.168.1.120

  uhd_find_devices output:

  serial: 322ED50
  addr: 192.168.1.120
  claimed: False
  fpga: n/a
  mgmt_addr: 192.168.1.120
  name: ni-x4xx-322ED50
  product: x410
  type: x4xx

  uhd_usrp_probe output:

  [ERROR] [MPM.PeriphManager] RFDC is not powered on
  [ERROR] [MPM.PeriphManager] Failed to initialize motherboard: RFDC is not powered on
  RuntimeError: RFDC is not powered on

  [ERROR] [MPM.RPCServer] Uncaught exception in method set_device_id: 'NoneType' object has no attribute 'set_device_id'
  [WARNING] [MPM.PeriphManager] Cannot run deinit(), device was never fully initialized!

  It seems the device is partially detected, but the RFDC does not power on and the RPC server fails with a 'NoneType' error when attempting to set the device ID.

  Could you please advise on possible causes or corrective actions to resolve this issue?

You write that your environment consists of an X410 running MPM at version 4.8 while your UHD is 4.7. While in general that may work, I’d encourage you to synchronize that. Nevertheless, this shouldn’t cause the described error.
Another issue I see is that in the output of uhd_find_devices it states “fpga: n/a”. However, this is probably the consequence of the “RFDC is not powered on” error. To exclude that: Is the device running a fresh firmware image?
And probably the most important point here: The X410 may only be used with both daughterboards installed, otherwise it must not turn on its RFDC. So it may be that your device does not recognize one or both daughterboards for whatever reason. One indicator for that may be that you cannot read back the daughterboard eeproms using the eeprom-dump db0 and eeprom-dump db1 commands. But all in all, I fear that RMA is the way to go forward.

/Martin

From: yokeshwaran.m@maxeyetech.com yokeshwaran.m@maxeyetech.com
Sent: Monday, June 2, 2025 9:24 PM
To: usrp-users@lists.ettus.com
Subject: [EXTERNAL] [USRP-users] X410 Initialization Failure - "RFDC is not powered on"

I'm encountering a critical issue while attempting to initialize an X410 USRP device. The device is detected correctly using uhd_find_devices, but fails to initialize with uhd_usrp_probe. Below is a summary of the setup and the error messages:

Environment:

• USRP Model: X410
• UHD Version: 4.7.0 (HEAD-0-ga5ed1872)
• MPM Version: 4.8.0.0-g308126a4
• OS: [Ubuntu 22.04]
• Device IP: 192.168.1.120

uhd_find_devices output:

serial: 322ED50 addr: 192.168.1.120 claimed: False fpga: n/a mgmt_addr: 192.168.1.120 name: ni-x4xx-322ED50 product: x410 type: x4xx uhd_usrp_probe output:

[ERROR] [MPM.PeriphManager] RFDC is not powered on [ERROR] [MPM.PeriphManager] Failed to initialize motherboard: RFDC is not powered on RuntimeError: RFDC is not powered on [ERROR] [MPM.RPCServer] Uncaught exception in method set_device_id: 'NoneType' object has no attribute 'set_device_id' [WARNING] [MPM.PeriphManager] Cannot run deinit(), device was never fully initialized! It seems the device is partially detected, but the RFDC does not power on and the RPC server fails with a 'NoneType' error when attempting to set the device ID. Could you please advise on possible causes or corrective actions to resolve this issue?