diff --git a/Documentation/boards/imx/Element14-WaRP7.rst b/Documentation/boards/imx/Element14-WaRP7.rst deleted file mode 100644 index df14f84..0000000 --- a/Documentation/boards/imx/Element14-WaRP7.rst +++ /dev/null @@ -1,54 +0,0 @@ -element14 WaRP7 -=============== - -This CPU card is based on an NXP i.MX7S SoC. - -Supported hardware -================== - -- NXP PMIC PFUZE3000 -- Kingston 08EMCP04-EL3AV100 eMCP (eMMC and LPDDR3 memory in one package) - - 8 GiB eMMC Triple-Level cell NAND flash, eMMC standard 5.0 (HS400) - - 512 MiB LPDDR3 SDRAM starting at address 0x80000000 - -Bootstrapping barebox -===================== - -The device boots in internal boot mode from eMMC and is shipped with a -vendor modified u-boot imximage. - -Barebox can be used as a drop-in replacement for the shipped bootloader. - -The WaRP7 IO Board has a double DIP switch where switch number two defines the -boot source of the i.MX7 SoC:: - - +-----+ - | | - | | O | <--- on = high level - | | | | - | O | | <--- off = low level - | | - | 1 2 | - +-----+ - -Bootsource is the internal eMMC:: - - +-----+ - | | - | O | | - | | | | - | | O | <---- eMMC - | | - | 1 2 | - +-----+ - -Bootsource is the USB:: - - +-----+ - | | - | O O | <---- USB - | | | | - | | | | - | | - | 1 2 | - +-----+ diff --git a/Documentation/boards/imx/Garz-Fricke-Cupid.rst b/Documentation/boards/imx/Garz-Fricke-Cupid.rst deleted file mode 100644 index 4520048..0000000 --- a/Documentation/boards/imx/Garz-Fricke-Cupid.rst +++ /dev/null @@ -1,9 +0,0 @@ -Garz+Fricke Cupid -================= - -This CPU card is based on a Freescale i.MX35 CPU. The card is shipped with: - - * 256MiB NAND flash - * 128MiB synchronous dynamic RAM - -see http://www.garz-fricke.com/cupid-core_de.html for more information diff --git a/Documentation/boards/imx/Garz-Fricke-Vincell.rst b/Documentation/boards/imx/Garz-Fricke-Vincell.rst deleted file mode 100644 index 58ab0ab..0000000 --- a/Documentation/boards/imx/Garz-Fricke-Vincell.rst +++ /dev/null @@ -1,43 +0,0 @@ -Garz+Fricke Vincell LT -====================== - -This CPU card is based on a Freescale i.MX53 CPU. The card is shipped with: - - * 512MiB NAND flash - * 512MiB synchronous dynamic RAM - * microSD slot - -see http://www.garz-fricke.com/en/products/embedded-systems/single-board-computer/ia-0086r/ for more information - - -Bootstrapping barebox -===================== - -The Vincell is shipped with the RedBoot bootloader. To replace RedBoot with -barebox, you first need to connect a serial console to the device. - -UART1 is located on the Molex header X39. When the Vincell is lying on the -display, then Pin 1 on the header is in the lower right: - - * Pin 1 - GND - * Pin 2 - TXD1 - * Pin 3 - RXD1 - -If everything is connected right, RedBoot shows up on the console. - -factory_bootstrap ------------------ - -Turn on the board and abort the boot process with ``Ctrl-C``. -Configure RedBoot so that it finds the barebox image on your TFTP server. -Execute ``fc`` and change the network setup according to your environment. -Be sure to copy the `Boot script` line to the prompt, otherwise it will be -set empty. The network setup can be validated with ``ping -h ``. -If the network setup is working properly, barebox can be loaded into memory:: - - load -v -r -b 0x80100000 barebox-guf-vincell-lt.img - exec - -Once in barebox, the bootloader can now be persisted to NAND:: - - barebox_update -t nand /mnt/tftp/barebox-guf-vincell-lt.img`` diff --git a/Documentation/boards/imx/Karo-TX25.rst b/Documentation/boards/imx/Karo-TX25.rst deleted file mode 100644 index 756c99d..0000000 --- a/Documentation/boards/imx/Karo-TX25.rst +++ /dev/null @@ -1,10 +0,0 @@ -Ka-Ro TX25 -========== - -Building the bootloader image for this target is covered by the ``imx_defconfig`` -multiimage configuration if the ``System Type`` menu entry ``Ka-Ro TX25`` -is enabled. - -Use the corresponding ``barebox-karo-tx25.img`` for external NAND boot. -Use the corresponding ``barebox-karo-tx25-internal.img`` for internal NAND, USB -or SD card boot. diff --git a/Documentation/boards/imx/Karo-TX6.rst b/Documentation/boards/imx/Karo-TX6.rst deleted file mode 100644 index 8dd26b5..0000000 --- a/Documentation/boards/imx/Karo-TX6.rst +++ /dev/null @@ -1,13 +0,0 @@ -KaRo TX6x -========= - -This CPU cards are based on a Freescale i.MX6 SoC. -There are currently six variants of this module, that are distinguished -by the suffix: 'Q' use an i.MX6Q and 'U' an i.MX6DL. - -The TX6U-801x modules are shipped with: - - * 128MiB NAND flash - * 1024MiB DDR3 SDRAM - -see http://www.karo-electronics.de/tx6.html for more information diff --git a/Documentation/boards/imx/Phytec-phyCARD-i.MX27.rst b/Documentation/boards/imx/Phytec-phyCARD-i.MX27.rst deleted file mode 100644 index d5d3837..0000000 --- a/Documentation/boards/imx/Phytec-phyCARD-i.MX27.rst +++ /dev/null @@ -1,8 +0,0 @@ -Phytec phyCARD-i.MX27 -===================== - -Building the bootloader image for this target is covered by the ``imx_defconfig`` -multiimage configuration if the ``System Type`` menu entry ``phyCard-i.MX27`` -is enabled. - -Use the corresponding ``barebox-phytec-phycard-imx27.img`` file for this target. diff --git a/Documentation/boards/imx/Phytec-phyCORE-i.MX27.rst b/Documentation/boards/imx/Phytec-phyCORE-i.MX27.rst deleted file mode 100644 index 4b40be7..0000000 --- a/Documentation/boards/imx/Phytec-phyCORE-i.MX27.rst +++ /dev/null @@ -1,8 +0,0 @@ -Phytec phyCORE-i.MX27 -===================== - -Building the bootloader image for this target is covered by the ``imx_defconfig`` -multiimage configuration if the ``System Type`` menu entry ``phyCORE-i.MX27`` -is enabled. - -Use the corresponding ``barebox-phytec-phycore-imx27.img`` file for this target. diff --git a/Documentation/boards/imx/Phytec-phyCORE-i.MX31.rst b/Documentation/boards/imx/Phytec-phyCORE-i.MX31.rst deleted file mode 100644 index 6c05bcd..0000000 --- a/Documentation/boards/imx/Phytec-phyCORE-i.MX31.rst +++ /dev/null @@ -1,41 +0,0 @@ -Phytec phyCORE-i.MX31 CPU module PCM-037 -======================================== - -The CPU module --------------- - -http://www.phytec.eu/europe/products/modules-overview/phycore/produktdetails/p/phycore-imx31-2.html - -This CPU card is based on a Freescale i.MX31 CPU. The card in -configuration -0000REU is shipped with: - - * 128 MiB synchronous dynamic RAM (DDR type) - * 64 MiB NAND flash - * 32 MiB NOR flash - * 512 kiB SRAM - * 4kiB EEPROM - * MMU, FPU - * Serial, Ethernet, USB (OTG), I2C, SPI, MMC/SD/SDIO, PCMCIA/CF, RTC - -Supported baseboards --------------------- - -Supported baseboards are: - * Silica / Phytec PCM-970 via phyMAP-i.MX31, PMA-001 - -How to get barebox for 'Phytec's phyCORE-i.MX31' ------------------------------------------------- - -Using the default configuration:: - - make ARCH=arm pcm037_defconfig - -Build the binary image:: - - make ARCH=arm CROSS_COMPILE=armv5compiler - -**NOTE:** replace ''armv5compiler'' with your ARM v5 cross compiler, - e.g.: ''arm-1136jfs-linux-gnueabi-'' - -The resulting binary image to be flashed will be ``barebox.bin``, whereas -the file named just ``barebox`` is an ELF executable for ARM. diff --git a/Documentation/boards/imx/Phytec-phyCORE-i.MX35.rst b/Documentation/boards/imx/Phytec-phyCORE-i.MX35.rst deleted file mode 100644 index adf5d26..0000000 --- a/Documentation/boards/imx/Phytec-phyCORE-i.MX35.rst +++ /dev/null @@ -1,7 +0,0 @@ -Phytec phyCORE-i.MX35 -===================== - -Building the bootloader image for this target is covered by the ``phytec-phycore-imx35_defconfig``. - -Use the corresponding ``barebox.bin`` file for this target. This image can be -used for booting in ``internal mode`` from NAND or NOR memory. diff --git a/Documentation/boards/imx/Wandboard.rst b/Documentation/boards/imx/Wandboard.rst deleted file mode 100644 index 574318a..0000000 --- a/Documentation/boards/imx/Wandboard.rst +++ /dev/null @@ -1,21 +0,0 @@ -Wandboard -========= - -The Wandboard is a carrier board available with three different -System-on-Module options, the Wandboard Solo (i.MX6S, 512MiB DDR3), -the Wandboard Dual (i.MX6DL, 1GiB DDR3) and Wandboard Quad (i.MX6Q, 2GiB DDR3). - -The device boots from the SD card slot on the System-on-Module board, it -will not boot from the slot on the carrier board. - -To boot barebox on any wandboard, build imx_v7_defconfig -and copy the barebox imx-image to the i.MX boot location of a SD card, e.g. -dd bs=1024 skip=1 seek=1 if=images/barebox-imx6-wandboard.img of=/dev/mmcblk0 - -Only one image exists, supporting all three Wandboard variants, barebox will -detect the Wandboard variant depending on the SoC variant. -This image is only usable for SD-boot. It will not boot via imx-usb-loader. - -Connect to the serial port using a null-modem cable to get console access. - -For further documentation, including board schematics see http://wandboard.org/ diff --git a/Documentation/boards/imx/amazon-kindle-3.rst b/Documentation/boards/imx/amazon-kindle-3.rst new file mode 100644 index 0000000..dffb7ef --- /dev/null +++ b/Documentation/boards/imx/amazon-kindle-3.rst @@ -0,0 +1,32 @@ +Amazon Kindle 3 "Kindle Keyboard" Model No. D00901 +================================================== + +This e-book reader is based on a Freescale i.MX35 SOC. +The device is equiped with: + +* 256MiB synchronous dynamic RAM +* 4GiB eMMC +* a MC13892 PMIC + +The device boots in internal boot mode from eMMC and is shipped with a +vendor modified u-boot imximage. + +To upload and run a new bootloader the device can be put into USB-downloader +mode by the SOC microcode when Vol+ is pressed during startup. A new USB +device "SE Blank RINGO" should appear, barebox may be uploaded using + +:: + + $ scripts/imx/imx-usb-loader barebox.imximg + +Note: a USB serial ACM console will be launched by a barebox init script +when the cursor select key is pressed during startup (e.g. before running +imx-usb-loader) + +Barebox may be used as drop-in replacement for the shipped bootloader. +When installing the barebox imximg on the eMMC take care not to overwrite +the partition table and vendor supplied serial numbers stored on the eMMC. +e.g. just write the imx-header and the application section:: + + memcpy -b -s barebox.imximg -d /dev/disk0.imx_header 1024 0 1024 + memcpy -b -s barebox.imximg -d /dev/disk0.self 4096 0 195584 diff --git a/Documentation/boards/imx/amazon-kindle-4-5.rst b/Documentation/boards/imx/amazon-kindle-4-5.rst new file mode 100644 index 0000000..bc6bf26 --- /dev/null +++ b/Documentation/boards/imx/amazon-kindle-4-5.rst @@ -0,0 +1,69 @@ +Amazon Kindle 4/5 Model No. D01100, D01200 and EY21 +=================================================== + +The Kindle Model No. D01100 (Kindle Wi-Fi), D01200 (Kindle Touch) +and EY21 (Paperwhite) are refered as the Kindle 4th and 5th generation. +Those e-book readers share a common set of hardware: + +* a Freescale i.MX50 SOC +* 2 or 4GiB eMMC +* a MC13892 PMIC + +The older readers D01100 and D01200 use 256MiB of LPDDR1, +while the newer EY21 uses 256MiB of LPDDR2. + +The devices boot up in internal boot mode from an eMMC boot partition and +are shipped with a vendor modified u-boot imximage based on u-boot v2009.08. + +To upload and run a new bootloader the older devices can be put into +USB-downloader mode by the SOC microcode when a specific key is pressed during +startup: + +* the fiveway down button on the model D01100 +* the home button on model D01200 + +A new USB device "NS Blank CODEX" should appear, barebox may be uploaded using + +:: + + $ scripts/imx/imx-usb-loader barebox-kindle-d01100.img + $ scripts/imx/imx-usb-loader barebox-kindle-d01200.img + +Hint: keep the select button pressed down to get the barebox USB console. + +Barebox may be used as drop-in replacement for the shipped bootloader, when +the imximg fits into 258048 bytes. When installing the barebox imximg on +the eMMC, take care not to overwrite the vendor supplied serial numbers stored +on the eMMC, +e.g. for the D01100 just write the imx-header and the application section:: + + loady -t usbserial + memcpy -b -s barebox-kindle-d01100.img -d /dev/disk0.boot0.imx_header 1024 0 2048 + memcpy -b -s barebox-kindle-d01100.img -d /dev/disk0.boot0.self 4096 0 253952 + +Note: a USB serial ACM console will be launched by a barebox init script +when + +* the cursor select key is pressed during startup of model D01100 +* the home button is pressed within a second after startup of model D01200. + If you press the home button during startup, you will enter USB boot mode. +* the EY21 has no keys to press, a USB console will be launched for 10s. + +This device is battery-powered and there is no way to switch the device off. +When the device is inactive, the kindle software will first reduce the +power consumption to a few milliamps of battery power, after some minutes +the power consumption is further reduced to about 550 microamps. Switching +on iomux pullups may significantly reduce your standby-time. + +Hints to reduce the build image size +------------------------------------ + +Note that a drop-in replacement barebox imximage must not exceed 258048 bytes +since the space behind it is in use. Hence, don't build in drivers and FS +that are not required, e.g. +``NET, DISK_AHCI, DISK_INTF_PLATFORM_IDE, DISK_ATA, VIDEO, PWM, LED, +USB_STORAGE, USB_ULPI, NAND, MTD_UBI, FS_UBIFS, MFD_MC34704, MFD_MC9SDZ60, +MFD_STMPE, EEPROM_AT25, EEPROM_AT24, KEYBOARD_GPIO, PARTITION_DISK_EFI`` + +Also unselect support for other boards to get rid of their dependencies. +Further select ``IMAGE_COMPRESSION_XZKERN``. diff --git a/Documentation/boards/imx/amazon-kindle-mx50.rst b/Documentation/boards/imx/amazon-kindle-mx50.rst deleted file mode 100644 index 1e71cd2..0000000 --- a/Documentation/boards/imx/amazon-kindle-mx50.rst +++ /dev/null @@ -1,58 +0,0 @@ -Amazon Kindle 4/5 Model No. D01100, D01200 and EY21 -=================================================== - -The Kindle Model No. D01100 (Kindle Wi-Fi), D01200 (Kindle Touch) -and EY21 (Paperwhite) are refered as the Kindle 4th and 5th generation. -Those e-book readers share a common set of hardware: - -* a Freescale i.MX50 SOC -* 2 or 4GiB eMMC -* a MC13892 PMIC - -The older readers D01100 and D01200 use 256MiB of LPDDR1, -while the newer EY21 uses 256MiB of LPDDR2. - -The devices boot up in internal boot mode from an eMMC boot partition and -are shipped with a vendor modified u-boot imximage based on u-boot v2009.08. - -To upload and run a new bootloader the older devices can be put into -USB-downloader mode by the SOC microcode when a specific key is pressed during -startup: -* the fiveway down button on the model D01100 -* the home button on model D01200 -A new USB device "NS Blank CODEX" should appear, barebox may be uploaded using -$ scripts/imx/imx-usb-loader barebox-kindle-d01100.img -$ scripts/imx/imx-usb-loader barebox-kindle-d01200.img -Hint: keep the select button pressed down to get the barebox USB console. - -Barebox may be used as drop-in replacement for the shipped bootloader, when -the imximg fits into 258048 bytes. When installing the barebox imximg on -the eMMC take care not to overwrite the vendor supplied serial numbers stored -on the eMMC. -e.g. for the D01100 just write the imx-header and the application section: -loady -t usbserial -memcpy -b -s barebox-kindle-d01100.img -d /dev/disk0.boot0.imx_header 1024 0 2048 -memcpy -b -s barebox-kindle-d01100.img -d /dev/disk0.boot0.self 4096 0 253952 - -Note: a USB serial ACM console will be launched by a barebox init script -when -* the cursor select key is pressed during startup of model D01100 -* the home button is pressed within a second after startup of model D01200. - If you press the home button during startup, you will enter USB boot mode. -* the EY21 has no keys to press, a USB console will be launched for 10s. - -This device is battery-powered and there is no way to switch the device off. -When the device is inactive, the kindle software will first reduce the -power consumption to a few milliamps of battery power, after some minutes -the power consumption is further reduced to about 550 microamps. Switching -on iomux pullups may significantly reduce your standby-time. - -Hints to reduce the build image size. -Note that a drop-in replacement barebox imximage must not exceed 258048 bytes -since the space behind it is in use. Hence, don't build in drivers and FS -that are not required, e.g.: - NET, DISK_AHCI, DISK_INTF_PLATFORM_IDE, DISK_ATA, VIDEO, PWM, LED, - USB_STORAGE, USB_ULPI, NAND, MTD_UBI, FS_UBIFS, MFD_MC34704, MFD_MC9SDZ60, - MFD_STMPE, EEPROM_AT25, EEPROM_AT24, KEYBOARD_GPIO, PARTITION_DISK_EFI -Also unselect support for other boards to get rid of their dependencies. -Further select IMAGE_COMPRESSION_XZKERN diff --git a/Documentation/boards/imx/amazon-kindle3.rst b/Documentation/boards/imx/amazon-kindle3.rst deleted file mode 100644 index 50592f2..0000000 --- a/Documentation/boards/imx/amazon-kindle3.rst +++ /dev/null @@ -1,28 +0,0 @@ -Amazon Kindle 3 "Kindle Keyboard" Model No. D00901 -================================================== - -This e-book reader is based on a Freescale i.MX35 SOC. -The device is equiped with: - -* 256MiB synchronous dynamic RAM -* 4GiB eMMC -* a MC13892 PMIC - -The device boots in internal boot mode from eMMC and is shipped with a -vendor modified u-boot imximage. - -To upload and run a new bootloader the device can be put into USB-downloader -mode by the SOC microcode when Vol+ is pressed during startup. A new USB -device "SE Blank RINGO" should appear, barebox may be uploaded using -$ scripts/imx/imx-usb-loader barebox.imximg - -Note: a USB serial ACM console will be launched by a barebox init script -when the cursor select key is pressed during startup (e.g. before running -imx-usb-loader) - -Barebox may be used as drop-in replacement for the shipped bootloader. -When installing the barebox imximg on the eMMC take care not to overwrite -the partition table and vendor supplied serial numbers stored on the eMMC. -e.g. just write the imx-header and the application section: -memcpy -b -s barebox.imximg -d /dev/disk0.imx_header 1024 0 1024 -memcpy -b -s barebox.imximg -d /dev/disk0.self 4096 0 195584 diff --git a/Documentation/boards/imx/element14-warp7.rst b/Documentation/boards/imx/element14-warp7.rst new file mode 100644 index 0000000..830a2fb --- /dev/null +++ b/Documentation/boards/imx/element14-warp7.rst @@ -0,0 +1,55 @@ +element14 WaRP7 +=============== + +This CPU card is based on an NXP i.MX7S SoC. + +Supported hardware +------------------ + +- NXP PMIC PFUZE3000 +- Kingston 08EMCP04-EL3AV100 eMCP (eMMC and LPDDR3 memory in one package) + + - 8 GiB eMMC Triple-Level cell NAND flash, eMMC standard 5.0 (HS400) + - 512 MiB LPDDR3 SDRAM starting at address 0x80000000 + +Bootstrapping barebox +--------------------- + +The device boots in internal boot mode from eMMC and is shipped with a +vendor modified u-boot imximage. + +Barebox can be used as a drop-in replacement for the shipped bootloader. + +The WaRP7 IO Board has a double DIP switch where switch number two defines the +boot source of the i.MX7 SoC:: + + +-----+ + | | + | | O | <--- on = high level + | | | | + | O | | <--- off = low level + | | + | 1 2 | + +-----+ + +Bootsource is the internal eMMC:: + + +-----+ + | | + | O | | + | | | | + | | O | <---- eMMC + | | + | 1 2 | + +-----+ + +Bootsource is the USB:: + + +-----+ + | | + | O O | <---- USB + | | | | + | | | | + | | + | 1 2 | + +-----+ diff --git a/Documentation/boards/imx/garz-fricke-cupid.rst b/Documentation/boards/imx/garz-fricke-cupid.rst new file mode 100644 index 0000000..4520048 --- /dev/null +++ b/Documentation/boards/imx/garz-fricke-cupid.rst @@ -0,0 +1,9 @@ +Garz+Fricke Cupid +================= + +This CPU card is based on a Freescale i.MX35 CPU. The card is shipped with: + + * 256MiB NAND flash + * 128MiB synchronous dynamic RAM + +see http://www.garz-fricke.com/cupid-core_de.html for more information diff --git a/Documentation/boards/imx/garz-fricke-vincell.rst b/Documentation/boards/imx/garz-fricke-vincell.rst new file mode 100644 index 0000000..09d87d6 --- /dev/null +++ b/Documentation/boards/imx/garz-fricke-vincell.rst @@ -0,0 +1,43 @@ +Garz+Fricke Vincell LT +====================== + +This CPU card is based on a Freescale i.MX53 CPU. The card is shipped with: + + * 512MiB NAND flash + * 512MiB synchronous dynamic RAM + * microSD slot + +See http://www.garz-fricke.com/en/products/embedded-systems/single-board-computer/ia-0086r/ for more information. + + +Bootstrapping barebox +--------------------- + +The Vincell is shipped with the RedBoot bootloader. To replace RedBoot with +barebox, you first need to connect a serial console to the device. + +UART1 is located on the Molex header X39. When the Vincell is lying on the +display, then Pin 1 on the header is in the lower right: + + * Pin 1 - GND + * Pin 2 - TXD1 + * Pin 3 - RXD1 + +If everything is connected right, RedBoot shows up on the console. + +factory_bootstrap +----------------- + +Turn on the board and abort the boot process with ``Ctrl-C``. +Configure RedBoot so that it finds the barebox image on your TFTP server. +Execute ``fc`` and change the network setup according to your environment. +Be sure to copy the `Boot script` line to the prompt, otherwise it will be +set empty. The network setup can be validated with ``ping -h ``. +If the network setup is working properly, barebox can be loaded into memory:: + + load -v -r -b 0x80100000 barebox-guf-vincell-lt.img + exec + +Once in barebox, the bootloader can now be persisted to NAND:: + + barebox_update -t nand /mnt/tftp/barebox-guf-vincell-lt.img`` diff --git a/Documentation/boards/imx/karo-tx25.rst b/Documentation/boards/imx/karo-tx25.rst new file mode 100644 index 0000000..756c99d --- /dev/null +++ b/Documentation/boards/imx/karo-tx25.rst @@ -0,0 +1,10 @@ +Ka-Ro TX25 +========== + +Building the bootloader image for this target is covered by the ``imx_defconfig`` +multiimage configuration if the ``System Type`` menu entry ``Ka-Ro TX25`` +is enabled. + +Use the corresponding ``barebox-karo-tx25.img`` for external NAND boot. +Use the corresponding ``barebox-karo-tx25-internal.img`` for internal NAND, USB +or SD card boot. diff --git a/Documentation/boards/imx/karo-tx6.rst b/Documentation/boards/imx/karo-tx6.rst new file mode 100644 index 0000000..acd6d68 --- /dev/null +++ b/Documentation/boards/imx/karo-tx6.rst @@ -0,0 +1,13 @@ +Ka-Ro TX6x +========== + +This CPU cards are based on a Freescale i.MX6 SoC. +There are currently six variants of this module, that are distinguished +by the suffix: 'Q' use an i.MX6Q and 'U' an i.MX6DL. + +The TX6U-801x modules are shipped with: + + * 128MiB NAND flash + * 1024MiB DDR3 SDRAM + +see http://www.karo-electronics.de/tx6.html for more information diff --git a/Documentation/boards/imx/phytec-phycard-i.mx27.rst b/Documentation/boards/imx/phytec-phycard-i.mx27.rst new file mode 100644 index 0000000..d5d3837 --- /dev/null +++ b/Documentation/boards/imx/phytec-phycard-i.mx27.rst @@ -0,0 +1,8 @@ +Phytec phyCARD-i.MX27 +===================== + +Building the bootloader image for this target is covered by the ``imx_defconfig`` +multiimage configuration if the ``System Type`` menu entry ``phyCard-i.MX27`` +is enabled. + +Use the corresponding ``barebox-phytec-phycard-imx27.img`` file for this target. diff --git a/Documentation/boards/imx/phytec-phycore-i.mx27.rst b/Documentation/boards/imx/phytec-phycore-i.mx27.rst new file mode 100644 index 0000000..4b40be7 --- /dev/null +++ b/Documentation/boards/imx/phytec-phycore-i.mx27.rst @@ -0,0 +1,8 @@ +Phytec phyCORE-i.MX27 +===================== + +Building the bootloader image for this target is covered by the ``imx_defconfig`` +multiimage configuration if the ``System Type`` menu entry ``phyCORE-i.MX27`` +is enabled. + +Use the corresponding ``barebox-phytec-phycore-imx27.img`` file for this target. diff --git a/Documentation/boards/imx/phytec-phycore-i.mx31.rst b/Documentation/boards/imx/phytec-phycore-i.mx31.rst new file mode 100644 index 0000000..d9a981b --- /dev/null +++ b/Documentation/boards/imx/phytec-phycore-i.mx31.rst @@ -0,0 +1,41 @@ +Phytec phyCORE-i.MX31 CPU module PCM-037 +======================================== + +The CPU module +-------------- + +http://www.phytec.eu/europe/products/modules-overview/phycore/produktdetails/p/phycore-imx31-2.html + +This CPU card is based on a Freescale i.MX31 CPU. The card in +configuration -0000REU is shipped with: + + * 128 MiB synchronous dynamic RAM (DDR type) + * 64 MiB NAND flash + * 32 MiB NOR flash + * 512 kiB SRAM + * 4kiB EEPROM + * MMU, FPU + * Serial, Ethernet, USB (OTG), I2C, SPI, MMC/SD/SDIO, PCMCIA/CF, RTC + +Supported baseboards +-------------------- + +Supported baseboards are: + * Silica / Phytec PCM-970 via phyMAP-i.MX31, PMA-001 + +How to get barebox for Phytec's phyCORE-i.MX31 +---------------------------------------------- + +Using the default configuration:: + + make ARCH=arm pcm037_defconfig + +Build the binary image:: + + make ARCH=arm CROSS_COMPILE=armv5compiler + +.. note:: replace ``armv5compiler`` with your ARM v5 cross compiler prefix, + e.g.: ``arm-1136jfs-linux-gnueabi-`` + +The resulting binary image to be flashed will be ``barebox.bin``, whereas +the file named just ``barebox`` is an ELF executable for ARM. diff --git a/Documentation/boards/imx/phytec-phycore-i.mx35.rst b/Documentation/boards/imx/phytec-phycore-i.mx35.rst new file mode 100644 index 0000000..adf5d26 --- /dev/null +++ b/Documentation/boards/imx/phytec-phycore-i.mx35.rst @@ -0,0 +1,7 @@ +Phytec phyCORE-i.MX35 +===================== + +Building the bootloader image for this target is covered by the ``phytec-phycore-imx35_defconfig``. + +Use the corresponding ``barebox.bin`` file for this target. This image can be +used for booting in ``internal mode`` from NAND or NOR memory. diff --git a/Documentation/boards/imx/synertronixx_scb9328.rst b/Documentation/boards/imx/synertronixx_scb9328.rst index 0e59046..a104d1c 100644 --- a/Documentation/boards/imx/synertronixx_scb9328.rst +++ b/Documentation/boards/imx/synertronixx_scb9328.rst @@ -1,4 +1,4 @@ -Synertronixx scb9328 +Synertronixx SCB9328 ==================== See http://www.synertronixx.de/produkte/scb9328/scb9328.htm diff --git a/Documentation/boards/imx/wandboard.rst b/Documentation/boards/imx/wandboard.rst new file mode 100644 index 0000000..8283b47 --- /dev/null +++ b/Documentation/boards/imx/wandboard.rst @@ -0,0 +1,22 @@ +Wandboard +========= + +The Wandboard is a carrier board available with three different +System-on-Module options, the Wandboard Solo (i.MX6S, 512MiB DDR3), +the Wandboard Dual (i.MX6DL, 1GiB DDR3) and Wandboard Quad (i.MX6Q, 2GiB DDR3). + +The device boots from the SD card slot on the System-on-Module board, it +will not boot from the slot on the carrier board. + +To boot barebox on any wandboard, build ``imx_v7_defconfig`` +and copy the barebox imx-image to the i.MX boot location of a SD card, e.g.:: + + dd bs=1024 skip=1 seek=1 if=images/barebox-imx6-wandboard.img of=/dev/mmcblk0 + +Only one image exists, supporting all three Wandboard variants, barebox will +detect the Wandboard variant depending on the SoC variant. +This image is only usable for SD boot. It will not boot via imx-usb-loader. + +Connect to the serial port using a null-modem cable to get console access. + +For further documentation, including board schematics, see http://wandboard.org/.