public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Altera Stratix II support
Date: Thu, 17 May 2007 15:02:32 -0700	[thread overview]
Message-ID: <464CD0F8.6020304@ovro.caltech.edu> (raw)
In-Reply-To: <ffc2b1d40705171449v2367de9crdb0186157e37084b@mail.gmail.com>

Hi Liberty,

> I am already knee deep in adding Altera Stratix II support to the
> u-boot via the fpga command (currently xlinix & acex1k are
> supported)...
> 
> of course I will re-post when i am done.
> 
> My only question is,
> 
> Am i reinventing the wheel?
> Is it already implemented anywhere?
> 
> If i am, where can I find a reference to the work already done?
> 
> If not I will soon give you one :)

I haven't looked for it yet, but I plan to add support
too eventually (= months from now when I get boards).

I haven't looked at the code, but here's how I plan to
configure my FPGAs. Your method may be different, so
perhaps between us we can come up with a consistent API.

The board I am designing will contain an MPC8349E, and
Altera Stratix II system controller FPGA on the processor
local bus, and then 4 other programmable FPGAs. A
board placement PDF is here;

http://www.ovro.caltech.edu/~dwh/carma_board/carma_board_placement.pdf

and engineering documents are here

http://www.ovro.caltech.edu/~dwh/carma_board/

The system controller FPGA will boot from Flash, a MAX II
CPLD will configure it on power-up, and then it'll bring the
PPC out of reset, which will then boot through Flash located
off the system controller FPGA (hence the system controller
comes to life before the processor). The other four FPGAs
will be programmed as the application dictates.

So given U-Boot running, I'd imagine tftp'ing RBF
(raw binary format) files generated by Quartus over to the
board. I'd then copy the files to a block of memory which
maps in my system controller to a fast-passive-parallel (FPP)
programmer. That state machine then programs the FPGAs.
In Linux the same procedure would be hidden behind
a driver so I could dd the RBFs into /dev/fgpa_fpp or
/sys/.../firmware.

The point of mapping the FPP programmer into a block of
local bus memory addresses is so that I can use the MPC8349E
DMA controller to DMA the RBF files from SDRAM memory to the
programmer memory (eg. from files in a RAM filesystem).
According to the datasheet MPC8349E DMA controller won't
burst with a fixed destination address (FIFO mode), so I'll
just fake it out and let it DMA to what it thinks
is an incrementing address location.

How are you planning on programming your FPGA?

Cheers
Dave

  reply	other threads:[~2007-05-17 22:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 21:49 [U-Boot-Users] Altera Stratix II support eran liberty
2007-05-17 22:02 ` David Hawkins [this message]
2007-05-18  5:46   ` eran liberty
2007-05-18 15:52     ` David Hawkins
2007-05-31 23:10       ` eran liberty
2007-05-31 23:46         ` Wolfgang Denk
2007-06-04 20:09           ` eran liberty
2007-06-04 20:13             ` eran liberty
     [not found]               ` <ffc2b1d40706041316y7cb61972h1fba91d4ef220ea9@mail.gmail.com>
2007-06-04 20:19                 ` eran liberty
2007-06-04 20:25                   ` eran liberty
2007-06-04 20:26                     ` eran liberty
2007-06-04 20:30                       ` eran liberty
2007-06-04 20:32                         ` eran liberty
2007-06-05 21:42                   ` Andy Fleming
2007-06-05  5:35                 ` eran liberty
2007-06-05 21:11                   ` Andy Fleming
2007-06-06  5:41                     ` eran liberty
2007-06-06 15:44                       ` Andy Fleming
2007-06-06 17:23                         ` eran liberty
2007-06-01 16:47         ` David Hawkins

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=464CD0F8.6020304@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --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