From: Ed B. <eb...@gm...> - 2011-10-27 21:10:40
|
I made the dangerous assumption that it has a 52Mhz clock. How can I tell? The hardware I am working with is an Ettus USRP1 that was dumped on my desk. It has worked with openBTS in the past (I believe version 2.3) and my task is to get it working again on 2.8. As far as I can tell, the USRP1 has 2 daughter cards, and each are labeled as WBX-FE-Simple cards. Looking at the openBTS for dummies tutorial ( gnuradio.org/redmine/attachments/219/for*dummies*.pdf) they show you how to install a 52Mhz clock. Looking at my ursp, nothing that looks like the new clock they added is on my box. -Ed On Thu, Oct 27, 2011 at 4:37 PM, Kurtis Heimerl <khe...@cs...>wrote: > Does is have a 52M clock? What kind of hardware is this? > > On Thu, Oct 27, 2011 at 11:59 AM, Ed Bindl <eb...@gm...> wrote: > > So, I've been strugging through this install over the past 2 days, and > now > > im totally stuck and have no idea where to go from here. > > > > I did a fresh install of ubuntu 11.04. > > > > I downloaded and ran the build-gnuradio script found here: > > > > > http://gnuradio.org/redmine/projects/gnuradio/wiki/InstallingGR#Using-the-build-gnuradio-script > > > > Starting the system... > > 1319741412.4869 ALARM 3074988736 OpenBTS.cpp:517:main: OpenBTS starting, > ver > > 2.6PUBLIC build date Oct 27 2011 > > 1319741412.4894 FORCE 3073693920 Logger.cpp:196:gLogInit: Setting > initial > > global logging level to NOTICE > > > > Warning: Treating daughterboard with invalid EEPROM contents as if it > were a > > "Basic Rx." > > Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom > > utility. > > > > > > Warning: Treating daughterboard with invalid EEPROM contents as if it > were a > > "Basic Rx." > > Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom > > utility. > > > > > > Warning: Treating daughterboard with invalid EEPROM contents as if it > were a > > "Basic Tx." > > Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom > > utility. > > > > > > Warning: Treating daughterboard with invalid EEPROM contents as if it > were a > > "Basic Tx." > > Warning: This is almost certainly wrong... Use appropriate burn-*-eeprom > > utility. > > > > transceiver: usrp_standard.cc:1024: virtual bool > > usrp_standard_tx::set_tx_freq(int, double): Assertion `dac_rate () == > > 128000000' failed. > > 1319741420.4914 ALARM 3066149744 TRXManager.cpp:90:clockHandler: TRX > clock > > interface timed out, assuming TRX is dead. > > 1319741423.4946 ALARM 3066149744 TRXManager.cpp:90:clockHandler: TRX > clock > > interface timed out, assuming TRX is dead. > > 1319741426.4977 ALARM 3066149744 TRXManager.cpp:90:clockHandler: TRX > clock > > interface timed out, assuming TRX is dead. > > 1319741429.5008 ALARM 3066149744 TRXManager.cpp:90:clockHandler: TRX > clock > > interface timed out, assuming TRX is dead. > > > > > > I am running a USRP1 with 2 WBX Daughter boards. Can anyone point me in > the > > right direction here? I'm not sure what else to do! > > > > > > Thanks, > > > > Ed > > > > > ------------------------------------------------------------------------------ > > The demand for IT networking professionals continues to grow, and the > > demand for specialized networking skills is growing even more rapidly. > > Take a complimentary Learning@Cisco Self-Assessment and learn > > about Cisco certifications, training, and career opportunities. > > http://p.sf.net/sfu/cisco-dev2dev > > _______________________________________________ > > Openbts-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > > > > |