• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 ... 5 6 [7] 8 9 ... 16
Author Topic: Sheevaplug installer - version 1.0  (Read 99902 times)
rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #90 on: October 16, 2009, 01:25:40 PM »

Have you tried replacing the USB cable, some people complained that the mini USB that came with the plug metal is thin and might not be plugged in all the way.
Logged

raydog153
Newbie
*

Karma: 0
Posts: 3


View Profile
« Reply #91 on: October 16, 2009, 01:31:07 PM »

Hello,

It seems I'm having problems with the Installer 1.0 that have already been reported but, after trying quite a few solutions I've read here, I'm still stuck.  I damaged my plug trying to move the boot from flash to SD.  I can still get the Marvell>> prompt but when it tries to boot (Linux) then I get the Bad Magic Number 00800000  I've tried the installer on both XP and Ubuntu 9.04 with no luck.  I have only a basic knowledge of Linux but it seems as if the USB stick (I've tried several with FAT32 and EXT2/3) in the plug isn't beeing accessed.  I'm attaching two files: one with Linux results and the other with XP.  My verson is 0x9e88.  Thanks for any help you can offer.
Thanks  BG

I got this a lot, and found out that it was due to the USB thumb drive I was using. Tried FAT16/FAT32, everything. Finally switched to a new thumb drive, and got further, but still problems. The third USB thumb drive worked for me....just try a different one until you get it right. If you use the Marvel commands you can find out if it sees your device or not etc...
Logged

bgrattan
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #92 on: October 16, 2009, 03:37:49 PM »

I used the "usb tree" command and it showed the flash drive correctly.  Is there another usb command that would give me more analysis?  Thanks.  BG
Logged

truxntrax
Newbie
*

Karma: 0
Posts: 21


View Profile
« Reply #93 on: October 19, 2009, 06:20:02 AM »

So how hard does this sound and how bad are the instructions....

I'm a linux newbie but wanting to learn (can copy files and move things around).  We get the plug - it works.  Start reading the wiki - that instructs may want to upgrade to a newer kernal and should probably do it now before it wipes everything. 

The instructions are rubbish and confusing. 

Can't one of the dev's write a bash script to do all the hard work for us?  Something that is just run from the plug itself hence removing all the hassle with connecting from another comp.

Am going to try to follow the instructions tonight but fear my new toy will be a brick very soon...

Why aren't the new plugs shipped with the new kernal???
Logged

chunk
Newbie
*

Karma: 0
Posts: 1


View Profile WWW
« Reply #94 on: October 20, 2009, 02:58:44 AM »

I finally got my plug working. I had poured over these forums and the plug wiki for hours.................... This is for use with the version 1 installer.

For instillation to nand with Windows:

1: Install the proper drivers. You will find all the information you need to do so here: http://plugcomputer.org/plugwiki/index.php/Serial_terminal_program
  1a: The drivers can be found on your CD.

2: Install libusb-win32-filter-bin-0.1.12.1.
  2a: http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/0.1.12.1/libusb-win32-filter-bin-0.1.12.1.exe/download

3: Update u-boot. You will find everything you need here: http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html
  3a: TFTP server I used: http://tftpd32.jounin.net/download/Tftpd32-3.35-setup.exe

4: Prepare the uboot-nand-custom.txt.
  4a: Replace the mac address in uboot/uboot-env/uboot-nand-custom.txt with the mac address on the back of your plug.

5: Copy all files in the the installer directory to a usb thumb drive(fat32 format).

6: Insert usb drive into your sheevaplug, connect console cable, connect power cable.

8: Click Start -> Run -> cmd -> <path to files> -> runme.exe nand

9: Wait for it to say "wrote file uboot.bin to nand". Remove console cable.

10: You can now log onto it through putty with user: root, pass: nosoup4u.


This is what worked for me. Hope it helps someone.
Logged

bgrattan
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #95 on: October 20, 2009, 11:49:59 AM »

Many thanks, Chunk, after 10 days I finally got it to install.  I kept getting errors on XP (hyperterm) even though I was able to connect to the plug with the console cable (USB).  It kept giving me an error that the installer program couldn't communicate with the plug.  I decided to try yet another time through my Linux machine and, after installing the missing libftdi.so.1 libraries, the thing took off.  Also many thanks to the person who developed the Installer 1.0!

Now I have to figure out how to move the rootfs to an SDHC (this is what messed me up in the beginning).

Thanks again,
BG
Logged

truxntrax
Newbie
*

Karma: 0
Posts: 21


View Profile
« Reply #96 on: October 20, 2009, 03:26:52 PM »

Ok I followed the instructions the best I could.

My host pc (ubuntu Jaunty) everything looked ok:
Code:
**** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)WARNING: All config files need .conf: /etc/modprobe.d/blacklist-vmc, it will be ignored in a future release.

 **** Preparing environment variables file ...
