Sheevaplug installer - alpha-6 release - Testers needed

[Rabeeh Khoury]

well, i don't think that it's your mistake since Windows and Linux do support bare FAT filesystem on the volume, unpartitioned.

I just fixed u-boot to support that; i'll send that to Marvell engineers for review and integration part of u-boot release.

[docbee]

Is there a way to set environment variables for u-boot without having these erased before?
Background of my question is, that I would like to preserve the MAC of the plug.

[Rabeeh Khoury]

You can edit the uboot-custom.txt file and change the MAC address accordingly.

Actually this is required in order to preserve the MAC address allocated to the unit

[sevi4310]

it doesn't work for me.
Any help would be appreciated.

<code>root@stockalerts:/tmp/installer/sheevaplug-installer-alpha-6# sudo ./runme.sh
 ****   Preparing environment variables file ...
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
3000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 17.862015s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
Warn : invalid block: 2
Error: erase operation didn't pass, status: 0xe1
erase failed
Error: timed out while waiting for target halted
Error: error executing hosted NAND write
Warn : target not halted
Warn : target reentered debug state, but not at the desired exit point: 0x7fffff0
Error: error executing hosted NAND write
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Error: error executing hosted NAND write
Warn : target not halted
Warn : target was in unknown state when halt was requested
Warn : DBGACK set while target was in unknown state. Reset or initialize target.
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x1000005c
MMU: disabled, D-Cache: disabled, I-Cache: disabled
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Error: error executing hosted NAND write
Warn : target not halted
Warn : target was in unknown state when halt was requested
Warn : DBGACK set while target was in unknown state. Reset or initialize target.
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x1000005c
MMU: disabled, D-Cache: disabled, I-Cache: disabled
Warn : target reentered debug state, but not at the desired exit point: 0x0010
Error: error executing hosted NAND write
Warn : target reentered debug state, but not at the desired exit point: 0x10000014
Error: error executing hosted NAND write
Error: timed out while waiting for target halted
Error: error executing hosted NAND write
Warn : target not halted
Error: timed out while waiting for target halted
Error: error executing hosted NAND write
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Warn : target not halted
Error: invalid mode value encountered
Error: cpsr contains invalid mode value - communication failure
Error: error executing hosted NAND write
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Error: NAND flash access requires halted target
Warn : target not halted
Warn : target was in unknown state when halt was requested
Warn : DBGACK set while target was in unknown state. Reset or initialize target.
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x600000d3 pc: 0x1000005c
MMU: disabled, D-Cache: disabled, I-Cache: disabled
wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 66.784401s
 ****   U-boot should be up and running now. Open your console ...
root@stockalerts:/tmp/installer/sheevaplug-installer-alpha-6#</code>

[Rabeeh Khoury]

how many times did you try the process?

Looks like uboot env variables were wrote ok; but u-boot itself wasn't because jtag wasn't able to halt the processor.

[sevi4310]

Does anyone knows how to fix Bad Magic Number
Installer worked good but booting gave me some errors.

Code:

512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
Bad Magic Number

[Rabeeh Khoury]

Refer to this -

http://plugcomputer.org/plugforum/index.php?topic=489.msg2890#msg2890

Please don't double post.

[christoph]

Flashing my plug with the stock installer 6 fails with «no space left on device» -> full log

Any help is welcome

[Rabeeh Khoury]

Strange.

Can you please press enter on the -

Code:

*****************************************************************

**** PRESS ENTER TO STOP THE COUNT DOWN
**** Will flash tarball from USB disk to internal NAND /dev/mtdblock1
**** This will wipe out EVERYTHING on the internal NAND flash
**** Will wait 10 seconds before the flash.

and then

Code:

cat /proc/mtd

[christoph]

Done so, the output is at http://random.christoph-egger.org/plug-cat-proc-mtd

[Rabeeh Khoury]

somehow the NAND partitions is not correct.
you have 1MB for U-boot, 4MB for kernel and the rest for rootfs; but when booting the kernel with sheevaplug installer the first partition for u-boot is not expoerted.

This leaves you to /dev/mtd0 - 4MB and /dev/mtd1 - 507MB for rootfs.

Now the problem in your case is that u-boot partition wasn't hidden, so /dev/mtd0 is 1MB, /dev/mtd1 is 4MB and /dev/mtd2 is 507MB.

The installer tries (by default) to untar the rootfs on /dev/mtd1, which is 4MB in your case instead of 507MB.

Did you use the installer as-is? or you did some modifications?

[christoph]

This is the installer as-is. I was first trying some other rootfs but switched back to a plainly extracted installer as there were troubles

[joosty]

For booting from SD you need to modify bootargs_root from the NAND thing (UBIFS etc...) to much more simpler -

Code:

bootargs_root root=/dev/mmcblk0p1

Which means boot from first partition (p1).

Note that you must make sure that the root filesystem type in the command (ubifs) is removed.

So, if I want to install to and boot from SD instead of NAND. I only have to change 'uboot_custom.txt':

Code:

bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs

into

Code:

bootargs_root root=/dev/mmcblk0p1

Is this correct? Any pre-formatting of the SD needed?

And can I incorporate the newest kernel (http://sheeva.with-linux.com/sheeva/index.php?dir=2.6.30.1) by just replacing 'uImage' and 'modules.tar.gz' in the 'installer' dir?

Joost

[Rabeeh Khoury]

Yes. And you need to untar the rootfs.tar.gz on the SD card with the relevant modules.tar.gz

[Rabeeh Khoury]

I just wanted to share some info on mini USB cable.

I used a 1.5Meter mini USB cable and I wasn't able even once to run the installer without having problems, indicated by timeouts and all sort of nasty things on openocd error messages.

I then changed the cable to shorter cable, which looked more shielded and worked first time.

Just some info.