From: Scott Anderson <scott_anderson@mvista.com>
To: James Don <JDon@spacebridge.com>
Cc: "''linuxppc-embedded@lists.linuxppc.org' '"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: advice please: virtex pro 2
Date: Thu, 08 May 2003 16:15:41 -0700 [thread overview]
Message-ID: <3EBAE51D.2C41C9CE@mvista.com> (raw)
In-Reply-To: DB0585C9F6F9D411BE8F00D0B7896A4CC0660A@SNCMAIL
James Don wrote:
> sorry ;-)
>
> does "it just works" mean plug and play with a reference design ... or do
> you mean it was so difficult to get running you know something else is wrong
> ... or does that mean you just got it working today?
Ah, sorry I was too terse. It means I used it on the ML300 for
debugging the kernel and drivers. I also used it to load the
kernel into memory so I didn't have to muck with the CompactFlash.
I mainly used its gdbserver interface, but also did use the telnet
interface at times. The BDI2000 config file I used was very terse.
The System ACE took care of initializing the hardware so by the
time the BDI got control, most things were pretty much taken care of.
Here's the INIT section from my file:
[INIT]
; init core register
WSPR 954 0x00000000 ;DCWR: Disable data cache write-thru
WSPR 1018 0x00000000 ;DCCR: Disable data cache
WSPR 1019 0x00000000 ;ICCR: Disable instruction cache
WSPR 982 0x00000000 ;EVPR: Exception Vector Table @0x00000000
; Setup MMU info
WM32 0x000000F0 0x00000000 ;invalidate page table base
Hope that was better,
Scott Anderson
scott_anderson@mvista.com MontaVista Software Inc.
(408)328-9214 1237 East Arques Ave.
http://www.mvista.com Sunnyvale, CA 94085
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-08 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 16:04 advice please: virtex pro 2 James Don
2003-05-08 23:15 ` Scott Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 17:11 Kerl, John
2003-05-07 10:38 James Don
2003-05-08 15:36 ` Scott Anderson
2003-05-08 16:53 ` Peter Ryser
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=3EBAE51D.2C41C9CE@mvista.com \
--to=scott_anderson@mvista.com \
--cc=JDon@spacebridge.com \
--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).