From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FPGA mess
Date: Thu, 6 Mar 2008 07:53:42 +0100 [thread overview]
Message-ID: <200803060753.43184.sr@denx.de> (raw)
In-Reply-To: <47CECD71.1080305@matrix-vision.de>
Andre,
On Wednesday 05 March 2008, Andre Schwarz wrote:
> you're listed as maintainer for the alpr board.
Correct. But I didn't use this board for quite some time.
> It's the only board that uses the ACEX1K.c file for FPGA loading...
Does it? To use this file you have to define CONFIG_FPGA_ACEX1K. I don't see
it defined anywhere in the whole U-Boot tree. So perhaps this code is not
used at all.
> I'm quite sure there are many boards with Altera FPGAs outside and can't
> believe they have all mounted
> platform flashes and therefore don't use u-boot for loading the FPGA.
> Nevertheless those board don't show up in the tree. Maybe they all keep
> their own patches like me ...
Maybe. I suggest you start pushing your code to change this situation. :)
> There are some points that doesn't seem to work out very well in general.
> This is where some questions come up (top->down) :
>
> common/cmd_fpga:
> In function do_fpga there's a used environment variable "fpgadata" that
> obviously stores the location of the bitstream.
> What sense does this make if the "data_size" parameter (=arg4) is _not_
> optional ?
> Instead the command "fpga load 0 0x..." leads to a load function with
> zero length.
> The user always has to supply all 4 args (load, nr, data, size).
> Of course the loading function could use the pre-defined bitstream size
> from the header or the device struct...
I have to admit that I don't understand what you are really asking here.
Please ask more specific questions. Or send a patch to fix something that
is "broken".
> common/altera.c
> What's that ACEX1K ? Isn't it a Cyclone chip and should use that interface
> ? Why does this need special treatment throughout the interface ?
I didn't introduce this file. Perhaps we should ask the author who committed
this code.
> include/ACEX1K.h
> Obviously there are some confusions about the various file formats and
> sizes that can be output
> from Altera's SoPC Builder. Compression is also possible with
> de-compression on the fly during load ...
> Of course the defined file sizes should match a raw bit file that
> represents the true size of the device.
>
> Why is ACEX1K and Cyclone not merged ?
No idea. If you have some fixes, please send patches.
> Does _any_ real board use the Altera path ? scanning the config files
> ... no.
alpr seems to use the cyclone2.c code.
> CYC2_ps_load in common/cyclon2.c the nCONFIG pin is never de-asserted
> during preparation. This code can't work.
No idea. I have to admit, that I didn't implement the FPGA booting on this
board. But it seems to work fine.
> Is there any interest in getting this fixed ?
Sure.
> What about Liberty's Stratix code ? It's living and working !
Sorry, but I have no clue what "Liberty's Stratix code" is.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-03-06 6:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 16:42 [U-Boot-Users] FPGA mess Andre Schwarz
2008-03-06 6:53 ` Stefan Roese [this message]
[not found] ` <47CFC43C.2060401@matrix-vision.de>
2008-03-06 14:24 ` Stefan Roese
2008-03-06 17:37 ` Heiko Schocher
2008-03-06 17:50 ` Andre Schwarz
2008-03-06 19:46 ` Heiko Schocher
2008-03-06 20:41 ` André Schwarz
2008-03-07 6:13 ` Heiko Schocher
2008-03-06 19:47 ` Stefan Roese
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=200803060753.43184.sr@denx.de \
--to=sr@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.