U-boot won't boot

I tried to start U-boot from GDB and first instruction (which is a branch instruction) caused GDB to output: "Cannot access memory at address 0x9fa90ddc", which is an address within the PL domain (M_AXI_GP1).

First shell:
$ /opt/Xilinx/SDK/2013.2/bin/lin/xmd
XMD% connect arm hw
XMD% source /opt/Xilinx/14.6/ISE_DS/EDK/sw/lib/hwplatform_templates/zed_hw_platform/ps7_init.tcl
XMD% ps7_init

Second shell:
$ /opt/Xilinx/SDK/2013.2/gnu/arm/lin/bin/arm-xilinx-eabi-gdb u-boot.elf
(gdb) target remote localhost:1234
(gdb) load
(gdb) step

The last command produced this output:
(gdb) step
Cannot access memory at address 0x9fa90ddc
reset () at start.S:131
131ttbltsave_boot_params

Are you using MizroZed or Zedboard? They have different hardware, and so (slightly, but still) different MIO pinout and different FSBL (if you are using Xilinx tools).
If you use MicroZed board, you may try alternative software, configuration files so far exist for MicroZed only. For debugging it allows you to control LED and UART output during the initial stages of booting, before U-boot prompt,
http://sourceforge.net/p/elphel/ezynq/ - standalone version
http://sourceforge.net/p/elphel/meta-ezynq - OpenEmbedded meta

Andrey

I'm using MicroZed.

1) Are you saying that the Xilinx U-boot repository does not have support for the MicroZed board?
Quite annoying Avnet hasn't pushed their MicroZed files upstream yet (a working U-boot is shipped with the board in its NOR flash)...

2) Do you know whether there are any issues using "zed_hw_platform" in the Xilinx SDK for making an FSBL for MicroZed?
Enabling debug in the FSBL, it seems to work fine, but I don't know if there are something it might not have configured or configured wrong.

3) Is there some official MicroZed tutorial or guide I have overlooked, which produce a working version of U-boot for MicroZed?

I tried to build from you reference (standalone version), but the build fails:
make[1]: Entering directory `elphel-ezynq/u-boot-xlnx/arch/arm/cpu/armv7/zynq'
make[1]: *** No rule to make target `.depend', needed by `all'.  Stop.

Hi Kian,

can you please post here or (to save bandwidth) email it to me at andrey_at_elphel.com the full output install_uboot.sh and makeuboot? I just tried in on a fresh computer w/o any problems.

1) When we got MicroZed in August, there was none.
2) Zedboard and Microzed have different connections, but we were able to make a working image with Xilinx tools, carefully entering data from the MicroZed documentation. MIO pins are different for 2 boards
3) Circuit diagram+documentation that are available for the board are sufficient to produce a working version. I can not send you our files produceds by Xilinx tools because Xilinx license does not allow such distribution.

Andrey

Hi Kian,

You need to run provided scripts, not just manual make commands.
First you need to run install_uboot.sh (seems you have done that), then follow instructions that that script outputs in the very end:
- modify initenv file to match you path to arm toolchain,
- cd to the u-boot directory and
- run ./makeuboot.
ezynqcfg.py program runs twice - first before 'make' to create C file (that was missing in your case), second - in the very end (to provide u-boot.bin length to the header). You can just read that makeuboot script to see what it does.

Andrey

FSBL:
I found the necessary tutorials for building a working FSBL for MicroZed here: www.microzed.org -> Reference Designs/Tutorials -> MicroZed
- Tutorial 01 Build the Zynq Hardware Platform
- Tutorial 02 First Application - Hello World
- Tutorial 04 FSBL and Boot from QSPI and SD Card

U-boot:
The U-boot for ZC70x seems to work - I only need it to launch the Linux kernel. See http://www.wiki.xilinx.com/Build+U-Boot
Use the "zynq_zc70x_config" target.

Kharas, "The U-boot for ZC70x seems to work" is not a real solution. U-Boot is licensed under GNU GPL, so it is illegal to distribute binaries without the source code. Source code for the u-boot.bin for Microzed, not the source for zynq_zc70x.

We plan to migrate to a proprietary bootloader in a later phase anyway. At the moment, it is just a matter of getting our OS's up and running at early stages of the project.

I see, KKaras, so you plan to use you house-built bootloader not based on U-Boot and the rest of the software not based on GNU/Linux. Correct?

