[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Doubt about FPGA code and firmware

From: Gabriel Morel
Subject: Re: [Discuss-gnuradio] Doubt about FPGA code and firmware
Date: Mon, 28 Feb 2011 10:28:40 -0500

I have to do almost the same thing.  But me, I have to bypass the data from the ADC by the mictor connector to a board from Xilinx, a ML401.  All the filter for equalizers or other types should be done in this one and the data go back in the usrp2 by the mictor connector again.
----- Original Message -----
Sent: Monday, February 28, 2011 10:10 AM
Subject: Re: [Discuss-gnuradio] Doubt about FPGA code and firmware


Sorry for answering so late.

@Gabriel Morel

For my Master Thesis I had to implement a kind of test bench for different versions of a particular block. Nothing really complex, multiplexers, filters, etc. The point is I must use the USRP2 board.

@Matthias Wilhelm

Could I ask why you recommend me the use of the UHD code instead of the GNU Radio code?



2011/2/14 Matt Ettus <address@hidden>
On 02/14/2011 06:09 AM, Eduardo Lloret Fuentes wrote:
> Hello,
> @Nick Foster
>     If your FPGA design doesn't include a Microblaze processor to do
>     something useful with the firmware image, you won't need to load the
>     firmware.
> My FPGA design doesn't include a Microblaze processor so I also think
> that I don't need it. My doubt comes from the boot sequence that I read
> in the USRP2GenFAQ section:
> http://gnuradio.org/redmine/wiki/gnuradio/USRP2GenFAQ#How-does-the-USRP2-boot-How-is-the-FPGA-firmware-loaded
> If I don't have a processor, the second step is not necessary but I
> don't know if the first (loading of FPGA design) is accomplished
> properly. What do you think?

The first step will work fine without the microblaze.  You will need to
make sure you keep triggering the watchdog timer to make sure nothing is
reset.  See the config page of the schematics to see how this works.


Discuss-gnuradio mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]