On 09/01/2010 12:51 PM, Jason Abele wrote:
I'll need to do some re-soldering and burn-db-eeprom with USRP1 and hopefully
this
should fix the problem:
http://gnuradio.org/redmine/wiki/1/USRPClockingNotes
Also, since you use UHD, you can change the daughterboard ID of a
daughterboard on a USRP2 from your host PC using:
<prefix>/share/uhd/utils/uhd_burn_db_eeprom
An example of changing the DBID for a DBSRX is show here:
http://www.ettus.com/uhd_docs/manual/html/dboards.html#id1
Jason
So, Jason, is this because the older FLEX-series boards used an on-board
clock that is
*different* than the one supplied by the USRP2, and the driver code
(either Classic or
UHD) assumes a different clock rate than the one that was previously
on-board, and thus
is mis-programming the PLL?
If the two clocks are the same frequency, then I don't understand why
changing from
"clock supplied on-board" to "clock supplied by USRP2" would "fix"
the problem.
Inquiring minds want to know...
--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
