To know if you design is loaded properly, you can
use the leds to indicate some state of your design. The led F is
already connect to the PROGRAM_DONE pin of the FPGA in the cpld. You can
also modify the cpld to turn on some light on the board.
what do you have to do in your thesis?
----- Original Message -----
Sent: Monday, February 14, 2011 9:09
Subject: Re: [Discuss-gnuradio] Doubt
about FPGA code and firmware
If your FPGA design doesn't include a Microblaze processor
something useful with the firmware image, you won't need to load
Will you start from a new project
or just modify the old one. I try to compile the raw ethernet version
but I have many problem. Give some news of your works
I started completely from a new project but If
I try to modify the old one I will tell you my results.
if you plan to use any part of the USRP2's hardware
(daughterboard, ADC, UART, ethernet, ...) and don't want to implement all
the steps required to configure and use them properly, I would suggest to
integrate your code parallel to the vanilla system (the UHD one!), it is far
more work to get it running otherwise. The firmware does a lot of stuff. If
you don't plan to use the hardware why not use a Spartan evaluation kit
instead, they have nicer I/O capabilities for experimenting and
I plan to use the BasicRX, BasicTX, LFTX and LFRX
daughterboards just as a simple input/output to the FPGA. Besides I need the
ADC and DAC but I thought they don't need the processor. A lot of thanks for
your advice. When you say to integrate the code to the vanilla system, do you
mean add my verilog code to their project?
I also think it would be
better to use a Spartan evaluation kit to do this but the use of the USRP2
board is part of my thesis requirements.
Thanks you so much to all of
you for your help.