diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.LED | 12 | ||||
| -rw-r--r-- | doc/README.at91 | 5 | ||||
| -rw-r--r-- | doc/README.nhk8815 (renamed from doc/README.nmdk8815) | 10 | ||||
| -rw-r--r-- | doc/README.omap3 | 1 |
4 files changed, 21 insertions, 7 deletions
diff --git a/doc/README.LED b/doc/README.LED index 1221177..94e552a 100644 --- a/doc/README.LED +++ b/doc/README.LED @@ -10,7 +10,7 @@ The first step is to define CONFIG_STATUS_LED in the board config file. If the LED support is only for a single board, define CONFIG_BOARD_SPECIFIC_LED in the board config file. -At a minimum, these macros must be defined at +At a minimum, these macros must be defined at STATUS_LED_BIT STATUS_LED_STATE STATUS_LED_PERIOD @@ -20,7 +20,7 @@ STATUS_LED_BIT<n> STATUS_LED_STATE<n> STATUS_LED_PERIOD<n> -Where <n> can a integer 1 through 3. +Where <n> can a integer 1 through 3. STATUS_LED_BIT is passed into the __led_* functions to identify which LED is being acted on. As such, the value choose must be unique with with respect to @@ -37,25 +37,25 @@ range from 2 to 10. Some other LED macros STATUS_LED_BOOT is the LED to light when the board is booting. This must be a -valid STATUS_LED_BIT value. +valid STATUS_LED_BIT value. STATUS_LED_RED is the red LED. It is used signal errors. This must be a valid STATUS_LED_BIT value. Other similar color LED's are STATUS_LED_YELLOW and -STATUS_LED_BLUE. +STATUS_LED_BLUE. These board must define these functions __led_init is called once to initialize the LED to STATUS_LED_STATE. One time start up code should be placed here. -__led_set is called to change the state of the LED. +__led_set is called to change the state of the LED. __led_toggle is called to toggle the current state of the LED. Colour LED ======================================== -Colour LED's are at present only used by ARM. +Colour LED's are at present only used by ARM. The functions names explain their purpose. diff --git a/doc/README.at91 b/doc/README.at91 index 9b4eae6..4a2c56b 100644 --- a/doc/README.at91 +++ b/doc/README.at91 @@ -62,11 +62,16 @@ Environment variables U-Boot environment variables can be stored at different places: - Dataflash on SPI chip select 0 (dataflash card) - Nand flash. + - Nor falsh (not populate by default) You can choose your storage location at config step (here for at91sam9260ek) : make at91sam9263ek_config - use data flash (spi cs0) (default) make at91sam9263ek_nandflash_config - use nand flash make at91sam9263ek_dataflash_cs0_config - use data flash (spi cs0) + make at91sam9263ek_norflash_config - use nor falsh + + You can choose to boot directly from U-Boot at config step + make at91sam9263ek_norflash_boot_config - boot from nor falsh ------------------------------------------------------------------------------ diff --git a/doc/README.nmdk8815 b/doc/README.nhk8815 index 453cfae..9008e39 100644 --- a/doc/README.nmdk8815 +++ b/doc/README.nhk8815 @@ -15,6 +15,16 @@ SDRAM configuration, PLL setup and initial loading from NAND is implemented in the X-Loader, so U-Boot is already running in SDRAM when control is handed over to it. +The Makefile offers two different configurations to be used if you +boot from Nand or OneNand. + + make nhk8815_config + make nhk8815_onenand_config + +Both support OneNand and Nand. Since U-Boot, running in RAM, can't know +where it was loaded from, the configurations differ in where the filesystem +is looked for by default. + On www.st.com/nomadik and on www.stnwireless.com there are documents, summary data and white papers on Nomadik. The full datasheet for diff --git a/doc/README.omap3 b/doc/README.omap3 index 66e781d..6227151 100644 --- a/doc/README.omap3 +++ b/doc/README.omap3 @@ -156,4 +156,3 @@ http://www.logicpd.com/sites/default/files/1012659A_Zoom_OMAP34x-II_MDP_Brief.pd [8] TI OMAP3 U-Boot: http://beagleboard.googlecode.com/files/u-boot_beagle_revb.tar.gz - |