public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Xilinx Spartan3 relocation code
Date: Tue, 21 Aug 2007 10:52:25 +0200	[thread overview]
Message-ID: <200708211052.25742.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <OF1CF35A58.C506D43F-ON8825733D.00604F3A-8825733D.00619C19@selinc.com>

Bruce,

what kind of bitstream file do you download to your FPGA?
A .bit File? In this case we should put the bit mirroring into the
wdata() callback or the *_sp_load() function, because the serial slave
download is fine without mirroring. Any way there is not need to malloc
a very huge amount of memory an do the mirroring on a buffer. This 
can be done on-the-fly during download.

Matthias

On Monday 20 August 2007 19:46, Bruce_Leonard at selinc.com wrote:
> Stefan,
> 
> > > > I fixed and added some things for the generic FPGA boot. Patches 
> will be
> > > > posted with the new board patch.
> 
> Sorry for the late reply, had a big BBQ this weekend for my anniversary 
> and haven't checked my e-mail in three or four days.  Could you please let 
> me know what your patches are going to look like?  I don't want to push up 
> any patches that will cover/conflict things you've got in your queue.
> 
> > > trouble getting the FPGA to program.  We're currently assuming that 
> our
> > > interface to the FPGA is broken, but if there's known issues in the
> > > generic code that would be nice to know :).
> 
> I finally figured out what stupid thing I was doing.  Both the FPGA and 
> the PPC are big endian, however if the processor is little endian the data 
> needs to be bit-swapped before going to the FPGA over SelectMap.  When I 
> was commenting out the code to do the bit-swapping (which we don't need to 
> do) I got over zealous by one line and wasn't initializing a pointer.  So 
> I was sending nothing but 0x24 to the FPGA.  Wonder why it didn't program? 
> :0
> 
> I'm going to try and come up with a clean way (probably a config option) 
> of doing or not doing the bit-swap thing in code.  If you're running a bit 
> endian system you really don't need or want to do it.  Little endian 
> systems, unless you're very carefull with your HW design, you want to do 
> it.  I'll have a patch for it in a couple of days.  I was thinking 
> something along the lines of "#define CFG_NO_SELECTMAP_BITSWAP".  If it's 
> not defined the code does the bit-swap, which is the way everything 
> currently works.  Or should it be a CONFIG instead?
> 
> Bruce
> 
> 

  reply	other threads:[~2007-08-21  8:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14 20:58 [U-Boot-Users] RFC: Xilinx Spartan3 relocation code Bruce_Leonard at selinc.com
2007-08-15 14:24 ` Matthias Fuchs
2007-08-15 17:25   ` Bruce_Leonard at selinc.com
2007-08-16  9:16     ` Matthias Fuchs
2007-08-16 16:37       ` Bruce_Leonard at selinc.com
2007-08-17  6:41         ` Stefan Roese
2007-08-20 17:46           ` Bruce_Leonard at selinc.com
2007-08-21  8:52             ` Matthias Fuchs [this message]
2007-08-21  9:04               ` Laurent Pinchart
2007-08-21 10:17                 ` Matthias Fuchs
2007-08-21 19:47                   ` Bruce_Leonard at selinc.com
2007-08-21 19:39               ` Bruce_Leonard at selinc.com
2007-08-22  6:53                 ` Matthias Fuchs
2007-08-17 11:03         ` Matthias Fuchs

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=200708211052.25742.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