[USRP-users] Loading custom FPGA image on E310
Sergio Cruz Perez
serchsype at hotmail.com
Mon Mar 7 14:43:01 EST 2016
Yes, I solved it adding my fpga image to the device3 arguments: self.device3 = variable_uhd_device3_0 = ettus.device3(uhd.device_addr_t( ",".join(("type=e3x0 ", "fpga=/usr/share/uhd/images/usrp_e310_rfnoc_fpga.bit")) ))
> Date: Mon, 7 Mar 2016 11:09:51 -0500
> To: usrp-users at lists.ettus.com
> Subject: Re: [USRP-users] Loading custom FPGA image on E310
> From: usrp-users at lists.ettus.com
> On 03/07/2016 11:03 AM, Moritz Fischer via USRP-users wrote:
> > Sergio,
> > On Fri, Mar 4, 2016 at 12:36 PM, Sergio Cruz Perez via USRP-users
> > <usrp-users at lists.ettus.com> wrote:
> >> uhd_image_loader --args="type=e3x0" --fpga-path="/usr/local/share/uhd/images/usrp_e310_rfnoc_fpga.bit"
> > Not for E310.
> >> Then, when I run uhd_usrp_probe --init-only, the image that is loaded is the original one (usrp_e310_fpga_.bit):
> > Try uhd_usrp_probe
> > --args='fpga=/usr/local/share/uhd/images/usrp_e310_rfnoc_fpga.bit.
> > Moritz
> The key take-away here is that the image is loaded every time a session
> starts with the E3xx FGPA, so you have to mention the desired
> FPGA image as a device argument for your apps, otherwise, it'll use
> the default.
> Some USRP devices (N2xx, USRP2, X3xx) have a "one time FPGA load"
> doctrine--you use a "loader", and the FPGA image remains until
> you explicitly change it. In other devices (USRP1, B2xx, E3xx) the
> FPGA image is loaded dynamically as part of your application
> session with the device.
> USRP-users mailing list
> USRP-users at lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the USRP-users