uImage doesn't boot
s.hauer at pengutronix.de
Thu Aug 22 02:46:40 EDT 2013
On Wed, Aug 21, 2013 at 02:30:17PM +0200, Vanhauwaert Wouter wrote:
> Before, I was working with Barebox 2013.05, which worked fine. Now I updated my sources to barebox 2013.07, but my kernel doesn't boot anymore. Barebox itself works as expected. When I do:
> bootm -v /mnt/tftp/uImage
> Image Name: Linux-18.104.22.168-01169-gbc81590-di
> Created: 2013-06-03 13:29:30 UTC
> OS: Linux
> Architecture: ARM
> Type: Kernel Image
> Compression: uncompressed
> Data Size: 2834488 Bytes = 2.7 MiB
> Load Address: 70008000
> Entry Point: 70008000
> Loading OS U-Boot uImage '/mnt/tftp/uImage'
> OS image is at 0x70008000-0x702bc037
> Passing control to ARM Linux uImage handler
> Starting kernel at 0x70008000...
> commandline: console=ttymxc4,115200 mtdparts=mxc_nand:3M(nand0.systemkernel),-(nand0.root);m25p0:384k(m25p0.barebox)ro,128k(m25p0.bareboxenv),3M(m25p0.recoverykernel)ro,512k(m25p0.storage)
> arch_number: 3297
Your arch_number suggests you are working on a Garz & Fricke Vincell
board. Is this correct?
> And that's it, it doesn't do anything after it. Althought this works
> with the previous barebox. What can cause this?
I have no quick idea. What you can always do is bisecting the problem,
but what I would do before is enabling earlyprintk in the kernel and
passing 'earlyprintk' to the kernel commandline. Often this gives a good
hint what's wrong.
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox