On Thu, Sep 27, 2012 at 9:08 AM, Gary Thomas <[email protected]> wrote: > 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.
OK you can take further step back and use edison SDK which has gcc 4.5 which then can _kind_ of eliminate the compiler if it fails with all 3 _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
