RE: BDI2000 and failed MMU translations

It's straight 2_4.  I wasn't stopping at start_kernel though.
I don't have PTBASE set up.

Not sure what I need.
Following some advice from mattl on #mklinux, I'm going to
break at start kernel FIRST, then connect with BDI, then
see if I can look at my data.

THX and Regards,

Matt

-----Original Message-----
From: Dan Malek [mailto:dan@embeddededge.com]
Sent: Wednesday, January 23, 2002 5:24 PM
To: Gessner, Matt
Cc: 'Linux PPC'
Subject: Re: BDI2000 and failed MMU translations


Gessner, Matt wrote:

quoted

I get a LOT of failed MMU translations reported.
Is this b/c I have something misconfigured?
I'm running 2.4.18 out of bk on an 860P.

Is it 2_4 or 2_4_devel?  I'm travelling for about the next
week, but will check it out when I return (if I can borrow
a BDI2000 from someone :-).

Has it worked on previous kernel versions?  If so, which ones?

Thanks.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Gessner, Matt wrote:

It's straight 2_4.  I wasn't stopping at start_kernel though.

You don't need to stop anywhere unless there are some breakpoints
you want to set for early debug.

I don't have PTBASE set up.

You need:
	MMU XLAT 0xc0000000
	PTBASE 0x000000f0

The newer kernels initialize the page table pointers for the BDI2000,
so ignore comments about stopping and setting values.  We went through
several iterations of implementation, so anything written about how to
do this manually is probably wrong :-).

...... I'm going to
break at start kernel FIRST, then connect with BDI, then
see if I can look at my data.

How do you break and then connect the BDI?  You need the BDI
connected to set and trap the breakpoint.

Have fun.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/