u-boot/board/boundary/nitrogen6x
Pali Rohár 2827c2f07d Fix usage of CONFIG_PREBOOT
Due to usage of PREBOOT in Kconfig, macro CONFIG_PREBOOT is always defined
when CONFIG_USE_PREBOOT is enabled. In case CONFIG_PREBOOT is not
explicitly enabled it is set to empty C string and therefore
'#ifdef CONFIG_PREBOOT' guard does not work. Fix this issue by introducing
a new Kconfig symbol PREBOOT_DEFINED which cause to define new C macro
CONFIG_PREBOOT_DEFINED only when CONFIG_PREBOOT is really defined.

Change usage of '#ifdef CONFIG_PREBOOT' by '#ifdef CONFIG_USE_PREBOOT' for
code which checks if preboot code would be called and by
'#ifdef CONFIG_PREBOOT_DEFINED' for defining preboot code.

Signed-off-by: Pali Rohár <pali@kernel.org>
2022-11-21 09:23:00 -05:00
..
6x_bootscript.txt
6x_bootscript_android.txt
6x_bootscript_android_recovery.txt
6x_upgrade.txt nitrogen6x: update video console name 2020-06-18 19:25:05 +02:00
800mhz_2x128mx16.cfg
800mhz_2x256mx16.cfg
800mhz_4x128mx16.cfg
800mhz_4x256mx16.cfg
1066mhz_4x128mx16.cfg
1066mhz_4x256mx16.cfg
clocks.cfg
ddr-setup.cfg
Kconfig nitrogen6x: Migrate DDR_MB to Kconfig 2021-08-31 17:47:49 -04:00
MAINTAINERS nitrogen6x: migrate to using device tree 2019-10-08 16:35:16 +02:00
Makefile
nitrogen6dl.cfg imx: Don't define __ASSEMBLY__ in source files 2022-02-08 23:07:58 -05:00
nitrogen6dl2g.cfg imx: Don't define __ASSEMBLY__ in source files 2022-02-08 23:07:58 -05:00
nitrogen6q.cfg imx: Don't define __ASSEMBLY__ in source files 2022-02-08 23:07:58 -05:00
nitrogen6q2g.cfg imx: Don't define __ASSEMBLY__ in source files 2022-02-08 23:07:58 -05:00
nitrogen6s.cfg imx: Don't define __ASSEMBLY__ in source files 2022-02-08 23:07:58 -05:00
nitrogen6s1g.cfg imx: Don't define __ASSEMBLY__ in source files 2022-02-08 23:07:58 -05:00
nitrogen6x.c Fix usage of CONFIG_PREBOOT 2022-11-21 09:23:00 -05:00
README WS cleanup: remove SPACE(s) followed by TAB 2021-09-30 09:08:16 -04:00
README.mx6qsabrelite WS cleanup: remove trailing empty lines 2021-09-30 08:08:56 -04:00

U-Boot for the Boundary Devices Nitrogen6X and
Freescale i.MX6Q SabreLite boards

This file contains information for the port of
U-Boot to the Boundary Devices Nitrogen6X and
Freescale i.MX6Q SabreLite boards.

1. Boot source, boot from SPI NOR
---------------------------------
The configuration in this directory supports both the
Nitrogen6X and Freescale SabreLite board, but in a
different fashion from Freescale's implementation in
board/freescale/mx6qsabrelite.

In particular, this image supports booting from SPI NOR
and saving the environment to SPI NOR.

It does not support 'boot from SD' at offset 0x400
except through the 'bmode' command.
	http://lists.denx.de/pipermail/u-boot/2012-August/131151.html

2. Boots using 6x_bootscript on SATA or SD card
-----------------------------------------------
The default bootcmd for these boards is configured
to look for and source a boot script named '6x_bootscript'
in the root of the first partition of the following
devices:

	sata 0
	mmc 0
	mmc 1

They're searched in the order listed above, trying both the
ext2 and fat filesystems.

2. Maintaining the SPI NOR
--------------------------
A couple of convenience commands

	clearenv - clear environment to factory default
	upgradeu - look and source a boot script named
		'6x_upgrade' to upgrade the U-Boot version
		in SPI NOR. The search is the same as for
		6x_bootscript described above.

3. Display support
------------------
U-Boot support for the following displays is configured by
default:

    HDMI           - 1024 x 768 for maximum compatibility
    Hannstar-XGA   - 1024 x 768 LVDS (Freescale part number MCIMX-LVDS1)
    wsvga-lvds     - 1024 x 600 LVDS (Boundary p/n Nit6X_1024x600)
    wvga-rgb       - 800 x 480 RGB (Boundary p/n Nit6X_800x480)

Since the ipuv3_fb display driver currently supports only a single display,
this code auto-detects panel by probing the HDMI Phy for Hot Plug Detect
or the I2C touch controller of the LVDS and RGB displays in the priority
listed above.

Setting 'panel' environment variable to one of the names above will
override auto-detection and force activation of the specified panel.

4. Building
------------

To build U-Boot for one of the Nitrogen6x or SabreLite board:

	make nitrogen6x_config
	make

Note that 'nitrogen6x' is a placeholder. The complete list of supported
board configurations is shown in the boards.cfg file:
	nitrogen6q		i.MX6Q/6D	1GB
	nitrogen6dl		i.MX6DL		1GB
	nitrogen6s		i.MX6S		512MB
	nitrogen6q2g		i.MX6Q/6D	2GB
	nitrogen6dl2g		i.MX6DL		2GB
	nitrogen6s1g		i.MX6S		1GB

The -6q variants support either the i.MX6Quad or i.MX6Dual processors
and are configured for a 64-bit memory bus at 1066 MHz.

The -6dl variants also use a 64-bit memory bus, operated at 800MHz.

The -6s variants use a 32-bit memory bus at 800MHz.

If you place the u-boot.imx into a single-partition SD card
along with a binary version of the boot script 6x_upgrade.txt,
you can program it using 'upgradeu':

	U-Boot> run upgradeu