public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Txema Lopez <tlopez@aotek.es>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem porting the POST instruction cache test to the MPC5200.
Date: Mon, 14 Nov 2005 17:07:23 +0100	[thread overview]
Message-ID: <4378B63B.1060705@aotek.es> (raw)

Hi all,

I'm trying to port the POST cache test to the MPC5200 and I've found 
some problems porting the cache_post_test5 function. I think the 
philosophy of the function (I think the comments are not updated) is  to 
lock an instruction in the  cache, modify the instruction position in 
memory with another instruction and verify that the instruction locked 
in the cache has been executed when we jump to the instruction . The 
locked instruction load the r3 register with a 0 value and the "new" 
instruction with a -1. When I debug the function with the gdb and the 
BDI2000 with the ddd front end I see in the Machine Code Window the 
intruction locked ( li r3, 0) but if I stepi the instruction the value 
in r3 will be -1. I can't understand what is happening. Who is telling 
the truth?.  I think the problem seems to be  with the lock proccess 
and  I have a doubt: Must I activate the intruction MMU to lock the 
cache in a MPC5200? I have read the MPC5200 core manual and this aspect 
is not clear to me. How can I see the instruction cache with the gdb (or 
BDI2000) without write a specific function ?.

Any clue will be welcomed.

Attached my test cache file for the MPC5200  based on  the cache_8xx.S file.

Thanks in advance.

Jose Maria Lopez.
 


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cache_5xxx.S
Url: http://lists.denx.de/pipermail/u-boot/attachments/20051114/6952858f/attachment.txt 

             reply	other threads:[~2005-11-14 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 16:07 Txema Lopez [this message]
2005-11-15 16:00 ` [U-Boot-Users] Problem porting the POST instruction cache test to the MPC5200 Stefan Mätje

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4378B63B.1060705@aotek.es \
    --to=tlopez@aotek.es \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox