U-boot Bricking My C3000, Trying to follow the 2.6.23.1 yonggun with uboot on the wiki Options

[Chadarius]

I'm following the 2.6.23.1 yonggun with uboot guide on the wiki.

The process for installing uboot always results in a bricking my c3000. After the uboot procedure, the orange charging light does not even go on. I have to restore the Sharp nand at that point. It does seem to boot on the local disk to a text prompt before I attempt to flash to the uboot update. I can login as root there, so the previous steps in that doc seem to be working.

I've reformatted the SD card to just a 128mb fat16 partition and used that for the uboot procedure. I had read that it was best to do that for the Sharp ROM to be able to read it properly.

Anyone else having issues with uboot like this? If so, what can I do to get around it?

[flux]

I'm not sure at all... but iirc, jpmatrix told me that u-boot on c3000 -> between difficult and impossible, due to lack of rom memory (only 16 Mo, not 128 like on c1000, c3100 and c3200). maybe you should try an install without u-boot ?
hope someone will confirm or infirm what i just told.

[jpmatrix]

I'm not sure at all... but iirc, jpmatrix told me that u-boot on c3000 -> between difficult and impossible, due to lack of rom memory (only 16 Mo, not 128 like on c1000, c3100 and c3200). maybe you should try an install without u-boot ?
hope someone will confirm or infirm what i just told.

i confirm that it doesn't work on my C3000
why did you want to install it ?
to install eabi just flash the 2.6.23 kernel of angstrom and untar the rootfs to the hdd

[svs57]

16Mb of NAND is enough for u-boot + emergency kernel and initrd + 2.6.x kernel
The problem is in NAND partition.
There are 3 default NAND partition:
First - System Area - 7Mb
Second - Root Filesystem - size is depend of model:
poodle - 22Mb
shepherd - 25Mb
husky - 53Mb
spitz - 5Mb
akita 58Mb
borzoi 32Mb
Third - Home - rest of NAND
First partition (7Mb) contains u-boot, emergency kernel, emergency initrd.
Rest of 1-st part. is 0x160000 was enough for kernel <=2.6.22.x
Kernel >=2.6.23 is bigger.
I change NAND partition sizes in drivers/mtd/nand/sharpsl.c
Then made relative changes in u-boot.
Now I can flash and use kernel 2.6.23
But kernel 2.6.23 has some bugs with timer and PM.
I have patch only solved timer bug

[jpmatrix]

16Mb of NAND is enough for u-boot + emergency kernel and initrd + 2.6.x kernel
The problem is in NAND partition.
There are 3 default NAND partition:
First - System Area - 7Mb
Second - Root Filesystem - size is depend of model:
poodle - 22Mb
shepherd - 25Mb
husky - 53Mb
spitz - 5Mb
akita 58Mb
borzoi 32Mb
Third - Home - rest of NAND
First partition (7Mb) contains u-boot, emergency kernel, emergency initrd.
Rest of 1-st part. is 0x160000 was enough for kernel <=2.6.22.x
Kernel >=2.6.23 is bigger.
I change NAND partition sizes in drivers/mtd/nand/sharpsl.c
Then made relative changes in u-boot.
Now I can flash and use kernel 2.6.23
But kernel 2.6.23 has some bugs with timer and PM.
I have patch only solved timer bug

thanks for your explanations ! i guessed you have a C3000 too ?
so to be when you flash the kernel on the C3000 with the ON-OK procedure, do that touch the partition sizes too or do that touch one system area ? are this partition settings in the updater.sh file ?
on my c3000 i can flash the first 2.6.23 kernel of angstrom but not the 2nd version they made...
which bugs are you talking about 2.6.23 timer and PM ? are they present in angstrom 2.6.23 one ? i didn't remark anything...

[svs57]

16Mb of NAND is enough for u-boot + emergency kernel and initrd + 2.6.x kernel
The problem is in NAND partition.
There are 3 default NAND partition:
First - System Area - 7Mb
Second - Root Filesystem - size is depend of model:
poodle - 22Mb
shepherd - 25Mb
husky - 53Mb
spitz - 5Mb
akita 58Mb
borzoi 32Mb
Third - Home - rest of NAND
First partition (7Mb) contains u-boot, emergency kernel, emergency initrd.
Rest of 1-st part. is 0x160000 was enough for kernel <=2.6.22.x
Kernel >=2.6.23 is bigger.
I change NAND partition sizes in drivers/mtd/nand/sharpsl.c
Then made relative changes in u-boot.
Now I can flash and use kernel 2.6.23
But kernel 2.6.23 has some bugs with timer and PM.
I have patch only solved timer bug

thanks for your explanations ! i guessed you have a C3000 too ?
so to be when you flash the kernel on the C3000 with the ON-OK procedure, do that touch the partition sizes too or do that touch one system area ? are this partition settings in the updater.sh file ?
on my c3000 i can flash the first 2.6.23 kernel of angstrom but not the 2nd version they made...
which bugs are you talking about 2.6.23 timer and PM ? are they present in angstrom 2.6.23 one ? i didn't remark anything...

I have only c750 and thinking about Nokia N810
You can change partitions size either by recompiling mtd/nand/sharpsl.c module
or adding bootarg:
mtdparts=sharpsl-nand:10240k@0k(smf),55296k@10240k(root),-(home)
(54Mb root for my shepherd)
I forget mention about once more bug in 2.6.23
It doesn't pass CONFIG_CMDLINE to kernel!
I made changes in u-boot to pass correct bootargs

http://bugzilla.kernel.org/show_bug.cgi?id=9229
http://bugzilla.kernel.org/show_bug.cgi?id=9217
http://bugzilla.kernel.org/show_bug.cgi?id=9275

[svs57]

about flashing
I flash kernel 2.6.23 from 2.6.22.9 with new NAND partitions
Not using emergency kernel (pressing OK while boot)