What version of buildroot are you using or are you using OE? You most likely
need to update u-boot to version 1.2 and follow the new methodology for
flashing the uImage and rootfs images. In earlier buildroot versions that
targeted systems with u-boot 1.1.4 there was just one combined image created
that you needed to flash. Now with uboot 1.2 the flash has three partitions.
One for u-boot, one for the uImage (kernel) and one for rootfs. SO the
buildprocess now create 2 images for reflashing the device using a new two
step process. There is a lot more info in the archives, but I suspect this
is what you are running into.
Be careful when reflashing u-boot because improper procedure will brick
[mailto:gumstix-users-bounces@...] On Behalf Of sriram
Sent: Saturday, April 12, 2008 9:16 AM
To: gumstix-users-request@...; General mailing list for
Subject: [Gumstix-users] Problem in starting kernel on connex-400
With my tool chain, CPU is getting reset with any new compiled flash image.
It is having problem in starting kernel...
Where as if original one is loaded it works!!!!!!!
Where lies the problem ????
here is the data displayed ..........
U-Boot 1.1.4 (Nov 6 2006 - 11:20:03) - 400 MHz - 1161
*** Welcome to Gumstix ***
U-Boot code: A3F00000 -> A3F25DE4 BSS: -> A3F5AF00
Bank #0: a0000000 64 MB
Flash: 16 MB
Using default environment
Hit any key to stop autoboot: 0
Instruction Cache is ON
### JFFS2 loading 'boot/uImage' to 0xa2000000
Scanning JFFS2 FS: ..... done.
### JFFS2 load complete: 805120 bytes loaded to 0xa2000000
## Booting image at a2000000 ...
Image Name: uImage
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 805056 Bytes = 786.2 kB
Load Address: a0008000
Entry Point: a0008000
Starting kernel ...
pc : [<a000823c>] lr : [<a0008270>]
sp : a00d5cf8 ip : a00080bc fp : 00000001
r10: 10000000 r9 : 00000000 r8 : a0000100
r7 : 00000175 r6 : 69052d06 r5 : a0008000 r4 : 00008000
r3 : 00004000 r2 : 00008000 r1 : 00000c1e r0 : 00004004
Flags: Nzcv IRQs off FIQs off Mode SVC_32
Resetting CPU ...