reading uboot/uboot-env/uboot-dflt.txt
uboot/uboot-env/fw_setenv baudrate 115200
CRC read error on uboot-env.bin: Success
uboot/uboot-env/fw_setenv loads_echo 0
uboot/uboot-env/fw_setenv ipaddr 10.4.50.165
uboot/uboot-env/fw_setenv serverip 10.4.50.5
uboot/uboot-env/fw_setenv rootpath /mnt/ARM_FS/
uboot/uboot-env/fw_setenv netmask 255.255.255.0
uboot/uboot-env/fw_setenv stdin serial
uboot/uboot-env/fw_setenv stdout serial
uboot/uboot-env/fw_setenv stderr serial
uboot/uboot-env/fw_setenv console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0\(uboot\)ro,0x1ff00000@0x100000\(root\)
uboot/uboot-env/fw_setenv mainlineLinux no
uboot/uboot-env/fw_setenv CASset min
uboot/uboot-env/fw_setenv enaMonExt no
uboot/uboot-env/fw_setenv enaCpuStream no
uboot/uboot-env/fw_setenv enaWrAllo no
uboot/uboot-env/fw_setenv pexMode RC
uboot/uboot-env/fw_setenv disL2Cache no
uboot/uboot-env/fw_setenv setL2CacheWT yes
uboot/uboot-env/fw_setenv disL2Prefetch yes
uboot/uboot-env/fw_setenv enaICPref yes
uboot/uboot-env/fw_setenv enaDCPref yes
uboot/uboot-env/fw_setenv sata_dma_mode yes
uboot/uboot-env/fw_setenv MALLOC_len 1
uboot/uboot-env/fw_setenv ethprime egiga0
uboot/uboot-env/fw_setenv netbsd_en no
uboot/uboot-env/fw_setenv vxworks_en no
uboot/uboot-env/fw_setenv bootargs_root root=/dev/nfs rw
uboot/uboot-env/fw_setenv bootargs_end :::DB88FXX81:eth0:none
uboot/uboot-env/fw_setenv image_name uImage
uboot/uboot-env/fw_setenv bootcmd tftpboot 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) \$\(bootargs_root\) nfsroot=\$\(serverip\):\$\(rootpath\) ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvNetConfig\) \$\(mvPhoneConfig\)\;  bootm 0x2000000\;
uboot/uboot-env/fw_setenv standalone fsload 0x2000000 \$\(image_name\)\;setenv bootargs \$\(console\) root=/dev/mtdblock0 rw ip=\$\(ipaddr\):\$\(serverip\)\$\(bootargs_end\) \$\(mvPhoneConfig\)\; bootm 0x2000000\;
uboot/uboot-env/fw_setenv bootdelay 3
uboot/uboot-env/fw_setenv disaMvPnp no
uboot/uboot-env/fw_setenv ethaddr 00:50:43:4e:2a:14
uboot/uboot-env/fw_setenv ethmtu 1500
uboot/uboot-env/fw_setenv mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot/uboot-env/fw_setenv mvNetConfig mv_net_config=\(00:11:88:0f:62:81,0:1:2:3\),mtu=1500
uboot/uboot-env/fw_setenv usb0Mode host
uboot/uboot-env/fw_setenv yuk_ethaddr 00:00:00:EE:51:81
uboot/uboot-env/fw_setenv nandEcc 1bit
uboot/uboot-env/fw_setenv netretry no
uboot/uboot-env/fw_setenv rcvrip 169.254.100.100
uboot/uboot-env/fw_setenv loadaddr 0x02000000
uboot/uboot-env/fw_setenv autoload no
uboot/uboot-env/fw_setenv enaAutoRecovery yes
uboot/uboot-env/fw_setenv ethact egiga0
reading uboot/uboot-env/uboot-nand-custom.txt
uboot/uboot-env/fw_setenv bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
uboot/uboot-env/fw_setenv mtdpartitions mtdparts=orion_nand:0x400000@0x100000\(uImage\),0x1fb00000@0x500000\(rootfs\)
uboot/uboot-env/fw_setenv ethaddr 00:50:43:01:da:96
uboot/uboot-env/fw_setenv real_bootcmd setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) \$\(bootargs_root\)\; nand read.e 0x00800000 0x00100000 0x00400000\; bootm 0x00800000
uboot/uboot-env/fw_setenv bootargs_console console=ttyS0,115200
uboot/uboot-env/fw_setenv bootcmd run recover1
uboot/uboot-env/fw_setenv recover1 setenv mainlineLinux yes\; setenv arcNumber 2097\; setenv bootcmd run recover2\; saveenv\; reset
uboot/uboot-env/fw_setenv recover2 run recover3\; setenv bootcmd \$\(real_bootcmd\)\; saveenv\; setenv bootargs \$\(bootargs_console\) \$\(mtdpartitions\) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand\; bootm 0x00800000 0x01100000
uboot/uboot-env/fw_setenv recover3 run recover4\; nand erase clean 0x00100000 0x00400000\; nand write.e 0x00800000 0x00100000 0x00400000
uboot/uboot-env/fw_setenv recover4 usb start\; fatload usb 0 0x00800000 uImage\; fatload usb 0 0x01100000 initrd

 **** Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0 (2009-07-26-14:56) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x0a02, ver: 0x2)
