marvell u-boot

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

marvell u-boot

Postby daemonize » Thu Apr 12, 2012 10:12 pm

Marvell's u-boot code is based on an ancient version of u-boot. I've had nothing but trouble when trying to use the u-boot version that is part of the ALARM installation process. I've tried to skirt the whole thing by building my own u-boot and adding support for SD card booting, but I've created an unstable boot that isn't usable.

When I use the u-boot and uImage supplied with the installation, sure it works... but when I try and use a standard arm v5 kernel and set the appropriate u-boot env variables (arcNumber=2097, mainlineLinux=yes, etc) I don't get passed the Uncompressing Linux... done, booting the kernel.

Has anyone had success with the marvell u-boot and just taking a plain old ALARM armv5 kernel (like from the ArchLinuxARM-armv5te-latest.tar.gz) and get that working? It seems like you have to use the marvell u-boot as much as I dislike it.
daemonize
 
Posts: 4
Joined: Thu Apr 12, 2012 10:05 pm

Re: marvell u-boot

Postby WarheadsSE » Thu Apr 12, 2012 10:16 pm

Which device do you have?

And what is this "standard arm v5 kernel"? SoC selected, version, etc
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: marvell u-boot

Postby daemonize » Thu Apr 12, 2012 10:20 pm

I am using the SheevaPlug.

the kernel I mean is
uImage: u-boot legacy uImage, Linux-3.1.7-2-ARCH, Linux/ARM, OS Kernel Image (Not compressed), 2851368 bytes, Sat Jan 14 10:46:24 2012, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0x1B836DD5, Data CRC: 0xE6B3F0E4

(for example)
daemonize
 
Posts: 4
Joined: Thu Apr 12, 2012 10:05 pm

Re: marvell u-boot

Postby daemonize » Thu Apr 12, 2012 10:25 pm

Here's an example failed boot:
$this->bbcode_second_pass_code('', '

__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ 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
*** Warning - bad CRC or NAND, using default environment

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>> setenv mainlineLinux 'yes'
Marvell>> setenv arcNumber '2097'
Marvell>> setenv bootcmd 'mmcinit; mmcinit; fatload mmc 0:1 0x00800000 uimage; bootm 0x00800000; reset'
Marvell>> setenv bootargs 'console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mmcblk0p2 rootwait rw'
Marvell>> boot
SD found. Card desciption is:
Manufacturer: 0x02, OEM "TM"
Product name: "SA02G", revision 0.7
Serial number: 356966785
Manufacturing date: 7/2011
CRC: 0x00, b0 = 0
SD found. Card desciption is:
Manufacturer: 0x02, OEM "TM"
Product name: "SA02G", revision 0.7
Serial number: 356966785
Manufacturing date: 7/2011
CRC: 0x00, b0 = 0
reading uimage

2851432 bytes read
## Booting image at 00800000 ...
Image Name: Linux-3.1.7-2-ARCH
Created: 2012-01-14 15:46:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2851368 Bytes = 2.7 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0000020f).

Available machine support:

ID (hex) NAME
00000690 Marvell DB-88F6281-BP Development Board
00000691 Marvell RD-88F6192-NAS Development Board
00000692 Marvell RD-88F6281 Reference Board
0000078c Marvell 88F6281 GTW GE Board
00000a76 Marvell eSATA SheevaPlug Reference Board
00000831 Marvell SheevaPlug Reference Board
00000a63 Marvell GuruPlug Reference Board
00000bb6 Seagate FreeAgent DockStar
00000c11 Seagate GoFlex Net
00000d0a Seagate GoFlex Home
00000b36 Iomega iConnect Wireless
00000f78 Pogoplug V4
0000085b QNAP TS-119/TS-219
000009c6 QNAP TS-41x
00000b44 Marvell OpenRD Ultimate Board
00000939 Marvell OpenRD Client Board
00000915 Marvell OpenRD Base Board
0000089a LaCie Network Space Max v2
000008a0 LaCie Internet Space v2
00000899 LaCie Network Space v2
0000089b LaCie d2 Network v2
0000089e LaCie 5Big Network v2
0000089c LaCie 2Big Network v2
00000b1e HP t5325 Thin Client

Please check your kernel config and/or bootloader.
')
daemonize
 
Posts: 4
Joined: Thu Apr 12, 2012 10:05 pm

Re: marvell u-boot

Postby WarheadsSE » Thu Apr 12, 2012 10:32 pm

Ahh..

set arcNumber 2097
set mainlineLinux yes
save
reset

.. let it boot.

u-boot does not read these values after initialization
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: marvell u-boot

Postby daemonize » Thu Apr 12, 2012 10:35 pm

You are my hero. GG
daemonize
 
Posts: 4
Joined: Thu Apr 12, 2012 10:05 pm


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 3 guests