X-Git-Url: https://git.karo-electronics.de/?a=blobdiff_plain;f=README;h=2c5682016100b455bbb9c60fa44537093c614455;hb=2d1a537d87727907bf4d888760cba4abc0b52ad3;hp=efd46933066d7963ab72ad571b26a4422a8f5627;hpb=1f4bb37d6bcae59b18a2438f3cdca6545a831ab5;p=karo-tx-uboot.git diff --git a/README b/README index efd4693306..2c56820161 100644 --- a/README +++ b/README @@ -1,5 +1,5 @@ # -# (C) Copyright 2000 - 2002 +# (C) Copyright 2000 - 2004 # Wolfgang Denk, DENX Software Engineering, wd@denx.de. # # See file CREDITS for list of people who contributed to this @@ -119,12 +119,12 @@ U-Boot will always have a patchlevel of "0". Directory Hierarchy: ==================== -- board Board dependend files -- common Misc architecture independend functions +- board Board dependent files +- common Misc architecture independent functions - cpu CPU specific files - disk Code for disk drive partition handling - doc Documentation (don't expect too much) -- drivers Common used device drivers +- drivers Commonly used device drivers - dtt Digital Thermometer and Thermostat drivers - examples Example code for standalone applications, etc. - include Header Files @@ -141,29 +141,31 @@ Directory Hierarchy: - cpu/74xx_7xx Files specific to Motorola MPC74xx and 7xx CPUs - cpu/arm925t Files specific to ARM 925 CPUs +- cpu/arm926ejs Files specific to ARM 926 CPUs - cpu/mpc5xx Files specific to Motorola MPC5xx CPUs - cpu/mpc8xx Files specific to Motorola MPC8xx CPUs - cpu/mpc824x Files specific to Motorola MPC824x CPUs - cpu/mpc8260 Files specific to Motorola MPC8260 CPU +- cpu/mpc85xx Files specific to Motorola MPC85xx CPUs - cpu/ppc4xx Files specific to IBM 4xx CPUs -- board/LEOX/ Files specific to boards manufactured by The LEOX team +- board/LEOX/ Files specific to boards manufactured by The LEOX team - board/LEOX/elpt860 Files specific to ELPT860 boards - board/RPXClassic Files specific to RPXClassic boards -- board/RPXlite Files specific to RPXlite boards +- board/RPXlite Files specific to RPXlite boards - board/at91rm9200dk Files specific to AT91RM9200DK boards - board/c2mon Files specific to c2mon boards -- board/cmi Files specific to cmi boards +- board/cmi Files specific to cmi boards - board/cogent Files specific to Cogent boards (need further configuration) Files specific to CPCIISER4 boards -- board/cpu86 Files specific to CPU86 boards +- board/cpu86 Files specific to CPU86 boards - board/cray/ Files specific to boards manufactured by Cray -- board/cray/L1 Files specific to L1 boards +- board/cray/L1 Files specific to L1 boards - board/cu824 Files specific to CU824 boards -- board/ebony Files specific to IBM Ebony board +- board/ebony Files specific to IBM Ebony board - board/eric Files specific to ERIC boards - board/esd/ Files specific to boards manufactured by ESD - board/esd/adciop Files specific to ADCIOP boards @@ -173,8 +175,8 @@ Directory Hierarchy: - board/esd/cpciiser4 Files specific to CPCIISER4 boards - board/esd/common Common files for ESD boards - board/esd/dasa_sim Files specific to DASA_SIM boards -- board/esd/du405 Files specific to DU405 boards -- board/esd/ocrtc Files specific to OCRTC boards +- board/esd/du405 Files specific to DU405 boards +- board/esd/ocrtc Files specific to OCRTC boards - board/esd/pci405 Files specific to PCI405 boards - board/esteem192e Files specific to ESTEEM192E boards @@ -195,46 +197,59 @@ Directory Hierarchy: - board/ivm Files specific to IVMS8/IVML24 boards - board/lantec Files specific to LANTEC boards - board/lwmon Files specific to LWMON boards +- board/Marvell Files specific to Marvell development boards +- board/Marvell/db64360 Files specific to db64360 board +- board/Marvell/db64460 Files specific to db64460 board - board/mbx8xx Files specific to MBX boards - board/mpc8260ads - Files specific to MPC8260ADS and PQ2FADS-ZU boards + Files specific to MPC826xADS and PQ2FADS-ZU/VR boards +- board/mpc8540ads + Files specific to MPC8540ADS boards +- board/mpc8560ads + Files specific to MPC8560ADS boards - board/mpl/ Files specific to boards manufactured by MPL - board/mpl/common Common files for MPL boards - board/mpl/pip405 Files specific to PIP405 boards - board/mpl/mip405 Files specific to MIP405 boards -- board/musenki Files specific to MUSEKNI boards -- board/mvs1 Files specific to MVS1 boards -- board/nx823 Files specific to NX823 boards -- board/oxc Files specific to OXC boards +- board/mpl/vcma9 Files specific to VCMA9 boards +- board/musenki Files specific to MUSEKNI boards +- board/mvs1 Files specific to MVS1 boards +- board/nx823 Files specific to NX823 boards +- board/oxc Files specific to OXC boards - board/omap1510inn Files specific to OMAP 1510 Innovator boards -- board/pcippc2 Files specific to PCIPPC2/PCIPPC6 boards -- board/pm826 Files specific to PM826 boards +- board/omap1610inn + Files specific to OMAP 1610 Innovator boards +- board/pcippc2 Files specific to PCIPPC2/PCIPPC6 boards +- board/pm826 Files specific to PM826 boards - board/ppmc8260 Files specific to PPMC8260 boards +- board/snmc/qs850 Files specific to QS850/823 boards +- board/snmc/qs860t Files specific to QS860T boards - board/rpxsuper Files specific to RPXsuper boards - board/rsdproto Files specific to RSDproto boards - board/sandpoint Files specific to Sandpoint boards -- board/sbc8260 Files specific to SBC8260 boards +- board/sbc8260 Files specific to SBC8260 boards - board/sacsng Files specific to SACSng boards - board/siemens Files specific to boards manufactured by Siemens AG - board/siemens/CCM Files specific to CCM boards - board/siemens/IAD210 Files specific to IAD210 boards -- board/siemens/SCM Files specific to SCM boards +- board/siemens/SCM Files specific to SCM boards - board/siemens/pcu_e Files specific to PCU_E boards - board/sixnet Files specific to SIXNET boards - board/spd8xx Files specific to SPD8xxTS boards - board/tqm8260 Files specific to TQM8260 boards - board/tqm8xx Files specific to TQM8xxL boards -- board/w7o Files specific to W7O boards +- board/w7o Files specific to W7O boards - board/walnut405 Files specific to Walnut405 boards -- board/westel/ Files specific to boards manufactured by Westel Wireless +- board/westel/ Files specific to boards manufactured by Westel Wireless - board/westel/amx860 Files specific to AMX860 boards -- board/utx8245 Files specific to UTX8245 boards +- board/utx8245 Files specific to UTX8245 boards +- board/zpc1900 Files specific to Zephyr Engineering ZPC.1900 board Software Configuration: ======================= @@ -301,8 +316,10 @@ The following options need to be configured: CONFIG_MPC823, CONFIG_MPC850, CONFIG_MPC855, CONFIG_MPC860 or CONFIG_MPC5xx or CONFIG_MPC824X, CONFIG_MPC8260 + or CONFIG_MPC85xx or CONFIG_IOP480 or CONFIG_405GP + or CONFIG_405EP or CONFIG_440 or CONFIG_MPC74xx or CONFIG_750FX @@ -319,47 +336,50 @@ The following options need to be configured: PowerPC based boards: --------------------- - CONFIG_ADCIOP, CONFIG_ICU862 CONFIG_RPXsuper, - CONFIG_ADS860, CONFIG_IP860, CONFIG_SM850, - CONFIG_AMX860, CONFIG_IPHASE4539, CONFIG_SPD823TS, - CONFIG_AR405, CONFIG_IVML24, CONFIG_SXNI855T, - CONFIG_BAB7xx, CONFIG_IVML24_128, CONFIG_Sandpoint8240, - CONFIG_CANBT, CONFIG_IVML24_256, CONFIG_Sandpoint8245, - CONFIG_CCM, CONFIG_IVMS8, CONFIG_TQM823L, - CONFIG_CPCI405, CONFIG_IVMS8_128, CONFIG_TQM850L, + CONFIG_ADCIOP, CONFIG_ICU862 CONFIG_RPXsuper, + CONFIG_ADS860, CONFIG_IP860, CONFIG_SM850, + CONFIG_AMX860, CONFIG_IPHASE4539, CONFIG_SPD823TS, + CONFIG_AR405, CONFIG_IVML24, CONFIG_SXNI855T, + CONFIG_BAB7xx, CONFIG_IVML24_128, CONFIG_Sandpoint8240, + CONFIG_CANBT, CONFIG_IVML24_256, CONFIG_Sandpoint8245, + CONFIG_CCM, CONFIG_IVMS8, CONFIG_TQM823L, + CONFIG_CPCI405, CONFIG_IVMS8_128, CONFIG_TQM850L, CONFIG_CPCI4052, CONFIG_IVMS8_256, CONFIG_TQM855L, CONFIG_CPCIISER4, CONFIG_LANTEC, CONFIG_TQM860L, - CONFIG_CPU86, CONFIG_MBX, CONFIG_TQM8260, - CONFIG_CRAYL1, CONFIG_MBX860T, CONFIG_TTTech, - CONFIG_CU824, CONFIG_MHPC, CONFIG_UTX8245, + CONFIG_CPU86, CONFIG_MBX, CONFIG_TQM8260, + CONFIG_CRAYL1, CONFIG_MBX860T, CONFIG_TTTech, + CONFIG_CU824, CONFIG_MHPC, CONFIG_UTX8245, CONFIG_DASA_SIM, CONFIG_MIP405, CONFIG_W7OLMC, - CONFIG_DU405, CONFIG_MOUSSE, CONFIG_W7OLMG, - CONFIG_ELPPC, CONFIG_MPC8260ADS, CONFIG_WALNUT405, - CONFIG_ERIC, CONFIG_MUSENKI, CONFIG_ZUMA, - CONFIG_ESTEEM192E, CONFIG_MVS1, CONFIG_c2mon, - CONFIG_ETX094, CONFIG_NX823, CONFIG_cogent_mpc8260, + CONFIG_DU405, CONFIG_MOUSSE, CONFIG_W7OLMG, + CONFIG_ELPPC, CONFIG_MPC8260ADS, CONFIG_WALNUT405, + CONFIG_ERIC, CONFIG_MUSENKI, CONFIG_ZUMA, + CONFIG_ESTEEM192E, CONFIG_MVS1, CONFIG_c2mon, + CONFIG_ETX094, CONFIG_NX823, CONFIG_cogent_mpc8260, CONFIG_EVB64260, CONFIG_OCRTC, CONFIG_cogent_mpc8xx, - CONFIG_FADS823, CONFIG_ORSG, CONFIG_ep8260, - CONFIG_FADS850SAR, CONFIG_OXC, CONFIG_gw8260, + CONFIG_FADS823, CONFIG_ORSG, CONFIG_ep8260, + CONFIG_FADS850SAR, CONFIG_OXC, CONFIG_gw8260, CONFIG_FADS860T, CONFIG_PCI405, CONFIG_hermes, - CONFIG_FLAGADM, CONFIG_PCIPPC2, CONFIG_hymod, - CONFIG_FPS850L, CONFIG_PCIPPC6, CONFIG_lwmon, - CONFIG_GEN860T, CONFIG_PIP405, CONFIG_pcu_e, - CONFIG_GENIETV, CONFIG_PM826, CONFIG_ppmc8260, - CONFIG_GTH, CONFIG_RPXClassic, CONFIG_rsdproto, - CONFIG_IAD210, CONFIG_RPXlite, CONFIG_sbc8260, - CONFIG_EBONY, CONFIG_sacsng, CONFIG_FPS860L, - CONFIG_V37, CONFIG_ELPT860, CONFIG_CMI, - CONFIG_NETVIA, CONFIG_RBC823 + CONFIG_FLAGADM, CONFIG_PCIPPC2, CONFIG_hymod, + CONFIG_FPS850L, CONFIG_PCIPPC6, CONFIG_lwmon, + CONFIG_GEN860T, CONFIG_PIP405, CONFIG_pcu_e, + CONFIG_GENIETV, CONFIG_PM826, CONFIG_ppmc8260, + CONFIG_GTH, CONFIG_RPXClassic, CONFIG_rsdproto, + CONFIG_IAD210, CONFIG_RPXlite, CONFIG_sbc8260, + CONFIG_EBONY, CONFIG_sacsng, CONFIG_FPS860L, + CONFIG_V37, CONFIG_ELPT860, CONFIG_CMI, + CONFIG_NETVIA, CONFIG_RBC823, CONFIG_ZPC1900, + CONFIG_MPC8540ADS, CONFIG_MPC8560ADS, CONFIG_QS850, + CONFIG_QS823, CONFIG_QS860T, CONFIG_DB64360, + CONFIG_DB64460, CONFIG_DUET_ADS ARM based boards: ----------------- CONFIG_HHP_CRADLE, CONFIG_DNP1110, CONFIG_EP7312, - CONFIG_IMPA7, CONFIG_LART, CONFIG_LUBBOCK, - CONFIG_INNOVATOROMAP1510, - CONFIG_SHANNON, CONFIG_SMDK2400, CONFIG_SMDK2410, - CONFIG_TRAB, CONFIG_AT91RM9200DK + CONFIG_IMPA7, CONFIG_LART, CONFIG_LUBBOCK, + CONFIG_INNOVATOROMAP1510, CONFIG_INNOVATOROMAP1610 + CONFIG_SHANNON, CONFIG_SMDK2400, CONFIG_SMDK2410, + CONFIG_TRAB, CONFIG_VCMA9, CONFIG_AT91RM9200DK - CPU Module Type: (if CONFIG_COGENT is defined) @@ -387,20 +407,37 @@ The following options need to be configured: CONFIG_ADSTYPE Possible values are: CFG_8260ADS - original MPC8260ADS - CFG_8266ADS - MPC8266ADS (untested) - CFG_PQ2FADS - PQ2FADS-ZU + CFG_8266ADS - MPC8266ADS + CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR - MPC824X Family Member (if CONFIG_MPC824X is defined) - Define exactly one of - CONFIG_MPC8240, CONFIG_MPC8245 + Define exactly one of + CONFIG_MPC8240, CONFIG_MPC8245 -- 8xx CPU Options: (if using an 8xx cpu) +- 8xx CPU Options: (if using an MPC8xx cpu) Define one or more of - CONFIG_8xx_GCLK_FREQ - if get_gclk_freq() can not work e.g. - no 32KHz reference PIT/RTC clock - -- Clock Interface: + CONFIG_8xx_GCLK_FREQ - if get_gclk_freq() cannot work + e.g. if there is no 32KHz + reference PIT/RTC clock + +- 859/866 CPU options: (if using a MPC859 or MPC866 CPU): + CFG_866_OSCCLK + CFG_866_CPUCLK_MIN + CFG_866_CPUCLK_MAX + CFG_866_CPUCLK_DEFAULT + See doc/README.MPC866 + + CFG_MEASURE_CPUCLK + + Define this to measure the actual CPU clock instead + of relying on the correctness of the configured + values. Mostly useful for board bringup to make sure + the PLL is locked at the intended frequency. Note + that this requires a (stable) reference clock (32 kHz + RTC clock), + +- Linux Kernel Interface: CONFIG_CLOCKS_IN_MHZ U-Boot stores all clock information in Hz @@ -410,11 +447,16 @@ The following options need to be configured: "clocks_in_mhz" can be defined so that U-Boot converts clock data to MHZ before passing it to the Linux kernel. - When CONFIG_CLOCKS_IN_MHZ is defined, a definition of "clocks_in_mhz=1" is automatically included in the default environment. + CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only] + + When transfering memsize parameter to linux, some versions + expect it to be in bytes, others in MB. + Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes. + - Console Interface: Depending on board, define exactly one serial port (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2, @@ -437,11 +479,11 @@ The following options need to be configured: bit-blit (cf. smiLynxEM) VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch) - VIDEO_VISIBLE_ROWS visible pixel rows - VIDEO_PIXEL_SIZE bytes per pixel + VIDEO_VISIBLE_ROWS visible pixel rows + VIDEO_PIXEL_SIZE bytes per pixel VIDEO_DATA_FORMAT graphic data format (0-5, cf. cfb_console.c) - VIDEO_FB_ADRS framebuffer address + VIDEO_FB_ADRS framebuffer address VIDEO_KBD_INIT_FCT keyboard int fct (i.e. i8042_kbd_init()) VIDEO_TSTC_FCT test char fct @@ -468,10 +510,16 @@ The following options need to be configured: default i/o. Serial console can be forced with environment 'console=serial'. + When CONFIG_SILENT_CONSOLE is defined, all console + messages (by U-Boot and Linux!) can be silenced with + the "silent" environment variable. See + doc/README.silent for more information. + - Console Baudrate: CONFIG_BAUDRATE - in bps Select one of the baudrates listed in CFG_BAUDRATE_TABLE, see below. + CFG_BRGCLK_PRESCALE, baudrate prescale - Interrupt driven serial port input: CONFIG_SERIAL_SOFTWARE_FIFO @@ -568,13 +616,18 @@ The following options need to be configured: #define enables commands: ------------------------- CFG_CMD_ASKENV * ask for env variable + CFG_CMD_AUTOSCRIPT Autoscript Support CFG_CMD_BDI bdinfo CFG_CMD_BEDBUG Include BedBug Debugger + CFG_CMD_BMP * BMP support CFG_CMD_BOOTD bootd CFG_CMD_CACHE icache, dcache CFG_CMD_CONSOLE coninfo CFG_CMD_DATE * support for RTC, date/time... CFG_CMD_DHCP DHCP support + CFG_CMD_DIAG * Diagnostics + CFG_CMD_DOC * Disk-On-Chip Support + CFG_CMD_DTT Digital Therm and Thermostat CFG_CMD_ECHO * echo arguments CFG_CMD_EEPROM * EEPROM read/write support CFG_CMD_ELF bootelf, bootvx @@ -584,27 +637,38 @@ The following options need to be configured: CFG_CMD_FDOS * Dos diskette Support CFG_CMD_FLASH flinfo, erase, protect CFG_CMD_FPGA FPGA device initialization support + CFG_CMD_HWFLOW * RTS/CTS hw flow control CFG_CMD_I2C * I2C serial bus support CFG_CMD_IDE * IDE harddisk support CFG_CMD_IMI iminfo + CFG_CMD_IMLS List all found images CFG_CMD_IMMAP * IMMR dump support CFG_CMD_IRQ * irqinfo + CFG_CMD_ITEST * Integer/string test of 2 values + CFG_CMD_JFFS2 * JFFS2 Support CFG_CMD_KGDB * kgdb CFG_CMD_LOADB loadb CFG_CMD_LOADS loads CFG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base, loop, mtest + CFG_CMD_MISC Misc functions like sleep etc CFG_CMD_MMC MMC memory mapped support CFG_CMD_MII MII utility commands + CFG_CMD_NAND * NAND support CFG_CMD_NET bootp, tftpboot, rarpboot CFG_CMD_PCI * pciinfo CFG_CMD_PCMCIA * PCMCIA support + CFG_CMD_PING * send ICMP ECHO_REQUEST to network host + CFG_CMD_PORTIO * Port I/O CFG_CMD_REGINFO * Register dump CFG_CMD_RUN run command in env variable + CFG_CMD_SAVES save S record dump CFG_CMD_SCSI * SCSI Support + CFG_CMD_SDRAM * print SDRAM configuration information CFG_CMD_SETGETDCR Support for DCR Register access (4xx only) CFG_CMD_SPI * SPI serial bus support CFG_CMD_USB * USB support + CFG_CMD_VFD * VFD support (TRAB) CFG_CMD_BSP * Board SPecific functions ----------------------------------------------- CFG_CMD_ALL all @@ -640,7 +704,7 @@ The following options need to be configured: - Watchdog: CONFIG_WATCHDOG If this variable is defined, it enables watchdog - support. There must support in the platform specific + support. There must be support in the platform specific code for a watchdog. For the 8xx and 8260 CPUs, the SIU Watchdog feature is enabled in the SYPCR register. @@ -787,9 +851,9 @@ The following options need to be configured: Following modes are supported (* is default): 800x600 1024x768 1280x1024 - 256 (8bit) 303* 305 307 - 65536 (16bit) 314 317 31a - 16,7 Mill (24bit) 315 318 31b + 256 (8bit) 303* 305 307 + 65536 (16bit) 314 317 31a + 16,7 Mill (24bit) 315 318 31b (i.e. setenv videomode 317; saveenv; reset;) CONFIG_VIDEO_SED13806 @@ -811,13 +875,18 @@ The following options need to be configured: display); also select one of the supported displays by defining one of these: - CONFIG_NEC_NL6648AC33: + CONFIG_NEC_NL6448AC33: + + NEC NL6448AC33-18. Active, color, single scan. - NEC NL6648AC33-18. Active, color, single scan. + CONFIG_NEC_NL6448BC20 + + NEC NL6448BC20-08. 6.5", 640x480. + Active, color, single scan. - CONFIG_NEC_NL6648BC20 + CONFIG_NEC_NL6448BC33_54 - NEC NL6648BC20-08. 6.5", 640x480. + NEC NL6448BC33-54. 10.4", 640x480. Active, color, single scan. CONFIG_SHARP_16x9 @@ -848,7 +917,7 @@ The following options need to be configured: Normally display is black on white background; define CFG_WHITE_ON_BLACK to get it inverted. -- Spash Screen Support: CONFIG_SPLASH_SCREEN +- Splash Screen Support: CONFIG_SPLASH_SCREEN If this option is set, the environment is checked for a variable "splashimage". If found, the usual display @@ -859,6 +928,16 @@ The following options need to be configured: allows for a "silent" boot where a splash screen is loaded very quickly after power-on. +- Compression support: + CONFIG_BZIP2 + + If this option is set, support for bzip2 compressed + images is included. If not, only uncompressed and gzip + compressed images are supported. + + NOTE: the bzip2 algorithm requires a lot of RAM, so + the malloc area (as defined by CFG_MALLOC_LEN) should + be at least 4MB. - Ethernet address: CONFIG_ETHADDR @@ -901,6 +980,29 @@ The following options need to be configured: 4th and following BOOTP requests: delay 0 ... 8 sec +- DHCP Advanced Options: + CONFIG_BOOTP_MASK + + You can fine tune the DHCP functionality by adding + these flags to the CONFIG_BOOTP_MASK define: + + CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS + serverip from a DHCP server, it is possible that more + than one DNS serverip is offered to the client. + If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS + serverip will be stored in the additional environment + variable "dnsip2". The first DNS serverip is always + stored in the variable "dnsip", when CONFIG_BOOTP_DNS + is added to the CONFIG_BOOTP_MASK. + + CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable + to do a dynamic update of a DNS server. To do this, they + need the hostname of the DHCP requester. + If CONFIG_BOOP_SEND_HOSTNAME is added to the + CONFIG_BOOTP_MASK, the content of the "hostname" + environment variable is passed as option 12 to + the DHCP server. + - Status LED: CONFIG_STATUS_LED Several configurations allow to display the current @@ -930,7 +1032,7 @@ The following options need to be configured: clock chips. See common/cmd_i2c.c for a description of the command line interface. - CONFIG_HARD_I2C selects the CPM hardware driver for I2C. + CONFIG_HARD_I2C selects the CPM hardware driver for I2C. CONFIG_SOFT_I2C configures u-boot to use a software (aka bit-banging) driver instead of CPM or similar hardware @@ -960,7 +1062,7 @@ The following options need to be configured: (Optional). Any commands necessary to enable the I2C controller or configure ports. - eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL) + eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL) I2C_PORT @@ -998,7 +1100,7 @@ The following options need to be configured: eg: #define I2C_SDA(bit) \ if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \ - else immr->im_cpm.cp_pbdat &= ~PB_SDA + else immr->im_cpm.cp_pbdat &= ~PB_SDA I2C_SCL(bit) @@ -1007,7 +1109,7 @@ The following options need to be configured: eg: #define I2C_SCL(bit) \ if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \ - else immr->im_cpm.cp_pbdat &= ~PB_SCL + else immr->im_cpm.cp_pbdat &= ~PB_SCL I2C_DELAY @@ -1104,7 +1206,7 @@ The following options need to be configured: Time to wait after FPGA configuration. The default is 200 mS. -- FPGA Support: CONFIG_FPGA_COUNT +- FPGA Support: CONFIG_FPGA_COUNT Specify the number of FPGA devices to support. @@ -1166,7 +1268,7 @@ The following options need to be configured: U-Boot considers the values of the environment variables "serial#" (Board Serial Number) and - "ethaddr" (Ethernet Address) to bb parameters that + "ethaddr" (Ethernet Address) to be parameters that are set once by the board vendor / manufacturer, and protects these variables from casual modification by the user. Once set, these variables are read-only, @@ -1276,12 +1378,12 @@ The following options need to be configured: of the backslashes before semicolons and special symbols. -- Default Environment +- Default Environment: CONFIG_EXTRA_ENV_SETTINGS Define this to contain any number of null terminated strings (variable = value pairs) that will be part of - the default enviroment compiled into the boot image. + the default environment compiled into the boot image. For example, place something like this in your board's config file: @@ -1294,7 +1396,7 @@ The following options need to be configured: internal format how the environment is stored by the U-Boot code. This is NOT an official, exported interface! Although it is unlikely that this format - will change soon, but there is no guarantee either. + will change soon, there is no guarantee either. You better know what you are doing here. Note: overly (ab)use of the default environment is @@ -1302,14 +1404,28 @@ The following options need to be configured: the environment like the autoscript function or the boot command first. -- DataFlash Support +- DataFlash Support: CONFIG_HAS_DATAFLASH Defining this option enables DataFlash features and allows to read/write in Dataflash via the standard commands cp, md... -- Show boot progress +- SystemACE Support: + CONFIG_SYSTEMACE + + Adding this option adds support for Xilinx SystemACE + chips attached via some sort of local bus. The address + of the chip must alsh be defined in the + CFG_SYSTEMACE_BASE macro. For example: + + #define CONFIG_SYSTEMACE + #define CFG_SYSTEMACE_BASE 0xf0000000 + + When SystemACE support is added, the "ace" device type + becomes available to the fat commands, i.e. fatls. + +- Show boot progress: CONFIG_SHOW_BOOT_PROGRESS Defining this option allows to add some board- @@ -1321,11 +1437,11 @@ The following options need to be configured: Arg Where When 1 common/cmd_bootm.c before attempting to boot an image - -1 common/cmd_bootm.c Image header has bad magic number + -1 common/cmd_bootm.c Image header has bad magic number 2 common/cmd_bootm.c Image header has correct magic number - -2 common/cmd_bootm.c Image header has bad checksum + -2 common/cmd_bootm.c Image header has bad checksum 3 common/cmd_bootm.c Image header has correct checksum - -3 common/cmd_bootm.c Image data has bad checksum + -3 common/cmd_bootm.c Image data has bad checksum 4 common/cmd_bootm.c Image data has correct checksum -4 common/cmd_bootm.c Image is for unsupported architecture 5 common/cmd_bootm.c Architecture check OK @@ -1338,10 +1454,10 @@ The following options need to be configured: 8 common/cmd_bootm.c Image Type check OK -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX) 9 common/cmd_bootm.c Start initial ramdisk verification - -10 common/cmd_bootm.c Ramdisk header has bad magic number - -11 common/cmd_bootm.c Ramdisk header has bad checksum + -10 common/cmd_bootm.c Ramdisk header has bad magic number + -11 common/cmd_bootm.c Ramdisk header has bad checksum 10 common/cmd_bootm.c Ramdisk header is OK - -12 common/cmd_bootm.c Ramdisk data has bad checksum + -12 common/cmd_bootm.c Ramdisk data has bad checksum 11 common/cmd_bootm.c Ramdisk data has correct checksum 12 common/cmd_bootm.c Ramdisk verification complete, start loading -13 common/cmd_bootm.c Wrong Image Type (not PPC Linux Ramdisk) @@ -1363,7 +1479,13 @@ The following options need to be configured: -1 common/cmd_ide.c Read Error on boot device -1 common/cmd_ide.c Image header has bad magic number - -1 common/cmd_nvedit.c Environment not changable, but has bad CRC + -1 common/cmd_nand.c Bad usage of "nand" command + -1 common/cmd_nand.c No boot device + -1 common/cmd_nand.c Unknown Chip ID on boot device + -1 common/cmd_nand.c Read Error on boot device + -1 common/cmd_nand.c Image header has bad magic number + + -1 common/env_common.c Environment has a bad CRC, using default Modem Support: @@ -1383,6 +1505,19 @@ Modem Support: Enables debugging stuff (char screen[1024], dbg()) for modem support. Useful only with BDI2000. +- Interrupt support (PPC): + + There are common interrupt_init() and timer_interrupt() + for all PPC archs. interrupt_init() calls interrupt_init_cpu() + for cpu specific initialization. interrupt_init_cpu() + should set decrementer_count to appropriate value. If + cpu resets decrementer automatically after interrupt + (ppc4xx) it should set decrementer_count to zero. + timer_interrupt() calls timer_interrupt_cpu() for cpu + specific handling. If board has watchdog / status_led + / other_activity_monitor it works automatically from + general timer_interrupt(). + - General: In the target system modem support is enabled when a @@ -1445,6 +1580,10 @@ Configuration Settings: - CFG_ALT_MEMTEST: Enable an alternate, more extensive memory test. +- CFG_MEMTEST_SCRATCH: + Scratch address used by the alternate memory test + You only need to set this if address zero isn't writeable + - CFG_TFTP_LOADADDR: Default load address for network file downloads @@ -1519,7 +1658,11 @@ Configuration Settings: - CFG_FLASH_CFI: Define if the flash driver uses extra elements in the - common flash structure for storing flash geometry + common flash structure for storing flash geometry. + +- CFG_FLASH_CFI_DRIVER + This option also enables the building of the cfi_flash driver + in the drivers directory - CFG_RX_ETH_BUFFER: Defines the number of ethernet receive buffers. On some @@ -1650,7 +1793,7 @@ to save the current settings. - CFG_EEPROM_PAGE_WRITE_DELAY_MS: If defined, the number of milliseconds to delay between - page writes. The default is zero milliseconds. + page writes. The default is zero milliseconds. - CFG_I2C_EEPROM_ADDR_LEN: The length in bytes of the EEPROM memory array address. Note @@ -1660,6 +1803,20 @@ to save the current settings. The size in bytes of the EEPROM device. +- CFG_ENV_IS_IN_DATAFLASH: + + Define this if you have a DataFlash memory device which you + want to use for the environment. + + - CFG_ENV_OFFSET: + - CFG_ENV_ADDR: + - CFG_ENV_SIZE: + + These three #defines specify the offset and size of the + environment area within the total memory of your DataFlash placed + at the specified address. + + - CFG_SPI_INIT_OFFSET Defines offset to the initial SPI buffer area in DPRAM. The @@ -1686,6 +1843,14 @@ Note: once the monitor has been relocated, then it will complain if the default environment is used; a new CRC is computed as soon as you use the "saveenv" command to store a valid environment. +- CFG_FAULT_ECHO_LINK_DOWN: + Echo the inverted Ethernet link state to the fault LED. + + Note: If this option is active, then CFG_FAULT_MII_ADDR + also needs to be defined. + +- CFG_FAULT_MII_ADDR: + MII address of the PHY to check for the Ethernet link state. Low Level (hardware related) configuration options: --------------------------------------------------- @@ -1696,9 +1861,9 @@ Low Level (hardware related) configuration options: - CFG_DEFAULT_IMMR: Default address of the IMMR after system reset. - Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU, - and RPXsuper) to be able to adjust the position of - the IMMR register after a reset. + Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU, + and RPXsuper) to be able to adjust the position of + the IMMR register after a reset. - Floppy Disk Support: CFG_FDC_DRIVE_NUMBER @@ -1732,7 +1897,7 @@ Low Level (hardware related) configuration options: - CFG_INIT_RAM_ADDR: - Start address of memory area tha can be used for + Start address of memory area that can be used for initial data and stack; please note that this must be writable memory that is working WITHOUT special initialization, i. e. you CANNOT use normal RAM which @@ -1846,7 +2011,7 @@ change it to: CROSS_COMPILE = ppc_4xx- -U-Boot is intended to be simple to build. After installing the +U-Boot is intended to be simple to build. After installing the sources you must configure U-Boot for one specific board type. This is done by typing: @@ -1872,6 +2037,9 @@ configurations; the following names are supported: GEN860T_config EBONY_config FPS860L_config ELPT860_config cmi_mpc5xx_config NETVIA_config at91rm9200dk_config omap1510inn_config MPC8260ADS_config + omap1610inn_config ZPC1900_config MPC8540ADS_config + MPC8560ADS_config QS850_config QS823_config + QS860T_config DUET_ADS_config Note: for some board special configuration names may exist; check if additional information is available from the board vendor; for @@ -1904,7 +2072,7 @@ Note: for some board special configuration names may exist; check if Finally, type "make all", and you should get some working U-Boot -images ready for downlod to / installation on your system: +images ready for download to / installation on your system: - "u-boot.bin" is a raw binary image - "u-boot" is an image in ELF binary format @@ -1923,7 +2091,7 @@ steps: 1. Add a new configuration option for your board to the toplevel "Makefile" and to the "MAKEALL" script, using the existing entries as examples. Note that here and at many other places - boards and other names are listed alphabetically sorted. Please + boards and other names are listed in alphabetical sort order. Please keep this order. 2. Create a new directory to hold your board specific code. Add any files you need. In your board directory, you will need at least @@ -1953,7 +2121,7 @@ cation did not break existing code. At least make sure that *ALL* of the supported boards compile WITHOUT ANY compiler warnings. To do so, just run the "MAKEALL" script, which will configure and build U-Boot for ALL supported system. Be warned, this will take a while. You can -select which (cross) compiler to use py passing a `CROSS_COMPILE' +select which (cross) compiler to use by passing a `CROSS_COMPILE' environment variable to the script, i. e. to use the cross tools from MontaVista's Hard Hat Linux you can type @@ -1987,15 +2155,15 @@ mw - memory write (fill) cp - memory copy cmp - memory compare crc32 - checksum calculation -imd - i2c memory display -imm - i2c memory modify (auto-incrementing) -inm - i2c memory modify (constant address) -imw - i2c memory write (fill) -icrc32 - i2c checksum calculation -iprobe - probe to discover valid I2C chip addresses -iloop - infinite loop on address range -isdram - print SDRAM configuration information -sspi - SPI utility commands +imd - i2c memory display +imm - i2c memory modify (auto-incrementing) +inm - i2c memory modify (constant address) +imw - i2c memory write (fill) +icrc32 - i2c checksum calculation +iprobe - probe to discover valid I2C chip addresses +iloop - infinite loop on address range +isdram - print SDRAM configuration information +sspi - SPI utility commands base - print or set address offset printenv- print environment variables setenv - set environment variables @@ -2080,10 +2248,10 @@ Some configuration options can be set using Environment Variables: does not overwrite the U-Boot stack and data). For instance, when you have a system with 16 MB - RAM, and want to reseve 4 MB from use by Linux, + RAM, and want to reserve 4 MB from use by Linux, you can do this by adding "mem=12M" to the value of the "bootargs" variable. However, now you must make - sure, that the initrd image is placed in the first + sure that the initrd image is placed in the first 12 MB as well - this can be done with setenv initrd_high 00c00000 @@ -2118,6 +2286,7 @@ depending the information provided by your boot server: bootfile - see above dnsip - IP address of your Domain Name Server + dnsip2 - IP address of your secondary Domain Name Server gatewayip - IP address of the Gateway (Router) to use hostname - Target hostname ipaddr - see above @@ -2151,8 +2320,8 @@ only effect after the next boot (yes, that's just like Windoze :-). Command Line Parsing: ===================== -There are two different command line parsers available with U-Boot: -the old "simple" one, and the much more pwerful "hush" shell: +There are two different command line parsers available with U-Boot: +the old "simple" one, and the much more powerful "hush" shell: Old, simple command line parser: -------------------------------- @@ -2193,9 +2362,9 @@ General rules: Note for Redundant Ethernet Interfaces: ======================================= -Some boards come with redundand ethernet interfaces; U-Boot supports +Some boards come with redundant ethernet interfaces; U-Boot supports such configurations and is capable of automatic selection of a -"working" interface when needed. MAC assignemnt works as follows: +"working" interface when needed. MAC assignment works as follows: Network interfaces are numbered eth0, eth1, eth2, ... Corresponding MAC addresses can be stored in the environment as "ethaddr" (=>eth0), @@ -2237,10 +2406,9 @@ defines the following image properties: LynxOS, pSOS, QNX, RTEMS, ARTOS; Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS). * Target CPU Architecture (Provisions for Alpha, ARM, Intel x86, - IA64, MIPS, MIPS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; - Currently supported: PowerPC). -* Compression Type (Provisions for uncompressed, gzip, bzip2; - Currently supported: uncompressed, gzip). + IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; + Currently supported: ARM, Intel x86, MIPS, NIOS, PowerPC). +* Compression Type (uncompressed, gzip, bzip2) * Load Address * Entry Point * Image Name @@ -2255,21 +2423,21 @@ Linux Support: ============== Although U-Boot should support any OS or standalone application -easily, Linux has always been in the focus during the design of +easily, the main focus has always been on Linux during the design of U-Boot. U-Boot includes many features that so far have been part of some special "boot loader" code within the Linux kernel. Also, any "initrd" images to be used are no longer part of one big Linux image; instead, kernel and "initrd" are separate images. This implementation -serves serveral purposes: +serves several purposes: - the same features can be used for other OS or standalone applications (for instance: using compressed images to reduce the Flash memory footprint) - it becomes much easier to port new Linux kernel versions because - lots of low-level, hardware dependend stuff are done by U-Boot + lots of low-level, hardware dependent stuff are done by U-Boot - the same Linux kernel image can now be used with different "initrd" images; of course this also means that different kernel images can @@ -2324,7 +2492,7 @@ Example: make uImage The "uImage" build target uses a special tool (in 'tools/mkimage') to -encapsulate a compressed Linux kernel image with header information, +encapsulate a compressed Linux kernel image with header information, CRC32 checksum etc. for use with U-Boot. This is what we are doing: * build a standard "vmlinux" kernel image (in ELF binary format): @@ -2521,7 +2689,7 @@ parameters. You can check and modify this variable using the ... If you want to boot a Linux kernel with initial ram disk, you pass -the memory addreses of both the kernel and the initrd image (PPBCOOT +the memory addresses of both the kernel and the initrd image (PPBCOOT format!) to the "bootm" command: => imi 40100000 40200000 @@ -2701,7 +2869,7 @@ Hit 'q': Minicom warning: ================ -Over time, many people have reported problems when trying to used the +Over time, many people have reported problems when trying to use the "minicom" terminal emulation program for serial download. I (wd) consider minicom to be broken, and recommend not to use it. Under Unix, I recommend to use C-Kermit for general purpose use (and @@ -2711,9 +2879,9 @@ use "cu" for S-Record download ("loads" command). Nevertheless, if you absolutely want to use it try adding this configuration to your "File transfer protocols" section: - Name Program Name U/D FullScr IO-Red. Multi - X kermit /usr/bin/kermit -i -l %l -s Y U Y N N - Y kermit /usr/bin/kermit -i -l %l -r N D Y N N + Name Program Name U/D FullScr IO-Red. Multi + X kermit /usr/bin/kermit -i -l %l -s Y U Y N N + Y kermit /usr/bin/kermit -i -l %l -r N D Y N N NetBSD Notes: @@ -2769,7 +2937,7 @@ models provide on-chip memory (like the IMMR area on MPC8xx and MPC826x processors), on others (parts of) the data cache can be locked as (mis-) used as memory, etc. - Chris Hallinan posted a good summy of these issues to the + Chris Hallinan posted a good summary of these issues to the u-boot-users mailing list: Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)? @@ -2815,9 +2983,9 @@ code for the initialization procedures: * Do not use any unitialized global data (or implicitely initialized as zero data - BSS segment) at all - this is undefined, initiali- - zation is performed later (when relocationg to RAM). + zation is performed later (when relocating to RAM). -* Stack space is very limited. Avoid big data buffers or things like +* Stack space is very limited. Avoid big data buffers or things like that. Having only the stack as writable memory limits means we cannot use @@ -2830,7 +2998,7 @@ the GCC compiler (Global Register Variables) to share the data: we place a pointer (gd) to the global data into a register which we reserve for this purpose. -When chosing a register for such a purpose we are restricted by the +When choosing a register for such a purpose we are restricted by the relevant (E)ABI specifications for the current architecture, and by GCC's implementation. @@ -2838,7 +3006,7 @@ For PowerPC, the following registers have specific use: R1: stack pointer R2: TOC pointer R3-R4: parameter passing and return values - R5-R10: parameter passing + R5-R10: parameter passing R13: small data area pointer R30: GOT pointer R31: frame pointer @@ -2920,7 +3088,7 @@ System Initialization: In the reset configuration, U-Boot starts at the reset entry point (on most PowerPC systens at address 0x00000100). Because of the reset configuration for CS0# this is a mirror of the onboard Flash memory. -To be able to re-map memory U-Boot then jumps to it's link address. +To be able to re-map memory U-Boot then jumps to its link address. To be able to implement the initialization code in C, a (small!) initial stack is set up in the internal Dual Ported RAM (in case CPUs which provide such a feature like MPC8xx or MPC8260), or in a locked @@ -2936,7 +3104,7 @@ simple memory test is run that determines the size of the SDRAM banks. When there is more than one SDRAM bank, and the banks are of -different size, the larger is mapped first. For equal size, the first +different size, the largest is mapped first. For equal size, the first bank (CS2#) is mapped first. The first mapping is always for address 0x00000000, with any additional banks following immediately to create contiguous memory starting from 0. @@ -2981,7 +3149,7 @@ int main (int argc, char *argv[]) while (learning) { Read the README file in the top level directory; - Read http://www.denx.de/re/DPLG.html + Read http://www.denx.de/twiki/bin/view/DULG/Manual ; Read the source, Luke; } @@ -3025,6 +3193,13 @@ Please note that U-Boot is implemented in C (and to some small parts in Assembler); no C++ is used, so please do not use C++ style comments (//) in your code. +Please also stick to the following formatting rules: +- remove any trailing white space +- use TAB characters for indentation, not spaces +- make sure NOT to use DOS '\r\n' line feeds +- do not add more than 2 empty lines to source files +- do not add trailing empty lines to source files + Submissions which do not conform to the standards may be returned with a request to reformat the changes.