Info : JTAG Tap/device matched
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 21.655987s
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 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot.bin to NAND flash 0 up to offset 0x00074000 in 79.351952s

 **** U-boot should be up and running now. Open your console ...

But I get the bad magic number error at the marvel command prompt on the plug:
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... 3 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
...

3331626 bytes read

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 ...
Bad Magic Number
Marvell>>

I have tried run recover1 but no luck.
  I believe my plug is an old version:

Vendor Id: 9e88
Product Id: 9e8f

Used a 2g flash voyager usb thmb drive.  Downloaded new uboot file from here:

http://plugcomputer.org/index.php/us/resources/downloads?func=showdown&id=54

Any ideas?  Many thanks!
Logged

boerner
Jr. Member
**

Karma: 0
Posts: 54


View Profile
« Reply #97 on: October 20, 2009, 03:32:05 PM »

Just a guess, but try another thumb drive? Looks like the plug has problems reading from it...you are trying to install to a USB stick, correct?
Logged

truxntrax
Newbie
*

Karma: 0
Posts: 21


View Profile
« Reply #98 on: October 20, 2009, 04:03:05 PM »

Yup usb stick - correct.

One bit of the instructions which really confused me is:

5.  Copy the following to the USB stick root directory:
      a. Root file-system (packed into rootfs.tar.gz)
      b. Kernel (named uImage)
      c. Kernel modules (packed into modules.tar.gz)
      d. Init ramdisk (uImage.initrd)
    If you do not have all, you can download from:
      a. http://plugcomputer.org/index.php/us/resources/downloads (distro, kernel(LSP), uboot)
      b. http://plugcomputer.org/plugwiki/index.php/Main_Page     (distrio,uboot)
      c. http://sheeva.with-linux.com/sheeva                      (mainline kernel+modules)

What does this mean?  all I have on my usb stick is the following files (is this correct):

initrd
modules.tar.gz
README.txt
rootfs.tar.gz
ubuntu-sheevaplug.sh

Thanks for your help - will hunt round for another usb stick.  Would it be worth formatting with fat 16 rather than fat 32?

Many thanks

Logged

boerner
Jr. Member
**

Karma: 0
Posts: 54


View Profile
« Reply #99 on: October 20, 2009, 04:09:23 PM »

I would leave the stick formatted as FAT32.

Following these instructions from the Installer package:

5.  Copy the following to the USB stick root directory:
      a. Root file-system (packed into rootfs.tar.gz)
      b. Kernel (named uImage)
      c. Kernel modules (packed into modules.tar.gz)
      d. Init ramdisk (uImage.initrd)

You should only have those four files in the root of the thumb drive. Looks like you might have been missing one...might want to re-try with the original USB stick first before swapping one out needlessly.
Logged

truxntrax
Newbie
*

Karma: 0
Posts: 21


View Profile
« Reply #100 on: October 20, 2009, 04:24:37 PM »

