• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: installer 1.0 booting sign salad  (Read 1275 times)
cubed
Newbie
*

Karma: 0
Posts: 2


View Profile
« on: June 27, 2010, 04:19:56 AM »

Hi,

I dont know what to do... After using the Sheevaplug installer form the Download Archiv:

http://www.plugcomputer.org/index.php/us/resources/downloads?func=fileinfo&id=53

The plug is not booting correctly

As you can see their isn't an error its only sign salad which makes it not easier...

This is a log created by putty, have tried several times:



Code:
Hit any key to stop autoboot:  3     2     0
Marvell>> run recover1

Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
 
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ 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:  3     2     1     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
.
...
.

2620504 bytes read
reading initrd
.
...

3331626 bytes read

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

Erasing at 0x100000 --   3% complete. Cleanmarker written at 0x100000.
Erasing at 0x120000 --   6% complete. Cleanmarker written at 0x120000.
Erasing at 0x140000 --   9% complete. Cleanmarker written at 0x140000.
Erasing at 0x160000 --  12% complete. Cleanmarker written at 0x160000.
Erasing at 0x180000 --  15% complete. Cleanmarker written at 0x180000.
Erasing at 0x1a0000 --  18% complete. Cleanmarker written at 0x1a0000.
Erasing at 0x1c0000 --  21% complete. Cleanmarker written at 0x1c0000.
Erasing at 0x1e0000 --  25% complete. Cleanmarker written at 0x1e0000.
Erasing at 0x200000 --  28% complete. Cleanmarker written at 0x200000.
Erasing at 0x220000 --  31% complete. Cleanmarker written at 0x220000.
Erasing at 0x240000 --  34% complete. Cleanmarker written at 0x240000.
Erasing at 0x260000 --  37% complete. Cleanmarker written at 0x260000.
Erasing at 0x280000 --  40% complete. Cleanmarker written at 0x280000.
Erasing at 0x2a0000 --  43% complete. Cleanmarker written at 0x2a0000.
Erasing at 0x2c0000 --  46% complete. Cleanmarker written at 0x2c0000.
Erasing at 0x2e0000 --  50% complete. Cleanmarker written at 0x2e0000.
Erasing at 0x300000 --  53% complete. Cleanmarker written at 0x300000.
Erasing at 0x320000 --  56% complete. Cleanmarker written at 0x320000.
Erasing at 0x340000 --  59% complete. Cleanmarker written at 0x340000.
Erasing at 0x360000 --  62% complete. Cleanmarker written at 0x360000.
Erasing at 0x380000 --  65% complete. Cleanmarker written at 0x380000.
Erasing at 0x3a0000 --  68% complete. Cleanmarker written at 0x3a0000.
Erasing at 0x3c0000 --  71% complete. Cleanmarker written at 0x3c0000.
Erasing at 0x3e0000 --  75% complete. Cleanmarker written at 0x3e0000.
Erasing at 0x400000 --  78% complete. Cleanmarker written at 0x400000.
Erasing at 0x420000 --  81% complete. Cleanmarker written at 0x420000.
Erasing at 0x440000 --  84% complete. Cleanmarker written at 0x440000.
Erasing at 0x460000 --  87% complete. Cleanmarker written at 0x460000.
Erasing at 0x480000 --  90% complete. Cleanmarker written at 0x480000.
Erasing at 0x4a0000 --  93% complete. Cleanmarker written at 0x4a0000.
Erasing at 0x4c0000 --  96% complete. Cleanmarker written at 0x4c0000.
Erasing at 0x4e0000 -- 100% complete. Cleanmarker written at 0x4e0000.
OK

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


