• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 2 [3] 4 5 ... 16
« previous next »
Author Topic: Sheevaplug installer - version 1.0  (Read 66398 times)
Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #30 on: September 17, 2009, 01:33:46 PM »
Code:
root@reedy-laptop:/media/disk/sheevaplug-installer-v1.0# php runme.php nand

 ****   exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)WARNING: All config files need .conf: /etc/modprobe.d/local-fdti, 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:01:CA:B0
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:CA:B0
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
Error: JTAG communication failure: check connection, JTAG interface, target power etc.
Error: trying to validate configured JTAG chain anyway...
Error: Could not validate JTAG scan chain, IR mismatch, scan returned 0x00. tap=feroceon.cpu pos=0 expected 0x1 got 0
Warn : Could not validate JTAG chain, continuing anyway...
Error: unexpected Feroceon EICE version signature
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted
Runtime error, file "openocd/config/board/sheevaplug.cfg", line 21:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplugroot@reedy-laptop:/media/disk/sheevaplug-installer-v1.0# lsusb
Bus 005 Device 003: ID 058f:6335 Alcor Micro Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 9e88:9e8f
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Any suggestions?


Thanks!
Logged

DamonHD
Full Member
***

Karma: 4
Posts: 169


View Profile WWW
« Reply #31 on: September 17, 2009, 01:51:26 PM »
IIRC, I had to get the ftdi still (apt-get).

Rgds

Damon
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #32 on: September 17, 2009, 02:23:55 PM »
Aye, me too. But that was a different error that went away Wink
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #33 on: September 18, 2009, 01:27:05 AM »
You can use the statically linked openocd I posted first.

Try to open a console to the device, does this work?
If not, try:
   disconnect the mini USB
   rmmmod ftdi_sio
   modprobe ftdi_sio vendor=0x9e88 product=0x9e8f
   reconnect the mini USB

Console should connect to your plug and you should see uboot printing.
If this works, then close your console application, disconnect/connect your mini USB and try the runme.php script.

I did notice that sometimes a reset via the pin hole on the plug is not sufficient, try first mini USB dis/connect and if this does not work power down the plug.
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #34 on: September 20, 2009, 03:31:24 AM »
Yup, console works fine from putty. Can use it as a terminal, and see what its printing when it reboots

I did notice when it did the thing above, the sheeva did just then reboot..

Will look at using the statically linked openocd
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #35 on: September 20, 2009, 04:20:38 PM »
Code:
root@reedy-laptop:/media/disk/sheevaplug-installer-v1.0# rmmod ftdi_sio
root@reedy-laptop:/media/disk/sheevaplug-installer-v1.0# modprobe ftdi_sio vendor=0x9e88 product=0x9e8f
WARNING: All config files need .conf: /etc/modprobe.d/local-fdti, it will be ignored in a future release.
root@reedy-laptop:/media/disk/sheevaplug-installer-v1.0# php runme.php nand
 **** exec(modprobe ftdi_sio vendor=0x9e88 product=0x9e8f)WARNING: All config files need .conf: /etc/modprobe.d/local-fdti, 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:01:CA:B0
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:CA:B0
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 ...
sh: openocd/openocd: Permission denied
 **** openocd FAILED
 **** Is the mini USB cable connected?
 **** Try powering down, then replugging the Sheevaplugroot@reedy-laptop:/media/disk/sheevaplug-installer-v1.0#

But like i said, it works fine via putty. That is with the openocd replaced with the one you posted
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #36 on: September 22, 2009, 03:49:11 AM »
Any chance your putty/minicom is open while running the runme.php ?
If so please close it before running the runme.php
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #37 on: September 22, 2009, 04:48:53 AM »
I've tried both (open and closed), or at least, im pretty sure i have.

That worked fine in 0.6 or whatever it was Wink

I'll check again tonight and verify
Logged

Rabeeh Khoury
Administrator
Full Member
*****

Karma: 5
Posts: 218


