From: Peter Barada <peterb@logicpd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OT Flashing high volume of devices
Date: Thu, 18 Nov 2010 15:50:52 -0500 [thread overview]
Message-ID: <4CE591AC.3050506@logicpd.com> (raw)
In-Reply-To: <20101118203933.EAD3714E647@gemini.denx.de>
On 11/18/2010 03:39 PM, Wolfgang Denk wrote:
> Dear Hamilton Vera,
>
> In message<AANLkTim-w-ijiNpPMsmUM++9MwWsxbOntOdPb5HH6D0Z@mail.gmail.com> you wrote:
>
>> Hi folks this is probably out off topic, we are happily using uboot in
>> our devices but I am wondering about the procedures to flash/deploy
>> uboot (or any bootloader) in a high scale production environment.
>>
> What sort of boot device are you using? NOR flash? NAND flash?
>
> For high volumes, you can get pre-programmed flash chips, so you have
> a running system when the boards come from assembly.
>
Indeed, pre-programing flash used in the board assembly is the way to
go. Most manufacturers make the initial image a self-test program that
initially exercise all I/O (the board is initially powered up attached
to a test/burn-in fixture), and if the test succeeds, then re-burns the
flash with the production image(u-boot/Linux/rootfs or otherwise) that
is part of the test-image. If the test fails, then the board is
rejected and reworked to diagnose/fix found issues (cold-solder, lifted
pins, etc).
Speed of testing/initial burn-in can be increased by running more than
one fixture in parallel.
--
Peter Barada
peterb at logicpd.com
next prev parent reply other threads:[~2010-11-18 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 20:25 [U-Boot] OT Flashing high volume of devices Hamilton Vera
2010-11-18 20:39 ` Wolfgang Denk
2010-11-18 20:50 ` Peter Barada [this message]
2010-11-18 20:52 ` Hamilton Vera
2010-11-18 21:52 ` Grant Edwards
2010-11-19 12:33 ` Hamilton Vera
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=4CE591AC.3050506@logicpd.com \
--to=peterb@logicpd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.