Hi kkaras,

After looking into this further, I found that the U-Boot binary which is shipping on MicroZed and distributed in the "MicroZed Linux microSD Card Image Archive 10.Aug.13" found on this page: http://www.microzed.org/documentation/1519 is publicly available from Xilinx from their GIT repository located here:

https://github.com/Xilinx/u-boot-xlnx

That binary provided in the MicroZed Linux microSD Archive was built directly from the xilinx-v14.5 release tag on that repository using the zynq_zed configuration since it is part of the Zed family of boards and is very similar to ZedBoard hardware configuration as far as U-Boot is concerned.

The dirty tag on the build is from the result of modification to the one of the configuration files for the default U-Boot environment.  This modification was made to support the MTD partitioning that was selected and to allow the second stage boot loader (U-Boot) to perform the PL configuration rather than have this task performed by the FSBL.

In particular, these extra environment variables are used to support these features of MicroZed.

#define CONFIG_EXTRA_ENV_SETTINGSt
t"ethaddr=00:0a:35:00:01:220"t
t"kernel_image=uImage0"t
t"ramdisk_image=uramdisk.image.gz0"t
t"devicetree_image=devicetree.dtb0"t
t"bitstream_image=system.bit.bin0"t
t"bitstream_size=0x3DBAFC0"t
t"loadbit_addr=0x1000000"t
t"kernel_size=0x5000000"t
t"devicetree_size=0x200000"t
t"ramdisk_size=0x5E00000"t
t"fdt_high=0x200000000"t
t"initrd_high=0x200000000"t
t"mmc_loadbit_fat=echo Loading bitstream from SD/MMC/eMMC to RAM.. && "
tt"mmcinfo && "
tt"fatload mmc 0 ${loadbit_addr} ${bitstream_image} && "
tt"fpga load 0 ${loadbit_addr} ${filesize}0"
t"norboot=echo Copying Linux from NOR flash to RAM... && "
tt"cp 0xE2100000 0x3000000 ${kernel_size} && "
tt"cp 0xE2600000 0x2A00000 ${devicetree_size} && "
tt"echo Copying ramdisk... && "
tt"cp 0xE2620000 0x2000000 ${ramdisk_size} && "
tt"bootm 0x3000000 0x2000000 0x2A000000"
t"qspiboot=echo Copying Linux from QSPI flash to RAM... && "
tt"sf probe 0 0 0 && "
tt"sf read ${loadbit_addr} 0xC00000 ${bitstream_size} && "
tt"mw 0xF8007080 0x30800100 0x4 && "
tt"fpga load 0 ${loadbit_addr} ${bitstream_size} && "
tt"sf read 0x3000000 0x100000 ${kernel_size} && "
tt"sf read 0x2A00000 0x600000 ${devicetree_size} && "
tt"echo Copying ramdisk... && "
tt"sf read 0x2000000 0x620000 ${ramdisk_size} && "
tt"bootm 0x3000000 0x2000000 0x2A000000"
t"sdboot=echo Copying Linux from SD to RAM... && "
tt"mmcinfo && "
tt"run mmc_loadbit_fat && "
tt"fatload mmc 0 0x3000000 ${kernel_image} && "
tt"fatload mmc 0 0x2A00000 ${devicetree_image} && "
tt"fatload mmc 0 0x2000000 ${ramdisk_image} && "
tt"bootm 0x3000000 0x2000000 0x2A000000"
t"nandboot=echo Copying Linux from NAND flash to RAM... && "
tt"nand read 0x3000000 0x100000 ${kernel_size} && "
tt"nand read 0x2A00000 0x600000 ${devicetree_size} && "
tt"echo Copying ramdisk... && "
tt"nand read 0x2000000 0x620000 ${ramdisk_size} && "
tt"bootm 0x3000000 0x2000000 0x2A000000"
t"jtagboot=echo TFTPing Linux to RAM... && "
tt"tftp 0x3000000 ${kernel_image} && "
tt"tftp 0x2A00000 ${devicetree_image} && "
tt"tftp 0x2000000 ${ramdisk_image} && "
tt"bootm 0x3000000 0x2000000 0x2A000000"

I apologize that these details have not been placed into a tutorial yet.  I plan to do this shortly or replace these MicroZed binaries with a newer release tag which can be supported longer (with tutorials also).

Regards,

-Kevin