> gai boger <bebe...@hotmail.com> writes:
> > It seems that the partition name "Kernel" in the nand no longer
> > exists. Using dfu-util, it doesn't recognize the name, and when I
> > use dfu-util -a 3 then it says it writes to an "UNDEFINED"
> > partition, and at the u-boot it says that I'm writing to the
> > "rootfs" partition.
>
> Have you read http://docs.openmoko.org/trac/ticket//2348 ?
I read it and that doesn't seem to be the problem nor the solution.
> Can you still boot the system in nand? If yes, check dmesg output for 2
> things:
>
> The kernel commandline should look similar to this:
>
> [ 0.000000] Kernel command line: rootfstype=jffs2
> root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=4
> regular_boot
> mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000>
> > (rootfs)
>
> And somewhat later:
>
> [ 1.300000] 6 cmdlinepart partitions found on MTD device neo1973-nand
> [ 1.305000] Creating 6 MTD partitions on "neo1973-nand":
> [ 1.305000] 0x000000000000-0x000000040000 : "u-boot"
> [ 1.305000] 0x000000040000-0x000000080000 : "u-boot_env"
> [ 1.305000] 0x000000080000-0x000000880000 : "kernel"
> [ 1.310000] 0x000000880000-0x000000920000 : "splash"
> [ 1.315000] 0x000000920000-0x000000960000 : "factory"
> [ 1.315000] 0x000000960000-0x000010000000 : "rootfs"
>
> Maybe you u-boot environment is damaged?
The dmesg output does appear when I'm using the SHR-unstable.
It seems that the problem is apparent only with the NOR u-boot and I've tried
several ways and I can't flash a new kernel to the NAND.
Forgive me if I hadn't done my homework and looked throughly through the wiki
pages but is there a way to flash a new kernel to the NAND through a
distribution working on the SD card?
_______________________________________________
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
