Thank you so much Matt.
My own .rbf file is already been copied into /usr/local/share/usrp/rev2
directory.
I tried
self._u=usrp.sink_s(which=which,fpga_filename='ionosonde_tx_test0106.rbf')
to load the .rbf file for tx and rx as well.
However, I got the error as bellow when I ran the top-level python code. (I'm
modifying the python program and FPGA bitstream of gr-sounder in gnuradio.)
Exception exceptions.AttributeError: "sounder instance has no attribute
'_transmitting'" in <bound method sounder.__del__ of <gnuradio.sounder.sounder
instance at 0x9e3078c>> ignored
Traceback (most recent call last):
File "./usrp_ionosonde.py", line 115, in <module>
main()
File "./usrp_ionosonde.py", line 91, in main
debug=options.debug,which=options.which)
TypeError: __init__() got an unexpected keyword argument 'which'
I also get this error when I do the simulation in PyDev. what's the problem it
sould be?
Thanks in advance
Yan
----- Original Message -----
From: Mattias Kjellsson <m...@kth.se>
Date: Monday, January 11, 2010 3:34 pm
Subject: Re: [Discuss-gnuradio] how to load my own .rbf bitstream?
To: discuss-gnuradio@gnu.org
> Yan Nie wrote:
> > Hello,
> >
> > I've created my own .rbf file. I see the USRP loads the FPGA
> bitstream
> > from /usr/rev{2,4}/*.rbf, but it doesn't allow me to copy my
> .rbf file
> > into this directory.
> I assume you tried the cp as root?
> > How can I load my FPGA bitstream?
> A quick look at http://gnuradio.org/doc/doxygen/index.html
> (which is a
> golden place) I found for instance
>
> usrp_sink_c_sptr
> <http://gnuradio.org/doc/doxygen/classboost_1_1shared__ptr.html>
> usrp_make_sink_c
> <http://gnuradio.org/doc/doxygen/classusrp__sink__c.html#c54a4bc557defc1c1157d09ef523cb4a>
>
> (int which_board, unsigned int interp_rate, int nchan, int mux,
> int
> fusb_block_size, int fusb_nblocks, const std::string
> fpga_filename,
> const std::string firmware_filename) throw (std::runtime_error)
>
> Although this is the c++ consturctor for a complex usrp sink,
> the
> mapping to python should be straight forward, and similar syntax
> (if not
> identical) can be used for the other types of sources/sinks.
>
> Hope this helps, and is what you asked for
> //Mattias
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