Writing data at 0x100000 --   0% complete.
Writing data at 0x10a000 --   1% complete.
Writing data at 0x114000 --   2% complete.
Writing data at 0x11e800 --   3% complete.
Writing data at 0x128800 --   4% complete.
Writing data at 0x133000 --   5% complete.
Writing data at 0x13d000 --   6% complete.
Writing data at 0x147800 --   7% complete.
Writing data at 0x151800 --   8% complete.
Writing data at 0x15c000 --   9% complete.
Writing data at 0x166000 --  10% complete.
Writing data at 0x170800 --  11% complete.
Writing data at 0x17a800 --  12% complete.
Writing data at 0x185000 --  13% complete.
Writing data at 0x18f000 --  14% complete.
Writing data at 0x199800 --  15% complete.
Writing data at 0x1a3800 --  16% complete.
Writing data at 0x1ae000 --  17% complete.
Writing data at 0x1b8000 --  18% complete.
Writing data at 0x1c2800 --  19% complete.
Writing data at 0x1cc800 --  20% complete.
Writing data at 0x1d7000 --  21% complete.
Writing data at 0x1e1000 --  22% complete.
Writing data at 0x1eb800 --  23% complete.
Writing data at 0x1f5800 --  24% complete.
Writing data at 0x1ff800 --  25% complete.
Writing data at 0x20a000 --  26% complete.
Writing data at 0x214000 --  27% complete.
Writing data at 0x21e800 --  28% complete.
Writing data at 0x228800 --  29% complete.
Writing data at 0x233000 --  30% complete.
Writing data at 0x23d000 --  31% complete.
Writing data at 0x247800 --  32% complete.
Writing data at 0x251800 --  33% complete.
Writing data at 0x25c000 --  34% complete.
Writing data at 0x266000 --  35% complete.
Writing data at 0x270800 --  36% complete.
Writing data at 0x27a800 --  37% complete.
Writing data at 0x285000 --  38% complete.
Writing data at 0x28f000 --  39% complete.
Writing data at 0x299800 --  40% complete.
Writing data at 0x2a3800 --  41% complete.
Writing data at 0x2ae000 --  42% complete.
Writing data at 0x2b8000 --  43% complete.
Writing data at 0x2c2800 --  44% complete.
Writing data at 0x2cc800 --  45% complete.
Writing data at 0x2d7000 --  46% complete.
Writing data at 0x2e1000 --  47% complete.
Writing data at 0x2eb800 --  48% complete.
Writing data at 0x2f5800 --  49% complete.
Writing data at 0x2ff800 --  50% complete.
Writing data at 0x30a000 --  51% complete.
Writing data at 0x314000 --  52% complete.
Writing data at 0x31e800 --  53% complete.
Writing data at 0x328800 --  54% complete.
Writing data at 0x333000 --  55% complete.
Writing data at 0x33d000 --  56% complete.
Writing data at 0x347800 --  57% complete.
Writing data at 0x351800 --  58% complete.
Writing data at 0x35c000 --  59% complete.
Writing data at 0x366000 --  60% complete.
Writing data at 0x370800 --  61% complete.
Writing data at 0x37a800 --  62% complete.
Writing data at 0x385000 --  63% complete.
Writing data at 0x38f000 --  64% complete.
Writing data at 0x399800 --  65% complete.
Writing data at 0x3a3800 --  66% complete.
Writing data at 0x3ae000 --  67% complete.
Writing data at 0x3b8000 --  68% complete.
Writing data at 0x3c2800 --  69% complete.
Writing data at 0x3cc800 --  70% complete.
Writing data at 0x3d7000 --  71% complete.
Writing data at 0x3e1000 --  72% complete.
Writing data at 0x3eb800 --  73% complete.
Writing data at 0x3f5800 --  74% complete.
Writing data at 0x3ff800 --  75% complete.
Writing data at 0x40a000 --  76% complete.
Writing data at 0x414000 --  77% complete.
Writing data at 0x41e800 --  78% complete.
Writing data at 0x428800 --  79% complete.
Writing data at 0x433000 --  80% complete.
Writing data at 0x43d000 --  81% complete.
Writing data at 0x447800 --  82% complete.
Writing data at 0x451800 --  83% complete.
Writing data at 0x45c000 --  84% complete.
Writing data at 0x466000 --  85% complete.
Writing data at 0x470800 --  86% complete.
Writing data at 0x47a800 --  87% complete.
Writing data at 0x485000 --  88% complete.
Writing data at 0x48f000 --  89% complete.
Writing data at 0x499800 --  90% complete.
Writing data at 0x4a3800 --  91% complete.
Writing data at 0x4ae000 --  92% complete.
Writing data at 0x4b8000 --  93% complete.
Writing data at 0x4c2800 --  94% complete.
Writing data at 0x4cc800 --  95% complete.
Writing data at 0x4d7000 --  96% complete.
Writing data at 0x4e1000 --  97% complete.
Writing data at 0x4eb800 --  98% complete.
Writing data at 0x4f5800 --  99% complete.
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:
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.
$  q  JeugA +˔B, (QWY4.da1- QP *E  Je5gAZ x &b F h Zia( )%A&-
JX Rj*   Be! H   d a). Jew  ] . * mY  iJ* RFZP kQ; g  (Q*+m[  2 3 BX +d  D a).   )P 
Logged

cubed
Newbie
*

Karma: 0
Posts: 2


View Profile
« Reply #1 on: June 28, 2010, 09:11:33 AM »

seems as if the probleme is gone by itself...

just left the plug alone and after a while it displayed the login...
since this isn't my first plug i don't get the difference, but it works so now its all fine Wink


cubed
Logged

tylernt
Jr. Member
**

Karma: 2
Posts: 56


View Profile
« Reply #2 on: June 28, 2010, 09:45:39 AM »

Appears that your kernel is set to the wrong baud rate (i.e., something other than 115200) for bootup messages. However since you eventually got a login prompt, your terminal is configured correctly. You should be able to pass a console=ttyS0,115200 argument to your kernel in U-Boot to eliminate the salad.
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #3 on: June 30, 2010, 10:43:34 PM »

What plug are you using?
If it based on 6282 then it is a known issue, Mainline Linux does not support this Z0 version SoC properly.

You will need to patch the kernel with this patch
Quote
Logged

Pages: [1]
Print
Jump to: