4.11. Freescale i.MX¶
Freescale i.MX is traditionally very well supported under barebox. Depending on the SoC, there are different Boot Modes supported. Older SoCs up to i.MX31 support only the external Boot Mode. Newer SoCs can be configured for internal or external Boot Mode with the internal boot mode being the more popular mode. The i.MX23 and i.MX28, also known as i.MXs, are special. These SoCs have a completely different boot mechanism, see Freescale MXS instead.
4.11.1. Internal Boot Mode¶
The Internal Boot Mode is supported on:
- i.MX25
- i.MX35
- i.MX50
- i.MX51
- i.MX53
- i.MX6
- i.MX7
- i.MX8MQ
With the Internal Boot Mode, the images contain a header which describes
where the binary shall be loaded and started. These headers also contain
a so-called DCD table which consists of register/value pairs. These are
executed by the Boot ROM and are used to configure the SDRAM. In barebox,
the i.MX images are generated with the scripts/imx/imx-image
tool.
Normally it’s not necessary to call this tool manually, it is executed
automatically at the end of the build process.
The images generated by the build process can be directly written to an SD card:
# with Multi Image support:
cat images/barebox-freescale-imx51-babbage.img > /dev/sdd
# otherwise:
cat barebox-flash-image > /dev/sdd
The above will overwrite the MBR (and consequently the partition table) on the destination SD card. To preserve the MBR while writing the rest of the image to the card, use:
dd if=images/barebox-freescale-imx51-babbage.img of=/dev/sdd bs=1024 skip=1 seek=1
NOTE: MaskROM on i.MX8 expects image to start at +33KiB mark, so the following command has to be used instead:
dd if=images/barebox-nxp-imx8mq-evk.img of=/dev/sdd bs=1024 skip=33 seek=33
Or, in case of NAND:
dd if=images/barebox-nxp-imx8mq-evk.img of=/dev/nand bs=1024 skip=33 seek=1
The images can also always be started second stage:
bootm /mnt/tftp/barebox-freescale-imx51-babbage.img
4.11.1.1. Information about the imx-image
tool¶
The imx-image tool can be used to generate imximages from raw binaries. It requires an configuration file describing how to setup the SDRAM on a particular board. This mainly consists of a poke table. The recognized options in this file are:
Header:
soc <soctype> |
|
loadaddr <adr> | The address the binary is uploaded to |
dcdofs <ofs> | The offset of the image header in the image. This should be:
* 0x400 : MMC/SD, NAND, serial ROM, PATA, SATA
* 0x1000 : NOR Flash
* 0x100 : OneNAND |
Memory manipulation:
wm 8 <addr> <value> | write <value> into byte <addr> |
wm 16 <addr> <value> | write <value> into short <addr> |
wm 32 <addr> <value> | write <value> into word <addr> |
set_bits <width> <addr> <value> | set set bits in <value> in <addr> |
clear_bits <width> <addr> <value> | clear set bits in <value> in <addr> |
nop | do nothing (just waste time) |
<width> can be of 8, 16 or 32.
Checking conditions:
check <width> <cond> <addr> <mask> | Poll until condition becomes true.
with <cond> being one of:
* until_all_bits_clear
* until_all_bits_set
* until_any_bit_clear
* until_any_bit_set |
Some notes about the mentioned conditions.
until_all_bits_clear
waits until(*addr & mask) == 0
is trueuntil_all_bits_set
waits until(*addr & mask) == mask
is trueuntil_any_bit_clear
waits until(*addr & mask) != mask
is trueuntil_any_bit_set
waits until(*addr & mask) != 0
is true.
4.11.1.2. USB Boot¶
Most boards can be explicitly configured for USB Boot Mode or fall back
to USB Boot when no other medium can be found. The barebox repository
contains a USB upload tool. As it depends on the libusb development headers,
it is not built by default. Enable it explicitly in make menuconfig
and install the libusb development package. On Debian, this can be done
with apt-get install libusb-dev
. After compilation, the tool can be used
with only the image name as argument:
scripts/imx/imx-usb-loader images/barebox-freescale-imx51-babbage.img
4.11.2. External Boot Mode¶
The External Boot Mode is supported by the older i.MX SoCs:
- i.MX1
- i.MX21
- i.MX27
- i.MX31
- i.MX35
The External Boot Mode supports booting only from NOR and NAND flash. On NOR flash, the binary is started directly on its physical address in memory. Booting from NAND flash is more complicated. The NAND flash controller copies the first 2kb of the image to the NAND Controller’s internal SRAM. This initial binary portion then has to:
- Set up the SDRAM
- Copy the initial binary to SDRAM to make the internal SRAM in the NAND flash controller free for use for the controller
- Copy the whole barebox image to SDRAM
- Start the image
It is possible to write the image directly to NAND. However, since NAND flash can have bad blocks which must be skipped during writing the image and also by the initial loader, it is recommended to use the barebox_update - update barebox to persistent media command for writing to NAND flash.
4.11.3. i.MX boards¶
Not all supported boards have a description here. Many newer boards also do
not have individual defconfig files, they are covered by imx_v7_defconfig
or imx_defconfig
instead.
- 4.11.3.1. Amazon Kindle 3 “Kindle Keyboard” Model No. D00901
- 4.11.3.2. Amazon Kindle 4/5 (Wi-Fi/No-Touch, Touch and Paperwhite)
- 4.11.3.3. element14 WaRP7
- 4.11.3.4. Eukrea CPUIMX27
- 4.11.3.5. Garz+Fricke Cupid
- 4.11.3.6. Garz+Fricke Vincell LT
- 4.11.3.7. Ka-Ro TX25
- 4.11.3.8. Ka-Ro TX6x
- 4.11.3.9. NXP i.MX8MQ EVK Evaluation Board
- 4.11.3.10. DDR Configuration Code
- 4.11.3.11. Build Barebox
- 4.11.3.12. Boot Configuration
- 4.11.3.13. Phytec phyCARD-i.MX27
- 4.11.3.14. Phytec phyCORE-i.MX27
- 4.11.3.15. Phytec phyCORE-i.MX31 CPU module PCM-037
- 4.11.3.16. Phytec phyCORE-i.MX35
- 4.11.3.17. Synertronixx SCB9328
- 4.11.3.18. Wandboard