Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot recover from gpsdo=internal #3

Open
shimaore opened this issue Dec 29, 2013 · 0 comments
Open

cannot recover from gpsdo=internal #3

shimaore opened this issue Dec 29, 2013 · 0 comments

Comments

@shimaore
Copy link
Contributor

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.

shimaore added a commit to shimaore/UHD-Fairwaves that referenced this issue Jan 28, 2014
This changeset prevents libusrp from trying to access the `gpsdo` parameter (which is unused with UmTRX). This allows tools using libusrp from starting even if the gpsdo parameter was set incorrectly on the board.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant