The size would be 0x20000000 for the entire device.  0x20000000 = 512MB

I can delete the posts which I just did for a whole bunch.  I don't have the permissions to block or delete the offending user.  Perhaps someone else could.

I never got that driver to run although I have not tried it since last May. 

I started using this driver for my cm19a and I modified my scripts to work with it.  http://www.linuxha.com/USB/  It has been a while since I compiled it but I think I remember editing the driver code and stripping it down to just support cm19a since that is all I needed.

edit: no actually I just changed the Makefile a bit for my build setup.  You should be able to use it as is.

I have not tried using a CM15A.

I also use a CM11a via a usb serial adapter.  For software to control the cm11a I use heyu which compiles fine.  http://heyu.tanj.com/

Booting from USB has problems when more than one USB device is attached.  Try connacting only your USB drive and see if it boots.  Then run some tests from there to see if your SDcard is working.  Also try a different SDcard.

The original file system and kernel shipped with the plug are pretty stripped down and doesn't have the kernel modules.  You would probably be better off if you upgrade your kernel and FS with the SheevaPlug installer 1.0 and work from that.

run


Then try modprobe again.

I had to run smbpasswd to get access working for my users samba users.  Did you run that?

smbpasswd -a user

Not up to me.  I'm just a customer.  Rabeeh Khoury started this thread so perhaps he can tell us what is in store.

Mark

sorry that was a cut and past error (fixed it)

Mark

No, it is correct.  0:1 specifies usb device:partition.  0x8000000 is the write address to memory for the image (you later bootm from this same address since it is were you wrote the kernel with ext2load).  /boot/uImage.sheeva.20090319 is the image name with full path  (the ext2 file system on the disk provides the actual disk read address and size of this file for reading).

The NAND doesn't have a partition table (this is why we have to pass it to the kernel by including the mtdparts in the bootargs section of the uboot  bootcmd we use)  We must also tell uboot the starting address to use for reading the kernel from flash and the length to read.  The kernel image is usually written raw to the second partition of the flash.  Again there are no real partitions, we decide how we want to divide it and then we must pass this information to uboot and to the kernel.  Most of us are using the 1st 1MB of flash for uBoot, then the next 4MB of flash for kernel Image, and the rest for the root file system.  Once you have picked the partition you intend to use you must be consistant with the information you pass to uBoot and the kernel.  The reason some of the documentation uses different numbers is because some people divide their flash differently.  You must adjust the commands to match the partitioning you are using.

With usb you don't need the read location or size since you are specifying a file and the file system will supply these.  you just specify the destination address in ram where you will then bootm from.

try executing:

does this U-boot support booting from sdcard?

I would like to get this working for my rsync over ssh that I use to sync up the server at my home and vacation home.  I suspect the limitation on the rsync through put is the ssh encryption.

Unfortunately I don't know even know where to start to enable using the encryption engine for ssh.  I've goggled a bit but have not tried real seriously yet.

I would be glad to help out getting this working if someone knows the basic setup needed to make this happen.

Mark

I saw the same thing. 

If I only have the drive plugged in the hub it tends to boot properly.  If I also have other devices plugged in uboot never finds the drive.  Seems like the ubs to serial port adapter I have is the worst offender.  I can plug all the devices in after it has booted and everything works fine.  So it seems to be uboot that has the limitations.

It sure would be nice if the uboot USB support worked better.