If you accidentally set the gpsdo EEPROM parameter to internal, apparently ZPU does not start the UDP services for RX/TX.
This makes all UHD-based services (including uhd_usrp_probe and the osmo-trx transceiver) fail with
Error: resolve: Service not found
What is problematic is that the current usrp_burn_mb_eeprom utilities will fail the same way, and prevents you from resetting the gspdo parameter to none. As a workaround I commented out the section under create gpsdo control objects in lib/usrp/umtrx/umtrx_impl.cpp and was able to re-set the value in the EEPROM.
It would be nice if the usrp_burn_mb_eeprom utility could be made to recover from this situation.
Alternatively, since based on ZPU's behavior, it seems UmTRX does not support gpsdo=internal, maybe preventing to set the parameter would be a simpler solution.
If you accidentally set the
gpsdoEEPROM parameter tointernal, apparently ZPU does not start the UDP services for RX/TX. This makes all UHD-based services (includinguhd_usrp_probeand theosmo-trxtransceiver) fail withWhat is problematic is that the current
usrp_burn_mb_eepromutilities will fail the same way, and prevents you from resetting thegspdoparameter tonone. As a workaround I commented out the section undercreate gpsdo control objectsinlib/usrp/umtrx/umtrx_impl.cppand was able to re-set the value in the EEPROM.It would be nice if the
usrp_burn_mb_eepromutility could be made to recover from this situation. Alternatively, since based on ZPU's behavior, it seems UmTRX does not supportgpsdo=internal, maybe preventing to set the parameter would be a simpler solution.