SheevaPlugs with a - (dash) in the S/N from GLOBALSCALE

[js4]

Hello,

I have been working with older version of the sheevaplug (pre-dash in S/N) and have successfully  loaded my own rootfs multiple times. So recently I received 12 more sheevaplugs from Globalscale that have some slight differences. The plastic is more white, the lights are different color, and the S/N format has changed, and for the life of me I cannot load a custom rootfs to it or the rootfs that comes with the sheeva installer. This is what it looks like if I try to re-flash it:

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2620440 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
$®q+eug+ËB,Z(QWY4.da1-ªQPª*E­JeugA+& $
R       !+
­1)ÖY,f4RNY¨Fi,6#¤ÉBb­ç7I7+bLj¤3@/¥KV2é1½U]6¨h«kÒJ+P+yX,Ò)f.l
)(©µ)¹
      A3¬WYP«µi®·iz­Q7;P
                        E4-$fAsªW5kFm1+t-JA(«kÊqje1»Ô
                                                     nqÛP+Iw§q¼EQ3®U¹U
                                                                      E4-Bb,+3ìWA{ÇI2ìfU"j5+

                                                                                            B|gI4îeP®ª7»
                                                                                                        ¾d0­öwTGQ8.â§]y¬w7;Xw­À1*u¤BZ®$VI:»n5/ÖGA4®5Ôgew«êÒh=ÉF2YB/

A:­þx®g}6¬uX.
             B,
               â2,      b9*O1$
âY
  a,
àY,     @¼wi2Ör®Ui0g¥]w­Öp.CÊ~7-jAzwi2 1'KQrÖ$v%/ª%u$«T`(U+Q½ËIP­Çe5­G4-þx©
                                                                           5dbY¦%q8í'U2~6ÖGI\¨ÔG_9,KYw.Wm5Ô
                                                                                                           bX®ÉPI6=V3ìWAt¬Òb2«
                                                                                                                              $]zVWe(+V6Z(ѧI1<i2 Z
                                                                                                                                                   F-i1U2§|w©êÌ1A4ìÒq1+KQqVBKb §IqV@+P)F0[)q8­'U"·j5¥q^(Z%0IZJ"¨BY¤£&8
A4£PVYwu%cR0U
             Æz,E4-Å^Z®)]0-f2\IA8,F8]u-BVªÕYs/¢dY)0y©]{«+9$¢^1«Õëyd0­§BW¶r6$Uqe_,@)ÖFT(vI1ÖFQ,UEz,«]3(*eC=(w]xexfJ,
                                                                                                                   ]sWQ(²pv'«XÒ)&
                                                                                                                                 ë]x§67Q1(U+Q­ËI­e5íGY¤³$!).Jg8¬wA{VÇI¸K%Iz¨ÖI:­7q¨7ÄW-ëñA5íA3­bX(Ti1Ö$f      ()©M5Ke1)+]x7]4(*uQ4.2ZG±4§U;wI¨æâqb
                                   b"¤JYi·ix¬§i1)Òc£ÕD-KZ<Ë6ÄS­÷7I7;¤j aEv®7$¬$&I:7Iw°.P
                                                                                        E4-rix¬§i®iu,e19U"¯r:Õ]w)yi5»
                                                                                                                     YwTÖ;®75ìgB|$f§J(bTuuTIq­
                                                                                                                                              Îx1(uWB¨
                                                                                                                                                      B
                                                                                                                                                       V:       A{­vq;½ª¦lu­


GLOBALSCALE said that Marvell changed the CPU on them causing a number of issues. Please let me know if anyone knows how to fix this!

[superpat]

Have a look at:-


http://plugcomputer.org/plugforum/index.php?topic=2002.0

cheers

Patrick

[js4]

Thanks! I'll give that kernel a shot.

[js4]

2.6.32 didn't work for me. I ran the second stage of bootstrap via chroot instead of booting off of the filesystem. I don't think that would mess it up, but maybe? I'm at a loss... I still get random characters.

[js4]

New rootfs on old device works fine:

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete. Cleanmarker written at 0x4e0000.
OK

NAND write: device 0 offset 0x100000, size 0x400000

Writing data at 0x4ff800 -- 100% complete.
 4194304 bytes written: OK
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2620440 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initrd.ext2.gz
   Created:      2009-08-19  14:24:20 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3331562 Bytes =  3.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux.............................................................                                          ................................................................................                                          ............................. done, booting the kernel.
Linux version 2.6.30.2 (kelly@speedy) (gcc version 4.2.1) #11 PREEMPT Wed Jul 22                                           19:53:31 MDT 2009
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(                                          uImage),0x1fb00000@0x500000(rootfs) root=/dev/ram0 rw ramdisk=0x01100000,8M inst                                          all_type=nand
NR_IRQS:114
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 = 512MB total
Memory: 510080KB available (4728K code, 998K data, 140K init, 0K highmem)



It doesn't look like I created it wrong. One thing to note - I noticed this box does have a - (dash) in the serial, but the box isn't as white as the new ones nor does it have the same color lights. Anyone able to help!?

[cjm]

Stupid question: could the console baud rate be incorrect? It seems unlikely that a corrupt kernel image prints this much crap before crashing...

[js4]

The devices do have different CPUs:

Linux version 2.6.30.2 (kelly@speedy) (gcc version 4.2.1) #11 PREEMPT Wed Jul 22 19:53:31 MDT 2009
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell SheevaPlug Reference Board

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


I might need to tweek the sheevainstaller. The each device uses a different kernel command line:

Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) ubi.mtd=1 root=ubi0:rootfs rootfstype=ubi

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

[js4]

I set my bootargs to this:

bootargs=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


ran this:

Marvell>> run $(bootargs); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000

got this:
Unknown command 'a0000' - try 'help'

The console setting keeps getting mangled to this:

console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)

Doesn't matter how many times i set it, it goes back to the same setting. Has anyone had this issue?

[birdman]

I set my bootargs to this:

bootargs=console=ttyS0,115200 mtdparts=
.......;
got this:
Unknown command 'a0000' - try 'help'

The console setting keeps getting mangled to this:

console=a0000
e=ttyS0,115200 mtdparts=.....

You're not cut&pasting from some UTF-* capable editor, are you?

[js4]

I'm using putty with utf-8

Marvell>> set console console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
Marvell>> saveenv
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
Marvell>> reset
▒
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ 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 A1 (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
Marvell>> print console
console=a0000

[js4]

Finally got it working. I had to change some things in uboot-dflt.txt and uboot-nand-custom.txt, and change the uImage I was using.

[warpcore]

Finally got it working. I had to change some things in uboot-dflt.txt and uboot-nand-custom.txt, and change the uImage I was using.

Can you please tell me what changes you did on those files? I am facing the *exact* same problem and if you provide me the details, I would be grateful.

Thanks in advance!

[marcus]

I set my bootargs to this:

bootargs=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


ran this:

Marvell>> run $(bootargs); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000

got this:
Unknown command 'a0000' - try 'help'

The console setting keeps getting mangled to this:

console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)

Doesn't matter how many times i set it, it goes back to the same setting. Has anyone had this issue?

The corrupted environment variable with value a0000 is a bug in one or more versions of U-Boot. Newer versions don't have the bug.