public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rick Stranberg <ras63@psu.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] TFTP retry count Infinite
Date: Fri, 22 Jun 2012 11:05:42 -0400	[thread overview]
Message-ID: <016501cd5088$7e212c50$7a6384f0$@edu> (raw)

Hello Everyone,

 

I'm new to this list and thought I would post a question.  We are developing
a FLASH-based board based on Micrel's KSZ9692 SOC that will run Linux
version 2.6.23.17.   Our desire is to be able to load a new Linux/rootfs
image via TFTP for testing without overwriting the current kernel/rootfs
stored in FLASH.

 

My original thought was to write a script using environmental variables.
The script would look for a mImage on a server and load it if it is there.
If we don't want to load an experimental linux/rootfs mImage, we would
simply do not have the file present on the server, and the script would
proceed to the next command having not found the file on the server.
However, when it gets to that point in the code, it continues to retry over
and over, and never gets past the 'File not Found' error.  

 

I looked in the README file and found the variable CONFIG_NET_RETRY_COUNT
and it seems to be set in a lot of files.  However, if this variable applies
to this, the script just ignores it and continues.

 

Does this parameter apply to this situation?  If not, what section of code
would I add/change to include this?  Not having modified Uboot, the task
seems to be daunting.  How would I begin?  Where would I start? 

 

Thanks a lot!

 

Regards,

Rick

 

 

 

             reply	other threads:[~2012-06-22 15:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 15:05 Rick Stranberg [this message]
2012-06-22 16:23 ` [U-Boot] TFTP retry count Infinite Wolfgang Denk
2012-06-22 17:22   ` Rick Stranberg
2012-06-22 18:17     ` 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='016501cd5088$7e212c50$7a6384f0$@edu' \
    --to=ras63@psu.edu \
    --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