[FS#139] kirkwood uimages for specific devices built by from source can only be booted with bootz
LEDE Bugs
lede-bugs at lists.infradead.org
Fri Sep 2 11:11:15 PDT 2016
A new Flyspray task has been opened. Details are below.
User who did this - bobafetthotmail (bobafetthotmail)
Attached to Project - LEDE Project
Summary - kirkwood uimages for specific devices built by from source can only be booted with bootz
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - High
Priority - Very Low
Reported Version - Trunk
Due in Version - Undecided
Due Date - Undecided
Details - This is true for all kirkwood uimages built by the LEDE system.
Both stock uboot and modern uboot act the same
NSA310> fatload usb 0 0x800000 lede-kirkwood-nsa310-uimage ; bootm 0x800000
reading lede-kirkwood-nsa310-uimage
1868588 bytes read in 83 ms (21.5 MiB/s)
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
but with bootz works
NSA310> bootz 0x800000
Kernel image @ 0x800000 [ 0x000000 - 0x1c51d8 ]
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.4.19 (alby at openSUSE-xeon) (gcc version 5.4.0 (LEDE GCC 5.4.0 r1480) ) #0 Thu Sep 1 13:01:04 2016
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: ZyXEL NSA310
[ 0.000000] Memory policy: Data cache writeback
## and it goes on and on here, not relevant for the bug report
I suspect that this is related to bug 131 https://bugs.lede-project.org/index.php?do=details&task_id=131
More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=139
More information about the lede-bugs
mailing list