• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: u-boot version kernel version nightmare  (Read 2322 times)
soxs060389
Newbie
*

Karma: 0
Posts: 9


View Profile
« on: July 19, 2010, 01:43:33 PM »

Generic Setup:

BigBox, my usual PC, running Fedora 13, TFTP Server
Guru, guruplug, you know... that nasty thing...

I tried to compile my own kernel (2.6.35.rc4) and finally succeded. The bad thing is I can not bot it. I flashed it to NAND bot either I get

Code:
Uncompressing Linux... done, booting the kernel.

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

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
00000831        Marvell SheevaPlug Reference Board
0000085b        QNAP TS-119/TS-219
000009c6        QNAP TS-41x
00000939        Marvell OpenRD Client Board
00000915        Marvell OpenRD Base Board
00000899        LaCie Network Space v2

Please check your kernel config and/or bootloader.

or just

Code:
Uncompressing Linux... done, booting the kernel.
and then guruplug just resets.

u-boot version is custom compiled

bdinfo shows arcNumber 0x0000a63 which 2659 in decimal. Setting this in u-boot has no effect at all, nor has mainlineLinux


Code:
arch_number = 0x00000A63
env_t       = 0x00000000
boot_params = 0x00000100
DRAM bank   = 0x00000000
-> start    = 0x00000000
-> size     = 0x10000000
DRAM bank   = 0x00000001
-> start    = 0x10000000
-> size     = 0x10000000
DRAM bank   = 0x00000002
-> start    = 0x00000000
-> size     = 0x00000000
DRAM bank   = 0x00000003
-> start    = 0x00000000
-> size     = 0x00000000
ethaddr     = 00:50:43:67:64:06
ip_addr     = 172.20.160.237
baudrate    = 115200 bps


And now comes the uggly part: The factory kernel from marvel actually boots!?!? Any tipps how I can achiev this with my custom kernel? Acording to my selfmade kernel the archNumber for guruplug is correct (${kernel}/arch/arm/tools/mach-type)
Code:
guruplug MACH_GURUPLUG GURUPLUG 2659

Please help me, I am quite displeased, especially with the information I am finding on this topic. Nothing specific, only vague testemonials.
Logged

fragfutter
Sr. Member
****

Karma: 12
Posts: 280


View Profile
« Reply #1 on: July 19, 2010, 01:54:49 PM »

did you apply any additional patches? What did you use as cross compiler chain (i had issues with gcc 4.5)
i use flipflips u-boot. No idea about the orginal u-boot

The process is actually pretty straight forward http://www.held-im-ruhestand.de/software/sheevaplug/Kernel

Logged

soxs060389
Newbie
*

Karma: 0
Posts: 9


View Profile
« Reply #2 on: July 19, 2010, 02:38:36 PM »

Its not the chain, armv5tel-redhat-linux-gnueabi-gcc .

I finally found the problem, it was simple and stupid. The guruplug_config make target did NOT enable the guruplug device, therefore a53 / 2659 was not definied within the uImage binary → error.

Now I have to fiddle with some kernel options as it seems, kernel boots to some point, but lacks some drivers. The predefined guruplug_config is reborn shit.


The only patches I applied were 002, 003 from the official guruplug patchset (001 went allready upstream in 2.6.35).


For today, I wasted enough time. Thanks for your time.

if anybody interested in uImage or u-boot.bkd just PM.
Logged

Pages: [1]
Print
Jump to: