On Sat, Feb 13, 2010 at 02:38:26AM +0300, Alexander Chemeris wrote: > Hi Eric, > > On Sat, Feb 13, 2010 at 02:29, Eric Blossom <e...@comsec.com> wrote: > > I think a better fix would be to burn the frequency into the > > motherboard flash on the USRP, then the host could query it. If the > > usrp didn't have a valid value stored, the host would assume the > > default 64MHz. > > Is it possible to reflash it quickly then? With our ClockTamers you can > change frequency even in real-time, without stopping USRP.
I don't think you'd wants to reflash the frequently. I was thinking of a one time change. In general, I was thinking that instead of changing all the apps in the world to support the option, you'd want to store the fpga clock rate in a single place. Another way to get the info is to use an environment variable. This does have the disadvantage that it's not directly correlated to the USRP that you're using. (This might matter if you had two usrps, one with modidified clock and one without.) Eric _______________________________________________ Patch-gnuradio mailing list Patch-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/patch-gnuradio