step by step install of Red Pitaya fails with file not found

Applications, development tools, FPGA, C, WEB
Post Reply
amalagon
Posts: 17
Joined: Thu Jan 15, 2015 9:34 pm

step by step install of Red Pitaya fails with file not found

Post by amalagon » Fri Jan 23, 2015 1:52 am

Hi,

I followed the instructions in this [url=viewtopic.php?f=8&t=49]post[\url] to build the C development environment for the redpitaya.
I'm using Debian on a 64-bin machine. I have a Vivado+SDK 2013.3 installation with an ISE License, and installed Xilinx to /opt/Xilinx. I followed the instructions to clone bare repos of linux and u-boot, and altered the BR2_TOOLCHAIN_EXTERNAL_PATH to reflect the correct path. I made sure to run make in a clean repo, and linked the paths for make and gmake.

I get the following 'file not found errors' when I try to run make in the RedPitaya directory:

Code: Select all

admx@admxcontrol:~/RedPitaya$ make
mkdir build
make -C OS/u-boot RP_VERSION=0.92-0 RP_REVISION=devbuild
make[1]: Entering directory `/home/admx/RedPitaya/OS/u-boot'
mkdir u-boot-xlnx
cd u-boot-xlnx; curl -L https://github.com/Xilinx/u-boot-xlnx/archive/xilinx-v14.6.01.tar.gz | tar xz --strip-components 1
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   135    0   135    0     0    449      0 --:--:-- --:--:-- --:--:--   574
  0     0    0 12.2M    0     0  3110k      0 --:--:--  0:00:04 --:--:-- 4429k
cat patches/*.patch | patch -p1 -d u-boot-xlnx
patching file include/configs/zynq_zed.h
patching file include/phy.h
patching file include/configs/zynq_common.h
patching file board/xilinx/zynq/board.c
patching file drivers/net/phy/lantiq.c
patching file drivers/net/phy/Makefile
patching file drivers/net/phy/lantiq.c
patching file drivers/net/phy/phy.c
patching file include/configs/zynq_common.h
patching file include/linux/mii.h
patching file include/phy.h
patching file drivers/net/phy/lantiq.c
patching file drivers/net/phy/lantiq.c
patching file include/configs/zynq_common.h
patching file boards.cfg
patching file include/configs/zynq_common.h
patching file include/configs/zynq_red_pitaya.h
patching file include/configs/zynq_red_pitaya.h
patching file tools/env/fw_env_main.c
patching file tools/env/Makefile
patching file tools/env/version.h
patching file arch/arm/cpu/armv7/zynq/ddrc.c
make -C u-boot-xlnx arch=ARM zynq_red_pitaya_config
make[2]: Entering directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
make[2]: Leaving directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
make[2]: Entering directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
Configuring for zynq_red_pitaya board...
make[2]: Leaving directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
make -C u-boot-xlnx arch=ARM all
/bin/bash: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
/bin/bash: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
dirname: missing operand
Try `dirname --help' for more information.
make[2]: Entering directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
Generating include/autoconf.mk
/bin/bash: line 3: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
Generating include/autoconf.mk.dep
/bin/bash: line 3: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
make[2]: Leaving directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
/bin/bash: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
/bin/bash: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
dirname: missing operand
Try `dirname --help' for more information.
make[2]: Entering directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
/bin/bash: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
/bin/bash: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-ld: No such file or directory
arm-xilinx-eabi-gcc -DDO_DEPS_ONLY \
		-g  -Os   -fno-common -ffixed-r8 -msoft-float  -fno-strict-aliasing -mno-unaligned-access -D__KERNEL__ -I/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__    -march=armv5 -Wall -Wstrict-prototypes       \
		-o lib/asm-offsets.s lib/asm-offsets.c -c -S
/bin/bash: /opt/Xilinx/Vivado/2013.3/../../SDK/2013.3/gnu/arm/lin/bin/arm-xilinx-eabi-gcc: No such file or directory
make[2]: *** [lib/asm-offsets.s] Error 127
make[2]: Leaving directory `/home/admx/RedPitaya/OS/u-boot/u-boot-xlnx'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/admx/RedPitaya/OS/u-boot'
make: *** [build/u-boot.elf] Error 2
admx@admxcontrol:~/RedPitaya$ [\code]

