[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss-gnuradio] External clock & code best practice (#uhd #clock #n21
From: |
Guenael JOUCHET |
Subject: |
[Discuss-gnuradio] External clock & code best practice (#uhd #clock #n210) |
Date: |
Sat, 11 Jan 2014 21:38:02 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
Hello,
I use an external rubidium reference clock with my N210, everything
works fine with some patchs (python & c++ libs), but I failed with the
conventional way.
I found useful information on this page :
http://files.ettus.com/uhd_docs/manual/html/gpsdo.html
But this command below change nothing :/
sudo ./usrp_burn_mb_eeprom --args addr=192... --key=gpsdo --val=external
Clock led remains off and the signal sampled is not locked (using for
exemple uhd_rx_cfile, uhd_fft.mod or osmocom_fft)
I solved my problem by patching my python scripts and the osmocom
library, but I wanted to know if I missed something somewhere.
For information, the line added to uhd_rx_cfile : (after the antenna
selection code)
self._u.set_clock_config(uhd.clock_config.external(), 0)
And for osmocom lib : (uhd_source_c.cc, end of the constructor)
_src->set_clock_source("external", 0);
Version used :
FW image : 003.006.002-rc2
linux; GNU C++ version 4.8.1; Boost_105300; UHD_003.006.002-64-g92b0b7ab
Any feedback appreciated.
Good day, Guenael