On Tue, Jul 24, 2007 at 04:19:58PM -0700, Roshan Baliga wrote: > S Mande wrote: > >1) Do I need a 3rd party tool to transfer my code to the FPGA on USRP ? > >I remember using a JTAG cable and Active-HDL for this task when i worked > >with Aldec procesors. > > I'm sure there are multiple ways to do this, but I just use the existing > usrp framework to load the RBF file onto the fpga. That is, when I > generate a new RBF file, I throw it into > /usr/local/share/usrp/rev4/std_2rxhb_2tx.rbf and load it up with my own > C application that links to libusrp.so. It's the quick and dirty way, > but hey, it works. > > >2) I believe that the firmware is loaded everytime I run GNU radio. Is > >it that I replace the existing fpga Verilog firmware code ( .v file > >) from its existing location .i.e. gnuradio folder > >with my modified Verilog firmware code ? > > The RBF file that is loaded is picked up from a predetermined location. > In my case, with a rev 4 usrp, it's > /usr/local/share/usrp/rev4/std_2rxhb_2tx.rbf. In your quartus project, > the file you want is in usrp/fpga/toplevel/usrp_std/usrp_std.rbf > > If you replace the file in /usr/local... with a new rbf file, the > gnuradio code will load it next time you power cycle/run the USRP. > > -Roshan
You can also specify the rbf file name in the usrp constructor: u = usrp.sourc_c(..., fpga_filename="myfile.rbf") Eric _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
