<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">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?</div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Cheers and I will keep searching,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
<br clear="all" style="font-family:arial"><div style="font-family:arial">Javier Domingo Cansino</div></div><div class="gmail_default" style><div class="gmail_default" style><font face="arial, helvetica, sans-serif"><br></font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">zynq-uboot> fatload mmc 0 0x3000000 uImage</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">reading uImage</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">4582152 bytes read in 405 ms (10.8 MiB/s)</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">zynq-uboot> fatload mmc 0 0x2A00000 devicetree.dtb</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">reading devicetree.dtb</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">2739 bytes read in 15 ms (177.7 KiB/s)</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">zynq-uboot> fatload mmc 0 0x2000000 uramdisk.image.gz</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">reading uramdisk.image.gz</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">796339 bytes read in 87 ms (8.7 MiB/s)</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">zynq-uboot> help bootm</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">bootm - boot application image from memory</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"><br></font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">Usage:</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">bootm [addr [arg ...]]</font></div><div class="gmail_default" style>
<font face="arial, helvetica, sans-serif"> - boot application image stored in memory</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> passing arguments 'arg ...'; when booting a Linux kernel,</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> 'arg' can be the address of an initrd image</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> When booting a Linux kernel which requires a flat device-tree</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> a third argument is required which is the address of the</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> device-tree blob. To boot that kernel without an initrd image,</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> use a '-' for the second argument. If you do not pass a third</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> a bd_info struct will be passed instead</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"><br></font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">For the new multi component uImage format (FIT) addresses</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> must be extened to include component or configuration unit name:</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> addr:<subimg_uname> - direct component image specification</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> addr#<conf_uname> - configuration specification</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Use iminfo command to get the list of existing component</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> images and configurations.</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"><br></font></div><div class="gmail_default" style>
<font face="arial, helvetica, sans-serif">Sub-commands to do part of the bootm sequence. The sub-commands must be</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">issued in the order below (it's ok to not issue all sub-commands):</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> start [addr [arg ...]]</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> loados - load OS image</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> ramdisk - relocate initrd, set env initrd_start/initrd_end</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> fdt - relocate flat device tree</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> cmdline - OS specific command line processing/setup</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> bdt - OS specific bd_t processing</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> prep - OS specific prep before relocation or go</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> go - start OS</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">zynq-uboot> bootm start 0x3000000 0x2000000 0x2A00000</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">## Booting kernel from Legacy Image at 03000000 ...</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Image Name: ARM OpenWrt Linux-3.13.7</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Image Type: ARM Linux Kernel Image (uncompressed)</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Data Size: 4582088 Bytes = 4.4 MiB</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Load Address: 80000000</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Entry Point: 80000000</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Verifying Checksum ... OK</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif">## Loading init Ramdisk from Legacy Image at 02000000 ...</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Image Name:</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Image Type: ARM Linux RAMDisk Image (uncompressed)</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Data Size: 796275 Bytes = 777.6 KiB</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Load Address: 00000000</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Entry Point: 00000000</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Verifying Checksum ... OK</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">## Flattened Device Tree blob at 02a00000</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Booting using the fdt blob at 0x2a00000</font></div><div class="gmail_default" style><font face="arial, helvetica, sans-serif">zynq-uboot> bootm loados</font></div>
<div class="gmail_default" style><font face="arial, helvetica, sans-serif"> Loading Kernel Image ...</font></div></div></div>