I know I have those files, as I can see them (snippet below):
[code]admx@admxcontrol:/opt/Xilinx/SDK/2013.3/gnu/arm/lin/bin$ ls
arm-xilinx-eabi-addr2line   arm-xilinx-linux-gnueabi-addr2line
arm-xilinx-eabi-ar	    arm-xilinx-linux-gnueabi-ar
arm-xilinx-eabi-as	    arm-xilinx-linux-gnueabi-as
arm-xilinx-eabi-c++	    arm-xilinx-linux-gnueabi-c++
arm-xilinx-eabi-c++filt     arm-xilinx-linux-gnueabi-c++filt
arm-xilinx-eabi-cpp	    arm-xilinx-linux-gnueabi-cpp
arm-xilinx-eabi-elfedit     arm-xilinx-linux-gnueabi-elfedit
arm-xilinx-eabi-g++	    arm-xilinx-linux-gnueabi-g++
arm-xilinx-eabi-gcc	    arm-xilinx-linux-gnueabi-gcc
arm-xilinx-eabi-gcc-4.7.3   arm-xilinx-linux-gnueabi-gcc-4.7.3
arm-xilinx-eabi-gcc-ar	    arm-xilinx-linux-gnueabi-gcc-ar
arm-xilinx-eabi-gcc-nm	    arm-xilinx-linux-gnueabi-gcc-nm
arm-xilinx-eabi-gcc-ranlib  arm-xilinx-linux-gnueabi-gcc-ranlib
arm-xilinx-eabi-gcov	    arm-xilinx-linux-gnueabi-gcov
arm-xilinx-eabi-gdb	    arm-xilinx-linux-gnueabi-gdb
arm-xilinx-eabi-gprof	    arm-xilinx-linux-gnueabi-gprof
arm-xilinx-eabi-ld	    arm-xilinx-linux-gnueabi-ld
arm-xilinx-eabi-nm	    arm-xilinx-linux-gnueabi-nm[\code]

Does anyone have any recommendations of what I should do? Thanks,

amalagon

Nils Roos
Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: step by step install of Red Pitaya fails with file not f

Post by Nils Roos » Fri Jan 23, 2015 11:10 am

Hi,
Did you do

Code: Select all

source /opt/Xilinx/Vivado/2013.3/settings64.sh
export CROSS_COMPILE=arm-xilinx-eabi-
before calling make ?

amalagon
Posts: 17
Joined: Thu Jan 15, 2015 9:34 pm

Re: step by step install of Red Pitaya fails with file not f

Post by amalagon » Fri Jan 23, 2015 8:55 pm

Hi Nils,

Yep, I sourced the settings64.sh file and did the export of CROSS_COMPILE with the eabi extension before running make. I remember reading in some other posts that people found the paths were getting mangled by some steps in the installation process; could that be what's going on?

amalagon

amalagon
Posts: 17
Joined: Thu Jan 15, 2015 9:34 pm

Re: step by step install of Red Pitaya fails with file not f

Post by amalagon » Thu Jan 29, 2015 4:21 am

I've gotten a bit further - I'm now trying to install the development environment on a VM with Ubuntu 14.04. I mistakenly chose a 32 bit iso image so that's what it's running. The host is running Mac 10.9.5.

After following the step by step installation guide, as well as installing multilib and g++, when I do

Code: Select all

cd RedPitaya
source /opt/Xilinx/Vivado/2013.3/settings32.sh
export CROSS_COMPILE=arm-xilinx-eabi-
make
I get the following error message:

Code: Select all

Kernel: arch/arm/boot/zImage is ready
UIMAGE arch/arm/boot/uImage
"mkimage" command not found - U-Boot images will not be built
make[ 3]: *** [arch/arm/boot/uImage] Error 1
make[2]: *** [uImage] Error 2
make[2]: Leaving directory `/home/admx/RedPitaya/OS/linux/linux-xlnx
I tried adding /var/git to my PATH (as that's where I cloned u-boot-xlnx) but got the same error when running make again in a fresh clone of RedPitaya - has anyone encountered this error?

Thanks,

amalagon

Nils Roos
Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: step by step install of Red Pitaya fails with file not f

Post by Nils Roos » Thu Jan 29, 2015 11:34 am

Hi amalagon,

The mkimage tool is an output product of the u-boot build; it will be in the OS/u-boot/u-boot-xlnx/tools folder. If you add that to your PATH environment variable before starting the build, it should work.

amalagon
Posts: 17
Joined: Thu Jan 15, 2015 9:34 pm

Re: step by step install of Red Pitaya fails [SOLVED]

Post by amalagon » Fri Jan 30, 2015 1:15 am

Thanks, success!

Post Reply
jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie

Who is online

Users browsing this forum: No registered users and 25 guests