public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andrew Dyer <amdyer@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [patch]virtex2 fix for bogus download error messages
Date: Wed, 12 Jan 2005 00:23:06 -0600	[thread overview]
Message-ID: <c166aa9f05011122234d01cfea@mail.gmail.com> (raw)

the virtex2 fpga download code watches for init going active during
a download of config data as an error condition.  init also goes active
after a configuration is finished in concert with the done signal.  The code
in cvs doesn't check for done active until all of the configuration
data is sent.

On our board the done signal would go active "early" as the
configuration data has a few extra pad bytes at the end, but the
code would print an error message even though the download
had suceeded.

The patch adds a check for done going active before checking
init.  If done is seen active the byte loading is cut short.  If debugging
is on it will print the count where it finished (8 bytes early for us).
It also changes the printf string to indicate the counts it prints are in
ticks and not mS.

I only have a system with 'slave parallel' style config interface, so I've
only patched that download version.  The virtex2 slave serial and spartan2
versions may have the same problem, I didn't have time to look.

-- 
Hardware, n.:
        The parts of a computer system that can be kicked.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: uboot-virtex2-patch.txt
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050112/b7b72ddb/attachment.txt 

             reply	other threads:[~2005-01-12  6:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12  6:23 Andrew Dyer [this message]
2005-09-24 21:41 ` [U-Boot-Users] [patch]virtex2 fix for bogus download error messages Wolfgang Denk

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=c166aa9f05011122234d01cfea@mail.gmail.com \
    --to=amdyer@gmail.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