diff options
| author | Stefan Agner <stefan.agner@toradex.com> | 2014-10-16 09:49:34 +0200 |
|---|---|---|
| committer | Stefan Agner <stefan@agner.ch> | 2015-04-14 09:08:09 +0200 |
| commit | b004926168f3bc15f9e26f14c16ae60a252b1304 (patch) | |
| tree | cc017fb1d5efa5df8cec951fa08ff01c787d22cf /include/configs/colibri_vf.h | |
| parent | 55380b56efef3f3bb1dc9c128c3ce2be56e653a3 (diff) | |
imx: add writebcb command
Add writebcb command which creates a NAND Boot Configuration Block
(BCB) at the beginning of the active flash device. The BCB stores
the information for the SoC internal boot ROM where the application
with a valid IVT header can be found on the NAND device. The first
two argument of the command need an offset of the NAND device where
the primary and secondary application can be found.
Typically, U-Boot is the application which gets loaded by the boot
ROM. Hence, the offset address need to be the address where U-Boot
(u-boot.imx along with a 0x400 long prefix) is stored on the device.
At least one location is mandatory.
Currently only the FCB (Firmware Configuration Block) is written to
the device. The DBBT (Discovered Bad Block Table) is optional and
not created by writebcb currently.
Diffstat (limited to 'include/configs/colibri_vf.h')
| -rw-r--r-- | include/configs/colibri_vf.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/configs/colibri_vf.h b/include/configs/colibri_vf.h index a6d38635f9..a30eff80ea 100644 --- a/include/configs/colibri_vf.h +++ b/include/configs/colibri_vf.h @@ -51,6 +51,7 @@ /* NAND support */ #define CONFIG_CMD_NAND +#define CONFIG_CMD_WRITEBCB #define CONFIG_SYS_MAX_NAND_DEVICE 1 #define CONFIG_SYS_NAND_BASE NFC_BASE_ADDR |