Looks like I have got a little further:

Added another file onto usb stick
sheeva-2.6.31.4-uImage

Changed it's name to uImage.

Now my plug looks to boot but then stops here:
Code:
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            4096 mtdblock0 (driver?)
1f01          519168 mtdblock1 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[<c0031a78>] (unwind_backtrace+0x0/0xe0) from [<c00424cc>] (panic+0x50/0x120)
[<c00424cc>] (panic+0x50/0x120) from [<c0008efc>] (mount_block_root+0x1d4/0x214)
[<c0008efc>] (mount_block_root+0x1d4/0x214) from [<c00090c8>] (prepare_namespace+0x90/0x1c4)
[<c00090c8>] (prepare_namespace+0x90/0x1c4) from [<c0008750>] (kernel_init+0xdc/0x110)
[<c0008750>] (kernel_init+0xdc/0x110) from [<c002d3a4>] (kernel_thread_exit+0x0/0x8)


Any ideas?  Must go to bed now or SWMBO will not be happy - thanks for your help.
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #101 on: October 21, 2009, 01:31:49 PM »

      d. Init ramdisk (uImage.initrd)
But named initrd.  At least that is what I had:
Code:
-rwxr-xr-x 1 birdman root      1853 Oct 10 18:09 README.txt
-rwxr-xr-x 1 birdman root   3331626 Oct 10 18:09 initrd
-rwxr-xr-x 1 birdman root   3561533 Oct 10 18:09 modules.tar.gz
-rwxr-xr-x 1 birdman root 136517388 Oct 10 18:10 rootfs.tar.gz
-rwxr-xr-x 1 birdman root   2620504 Oct 10 18:10 uImage
Logged

truxntrax
Newbie
*

Karma: 0
Posts: 21


View Profile
« Reply #102 on: October 21, 2009, 03:01:28 PM »

Birdman where did you get your files from.  Mine are different sizes:

mine:
Code:
-rwx------ 1 john root   3331626 2009-08-19 15:24 initrd
-rwx------ 1 john root   3561533 2009-07-23 03:11 modules.tar.gz
-rwx------ 1 john root 116466688 2009-10-16 20:24 rootfs.tar.gz
-rwx------ 1 john root   2014240 2009-10-21 20:39 uImage
Yours:
Code:
-rwxr-xr-x 1 birdman root      1853 Oct 10 18:09 README.txt
-rwxr-xr-x 1 birdman root   3331626 Oct 10 18:09 initrd
-rwxr-xr-x 1 birdman root   3561533 Oct 10 18:09 modules.tar.gz
-rwxr-xr-x 1 birdman root 136517388 Oct 10 18:10 rootfs.tar.gz
-rwxr-xr-x 1 birdman root   2620504 Oct 10 18:10 uImage

Where did you get your uImage and rootfs?

BTW with the files I have the ploug reboots but stops here:
Code:
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

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
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **

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.22.18-6plug
   Created:      2009-03-11  18:32:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2014176 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initrd.ext2.gz
   Created:      2009-08-19  14:24:20 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3331562 Bytes =  3.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

But here it just hangs 0 have tried recover run1 etc....
Many thanks
« Last Edit: October 21, 2009, 03:04:39 PM by truxntrax » Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #103 on: October 21, 2009, 05:19:37 PM »

Birdman where did you get your files from.  Mine are different sizes:
|Well - 2 of yours are different sizes - rootfs and uImage (which is slightly worrying given that your Modules file is the same size).  And they have mod timestamps from after mine (which are all stamped with when I unpacked things)

My notes say it was picked up via http://plugcomputer.org/plugforum/index.php?topic=717.0.  I've just downloaded via the link in that posting again, and I get the same file as I already have.

[I did need the statically linked openocd attached to  http://plugcomputer.org/plugforum/index.php?topic=717.msg4535#msg4535, but that's irrelevant to this issue, I believe]

So - I suppose the real question is, "Where did you get yours from?".
Logged

truxntrax
Newbie
*

Karma: 0
Posts: 21


View Profile
« Reply #104 on: October 22, 2009, 02:06:30 AM »

MMmm.  Can't remember where I go my files from.  I remeber having trouble downloading the installer v1.0.

Will download again and check the file sizes.  Will check tonight..

Thanks for the pointers.
Logged

Pages: 1 ... 5 6 [7] 8 9 ... 16
Print
Jump to: