Becky Olson
2017-02-27 23:12:16 UTC
I have an old overo gumstix with a tobi board. We have 3 of these
boards which I would like to upgrade.
(ie ->)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 MHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
It only has the 256MiB nand. I have tried flashing the nand countless
times in different ways but I cannot get it to boot. It will boot from
my mmc card. It boots using DTS from mmc
The latest attempt gives the below:
U-Boot SPL 2014.10 (Apr 26 2015 - 19:49:36)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
U-Boot 2014.10 (Apr 26 2015 - 19:49:36)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 MHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
Board revision: 0
Tranceiver detected on mmc2
No EEPROM on expansion board
Die ID #132a00240000000004038e710100c01f
Net: smc911x-0
Warning: smc911x-0 using MAC address from net device
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
Booting from nand ...
NAND read: device 0 offset 0x280000, size 0x800000
8388608 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Booting from nand with DTS...
UBI: attaching mtd1 to ubi0
Error reading superblock on volume 'ubi0:rootfs' errno=-19!
ubifsmount - mount UBIFS volume
Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
Kernel image @ 0x82000000 [ 0x000000 - 0x48f520 ]
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
My flashing consists of the following commands:
I was hoping adding the zImage and the dtb board would help but it did
not. I also just used the standard ubi image which you can download. Iâm
trying to move it to yocto 1.7.2 . Should I back up the MLO and
u-boot.img? Or what can I do to get the nand to flash and boot. I have
also tried using ubiformat and that gives me a kernel sync error when
it is formatting.
My commands:
Overo # nand erase.chip
NAND erase.chip: device 0 whole chip
Erasing at 0xffe0000 -- 100% complete.
OK
Overo # fatload mmc 0 $loadaddr MLO
reading MLO
57396 bytes read in 8 ms (6.8 MiB/s)
Overo # nandecc hw
Overo # nand write $loadaddr 0 20000
NAND write: device 0 offset 0x0, size 0x20000
131072 bytes written: OK
Overo # nand write $loadaddr 20000 20000
NAND write: device 0 offset 0x20000, size 0x20000
131072 bytes written: OK
Overo # nand write $loadaddr 40000 20000
NAND write: device 0 offset 0x40000, size 0x20000
131072 bytes written: OK
Overo # nand write $loadaddr 60000 20000
NAND write: device 0 offset 0x60000, size 0x20000
131072 bytes written: OK
Overo # fatload mmc 0 $loadaddr u-boot.img
reading u-boot.img
397108 bytes read in 33 ms (11.5 MiB/s)
Overo # nandecc sw bch8
Overo # nand write $loadaddr u-boot $filesize
NAND write: device 0 offset 0x80000, size 0x60f34
397108 bytes written: OK
Overo # load mmc 0:2 $loadaddr /boot/zImage
4781344 bytes read in 398 ms (11.5 MiB/s)
Overo # nand write $loadaddr linux $filesize
NAND write: device 0 offset 0x280000, size 0x48f520
4781344 bytes written: OK
Overo # load mmc 0:2 ${fdtaddr} /boot/omap3-overo-storm-tobi.dtb
65848 bytes read in 46 ms (1.4 MiB/s)
Overo # nand write ${fdtaddr} 0x800000 $filesize
NAND write: device 0 offset 0x800000, size 0x10138
65848 bytes written: OK
Overo # ext2load 0:2 $loadaddr /gumstix-console-image-uvb.ubi
** Bad device 0:2 0x82000000 **
Overo # ext2load mmc 0:2 $loadaddr /gumstix-console-image-uvb.ubi
186646528 bytes read in 13594 ms (13.1 MiB/s)
Overo # nand write $loadaddr rootfs $filesize
NAND write: device 0 offset 0xa80000, size 0xb200000
186646528 bytes written: OK
Any ideas what I can do to get it to work?
Thanks,
Becky
boards which I would like to upgrade.
(ie ->)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 MHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
It only has the 256MiB nand. I have tried flashing the nand countless
times in different ways but I cannot get it to boot. It will boot from
my mmc card. It boots using DTS from mmc
The latest attempt gives the below:
U-Boot SPL 2014.10 (Apr 26 2015 - 19:49:36)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
U-Boot 2014.10 (Apr 26 2015 - 19:49:36)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 MHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
Board revision: 0
Tranceiver detected on mmc2
No EEPROM on expansion board
Die ID #132a00240000000004038e710100c01f
Net: smc911x-0
Warning: smc911x-0 using MAC address from net device
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
Booting from nand ...
NAND read: device 0 offset 0x280000, size 0x800000
8388608 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Booting from nand with DTS...
UBI: attaching mtd1 to ubi0
Error reading superblock on volume 'ubi0:rootfs' errno=-19!
ubifsmount - mount UBIFS volume
Usage:
ubifsmount <volume-name>
- mount 'volume-name' volume
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
UBIFS not mounted, use ubifs mount to mount volume first!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
Kernel image @ 0x82000000 [ 0x000000 - 0x48f520 ]
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
My flashing consists of the following commands:
I was hoping adding the zImage and the dtb board would help but it did
not. I also just used the standard ubi image which you can download. Iâm
trying to move it to yocto 1.7.2 . Should I back up the MLO and
u-boot.img? Or what can I do to get the nand to flash and boot. I have
also tried using ubiformat and that gives me a kernel sync error when
it is formatting.
My commands:
Overo # nand erase.chip
NAND erase.chip: device 0 whole chip
Erasing at 0xffe0000 -- 100% complete.
OK
Overo # fatload mmc 0 $loadaddr MLO
reading MLO
57396 bytes read in 8 ms (6.8 MiB/s)
Overo # nandecc hw
Overo # nand write $loadaddr 0 20000
NAND write: device 0 offset 0x0, size 0x20000
131072 bytes written: OK
Overo # nand write $loadaddr 20000 20000
NAND write: device 0 offset 0x20000, size 0x20000
131072 bytes written: OK
Overo # nand write $loadaddr 40000 20000
NAND write: device 0 offset 0x40000, size 0x20000
131072 bytes written: OK
Overo # nand write $loadaddr 60000 20000
NAND write: device 0 offset 0x60000, size 0x20000
131072 bytes written: OK
Overo # fatload mmc 0 $loadaddr u-boot.img
reading u-boot.img
397108 bytes read in 33 ms (11.5 MiB/s)
Overo # nandecc sw bch8
Overo # nand write $loadaddr u-boot $filesize
NAND write: device 0 offset 0x80000, size 0x60f34
397108 bytes written: OK
Overo # load mmc 0:2 $loadaddr /boot/zImage
4781344 bytes read in 398 ms (11.5 MiB/s)
Overo # nand write $loadaddr linux $filesize
NAND write: device 0 offset 0x280000, size 0x48f520
4781344 bytes written: OK
Overo # load mmc 0:2 ${fdtaddr} /boot/omap3-overo-storm-tobi.dtb
65848 bytes read in 46 ms (1.4 MiB/s)
Overo # nand write ${fdtaddr} 0x800000 $filesize
NAND write: device 0 offset 0x800000, size 0x10138
65848 bytes written: OK
Overo # ext2load 0:2 $loadaddr /gumstix-console-image-uvb.ubi
** Bad device 0:2 0x82000000 **
Overo # ext2load mmc 0:2 $loadaddr /gumstix-console-image-uvb.ubi
186646528 bytes read in 13594 ms (13.1 MiB/s)
Overo # nand write $loadaddr rootfs $filesize
NAND write: device 0 offset 0xa80000, size 0xb200000
186646528 bytes written: OK
Any ideas what I can do to get it to work?
Thanks,
Becky