From mboxrd@z Thu Jan  1 00:00:00 1970
From: shangway <shangway@yahoo.com>
Date: Mon, 8 May 2006 19:58:19 -0700 (PDT)
Subject: [U-Boot-Users] u-boot fails at cpu_init_f
Message-ID: <20060509025819.33828.qmail@web60014.mail.yahoo.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi all,

I'm trying to get u-boot to run on a proprietary 8540
based board. The board is similar to the MPC8540ADS
which configuration I used to build u-boot. I am using
eldk 4.0. I managed to download u-boot to flash, but I
am unable to run it. By stepping through the code, I
found that it fails in the first c-function
"cpu_init_f". 

This is the assembly code for cpu_init_f:

fff82e10 <cpu_init_f>:
fff82e10:	94 21 ff f0 	stwu    r1,-16(r1)
fff82e14:	3c 60 e4 01 	lis     r3,-7167
fff82e18:	7c 08 02 a6 	mflr    r0
fff82e1c:	60 63 3f 80 	ori     r3,r3,16256
fff82e20:	38 80 00 00 	li      r4,0
fff82e24:	38 a0 00 30 	li      r5,48
fff82e28:	90 01 00 14 	stw     r0,20(r1)
fff82e2c:	48 00 59 b1 	bl      fff887dc <memset>
fff82e30:	3c 00 ff 00 	lis     r0,-256
fff82e34:	3d 20 e0 00 	lis     r9,-8192
fff82e38:	60 00 18 01 	ori     r0,r0,6145
fff82e3c:	3d 60 ff 00 	lis     r11,-256
fff82e40:	90 09 50 00 	stw     r0,20480(r9)
fff82e44:	61 6b 6f f7 	ori     r11,r11,28663
fff82e48:	38 00 e1 f1 	li      r0,-7695
fff82e4c:	91 69 50 04 	stw     r11,20484(r9)
fff82e50:	3d 40 f8 00 	lis     r10,-2048
fff82e54:	90 09 50 24 	stw     r0,20516(r9)
fff82e58:	61 4a 08 01 	ori     r10,r10,2049
fff82e5c:	80 01 00 14 	lwz     r0,20(r1)
fff82e60:	38 21 00 10 	addi    r1,r1,16
fff82e64:	91 49 50 20 	stw     r10,20512(r9)
fff82e68:	7c 08 03 a6 	mtlr    r0
fff82e6c:	4e 80 00 20 	blr
fff82e70:	00 02 86 0c 	.long 0x2860c

The code runs fine (at least that's what I think)
until  0xfff82e5c. The cpu hangs when I try to execute
that instruction. This is the first time, that there
is a load from an address which is not in flash, so I
suspect, that setting up the cache as RAM failed. 
I also tried to manually write data to that location
with gdb, but I read only 0x0.
As this is still in the initialization process of the
cpu, I don't think that it is related to a possibly
wrong board configuration, or am I wrong.

Any ideas?

Thanks in advance and best regards,

Gordon.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com