View Profile
« Reply #38 on: September 22, 2009, 08:19:16 AM »
Note that armin76 reported (and I reproduced) and issue with the 'console' environment variable when being manually saved in u-boot
The problem is that it doesn't get saved and always revers to the value '0xa0000'.

We found the issue and will be fixed soon with newer version of U-Boot.
Logged

hypn0toad
Newbie
*

Karma: 0
Posts: 29


View Profile
« Reply #39 on: September 22, 2009, 10:51:10 AM »
i'm currently running everything alpha6

so is there any way i could just upgrade it without wiping everything out?  maybe a way to backup my programs and files or something?  i don't have to go through all of the same configuration stuff again...  right now i have eveyrthing booting from my SD card and have lots of stuff setup properly
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #40 on: September 22, 2009, 04:08:09 PM »
Quote from: Rabeeh Khoury on September 22, 2009, 08:19:16 AM
Note that armin76 reported (and I reproduced) and issue with the 'console' environment variable when being manually saved in u-boot
The problem is that it doesn't get saved and always revers to the value '0xa0000'.

We found the issue and will be fixed soon with newer version of U-Boot.


Is that directed at my problem?


rooster, having putty closed makes no difference

/dev/ttyUSB1 is where putty is accessing...

/dev/ttyUSB0 seems to have gone
« Last Edit: September 22, 2009, 04:19:37 PM by Reedy » Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #41 on: September 23, 2009, 12:57:02 AM »
Quote
so is there any way i could just upgrade it without wiping everything out?
If you want to burn the new uboot then you can run the installer without any USB DOK connected to the plug, so basically you are running the openocd to burn the uboot and uboot env.

If this is the case I recommend you change the /uboot-env/uboot-mmc-custom.txt file.
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #42 on: September 23, 2009, 01:28:36 AM »
Hi Reedy,

Quote
/dev/ttyUSB0 seems to have gone

When plugging your mini USB you should see two new devices in the /dev/ttyUSB*, here is my dmesg for the mini USB plug action:
Quote
[1905919.096051] usb 1-1: new full speed USB device using uhci_hcd and address 24
[1905919.303628] usb 1-1: configuration #1 chosen from 1 choice
[1905919.313276] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
[1905919.313332] ftdi_sio: Detected FT2232C
[1905919.313539] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB1
[1905919.319860] ftdi_sio 1-1:1.1: FTDI USB Serial Device converter detected
[1905919.319913] ftdi_sio: Detected FT2232C
[1905919.320038] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB2

The first one is used by the openocd as JTAG and the second one is the console.
Do you see these two devices?
Logged

klauterbach
Newbie
*

Karma: 0
Posts: 4


View Profile
« Reply #43 on: September 23, 2009, 05:22:06 AM »
Installation to mmc is failing for me during the "scanning for storage devices" state. The error is below. As far as I know, it's scanning for the USB DOK with the installer files on it. I have a sandisk cruzer 1G (FAT16) USB stick in the USB port with the appropriate data on it. I don't understand why it's not being detected?  Can anyone suggest a solution?

Also, what does "Bad Magic Number" mean?

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... 2 USB Device(s) found
       scanning bus for storage devices... T T T Device NOT ready
   Request Sense returned 00 00 00
0 Storage Device(s) found
Device NOT ready
   Request Sense returned 00 00 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
Device NOT ready
   Request Sense returned 00 00 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
## Booting image at 00800000 ...
Bad Magic Number

Thanks
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #44 on: September 23, 2009, 11:58:14 AM »
Hi klauterbach,

The cruzer is U3 based, could it be that the U3 is preventing uboot to recognize the DOK? can you try another DOK?

Regarding the Bad Magic number, since uboot could not find the DOK it continued the boot procedure by trying to load from 00800000 but since nothing was burned there but this sector was erased the uImage Magic number could not be found, thus uboot did not find a valid uImage.
Logged

Pages: 1 2 [3] 4 5 ... 16
Print
« previous next »
Jump to: