Lab 1.3 not working at the final stage

Hi lasur2,

I have not seen a U-Boot crash at this point before when using the git 14.2 release tag.  Did you press a key during the autoboot countdown?  If not, U-Boot will automatically try to boot Linux, which if you are still on Lab 1.3 would be expected to fail.

Assuming that you are pressing a key to interrupt autoboot and there is a real crash, perhaps you accidentally ended up on the wrong release tag or board config.  You can see what release tag is currently checked out by changing into the U-Boot folder and checking the status of the local repository.

$ cd u-boot-xlnx
$ git status

Also, be sure that you configured U-Boot for ZedBoard using this command:

$ make zynq_zed_config

You can also try the lab solution file boot.bin to see if you see the same error.

Regards,

-Kevin

Hi Folks,

I also had trouble in the final stage.
My terminal didn't respond.
The instruction in step 12, page 16, says power cycle the board. This causes Tera Term to looses the terminal connection. Instead Press BUTTON 7 u201CPS-RSTu201D in the bottom left corner of the board to warm-boot the board.
Then the terminal starts responding with the uboot-prompt when you send keyboard chars to interupt the booting sequence.

Just sharing it. Hope this helps.

Rgds,
Technicolor
Just sharing

Hi Kevin,

    Thanks for the response. I am re-doing the lab as I need to get it working !

   $ cd u-boot-xlnx

   $ git status gives me the following o/p

# On branch xilinx-14.2-build1-trd
# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#tmodified:   include/configs/zynq_zed.h
#
no changes added to commit (use "git add" and/or "git commit -a")


   $ make distclean gives me the following O/p
   awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend

   $ make zynq_zed_config gives me
awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend
Configuring for zynq_zed board...

Then copy and paste the patch file Now,

$ git apply 0001-Xilinx-ARM-Experimental-32MB-Ramdisk-on-ZedBoard.patch

Upto this point is lab1.2 Experiment #2 and I am successful.

Now when I move to lab1.2 Experiment #3,

$pwd
I am in /home/training/u-boot-xlnx

$ make

I see the following errors:

