booting uImage for mx35 3stack

booting uImage for mx35 3stack

[Marc Reilly]

[-- Attachment #1.1: Type: text/plain, Size: 1513 bytes --]

Hi All,

 

I'm not having much luck booting a kernel on the mx35 3stack!

Nothing happens after "done, booting the kernel" (boot snippet at end of
email)

Barebox and the kernel are in the NOR flash.

 

I've successfully booted the exact uImage using u-boot v1, so I'm fairly
confident it's OK.

 

Any suggestions of what could be wrong?

The machine arch # is correct. The tagged list looks correct (gdb mem dump
just before calling theKernel()).

 

Guessing something is not being inited as required. Or I've done something
silly.

 

I assume other people have booted successfully on this board. (Any known
working kernel images would be great to test against!)

 

Hints greatly appreciated.

 

Cheers,

Marc

 

---boot log, as far as it gets:

 

barebox:/ boot


   Verifying Checksum ... OK


   Image Name:   Angstrom/2.6.31/mx35pdk


   Created:      2010-04-14   0:24:42 UTC


   Data Size:    2216628 Bytes =  2.1 MB


   Load Address: 80008000


   Entry Point:  80008000


OK


commandline: console=ttymxc0,115200 video=mx3fb:CTP-CLAA070LC0ACW ip=::::::
root

=/dev/mtdblock7 rootfstype=jffs2
mtdparts=\"physmap-flash.0:256k(barebox)ro,512k

(bareboxenv),3M(kernel),-(root);mxc_nand:256k(barebox)ro,512k(bareboxenv),2M
(ker

nel),-(root)\"


arch_number: 1645


 


Starting kernel ...


 


Uncompressing
Linux.............................................................

............................................................................
....

..... done, booting the kernel.    


[-- Attachment #1.2: Type: text/html, Size: 11033 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: booting uImage for mx35 3stack

[Sascha Hauer]

Hi Marc,

On Wed, Apr 14, 2010 at 06:19:49PM +1000, Marc Reilly wrote:
> Hi All,
> 
>  
> 
> I'm not having much luck booting a kernel on the mx35 3stack!
> 
> 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.

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

Sascha



-- 
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 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

RE: booting uImage for mx35 3stack

[Marc Reilly]

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@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


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: booting uImage for mx35 3stack

['Sascha Hauer']

On Thu, Apr 15, 2010 at 02:04:16PM +1000, Marc Reilly wrote:
> 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.

Sounds somewhat familiar. I have just tested 2.6.31 and
2.6.34-rc-something on my board, both working fine.
Maybe this has something to do with the clocks. You could check the
register values of the CCM module in barebox and U-Boot
(md 0x53f80000+0x80).

Also note this mail:

http://lists.infradead.org/pipermail/linux-arm-kernel/2010-April/012691.html

I suspect a bug in the kernel there which is still present.

Sascha


-- 
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 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox