[OpenWrt-Devel] Xilinx Zynq zedboard integration

Javier Domingo Cansino javierdo1 at gmail.com
Sun Jun 29 07:35:44 EDT 2014

​I have manually executed the boot sequence in the uboot, and the result is
that it fails on the command bootm loados. Any idea on how to debug what
can be wrong?

Cheers and I will keep searching,

Javier Domingo Cansino

zynq-uboot> fatload mmc 0 0x3000000 uImage
reading uImage
4582152 bytes read in 405 ms (10.8 MiB/s)
zynq-uboot> fatload mmc 0 0x2A00000 devicetree.dtb
reading devicetree.dtb
2739 bytes read in 15 ms (177.7 KiB/s)
zynq-uboot> fatload mmc 0 0x2000000 uramdisk.image.gz
reading uramdisk.image.gz
796339 bytes read in 87 ms (8.7 MiB/s)
zynq-uboot> help bootm
bootm - boot application image from memory

bootm [addr [arg ...]]
    - boot application image stored in memory
        passing arguments 'arg ...'; when booting a Linux kernel,
        'arg' can be the address of an initrd image
        When booting a Linux kernel which requires a flat device-tree
        a third argument is required which is the address of the
        device-tree blob. To boot that kernel without an initrd image,
        use a '-' for the second argument. If you do not pass a third
        a bd_info struct will be passed instead

For the new multi component uImage format (FIT) addresses
        must be extened to include component or configuration unit name:
        addr:<subimg_uname> - direct component image specification
        addr#<conf_uname>   - configuration specification
        Use iminfo command to get the list of existing component
        images and configurations.

Sub-commands to do part of the bootm sequence.  The sub-commands must be
issued in the order below (it's ok to not issue all sub-commands):
        start [addr [arg ...]]
        loados  - load OS image
        ramdisk - relocate initrd, set env initrd_start/initrd_end
        fdt     - relocate flat device tree
        cmdline - OS specific command line processing/setup
        bdt     - OS specific bd_t processing
        prep    - OS specific prep before relocation or go
        go      - start OS
zynq-uboot> bootm start 0x3000000 0x2000000 0x2A00000
## Booting kernel from Legacy Image at 03000000 ...
   Image Name:   ARM OpenWrt Linux-3.13.7
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4582088 Bytes = 4.4 MiB
   Load Address: 80000000
   Entry Point:  80000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
   Image Name:
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    796275 Bytes = 777.6 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02a00000
   Booting using the fdt blob at 0x2a00000
zynq-uboot> bootm loados
   Loading Kernel Image ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20140629/19b56713/attachment.htm>
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list