ake: arm-linux-gcc: Command not found
/bin/sh: arm-linux-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk
/bin/sh: line 3: arm-linux-gcc: command not found
/bin/sh: arm-linux-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
Generating include/autoconf.mk.dep
/bin/sh: line 3: arm-linux-gcc: command not found
make: arm-linux-gcc: Command not found
/bin/sh: arm-linux-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/sh: arm-linux-gcc: command not found
/bin/sh: arm-linux-ld: command not found
/bin/sh: arm-linux-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
/bin/sh: arm-linux-gcc: command not found
dirname: missing operand
Try `dirname --help' for more information.
arm-linux-gcc -DDO_DEPS_ONLY
tt-g  -Os   -fno-common -ffixed-r8 -msoft-float   -fno-strict-aliasing  -fno-common -ffixed-r8 -msoft-float  -D__KERNEL__ -I/home/training/u-boot-xlnx/include -fno-builtin -ffreestanding -nostdinc -isystem  -pipe  -DCONFIG_ARM -D__ARM__         -march=armv5 -march=armv7-a -I/home/training/u-boot-xlnx/board/xilinx/common -I/home/training/u-boot-xlnx/board/xilinx/zynq_common -Wall -Wstrict-prototypes -mno-unaligned-access   
tt-o lib/asm-offsets.s lib/asm-offsets.c -c -S
make: arm-linux-gcc: Command not found
make: *** [lib/asm-offsets.s] Error 127


This is the cross compiler error I suppose. I am not sure how to fix it. please help!!

Thank you!!

Hi lasur2,

Those error messages seem to indicate that the cross compiler toolchain cannot be found on your system.  I can think of two likely causes for this.  The first cause would be that the CodeSourcery Toolchain did not get installed correctly during the Lab 0.1 exercises.  The second is that the wrong compiler prefix OR incorrect paths have been specified.

Both the toolchain and the path to the toolchain must be setup on your system.  Otherwise, at build time, the compiler executable will not be found properly.

One other thing to note is that I used an Ubuntu machine a while back which required me to specify the cross-compiler prefix as part of the make command.  If you have a similar system, you may need to do something like this:

$ make ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi-

Regards,

-Kevin

Hi Kevin,

   Thanks for your remote support. I was able to debug with your pointer and got the lab1.3 working ..

   I am currently facing difficulty in getting lab 2.3 work. I am debugging on my own. Shall seek your help and pointers in case I run into problems while debug.

Thank you very much once again!!

Hi lasur2,

Glad to hear that you were able to get Lab 1.3 working. If you continue to have problems with Lab 2.3, please repost your 2.3 issue as a new topic so that it is easier for other community members to find.

Regards,

-Kevin

Hi All,
M stuck at a step behind !

M not getting message on the serial terminal "Hit any key to stop autoboot: 3"

And everything stops here, m using tera term for the communication and terminal is not responding at all..
Can anyone help me on this ?
below is the copy of my XMD terminal....
Xilinx Microprocessor Debugger (XMD) Engine
Xilinx EDK 14.2 Build EDK_P.28xd
Copyright (c) 1995-2012 Xilinx, Inc.  All rights reserved.

XMD%
XMD%
Accepted a new TCLSock connection from 127.0.0.1 on port 3462
connect arm hw

JTAG chain configuration
--------------------------------------------------
Device   ID Code        IR Length    Part Name
1       4ba00477           4        Cortex-A9
2       03727093           6        XC7Z020

CortexA9 Processor Configuration
-------------------------------------
Version.............................0x00000003
User ID.............................0x00000000
No of PC Breakpoints................6
No of Addr/Data Watchpoints.........1

Connected to "arm" target. id = 64
Starting GDB server for "arm" target (id = 64) at TCP port no 1234
XMD% source ps7_init
couldn't read file "ps7_init": no such file or directory
XMD% cd ..
XMD% cd ..
XMD% cd ..
XMD% cd ..
XMD% cd xilinxtest
XMD% cd project
XMD% cd opfile
XMD% source ps7_init
couldn't read file "ps7_init": no such file or directory
XMD% ls
bootimage.bif
ps7_init.tcl
u-boot.bin
u-boot.elf
u-boot.mcs
XMD% source ps7_init.tcl
XMD% ps7_init
XMD% dow -data qspi_image.bin 0x08000000
warning: FPGA is NOT Configured. Accessing FPGA Address space can
cause the System to hang. Use "fpga" command to Configure the FPGA
ERROR: Cannot OPEN File
t - qspi_image.bin

XMD% init_user
Info:  Enabling level shifters and clearing fabric port resets
XMD% dow u-boot.elf
warning: FPGA is NOT Configured. Accessing FPGA Address space can
cause the System to hang. Use "fpga" command to Configure the FPGA
Downloading Program -- u-boot.elf
tsection, .text: 0x04000000-0x0402aa83
tsection, .rodata: 0x0402aa84-0x04035a7e
tsection, .hash: 0x04035a80-0x04035ac7
tsection, .data: 0x04035ac8-0x0403658f
tsection, .got.plt: 0x04036590-0x0403659b
tsection, .u_boot_cmd: 0x0403659c-0x04036bbb
tsection, .rel.dyn: 0x04036bbc-0x0403c8eb
tsection, .dynsym: 0x0403c8ec-0x0403c9bb
tsection, .bss: 0x04036bbc-0x04079acb
Setting PC with Program Start Address 0x04000000
XMD% dow -data u-boot.bin 0x08000000
warning: FPGA is NOT Configured. Accessing FPGA Address space can
cause the System to hang. Use "fpga" command to Configure the FPGA
Downloading Data File -- u-boot.bin at 0x08000000
Progress ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................Done
XMD% con

RUNNING> XMD% sf probe 0 0 0
invalid command name "sf"
XMD% stop
Processor stopped