discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] USRP2 firmware build error


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] USRP2 firmware build error
Date: Mon, 5 Apr 2010 22:19:18 -0400

On Mon, Apr 5, 2010 at 4:40 PM, Stefan Fehrle <address@hidden> wrote:
>
> Tom Rondeau schrieb:
>>> Now I can build the firmware.
>>>
>>> When I copy "txrx.bin" from the subfolder apps to the sd-card. I can't
>>> connect to the USRP2. The led e and f burns. The GNU Radio Companion
>>> (GRC)
>>> stops the program with the error message "RuntimeError: No USRPs found
>>> on
>>> interface eth1".
>>>
>>> When I copy "txrx.bin" from
>>> http://gnuradio.org/releases/usrp2-bin/release/ on the same sd-card I
>>> have
>>> no errors and the programm runs perfect.
>>>
>>> Where did I make the misatke?
>>
>>
>> Did you build the microblaze compiler yourself (from
>> EDK101_GPL_GNU_src.tar.gz with the patch) or use the prebuilt binary
>> (from mb-gcc-4.1.1.gr2.i386.tar.gz)? As I said in a message to the
>> list a few days ago, when building the microblaze compiler, you need
>> to be careful what GCC compiler you use. I've never had an issue using
>> the prebuilt version for making firmware images, though.
>>
>> Tom
>>
>>
>
> I use the prebuilt binary of http://gnuradio.org/tools/
> Should I use a special version of the fpga software when I build my own
> firmware?
>
> When I run the command "mb-gcc -v" in a shell I get this as the response:
>
> Using built-in specs.
> Target: microblaze-xilinx-elf
> Configured with:
> /home/eb/build/Xilinx_EDK_GNU_10.1i/mb/build/lin/bld_gcc/gcc/configure -
> target=microblaze-xilinx-elf --
> prefix=/home/eb/build/Xilinx_EDK_GNU_10.1i/mb/release/lin/mb --program-
> prefix=mb- --with-newlib --enable-languages=c,c++ --enable-multilib
> --disable-
> libssp --disable-newlib-atexit-dynamic-alloc --enable-optimize-memory
> Thread model: single
> gcc version 4.1.1 20060524 (Xilinx EDK 10.1 Build EDK_K.10 13 Oct 2008)
>
>
> Stefan


Yep, that's the right one, so something else must be going on.

Tom




reply via email to

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