diff options
| author | Mike Dunn <mikedunn@newsguy.com> | 2013-06-18 11:08:51 -0700 |
|---|---|---|
| committer | Marek Vasut <marex@denx.de> | 2013-06-22 15:25:28 +0200 |
| commit | 3497d43215b6919e680fefe59b38b71516adf2a0 (patch) | |
| tree | f062538ff8248f4897bc89de86bc5b385c5f1942 /arch | |
| parent | 0dc0e846f3634fcc728f086ae1b7a4b76294e4c9 (diff) | |
| download | u-boot-imx-3497d43215b6919e680fefe59b38b71516adf2a0.zip u-boot-imx-3497d43215b6919e680fefe59b38b71516adf2a0.tar.gz u-boot-imx-3497d43215b6919e680fefe59b38b71516adf2a0.tar.bz2 | |
pxa: palmtreo680 flash programming utility
This adds a userspace linux utility that writes the u-boot image to an mtd
partition on the docg4 nand flash.
A special utility is required to do this because u-boot is partially loaded by
an initial program loader (IPL) that is permanently programmed to the boot
region of the flash. This IPL expects the image to be written in a unique
format. The characteristics of this format can be summarized as follows:
- Flash blocks to be loaded must have a magic number in the oob bytes of the
first page of the block.
- Each page must be written redundantly in the subsequent page.
- The integrated flash controller's "reliable mode" is used, requiring that
alternate 2k regions (4 pages) are skipped when writing.
For these reasons, a u-boot image can not be written using nandwrite from
mtd-utils.
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions