public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ben Warren <bwarren@qstreams.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FPGA loading question
Date: Thu, 27 Sep 2007 13:36:42 -0400	[thread overview]
Message-ID: <46FBEA2A.3070806@qstreams.com> (raw)
In-Reply-To: <3972542e0709270910m2ab84a80td1017771b81af2bb@mail.gmail.com>

E Robertson wrote:
> On 9/27/07, Stefan Roese <sr@denx.de> wrote:
>   
>> Hi Matthias,
>>
>> On Thursday 27 September 2007, Matthias Fuchs wrote:
>>     
>>> What kind of CPU are you using? Please note that 4xx U-Boot ports have
>>> the cache disabled. Without cache booting a Spartan 3E in SS-mode
>>> may take very very :-(
>>>       
>> Only 44x have cache disabled. 40x has icache enabled.
>>
>> BTW: I'm still waiting for the patch to enable the cache on 44x systems... ;)
>>
>> Viele Gr??e,
>> Stefan
>>     
>
> I'm using an NXP ARM9 'A404 and can disable cache on my platform.  Due
> to my hardware fool-up, I'll have to use a bit banging method.
> I'm also concern about loading error and recovery and I'm considering
> instead to do the programming in the kernel. If there is a problem for
> some reason and the FPGA needs to be reloaded, I'll have to do it in
> the kernel anyway.
> I'm  not sure about embedding a bin file in the kernel driver either
> but It's worth pursuing.
>   
If your design can wait until Linux is booted before programming the 
FPGA, you have a world of possibilities available.  In my designs, I 
have a simple char driver with a 'write' method that bit-bangs the image 
in.  This way you can keep your image as a file in the file system and 
can add whatever encryption, wrapper or whatever your heart desires.  It 
makes trying different FPGA images a breeze.

regards,
Ben

  reply	other threads:[~2007-09-27 17:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 20:48 [U-Boot-Users] FPGA loading question E Robertson
2007-09-27 13:21 ` Matthias Fuchs
2007-09-27 15:47   ` Stefan Roese
2007-09-27 16:10     ` E Robertson
2007-09-27 17:36       ` Ben Warren [this message]
2007-09-27 18:01         ` E Robertson
2007-09-27 18:31           ` Ben Warren

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=46FBEA2A.3070806@qstreams.com \
    --to=bwarren@qstreams.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