Sheevaplug installer - alpha-6 release - Testers needed

[joosty]

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

Couldn't the installer take care of this, just like when installing to NAND (when no manual untarring is necessary)?

I'm getting the impression that 'installation onto SD' actually means: just doing a regular install to NAND, and afterwards insert an SD card with a bootable filesystem, and reconfiguring uboot to boot onto SD.

Joost

[joosty]

From 'uboot-custom.txt':

Code:

# NAND flash partitions. If using kernel >= 2.6.30 then replace orion_nand with orion_mtd
mtdpartitions mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)

Doesn't the installer come with kernel 2.6.30? Then why does it use 'orion_nand' instead of 'orion_mtd' as the comments suggest?

[Rabeeh Khoury]

The original Marvell kernel uses one and the kernel.org kernel uses different.

[antonio]

Can someone post more detailed step-by-step instructions on how to setup the USB disk?  The README and the WIKI are incomplete and they do not reference actually decompressing the files in ./installer for example.

I'm trying to decompress rootfs.tar.gz and I'm getting errors like "Cannot change ownership to uid 0, gid 0" as well as some symbolic link errors.  I tried this as a regular user as well as root.

[Rabeeh Khoury]

you shouldn't be decomprissing the rootfs.tar.gz
just copy the content of the installer/ directory to the root directory of your USB HDD

Make sure your USB HDD has partitions.

[antonio]

Thank you - i was confused with some of the postings regarding untar'ing those files.

I moved everything from the /installer directory to the root directory of the USB drive.  I have a single 8GB FAT32 partition on the drive; I connected the drive to the sheevaplug, and executed runme.sh from my Ubuntu host machine and was able to start the process, but it's failing to load some files:

Code:

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage

** Unable to read "uImage" from usb 0:1 **
reading initrd

** Unable to read "initrd" from usb 0:1 **

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete. Cleanmarker written at 0x4e0000.
OK

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

Writing data at 0x4ff800 -- 100% complete.
 4194304 bytes written: OK
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30-rc6
   Created:      2009-05-20  11:42:10 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2595144 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
Marvell>>

[antonio]

The issue was related to USB incompatibility.  The 4th device I tried did the trick.

[fragfutter]

looks like the last batch of sheevaplugs changed vendor and product id. Modified scripts-linux/openocd/config/interface/sheevaplug.cfg to

interface ft2232
ft2232_layout sheevaplug
ft2232_vid_pid 0x0403 0x6010
#ft2232_vid_pid 0x9e88 0x9e8f
#ft2232_device_desc "SheevaPlug JTAGKey FT2232D B"
jtag_khz 2000

[pjratl]

ok trying to get things to boot and run from a SD card

I saw this and was a bit confused as to exactly what to do

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

so instead I followed the instructions on the wiki

Now copy your existing nand file system onto the sd card. The second cp of /dev is required because the first cp doesn't populate the new /dev directory. The first cp takes 10–15 minutes, so relax for a bit.

>cp -ax / /mnt/sdcard # takes 13 minutes
>cp -a /dev /mnt/sdcard

which seemed to work however apt-get isn't working correctly  at first it complained about missing files and directories which I created but now I am getting this

Code:

E: Couldn't configure pre-depend libc6 for findutils, probably a dependency cycle.

which clearly is bad

how exactly do I move the needed files to the sd drive?

And thanks again in advance!

[pjratl]

ok further testing reveals I get the error from the straightinstall without moving to SD

Code:

root@ubuntu:~# apt-get install nano
Reading package lists... Done
Building dependency tree... Done
The following extra packages will be installed:
  findutils gcc-4.3-base libc6 libgcc1 libgpm2 libncursesw5
Suggested packages:
  mlocate locate slocate locales glibc-doc gpm spell
The following NEW packages will be installed:
  findutils gcc-4.3-base libc6 libgcc1 libgpm2 libncursesw5 nano
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/5902kB of archives.
After this operation, 15.6MB of additional disk space will be used.
Do you want to continue [Y/n]?
E: Couldn't configure pre-depend libc6 for findutils, probably a dependency cycle.

in other words for me apt-get is broken with alpha 6

[pjratl]

Ok I have now determined that the files on the usb drive were corrupted I have recopied them to the drive. Is there a way from uboot to start the load process?

I am guessing bubt might do the trick. Can anyone help me here?

update

the correct answer is run recover1

I think I am whole again

[OmahaVike]

strange.  in order for me to boot off my SD card, i had to set my bootargs differently.  if i tried to use the aforementioned root=/dev/mmcblk0p1, the system would error and tell me that there are a few choices.

eventually, i had to use:

Code:

setenv bootargs_root root=b301

and now that i've rebooted, i'm not sure it actually worked.  (i wrote a file to the root directory and it's now showing up after rebooting -- i didn't saveenv but rather typed 'boot') anyone know how i can check to see if the FS is set for the SD card versus the internal flash?

thanks!

[fragfutter]

you can check what is mounted by typing

Code:

mount

in the booted linux system. Should show

Code:

/dev/mmcblk0p1 on / type ext3

.

most likely you have not mounted the sdcard.

to boot from the sdcard you need the init the mmc system in u-boot (this is most important after a full system reset. after a normal reboot the mmc stays initialized).

So booting goes like

mmcinit
load a kernel from somewhere (nand, tftp, sdcard, ...)
load an initrd from somewhere
define bootargs including the rootfs
run the loaded kernel

i can't say the exact commands out of my head but the wiki should tell.

[debio]

When I run runme.sh, I get this:

Code:

# ./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 $
2000 kHz
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 453:

 ****   openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

The Sheevaplug is connected and I can connect to the Linux host on /dev/ttyUSB1. Rebooting the plug made no difference. The kernel logs show this:

Code:

Aug  5 16:50:45 Reno kernel: usb 4-2: new full speed USB device using ohci_hcd and address 7                 
Aug  5 16:50:45 Reno kernel: usb 4-2: configuration #1 chosen from 1 choice                                 
Aug  5 16:50:45 Reno kernel: ftdi_sio 4-2:1.0: FTDI USB Serial Device converter detected                     
Aug  5 16:50:45 Reno kernel: usb 4-2: Detected FT2232C                                                       
Aug  5 16:50:45 Reno kernel: usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB0               
Aug  5 16:50:45 Reno kernel: ftdi_sio 4-2:1.1: FTDI USB Serial Device converter detected                     
Aug  5 16:50:45 Reno kernel: usb 4-2: Detected FT2232C                                                       
Aug  5 16:50:45 Reno kernel: usb 4-2: FTDI USB Serial Device converter now attached to ttyUSB1

Should I try recompiling OpenOCD on my non-ARM linux box?
It looks like I have libftdi and not libftdi2xx, would that cause problems? OpenOCD didn't have any errors about dynamic library loading...
Actually, could Bad Things (TM) be happening because I'm running this on 64 bit Linux? I'll try it on a 32 bit system...
On the 32 bit system, openocd segfaulted almost instantly. Ergh, I guess I'll try recompiling it.

Okay, it looks like it's working from my 64 bit box with fragfutter's modifications to interface.cfg.

[fragfutter]

see a few posts up. openocd does not find the plug because the usb identifier changed.

edit: user found it himself