From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Some RFCs about U-Boot's the generic FPGA support
Date: Wed, 22 Aug 2007 09:59:49 +0200 [thread overview]
Message-ID: <200708220959.49548.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <200708220928.36868.laurentp@cse-semaphore.com>
Hi Laurent,
you cannot imagine how many grey hair this bit naming and numbering convention
cost me. I learned to never use D0/7 when meaning MSB/LSB:-)
On Wednesday 22 August 2007 09:28, Laurent Pinchart wrote:
> > I must respectfully disagree. In my design, if I mirror in the code the
> > FPGA does NOT load. In a PPC, D0 is the MSB, NOT the LSB. In a Spartan 3
> > FPGA, D0 is the MSB, NOT the LSB. Therefore if you connect your bus
> > straight across between the PPC and the Spartan 3 FPGA, AND do mirroring
> > in the code, your FPGA will not load.
>
> I got a similar design, except that D0-D7 on the PPC are connected to D7-D0 on
> the FPGA. I'll go scold our hardware engineer :-)
Sometimes it's even worth as softwa/orkers to review schematics when you
know that you will get the board on your desk for writing software :-)
(But do not sign anything or the hardware engineer will scold you afterwards.)
> With a properly connected bus between the processor and the FPGA, bit reversal
> is thus not needed when loading a .bit file (fpga loadb) or a non mirrored
> PROM file (fpga load).
BTW, you can even load a .bit file using fpga load because the FPGA will
discard the header.
>
> For hardware with bit mirroring on the bus, I suggest either using a mirrored
> PROM file or mirroring the bit in the data write callback. I thus vote for
Ack
> removing bit mirroring in fpga_loadbitstream() and adding an explanation of
Ack. So all the malloc and the timeconsuming loop code will disappear. Yippi!
> this issue (either in the code or in the documentation) to prevent hardware
> mistakes in future designs.
Good idea. But do you think that hardware engineers will read through the
cmd_fpga.c file?
I will cleanup my changes and submit a patch soon.
Matthias
next prev parent reply other threads:[~2007-08-22 7:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 13:13 [U-Boot-Users] Some RFCs about U-Boot's the generic FPGA support Matthias Fuchs
2007-08-20 13:47 ` Laurent Pinchart
2007-08-20 15:46 ` Matthias Fuchs
2007-08-21 8:59 ` Laurent Pinchart
2007-08-21 10:46 ` Matthias Fuchs
2007-08-21 11:33 ` Laurent Pinchart
2007-08-21 12:53 ` Matthias Fuchs
2007-08-21 20:09 ` Bruce_Leonard at selinc.com
2007-08-22 7:28 ` Laurent Pinchart
2007-08-22 7:59 ` Matthias Fuchs [this message]
2007-08-22 8:23 ` Laurent Pinchart
2007-08-22 17:12 ` Bruce_Leonard at selinc.com
2007-08-22 17:09 ` Bruce_Leonard at selinc.com
2007-08-22 17:33 ` Jerry Van Baren
2007-08-22 18:03 ` [U-Boot-Users] Loading vxWorks by u-boot Leonid
2007-08-22 19:40 ` Chris Fester
2007-08-22 20:12 ` Leonid
2007-08-22 20:42 ` Chris Fester
2007-08-22 21:18 ` Leonid
2007-08-22 20:12 ` Frank
2007-08-23 6:27 ` [U-Boot-Users] Antw: " Niklaus Giger
2007-10-09 20:04 ` [U-Boot-Users] Some RFCs about U-Boot's the generic FPGA support Bruce_Leonard at selinc.com
2007-08-23 7:41 ` Matthias Fuchs
2007-08-23 18:59 ` Bruce_Leonard at selinc.com
2007-08-20 13:52 ` Wolfgang Denk
2007-08-20 18:46 ` Bruce_Leonard at selinc.com
2007-08-21 8:30 ` Matthias Fuchs
2007-08-21 19:37 ` Bruce_Leonard at selinc.com
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=200708220959.49548.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--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