RE: BDI2000 and failed MMU translations

Whooops, too soon.

OK, AFTER the first breakpoint, it then gets mad about
single stepping.

The MMU xlation fails for the next address.

Matt

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


Gessner, Matt wrote:

quoted

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.

quoted

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 :-).

quoted

...... 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/

Gessner, Matt wrote:

Whooops, too soon.

I'm sure it's my fault, I'm sorry.

I started making some changes to support large page sizes and I think
it screwed up the BDI2000.  I'll have a patch in as quickly as possible
(yet tonight) and post it.  I won't be able to test it with the BDI2000
but it is basically backing out some changes I made.

I apologize.


	-- Dan


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