cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
cto@qlt
Visitor
Visitor
3,327 Views
Registered: ‎08-06-2017

problem with zybo: Can not compile u-boot

Jump to solution

I followed this tutorial: https://www.instructables.com/id/Embedded-Linux-Tutorial-Zybo/

but now I'm stuck,

when I enter: make CROSS_COMPILE=arm-xilinx-linux-gnueabi-zynq_ZYBO_config

I get the error: System not configured - see README
I have no idea why that occurs, I'm using ubuntu 16 with Vivado Web+SDK 16.4 its a new VM so I have only the xilinx software installed, do i need to install anything else may be?

0 Kudos
Reply
1 Solution

Accepted Solutions
hpoetzl
Voyager
Voyager
5,742 Views
Registered: ‎06-24-2013

Hey cto@qlt

 

The problem is very likely a missing space in your command:

 

make CROSS_COMPILE=arm-xilinx-linux-gnueabi-zynq_ZYBO_config

This should actually be:

 

make CROSS_COMPILE=arm-xilinx-linux-gnueabi- zynq_zybo_config

Also note that lower and upper case is important on Unix/Linux systems.

 

Hope it helps,

Herbert

-------------- Yes, I do this for fun!

View solution in original post

7 Replies
hpoetzl
Voyager
Voyager
5,743 Views
Registered: ‎06-24-2013

Hey cto@qlt

 

The problem is very likely a missing space in your command:

 

make CROSS_COMPILE=arm-xilinx-linux-gnueabi-zynq_ZYBO_config

This should actually be:

 

make CROSS_COMPILE=arm-xilinx-linux-gnueabi- zynq_zybo_config

Also note that lower and upper case is important on Unix/Linux systems.

 

Hope it helps,

Herbert

-------------- Yes, I do this for fun!

View solution in original post

cto@qlt
Visitor
Visitor
3,293 Views
Registered: ‎08-06-2017

That solved that issue.

now I have a new one:

 

 

user@ubuntu:~/DIGILENT_LINUX/u-boot-Digilent-Dev$ make CROSS_COMPILE=arm-xilinx-linux-gnueabi- zynq_zybo_config
Configuring for zynq_zybo board...
trax@ubuntu:~/DIGILENT_LINUX/u-boot-Digilent-Dev$ make CROSS_COMPILE=arm-xilinx-linux-gnueabi-
/bin/bash: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
/bin/bash: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
dirname: missing operand
Try 'dirname --help' for more information.
Generating include/autoconf.mk
/bin/bash: line 2: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
Generating include/autoconf.mk.dep
/bin/bash: line 2: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
/bin/bash: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
/bin/bash: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-ld: No such file or directory
Generating include/spl-autoconf.mk
/bin/bash: line 2: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
Generating include/tpl-autoconf.mk
/bin/bash: line 2: /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
arm-xilinx-linux-gnueabi-gcc -DDO_DEPS_ONLY \
	-g  -Os   -ffunction-sections -fdata-sections -fno-common -ffixed-r9   -fno-strict-aliasing -mno-unaligned-access -mfpu=neon -D__KERNEL__  -I/home/trax/DIGILENT_LINUX/u-boot-Digilent-Dev/include  -I/home/trax/DIGILENT_LINUX/u-boot-Digilent-Dev/arch/arm/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/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc: No such file or directory
Makefile:694: recipe for target 'lib/asm-offsets.s' failed
make: *** [lib/asm-offsets.s] Error 127
user@ubuntu:~/DIGILENT_LINUX/u-boot-Digilent-Dev$ 

 

 

but the fiel is there:

user@ubuntu:~/DIGILENT_LINUX/u-boot-Digilent-Dev$ ls -l /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc
-rwxr-xr-x 1 root root 735360 Oct 26  2016 /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc

its listed, and the file has execute permission, but when I try to execute it i get the no such file error wtf :/

any ideas how that happens?

hbucher
Scholar
Scholar
3,276 Views
Registered: ‎03-22-2016

cto@qlt  If it solved the issue, it is correct etiquette to give @hpoetzl the solution, then open a new request. That will keep new answers coming fast your way. 

Just a few of the respondents here are Xilinx employees. Mostly are here just for the dopamine kick of a kudos and solutions accepted (my case anyway).

Keep that in mind.

vitorian.com --- We do this for fun. Always give kudos. Accept as solution if your question was answered.
I will not answer to personal messages - use the forums instead.
hpoetzl
Voyager
Voyager
3,248 Views
Registered: ‎06-24-2013

Hey cto@qlt

 

The executable in question is a dynamically linked binary, which means that it depends on some libraries.

If one of the libraries is missing, you will get 'No such file or directory'.

Double check the library dependencies with:

 

ldd /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc

And see if the listed libraries are properly configured.

 

Hope this helps,

Herbert

-------------- Yes, I do this for fun!
cto@qlt
Visitor
Visitor
3,176 Views
Registered: ‎08-06-2017
@ubuntu:~/DIGILENT_LINUX/u-boot-Digilent-Dev$ ldd /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc
	not a dynamic executable

wtf?

should I install the xilinx software again or what else should I try?

I have also an other problem i cant start the SDK, when I go on start SDK nothing happens

0 Kudos
Reply
hbucher
Scholar
Scholar
3,168 Views
Registered: ‎03-22-2016

cto@qlt  Can you do a 

 

file /opt/Xilinx/SDK/2016.4/gnu/arm/lin/bin/arm-xilinx-linux-gnueabi-gcc

In my install it is a ELF 32-bit LSB executable, dynamically linked.

 

vitorian.com --- We do this for fun. Always give kudos. Accept as solution if your question was answered.
I will not answer to personal messages - use the forums instead.
cto@qlt
Visitor
Visitor
3,145 Views
Registered: ‎08-06-2017

Ah its 32 bit, that explains a lot...

after installing support for 32 bit executables the build process works Thanks :-)

0 Kudos
Reply