OK, we have to load and start at the same address. I think the kernel was built to load at 0x8000, so I changed the bootcmd as follows:

Marvell>> setenv bootcmd_usb 'setenv bootargs $(bootargs_usb); usb start; fatload usb 0:1 0x8000 uImage; bootm 0x8000; reset'
Marvell>> saveenv

Now I get the following--it appears that the uImage is bad at location 0x800c:

(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
...

2106764 bytes read
## Booting image at 00008000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-07-16  17:35:40 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2106700 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK

Starting kernel ...

undefined instruction
pc : [<0000800c>]          lr : [<006453f8>]
sp : 005fe514  ip : 00000004     fp : 00000002
r10: 006540b0  r9 : 005ff1f0     r8 : 005fffcc
r7 : 00000000  r6 : 00000000     r5 : 00000154  r4 : 00000000
r3 : 00008000  r2 : 00000100     r1 : 00000831  r0 : 00000000
Flags: Nzcv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

I am compiling the kernel distributed by Marvell and trying to load it onto the Sheeva Plug from a USB memory stick. The plug is loading the kernel, but it goes into never-never land. Can you suggest a possible problem location?

Here is the tail of "make uImage":

Image Name:   Linux-2.6.22.18
Created:      Thu Jul 16 10:35:40 2009
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2106700 Bytes = 2057.32 kB = 2.01 MB
Load Address: 0x00008000
Entry Point:  0x00008000
  Image arch/arm/boot/uImage is ready

Here is how it hangs:

(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
...

2106764 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-07-16  17:35:40 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2106700 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Here is the boot environment:

Marvell>> echo $(bootcmd)
run bootcmd_usb; run bootcmd_nand
Marvell>> echo $(bootcmd_usb)
setenv bootargs $(bootargs_usb); usb start; fatload usb 0:1 0x0008000 uImage; bootm 0x8000000; reset
Marvell>> echo $(bootargs_usb)
console=ttyS0,115200 root=/dev/sda2 rootdelay=20 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw

But it seems to mount as sysfs:

root@ubuntu:~# mount -t sysfs /dev/mtdblock1 /mnt/mtdroot
root@ubuntu:~# ls -l /mnt/mtdroot
total 0
drwxr-xr-x  2 root root 0 Jul  6 22:55 block
drwxr-xr-x 13 root root 0 Jul  6 22:55 bus
drwxr-xr-x 31 root root 0 Jul  6 22:55 class
drwxr-xr-x  4 root root 0 Jul  6 22:55 dev
drwxr-xr-x  5 root root 0 Jul  6 22:55 devices
drwxr-xr-x  2 root root 0 Jul  6 22:55 firmware
drwxr-xr-x  3 root root 0 Jul  6 22:55 fs
drwxr-xr-x  5 root root 0 Jul  6 22:55 kernel
drwxr-xr-x 31 root root 0 Jul  6 22:55 module

Thanks for pointing me in the right direction.

Well at least it recognizes the file system, but:

root@ubuntu:~# mount -t jffs2 /dev/mtdblock1 /mnt/mtdroot
mount: /dev/mtdblock1: can't read superblock
root@ubuntu:~#

It churned around for awhile to get to this failure.

I am following the wiki for the subject, http://www.computingplugs.com/index.php/Booting_entirely_off_an_external_USB_device.

When I try to mount the file system from nand I get this failure:

root@ubuntu:~# mount /dev/mtdblock1 /mnt/mtdroot
VFS: Can't find ext4 filesystem on dev mtdblock1.
FAT: bogus number of FAT structure
mount: you must specify the filesystem type

So I try this:

root@ubuntu:~# mount -t ext2 /dev/mtdblock1 /mnt/mtdroot
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

I am working on a plug that was restored using the installer http://www.openplug.org/plugwiki/index.php/SheevaPlug_Installer

Why can't I mount the file system?

Wes

This may not be appropriate for the PlugComputer forum, but I don't know where else to turn. I am wanting to install the  new (good) U-bo0t on the plug. I am reading the http://plugcomputer.org/plugwiki/index.php/Das_U-boot_plug_support. I have gotten down to the "How to download..." and "On Linux host setup OpenOCD...". Then I am reading http://www.openplug.org/plugwiki/index.php/Setting_Up_OpenOCD_Under_Linux.

I downloaded http://www.intra2net.com/en/developer/libftdi. The instructions say "Follow the instructions included in the version supplied for your architecture. I could find no instructions. I tried to configure and build the library but I get

checking for libusb-config... /usr/local/lib/libusb-1.0.s0.0.0.0:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
./configure: line 19885: /usr/local/lib/libusb-1.0.s0.0.0.0:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin: No such file or directory
./configure: line 19886: /usr/local/lib/libusb-1.0.s0.0.0.0:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin: No such file or directory
checking if libusb version is >= 0.1.7... ./configure: line 19899: /usr/local/lib/libusb-1.0.s0.0.0.0:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin: No such file or directory

yum says that I do have libsub installed. Please help this Linux newbie

The u-boot source download contains the 1.1.4 release and some 3.4.16 files. The Release Notes talk about a patch for updatging 1.1.4 to 3.4.11, but I have not been able to locate that patch file. Can someone tell me how to upgrade 1.1.4?

I think I am almost there to boot the Sheeva from a USB stick. Here is the stick info:

Marvell>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Marvell>> usb info
1: Hub,  USB Revision 2.0
 - Marvell EHCI
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Mass Storage,  USB Revision 2.0
 -          USB DISK 20X     07531C9032DF
 - Class: (from Interface) Mass Storage
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0d7d  Product 0x1600 Version 1.0
   Configuration: 1
   - Interfaces: 1 Bus Powered 200mA
     Interface: 0
     - Alternate Settings 0, Endpoints: 3
     - Class Mass Storage, Transp. SCSI, Bulk only
     - Endpoint 1 In Bulk MaxPacket 512
     - Endpoint 2 Out Bulk MaxPacket 512
     - Endpoint 3 In Interrupt MaxPacket 64 Interval 4ms

Here is the partition table:

Marvell>> usb part
print_part of 0

Partition Map for USB device 0  --   Partition Type: DOS

Partition     Start Sector     Num Sectors     Type
    1                   32            5088       6
    2                 5120         1960960      83

That is uImage in partition 0:1, and root in partition 0:2
Here are the environment variables:

bootcmd=usb start; fatload usb 0:1 0x8000000 uImage; bootm 0x8000000; reset
bootargs_usb=console=ttyS0,=115200 ro root=/dev/sda1 rootdelay=10

But this is what I get when I try to boot:

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
................................................................................
................................................................................
......................

1869708 bytes read
## Booting image at 08000000 ...
Bad Magic Number

Where am I going wrong?

Wes

Could it be an out-of-memory issue?

I am running a tftp server on my CentOS Linux i386 system.
Here is the tftpserver startup:

[root@compaps ~]# /opt/tftpServer/tftpserversp/tftpserver -v
TFTP Server SinglePort Version 1.62 Unix Built 1621

starting TFTP...
username: root
alias / is mapped to /home/tftp/
permitted clients: 192.168.1.100-192.168.1.120
max blksize: 65464
default blksize: 512
default timeout: 3
file read allowed: Yes
file create allowed: No
file overwrite allowed: No
listening on: 192.168.1.101:69

Accepting requests..
Client 192.168.1.101:35676 /home/tftp/hello.o2, 10 Blocks Served

The above message resulted from a test using
tftp localhost
and get hello.o2
which was successful.

The following is from the Sheeva plug console running tftp
that was connected to the tftp server:

tftp> status
Connected to 192.168.1.101.
Mode: netascii Verbose: off Tracing: off
Rexmt-interval: 5 seconds, Max-timeout: 25 seconds
tftp> verbose
Verbose mode on.
tftp> get hello.o2
getting from 192.168.1.101:hello.o2 to hello.o2 [netascii]
Transfer timed out.

Does anyone know why the request from the Sheeva plug failed?

Wes

Thanks, Charles.

Yes, of course, it was a pathing problem. With your suggestion I found that cc1 is actually in
/home/gcc/libexec/gcc/arm-none-linux-gnueabi/4.2.1

I can see why they call them cross compilers--they are always very angry about something!

Wes Stupar

When I execute this,
[root@compaps hello]# /home/gcc/arm-none-linix-gnueabi/bin/gcc -o hello.sheeva hello.c
I get this:
gcc: error trying to exec 'cc1': execvp: No such file or directory
Can someone interpret this for me?

I am trying to add the 0002 patch per "Procedure to Configure and Build the Linux kernel with 4.2.7 LSP". When I execute
[root@compaps linux-feroceon_4_2_7_KW]# patch -p1 0002_SheevaPlug_support.patch 
it never terminates the operation.

Where am I going wrong?

OK, now I have gcc. Thank you, Mr. Morgan. I had to stumble through the apt-get several times for install, then I had to do an "apt-get update" and then do an install again, but all's well that ends well. BTW, I looked into rc.local and found that the mkdir was already there.

Wes

Well, I tried apt-get install build-essential, and this is what I got:

The following packages will be upgraded:
  gcc-4.3-base libc6 libgcc1 libstdc++6
4 upgraded, 21 newly installed, 0 to remove and 9 not upgraded.
E: Could not open lock file /var/cache/apt/archives/lock - open (2 No such file
or directory)
E: Unable to lock the download directory

What is the apt archives lock file?

Wes