linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "alayrac" <christophe.alayrac@cresitt.com>
To: "'Peter Mendham'" <petermendham@computing.dundee.ac.uk>,
	<linuxppc-embedded@ozlabs.org>
Subject: RE : Using Linux on ML405: Some basic questions
Date: Tue, 28 Nov 2006 09:09:20 +0100	[thread overview]
Message-ID: <000001c712c4$8252e870$c900a8c0@CRESITTLAB> (raw)
In-Reply-To: <456AF9A5.70301@computing.dundee.ac.uk>

Peter,

I'will try to help you on systemace only.

XACCACE can load an ace file from a FAT16 partition into the FPGA fabric
using boundary scan chain (JTAG).

First of all it loads the FPGA fabric, the bitsream file. If you have a
look in Applications in the ML405 project there should be a bootloop
code marked as activated and as used to initialized BRAM.=20
This code is loaded at address 0xFFFFFFFC (where there is a BRAM) wich
is the reset address of the powerpc. Thus after bitstream dowload, the
powerpc is in an infinite loop so that it won't try to access any
peripheral, especially memory.

Then systemeace will downlaod the elf file, in your case the kernel
image (it could be standalone apllication as well as uboot).

To do so the systemace take controle of powerpc through jtag chain (just
as you are dowing with the JTAG cable when you are debugging you code on
powerpc inside the FPGA). In fact the FPGA fabric include a JTAG daisy
chain, so that the PowerPC is seen on JTAG chain after FPGA
initialization (if you start an xps design from scratch you will see in
the wizard that you can select the debug chain of your powerpc from JTAG
or stub...)

So just to finish, as soon as system ace can see the PowerPC through
JTAG, it can see and use all powerpc peripherals and espaecially the
memory in your case. So it read the destination address of the elf image
to laod (from the elf file itself) and just copy the data at the
specific address. Then it put the PC at this address and sart the
powerpc.

Regards.

Chris

CRESITT INDUSTRIE
12 Rue de Blois, BP6744
45067 ORLEANS Cedex 2
Tel : 02.38.49.45.59
Fax :02.38.49.45.55
Email : christophe.alayrac@cresitt.com=20
Web : http://www.cresitt.com


<----> -----Message d'origine-----
<----> De=A0: linuxppc-embedded-
<----> bounces+christophe.alayrac=3Dcresitt.com@ozlabs.org
[mailto:linuxppc-
<----> embedded-bounces+christophe.alayrac=3Dcresitt.com@ozlabs.org] De =
la
<----> part de Peter Mendham
<----> Envoy=E9=A0: lundi 27 novembre 2006 15:44
<----> =C0=A0: linuxppc-embedded@ozlabs.org
<----> Objet=A0: Using Linux on ML405: Some basic questions
<---->=20
<----> Dear all,
<---->=20
<----> I am experimenting with Linux on an ML405 dev board in
preparation
<----> for
<----> designing a board of our own.  I am not massively knowledgeable
about
<----> Linux internals and am learning as I go along.  At the moment I'm
<----> working with a 2.4.26 kernel and the demonstration hardware
<----> configuration.  I have built the kernel and created a new root
file
<----> systems using buildroot/busybox.  Most of the time I have a
working
<----> system :)
<---->=20
<----> I have a few questions, I was wondering if someone could help me
out:
<---->=20
<----> 1) I don't really understand how the kernel image gets loaded
from
<----> the
<----> .ace file.  I've seen articles which say that the SystemAce
<----> controller
<----> puts the kernel image directly into RAM, but on inspection of the
<----> datasheet I can't see any capability other that JTAG programming
and
<----> acting as a slave to a processor.  Can anyone explain the way
this
<----> works?
<---->=20
<----> 2) I'm trying to simplify the kernel as much as possible, is
there a
<----> way
<----> to do without devfs?  If I don't have devfs do I need an initrd?
If
<----> so,
<----> what do I need to put on the initrd, can it just be a minimal
/dev
<----> directory?
<---->=20
<----> 3) I will eventually be wanting tri-mode ethernet support,
ideally
<----> under
<----> a 2.6 kernel.  I've been trying to follow the discussions on this
<----> mailing list with respect to the support for the tri-mode MAC and
<----> scatter gather/DMA support.  Can anyone summarise what sort of
stage
<----> this is at? Is auto-negotiation supported? Once I get past the
<----> hurdles I
<----> have at the moment my next step is to attempt incorporating the
tri-
<----> mode
<----> IP and getting it working under Linux.  If there's anything I can
do
<----> to
<----> help the effort at that point I'd be glad to put in some time.
<---->=20
<----> Many thanks in advance,
<----> -- Peter
<---->=20
<----> _______________________________________________
<----> Linuxppc-embedded mailing list
<----> Linuxppc-embedded@ozlabs.org
<----> https://ozlabs.org/mailman/listinfo/linuxppc-embedded

  reply	other threads:[~2006-11-28  8:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 14:43 Using Linux on ML405: Some basic questions Peter Mendham
2006-11-28  8:09 ` alayrac [this message]
2006-11-28 10:52   ` RE : " Peter Mendham
2006-11-28 13:39     ` RE : " alayrac
2006-11-28 15:03     ` Magnus Hjorth
2006-11-28 16:13       ` Peter Mendham
2006-11-28 15:56     ` Andrei Konovalov
     [not found] <8506C3905ED0764F889ADEB33E3A9E8062CF4F@MAIA.scopus.net>
2006-11-28 10:57 ` Peter Mendham
2007-01-17 22:39   ` Using Linux on an FX60 board RichardL

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='000001c712c4$8252e870$c900a8c0@CRESITTLAB' \
    --to=christophe.alayrac@cresitt.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=petermendham@computing.dundee.ac.uk \
    /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).