On 2012-09-27 07:55, Khem Raj wrote:
On Thu, Sep 27, 2012 at 6:47 AM, <[email protected]> wrote:
Hi,
as I wrote before, I have an older version. I used the kernel version of that
one to start up my new meta-ivi build. It crashed later with a kernel panic,
but at least the kernel is running.
After that I compared the two kernel version I have, with mkimage -l.
1. Kernel version that is working quite well:
mkimage -l uImage
Image Name: Linux-3.1.0
Created: Fri Sep 21 11:25:32 2012
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4144744 Bytes = 4047.60 kB = 3.95 MB
Load Address: 80008000
Entry Point: 80008000
2. Kernel version that fails after uncompression:
mkimage -l uImage
Image Name: Linux-3.1.0
Created: Thu Sep 27 07:07:25 2012
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4176432 Bytes = 4078.55 kB = 3.98 MB
Load Address: 80008000
Entry Point: 80008000
I don't see any major issues here, so I guess I need to check the toolchain as
proposed by Enrico.
Download denzil SDK for arm which is gcc 4.6 based and compile kernel
using that and see if that boots. There could be some kernel+toolchain
interaction w.r.t gcc 4.7 which is what is
default in current master/(would be 1.3) release, sometimes gcc
exposes latent bugs in kernel
and at times its wise versa
I've tried this kernel on a PandaBoard, built with both GCC-4.7.2 (latest
master)
and GCC-4.6.3 (~denzil). Both fail during to come up.
The next step would be to diagnose this with a JTAG. Sadly, I've not been able
to get my XDS100v2 to work with the PandaBoard yet, so it'll have to be someone
else to carry this torch.
Christian
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im Auftrag von Enrico
Gesendet: Donnerstag, 27. September 2012 14:07
An: Schulenberg Christian, EI-42
Cc: [email protected]
Betreff: Re: [meta-ti] pandaboard not booting
On Thu, Sep 27, 2012 at 1:16 PM, <[email protected]> wrote:
I'm using the same kernel version as I did before. It's the default kernel 3.1
as configured in the meta-ti layer: ti-ubuntu-3.1.0-1282.11, Revision:
a5c60c099296fcfc0c8fa8085c40883971486512
Do you really think it makes sense to switch to a more recent one?
No, but i have no better ideas right now...
You could check if it's a known toolchain bug with that kernel, but i
think it would be faster to try a newer kernel (from the same
repository, ti ubuntu integration).
Enrico
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti
