upstream u-boot with additional patches for our devices/boards: https://lists.denx.de/pipermail/u-boot/2017-March/282789.html (AXP crashes) ; Gbit ethernet patch for some LIME2 revisions ; with SPI flash support
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
u-boot/include/configs/omap3_evm_quick_nand.h

93 lines
2.6 KiB

/*
* Configuration settings for quick boot from NAND on OMAP3 EVM.
*
* Copyright (C) 2006-2010 Texas Instruments Incorporated - http://www.ti.com/
*
* Author :
* Sanjeev Premi <premi@ti.com>
*
* SPDX-License-Identifier: GPL-2.0+
*/
#ifndef __OMAP3_EVM_QUICK_NAND_H
#define __OMAP3_EVM_QUICK_NAND_H
#include <asm/arch/cpu.h>
#include <asm/arch/omap.h>
/* ----------------------------------------------------------------------------
* Supported U-boot commands
* ----------------------------------------------------------------------------
*/
#define CONFIG_CMD_NAND
/*
* Board revision is detected by probing the Ethernet chip.
*
* When revision is statically configured via CONFIG_STATIC_BOARD_REV,
* this option can be removed. Generated binary is leaner by ~16Kbytes.
*/
/* ----------------------------------------------------------------------------
* Supported U-boot features
* ----------------------------------------------------------------------------
*/
#define CONFIG_SILENT_CONSOLE
#define CONFIG_ENV_IS_NOWHERE
/* -----------------------------------------------------------------------------
* Include common board configuration
* -----------------------------------------------------------------------------
*/
#include "omap3_evm_common.h"
/* -----------------------------------------------------------------------------
* Default environment
* -----------------------------------------------------------------------------
*/
#define CONFIG_BOOTDELAY 0
#define CONFIG_EXTRA_ENV_SETTINGS \
"verify=no\0" \
"silent=1"
#define CONFIG_BOOTCOMMAND \
"nandecc hw; " \
"nand read.i 0x80000000 280000 300000; " \
"bootm 0x80000000;"
/*
* Update the bootargs as necessary e.g. size of memory, partition and fstype
*/
#define CONFIG_BOOTARGS \
"quiet " \
"console=ttyO0,115200n8 " \
"mem=128M " \
"noinitrd " \
"root=/dev/mtdblock4 rw " \
"rootfstype=jffs2 "
/*
* SPL
*/
#define CONFIG_SPL_NAND_SIMPLE
#define CONFIG_SPL_NAND_SUPPORT
#define CONFIG_SPL_NAND_BASE
#define CONFIG_SPL_NAND_DRIVERS
#define CONFIG_SPL_NAND_ECC
#define CONFIG_SYS_NAND_5_ADDR_CYCLE
#define CONFIG_SYS_NAND_PAGE_COUNT 64
#define CONFIG_SYS_NAND_PAGE_SIZE 2048
#define CONFIG_SYS_NAND_OOBSIZE 64
#define CONFIG_SYS_NAND_BLOCK_SIZE (128*1024)
#define CONFIG_SYS_NAND_BAD_BLOCK_POS 0
#define CONFIG_SYS_NAND_ECCPOS {2, 3, 4, 5, 6, 7, 8, 9,\
10, 11, 12, 13}
#define CONFIG_SYS_NAND_ECCSIZE 512
#define CONFIG_SYS_NAND_ECCBYTES 3
mtd: nand: omap: add CONFIG_NAND_OMAP_ECCSCHEME for selection of ecc-scheme This patch adds new CONFIG_NAND_OMAP_ECCSCHEME, replacing other distributed CONFIG_xx used for selecting NAND ecc-schemes. This patch aims at solving following issues. 1) Currently ecc-scheme is tied to SoC platform, which prevents user to select other ecc-schemes also supported in hardware. like; - most of OMAP3 SoC platforms use only 1-bit Hamming ecc-scheme, inspite the fact that they can use higher ecc-schemes like 8-bit ecc-schemes with software based error detection (OMAP_ECC_BCH4_CODE_HW_DETECTION_SW). - most of AM33xx SoC plaforms use 8-bit BCH ecc-scheme for now, but hardware supports BCH16 ecc-scheme also. 2) Different platforms use different CONFIG_xx to select ecc-schemes, which adds confusion for user while migrating platforms. - *CONFIG_NAND_OMAP_ELM* which enables ELM hardware engine, selects only 8-bit BCH ecc-scheme with h/w based error-correction (OMAP_ECC_BCH8_CODE_HW) whereas ELM hardware engine supports other ecc-schemes also like; BCH4, and BCH16 (in future). - *CONFIG_NAND_OMAP_BCH8* selects 8-bit BCH ecc-scheme with s/w based error correction (OMAP_ECC_BCH8_CODE_HW_DETECTION_SW). - *CONFIG_SPL_NAND_SOFTECC* selects 1-bit Hamming ecc-scheme using s/w library Thus adding new *CONFIG_NAND_OMAP_ECCSCHEME* de-couples ecc-scheme dependency on SoC platform and NAND driver. And user can select ecc-scheme independently foreach board. However, selection some hardware based ecc-schemes (OMAP_ECC_BCHx_CODE_HW) still depends on presence of ELM hardware engine on SoC. (Refer doc/README.nand) Signed-off-by: Pekon Gupta <pekon@ti.com>
11 years ago
#define CONFIG_NAND_OMAP_ECCSCHEME OMAP_ECC_HAM1_CODE_HW
#define CONFIG_SYS_NAND_U_BOOT_START CONFIG_SYS_TEXT_BASE
#define CONFIG_SYS_NAND_U_BOOT_OFFS 0x80000
#endif /* __OMAP3_EVM_QUICK_NAND_H */