From: Sebastian --- <sep...@ho...> - 2011-01-24 17:39:39
|
I Recompiled Everything. gnuradio-3.3.0.tar.gz and openbts-2.6.0Mamou.tar.gz Still says: 1295888882.0261 ALARM 3079568240 Transceiver.cpp:551:driveControl: TX failed to tune 1295888882.0261 ALARM 3078915792 TRXManager.cpp:349:tune: TXTUNE failed with status 1 But only with 52M > Date: Mon, 24 Jan 2011 12:21:14 -0200 > Subject: Re: [Openbts-discuss] openbts doesnt work with 52Mhz > From: igo...@gm... > To: sep...@ho... > CC: ope...@li... > > Yes, you have to recompile. > The clock frequency is hard-coded in the gnuradio code > > On Mon, Jan 24, 2011 at 9:12 AM, Sebastian --- <sep...@ho...> wrote: > > I use the latest gnuradio version (pulled from git), openbts 2.6 and usrp1 > > with clocktamer. > > > > everything works fine with 64Mhz, I can connect my phone to openbts. > > > > when I adjust clocktamer to 52Mhz and edit openbts.config to transceiver52M, > > openbts gives me TX tune errors. > > > > I assume gnuradio supports auto switching between clk-freq? Or do i have to > > recompile gnuradio when i change freq? > > > > ------------------------------------------------------------------------------ > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > > Finally, a world-class log management solution at an even better price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY! > > http://p.sf.net/sfu/arcsight-sfd2d > > _______________________________________________ > > Openbts-discuss mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openbts-discuss > > > > > > > > -- > Igor Almeida |