USRP2 firmware build error

I wanted to build the USRP2 firmware to enable the testclk at J503, but
I
have some errors. I download the source with the command "git clone
git://gnuradio.org/gnuradio
" and the mb-gcc from http://gnuradio.org/tools/

Then I execute the commands “./bootstrap” and “./configure.gnu
MB_GCC=/usr/local/bin/microblaze/bin/mb-gcc”. I have no errors or
warnings. Then I execute the command “make” and I have the following
errors:

[email protected]:/usr/local/src/gnuradio/usrp2/firmware# make
make all-recursive
make[1]: Entering directory /usr/local/src/gnuradio/usrp2/firmware' Making all in config make[2]: Entering directory/usr/local/src/gnuradio/usrp2/firmware/config’
make[2]: Nothing to be done for all'. make[2]: Leaving directory/usr/local/src/gnuradio/usrp2/firmware/config’
Making all in include
make[2]: Entering directory
/usr/local/src/gnuradio/usrp2/firmware/include' make[2]: Nothing to be done forall’.
make[2]: Leaving directory
/usr/local/src/gnuradio/usrp2/firmware/include' Making all in lib make[2]: Entering directory/usr/local/src/gnuradio/usrp2/firmware/lib’
gcc -DHAVE_CONFIG_H -I. -I… -DHAL_IO_USES_UART -I…/include -I…/lib
–std=gnu99 -Wall -Werror-implicit-function-declaration -mxl-soft-div
-msoft-float -mxl-soft-mul -mxl-barrel-shift -O2 -MT abort.o -MD -MP -MF
.deps/abort.Tpo -c -o abort.o abort.c
cc1: error: unrecognized command line option “-mxl-soft-div”
cc1: error: unrecognized command line option “-mxl-soft-mul”
cc1: error: unrecognized command line option “-mxl-barrel-shift”
make[2]: *** [abort.o] Error 1
make[2]: Leaving directory /usr/local/src/gnuradio/usrp2/firmware/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory/usr/local/src/gnuradio/usrp2/firmware’
make: *** [all] Error 2
[email protected]:/usr/local/src/gnuradio/usrp2/firmware#

I use Kubuntu 9.04

On Tue, Mar 30, 2010 at 08:38:08AM +0200, Stefan F. wrote:

I wanted to build the USRP2 firmware to enable the testclk at J503, but I
have some errors. I download the source with the command "git clone
git://gnuradio.org/gnuradio
" and the mb-gcc from http://gnuradio.org/tools/

Then I execute the commands “./bootstrap” and “./configure.gnu
MB_GCC=/usr/local/bin/microblaze/bin/mb-gcc”. I have no errors or
warnings. Then I execute the command “make” and I have the following errors:

If you’re building from the firmware directory you must use:

If in firmware directory

./boostrap && ./configure.gnu

This will get you the correct compiler.

If you build the host code and the firmware from the top of the build,
you only need to do

If at top of build tree

./bootstrap && ./configure

On Tue, Mar 30, 2010 at 12:05:25PM +0200, Stefan F. wrote:

Then I execute the commands “./bootstrap” and "./configure.gnu

make[2]: Entering directory
Making all in lib
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/gnuradio/usrp2/firmware’
make: *** [all] Error 2
[email protected]:/usr/local/src/gnuradio/usrp2/firmware#

I use Kubuntu 9.04

I did this but it dosen’t solve the problem of executing the command “make”

Sorry, try this:

$ export PATH=/usr/local/bin/microblaze/bin:$PATH
$ ./bootstrap && ./configure.gnu
$ make

Eric

Eric B. schrieb:

" and the mb-gcc from http://gnuradio.org/tools/

make[1]: Entering directory `/usr/local/src/gnuradio/usrp2/firmware’
make[2]: Leaving directory
cc1: error: unrecognized command line option “-mxl-soft-div”

$ ./bootstrap && ./configure.gnu
$ make

Eric

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?

Eric B. schrieb:

warnings. Then I execute the command “make” and I have the following
you only need to do
make[2]: Nothing to be done for `all’.
gcc -DHAVE_CONFIG_H -I. -I… -DHAL_IO_USES_UART -I…/include -I…/lib
make: *** [all] Error 2
[email protected]:/usr/local/src/gnuradio/usrp2/firmware#

I use Kubuntu 9.04

I did this but it dosen’t solve the problem of executing the command
“make”

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

On Mon, Apr 5, 2010 at 4:40 PM, Stefan F. [email protected]
wrote:

(from mb-gcc-4.1.1.gr2.i386.tar.gz)? As I said in a message to the
firmware?
–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

Tom R. schrieb:

http://gnuradio.org/releases/usrp2-bin/release/ on the same sd-card I
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

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs