linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ibm405gp <ibm405.linux@laposte.net>
To: list <linuxppc-embedded@lists.linuxppc.org>
Subject: Abatron Bdi2000 and 405GP
Date: Tue, 06 Nov 2001 14:26:29 +0100	[thread overview]
Message-ID: <3BE7E505.DC9DE6E8@laposte.net> (raw)


Hello,

How can i read back (or write) for example, the FPGA registers from the
walnut board (at @OxFO300000) with abatron.
I can read this memory area just after the ioremap operation (in
walnut.c) when the entry for 0XF0300000 is present
in the TLB without any problem (0xF0300000 -> 0xF0300000). With the
abatron debugger, i should be able to read any virtual adress, even if
this adress is not present in the TLB. Am i right ? Any suggestion ?
Thanks.

I'am using the latest version of bdiGdb (1.07), with the folllowing
config file :

[INIT]
; Setup MMU info
WM32    0x000000f4  0x00000000  ;invalidate kernel  page table base
WM32    0x000000f8  0x00000000  ;invalidate process page table base
WM32    0x000000f0  0xc00000f4  ;invalidate page table base

[TARGET]
MMU         XLAT 0xC0000000     ;enable virtual address mode
PTBASE      0x000000f0          ;address where kernel/user stores
pointer to page table

the hhl 2.0 from monta vista with the following head_4xx.S

	/* Add helper information for the Abatron bdiGDB debugger.
	*/
	lis	r5, abatron_pteptrs@ha
	ori	r5, r5, abatron_pteptrs@l
	stw	r5, 0xf0(r0)	/* This much match your Abatron config */
	lis	r6, swapper_pg_dir@h
	ori	r6, r6, swapper_pg_dir@l
	tophys(r5, r5)
	stw	r6, 0(r5)

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

             reply	other threads:[~2001-11-06 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 13:26 ibm405gp [this message]
2001-11-06 18:29 ` Abatron Bdi2000 and 405GP Dan Malek
2001-11-07 23:00   ` 405GP interrupts tip and looking for a little console help Mark Pilon
2001-11-08  1:22     ` Phillip Lougher

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=3BE7E505.DC9DE6E8@laposte.net \
    --to=ibm405.linux@laposte.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).