new uboot version 3.4.25

[rooster]

here is patched (with pingtoo`s patch http://plugcomputer.org/plugforum/index.php?topic=1134.msg7028#msg7028) 3.4.27 image

[pancho]

Hi!

For some reason, your build
http://plugcomputer.org/plugforum/index.php?action=dlattach;topic=1134.0;attach=221

does not work for me:
Marvell>> boot
SDHC found. Card desciption is:
Manufacturer:       0x03, OEM "SD"
Product name:       "SD08G", revision 8.0
Serial number:      2155893930
Manufacturing date: 7/2009
CRC:                0x00, b0 = 0

4301595 bytes read

1811960 bytes read
## Booting image at 00400000 ...
   Image Name:   Debian kernel
   Created:      2010-01-04  18:15:08 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1811896 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC


The build that pingtoo provided previously in this thread does work nicely, though:
http://plugcomputer.org/plugforum/index.php?action=dlattach;topic=1134.0;attach=201

Note that I tested your build twice, resetting the environment upon bubt.

If you need me to perform some tests, just say so.

Hope that it helps.

Happy hacking,

pancho.

[odoll]

here is patched (with pingtoo`s patch http://plugcomputer.org/plugforum/index.php?topic=1134.msg7028#msg7028) 3.4.27 image

Hi rooster, though pingtoo's versions works for me same issue with yours as pancho reported.

Marvell>> version

U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27 - pingtoo patch.01
Marvell>> bubt u-boot-rd88f6281Sheevaplug_400db_nand.bin
Using egiga0 device
TFTP from server 194.a.b.c; our IP address is 194.a.b.d
Filename 'u-boot-rd88f6281Sheevaplug_400db_nand.bin'.
Load address: 0x2000000
Loading: #################################################################
         ############################
done
Bytes transferred = 474592 (73de0 hex)

**Warning**
If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
Override Env parameters? (y/n) n
Erase 0 - 655360 ...
Copy to Nand Flash...
done
Marvell>> reset
[...]
Marvell>> version

U-Boot 1.1.4 (Dec 29 2009 - 13:18:27) Marvell version: 3.4.27
Marvell>> run bootcmd_sd
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0

2860756 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.3
   Created:      2010-01-07  23:31:19 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2860692 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

[tbm]

pancho: not sure it will fix what you see but it's worth trying.

It seems I didn't choose good values to load the kernel/ramdisk.  Please edit your bootcmd* env variables and replace
0x400000 with 0x00800000 and 0x0800000 with 0x01100000

Does that help?

[tbm]

I take back what I just said.  I just upgraded to 3.4.27 and get exactly the same error.  And the alternative u-boot (link from pancho) works for me!

[pancho]

@tbm
Hi!

If I recall correctly, this issue is related to the crosscompiler toolchain.  For some reason, the one that pingtoo uses does the trick (in Gentoo, /methinks), but the one used by rooster does not.

Cheers,

pancho.

[johnbock]

new QAed uboot version is ready, following are changes from last version (3.4.23):

  U-boot 3.4.27
  =============
  -) Modified in bootrom header file of 6280 the register values of 0x1620, and sequence of 0x1400. In mvUsb.c modified 0x50420 b[16:14] for 6280.
  -) Updated HAL.
  -) Changed electrical charactaristics of the PEX PHY in mvPex.c.


  U-boot 3.4.26
  =============
  -) Added 6282 option to mv_usb.c hal init function (prior to this addition the USB of the device was not initialized)
  -) Fixed in mvSata.h the device ID of 6282 to 1155 in order to make the integrated SATA controller work.

The SATA subsystem on the eSATA SheevaPlug is not being properly recognized using the 3.4.27 w/ pingtoo patch.

After a ide reset I get

Code:

Marvell>> version

U-Boot 1.1.4 (Dec 27 2009 - 22:03:21) Marvell version: 3.4.27 - pingtoo patch.01
Marvell>> ide reset

Reset IDE:
Marvell Serial ATA Adapter
Warning Integrated SATA is Powered Off
no device found

[tbm]

So is there a new version of u-boot available?  Ideally one that supports the SheevaPlug eSATA too.

Also, any idea when there will be a Marvell QAed release based on the official u-boot sources rather than the Marvell fork?

[tbm]

rooster, any comments on this at all?

[rooster]

Hi,

I am not aware of a new uboot version that supports eSATA, need to verify it.
There is no due date for an official uboot to plug AFAIK

[karl]

Sorry for bumping this thread. I have a Seagate FreeAgent DockStar. I would like to put Debian on it. I was wondering whether I can flash the pingtoo's patched U-Boot (u-boot-rd88f6281Sheevaplug_400db_nand.bin-pingtoo-patch.01) on my device or it is strictly for SheevaPlug?

Thanks,
Karl

[tylernt]

As far as I know the DockStar is simply a stripped-down Sheeva. The only catch is, nobody has been able to make a working JTAG interface for the DockStar yet so flashing the stock mtd0 u-Boot is very, very dangerous. The solution is to place your new bootloader in mtd3 (which is unused) and instruct the stock u-Boot to chainload it to a different area of RAM. Also, when using your own u-Boot from mtd3, make sure you set it to store it's environment variables in a different location so you don't corrupt the stock mtd0 u-Boot environment variables (thus bricking your 'Star).

A Sheeva kernel "should" boot on Dockstar... but I'm going to try it later tonight to find out for sure...

[wergio]

There is limit in mmc code. it can only address at most 4GB-something(which I have not exactly figure out) from beginning of a partition. So for example if you have 8GB SD, divide in to 2 partitions each 4GB, then you most likely OK with in u-boot, the mmc command set can address up to 4GB-(1 x ext2 block size) for sure, so unless you happen to have your object in that last block.

However if you divide your partitions to one greater then 4GB and the other one less then 4GB and if you wish use u-boot to access then you better put your object in the smaller partition.

i have a 16Gb SD with a single big partition
a dumb but easy solution I adopted is to copy the uImage in the root dir so a low inode will be assigned and u-boot will correctly load the kernel with:
ext2load mmc 0 0x800000 /uImage
instead of
ext2load mmc 0 0x800000 /boot/uImage

[Abra]

Martin, there is an u-boot somewhere that supports esata (i boot from esata), but I can't remember which one.
I'm pretty sure I found it on this forum or the newit forum.
I oculd give you a checksum if you want, or give you the binary.

[KidE]

Gents,

Will this version of uboot work correctly with the Guruserver Plus? Iḿ working with a pretty ancient version here so an update would be great ;-)