public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Question regarding FPGA firmware load in u-boot
Date: Mon, 22 Jun 2009 08:19:42 +0200	[thread overview]
Message-ID: <200906220819.42826.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <1245480010.3932.11.camel@swa-e6500>

Andr??,

> Dieter,
>
> On Fri, 2009-06-19 at 17:46 +0200, Dieter Kiermaier wrote:
> > Hello List,
> >
> > I want to boot a (Lattice) FPGA from u-boot by using Slave Serial
> > configuration on a Marvell Kirkwood device.
>
> Should be no problem as long as you'll have access to GPIO.

I'm working on it :)
But more likely I would have the SPI controller to do the serializing of the 
bitstream. But maybe this would be the second step.
>
> > As seen there is an (Xilinx and Altera) FPGA loader driver allready
> > available in u-boot.
> > Please can somebody explain how I have to provide a FPGA bitstream
> > image to u-boot?
>
> The easiest way is to reserve some unused flash sectors and use the
> first sector's start adress as arg for "fpga load".
>

I assume this will only work with NOR flash, right?
If I'm using NAND flash I have to copy the image to ram first?

> > It seems I have to create a image with mkimage?
>
> no - Lattice specififc bitstream can be stored in raw format.
> mkimage may be useful for update, but personally I prefer update via
> dedicated linux mtd partition.
>
> > This image have to be loaded into ram and the address has to be provided
> > to the load command?
>
> Usually an FPGA is *very* board specific. I'd suggest to use flash and
> create a corresponding mtd partition for linux, i.e. make it
> maintainable.
>
Seems to be a good way.
Is there a cmd in u-boot to read a file from a jffs2 filesystem inside a nand 
flash partition?

> > Is there a maintainer for the FPGA code inside u-boot?
> > I'm willing to contribute some extensions for Lattice FPGAs if I'm
> > successful!
>
> excellent - all you'll need is the Lattice specific bit toggle sequence.
>
> submitting a proper patch will surely do.
>
I'm trying to get an idea what place is the best to integrate the lattice 
architecture in to the fpga framework.
If I have any further questions - can I ask you again?

>
> Regards,
>
> Andr??

Many thanks for helping,
Dieter


>
> > Thanks to all,
> > Dieter
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
>
> MATRIX VISION GmbH, Talstra?e 16, DE-71570 Oppenweiler
> Registergericht: Amtsgericht Stuttgart, HRB 271090
> Gesch?ftsf?hrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner,
> Hans-Joachim Reich

  reply	other threads:[~2009-06-22  6:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 15:46 [U-Boot] Question regarding FPGA firmware load in u-boot Dieter Kiermaier
2009-06-20  6:40 ` André Schwarz
2009-06-22  6:19   ` Dieter Kiermaier [this message]
2009-06-22  8:46     ` André Schwarz
2009-06-22  9:00       ` Dieter Kiermaier
2009-06-22  9:17         ` André Schwarz
2009-06-22  9:36           ` Dieter Kiermaier
     [not found] <73173D32E9439E4ABB5151606C3E19E201D8E62C79@SC-VEXCH1.marvell.com>
2009-06-22  9:33 ` Dieter Kiermaier

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=200906220819.42826.dk-arm-linux@gmx.de \
    --to=dk-arm-linux@gmx.de \
    --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