From: Robert Schwebel <robert@schwebel.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Production und U-boot
Date: Sat, 31 Jan 2004 08:25:01 +0100 [thread overview]
Message-ID: <20040131072501.GC32127@pengutronix.de> (raw)
In-Reply-To: <37FB7AA6F5F9814FB634A7BF4C35A6F501213E4E@ESEALNT442.al.sw.ericsson.se>
On Thu, Jan 29, 2004 at 12:45:17PM +0100, Matias Sundman (AL/EAB) wrote:
> Now what I am thinking of is to program U-boot to recognize a pin in
> the backplane, if the pin is set the board is in a production facility
> - BOOTP and a TFTP download of the flash image shall be done, and
> burned in flash ( by U-boot ). The pin is set by production staff.
I've done similar things with our boards, mostly by setting a
bootcmd_foobar variable in the environment (from misc_init_r()) when the
pin is set and setting bootcmd to 'run bootcmd_foobar' in that case;
this way you can test your scenario by running it manually from the
command line.
> If it is not set U-boot shall start a Image from flash ( Containing
> Linux and a Rootfile system ) since it is in a "sharp" environment.
The other thing I'm currently implementing is to setup a generic
scripting mechanism which tests and flashed boards with an "expect"
script - this works pretty well and you can also perform some test cases
with U-Boot and Linux while setting up the board, including
autogenerated test reports.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hornemannstra?e 12, 31137 Hildesheim, Germany
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4
next prev parent reply other threads:[~2004-01-31 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 11:45 [U-Boot-Users] Production und U-boot Matias Sundman
2004-01-31 7:25 ` Robert Schwebel [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-30 7:31 Matias Sundman
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=20040131072501.GC32127@pengutronix.de \
--to=robert@schwebel.de \
--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