ebp
Newbie
Karma: 1
Posts: 24
|
 |
« Reply #90 on: August 06, 2009, 01:17:37 PM » |
|
I'm not sure exactly what wrong, when i follow the guide in the wiki i get the following error on the linux host: stina@stina-desktop:~/Skrivebord/sheevaplug-installer-alpha-6$ sudo ./runme.sh
[sudo] password for stina:
**** 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 seems like it just does a normal boot: =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2009.08.06 22:14:04 =~=~=~=~=~=~=~=~=~=~=~=
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: SHEEVA PLUG LE
U-Boot 1.1.4 (Mar 19 2009 - 16:06:59) Marvell version: 3.4.16
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CEE80
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
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND: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: 3 2 1 0
NAND read: device 0 offset 0x100000, size 0x400000
Reading data from 0x100000 -- 0% complete.
Reading data from 0x10a000 -- 1% complete.
Reading data from 0x114000 -- 2% complete.
Reading data from 0x11e800 -- 3% complete.
Reading data from 0x128800 -- 4% complete.
Reading data from 0x133000 -- 5% complete.
Reading data from 0x13d000 -- 6% complete.
Reading data from 0x147800 -- 7% complete.
Reading data from 0x151800 -- 8% complete.
Reading data from 0x15c000 -- 9% complete.
Reading data from 0x166000 -- 10% complete.
Reading data from 0x170800 -- 11% complete.
Reading data from 0x17a800 -- 12% complete.
Reading data from 0x185000 -- 13% complete.
Reading data from 0x18f000 -- 14% complete.
Reading data from 0x199800 -- 15% complete.
Reading data from 0x1a3800 -- 16% complete.
Reading data from 0x1ae000 -- 17% complete.
Reading data from 0x1b8000 -- 18% complete.
Reading data from 0x1c2800 -- 19% complete.
Reading data from 0x1cc800 -- 20% complete.
Reading data from 0x1d7000 -- 21% complete.
Reading data from 0x1e1000 -- 22% complete.
Reading data from 0x1eb800 -- 23% complete.
Reading data from 0x1f5800 -- 24% complete.
Reading data from 0x1ff800 -- 25% complete.
Reading data from 0x20a000 -- 26% complete.
Reading data from 0x214000 -- 27% complete.
Reading data from 0x21e800 -- 28% complete.
Reading data from 0x228800 -- 29% complete.
Reading data from 0x233000 -- 30% complete.
Reading data from 0x23d000 -- 31% complete.
Reading data from 0x247800 -- 32% complete.
Reading data from 0x251800 -- 33% complete.
Reading data from 0x25c000 -- 34% complete.
Reading data from 0x266000 -- 35% complete.
Reading data from 0x270800 -- 36% complete.
Reading data from 0x27a800 -- 37% complete.
Reading data from 0x285000 -- 38% complete.
Reading data from 0x28f000 -- 39% complete.
Reading data from 0x299800 -- 40% complete.
Reading data from 0x2a3800 -- 41% complete.
Reading data from 0x2ae000 -- 42% complete.
Reading data from 0x2b8000 -- 43% complete.
Reading data from 0x2c2800 -- 44% complete.
Reading data from 0x2cc800 -- 45% complete.
Reading data from 0x2d7000 -- 46% complete.
Reading data from 0x2e1000 -- 47% complete.
Reading data from 0x2eb800 -- 48% complete.
Reading data from 0x2f5800 -- 49% complete.
Reading data from 0x2ff800 -- 50% complete.
Reading data from 0x30a000 -- 51% complete.
Reading data from 0x314000 -- 52% complete.
Reading data from 0x31e800 -- 53% complete.
Reading data from 0x328800 -- 54% complete.
Reading data from 0x333000 -- 55% complete.
Reading data from 0x33d000 -- 56% complete.
Reading data from 0x347800 -- 57% complete.
Reading data from 0x351800 -- 58% complete.
Reading data from 0x35c000 -- 59% complete.
Reading data from 0x366000 -- 60% complete.
Reading data from 0x370800 -- 61% complete.
Reading data from 0x37a800 -- 62% complete.
Reading data from 0x385000 -- 63% complete.
Reading data from 0x38f000 -- 64% complete.
Reading data from 0x399800 -- 65% complete.
Reading data from 0x3a3800 -- 66% complete.
Reading data from 0x3ae000 -- 67% complete.
Reading data from 0x3b8000 -- 68% complete.
Reading data from 0x3c2800 -- 69% complete.
Reading data from 0x3cc800 -- 70% complete.
Reading data from 0x3d7000 -- 71% complete.
Reading data from 0x3e1000 -- 72% complete.
Reading data from 0x3eb800 -- 73% complete.
Reading data from 0x3f5800 -- 74% complete.
Reading data from 0x3ff800 -- 75% complete.
Reading data from 0x40a000 -- 76% complete.
Reading data from 0x414000 -- 77% complete.
Reading data from 0x41e800 -- 78% complete.
Reading data from 0x428800 -- 79% complete.
Reading data from 0x433000 -- 80% complete.
Reading data from 0x43d000 -- 81% complete.
Reading data from 0x447800 -- 82% complete.
Reading data from 0x451800 -- 83% complete.
Reading data from 0x45c000 -- 84% complete.
Reading data from 0x466000 -- 85% complete.
Reading data from 0x470800 -- 86% complete.
Reading data from 0x47a800 -- 87% complete.
Reading data from 0x485000 -- 88% complete.
Reading data from 0x48f000 -- 89% complete.
Reading data from 0x499800 -- 90% complete.
Reading data from 0x4a3800 -- 91% complete.
Reading data from 0x4ae000 -- 92% complete.
Reading data from 0x4b8000 -- 93% complete.
Reading data from 0x4c2800 -- 94% complete.
Reading data from 0x4cc800 -- 95% complete.
Reading data from 0x4d7000 -- 96% complete.
Reading data from 0x4e1000 -- 97% complete.
Reading data from 0x4eb800 -- 98% complete.
Reading data from 0x4f5800 -- 99% complete.
Reading data from 0x4ff800 -- 100% complete.
4194304 bytes read: OK
## Booting image at 00800000 ...
Image Name: Linux-2.6.22.18
Created: 2009-03-19 9:18:16 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2106696 Bytes = 2 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.22.18 (dhaval@devbox) (gcc version 4.2.1) #1 Thu Mar 19 14:46:22 IST 2009
CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
Built 1 zonelists. Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
PID hash table entries: 2048 (order: 11, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB 0MB 0MB = 512MB total
Memory: 515456KB available (3864K code, 257K data, 104K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....base 10000000, size 256MB
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e8000000, size 128MB
PEX0_IO ....base f2000000, size 1MB
INTER_REGS ....base f1000000, size 1MB
NFLASH_CS ....base fa000000, size 2MB
SPI_CS ....base f4000000, size 16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size 2MB
Marvell Development Board (LSP Version KW_LSP_4.2.7_patch2)-- SHEEVA PLUG Soc: 88F6281 A0 LE
Detected Tclk 200000000 and SysClk 400000000
MV Buttons Device Load
Marvell USB EHCI Host controller #0: c08b8600
PEX0 interface detected no Link.
PCI: bus0: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
Time: kw_clocksource clocksource has been installed.
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
RTC registered
Use the XOR engines (acceleration) for enhancing the following functions:
o RAID 5 Xor calculation
o kernel memcpy
o kenrel memzero
Number of XOR engines to use: 4
cesadev_init(c000c894)
mvCesaInit: sessions=640, queue=64, pSram=f0000000
Warning: TS unit is powered off.
MV Buttons Driver Load
NTFS driver 2.1.28 [Flags: R/O].
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
Loading Marvell Ethernet Driver:
o Cached descriptors in DRAM
o DRAM SW cache-coherency
o Single RX Queue support - ETH_DEF_RXQ=0
o Single TX Queue support - ETH_DEF_TXQ=0
o TCP segmentation offload enabled
o Receive checksum offload enabled
o Transmit checksum offload enabled
o Network Fast Processing (Routing) supported
o Driver ERROR statistics enabled
o Driver INFO statistics enabled
o Proc tool API enabled
o Rx descripors: q0=128
o Tx descripors: q0=532
o Loading network interface(s):
o eth0, ifindex = 1, GbE port = 0
o eth1, ifindex = 2, GbE port = 1
mvFpRuleDb (dfd00000): 16384 entries, 65536 bytes
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Warning Sata is Powered Off
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 678 at 0x054c0000
Bad eraseblock 2043 at 0x0ff60000
Bad eraseblock 2835 at 0x16260000
Bad eraseblock 2836 at 0x16280000
Bad eraseblock 2838 at 0x162c0000
Bad eraseblock 2841 at 0x16320000
Bad eraseblock 3704 at 0x1cf00000
Bad eraseblock 3705 at 0x1cf20000
Bad eraseblock 3706 at 0x1cf40000
Bad eraseblock 3707 at 0x1cf60000
Bad eraseblock 3709 at 0x1cfa0000
2 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 2 MTD partitions on "nand_mtd":
0x00100000-0x00500000 : "uImage"
0x00500000-0x20000000 : "rootfs"
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
USB Universal Host Controller Interface driver v3.0
usb 1-1: new high speed USB device using ehci_marvell and address 2
usb 1-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux telephony interface: v1.00
Marvell Telephony Driver:
mvBoardVoiceAssembleModeGet: TDM not supported(boardId=0x9)
assembly=-1,irq=-1
mp_check_config: Error, invalid voice assembley mode
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
raid6: int32x1 97 MB/s
raid6: int32x2 114 MB/s
raid6: int32x4 122 MB/s
raid6: int32x8 111 MB/s
raid6: using algorithm int32x4 (122 MB/s)
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
raid5: measuring checksumming speed
arm4regs : 1071.600 MB/sec
8regs : 754.800 MB/sec
32regs : 900.000 MB/sec
raid5: using function: arm4regs (1071.600 MB/sec)
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
dm_crypt using the OCF package.
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mvsdmmc: irq =28 start f1090000
mvsdmmc: no IRQ detect
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).
mvCLAudioCodecRegGet: Error while reading register!
mvCLAudioCodecInit: Error - Invalid Cirrus Logic chip/rev ID!
Error - Cannot initialize audio decoder.at address =0xff<6>ALSA device list:
#0: Marvell mv88fx_snd ALSA driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
eth0: started
IP-Config: Complete:
device=eth0, addr=10.4.50.4, mask=255.255.255.0, gw=10.4.50.5,
host=DB88FXX81, domain=, nis-domain=(none),
bootserver=10.4.50.5, rootserver=10.4.50.5, rootpath=
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Empty flash at 0x01162070 ends at 0x01162800
Empty flash at 0x08548070 ends at 0x08548800
Empty flash at 0x0c6d3f60 ends at 0x0c6d4000
Empty flash at 0x0d206034 ends at 0x0d206800
Empty flash at 0x0ec90198 ends at 0x0ec90800
Empty flash at 0x0f227f6c ends at 0x0f228000
Empty flash at 0x0f75b0f4 ends at 0x0f75b800
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 104K
scsi 0:0:0:0: Direct-Access USB 2.0 Flash Disk 2.00 PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 1015808 512-byte hardware sectors (520 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 1015808 512-byte hardware sectors (520 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
* Filesystem type 'fusectl' is not supported. Skipping mount.
* Setting preliminary keymap...
[ OK ]
* Starting kernel event manager...
[ OK ]
* Loading hardware drivers...
[ OK ]
* Loading kernel modules... * Loading manual drivers...
[ OK ]
* Setting kernel variables (/etc/sysctl.conf)...
[ OK ]
* Setting kernel variables (/etc/sysctl.d/10-console-messages.conf)...
[ OK ]
* Setting kernel variables (/etc/sysctl.d/10-network-security.conf)... error: "net.ipv4.tcp_syncookies" is an unknown key
[fail]
* Activating swap...
[ OK ]
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
* Starting early crypto disks...
[ OK ]
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.22.18/modules.dep: No such file or directory
* Starting remaining crypto disks...
[ OK ]
* Checking file systems... fsck 1.41.4 (27-Jan-2009)
[ OK ]
* Mounting local filesystems... ntfs-3g: Failed to access volume '/dev/sda2': No such file or directory
Please type '/sbin/mount.ntfs-3g --help' for more information.
[fail]
* Activating swapfile swap...
[ OK ]
* Configuring network interfaces...
[ OK ]
* Setting up console font and keymap...
[ OK ]
* Starting system log daemon...
Ubuntu 9.04 simba ttyS0
simba login:
[ OK ]
* Starting kernel log daemon...
[ OK ]
* Starting OpenBSD Secure Shell server sshd
[ OK ]
* To run ddclient as a daemon, please set run_daemon to 'true' in /etc/default/ddclient
...done.
* Starting Samba daemons
[ OK ]
* Starting periodic command scheduler crond
[ OK ]
Error : Temporary failure in name resolution
8 Feb 14:00:21 ntpdate[1215]: can't find host ntp.ubuntu.com
8 Feb 14:00:21 ntpdate[1215]: no servers can be used, exiting Hope you can help, i'm a newbie. |
|
|
|
|
Logged
|
|
|
|
|
debio
Newbie
Karma: 0
Posts: 38
|
|
« Reply #91 on: August 06, 2009, 02:49:13 PM » |
|
|
|
|
|
|
Logged
|
|
|
|
|
ebp
Newbie
Karma: 1
Posts: 24
|
|
« Reply #92 on: August 07, 2009, 12:20:21 AM » |
|
Thank you very much, now it works perfectly  |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #93 on: August 07, 2009, 05:22:28 AM » |
|
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?
Any new suggestions? I do need to download some source for the installer binaries to chage that default? Where is that source? Any Idea when there will be a followup version? |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #94 on: August 08, 2009, 06:23:39 PM » |
|
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?
Any new suggestions? I do need to download some source for the installer binaries to chage that default? Where is that source? Any Idea when there will be a followup version? Any updates on this? I have the exact same problem as christoph: tar: write error: No space left on device
...
# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 1fb00000 00020000 "root"
#
Is there some way to force the current install to use the correct partitions (or make the actual partitions match what the installer is expecting), or will I have to wait until another installer version is released? I'd be happy to provide any information you need. EDIT: If it helps any, I had to change the sheevaplug.cfg for the new vid/pid, and my bootargs_root is just "bootargs_root root=/dev/mtdblock1" (I want to just boot from the NAND, and the comments in the file are anything but clear on what I should change it to, so I may have messed that up) |
|
|
|
« Last Edit: August 08, 2009, 06:30:16 PM by SgtPepper »
|
Logged
|
|
|
|
|
|
|
|
« Reply #95 on: August 09, 2009, 05:56:11 AM » |
|
no idea why your linux sees the first mtd partition. can you boot into u-boot and check what "printenv mtdpartitions" is? I think you can play around with it using mtdparts, but here i would need to test myself.
The other way is to modify the installer to use a different partition. After writing the complete nand flash memory over jtag the installer does the following:
* load a initrd from usb
* load a kernel from usb
* boot the kernel
* mount and format mtd devices (<-- fix this)
* untar the the file roots into this mtd device
so to fix the installer you need to fix it to use the right device.
Get the initrd from the installer (the one you copied on the usb stick).
Strip the u-boot header (dd if=initrd of=initrd.gz ibs=64 skip=1)
Unzip it (gunzip initrd.gz)
Mount it in a loop (mount -o loop initird <some/path>)
modify <some/path>/etc/init.d/rcS
unmount the initrd, gzip it, repack it
(this should be the trick mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n initrd -d initrd.gz initrd)
sorry you need to figure this out yourself. you might want to simply drop to a shell in rcS and do it interactive. actualy hitting any key during the countdown (PRESS ENTER TO STOP THE COUNT DOWN) should drop to a shell. So forget about the modification. Just hit a key, look at the rcS and do it step by step.
|
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #96 on: August 09, 2009, 06:23:41 AM » |
|
no idea why your linux sees the first mtd partition. can you boot into u-boot and check what "printenv mtdpartitions" is? I think you can play around with it using mtdparts, but here i would need to test myself.
The other way is to modify the installer to use a different partition. After writing the complete nand flash memory over jtag the installer does the following:
* load a initrd from usb
* load a kernel from usb
* boot the kernel
* mount and format mtd devices (<-- fix this)
* untar the the file roots into this mtd device
so to fix the installer you need to fix it to use the right device.
Get the initrd from the installer (the one you copied on the usb stick).
Strip the u-boot header (dd if=initrd of=initrd.gz ibs=64 skip=1)
Unzip it (gunzip initrd.gz)
Mount it in a loop (mount -o loop initird <some/path>)
modify <some/path>/etc/init.d/rcS
unmount the initrd, gzip it, repack it
(this should be the trick mkimage -A arm -O linux -T ramdisk -C gzip -a 0x0 -e 0x0 -n initrd -d initrd.gz initrd)
sorry you need to figure this out yourself. you might want to simply drop to a shell in rcS and do it interactive. actualy hitting any key during the countdown (PRESS ENTER TO STOP THE COUNT DOWN) should drop to a shell. So forget about the modification. Just hit a key, look at the rcS and do it step by step.
Thanks for the response. Marvell>> printenv mtdpartitions
mtdpartitions=mtdparts=orion_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
Marvell>>
After replacing /dev/mtdblock1 with /dev/mtdblock2 (or /dev/mtd2) for the mounting of /mnt2 in rcS and manually running it leads me to the same "no space left on device" error. Was I understanding correctly what needed to change? EDIT: I'm guessing it has something to do with: # mount -t jffs2 /dev/mtdblock2 /mnt2
Empty flash at 0x013658f8 ends at 0x01366000
jffs2_scan_inode_node(): CRC failed on node at 0x04897fc8: Read 0xffffffff, calculated 0x02556d46
Empty flash at 0x04898010 ends at 0x04898800
Empty flash at 0x0d3b8128 ends at 0x0d3b8800
Empty flash at 0x0f55432c ends at 0x0f554800
Empty flash at 0x130e600c ends at 0x130e6800
jffs2_scan_inode_node(): CRC failed on node at 0x16a75fdc: Read 0xffffffff, calculated 0x1a189dab
Empty flash at 0x16a76024 ends at 0x16a76800
# df /dev/mtdblock2
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mtdblock2 519168 321952 197216 62% /mnt2
#
It looks like /dev/mtdblock2 still has my old rootfs in place. Shouldn't it have been erased earlier in the install process? I had noticed those "Empty flash" and "CRC failed" messages on boot before I tried the alpha-6 installer, but I thought it would straighten it out by overwriting. Do I have a faulty device? |
|
|
|
« Last Edit: August 09, 2009, 07:03:19 AM by SgtPepper »
|
Logged
|
|
|
|
|
|
|
|
« Reply #97 on: August 09, 2009, 11:19:05 AM » |
|
the installer is using ubifs (and i never used those tools). but it's not only the mount. Looking at rcS i can see that the installer starts to mess with the flash directly at the beginning echo "**** Erasing all flash"
if [ $UBIFS ]; then
ubiformat -y /dev/mtd1
ubiattach /dev/ubi_ctrl -m 1
|
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #98 on: August 09, 2009, 03:08:10 PM » |
|
the installer is using ubifs (and i never used those tools). but it's not only the mount. Looking at rcS i can see that the installer starts to mess with the flash directly at the beginning
Thanks again. The problem was that in my hurry (I had just a few minutes free to it), I thought $UBIFS code blocks were for booting off SD and wouldn't be run for me. Looking at rcS again, I see that it is just an option to use JFFS2 in flash rather than ubifs. I changed all the places that referred to "-m 1", "mtd1", and "mtdblock1" to 2s (went again and rebuilt initrd) and changed my bootargs_root to "ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs". Success! Thanks again. |
|
|
|
« Last Edit: August 09, 2009, 06:15:37 PM by SgtPepper »
|
Logged
|
|
|
|
|
boerner
Jr. Member
Karma: 0
Posts: 54
|
|
« Reply #99 on: August 10, 2009, 01:00:31 PM » |
|
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
Just wanted to add a note of thanks to fragfutter. Having finally gotten a Sheevaplug last Friday, I immediately tried to update it via the installer and could not figure it why the plug wasn't being detected. This information solved my problem and prevented me from punching a kitten this morning :-) Thanks again. |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #100 on: August 10, 2009, 09:17:48 PM » |
|
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: 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! i found the exact same issue. i've outlined it in more detail here: http://plugcomputer.org/plugforum/index.php?topic=591.0 |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #101 on: August 14, 2009, 01:02:25 PM » |
|
Hi,
I reloaded my alpha-6 installer on my Linux host. I'm using a 3rd USB stick. The plug does not seem to like it either.
See: "** Unable to use usb 0:1 for fatload **" I have the same problem today. I've created a "FAT32" filesystem on the first (only) partition of a 4GB PNY USB memory stick. This shows up under lsusb as: Bus 001 Device 024: ID 090c:1000 Feiya Technology Corp. Flash Drive I've also tried a 512MB IBM microDrive through a powered hub. That produced slightly different output when scanning for storage devices: USB: scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... T T T T Device NOT ready
Request Sense returned 00 00 00
1 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 **
Any further suggestions? |
|
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #102 on: August 14, 2009, 04:28:28 PM » |
|
To answer my own problem.
I remembered I also had a spare 1GB microSD card and using that with an SD adaptor and an SD->USB adaptor seems to have done the trick.
Not sure what the issue was with the other USB stick. It mounts OK now that the system is running.
One problem I do have now is that eth0 only seems to want to run IPv6, which doesn't help me much with an IPv4 router. Is there a link somewhere to a useful "How to configure Ubuntu" page? And not "help.ubuntu.com", which seems to assume you are using a GUI - I need a description of which config files are where.
|
|
|
|
« Last Edit: August 14, 2009, 04:51:38 PM by birdman »
|
Logged
|
|
|
|
|
Billy
Newbie
Karma: 0
Posts: 12
|
|
« Reply #103 on: August 20, 2009, 12:24:55 AM » |
|
Sorry, I'm an absolute newbie. I got my Plug 2 weeks ago. Now I wanted to update it by alpha-6 installer. When I used alpha-6 Installer according the Install WIKI, I got the following message on my Linux system: root@Lt-Ubuntu:~/Desktop/Sheeva# ./runme.sh
**** Preparing environment variables file ...
grep: installer/uboot-custom.txt: No such file or directory
**** 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
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 20.600372s
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 0x00073000 in 73.503960s
**** U-boot should be up and running now. Open your console ...
root@Lt-Ubuntu:~/Desktop/Sheeva#
It tells me that the install should be ok. After connecting to the Plug I get the following message. __ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: SHEEVA PLUG LE
U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16
<INTERRUPT>
Marvell>> e: 00600000 -> 0067FFF0 BSS: -> 006CF100
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
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND: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
egiga0 no link
mvEgigaInit: egiga1 mvEthPortEnable failed (error)
mvEgigaInit: egiga1 failed
Using egiga0 device
TFTP from server 10.4.50.5; our IP address is 10.4.50.165
Filename 'uImage'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
## Booting image at 02000000 ...
Bad Magic Number
Marvell>>
I assume, uboot is not running correctly. What is gooing wrong? I tried it with 4 different USB sticks. How can I test whether the stick is recognized by the Plug? Thanks for your help. |
 Console (0 KB - downloaded 78 times.)
|
|
|
Logged
|
|
|
|
|
|
|
|
« Reply #104 on: August 21, 2009, 10:50:11 AM » |
|
I am getting the same problems as restamp and bpsbr_ernie. When I execute the runme script I get a slew of JTAG errors due to the fact that ttyUSB0 device node just vanished from my host.
Do we know if this is a problem with the sheevaplug itself, or could it be a bug in the ftdi_sio driver for linux (which may be fixed in some distributions and not others)?
|
|
|
|
|
Logged
|
|
|
|
|
|
