booting uImage for mx35 3stack

Marc Reilly marc at cpdesign.com.au
Thu Apr 15 00:04:16 EDT 2010


Hi Sascha,

Thanks for all your help, and speedy responses.

> > Nothing happens after "done, booting the kernel" (boot snippet at end
> > of
> > email)
> 
> Newer kernels have earlyprintk support that could be of help here.
> Please apply commit-id 93fd03a8c6728b58879f8af20ffd55d9c32a778b to your
> kernel and add 'earlyprintk' to your kernel command line.

Great tip. It shows the kernel is starting ok and getting stuck just after
irqs are enabled. 
I'm still a bit baffled as to why this only happens with barebox.

Uncompressing
Linux.......................................................................
......
........................................................................
done, booting the kerne
l.

[    0.000000] Linux version 2.6.31-00443-g587ea71-dirty (marc at susedev1)
(gcc version 4.3.3 (GCC
) ) #5 PREEMPT Thu Apr 15 13:45:48 EST 2010

[    0.000000] CPU: ARMv6-compatible processor [4117b363] revision 3
(ARMv6TEJ), cr=00c5387f    
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing
instruction cache             
[    0.000000] Machine: Freescale MX35 3-Stack Board

[    0.000000] Memory policy: ECC disabled, Data cache writeback

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total
pages: 32512       
[    0.000000] Kernel command line: earlyprintk=serial,ttymxc0,115200

[    0.000000] console [earlycon0] enabled

[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)

[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536
bytes)                   
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

[    0.000000] Memory: 128MB = 128MB total

[    0.000000] Memory: 124804KB available (4240K code, 490K data, 128K init,
0K highmem)        
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1          
[    0.000000] NR_IRQS:256

[    0.000000] irq.c: MXC IRQ initialized

 

Then nothing...

I'm thinking maybe some pin/input is initialized wrong and causing infinite
interrupts.
.. but I think I'm clutching at straws. Again, any more hints greatly
appreciated!

> Do you have MMU enabled? If yes you could try disabling it
No MMU enabled

Cheers,
Marc




More information about the barebox mailing list