README 125 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147114811491150115111521153115411551156115711581159116011611162116311641165116611671168116911701171117211731174117511761177117811791180118111821183118411851186118711881189119011911192119311941195119611971198119912001201120212031204120512061207120812091210121112121213121412151216121712181219122012211222122312241225122612271228122912301231123212331234123512361237123812391240124112421243124412451246124712481249125012511252125312541255125612571258125912601261126212631264126512661267126812691270127112721273127412751276127712781279128012811282128312841285128612871288128912901291129212931294129512961297129812991300130113021303130413051306130713081309131013111312131313141315131613171318131913201321132213231324132513261327132813291330133113321333133413351336133713381339134013411342134313441345134613471348134913501351135213531354135513561357135813591360136113621363136413651366136713681369137013711372137313741375137613771378137913801381138213831384138513861387138813891390139113921393139413951396139713981399140014011402140314041405140614071408140914101411141214131414141514161417141814191420142114221423142414251426142714281429143014311432143314341435143614371438143914401441144214431444144514461447144814491450145114521453145414551456145714581459146014611462146314641465146614671468146914701471147214731474147514761477147814791480148114821483148414851486148714881489149014911492149314941495149614971498149915001501150215031504150515061507150815091510151115121513151415151516151715181519152015211522152315241525152615271528152915301531153215331534153515361537153815391540154115421543154415451546154715481549155015511552155315541555155615571558155915601561156215631564156515661567156815691570157115721573157415751576157715781579158015811582158315841585158615871588158915901591159215931594159515961597159815991600160116021603160416051606160716081609161016111612161316141615161616171618161916201621162216231624162516261627162816291630163116321633163416351636163716381639164016411642164316441645164616471648164916501651165216531654165516561657165816591660166116621663166416651666166716681669167016711672167316741675167616771678167916801681168216831684168516861687168816891690169116921693169416951696169716981699170017011702170317041705170617071708170917101711171217131714171517161717171817191720172117221723172417251726172717281729173017311732173317341735173617371738173917401741174217431744174517461747174817491750175117521753175417551756175717581759176017611762176317641765176617671768176917701771177217731774177517761777177817791780178117821783178417851786178717881789179017911792179317941795179617971798179918001801180218031804180518061807180818091810181118121813181418151816181718181819182018211822182318241825182618271828182918301831183218331834183518361837183818391840184118421843184418451846184718481849185018511852185318541855185618571858185918601861186218631864186518661867186818691870187118721873187418751876187718781879188018811882188318841885188618871888188918901891189218931894189518961897189818991900190119021903190419051906190719081909191019111912191319141915191619171918191919201921192219231924192519261927192819291930193119321933193419351936193719381939194019411942194319441945194619471948194919501951195219531954195519561957195819591960196119621963196419651966196719681969197019711972197319741975197619771978197919801981198219831984198519861987198819891990199119921993199419951996199719981999200020012002200320042005200620072008200920102011201220132014201520162017201820192020202120222023202420252026202720282029203020312032203320342035203620372038203920402041204220432044204520462047204820492050205120522053205420552056205720582059206020612062206320642065206620672068206920702071207220732074207520762077207820792080208120822083208420852086208720882089209020912092209320942095209620972098209921002101210221032104210521062107210821092110211121122113211421152116211721182119212021212122212321242125212621272128212921302131213221332134213521362137213821392140214121422143214421452146214721482149215021512152215321542155215621572158215921602161216221632164216521662167216821692170217121722173217421752176217721782179218021812182218321842185218621872188218921902191219221932194219521962197219821992200220122022203220422052206220722082209221022112212221322142215221622172218221922202221222222232224222522262227222822292230223122322233223422352236223722382239224022412242224322442245224622472248224922502251225222532254225522562257225822592260226122622263226422652266226722682269227022712272227322742275227622772278227922802281228222832284228522862287228822892290229122922293229422952296229722982299230023012302230323042305230623072308230923102311231223132314231523162317231823192320232123222323232423252326232723282329233023312332233323342335233623372338233923402341234223432344234523462347234823492350235123522353235423552356235723582359236023612362236323642365236623672368236923702371237223732374237523762377237823792380238123822383238423852386238723882389239023912392239323942395239623972398239924002401240224032404240524062407240824092410241124122413241424152416241724182419242024212422242324242425242624272428242924302431243224332434243524362437243824392440244124422443244424452446244724482449245024512452245324542455245624572458245924602461246224632464246524662467246824692470247124722473247424752476247724782479248024812482248324842485248624872488248924902491249224932494249524962497249824992500250125022503250425052506250725082509251025112512251325142515251625172518251925202521252225232524252525262527252825292530253125322533253425352536253725382539254025412542254325442545254625472548254925502551255225532554255525562557255825592560256125622563256425652566256725682569257025712572257325742575257625772578257925802581258225832584258525862587258825892590259125922593259425952596259725982599260026012602260326042605260626072608260926102611261226132614261526162617261826192620262126222623262426252626262726282629263026312632263326342635263626372638263926402641264226432644264526462647264826492650265126522653265426552656265726582659266026612662266326642665266626672668266926702671267226732674267526762677267826792680268126822683268426852686268726882689269026912692269326942695269626972698269927002701270227032704270527062707270827092710271127122713271427152716271727182719272027212722272327242725272627272728272927302731273227332734273527362737273827392740274127422743274427452746274727482749275027512752275327542755275627572758275927602761276227632764276527662767276827692770277127722773277427752776277727782779278027812782278327842785278627872788278927902791279227932794279527962797279827992800280128022803280428052806280728082809281028112812281328142815281628172818281928202821282228232824282528262827282828292830283128322833283428352836283728382839284028412842284328442845284628472848284928502851285228532854285528562857285828592860286128622863286428652866286728682869287028712872287328742875287628772878287928802881288228832884288528862887288828892890289128922893289428952896289728982899290029012902290329042905290629072908290929102911291229132914291529162917291829192920292129222923292429252926292729282929293029312932293329342935293629372938293929402941294229432944294529462947294829492950295129522953295429552956295729582959296029612962296329642965296629672968296929702971297229732974297529762977297829792980298129822983298429852986298729882989299029912992299329942995299629972998299930003001300230033004300530063007300830093010301130123013301430153016301730183019302030213022302330243025302630273028302930303031303230333034303530363037303830393040304130423043304430453046304730483049305030513052305330543055305630573058305930603061306230633064306530663067306830693070307130723073307430753076307730783079308030813082308330843085308630873088308930903091309230933094309530963097309830993100310131023103310431053106310731083109311031113112311331143115311631173118311931203121312231233124312531263127312831293130313131323133313431353136313731383139314031413142314331443145314631473148314931503151315231533154315531563157315831593160316131623163316431653166316731683169317031713172317331743175317631773178317931803181318231833184318531863187318831893190319131923193319431953196319731983199320032013202320332043205320632073208320932103211321232133214321532163217321832193220322132223223322432253226322732283229323032313232323332343235323632373238323932403241324232433244324532463247324832493250325132523253325432553256325732583259326032613262326332643265326632673268326932703271327232733274327532763277327832793280328132823283328432853286328732883289329032913292329332943295329632973298329933003301330233033304330533063307330833093310331133123313331433153316331733183319332033213322332333243325332633273328332933303331333233333334333533363337333833393340334133423343334433453346334733483349335033513352335333543355335633573358335933603361336233633364336533663367336833693370337133723373337433753376337733783379338033813382338333843385338633873388338933903391339233933394339533963397339833993400340134023403340434053406340734083409341034113412341334143415341634173418341934203421342234233424342534263427342834293430343134323433343434353436343734383439344034413442344334443445344634473448344934503451345234533454345534563457345834593460346134623463346434653466346734683469347034713472347334743475347634773478347934803481348234833484348534863487348834893490349134923493349434953496349734983499350035013502350335043505350635073508350935103511351235133514351535163517351835193520352135223523352435253526352735283529353035313532353335343535353635373538353935403541354235433544354535463547354835493550355135523553355435553556355735583559356035613562356335643565356635673568356935703571357235733574357535763577357835793580358135823583358435853586358735883589359035913592359335943595359635973598359936003601360236033604360536063607360836093610361136123613361436153616361736183619362036213622362336243625362636273628362936303631363236333634363536363637363836393640364136423643364436453646364736483649365036513652365336543655365636573658365936603661366236633664366536663667366836693670367136723673367436753676367736783679368036813682368336843685368636873688368936903691369236933694369536963697369836993700370137023703370437053706370737083709371037113712371337143715371637173718371937203721372237233724372537263727372837293730373137323733373437353736373737383739374037413742374337443745374637473748374937503751375237533754375537563757375837593760376137623763376437653766376737683769377037713772377337743775377637773778377937803781378237833784
  1. #
  2. # (C) Copyright 2000 - 2005
  3. # Wolfgang Denk, DENX Software Engineering, wd@denx.de.
  4. #
  5. # See file CREDITS for list of people who contributed to this
  6. # project.
  7. #
  8. # This program is free software; you can redistribute it and/or
  9. # modify it under the terms of the GNU General Public License as
  10. # published by the Free Software Foundation; either version 2 of
  11. # the License, or (at your option) any later version.
  12. #
  13. # This program is distributed in the hope that it will be useful,
  14. # but WITHOUT ANY WARRANTY; without even the implied warranty of
  15. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  16. # GNU General Public License for more details.
  17. #
  18. # You should have received a copy of the GNU General Public License
  19. # along with this program; if not, write to the Free Software
  20. # Foundation, Inc., 59 Temple Place, Suite 330, Boston,
  21. # MA 02111-1307 USA
  22. #
  23. Summary:
  24. ========
  25. This directory contains the source code for U-Boot, a boot loader for
  26. Embedded boards based on PowerPC, ARM, MIPS and several other
  27. processors, which can be installed in a boot ROM and used to
  28. initialize and test the hardware or to download and run application
  29. code.
  30. The development of U-Boot is closely related to Linux: some parts of
  31. the source code originate in the Linux source tree, we have some
  32. header files in common, and special provision has been made to
  33. support booting of Linux images.
  34. Some attention has been paid to make this software easily
  35. configurable and extendable. For instance, all monitor commands are
  36. implemented with the same call interface, so that it's very easy to
  37. add new commands. Also, instead of permanently adding rarely used
  38. code (for instance hardware test utilities) to the monitor, you can
  39. load and run it dynamically.
  40. Status:
  41. =======
  42. In general, all boards for which a configuration option exists in the
  43. Makefile have been tested to some extent and can be considered
  44. "working". In fact, many of them are used in production systems.
  45. In case of problems see the CHANGELOG and CREDITS files to find out
  46. who contributed the specific port.
  47. Where to get help:
  48. ==================
  49. In case you have questions about, problems with or contributions for
  50. U-Boot you should send a message to the U-Boot mailing list at
  51. <u-boot-users@lists.sourceforge.net>. There is also an archive of
  52. previous traffic on the mailing list - please search the archive
  53. before asking FAQ's. Please see
  54. http://lists.sourceforge.net/lists/listinfo/u-boot-users/
  55. Where we come from:
  56. ===================
  57. - start from 8xxrom sources
  58. - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
  59. - clean up code
  60. - make it easier to add custom boards
  61. - make it possible to add other [PowerPC] CPUs
  62. - extend functions, especially:
  63. * Provide extended interface to Linux boot loader
  64. * S-Record download
  65. * network boot
  66. * PCMCIA / CompactFLash / ATA disk / SCSI ... boot
  67. - create ARMBoot project (http://sourceforge.net/projects/armboot)
  68. - add other CPU families (starting with ARM)
  69. - create U-Boot project (http://sourceforge.net/projects/u-boot)
  70. Names and Spelling:
  71. ===================
  72. The "official" name of this project is "Das U-Boot". The spelling
  73. "U-Boot" shall be used in all written text (documentation, comments
  74. in source files etc.). Example:
  75. This is the README file for the U-Boot project.
  76. File names etc. shall be based on the string "u-boot". Examples:
  77. include/asm-ppc/u-boot.h
  78. #include <asm/u-boot.h>
  79. Variable names, preprocessor constants etc. shall be either based on
  80. the string "u_boot" or on "U_BOOT". Example:
  81. U_BOOT_VERSION u_boot_logo
  82. IH_OS_U_BOOT u_boot_hush_start
  83. Versioning:
  84. ===========
  85. U-Boot uses a 3 level version number containing a version, a
  86. sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",
  87. sub-version "34", and patchlevel "4".
  88. The patchlevel is used to indicate certain stages of development
  89. between released versions, i. e. officially released versions of
  90. U-Boot will always have a patchlevel of "0".
  91. Directory Hierarchy:
  92. ====================
  93. - board Board dependent files
  94. - common Misc architecture independent functions
  95. - cpu CPU specific files
  96. - 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
  97. - arm720t Files specific to ARM 720 CPUs
  98. - arm920t Files specific to ARM 920 CPUs
  99. - at91rm9200 Files specific to Atmel AT91RM9200 CPU
  100. - imx Files specific to Freescale MC9328 i.MX CPUs
  101. - s3c24x0 Files specific to Samsung S3C24X0 CPUs
  102. - arm925t Files specific to ARM 925 CPUs
  103. - arm926ejs Files specific to ARM 926 CPUs
  104. - arm1136 Files specific to ARM 1136 CPUs
  105. - at32ap Files specific to Atmel AVR32 AP CPUs
  106. - i386 Files specific to i386 CPUs
  107. - ixp Files specific to Intel XScale IXP CPUs
  108. - mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
  109. - mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs
  110. - mcf532x Files specific to Freescale ColdFire MCF5329 CPUs
  111. - mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs
  112. - mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs
  113. - mips Files specific to MIPS CPUs
  114. - mpc5xx Files specific to Freescale MPC5xx CPUs
  115. - mpc5xxx Files specific to Freescale MPC5xxx CPUs
  116. - mpc8xx Files specific to Freescale MPC8xx CPUs
  117. - mpc8220 Files specific to Freescale MPC8220 CPUs
  118. - mpc824x Files specific to Freescale MPC824x CPUs
  119. - mpc8260 Files specific to Freescale MPC8260 CPUs
  120. - mpc85xx Files specific to Freescale MPC85xx CPUs
  121. - nios Files specific to Altera NIOS CPUs
  122. - nios2 Files specific to Altera Nios-II CPUs
  123. - ppc4xx Files specific to AMCC PowerPC 4xx CPUs
  124. - pxa Files specific to Intel XScale PXA CPUs
  125. - s3c44b0 Files specific to Samsung S3C44B0 CPUs
  126. - sa1100 Files specific to Intel StrongARM SA1100 CPUs
  127. - disk Code for disk drive partition handling
  128. - doc Documentation (don't expect too much)
  129. - drivers Commonly used device drivers
  130. - dtt Digital Thermometer and Thermostat drivers
  131. - examples Example code for standalone applications, etc.
  132. - include Header Files
  133. - lib_arm Files generic to ARM architecture
  134. - lib_avr32 Files generic to AVR32 architecture
  135. - lib_generic Files generic to all architectures
  136. - lib_i386 Files generic to i386 architecture
  137. - lib_m68k Files generic to m68k architecture
  138. - lib_mips Files generic to MIPS architecture
  139. - lib_nios Files generic to NIOS architecture
  140. - lib_ppc Files generic to PowerPC architecture
  141. - libfdt Library files to support flattened device trees
  142. - net Networking code
  143. - post Power On Self Test
  144. - rtc Real Time Clock drivers
  145. - tools Tools to build S-Record or U-Boot images, etc.
  146. Software Configuration:
  147. =======================
  148. Configuration is usually done using C preprocessor defines; the
  149. rationale behind that is to avoid dead code whenever possible.
  150. There are two classes of configuration variables:
  151. * Configuration _OPTIONS_:
  152. These are selectable by the user and have names beginning with
  153. "CONFIG_".
  154. * Configuration _SETTINGS_:
  155. These depend on the hardware etc. and should not be meddled with if
  156. you don't know what you're doing; they have names beginning with
  157. "CFG_".
  158. Later we will add a configuration tool - probably similar to or even
  159. identical to what's used for the Linux kernel. Right now, we have to
  160. do the configuration by hand, which means creating some symbolic
  161. links and editing some configuration files. We use the TQM8xxL boards
  162. as an example here.
  163. Selection of Processor Architecture and Board Type:
  164. ---------------------------------------------------
  165. For all supported boards there are ready-to-use default
  166. configurations available; just type "make <board_name>_config".
  167. Example: For a TQM823L module type:
  168. cd u-boot
  169. make TQM823L_config
  170. For the Cogent platform, you need to specify the cpu type as well;
  171. e.g. "make cogent_mpc8xx_config". And also configure the cogent
  172. directory according to the instructions in cogent/README.
  173. Configuration Options:
  174. ----------------------
  175. Configuration depends on the combination of board and CPU type; all
  176. such information is kept in a configuration file
  177. "include/configs/<board_name>.h".
  178. Example: For a TQM823L module, all configuration settings are in
  179. "include/configs/TQM823L.h".
  180. Many of the options are named exactly as the corresponding Linux
  181. kernel configuration options. The intention is to make it easier to
  182. build a config tool - later.
  183. The following options need to be configured:
  184. - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
  185. - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
  186. - CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)
  187. Define exactly one, e.g. CONFIG_ATSTK1002
  188. - CPU Module Type: (if CONFIG_COGENT is defined)
  189. Define exactly one of
  190. CONFIG_CMA286_60_OLD
  191. --- FIXME --- not tested yet:
  192. CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
  193. CONFIG_CMA287_23, CONFIG_CMA287_50
  194. - Motherboard Type: (if CONFIG_COGENT is defined)
  195. Define exactly one of
  196. CONFIG_CMA101, CONFIG_CMA102
  197. - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
  198. Define one or more of
  199. CONFIG_CMA302
  200. - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
  201. Define one or more of
  202. CONFIG_LCD_HEARTBEAT - update a character position on
  203. the lcd display every second with
  204. a "rotator" |\-/|\-/
  205. - Board flavour: (if CONFIG_MPC8260ADS is defined)
  206. CONFIG_ADSTYPE
  207. Possible values are:
  208. CFG_8260ADS - original MPC8260ADS
  209. CFG_8266ADS - MPC8266ADS
  210. CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
  211. CFG_8272ADS - MPC8272ADS
  212. - MPC824X Family Member (if CONFIG_MPC824X is defined)
  213. Define exactly one of
  214. CONFIG_MPC8240, CONFIG_MPC8245
  215. - 8xx CPU Options: (if using an MPC8xx cpu)
  216. CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
  217. get_gclk_freq() cannot work
  218. e.g. if there is no 32KHz
  219. reference PIT/RTC clock
  220. CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
  221. or XTAL/EXTAL)
  222. - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
  223. CFG_8xx_CPUCLK_MIN
  224. CFG_8xx_CPUCLK_MAX
  225. CONFIG_8xx_CPUCLK_DEFAULT
  226. See doc/README.MPC866
  227. CFG_MEASURE_CPUCLK
  228. Define this to measure the actual CPU clock instead
  229. of relying on the correctness of the configured
  230. values. Mostly useful for board bringup to make sure
  231. the PLL is locked at the intended frequency. Note
  232. that this requires a (stable) reference clock (32 kHz
  233. RTC clock or CFG_8XX_XIN)
  234. - Intel Monahans options:
  235. CFG_MONAHANS_RUN_MODE_OSC_RATIO
  236. Defines the Monahans run mode to oscillator
  237. ratio. Valid values are 8, 16, 24, 31. The core
  238. frequency is this value multiplied by 13 MHz.
  239. CFG_MONAHANS_TURBO_RUN_MODE_RATIO
  240. Defines the Monahans turbo mode to oscillator
  241. ratio. Valid values are 1 (default if undefined) and
  242. 2. The core frequency as calculated above is multiplied
  243. by this value.
  244. - Linux Kernel Interface:
  245. CONFIG_CLOCKS_IN_MHZ
  246. U-Boot stores all clock information in Hz
  247. internally. For binary compatibility with older Linux
  248. kernels (which expect the clocks passed in the
  249. bd_info data to be in MHz) the environment variable
  250. "clocks_in_mhz" can be defined so that U-Boot
  251. converts clock data to MHZ before passing it to the
  252. Linux kernel.
  253. When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
  254. "clocks_in_mhz=1" is automatically included in the
  255. default environment.
  256. CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
  257. When transfering memsize parameter to linux, some versions
  258. expect it to be in bytes, others in MB.
  259. Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
  260. CONFIG_OF_LIBFDT / CONFIG_OF_FLAT_TREE
  261. New kernel versions are expecting firmware settings to be
  262. passed using flattened device trees (based on open firmware
  263. concepts).
  264. CONFIG_OF_LIBFDT
  265. * New libfdt-based support
  266. * Adds the "fdt" command
  267. * The bootm command automatically updates the fdt
  268. CONFIG_OF_FLAT_TREE
  269. * Deprecated, see CONFIG_OF_LIBFDT
  270. * Original ft_build.c-based support
  271. * Automatically modifies the dft as part of the bootm command
  272. * The environment variable "disable_of", when set,
  273. disables this functionality.
  274. OF_CPU - The proper name of the cpus node.
  275. OF_SOC - The proper name of the soc node.
  276. OF_TBCLK - The timebase frequency.
  277. OF_STDOUT_PATH - The path to the console device
  278. boards with QUICC Engines require OF_QE to set UCC mac addresses
  279. CONFIG_OF_HAS_BD_T
  280. * CONFIG_OF_LIBFDT - enables the "fdt bd_t" command
  281. * CONFIG_OF_FLAT_TREE - The resulting flat device tree
  282. will have a copy of the bd_t. Space should be
  283. pre-allocated in the dts for the bd_t.
  284. CONFIG_OF_HAS_UBOOT_ENV
  285. * CONFIG_OF_LIBFDT - enables the "fdt env" command
  286. * CONFIG_OF_FLAT_TREE - The resulting flat device tree
  287. will have a copy of u-boot's environment variables
  288. CONFIG_OF_BOARD_SETUP
  289. Board code has addition modification that it wants to make
  290. to the flat device tree before handing it off to the kernel
  291. CONFIG_OF_BOOT_CPU
  292. This define fills in the correct boot cpu in the boot
  293. param header, the default value is zero if undefined.
  294. - Serial Ports:
  295. CFG_PL010_SERIAL
  296. Define this if you want support for Amba PrimeCell PL010 UARTs.
  297. CFG_PL011_SERIAL
  298. Define this if you want support for Amba PrimeCell PL011 UARTs.
  299. CONFIG_PL011_CLOCK
  300. If you have Amba PrimeCell PL011 UARTs, set this variable to
  301. the clock speed of the UARTs.
  302. CONFIG_PL01x_PORTS
  303. If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
  304. define this to a list of base addresses for each (supported)
  305. port. See e.g. include/configs/versatile.h
  306. - Console Interface:
  307. Depending on board, define exactly one serial port
  308. (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
  309. CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
  310. console by defining CONFIG_8xx_CONS_NONE
  311. Note: if CONFIG_8xx_CONS_NONE is defined, the serial
  312. port routines must be defined elsewhere
  313. (i.e. serial_init(), serial_getc(), ...)
  314. CONFIG_CFB_CONSOLE
  315. Enables console device for a color framebuffer. Needs following
  316. defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
  317. VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
  318. (default big endian)
  319. VIDEO_HW_RECTFILL graphic chip supports
  320. rectangle fill
  321. (cf. smiLynxEM)
  322. VIDEO_HW_BITBLT graphic chip supports
  323. bit-blit (cf. smiLynxEM)
  324. VIDEO_VISIBLE_COLS visible pixel columns
  325. (cols=pitch)
  326. VIDEO_VISIBLE_ROWS visible pixel rows
  327. VIDEO_PIXEL_SIZE bytes per pixel
  328. VIDEO_DATA_FORMAT graphic data format
  329. (0-5, cf. cfb_console.c)
  330. VIDEO_FB_ADRS framebuffer address
  331. VIDEO_KBD_INIT_FCT keyboard int fct
  332. (i.e. i8042_kbd_init())
  333. VIDEO_TSTC_FCT test char fct
  334. (i.e. i8042_tstc)
  335. VIDEO_GETC_FCT get char fct
  336. (i.e. i8042_getc)
  337. CONFIG_CONSOLE_CURSOR cursor drawing on/off
  338. (requires blink timer
  339. cf. i8042.c)
  340. CFG_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
  341. CONFIG_CONSOLE_TIME display time/date info in
  342. upper right corner
  343. (requires CONFIG_CMD_DATE)
  344. CONFIG_VIDEO_LOGO display Linux logo in
  345. upper left corner
  346. CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
  347. linux_logo.h for logo.
  348. Requires CONFIG_VIDEO_LOGO
  349. CONFIG_CONSOLE_EXTRA_INFO
  350. addional board info beside
  351. the logo
  352. When CONFIG_CFB_CONSOLE is defined, video console is
  353. default i/o. Serial console can be forced with
  354. environment 'console=serial'.
  355. When CONFIG_SILENT_CONSOLE is defined, all console
  356. messages (by U-Boot and Linux!) can be silenced with
  357. the "silent" environment variable. See
  358. doc/README.silent for more information.
  359. - Console Baudrate:
  360. CONFIG_BAUDRATE - in bps
  361. Select one of the baudrates listed in
  362. CFG_BAUDRATE_TABLE, see below.
  363. CFG_BRGCLK_PRESCALE, baudrate prescale
  364. - Interrupt driven serial port input:
  365. CONFIG_SERIAL_SOFTWARE_FIFO
  366. PPC405GP only.
  367. Use an interrupt handler for receiving data on the
  368. serial port. It also enables using hardware handshake
  369. (RTS/CTS) and UART's built-in FIFO. Set the number of
  370. bytes the interrupt driven input buffer should have.
  371. Leave undefined to disable this feature, including
  372. disable the buffer and hardware handshake.
  373. - Console UART Number:
  374. CONFIG_UART1_CONSOLE
  375. AMCC PPC4xx only.
  376. If defined internal UART1 (and not UART0) is used
  377. as default U-Boot console.
  378. - Boot Delay: CONFIG_BOOTDELAY - in seconds
  379. Delay before automatically booting the default image;
  380. set to -1 to disable autoboot.
  381. See doc/README.autoboot for these options that
  382. work with CONFIG_BOOTDELAY. None are required.
  383. CONFIG_BOOT_RETRY_TIME
  384. CONFIG_BOOT_RETRY_MIN
  385. CONFIG_AUTOBOOT_KEYED
  386. CONFIG_AUTOBOOT_PROMPT
  387. CONFIG_AUTOBOOT_DELAY_STR
  388. CONFIG_AUTOBOOT_STOP_STR
  389. CONFIG_AUTOBOOT_DELAY_STR2
  390. CONFIG_AUTOBOOT_STOP_STR2
  391. CONFIG_ZERO_BOOTDELAY_CHECK
  392. CONFIG_RESET_TO_RETRY
  393. - Autoboot Command:
  394. CONFIG_BOOTCOMMAND
  395. Only needed when CONFIG_BOOTDELAY is enabled;
  396. define a command string that is automatically executed
  397. when no character is read on the console interface
  398. within "Boot Delay" after reset.
  399. CONFIG_BOOTARGS
  400. This can be used to pass arguments to the bootm
  401. command. The value of CONFIG_BOOTARGS goes into the
  402. environment value "bootargs".
  403. CONFIG_RAMBOOT and CONFIG_NFSBOOT
  404. The value of these goes into the environment as
  405. "ramboot" and "nfsboot" respectively, and can be used
  406. as a convenience, when switching between booting from
  407. ram and nfs.
  408. - Pre-Boot Commands:
  409. CONFIG_PREBOOT
  410. When this option is #defined, the existence of the
  411. environment variable "preboot" will be checked
  412. immediately before starting the CONFIG_BOOTDELAY
  413. countdown and/or running the auto-boot command resp.
  414. entering interactive mode.
  415. This feature is especially useful when "preboot" is
  416. automatically generated or modified. For an example
  417. see the LWMON board specific code: here "preboot" is
  418. modified when the user holds down a certain
  419. combination of keys on the (special) keyboard when
  420. booting the systems
  421. - Serial Download Echo Mode:
  422. CONFIG_LOADS_ECHO
  423. If defined to 1, all characters received during a
  424. serial download (using the "loads" command) are
  425. echoed back. This might be needed by some terminal
  426. emulations (like "cu"), but may as well just take
  427. time on others. This setting #define's the initial
  428. value of the "loads_echo" environment variable.
  429. - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
  430. CONFIG_KGDB_BAUDRATE
  431. Select one of the baudrates listed in
  432. CFG_BAUDRATE_TABLE, see below.
  433. - Monitor Functions:
  434. Monitor commands can be included or excluded
  435. from the build by using the #include files
  436. "config_cmd_all.h" and #undef'ing unwanted
  437. commands, or using "config_cmd_default.h"
  438. and augmenting with additional #define's
  439. for wanted commands.
  440. The default command configuration includes all commands
  441. except those marked below with a "*".
  442. CONFIG_CMD_ASKENV * ask for env variable
  443. CONFIG_CMD_AUTOSCRIPT Autoscript Support
  444. CONFIG_CMD_BDI bdinfo
  445. CONFIG_CMD_BEDBUG * Include BedBug Debugger
  446. CONFIG_CMD_BMP * BMP support
  447. CONFIG_CMD_BSP * Board specific commands
  448. CONFIG_CMD_BOOTD bootd
  449. CONFIG_CMD_CACHE * icache, dcache
  450. CONFIG_CMD_CONSOLE coninfo
  451. CONFIG_CMD_DATE * support for RTC, date/time...
  452. CONFIG_CMD_DHCP * DHCP support
  453. CONFIG_CMD_DIAG * Diagnostics
  454. CONFIG_CMD_DOC * Disk-On-Chip Support
  455. CONFIG_CMD_DTT * Digital Therm and Thermostat
  456. CONFIG_CMD_ECHO echo arguments
  457. CONFIG_CMD_EEPROM * EEPROM read/write support
  458. CONFIG_CMD_ELF * bootelf, bootvx
  459. CONFIG_CMD_ENV saveenv
  460. CONFIG_CMD_FDC * Floppy Disk Support
  461. CONFIG_CMD_FAT * FAT partition support
  462. CONFIG_CMD_FDOS * Dos diskette Support
  463. CONFIG_CMD_FLASH flinfo, erase, protect
  464. CONFIG_CMD_FPGA FPGA device initialization support
  465. CONFIG_CMD_HWFLOW * RTS/CTS hw flow control
  466. CONFIG_CMD_I2C * I2C serial bus support
  467. CONFIG_CMD_IDE * IDE harddisk support
  468. CONFIG_CMD_IMI iminfo
  469. CONFIG_CMD_IMLS List all found images
  470. CONFIG_CMD_IMMAP * IMMR dump support
  471. CONFIG_CMD_IRQ * irqinfo
  472. CONFIG_CMD_ITEST Integer/string test of 2 values
  473. CONFIG_CMD_JFFS2 * JFFS2 Support
  474. CONFIG_CMD_KGDB * kgdb
  475. CONFIG_CMD_LOADB loadb
  476. CONFIG_CMD_LOADS loads
  477. CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
  478. loop, loopw, mtest
  479. CONFIG_CMD_MISC Misc functions like sleep etc
  480. CONFIG_CMD_MMC * MMC memory mapped support
  481. CONFIG_CMD_MII * MII utility commands
  482. CONFIG_CMD_NAND * NAND support
  483. CONFIG_CMD_NET bootp, tftpboot, rarpboot
  484. CONFIG_CMD_PCI * pciinfo
  485. CONFIG_CMD_PCMCIA * PCMCIA support
  486. CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network
  487. host
  488. CONFIG_CMD_PORTIO * Port I/O
  489. CONFIG_CMD_REGINFO * Register dump
  490. CONFIG_CMD_RUN run command in env variable
  491. CONFIG_CMD_SAVES * save S record dump
  492. CONFIG_CMD_SCSI * SCSI Support
  493. CONFIG_CMD_SDRAM * print SDRAM configuration information
  494. (requires CONFIG_CMD_I2C)
  495. CONFIG_CMD_SETGETDCR Support for DCR Register access
  496. (4xx only)
  497. CONFIG_CMD_SPI * SPI serial bus support
  498. CONFIG_CMD_USB * USB support
  499. CONFIG_CMD_VFD * VFD support (TRAB)
  500. CONFIG_CMD_BSP * Board SPecific functions
  501. CONFIG_CMD_CDP * Cisco Discover Protocol support
  502. CONFIG_CMD_FSL * Microblaze FSL support
  503. EXAMPLE: If you want all functions except of network
  504. support you can write:
  505. #include "config_cmd_all.h"
  506. #undef CONFIG_CMD_NET
  507. Other Commands:
  508. fdt (flattened device tree) command: CONFIG_OF_LIBFDT
  509. Note: Don't enable the "icache" and "dcache" commands
  510. (configuration option CONFIG_CMD_CACHE) unless you know
  511. what you (and your U-Boot users) are doing. Data
  512. cache cannot be enabled on systems like the 8xx or
  513. 8260 (where accesses to the IMMR region must be
  514. uncached), and it cannot be disabled on all other
  515. systems where we (mis-) use the data cache to hold an
  516. initial stack and some data.
  517. XXX - this list needs to get updated!
  518. - Watchdog:
  519. CONFIG_WATCHDOG
  520. If this variable is defined, it enables watchdog
  521. support. There must be support in the platform specific
  522. code for a watchdog. For the 8xx and 8260 CPUs, the
  523. SIU Watchdog feature is enabled in the SYPCR
  524. register.
  525. - U-Boot Version:
  526. CONFIG_VERSION_VARIABLE
  527. If this variable is defined, an environment variable
  528. named "ver" is created by U-Boot showing the U-Boot
  529. version as printed by the "version" command.
  530. This variable is readonly.
  531. - Real-Time Clock:
  532. When CONFIG_CMD_DATE is selected, the type of the RTC
  533. has to be selected, too. Define exactly one of the
  534. following options:
  535. CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
  536. CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
  537. CONFIG_RTC_MC146818 - use MC146818 RTC
  538. CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
  539. CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
  540. CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
  541. CONFIG_RTC_DS164x - use Dallas DS164x RTC
  542. CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
  543. CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
  544. Note that if the RTC uses I2C, then the I2C interface
  545. must also be configured. See I2C Support, below.
  546. - Timestamp Support:
  547. When CONFIG_TIMESTAMP is selected, the timestamp
  548. (date and time) of an image is printed by image
  549. commands like bootm or iminfo. This option is
  550. automatically enabled when you select CONFIG_CMD_DATE .
  551. - Partition Support:
  552. CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
  553. and/or CONFIG_ISO_PARTITION
  554. If IDE or SCSI support is enabled (CONFIG_CMD_IDE or
  555. CONFIG_CMD_SCSI) you must configure support for at least
  556. one partition type as well.
  557. - IDE Reset method:
  558. CONFIG_IDE_RESET_ROUTINE - this is defined in several
  559. board configurations files but used nowhere!
  560. CONFIG_IDE_RESET - is this is defined, IDE Reset will
  561. be performed by calling the function
  562. ide_set_reset(int reset)
  563. which has to be defined in a board specific file
  564. - ATAPI Support:
  565. CONFIG_ATAPI
  566. Set this to enable ATAPI support.
  567. - LBA48 Support
  568. CONFIG_LBA48
  569. Set this to enable support for disks larger than 137GB
  570. Also look at CFG_64BIT_LBA ,CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL
  571. Whithout these , LBA48 support uses 32bit variables and will 'only'
  572. support disks up to 2.1TB.
  573. CFG_64BIT_LBA:
  574. When enabled, makes the IDE subsystem use 64bit sector addresses.
  575. Default is 32bit.
  576. - SCSI Support:
  577. At the moment only there is only support for the
  578. SYM53C8XX SCSI controller; define
  579. CONFIG_SCSI_SYM53C8XX to enable it.
  580. CFG_SCSI_MAX_LUN [8], CFG_SCSI_MAX_SCSI_ID [7] and
  581. CFG_SCSI_MAX_DEVICE [CFG_SCSI_MAX_SCSI_ID *
  582. CFG_SCSI_MAX_LUN] can be adjusted to define the
  583. maximum numbers of LUNs, SCSI ID's and target
  584. devices.
  585. CFG_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
  586. - NETWORK Support (PCI):
  587. CONFIG_E1000
  588. Support for Intel 8254x gigabit chips.
  589. CONFIG_EEPRO100
  590. Support for Intel 82557/82559/82559ER chips.
  591. Optional CONFIG_EEPRO100_SROM_WRITE enables eeprom
  592. write routine for first time initialisation.
  593. CONFIG_TULIP
  594. Support for Digital 2114x chips.
  595. Optional CONFIG_TULIP_SELECT_MEDIA for board specific
  596. modem chip initialisation (KS8761/QS6611).
  597. CONFIG_NATSEMI
  598. Support for National dp83815 chips.
  599. CONFIG_NS8382X
  600. Support for National dp8382[01] gigabit chips.
  601. - NETWORK Support (other):
  602. CONFIG_DRIVER_LAN91C96
  603. Support for SMSC's LAN91C96 chips.
  604. CONFIG_LAN91C96_BASE
  605. Define this to hold the physical address
  606. of the LAN91C96's I/O space
  607. CONFIG_LAN91C96_USE_32_BIT
  608. Define this to enable 32 bit addressing
  609. CONFIG_DRIVER_SMC91111
  610. Support for SMSC's LAN91C111 chip
  611. CONFIG_SMC91111_BASE
  612. Define this to hold the physical address
  613. of the device (I/O space)
  614. CONFIG_SMC_USE_32_BIT
  615. Define this if data bus is 32 bits
  616. CONFIG_SMC_USE_IOFUNCS
  617. Define this to use i/o functions instead of macros
  618. (some hardware wont work with macros)
  619. - USB Support:
  620. At the moment only the UHCI host controller is
  621. supported (PIP405, MIP405, MPC5200); define
  622. CONFIG_USB_UHCI to enable it.
  623. define CONFIG_USB_KEYBOARD to enable the USB Keyboard
  624. and define CONFIG_USB_STORAGE to enable the USB
  625. storage devices.
  626. Note:
  627. Supported are USB Keyboards and USB Floppy drives
  628. (TEAC FD-05PUB).
  629. MPC5200 USB requires additional defines:
  630. CONFIG_USB_CLOCK
  631. for 528 MHz Clock: 0x0001bbbb
  632. CONFIG_USB_CONFIG
  633. for differential drivers: 0x00001000
  634. for single ended drivers: 0x00005000
  635. CFG_USB_EVENT_POLL
  636. May be defined to allow interrupt polling
  637. instead of using asynchronous interrupts
  638. - USB Device:
  639. Define the below if you wish to use the USB console.
  640. Once firmware is rebuilt from a serial console issue the
  641. command "setenv stdin usbtty; setenv stdout usbtty" and
  642. attach your usb cable. The Unix command "dmesg" should print
  643. it has found a new device. The environment variable usbtty
  644. can be set to gserial or cdc_acm to enable your device to
  645. appear to a USB host as a Linux gserial device or a
  646. Common Device Class Abstract Control Model serial device.
  647. If you select usbtty = gserial you should be able to enumerate
  648. a Linux host by
  649. # modprobe usbserial vendor=0xVendorID product=0xProductID
  650. else if using cdc_acm, simply setting the environment
  651. variable usbtty to be cdc_acm should suffice. The following
  652. might be defined in YourBoardName.h
  653. CONFIG_USB_DEVICE
  654. Define this to build a UDC device
  655. CONFIG_USB_TTY
  656. Define this to have a tty type of device available to
  657. talk to the UDC device
  658. CFG_CONSOLE_IS_IN_ENV
  659. Define this if you want stdin, stdout &/or stderr to
  660. be set to usbtty.
  661. mpc8xx:
  662. CFG_USB_EXTC_CLK 0xBLAH
  663. Derive USB clock from external clock "blah"
  664. - CFG_USB_EXTC_CLK 0x02
  665. CFG_USB_BRG_CLK 0xBLAH
  666. Derive USB clock from brgclk
  667. - CFG_USB_BRG_CLK 0x04
  668. If you have a USB-IF assigned VendorID then you may wish to
  669. define your own vendor specific values either in BoardName.h
  670. or directly in usbd_vendor_info.h. If you don't define
  671. CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
  672. CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
  673. should pretend to be a Linux device to it's target host.
  674. CONFIG_USBD_MANUFACTURER
  675. Define this string as the name of your company for
  676. - CONFIG_USBD_MANUFACTURER "my company"
  677. CONFIG_USBD_PRODUCT_NAME
  678. Define this string as the name of your product
  679. - CONFIG_USBD_PRODUCT_NAME "acme usb device"
  680. CONFIG_USBD_VENDORID
  681. Define this as your assigned Vendor ID from the USB
  682. Implementors Forum. This *must* be a genuine Vendor ID
  683. to avoid polluting the USB namespace.
  684. - CONFIG_USBD_VENDORID 0xFFFF
  685. CONFIG_USBD_PRODUCTID
  686. Define this as the unique Product ID
  687. for your device
  688. - CONFIG_USBD_PRODUCTID 0xFFFF
  689. - MMC Support:
  690. The MMC controller on the Intel PXA is supported. To
  691. enable this define CONFIG_MMC. The MMC can be
  692. accessed from the boot prompt by mapping the device
  693. to physical memory similar to flash. Command line is
  694. enabled with CONFIG_CMD_MMC. The MMC driver also works with
  695. the FAT fs. This is enabled with CONFIG_CMD_FAT.
  696. - Journaling Flash filesystem support:
  697. CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
  698. CONFIG_JFFS2_NAND_DEV
  699. Define these for a default partition on a NAND device
  700. CFG_JFFS2_FIRST_SECTOR,
  701. CFG_JFFS2_FIRST_BANK, CFG_JFFS2_NUM_BANKS
  702. Define these for a default partition on a NOR device
  703. CFG_JFFS_CUSTOM_PART
  704. Define this to create an own partition. You have to provide a
  705. function struct part_info* jffs2_part_info(int part_num)
  706. If you define only one JFFS2 partition you may also want to
  707. #define CFG_JFFS_SINGLE_PART 1
  708. to disable the command chpart. This is the default when you
  709. have not defined a custom partition
  710. - Keyboard Support:
  711. CONFIG_ISA_KEYBOARD
  712. Define this to enable standard (PC-Style) keyboard
  713. support
  714. CONFIG_I8042_KBD
  715. Standard PC keyboard driver with US (is default) and
  716. GERMAN key layout (switch via environment 'keymap=de') support.
  717. Export function i8042_kbd_init, i8042_tstc and i8042_getc
  718. for cfb_console. Supports cursor blinking.
  719. - Video support:
  720. CONFIG_VIDEO
  721. Define this to enable video support (for output to
  722. video).
  723. CONFIG_VIDEO_CT69000
  724. Enable Chips & Technologies 69000 Video chip
  725. CONFIG_VIDEO_SMI_LYNXEM
  726. Enable Silicon Motion SMI 712/710/810 Video chip. The
  727. video output is selected via environment 'videoout'
  728. (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
  729. assumed.
  730. For the CT69000 and SMI_LYNXEM drivers, videomode is
  731. selected via environment 'videomode'. Two diferent ways
  732. are possible:
  733. - "videomode=num" 'num' is a standard LiLo mode numbers.
  734. Following standard modes are supported (* is default):
  735. Colors 640x480 800x600 1024x768 1152x864 1280x1024
  736. -------------+---------------------------------------------
  737. 8 bits | 0x301* 0x303 0x305 0x161 0x307
  738. 15 bits | 0x310 0x313 0x316 0x162 0x319
  739. 16 bits | 0x311 0x314 0x317 0x163 0x31A
  740. 24 bits | 0x312 0x315 0x318 ? 0x31B
  741. -------------+---------------------------------------------
  742. (i.e. setenv videomode 317; saveenv; reset;)
  743. - "videomode=bootargs" all the video parameters are parsed
  744. from the bootargs. (See drivers/video/videomodes.c)
  745. CONFIG_VIDEO_SED13806
  746. Enable Epson SED13806 driver. This driver supports 8bpp
  747. and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
  748. or CONFIG_VIDEO_SED13806_16BPP
  749. - Keyboard Support:
  750. CONFIG_KEYBOARD
  751. Define this to enable a custom keyboard support.
  752. This simply calls drv_keyboard_init() which must be
  753. defined in your board-specific files.
  754. The only board using this so far is RBC823.
  755. - LCD Support: CONFIG_LCD
  756. Define this to enable LCD support (for output to LCD
  757. display); also select one of the supported displays
  758. by defining one of these:
  759. CONFIG_NEC_NL6448AC33:
  760. NEC NL6448AC33-18. Active, color, single scan.
  761. CONFIG_NEC_NL6448BC20
  762. NEC NL6448BC20-08. 6.5", 640x480.
  763. Active, color, single scan.
  764. CONFIG_NEC_NL6448BC33_54
  765. NEC NL6448BC33-54. 10.4", 640x480.
  766. Active, color, single scan.
  767. CONFIG_SHARP_16x9
  768. Sharp 320x240. Active, color, single scan.
  769. It isn't 16x9, and I am not sure what it is.
  770. CONFIG_SHARP_LQ64D341
  771. Sharp LQ64D341 display, 640x480.
  772. Active, color, single scan.
  773. CONFIG_HLD1045
  774. HLD1045 display, 640x480.
  775. Active, color, single scan.
  776. CONFIG_OPTREX_BW
  777. Optrex CBL50840-2 NF-FW 99 22 M5
  778. or
  779. Hitachi LMG6912RPFC-00T
  780. or
  781. Hitachi SP14Q002
  782. 320x240. Black & white.
  783. Normally display is black on white background; define
  784. CFG_WHITE_ON_BLACK to get it inverted.
  785. - Splash Screen Support: CONFIG_SPLASH_SCREEN
  786. If this option is set, the environment is checked for
  787. a variable "splashimage". If found, the usual display
  788. of logo, copyright and system information on the LCD
  789. is suppressed and the BMP image at the address
  790. specified in "splashimage" is loaded instead. The
  791. console is redirected to the "nulldev", too. This
  792. allows for a "silent" boot where a splash screen is
  793. loaded very quickly after power-on.
  794. - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
  795. If this option is set, additionally to standard BMP
  796. images, gzipped BMP images can be displayed via the
  797. splashscreen support or the bmp command.
  798. - Compression support:
  799. CONFIG_BZIP2
  800. If this option is set, support for bzip2 compressed
  801. images is included. If not, only uncompressed and gzip
  802. compressed images are supported.
  803. NOTE: the bzip2 algorithm requires a lot of RAM, so
  804. the malloc area (as defined by CFG_MALLOC_LEN) should
  805. be at least 4MB.
  806. - MII/PHY support:
  807. CONFIG_PHY_ADDR
  808. The address of PHY on MII bus.
  809. CONFIG_PHY_CLOCK_FREQ (ppc4xx)
  810. The clock frequency of the MII bus
  811. CONFIG_PHY_GIGE
  812. If this option is set, support for speed/duplex
  813. detection of Gigabit PHY is included.
  814. CONFIG_PHY_RESET_DELAY
  815. Some PHY like Intel LXT971A need extra delay after
  816. reset before any MII register access is possible.
  817. For such PHY, set this option to the usec delay
  818. required. (minimum 300usec for LXT971A)
  819. CONFIG_PHY_CMD_DELAY (ppc4xx)
  820. Some PHY like Intel LXT971A need extra delay after
  821. command issued before MII status register can be read
  822. - Ethernet address:
  823. CONFIG_ETHADDR
  824. CONFIG_ETH2ADDR
  825. CONFIG_ETH3ADDR
  826. Define a default value for ethernet address to use
  827. for the respective ethernet interface, in case this
  828. is not determined automatically.
  829. - IP address:
  830. CONFIG_IPADDR
  831. Define a default value for the IP address to use for
  832. the default ethernet interface, in case this is not
  833. determined through e.g. bootp.
  834. - Server IP address:
  835. CONFIG_SERVERIP
  836. Defines a default value for theIP address of a TFTP
  837. server to contact when using the "tftboot" command.
  838. - Multicast TFTP Mode:
  839. CONFIG_MCAST_TFTP
  840. Defines whether you want to support multicast TFTP as per
  841. rfc-2090; for example to work with atftp. Lets lots of targets
  842. tftp down the same boot image concurrently. Note: the ethernet
  843. driver in use must provide a function: mcast() to join/leave a
  844. multicast group.
  845. CONFIG_BOOTP_RANDOM_DELAY
  846. - BOOTP Recovery Mode:
  847. CONFIG_BOOTP_RANDOM_DELAY
  848. If you have many targets in a network that try to
  849. boot using BOOTP, you may want to avoid that all
  850. systems send out BOOTP requests at precisely the same
  851. moment (which would happen for instance at recovery
  852. from a power failure, when all systems will try to
  853. boot, thus flooding the BOOTP server. Defining
  854. CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
  855. inserted before sending out BOOTP requests. The
  856. following delays are inserted then:
  857. 1st BOOTP request: delay 0 ... 1 sec
  858. 2nd BOOTP request: delay 0 ... 2 sec
  859. 3rd BOOTP request: delay 0 ... 4 sec
  860. 4th and following
  861. BOOTP requests: delay 0 ... 8 sec
  862. - DHCP Advanced Options:
  863. You can fine tune the DHCP functionality by defining
  864. CONFIG_BOOTP_* symbols:
  865. CONFIG_BOOTP_SUBNETMASK
  866. CONFIG_BOOTP_GATEWAY
  867. CONFIG_BOOTP_HOSTNAME
  868. CONFIG_BOOTP_NISDOMAIN
  869. CONFIG_BOOTP_BOOTPATH
  870. CONFIG_BOOTP_BOOTFILESIZE
  871. CONFIG_BOOTP_DNS
  872. CONFIG_BOOTP_DNS2
  873. CONFIG_BOOTP_SEND_HOSTNAME
  874. CONFIG_BOOTP_NTPSERVER
  875. CONFIG_BOOTP_TIMEOFFSET
  876. CONFIG_BOOTP_VENDOREX
  877. CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
  878. environment variable, not the BOOTP server.
  879. CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
  880. serverip from a DHCP server, it is possible that more
  881. than one DNS serverip is offered to the client.
  882. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
  883. serverip will be stored in the additional environment
  884. variable "dnsip2". The first DNS serverip is always
  885. stored in the variable "dnsip", when CONFIG_BOOTP_DNS
  886. is defined.
  887. CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
  888. to do a dynamic update of a DNS server. To do this, they
  889. need the hostname of the DHCP requester.
  890. If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
  891. of the "hostname" environment variable is passed as
  892. option 12 to the DHCP server.
  893. - CDP Options:
  894. CONFIG_CDP_DEVICE_ID
  895. The device id used in CDP trigger frames.
  896. CONFIG_CDP_DEVICE_ID_PREFIX
  897. A two character string which is prefixed to the MAC address
  898. of the device.
  899. CONFIG_CDP_PORT_ID
  900. A printf format string which contains the ascii name of
  901. the port. Normally is set to "eth%d" which sets
  902. eth0 for the first ethernet, eth1 for the second etc.
  903. CONFIG_CDP_CAPABILITIES
  904. A 32bit integer which indicates the device capabilities;
  905. 0x00000010 for a normal host which does not forwards.
  906. CONFIG_CDP_VERSION
  907. An ascii string containing the version of the software.
  908. CONFIG_CDP_PLATFORM
  909. An ascii string containing the name of the platform.
  910. CONFIG_CDP_TRIGGER
  911. A 32bit integer sent on the trigger.
  912. CONFIG_CDP_POWER_CONSUMPTION
  913. A 16bit integer containing the power consumption of the
  914. device in .1 of milliwatts.
  915. CONFIG_CDP_APPLIANCE_VLAN_TYPE
  916. A byte containing the id of the VLAN.
  917. - Status LED: CONFIG_STATUS_LED
  918. Several configurations allow to display the current
  919. status using a LED. For instance, the LED will blink
  920. fast while running U-Boot code, stop blinking as
  921. soon as a reply to a BOOTP request was received, and
  922. start blinking slow once the Linux kernel is running
  923. (supported by a status LED driver in the Linux
  924. kernel). Defining CONFIG_STATUS_LED enables this
  925. feature in U-Boot.
  926. - CAN Support: CONFIG_CAN_DRIVER
  927. Defining CONFIG_CAN_DRIVER enables CAN driver support
  928. on those systems that support this (optional)
  929. feature, like the TQM8xxL modules.
  930. - I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C
  931. These enable I2C serial bus commands. Defining either of
  932. (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
  933. include the appropriate I2C driver for the selected cpu.
  934. This will allow you to use i2c commands at the u-boot
  935. command line (as long as you set CONFIG_CMD_I2C in
  936. CONFIG_COMMANDS) and communicate with i2c based realtime
  937. clock chips. See common/cmd_i2c.c for a description of the
  938. command line interface.
  939. CONFIG_I2C_CMD_TREE is a recommended option that places
  940. all I2C commands under a single 'i2c' root command. The
  941. older 'imm', 'imd', 'iprobe' etc. commands are considered
  942. deprecated and may disappear in the future.
  943. CONFIG_HARD_I2C selects a hardware I2C controller.
  944. CONFIG_SOFT_I2C configures u-boot to use a software (aka
  945. bit-banging) driver instead of CPM or similar hardware
  946. support for I2C.
  947. There are several other quantities that must also be
  948. defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
  949. In both cases you will need to define CFG_I2C_SPEED
  950. to be the frequency (in Hz) at which you wish your i2c bus
  951. to run and CFG_I2C_SLAVE to be the address of this node (ie
  952. the cpu's i2c node address).
  953. Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)
  954. sets the cpu up as a master node and so its address should
  955. therefore be cleared to 0 (See, eg, MPC823e User's Manual
  956. p.16-473). So, set CFG_I2C_SLAVE to 0.
  957. That's all that's required for CONFIG_HARD_I2C.
  958. If you use the software i2c interface (CONFIG_SOFT_I2C)
  959. then the following macros need to be defined (examples are
  960. from include/configs/lwmon.h):
  961. I2C_INIT
  962. (Optional). Any commands necessary to enable the I2C
  963. controller or configure ports.
  964. eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
  965. I2C_PORT
  966. (Only for MPC8260 CPU). The I/O port to use (the code
  967. assumes both bits are on the same port). Valid values
  968. are 0..3 for ports A..D.
  969. I2C_ACTIVE
  970. The code necessary to make the I2C data line active
  971. (driven). If the data line is open collector, this
  972. define can be null.
  973. eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
  974. I2C_TRISTATE
  975. The code necessary to make the I2C data line tri-stated
  976. (inactive). If the data line is open collector, this
  977. define can be null.
  978. eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
  979. I2C_READ
  980. Code that returns TRUE if the I2C data line is high,
  981. FALSE if it is low.
  982. eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
  983. I2C_SDA(bit)
  984. If <bit> is TRUE, sets the I2C data line high. If it
  985. is FALSE, it clears it (low).
  986. eg: #define I2C_SDA(bit) \
  987. if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
  988. else immr->im_cpm.cp_pbdat &= ~PB_SDA
  989. I2C_SCL(bit)
  990. If <bit> is TRUE, sets the I2C clock line high. If it
  991. is FALSE, it clears it (low).
  992. eg: #define I2C_SCL(bit) \
  993. if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
  994. else immr->im_cpm.cp_pbdat &= ~PB_SCL
  995. I2C_DELAY
  996. This delay is invoked four times per clock cycle so this
  997. controls the rate of data transfer. The data rate thus
  998. is 1 / (I2C_DELAY * 4). Often defined to be something
  999. like:
  1000. #define I2C_DELAY udelay(2)
  1001. CFG_I2C_INIT_BOARD
  1002. When a board is reset during an i2c bus transfer
  1003. chips might think that the current transfer is still
  1004. in progress. On some boards it is possible to access
  1005. the i2c SCLK line directly, either by using the
  1006. processor pin as a GPIO or by having a second pin
  1007. connected to the bus. If this option is defined a
  1008. custom i2c_init_board() routine in boards/xxx/board.c
  1009. is run early in the boot sequence.
  1010. CONFIG_I2CFAST (PPC405GP|PPC405EP only)
  1011. This option enables configuration of bi_iic_fast[] flags
  1012. in u-boot bd_info structure based on u-boot environment
  1013. variable "i2cfast". (see also i2cfast)
  1014. CONFIG_I2C_MULTI_BUS
  1015. This option allows the use of multiple I2C buses, each of which
  1016. must have a controller. At any point in time, only one bus is
  1017. active. To switch to a different bus, use the 'i2c dev' command.
  1018. Note that bus numbering is zero-based.
  1019. CFG_I2C_NOPROBES
  1020. This option specifies a list of I2C devices that will be skipped
  1021. when the 'i2c probe' command is issued (or 'iprobe' using the legacy
  1022. command). If CONFIG_I2C_MULTI_BUS is set, specify a list of bus-device
  1023. pairs. Otherwise, specify a 1D array of device addresses
  1024. e.g.
  1025. #undef CONFIG_I2C_MULTI_BUS
  1026. #define CFG_I2C_NOPROBES {0x50,0x68}
  1027. will skip addresses 0x50 and 0x68 on a board with one I2C bus
  1028. #define CONFIG_I2C_MULTI_BUS
  1029. #define CFG_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
  1030. will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
  1031. CFG_SPD_BUS_NUM
  1032. If defined, then this indicates the I2C bus number for DDR SPD.
  1033. If not defined, then U-Boot assumes that SPD is on I2C bus 0.
  1034. CFG_RTC_BUS_NUM
  1035. If defined, then this indicates the I2C bus number for the RTC.
  1036. If not defined, then U-Boot assumes that RTC is on I2C bus 0.
  1037. CFG_DTT_BUS_NUM
  1038. If defined, then this indicates the I2C bus number for the DTT.
  1039. If not defined, then U-Boot assumes that DTT is on I2C bus 0.
  1040. CONFIG_FSL_I2C
  1041. Define this option if you want to use Freescale's I2C driver in
  1042. drivers/i2c/fsl_i2c.c.
  1043. - SPI Support: CONFIG_SPI
  1044. Enables SPI driver (so far only tested with
  1045. SPI EEPROM, also an instance works with Crystal A/D and
  1046. D/As on the SACSng board)
  1047. CONFIG_SPI_X
  1048. Enables extended (16-bit) SPI EEPROM addressing.
  1049. (symmetrical to CONFIG_I2C_X)
  1050. CONFIG_SOFT_SPI
  1051. Enables a software (bit-bang) SPI driver rather than
  1052. using hardware support. This is a general purpose
  1053. driver that only requires three general I/O port pins
  1054. (two outputs, one input) to function. If this is
  1055. defined, the board configuration must define several
  1056. SPI configuration items (port pins to use, etc). For
  1057. an example, see include/configs/sacsng.h.
  1058. CONFIG_HARD_SPI
  1059. Enables a hardware SPI driver for general-purpose reads
  1060. and writes. As with CONFIG_SOFT_SPI, the board configuration
  1061. must define a list of chip-select function pointers.
  1062. Currently supported on some MPC8xxx processors. For an
  1063. example, see include/configs/mpc8349emds.h.
  1064. - FPGA Support: CONFIG_FPGA
  1065. Enables FPGA subsystem.
  1066. CONFIG_FPGA_<vendor>
  1067. Enables support for specific chip vendors.
  1068. (ALTERA, XILINX)
  1069. CONFIG_FPGA_<family>
  1070. Enables support for FPGA family.
  1071. (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
  1072. CONFIG_FPGA_COUNT
  1073. Specify the number of FPGA devices to support.
  1074. CFG_FPGA_PROG_FEEDBACK
  1075. Enable printing of hash marks during FPGA configuration.
  1076. CFG_FPGA_CHECK_BUSY
  1077. Enable checks on FPGA configuration interface busy
  1078. status by the configuration function. This option
  1079. will require a board or device specific function to
  1080. be written.
  1081. CONFIG_FPGA_DELAY
  1082. If defined, a function that provides delays in the FPGA
  1083. configuration driver.
  1084. CFG_FPGA_CHECK_CTRLC
  1085. Allow Control-C to interrupt FPGA configuration
  1086. CFG_FPGA_CHECK_ERROR
  1087. Check for configuration errors during FPGA bitfile
  1088. loading. For example, abort during Virtex II
  1089. configuration if the INIT_B line goes low (which
  1090. indicated a CRC error).
  1091. CFG_FPGA_WAIT_INIT
  1092. Maximum time to wait for the INIT_B line to deassert
  1093. after PROB_B has been deasserted during a Virtex II
  1094. FPGA configuration sequence. The default time is 500
  1095. mS.
  1096. CFG_FPGA_WAIT_BUSY
  1097. Maximum time to wait for BUSY to deassert during
  1098. Virtex II FPGA configuration. The default is 5 mS.
  1099. CFG_FPGA_WAIT_CONFIG
  1100. Time to wait after FPGA configuration. The default is
  1101. 200 mS.
  1102. - Configuration Management:
  1103. CONFIG_IDENT_STRING
  1104. If defined, this string will be added to the U-Boot
  1105. version information (U_BOOT_VERSION)
  1106. - Vendor Parameter Protection:
  1107. U-Boot considers the values of the environment
  1108. variables "serial#" (Board Serial Number) and
  1109. "ethaddr" (Ethernet Address) to be parameters that
  1110. are set once by the board vendor / manufacturer, and
  1111. protects these variables from casual modification by
  1112. the user. Once set, these variables are read-only,
  1113. and write or delete attempts are rejected. You can
  1114. change this behviour:
  1115. If CONFIG_ENV_OVERWRITE is #defined in your config
  1116. file, the write protection for vendor parameters is
  1117. completely disabled. Anybody can change or delete
  1118. these parameters.
  1119. Alternatively, if you #define _both_ CONFIG_ETHADDR
  1120. _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
  1121. ethernet address is installed in the environment,
  1122. which can be changed exactly ONCE by the user. [The
  1123. serial# is unaffected by this, i. e. it remains
  1124. read-only.]
  1125. - Protected RAM:
  1126. CONFIG_PRAM
  1127. Define this variable to enable the reservation of
  1128. "protected RAM", i. e. RAM which is not overwritten
  1129. by U-Boot. Define CONFIG_PRAM to hold the number of
  1130. kB you want to reserve for pRAM. You can overwrite
  1131. this default value by defining an environment
  1132. variable "pram" to the number of kB you want to
  1133. reserve. Note that the board info structure will
  1134. still show the full amount of RAM. If pRAM is
  1135. reserved, a new environment variable "mem" will
  1136. automatically be defined to hold the amount of
  1137. remaining RAM in a form that can be passed as boot
  1138. argument to Linux, for instance like that:
  1139. setenv bootargs ... mem=\${mem}
  1140. saveenv
  1141. This way you can tell Linux not to use this memory,
  1142. either, which results in a memory region that will
  1143. not be affected by reboots.
  1144. *WARNING* If your board configuration uses automatic
  1145. detection of the RAM size, you must make sure that
  1146. this memory test is non-destructive. So far, the
  1147. following board configurations are known to be
  1148. "pRAM-clean":
  1149. ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
  1150. HERMES, IP860, RPXlite, LWMON, LANTEC,
  1151. PCU_E, FLAGADM, TQM8260
  1152. - Error Recovery:
  1153. CONFIG_PANIC_HANG
  1154. Define this variable to stop the system in case of a
  1155. fatal error, so that you have to reset it manually.
  1156. This is probably NOT a good idea for an embedded
  1157. system where you want to system to reboot
  1158. automatically as fast as possible, but it may be
  1159. useful during development since you can try to debug
  1160. the conditions that lead to the situation.
  1161. CONFIG_NET_RETRY_COUNT
  1162. This variable defines the number of retries for
  1163. network operations like ARP, RARP, TFTP, or BOOTP
  1164. before giving up the operation. If not defined, a
  1165. default value of 5 is used.
  1166. - Command Interpreter:
  1167. CONFIG_AUTO_COMPLETE
  1168. Enable auto completion of commands using TAB.
  1169. Note that this feature has NOT been implemented yet
  1170. for the "hush" shell.
  1171. CFG_HUSH_PARSER
  1172. Define this variable to enable the "hush" shell (from
  1173. Busybox) as command line interpreter, thus enabling
  1174. powerful command line syntax like
  1175. if...then...else...fi conditionals or `&&' and '||'
  1176. constructs ("shell scripts").
  1177. If undefined, you get the old, much simpler behaviour
  1178. with a somewhat smaller memory footprint.
  1179. CFG_PROMPT_HUSH_PS2
  1180. This defines the secondary prompt string, which is
  1181. printed when the command interpreter needs more input
  1182. to complete a command. Usually "> ".
  1183. Note:
  1184. In the current implementation, the local variables
  1185. space and global environment variables space are
  1186. separated. Local variables are those you define by
  1187. simply typing `name=value'. To access a local
  1188. variable later on, you have write `$name' or
  1189. `${name}'; to execute the contents of a variable
  1190. directly type `$name' at the command prompt.
  1191. Global environment variables are those you use
  1192. setenv/printenv to work with. To run a command stored
  1193. in such a variable, you need to use the run command,
  1194. and you must not use the '$' sign to access them.
  1195. To store commands and special characters in a
  1196. variable, please use double quotation marks
  1197. surrounding the whole text of the variable, instead
  1198. of the backslashes before semicolons and special
  1199. symbols.
  1200. - Commandline Editing and History:
  1201. CONFIG_CMDLINE_EDITING
  1202. Enable editiong and History functions for interactive
  1203. commandline input operations
  1204. - Default Environment:
  1205. CONFIG_EXTRA_ENV_SETTINGS
  1206. Define this to contain any number of null terminated
  1207. strings (variable = value pairs) that will be part of
  1208. the default environment compiled into the boot image.
  1209. For example, place something like this in your
  1210. board's config file:
  1211. #define CONFIG_EXTRA_ENV_SETTINGS \
  1212. "myvar1=value1\0" \
  1213. "myvar2=value2\0"
  1214. Warning: This method is based on knowledge about the
  1215. internal format how the environment is stored by the
  1216. U-Boot code. This is NOT an official, exported
  1217. interface! Although it is unlikely that this format
  1218. will change soon, there is no guarantee either.
  1219. You better know what you are doing here.
  1220. Note: overly (ab)use of the default environment is
  1221. discouraged. Make sure to check other ways to preset
  1222. the environment like the autoscript function or the
  1223. boot command first.
  1224. - DataFlash Support:
  1225. CONFIG_HAS_DATAFLASH
  1226. Defining this option enables DataFlash features and
  1227. allows to read/write in Dataflash via the standard
  1228. commands cp, md...
  1229. - SystemACE Support:
  1230. CONFIG_SYSTEMACE
  1231. Adding this option adds support for Xilinx SystemACE
  1232. chips attached via some sort of local bus. The address
  1233. of the chip must alsh be defined in the
  1234. CFG_SYSTEMACE_BASE macro. For example:
  1235. #define CONFIG_SYSTEMACE
  1236. #define CFG_SYSTEMACE_BASE 0xf0000000
  1237. When SystemACE support is added, the "ace" device type
  1238. becomes available to the fat commands, i.e. fatls.
  1239. - TFTP Fixed UDP Port:
  1240. CONFIG_TFTP_PORT
  1241. If this is defined, the environment variable tftpsrcp
  1242. is used to supply the TFTP UDP source port value.
  1243. If tftpsrcp isn't defined, the normal pseudo-random port
  1244. number generator is used.
  1245. Also, the environment variable tftpdstp is used to supply
  1246. the TFTP UDP destination port value. If tftpdstp isn't
  1247. defined, the normal port 69 is used.
  1248. The purpose for tftpsrcp is to allow a TFTP server to
  1249. blindly start the TFTP transfer using the pre-configured
  1250. target IP address and UDP port. This has the effect of
  1251. "punching through" the (Windows XP) firewall, allowing
  1252. the remainder of the TFTP transfer to proceed normally.
  1253. A better solution is to properly configure the firewall,
  1254. but sometimes that is not allowed.
  1255. - Show boot progress:
  1256. CONFIG_SHOW_BOOT_PROGRESS
  1257. Defining this option allows to add some board-
  1258. specific code (calling a user-provided function
  1259. "show_boot_progress(int)") that enables you to show
  1260. the system's boot progress on some display (for
  1261. example, some LED's) on your board. At the moment,
  1262. the following checkpoints are implemented:
  1263. Arg Where When
  1264. 1 common/cmd_bootm.c before attempting to boot an image
  1265. -1 common/cmd_bootm.c Image header has bad magic number
  1266. 2 common/cmd_bootm.c Image header has correct magic number
  1267. -2 common/cmd_bootm.c Image header has bad checksum
  1268. 3 common/cmd_bootm.c Image header has correct checksum
  1269. -3 common/cmd_bootm.c Image data has bad checksum
  1270. 4 common/cmd_bootm.c Image data has correct checksum
  1271. -4 common/cmd_bootm.c Image is for unsupported architecture
  1272. 5 common/cmd_bootm.c Architecture check OK
  1273. -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
  1274. 6 common/cmd_bootm.c Image Type check OK
  1275. -6 common/cmd_bootm.c gunzip uncompression error
  1276. -7 common/cmd_bootm.c Unimplemented compression type
  1277. 7 common/cmd_bootm.c Uncompression OK
  1278. -8 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
  1279. 8 common/cmd_bootm.c Image Type check OK
  1280. -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
  1281. 9 common/cmd_bootm.c Start initial ramdisk verification
  1282. -10 common/cmd_bootm.c Ramdisk header has bad magic number
  1283. -11 common/cmd_bootm.c Ramdisk header has bad checksum
  1284. 10 common/cmd_bootm.c Ramdisk header is OK
  1285. -12 common/cmd_bootm.c Ramdisk data has bad checksum
  1286. 11 common/cmd_bootm.c Ramdisk data has correct checksum
  1287. 12 common/cmd_bootm.c Ramdisk verification complete, start loading
  1288. -13 common/cmd_bootm.c Wrong Image Type (not PPC Linux Ramdisk)
  1289. 13 common/cmd_bootm.c Start multifile image verification
  1290. 14 common/cmd_bootm.c No initial ramdisk, no multifile, continue.
  1291. 15 common/cmd_bootm.c All preparation done, transferring control to OS
  1292. -30 lib_ppc/board.c Fatal error, hang the system
  1293. -31 post/post.c POST test failed, detected by post_output_backlog()
  1294. -32 post/post.c POST test failed, detected by post_run_single()
  1295. 34 common/cmd_doc.c before loading a Image from a DOC device
  1296. -35 common/cmd_doc.c Bad usage of "doc" command
  1297. 35 common/cmd_doc.c correct usage of "doc" command
  1298. -36 common/cmd_doc.c No boot device
  1299. 36 common/cmd_doc.c correct boot device
  1300. -37 common/cmd_doc.c Unknown Chip ID on boot device
  1301. 37 common/cmd_doc.c correct chip ID found, device available
  1302. -38 common/cmd_doc.c Read Error on boot device
  1303. 38 common/cmd_doc.c reading Image header from DOC device OK
  1304. -39 common/cmd_doc.c Image header has bad magic number
  1305. 39 common/cmd_doc.c Image header has correct magic number
  1306. -40 common/cmd_doc.c Error reading Image from DOC device
  1307. 40 common/cmd_doc.c Image header has correct magic number
  1308. 41 common/cmd_ide.c before loading a Image from a IDE device
  1309. -42 common/cmd_ide.c Bad usage of "ide" command
  1310. 42 common/cmd_ide.c correct usage of "ide" command
  1311. -43 common/cmd_ide.c No boot device
  1312. 43 common/cmd_ide.c boot device found
  1313. -44 common/cmd_ide.c Device not available
  1314. 44 common/cmd_ide.c Device available
  1315. -45 common/cmd_ide.c wrong partition selected
  1316. 45 common/cmd_ide.c partition selected
  1317. -46 common/cmd_ide.c Unknown partition table
  1318. 46 common/cmd_ide.c valid partition table found
  1319. -47 common/cmd_ide.c Invalid partition type
  1320. 47 common/cmd_ide.c correct partition type
  1321. -48 common/cmd_ide.c Error reading Image Header on boot device
  1322. 48 common/cmd_ide.c reading Image Header from IDE device OK
  1323. -49 common/cmd_ide.c Image header has bad magic number
  1324. 49 common/cmd_ide.c Image header has correct magic number
  1325. -50 common/cmd_ide.c Image header has bad checksum
  1326. 50 common/cmd_ide.c Image header has correct checksum
  1327. -51 common/cmd_ide.c Error reading Image from IDE device
  1328. 51 common/cmd_ide.c reading Image from IDE device OK
  1329. 52 common/cmd_nand.c before loading a Image from a NAND device
  1330. -53 common/cmd_nand.c Bad usage of "nand" command
  1331. 53 common/cmd_nand.c correct usage of "nand" command
  1332. -54 common/cmd_nand.c No boot device
  1333. 54 common/cmd_nand.c boot device found
  1334. -55 common/cmd_nand.c Unknown Chip ID on boot device
  1335. 55 common/cmd_nand.c correct chip ID found, device available
  1336. -56 common/cmd_nand.c Error reading Image Header on boot device
  1337. 56 common/cmd_nand.c reading Image Header from NAND device OK
  1338. -57 common/cmd_nand.c Image header has bad magic number
  1339. 57 common/cmd_nand.c Image header has correct magic number
  1340. -58 common/cmd_nand.c Error reading Image from NAND device
  1341. 58 common/cmd_nand.c reading Image from NAND device OK
  1342. -60 common/env_common.c Environment has a bad CRC, using default
  1343. 64 net/eth.c starting with Ethernetconfiguration.
  1344. -64 net/eth.c no Ethernet found.
  1345. 65 net/eth.c Ethernet found.
  1346. -80 common/cmd_net.c usage wrong
  1347. 80 common/cmd_net.c before calling NetLoop()
  1348. -81 common/cmd_net.c some error in NetLoop() occured
  1349. 81 common/cmd_net.c NetLoop() back without error
  1350. -82 common/cmd_net.c size == 0 (File with size 0 loaded)
  1351. 82 common/cmd_net.c trying automatic boot
  1352. 83 common/cmd_net.c running autoscript
  1353. -83 common/cmd_net.c some error in automatic boot or autoscript
  1354. 84 common/cmd_net.c end without errors
  1355. Modem Support:
  1356. --------------
  1357. [so far only for SMDK2400 and TRAB boards]
  1358. - Modem support endable:
  1359. CONFIG_MODEM_SUPPORT
  1360. - RTS/CTS Flow control enable:
  1361. CONFIG_HWFLOW
  1362. - Modem debug support:
  1363. CONFIG_MODEM_SUPPORT_DEBUG
  1364. Enables debugging stuff (char screen[1024], dbg())
  1365. for modem support. Useful only with BDI2000.
  1366. - Interrupt support (PPC):
  1367. There are common interrupt_init() and timer_interrupt()
  1368. for all PPC archs. interrupt_init() calls interrupt_init_cpu()
  1369. for cpu specific initialization. interrupt_init_cpu()
  1370. should set decrementer_count to appropriate value. If
  1371. cpu resets decrementer automatically after interrupt
  1372. (ppc4xx) it should set decrementer_count to zero.
  1373. timer_interrupt() calls timer_interrupt_cpu() for cpu
  1374. specific handling. If board has watchdog / status_led
  1375. / other_activity_monitor it works automatically from
  1376. general timer_interrupt().
  1377. - General:
  1378. In the target system modem support is enabled when a
  1379. specific key (key combination) is pressed during
  1380. power-on. Otherwise U-Boot will boot normally
  1381. (autoboot). The key_pressed() fuction is called from
  1382. board_init(). Currently key_pressed() is a dummy
  1383. function, returning 1 and thus enabling modem
  1384. initialization.
  1385. If there are no modem init strings in the
  1386. environment, U-Boot proceed to autoboot; the
  1387. previous output (banner, info printfs) will be
  1388. supressed, though.
  1389. See also: doc/README.Modem
  1390. Configuration Settings:
  1391. -----------------------
  1392. - CFG_LONGHELP: Defined when you want long help messages included;
  1393. undefine this when you're short of memory.
  1394. - CFG_PROMPT: This is what U-Boot prints on the console to
  1395. prompt for user input.
  1396. - CFG_CBSIZE: Buffer size for input from the Console
  1397. - CFG_PBSIZE: Buffer size for Console output
  1398. - CFG_MAXARGS: max. Number of arguments accepted for monitor commands
  1399. - CFG_BARGSIZE: Buffer size for Boot Arguments which are passed to
  1400. the application (usually a Linux kernel) when it is
  1401. booted
  1402. - CFG_BAUDRATE_TABLE:
  1403. List of legal baudrate settings for this board.
  1404. - CFG_CONSOLE_INFO_QUIET
  1405. Suppress display of console information at boot.
  1406. - CFG_CONSOLE_IS_IN_ENV
  1407. If the board specific function
  1408. extern int overwrite_console (void);
  1409. returns 1, the stdin, stderr and stdout are switched to the
  1410. serial port, else the settings in the environment are used.
  1411. - CFG_CONSOLE_OVERWRITE_ROUTINE
  1412. Enable the call to overwrite_console().
  1413. - CFG_CONSOLE_ENV_OVERWRITE
  1414. Enable overwrite of previous console environment settings.
  1415. - CFG_MEMTEST_START, CFG_MEMTEST_END:
  1416. Begin and End addresses of the area used by the
  1417. simple memory test.
  1418. - CFG_ALT_MEMTEST:
  1419. Enable an alternate, more extensive memory test.
  1420. - CFG_MEMTEST_SCRATCH:
  1421. Scratch address used by the alternate memory test
  1422. You only need to set this if address zero isn't writeable
  1423. - CFG_TFTP_LOADADDR:
  1424. Default load address for network file downloads
  1425. - CFG_LOADS_BAUD_CHANGE:
  1426. Enable temporary baudrate change while serial download
  1427. - CFG_SDRAM_BASE:
  1428. Physical start address of SDRAM. _Must_ be 0 here.
  1429. - CFG_MBIO_BASE:
  1430. Physical start address of Motherboard I/O (if using a
  1431. Cogent motherboard)
  1432. - CFG_FLASH_BASE:
  1433. Physical start address of Flash memory.
  1434. - CFG_MONITOR_BASE:
  1435. Physical start address of boot monitor code (set by
  1436. make config files to be same as the text base address
  1437. (TEXT_BASE) used when linking) - same as
  1438. CFG_FLASH_BASE when booting from flash.
  1439. - CFG_MONITOR_LEN:
  1440. Size of memory reserved for monitor code, used to
  1441. determine _at_compile_time_ (!) if the environment is
  1442. embedded within the U-Boot image, or in a separate
  1443. flash sector.
  1444. - CFG_MALLOC_LEN:
  1445. Size of DRAM reserved for malloc() use.
  1446. - CFG_BOOTM_LEN:
  1447. Normally compressed uImages are limited to an
  1448. uncompressed size of 8 MBytes. If this is not enough,
  1449. you can define CFG_BOOTM_LEN in your board config file
  1450. to adjust this setting to your needs.
  1451. - CFG_BOOTMAPSZ:
  1452. Maximum size of memory mapped by the startup code of
  1453. the Linux kernel; all data that must be processed by
  1454. the Linux kernel (bd_info, boot arguments, eventually
  1455. initrd image) must be put below this limit.
  1456. - CFG_MAX_FLASH_BANKS:
  1457. Max number of Flash memory banks
  1458. - CFG_MAX_FLASH_SECT:
  1459. Max number of sectors on a Flash chip
  1460. - CFG_FLASH_ERASE_TOUT:
  1461. Timeout for Flash erase operations (in ms)
  1462. - CFG_FLASH_WRITE_TOUT:
  1463. Timeout for Flash write operations (in ms)
  1464. - CFG_FLASH_LOCK_TOUT
  1465. Timeout for Flash set sector lock bit operation (in ms)
  1466. - CFG_FLASH_UNLOCK_TOUT
  1467. Timeout for Flash clear lock bits operation (in ms)
  1468. - CFG_FLASH_PROTECTION
  1469. If defined, hardware flash sectors protection is used
  1470. instead of U-Boot software protection.
  1471. - CFG_DIRECT_FLASH_TFTP:
  1472. Enable TFTP transfers directly to flash memory;
  1473. without this option such a download has to be
  1474. performed in two steps: (1) download to RAM, and (2)
  1475. copy from RAM to flash.
  1476. The two-step approach is usually more reliable, since
  1477. you can check if the download worked before you erase
  1478. the flash, but in some situations (when sytem RAM is
  1479. too limited to allow for a tempory copy of the
  1480. downloaded image) this option may be very useful.
  1481. - CFG_FLASH_CFI:
  1482. Define if the flash driver uses extra elements in the
  1483. common flash structure for storing flash geometry.
  1484. - CFG_FLASH_CFI_DRIVER
  1485. This option also enables the building of the cfi_flash driver
  1486. in the drivers directory
  1487. - CFG_FLASH_QUIET_TEST
  1488. If this option is defined, the common CFI flash doesn't
  1489. print it's warning upon not recognized FLASH banks. This
  1490. is useful, if some of the configured banks are only
  1491. optionally available.
  1492. - CFG_RX_ETH_BUFFER:
  1493. Defines the number of ethernet receive buffers. On some
  1494. ethernet controllers it is recommended to set this value
  1495. to 8 or even higher (EEPRO100 or 405 EMAC), since all
  1496. buffers can be full shortly after enabling the interface
  1497. on high ethernet traffic.
  1498. Defaults to 4 if not defined.
  1499. The following definitions that deal with the placement and management
  1500. of environment data (variable area); in general, we support the
  1501. following configurations:
  1502. - CFG_ENV_IS_IN_FLASH:
  1503. Define this if the environment is in flash memory.
  1504. a) The environment occupies one whole flash sector, which is
  1505. "embedded" in the text segment with the U-Boot code. This
  1506. happens usually with "bottom boot sector" or "top boot
  1507. sector" type flash chips, which have several smaller
  1508. sectors at the start or the end. For instance, such a
  1509. layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
  1510. such a case you would place the environment in one of the
  1511. 4 kB sectors - with U-Boot code before and after it. With
  1512. "top boot sector" type flash chips, you would put the
  1513. environment in one of the last sectors, leaving a gap
  1514. between U-Boot and the environment.
  1515. - CFG_ENV_OFFSET:
  1516. Offset of environment data (variable area) to the
  1517. beginning of flash memory; for instance, with bottom boot
  1518. type flash chips the second sector can be used: the offset
  1519. for this sector is given here.
  1520. CFG_ENV_OFFSET is used relative to CFG_FLASH_BASE.
  1521. - CFG_ENV_ADDR:
  1522. This is just another way to specify the start address of
  1523. the flash sector containing the environment (instead of
  1524. CFG_ENV_OFFSET).
  1525. - CFG_ENV_SECT_SIZE:
  1526. Size of the sector containing the environment.
  1527. b) Sometimes flash chips have few, equal sized, BIG sectors.
  1528. In such a case you don't want to spend a whole sector for
  1529. the environment.
  1530. - CFG_ENV_SIZE:
  1531. If you use this in combination with CFG_ENV_IS_IN_FLASH
  1532. and CFG_ENV_SECT_SIZE, you can specify to use only a part
  1533. of this flash sector for the environment. This saves
  1534. memory for the RAM copy of the environment.
  1535. It may also save flash memory if you decide to use this
  1536. when your environment is "embedded" within U-Boot code,
  1537. since then the remainder of the flash sector could be used
  1538. for U-Boot code. It should be pointed out that this is
  1539. STRONGLY DISCOURAGED from a robustness point of view:
  1540. updating the environment in flash makes it always
  1541. necessary to erase the WHOLE sector. If something goes
  1542. wrong before the contents has been restored from a copy in
  1543. RAM, your target system will be dead.
  1544. - CFG_ENV_ADDR_REDUND
  1545. CFG_ENV_SIZE_REDUND
  1546. These settings describe a second storage area used to hold
  1547. a redundand copy of the environment data, so that there is
  1548. a valid backup copy in case there is a power failure during
  1549. a "saveenv" operation.
  1550. BE CAREFUL! Any changes to the flash layout, and some changes to the
  1551. source code will make it necessary to adapt <board>/u-boot.lds*
  1552. accordingly!
  1553. - CFG_ENV_IS_IN_NVRAM:
  1554. Define this if you have some non-volatile memory device
  1555. (NVRAM, battery buffered SRAM) which you want to use for the
  1556. environment.
  1557. - CFG_ENV_ADDR:
  1558. - CFG_ENV_SIZE:
  1559. These two #defines are used to determin the memory area you
  1560. want to use for environment. It is assumed that this memory
  1561. can just be read and written to, without any special
  1562. provision.
  1563. BE CAREFUL! The first access to the environment happens quite early
  1564. in U-Boot initalization (when we try to get the setting of for the
  1565. console baudrate). You *MUST* have mappend your NVRAM area then, or
  1566. U-Boot will hang.
  1567. Please note that even with NVRAM we still use a copy of the
  1568. environment in RAM: we could work on NVRAM directly, but we want to
  1569. keep settings there always unmodified except somebody uses "saveenv"
  1570. to save the current settings.
  1571. - CFG_ENV_IS_IN_EEPROM:
  1572. Use this if you have an EEPROM or similar serial access
  1573. device and a driver for it.
  1574. - CFG_ENV_OFFSET:
  1575. - CFG_ENV_SIZE:
  1576. These two #defines specify the offset and size of the
  1577. environment area within the total memory of your EEPROM.
  1578. - CFG_I2C_EEPROM_ADDR:
  1579. If defined, specified the chip address of the EEPROM device.
  1580. The default address is zero.
  1581. - CFG_EEPROM_PAGE_WRITE_BITS:
  1582. If defined, the number of bits used to address bytes in a
  1583. single page in the EEPROM device. A 64 byte page, for example
  1584. would require six bits.
  1585. - CFG_EEPROM_PAGE_WRITE_DELAY_MS:
  1586. If defined, the number of milliseconds to delay between
  1587. page writes. The default is zero milliseconds.
  1588. - CFG_I2C_EEPROM_ADDR_LEN:
  1589. The length in bytes of the EEPROM memory array address. Note
  1590. that this is NOT the chip address length!
  1591. - CFG_I2C_EEPROM_ADDR_OVERFLOW:
  1592. EEPROM chips that implement "address overflow" are ones
  1593. like Catalyst 24WC04/08/16 which has 9/10/11 bits of
  1594. address and the extra bits end up in the "chip address" bit
  1595. slots. This makes a 24WC08 (1Kbyte) chip look like four 256
  1596. byte chips.
  1597. Note that we consider the length of the address field to
  1598. still be one byte because the extra address bits are hidden
  1599. in the chip address.
  1600. - CFG_EEPROM_SIZE:
  1601. The size in bytes of the EEPROM device.
  1602. - CFG_ENV_IS_IN_DATAFLASH:
  1603. Define this if you have a DataFlash memory device which you
  1604. want to use for the environment.
  1605. - CFG_ENV_OFFSET:
  1606. - CFG_ENV_ADDR:
  1607. - CFG_ENV_SIZE:
  1608. These three #defines specify the offset and size of the
  1609. environment area within the total memory of your DataFlash placed
  1610. at the specified address.
  1611. - CFG_ENV_IS_IN_NAND:
  1612. Define this if you have a NAND device which you want to use
  1613. for the environment.
  1614. - CFG_ENV_OFFSET:
  1615. - CFG_ENV_SIZE:
  1616. These two #defines specify the offset and size of the environment
  1617. area within the first NAND device.
  1618. - CFG_ENV_OFFSET_REDUND
  1619. This setting describes a second storage area of CFG_ENV_SIZE
  1620. size used to hold a redundant copy of the environment data,
  1621. so that there is a valid backup copy in case there is a
  1622. power failure during a "saveenv" operation.
  1623. Note: CFG_ENV_OFFSET and CFG_ENV_OFFSET_REDUND must be aligned
  1624. to a block boundary, and CFG_ENV_SIZE must be a multiple of
  1625. the NAND devices block size.
  1626. - CFG_SPI_INIT_OFFSET
  1627. Defines offset to the initial SPI buffer area in DPRAM. The
  1628. area is used at an early stage (ROM part) if the environment
  1629. is configured to reside in the SPI EEPROM: We need a 520 byte
  1630. scratch DPRAM area. It is used between the two initialization
  1631. calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
  1632. to be a good choice since it makes it far enough from the
  1633. start of the data area as well as from the stack pointer.
  1634. Please note that the environment is read-only until the monitor
  1635. has been relocated to RAM and a RAM copy of the environment has been
  1636. created; also, when using EEPROM you will have to use getenv_r()
  1637. until then to read environment variables.
  1638. The environment is protected by a CRC32 checksum. Before the monitor
  1639. is relocated into RAM, as a result of a bad CRC you will be working
  1640. with the compiled-in default environment - *silently*!!! [This is
  1641. necessary, because the first environment variable we need is the
  1642. "baudrate" setting for the console - if we have a bad CRC, we don't
  1643. have any device yet where we could complain.]
  1644. Note: once the monitor has been relocated, then it will complain if
  1645. the default environment is used; a new CRC is computed as soon as you
  1646. use the "saveenv" command to store a valid environment.
  1647. - CFG_FAULT_ECHO_LINK_DOWN:
  1648. Echo the inverted Ethernet link state to the fault LED.
  1649. Note: If this option is active, then CFG_FAULT_MII_ADDR
  1650. also needs to be defined.
  1651. - CFG_FAULT_MII_ADDR:
  1652. MII address of the PHY to check for the Ethernet link state.
  1653. - CFG_64BIT_VSPRINTF:
  1654. Makes vsprintf (and all *printf functions) support printing
  1655. of 64bit values by using the L quantifier
  1656. - CFG_64BIT_STRTOUL:
  1657. Adds simple_strtoull that returns a 64bit value
  1658. Low Level (hardware related) configuration options:
  1659. ---------------------------------------------------
  1660. - CFG_CACHELINE_SIZE:
  1661. Cache Line Size of the CPU.
  1662. - CFG_DEFAULT_IMMR:
  1663. Default address of the IMMR after system reset.
  1664. Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
  1665. and RPXsuper) to be able to adjust the position of
  1666. the IMMR register after a reset.
  1667. - Floppy Disk Support:
  1668. CFG_FDC_DRIVE_NUMBER
  1669. the default drive number (default value 0)
  1670. CFG_ISA_IO_STRIDE
  1671. defines the spacing between fdc chipset registers
  1672. (default value 1)
  1673. CFG_ISA_IO_OFFSET
  1674. defines the offset of register from address. It
  1675. depends on which part of the data bus is connected to
  1676. the fdc chipset. (default value 0)
  1677. If CFG_ISA_IO_STRIDE CFG_ISA_IO_OFFSET and
  1678. CFG_FDC_DRIVE_NUMBER are undefined, they take their
  1679. default value.
  1680. if CFG_FDC_HW_INIT is defined, then the function
  1681. fdc_hw_init() is called at the beginning of the FDC
  1682. setup. fdc_hw_init() must be provided by the board
  1683. source code. It is used to make hardware dependant
  1684. initializations.
  1685. - CFG_IMMR: Physical address of the Internal Memory.
  1686. DO NOT CHANGE unless you know exactly what you're
  1687. doing! (11-4) [MPC8xx/82xx systems only]
  1688. - CFG_INIT_RAM_ADDR:
  1689. Start address of memory area that can be used for
  1690. initial data and stack; please note that this must be
  1691. writable memory that is working WITHOUT special
  1692. initialization, i. e. you CANNOT use normal RAM which
  1693. will become available only after programming the
  1694. memory controller and running certain initialization
  1695. sequences.
  1696. U-Boot uses the following memory types:
  1697. - MPC8xx and MPC8260: IMMR (internal memory of the CPU)
  1698. - MPC824X: data cache
  1699. - PPC4xx: data cache
  1700. - CFG_GBL_DATA_OFFSET:
  1701. Offset of the initial data structure in the memory
  1702. area defined by CFG_INIT_RAM_ADDR. Usually
  1703. CFG_GBL_DATA_OFFSET is chosen such that the initial
  1704. data is located at the end of the available space
  1705. (sometimes written as (CFG_INIT_RAM_END -
  1706. CFG_INIT_DATA_SIZE), and the initial stack is just
  1707. below that area (growing from (CFG_INIT_RAM_ADDR +
  1708. CFG_GBL_DATA_OFFSET) downward.
  1709. Note:
  1710. On the MPC824X (or other systems that use the data
  1711. cache for initial memory) the address chosen for
  1712. CFG_INIT_RAM_ADDR is basically arbitrary - it must
  1713. point to an otherwise UNUSED address space between
  1714. the top of RAM and the start of the PCI space.
  1715. - CFG_SIUMCR: SIU Module Configuration (11-6)
  1716. - CFG_SYPCR: System Protection Control (11-9)
  1717. - CFG_TBSCR: Time Base Status and Control (11-26)
  1718. - CFG_PISCR: Periodic Interrupt Status and Control (11-31)
  1719. - CFG_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30)
  1720. - CFG_SCCR: System Clock and reset Control Register (15-27)
  1721. - CFG_OR_TIMING_SDRAM:
  1722. SDRAM timing
  1723. - CFG_MAMR_PTA:
  1724. periodic timer for refresh
  1725. - CFG_DER: Debug Event Register (37-47)
  1726. - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CFG_REMAP_OR_AM,
  1727. CFG_PRELIM_OR_AM, CFG_OR_TIMING_FLASH, CFG_OR0_REMAP,
  1728. CFG_OR0_PRELIM, CFG_BR0_PRELIM, CFG_OR1_REMAP, CFG_OR1_PRELIM,
  1729. CFG_BR1_PRELIM:
  1730. Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
  1731. - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
  1732. CFG_OR_TIMING_SDRAM, CFG_OR2_PRELIM, CFG_BR2_PRELIM,
  1733. CFG_OR3_PRELIM, CFG_BR3_PRELIM:
  1734. Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
  1735. - CFG_MAMR_PTA, CFG_MPTPR_2BK_4K, CFG_MPTPR_1BK_4K, CFG_MPTPR_2BK_8K,
  1736. CFG_MPTPR_1BK_8K, CFG_MAMR_8COL, CFG_MAMR_9COL:
  1737. Machine Mode Register and Memory Periodic Timer
  1738. Prescaler definitions (SDRAM timing)
  1739. - CFG_I2C_UCODE_PATCH, CFG_I2C_DPMEM_OFFSET [0x1FC0]:
  1740. enable I2C microcode relocation patch (MPC8xx);
  1741. define relocation offset in DPRAM [DSP2]
  1742. - CFG_SMC_UCODE_PATCH, CFG_SMC_DPMEM_OFFSET [0x1FC0]:
  1743. enable SMC microcode relocation patch (MPC8xx);
  1744. define relocation offset in DPRAM [SMC1]
  1745. - CFG_SPI_UCODE_PATCH, CFG_SPI_DPMEM_OFFSET [0x1FC0]:
  1746. enable SPI microcode relocation patch (MPC8xx);
  1747. define relocation offset in DPRAM [SCC4]
  1748. - CFG_USE_OSCCLK:
  1749. Use OSCM clock mode on MBX8xx board. Be careful,
  1750. wrong setting might damage your board. Read
  1751. doc/README.MBX before setting this variable!
  1752. - CFG_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
  1753. Offset of the bootmode word in DPRAM used by post
  1754. (Power On Self Tests). This definition overrides
  1755. #define'd default value in commproc.h resp.
  1756. cpm_8260.h.
  1757. - CFG_PCI_SLV_MEM_LOCAL, CFG_PCI_SLV_MEM_BUS, CFG_PICMR0_MASK_ATTRIB,
  1758. CFG_PCI_MSTR0_LOCAL, CFG_PCIMSK0_MASK, CFG_PCI_MSTR1_LOCAL,
  1759. CFG_PCIMSK1_MASK, CFG_PCI_MSTR_MEM_LOCAL, CFG_PCI_MSTR_MEM_BUS,
  1760. CFG_CPU_PCI_MEM_START, CFG_PCI_MSTR_MEM_SIZE, CFG_POCMR0_MASK_ATTRIB,
  1761. CFG_PCI_MSTR_MEMIO_LOCAL, CFG_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
  1762. CFG_PCI_MSTR_MEMIO_SIZE, CFG_POCMR1_MASK_ATTRIB, CFG_PCI_MSTR_IO_LOCAL,
  1763. CFG_PCI_MSTR_IO_BUS, CFG_CPU_PCI_IO_START, CFG_PCI_MSTR_IO_SIZE,
  1764. CFG_POCMR2_MASK_ATTRIB: (MPC826x only)
  1765. Overrides the default PCI memory map in cpu/mpc8260/pci.c if set.
  1766. - CONFIG_SPD_EEPROM
  1767. Get DDR timing information from an I2C EEPROM. Common with pluggable
  1768. memory modules such as SODIMMs
  1769. SPD_EEPROM_ADDRESS
  1770. I2C address of the SPD EEPROM
  1771. - CFG_SPD_BUS_NUM
  1772. If SPD EEPROM is on an I2C bus other than the first one, specify here.
  1773. Note that the value must resolve to something your driver can deal with.
  1774. - CFG_83XX_DDR_USES_CS0
  1775. Only for 83xx systems. If specified, then DDR should be configured
  1776. using CS0 and CS1 instead of CS2 and CS3.
  1777. - CFG_83XX_DDR_USES_CS0
  1778. Only for 83xx systems. If specified, then DDR should be configured
  1779. using CS0 and CS1 instead of CS2 and CS3.
  1780. - CONFIG_ETHER_ON_FEC[12]
  1781. Define to enable FEC[12] on a 8xx series processor.
  1782. - CONFIG_FEC[12]_PHY
  1783. Define to the hardcoded PHY address which corresponds
  1784. to the given FEC; i. e.
  1785. #define CONFIG_FEC1_PHY 4
  1786. means that the PHY with address 4 is connected to FEC1
  1787. When set to -1, means to probe for first available.
  1788. - CONFIG_FEC[12]_PHY_NORXERR
  1789. The PHY does not have a RXERR line (RMII only).
  1790. (so program the FEC to ignore it).
  1791. - CONFIG_RMII
  1792. Enable RMII mode for all FECs.
  1793. Note that this is a global option, we can't
  1794. have one FEC in standard MII mode and another in RMII mode.
  1795. - CONFIG_CRC32_VERIFY
  1796. Add a verify option to the crc32 command.
  1797. The syntax is:
  1798. => crc32 -v <address> <count> <crc32>
  1799. Where address/count indicate a memory area
  1800. and crc32 is the correct crc32 which the
  1801. area should have.
  1802. - CONFIG_LOOPW
  1803. Add the "loopw" memory command. This only takes effect if
  1804. the memory commands are activated globally (CONFIG_CMD_MEM).
  1805. - CONFIG_MX_CYCLIC
  1806. Add the "mdc" and "mwc" memory commands. These are cyclic
  1807. "md/mw" commands.
  1808. Examples:
  1809. => mdc.b 10 4 500
  1810. This command will print 4 bytes (10,11,12,13) each 500 ms.
  1811. => mwc.l 100 12345678 10
  1812. This command will write 12345678 to address 100 all 10 ms.
  1813. This only takes effect if the memory commands are activated
  1814. globally (CONFIG_CMD_MEM).
  1815. - CONFIG_SKIP_LOWLEVEL_INIT
  1816. - CONFIG_SKIP_RELOCATE_UBOOT
  1817. [ARM only] If these variables are defined, then
  1818. certain low level initializations (like setting up
  1819. the memory controller) are omitted and/or U-Boot does
  1820. not relocate itself into RAM.
  1821. Normally these variables MUST NOT be defined. The
  1822. only exception is when U-Boot is loaded (to RAM) by
  1823. some other boot loader or by a debugger which
  1824. performs these intializations itself.
  1825. Building the Software:
  1826. ======================
  1827. Building U-Boot has been tested in native PPC environments (on a
  1828. PowerBook G3 running LinuxPPC 2000) and in cross environments
  1829. (running RedHat 6.x and 7.x Linux on x86, Solaris 2.6 on a SPARC, and
  1830. NetBSD 1.5 on x86).
  1831. If you are not using a native PPC environment, it is assumed that you
  1832. have the GNU cross compiling tools available in your path and named
  1833. with a prefix of "powerpc-linux-". If this is not the case, (e.g. if
  1834. you are using Monta Vista's Hard Hat Linux CDK 1.2) you must change
  1835. the definition of CROSS_COMPILE in Makefile. For HHL on a 4xx CPU,
  1836. change it to:
  1837. CROSS_COMPILE = ppc_4xx-
  1838. U-Boot is intended to be simple to build. After installing the
  1839. sources you must configure U-Boot for one specific board type. This
  1840. is done by typing:
  1841. make NAME_config
  1842. where "NAME_config" is the name of one of the existing
  1843. configurations; see the main Makefile for supported names.
  1844. Note: for some board special configuration names may exist; check if
  1845. additional information is available from the board vendor; for
  1846. instance, the TQM823L systems are available without (standard)
  1847. or with LCD support. You can select such additional "features"
  1848. when chosing the configuration, i. e.
  1849. make TQM823L_config
  1850. - will configure for a plain TQM823L, i. e. no LCD support
  1851. make TQM823L_LCD_config
  1852. - will configure for a TQM823L with U-Boot console on LCD
  1853. etc.
  1854. Finally, type "make all", and you should get some working U-Boot
  1855. images ready for download to / installation on your system:
  1856. - "u-boot.bin" is a raw binary image
  1857. - "u-boot" is an image in ELF binary format
  1858. - "u-boot.srec" is in Motorola S-Record format
  1859. By default the build is performed locally and the objects are saved
  1860. in the source directory. One of the two methods can be used to change
  1861. this behavior and build U-Boot to some external directory:
  1862. 1. Add O= to the make command line invocations:
  1863. make O=/tmp/build distclean
  1864. make O=/tmp/build NAME_config
  1865. make O=/tmp/build all
  1866. 2. Set environment variable BUILD_DIR to point to the desired location:
  1867. export BUILD_DIR=/tmp/build
  1868. make distclean
  1869. make NAME_config
  1870. make all
  1871. Note that the command line "O=" setting overrides the BUILD_DIR environment
  1872. variable.
  1873. Please be aware that the Makefiles assume you are using GNU make, so
  1874. for instance on NetBSD you might need to use "gmake" instead of
  1875. native "make".
  1876. If the system board that you have is not listed, then you will need
  1877. to port U-Boot to your hardware platform. To do this, follow these
  1878. steps:
  1879. 1. Add a new configuration option for your board to the toplevel
  1880. "Makefile" and to the "MAKEALL" script, using the existing
  1881. entries as examples. Note that here and at many other places
  1882. boards and other names are listed in alphabetical sort order. Please
  1883. keep this order.
  1884. 2. Create a new directory to hold your board specific code. Add any
  1885. files you need. In your board directory, you will need at least
  1886. the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
  1887. 3. Create a new configuration file "include/configs/<board>.h" for
  1888. your board
  1889. 3. If you're porting U-Boot to a new CPU, then also create a new
  1890. directory to hold your CPU specific code. Add any files you need.
  1891. 4. Run "make <board>_config" with your new name.
  1892. 5. Type "make", and you should get a working "u-boot.srec" file
  1893. to be installed on your target system.
  1894. 6. Debug and solve any problems that might arise.
  1895. [Of course, this last step is much harder than it sounds.]
  1896. Testing of U-Boot Modifications, Ports to New Hardware, etc.:
  1897. ==============================================================
  1898. If you have modified U-Boot sources (for instance added a new board
  1899. or support for new devices, a new CPU, etc.) you are expected to
  1900. provide feedback to the other developers. The feedback normally takes
  1901. the form of a "patch", i. e. a context diff against a certain (latest
  1902. official or latest in CVS) version of U-Boot sources.
  1903. But before you submit such a patch, please verify that your modifi-
  1904. cation did not break existing code. At least make sure that *ALL* of
  1905. the supported boards compile WITHOUT ANY compiler warnings. To do so,
  1906. just run the "MAKEALL" script, which will configure and build U-Boot
  1907. for ALL supported system. Be warned, this will take a while. You can
  1908. select which (cross) compiler to use by passing a `CROSS_COMPILE'
  1909. environment variable to the script, i. e. to use the cross tools from
  1910. MontaVista's Hard Hat Linux you can type
  1911. CROSS_COMPILE=ppc_8xx- MAKEALL
  1912. or to build on a native PowerPC system you can type
  1913. CROSS_COMPILE=' ' MAKEALL
  1914. When using the MAKEALL script, the default behaviour is to build U-Boot
  1915. in the source directory. This location can be changed by setting the
  1916. BUILD_DIR environment variable. Also, for each target built, the MAKEALL
  1917. script saves two log files (<target>.ERR and <target>.MAKEALL) in the
  1918. <source dir>/LOG directory. This default location can be changed by
  1919. setting the MAKEALL_LOGDIR environment variable. For example:
  1920. export BUILD_DIR=/tmp/build
  1921. export MAKEALL_LOGDIR=/tmp/log
  1922. CROSS_COMPILE=ppc_8xx- MAKEALL
  1923. With the above settings build objects are saved in the /tmp/build, log
  1924. files are saved in the /tmp/log and the source tree remains clean during
  1925. the whole build process.
  1926. See also "U-Boot Porting Guide" below.
  1927. Monitor Commands - Overview:
  1928. ============================
  1929. go - start application at address 'addr'
  1930. run - run commands in an environment variable
  1931. bootm - boot application image from memory
  1932. bootp - boot image via network using BootP/TFTP protocol
  1933. tftpboot- boot image via network using TFTP protocol
  1934. and env variables "ipaddr" and "serverip"
  1935. (and eventually "gatewayip")
  1936. rarpboot- boot image via network using RARP/TFTP protocol
  1937. diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
  1938. loads - load S-Record file over serial line
  1939. loadb - load binary file over serial line (kermit mode)
  1940. md - memory display
  1941. mm - memory modify (auto-incrementing)
  1942. nm - memory modify (constant address)
  1943. mw - memory write (fill)
  1944. cp - memory copy
  1945. cmp - memory compare
  1946. crc32 - checksum calculation
  1947. imd - i2c memory display
  1948. imm - i2c memory modify (auto-incrementing)
  1949. inm - i2c memory modify (constant address)
  1950. imw - i2c memory write (fill)
  1951. icrc32 - i2c checksum calculation
  1952. iprobe - probe to discover valid I2C chip addresses
  1953. iloop - infinite loop on address range
  1954. isdram - print SDRAM configuration information
  1955. sspi - SPI utility commands
  1956. base - print or set address offset
  1957. printenv- print environment variables
  1958. setenv - set environment variables
  1959. saveenv - save environment variables to persistent storage
  1960. protect - enable or disable FLASH write protection
  1961. erase - erase FLASH memory
  1962. flinfo - print FLASH memory information
  1963. bdinfo - print Board Info structure
  1964. iminfo - print header information for application image
  1965. coninfo - print console devices and informations
  1966. ide - IDE sub-system
  1967. loop - infinite loop on address range
  1968. loopw - infinite write loop on address range
  1969. mtest - simple RAM test
  1970. icache - enable or disable instruction cache
  1971. dcache - enable or disable data cache
  1972. reset - Perform RESET of the CPU
  1973. echo - echo args to console
  1974. version - print monitor version
  1975. help - print online help
  1976. ? - alias for 'help'
  1977. Monitor Commands - Detailed Description:
  1978. ========================================
  1979. TODO.
  1980. For now: just type "help <command>".
  1981. Environment Variables:
  1982. ======================
  1983. U-Boot supports user configuration using Environment Variables which
  1984. can be made persistent by saving to Flash memory.
  1985. Environment Variables are set using "setenv", printed using
  1986. "printenv", and saved to Flash using "saveenv". Using "setenv"
  1987. without a value can be used to delete a variable from the
  1988. environment. As long as you don't save the environment you are
  1989. working with an in-memory copy. In case the Flash area containing the
  1990. environment is erased by accident, a default environment is provided.
  1991. Some configuration options can be set using Environment Variables:
  1992. baudrate - see CONFIG_BAUDRATE
  1993. bootdelay - see CONFIG_BOOTDELAY
  1994. bootcmd - see CONFIG_BOOTCOMMAND
  1995. bootargs - Boot arguments when booting an RTOS image
  1996. bootfile - Name of the image to load with TFTP
  1997. autoload - if set to "no" (any string beginning with 'n'),
  1998. "bootp" will just load perform a lookup of the
  1999. configuration from the BOOTP server, but not try to
  2000. load any image using TFTP
  2001. autostart - if set to "yes", an image loaded using the "bootp",
  2002. "rarpboot", "tftpboot" or "diskboot" commands will
  2003. be automatically started (by internally calling
  2004. "bootm")
  2005. If set to "no", a standalone image passed to the
  2006. "bootm" command will be copied to the load address
  2007. (and eventually uncompressed), but NOT be started.
  2008. This can be used to load and uncompress arbitrary
  2009. data.
  2010. i2cfast - (PPC405GP|PPC405EP only)
  2011. if set to 'y' configures Linux I2C driver for fast
  2012. mode (400kHZ). This environment variable is used in
  2013. initialization code. So, for changes to be effective
  2014. it must be saved and board must be reset.
  2015. initrd_high - restrict positioning of initrd images:
  2016. If this variable is not set, initrd images will be
  2017. copied to the highest possible address in RAM; this
  2018. is usually what you want since it allows for
  2019. maximum initrd size. If for some reason you want to
  2020. make sure that the initrd image is loaded below the
  2021. CFG_BOOTMAPSZ limit, you can set this environment
  2022. variable to a value of "no" or "off" or "0".
  2023. Alternatively, you can set it to a maximum upper
  2024. address to use (U-Boot will still check that it
  2025. does not overwrite the U-Boot stack and data).
  2026. For instance, when you have a system with 16 MB
  2027. RAM, and want to reserve 4 MB from use by Linux,
  2028. you can do this by adding "mem=12M" to the value of
  2029. the "bootargs" variable. However, now you must make
  2030. sure that the initrd image is placed in the first
  2031. 12 MB as well - this can be done with
  2032. setenv initrd_high 00c00000
  2033. If you set initrd_high to 0xFFFFFFFF, this is an
  2034. indication to U-Boot that all addresses are legal
  2035. for the Linux kernel, including addresses in flash
  2036. memory. In this case U-Boot will NOT COPY the
  2037. ramdisk at all. This may be useful to reduce the
  2038. boot time on your system, but requires that this
  2039. feature is supported by your Linux kernel.
  2040. ipaddr - IP address; needed for tftpboot command
  2041. loadaddr - Default load address for commands like "bootp",
  2042. "rarpboot", "tftpboot", "loadb" or "diskboot"
  2043. loads_echo - see CONFIG_LOADS_ECHO
  2044. serverip - TFTP server IP address; needed for tftpboot command
  2045. bootretry - see CONFIG_BOOT_RETRY_TIME
  2046. bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
  2047. bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
  2048. ethprime - When CONFIG_NET_MULTI is enabled controls which
  2049. interface is used first.
  2050. ethact - When CONFIG_NET_MULTI is enabled controls which
  2051. interface is currently active. For example you
  2052. can do the following
  2053. => setenv ethact FEC ETHERNET
  2054. => ping 192.168.0.1 # traffic sent on FEC ETHERNET
  2055. => setenv ethact SCC ETHERNET
  2056. => ping 10.0.0.1 # traffic sent on SCC ETHERNET
  2057. ethrotate - When set to "no" U-Boot does not go through all
  2058. available network interfaces.
  2059. It just stays at the currently selected interface.
  2060. netretry - When set to "no" each network operation will
  2061. either succeed or fail without retrying.
  2062. When set to "once" the network operation will
  2063. fail when all the available network interfaces
  2064. are tried once without success.
  2065. Useful on scripts which control the retry operation
  2066. themselves.
  2067. npe_ucode - see CONFIG_IXP4XX_NPE_EXT_UCOD
  2068. if set load address for the npe microcode
  2069. tftpsrcport - If this is set, the value is used for TFTP's
  2070. UDP source port.
  2071. tftpdstport - If this is set, the value is used for TFTP's UDP
  2072. destination port instead of the Well Know Port 69.
  2073. vlan - When set to a value < 4095 the traffic over
  2074. ethernet is encapsulated/received over 802.1q
  2075. VLAN tagged frames.
  2076. The following environment variables may be used and automatically
  2077. updated by the network boot commands ("bootp" and "rarpboot"),
  2078. depending the information provided by your boot server:
  2079. bootfile - see above
  2080. dnsip - IP address of your Domain Name Server
  2081. dnsip2 - IP address of your secondary Domain Name Server
  2082. gatewayip - IP address of the Gateway (Router) to use
  2083. hostname - Target hostname
  2084. ipaddr - see above
  2085. netmask - Subnet Mask
  2086. rootpath - Pathname of the root filesystem on the NFS server
  2087. serverip - see above
  2088. There are two special Environment Variables:
  2089. serial# - contains hardware identification information such
  2090. as type string and/or serial number
  2091. ethaddr - Ethernet address
  2092. These variables can be set only once (usually during manufacturing of
  2093. the board). U-Boot refuses to delete or overwrite these variables
  2094. once they have been set once.
  2095. Further special Environment Variables:
  2096. ver - Contains the U-Boot version string as printed
  2097. with the "version" command. This variable is
  2098. readonly (see CONFIG_VERSION_VARIABLE).
  2099. Please note that changes to some configuration parameters may take
  2100. only effect after the next boot (yes, that's just like Windoze :-).
  2101. Command Line Parsing:
  2102. =====================
  2103. There are two different command line parsers available with U-Boot:
  2104. the old "simple" one, and the much more powerful "hush" shell:
  2105. Old, simple command line parser:
  2106. --------------------------------
  2107. - supports environment variables (through setenv / saveenv commands)
  2108. - several commands on one line, separated by ';'
  2109. - variable substitution using "... ${name} ..." syntax
  2110. - special characters ('$', ';') can be escaped by prefixing with '\',
  2111. for example:
  2112. setenv bootcmd bootm \${address}
  2113. - You can also escape text by enclosing in single apostrophes, for example:
  2114. setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
  2115. Hush shell:
  2116. -----------
  2117. - similar to Bourne shell, with control structures like
  2118. if...then...else...fi, for...do...done; while...do...done,
  2119. until...do...done, ...
  2120. - supports environment ("global") variables (through setenv / saveenv
  2121. commands) and local shell variables (through standard shell syntax
  2122. "name=value"); only environment variables can be used with "run"
  2123. command
  2124. General rules:
  2125. --------------
  2126. (1) If a command line (or an environment variable executed by a "run"
  2127. command) contains several commands separated by semicolon, and
  2128. one of these commands fails, then the remaining commands will be
  2129. executed anyway.
  2130. (2) If you execute several variables with one call to run (i. e.
  2131. calling run with a list af variables as arguments), any failing
  2132. command will cause "run" to terminate, i. e. the remaining
  2133. variables are not executed.
  2134. Note for Redundant Ethernet Interfaces:
  2135. =======================================
  2136. Some boards come with redundant ethernet interfaces; U-Boot supports
  2137. such configurations and is capable of automatic selection of a
  2138. "working" interface when needed. MAC assignment works as follows:
  2139. Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
  2140. MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
  2141. "eth1addr" (=>eth1), "eth2addr", ...
  2142. If the network interface stores some valid MAC address (for instance
  2143. in SROM), this is used as default address if there is NO correspon-
  2144. ding setting in the environment; if the corresponding environment
  2145. variable is set, this overrides the settings in the card; that means:
  2146. o If the SROM has a valid MAC address, and there is no address in the
  2147. environment, the SROM's address is used.
  2148. o If there is no valid address in the SROM, and a definition in the
  2149. environment exists, then the value from the environment variable is
  2150. used.
  2151. o If both the SROM and the environment contain a MAC address, and
  2152. both addresses are the same, this MAC address is used.
  2153. o If both the SROM and the environment contain a MAC address, and the
  2154. addresses differ, the value from the environment is used and a
  2155. warning is printed.
  2156. o If neither SROM nor the environment contain a MAC address, an error
  2157. is raised.
  2158. Image Formats:
  2159. ==============
  2160. The "boot" commands of this monitor operate on "image" files which
  2161. can be basicly anything, preceeded by a special header; see the
  2162. definitions in include/image.h for details; basicly, the header
  2163. defines the following image properties:
  2164. * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
  2165. 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
  2166. LynxOS, pSOS, QNX, RTEMS, ARTOS;
  2167. Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS).
  2168. * Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86,
  2169. IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
  2170. Currently supported: ARM, AVR32, Intel x86, MIPS, NIOS, PowerPC).
  2171. * Compression Type (uncompressed, gzip, bzip2)
  2172. * Load Address
  2173. * Entry Point
  2174. * Image Name
  2175. * Image Timestamp
  2176. The header is marked by a special Magic Number, and both the header
  2177. and the data portions of the image are secured against corruption by
  2178. CRC32 checksums.
  2179. Linux Support:
  2180. ==============
  2181. Although U-Boot should support any OS or standalone application
  2182. easily, the main focus has always been on Linux during the design of
  2183. U-Boot.
  2184. U-Boot includes many features that so far have been part of some
  2185. special "boot loader" code within the Linux kernel. Also, any
  2186. "initrd" images to be used are no longer part of one big Linux image;
  2187. instead, kernel and "initrd" are separate images. This implementation
  2188. serves several purposes:
  2189. - the same features can be used for other OS or standalone
  2190. applications (for instance: using compressed images to reduce the
  2191. Flash memory footprint)
  2192. - it becomes much easier to port new Linux kernel versions because
  2193. lots of low-level, hardware dependent stuff are done by U-Boot
  2194. - the same Linux kernel image can now be used with different "initrd"
  2195. images; of course this also means that different kernel images can
  2196. be run with the same "initrd". This makes testing easier (you don't
  2197. have to build a new "zImage.initrd" Linux image when you just
  2198. change a file in your "initrd"). Also, a field-upgrade of the
  2199. software is easier now.
  2200. Linux HOWTO:
  2201. ============
  2202. Porting Linux to U-Boot based systems:
  2203. ---------------------------------------
  2204. U-Boot cannot save you from doing all the necessary modifications to
  2205. configure the Linux device drivers for use with your target hardware
  2206. (no, we don't intend to provide a full virtual machine interface to
  2207. Linux :-).
  2208. But now you can ignore ALL boot loader code (in arch/ppc/mbxboot).
  2209. Just make sure your machine specific header file (for instance
  2210. include/asm-ppc/tqm8xx.h) includes the same definition of the Board
  2211. Information structure as we define in include/u-boot.h, and make
  2212. sure that your definition of IMAP_ADDR uses the same value as your
  2213. U-Boot configuration in CFG_IMMR.
  2214. Configuring the Linux kernel:
  2215. -----------------------------
  2216. No specific requirements for U-Boot. Make sure you have some root
  2217. device (initial ramdisk, NFS) for your target system.
  2218. Building a Linux Image:
  2219. -----------------------
  2220. With U-Boot, "normal" build targets like "zImage" or "bzImage" are
  2221. not used. If you use recent kernel source, a new build target
  2222. "uImage" will exist which automatically builds an image usable by
  2223. U-Boot. Most older kernels also have support for a "pImage" target,
  2224. which was introduced for our predecessor project PPCBoot and uses a
  2225. 100% compatible format.
  2226. Example:
  2227. make TQM850L_config
  2228. make oldconfig
  2229. make dep
  2230. make uImage
  2231. The "uImage" build target uses a special tool (in 'tools/mkimage') to
  2232. encapsulate a compressed Linux kernel image with header information,
  2233. CRC32 checksum etc. for use with U-Boot. This is what we are doing:
  2234. * build a standard "vmlinux" kernel image (in ELF binary format):
  2235. * convert the kernel into a raw binary image:
  2236. ${CROSS_COMPILE}-objcopy -O binary \
  2237. -R .note -R .comment \
  2238. -S vmlinux linux.bin
  2239. * compress the binary image:
  2240. gzip -9 linux.bin
  2241. * package compressed binary image for U-Boot:
  2242. mkimage -A ppc -O linux -T kernel -C gzip \
  2243. -a 0 -e 0 -n "Linux Kernel Image" \
  2244. -d linux.bin.gz uImage
  2245. The "mkimage" tool can also be used to create ramdisk images for use
  2246. with U-Boot, either separated from the Linux kernel image, or
  2247. combined into one file. "mkimage" encapsulates the images with a 64
  2248. byte header containing information about target architecture,
  2249. operating system, image type, compression method, entry points, time
  2250. stamp, CRC32 checksums, etc.
  2251. "mkimage" can be called in two ways: to verify existing images and
  2252. print the header information, or to build new images.
  2253. In the first form (with "-l" option) mkimage lists the information
  2254. contained in the header of an existing U-Boot image; this includes
  2255. checksum verification:
  2256. tools/mkimage -l image
  2257. -l ==> list image header information
  2258. The second form (with "-d" option) is used to build a U-Boot image
  2259. from a "data file" which is used as image payload:
  2260. tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
  2261. -n name -d data_file image
  2262. -A ==> set architecture to 'arch'
  2263. -O ==> set operating system to 'os'
  2264. -T ==> set image type to 'type'
  2265. -C ==> set compression type 'comp'
  2266. -a ==> set load address to 'addr' (hex)
  2267. -e ==> set entry point to 'ep' (hex)
  2268. -n ==> set image name to 'name'
  2269. -d ==> use image data from 'datafile'
  2270. Right now, all Linux kernels for PowerPC systems use the same load
  2271. address (0x00000000), but the entry point address depends on the
  2272. kernel version:
  2273. - 2.2.x kernels have the entry point at 0x0000000C,
  2274. - 2.3.x and later kernels have the entry point at 0x00000000.
  2275. So a typical call to build a U-Boot image would read:
  2276. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2277. > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
  2278. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz \
  2279. > examples/uImage.TQM850L
  2280. Image Name: 2.4.4 kernel for TQM850L
  2281. Created: Wed Jul 19 02:34:59 2000
  2282. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2283. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2284. Load Address: 0x00000000
  2285. Entry Point: 0x00000000
  2286. To verify the contents of the image (or check for corruption):
  2287. -> tools/mkimage -l examples/uImage.TQM850L
  2288. Image Name: 2.4.4 kernel for TQM850L
  2289. Created: Wed Jul 19 02:34:59 2000
  2290. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2291. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2292. Load Address: 0x00000000
  2293. Entry Point: 0x00000000
  2294. NOTE: for embedded systems where boot time is critical you can trade
  2295. speed for memory and install an UNCOMPRESSED image instead: this
  2296. needs more space in Flash, but boots much faster since it does not
  2297. need to be uncompressed:
  2298. -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz
  2299. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2300. > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
  2301. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux \
  2302. > examples/uImage.TQM850L-uncompressed
  2303. Image Name: 2.4.4 kernel for TQM850L
  2304. Created: Wed Jul 19 02:34:59 2000
  2305. Image Type: PowerPC Linux Kernel Image (uncompressed)
  2306. Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
  2307. Load Address: 0x00000000
  2308. Entry Point: 0x00000000
  2309. Similar you can build U-Boot images from a 'ramdisk.image.gz' file
  2310. when your kernel is intended to use an initial ramdisk:
  2311. -> tools/mkimage -n 'Simple Ramdisk Image' \
  2312. > -A ppc -O linux -T ramdisk -C gzip \
  2313. > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
  2314. Image Name: Simple Ramdisk Image
  2315. Created: Wed Jan 12 14:01:50 2000
  2316. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2317. Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
  2318. Load Address: 0x00000000
  2319. Entry Point: 0x00000000
  2320. Installing a Linux Image:
  2321. -------------------------
  2322. To downloading a U-Boot image over the serial (console) interface,
  2323. you must convert the image to S-Record format:
  2324. objcopy -I binary -O srec examples/image examples/image.srec
  2325. The 'objcopy' does not understand the information in the U-Boot
  2326. image header, so the resulting S-Record file will be relative to
  2327. address 0x00000000. To load it to a given address, you need to
  2328. specify the target address as 'offset' parameter with the 'loads'
  2329. command.
  2330. Example: install the image to address 0x40100000 (which on the
  2331. TQM8xxL is in the first Flash bank):
  2332. => erase 40100000 401FFFFF
  2333. .......... done
  2334. Erased 8 sectors
  2335. => loads 40100000
  2336. ## Ready for S-Record download ...
  2337. ~>examples/image.srec
  2338. 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
  2339. ...
  2340. 15989 15990 15991 15992
  2341. [file transfer complete]
  2342. [connected]
  2343. ## Start Addr = 0x00000000
  2344. You can check the success of the download using the 'iminfo' command;
  2345. this includes a checksum verification so you can be sure no data
  2346. corruption happened:
  2347. => imi 40100000
  2348. ## Checking Image at 40100000 ...
  2349. Image Name: 2.2.13 for initrd on TQM850L
  2350. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2351. Data Size: 335725 Bytes = 327 kB = 0 MB
  2352. Load Address: 00000000
  2353. Entry Point: 0000000c
  2354. Verifying Checksum ... OK
  2355. Boot Linux:
  2356. -----------
  2357. The "bootm" command is used to boot an application that is stored in
  2358. memory (RAM or Flash). In case of a Linux kernel image, the contents
  2359. of the "bootargs" environment variable is passed to the kernel as
  2360. parameters. You can check and modify this variable using the
  2361. "printenv" and "setenv" commands:
  2362. => printenv bootargs
  2363. bootargs=root=/dev/ram
  2364. => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2365. => printenv bootargs
  2366. bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2367. => bootm 40020000
  2368. ## Booting Linux kernel at 40020000 ...
  2369. Image Name: 2.2.13 for NFS on TQM850L
  2370. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2371. Data Size: 381681 Bytes = 372 kB = 0 MB
  2372. Load Address: 00000000
  2373. Entry Point: 0000000c
  2374. Verifying Checksum ... OK
  2375. Uncompressing Kernel Image ... OK
  2376. Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:35:17 MEST 2000
  2377. Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2378. time_init: decrementer frequency = 187500000/60
  2379. Calibrating delay loop... 49.77 BogoMIPS
  2380. Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
  2381. ...
  2382. If you want to boot a Linux kernel with initial ram disk, you pass
  2383. the memory addresses of both the kernel and the initrd image (PPBCOOT
  2384. format!) to the "bootm" command:
  2385. => imi 40100000 40200000
  2386. ## Checking Image at 40100000 ...
  2387. Image Name: 2.2.13 for initrd on TQM850L
  2388. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2389. Data Size: 335725 Bytes = 327 kB = 0 MB
  2390. Load Address: 00000000
  2391. Entry Point: 0000000c
  2392. Verifying Checksum ... OK
  2393. ## Checking Image at 40200000 ...
  2394. Image Name: Simple Ramdisk Image
  2395. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2396. Data Size: 566530 Bytes = 553 kB = 0 MB
  2397. Load Address: 00000000
  2398. Entry Point: 00000000
  2399. Verifying Checksum ... OK
  2400. => bootm 40100000 40200000
  2401. ## Booting Linux kernel at 40100000 ...
  2402. Image Name: 2.2.13 for initrd on TQM850L
  2403. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2404. Data Size: 335725 Bytes = 327 kB = 0 MB
  2405. Load Address: 00000000
  2406. Entry Point: 0000000c
  2407. Verifying Checksum ... OK
  2408. Uncompressing Kernel Image ... OK
  2409. ## Loading RAMDisk Image at 40200000 ...
  2410. Image Name: Simple Ramdisk Image
  2411. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2412. Data Size: 566530 Bytes = 553 kB = 0 MB
  2413. Load Address: 00000000
  2414. Entry Point: 00000000
  2415. Verifying Checksum ... OK
  2416. Loading Ramdisk ... OK
  2417. Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:32:08 MEST 2000
  2418. Boot arguments: root=/dev/ram
  2419. time_init: decrementer frequency = 187500000/60
  2420. Calibrating delay loop... 49.77 BogoMIPS
  2421. ...
  2422. RAMDISK: Compressed image found at block 0
  2423. VFS: Mounted root (ext2 filesystem).
  2424. bash#
  2425. Boot Linux and pass a flat device tree:
  2426. -----------
  2427. First, U-Boot must be compiled with the appropriate defines. See the section
  2428. titled "Linux Kernel Interface" above for a more in depth explanation. The
  2429. following is an example of how to start a kernel and pass an updated
  2430. flat device tree:
  2431. => print oftaddr
  2432. oftaddr=0x300000
  2433. => print oft
  2434. oft=oftrees/mpc8540ads.dtb
  2435. => tftp $oftaddr $oft
  2436. Speed: 1000, full duplex
  2437. Using TSEC0 device
  2438. TFTP from server 192.168.1.1; our IP address is 192.168.1.101
  2439. Filename 'oftrees/mpc8540ads.dtb'.
  2440. Load address: 0x300000
  2441. Loading: #
  2442. done
  2443. Bytes transferred = 4106 (100a hex)
  2444. => tftp $loadaddr $bootfile
  2445. Speed: 1000, full duplex
  2446. Using TSEC0 device
  2447. TFTP from server 192.168.1.1; our IP address is 192.168.1.2
  2448. Filename 'uImage'.
  2449. Load address: 0x200000
  2450. Loading:############
  2451. done
  2452. Bytes transferred = 1029407 (fb51f hex)
  2453. => print loadaddr
  2454. loadaddr=200000
  2455. => print oftaddr
  2456. oftaddr=0x300000
  2457. => bootm $loadaddr - $oftaddr
  2458. ## Booting image at 00200000 ...
  2459. Image Name: Linux-2.6.17-dirty
  2460. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2461. Data Size: 1029343 Bytes = 1005.2 kB
  2462. Load Address: 00000000
  2463. Entry Point: 00000000
  2464. Verifying Checksum ... OK
  2465. Uncompressing Kernel Image ... OK
  2466. Booting using flat device tree at 0x300000
  2467. Using MPC85xx ADS machine description
  2468. Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
  2469. [snip]
  2470. More About U-Boot Image Types:
  2471. ------------------------------
  2472. U-Boot supports the following image types:
  2473. "Standalone Programs" are directly runnable in the environment
  2474. provided by U-Boot; it is expected that (if they behave
  2475. well) you can continue to work in U-Boot after return from
  2476. the Standalone Program.
  2477. "OS Kernel Images" are usually images of some Embedded OS which
  2478. will take over control completely. Usually these programs
  2479. will install their own set of exception handlers, device
  2480. drivers, set up the MMU, etc. - this means, that you cannot
  2481. expect to re-enter U-Boot except by resetting the CPU.
  2482. "RAMDisk Images" are more or less just data blocks, and their
  2483. parameters (address, size) are passed to an OS kernel that is
  2484. being started.
  2485. "Multi-File Images" contain several images, typically an OS
  2486. (Linux) kernel image and one or more data images like
  2487. RAMDisks. This construct is useful for instance when you want
  2488. to boot over the network using BOOTP etc., where the boot
  2489. server provides just a single image file, but you want to get
  2490. for instance an OS kernel and a RAMDisk image.
  2491. "Multi-File Images" start with a list of image sizes, each
  2492. image size (in bytes) specified by an "uint32_t" in network
  2493. byte order. This list is terminated by an "(uint32_t)0".
  2494. Immediately after the terminating 0 follow the images, one by
  2495. one, all aligned on "uint32_t" boundaries (size rounded up to
  2496. a multiple of 4 bytes).
  2497. "Firmware Images" are binary images containing firmware (like
  2498. U-Boot or FPGA images) which usually will be programmed to
  2499. flash memory.
  2500. "Script files" are command sequences that will be executed by
  2501. U-Boot's command interpreter; this feature is especially
  2502. useful when you configure U-Boot to use a real shell (hush)
  2503. as command interpreter.
  2504. Standalone HOWTO:
  2505. =================
  2506. One of the features of U-Boot is that you can dynamically load and
  2507. run "standalone" applications, which can use some resources of
  2508. U-Boot like console I/O functions or interrupt services.
  2509. Two simple examples are included with the sources:
  2510. "Hello World" Demo:
  2511. -------------------
  2512. 'examples/hello_world.c' contains a small "Hello World" Demo
  2513. application; it is automatically compiled when you build U-Boot.
  2514. It's configured to run at address 0x00040004, so you can play with it
  2515. like that:
  2516. => loads
  2517. ## Ready for S-Record download ...
  2518. ~>examples/hello_world.srec
  2519. 1 2 3 4 5 6 7 8 9 10 11 ...
  2520. [file transfer complete]
  2521. [connected]
  2522. ## Start Addr = 0x00040004
  2523. => go 40004 Hello World! This is a test.
  2524. ## Starting application at 0x00040004 ...
  2525. Hello World
  2526. argc = 7
  2527. argv[0] = "40004"
  2528. argv[1] = "Hello"
  2529. argv[2] = "World!"
  2530. argv[3] = "This"
  2531. argv[4] = "is"
  2532. argv[5] = "a"
  2533. argv[6] = "test."
  2534. argv[7] = "<NULL>"
  2535. Hit any key to exit ...
  2536. ## Application terminated, rc = 0x0
  2537. Another example, which demonstrates how to register a CPM interrupt
  2538. handler with the U-Boot code, can be found in 'examples/timer.c'.
  2539. Here, a CPM timer is set up to generate an interrupt every second.
  2540. The interrupt service routine is trivial, just printing a '.'
  2541. character, but this is just a demo program. The application can be
  2542. controlled by the following keys:
  2543. ? - print current values og the CPM Timer registers
  2544. b - enable interrupts and start timer
  2545. e - stop timer and disable interrupts
  2546. q - quit application
  2547. => loads
  2548. ## Ready for S-Record download ...
  2549. ~>examples/timer.srec
  2550. 1 2 3 4 5 6 7 8 9 10 11 ...
  2551. [file transfer complete]
  2552. [connected]
  2553. ## Start Addr = 0x00040004
  2554. => go 40004
  2555. ## Starting application at 0x00040004 ...
  2556. TIMERS=0xfff00980
  2557. Using timer 1
  2558. tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
  2559. Hit 'b':
  2560. [q, b, e, ?] Set interval 1000000 us
  2561. Enabling timer
  2562. Hit '?':
  2563. [q, b, e, ?] ........
  2564. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
  2565. Hit '?':
  2566. [q, b, e, ?] .
  2567. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
  2568. Hit '?':
  2569. [q, b, e, ?] .
  2570. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
  2571. Hit '?':
  2572. [q, b, e, ?] .
  2573. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
  2574. Hit 'e':
  2575. [q, b, e, ?] ...Stopping timer
  2576. Hit 'q':
  2577. [q, b, e, ?] ## Application terminated, rc = 0x0
  2578. Minicom warning:
  2579. ================
  2580. Over time, many people have reported problems when trying to use the
  2581. "minicom" terminal emulation program for serial download. I (wd)
  2582. consider minicom to be broken, and recommend not to use it. Under
  2583. Unix, I recommend to use C-Kermit for general purpose use (and
  2584. especially for kermit binary protocol download ("loadb" command), and
  2585. use "cu" for S-Record download ("loads" command).
  2586. Nevertheless, if you absolutely want to use it try adding this
  2587. configuration to your "File transfer protocols" section:
  2588. Name Program Name U/D FullScr IO-Red. Multi
  2589. X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
  2590. Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
  2591. NetBSD Notes:
  2592. =============
  2593. Starting at version 0.9.2, U-Boot supports NetBSD both as host
  2594. (build U-Boot) and target system (boots NetBSD/mpc8xx).
  2595. Building requires a cross environment; it is known to work on
  2596. NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
  2597. need gmake since the Makefiles are not compatible with BSD make).
  2598. Note that the cross-powerpc package does not install include files;
  2599. attempting to build U-Boot will fail because <machine/ansi.h> is
  2600. missing. This file has to be installed and patched manually:
  2601. # cd /usr/pkg/cross/powerpc-netbsd/include
  2602. # mkdir powerpc
  2603. # ln -s powerpc machine
  2604. # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
  2605. # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
  2606. Native builds *don't* work due to incompatibilities between native
  2607. and U-Boot include files.
  2608. Booting assumes that (the first part of) the image booted is a
  2609. stage-2 loader which in turn loads and then invokes the kernel
  2610. proper. Loader sources will eventually appear in the NetBSD source
  2611. tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
  2612. meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
  2613. Implementation Internals:
  2614. =========================
  2615. The following is not intended to be a complete description of every
  2616. implementation detail. However, it should help to understand the
  2617. inner workings of U-Boot and make it easier to port it to custom
  2618. hardware.
  2619. Initial Stack, Global Data:
  2620. ---------------------------
  2621. The implementation of U-Boot is complicated by the fact that U-Boot
  2622. starts running out of ROM (flash memory), usually without access to
  2623. system RAM (because the memory controller is not initialized yet).
  2624. This means that we don't have writable Data or BSS segments, and BSS
  2625. is not initialized as zero. To be able to get a C environment working
  2626. at all, we have to allocate at least a minimal stack. Implementation
  2627. options for this are defined and restricted by the CPU used: Some CPU
  2628. models provide on-chip memory (like the IMMR area on MPC8xx and
  2629. MPC826x processors), on others (parts of) the data cache can be
  2630. locked as (mis-) used as memory, etc.
  2631. Chris Hallinan posted a good summary of these issues to the
  2632. u-boot-users mailing list:
  2633. Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
  2634. From: "Chris Hallinan" <clh@net1plus.com>
  2635. Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
  2636. ...
  2637. Correct me if I'm wrong, folks, but the way I understand it
  2638. is this: Using DCACHE as initial RAM for Stack, etc, does not
  2639. require any physical RAM backing up the cache. The cleverness
  2640. is that the cache is being used as a temporary supply of
  2641. necessary storage before the SDRAM controller is setup. It's
  2642. beyond the scope of this list to expain the details, but you
  2643. can see how this works by studying the cache architecture and
  2644. operation in the architecture and processor-specific manuals.
  2645. OCM is On Chip Memory, which I believe the 405GP has 4K. It
  2646. is another option for the system designer to use as an
  2647. initial stack/ram area prior to SDRAM being available. Either
  2648. option should work for you. Using CS 4 should be fine if your
  2649. board designers haven't used it for something that would
  2650. cause you grief during the initial boot! It is frequently not
  2651. used.
  2652. CFG_INIT_RAM_ADDR should be somewhere that won't interfere
  2653. with your processor/board/system design. The default value
  2654. you will find in any recent u-boot distribution in
  2655. walnut.h should work for you. I'd set it to a value larger
  2656. than your SDRAM module. If you have a 64MB SDRAM module, set
  2657. it above 400_0000. Just make sure your board has no resources
  2658. that are supposed to respond to that address! That code in
  2659. start.S has been around a while and should work as is when
  2660. you get the config right.
  2661. -Chris Hallinan
  2662. DS4.COM, Inc.
  2663. It is essential to remember this, since it has some impact on the C
  2664. code for the initialization procedures:
  2665. * Initialized global data (data segment) is read-only. Do not attempt
  2666. to write it.
  2667. * Do not use any unitialized global data (or implicitely initialized
  2668. as zero data - BSS segment) at all - this is undefined, initiali-
  2669. zation is performed later (when relocating to RAM).
  2670. * Stack space is very limited. Avoid big data buffers or things like
  2671. that.
  2672. Having only the stack as writable memory limits means we cannot use
  2673. normal global data to share information beween the code. But it
  2674. turned out that the implementation of U-Boot can be greatly
  2675. simplified by making a global data structure (gd_t) available to all
  2676. functions. We could pass a pointer to this data as argument to _all_
  2677. functions, but this would bloat the code. Instead we use a feature of
  2678. the GCC compiler (Global Register Variables) to share the data: we
  2679. place a pointer (gd) to the global data into a register which we
  2680. reserve for this purpose.
  2681. When choosing a register for such a purpose we are restricted by the
  2682. relevant (E)ABI specifications for the current architecture, and by
  2683. GCC's implementation.
  2684. For PowerPC, the following registers have specific use:
  2685. R1: stack pointer
  2686. R2: reserved for system use
  2687. R3-R4: parameter passing and return values
  2688. R5-R10: parameter passing
  2689. R13: small data area pointer
  2690. R30: GOT pointer
  2691. R31: frame pointer
  2692. (U-Boot also uses R14 as internal GOT pointer.)
  2693. ==> U-Boot will use R2 to hold a pointer to the global data
  2694. Note: on PPC, we could use a static initializer (since the
  2695. address of the global data structure is known at compile time),
  2696. but it turned out that reserving a register results in somewhat
  2697. smaller code - although the code savings are not that big (on
  2698. average for all boards 752 bytes for the whole U-Boot image,
  2699. 624 text + 127 data).
  2700. On Blackfin, the normal C ABI (except for P5) is followed as documented here:
  2701. http://docs.blackfin.uclinux.org/doku.php?id=application_binary_interface
  2702. ==> U-Boot will use P5 to hold a pointer to the global data
  2703. On ARM, the following registers are used:
  2704. R0: function argument word/integer result
  2705. R1-R3: function argument word
  2706. R9: GOT pointer
  2707. R10: stack limit (used only if stack checking if enabled)
  2708. R11: argument (frame) pointer
  2709. R12: temporary workspace
  2710. R13: stack pointer
  2711. R14: link register
  2712. R15: program counter
  2713. ==> U-Boot will use R8 to hold a pointer to the global data
  2714. NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
  2715. or current versions of GCC may "optimize" the code too much.
  2716. Memory Management:
  2717. ------------------
  2718. U-Boot runs in system state and uses physical addresses, i.e. the
  2719. MMU is not used either for address mapping nor for memory protection.
  2720. The available memory is mapped to fixed addresses using the memory
  2721. controller. In this process, a contiguous block is formed for each
  2722. memory type (Flash, SDRAM, SRAM), even when it consists of several
  2723. physical memory banks.
  2724. U-Boot is installed in the first 128 kB of the first Flash bank (on
  2725. TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
  2726. booting and sizing and initializing DRAM, the code relocates itself
  2727. to the upper end of DRAM. Immediately below the U-Boot code some
  2728. memory is reserved for use by malloc() [see CFG_MALLOC_LEN
  2729. configuration setting]. Below that, a structure with global Board
  2730. Info data is placed, followed by the stack (growing downward).
  2731. Additionally, some exception handler code is copied to the low 8 kB
  2732. of DRAM (0x00000000 ... 0x00001FFF).
  2733. So a typical memory configuration with 16 MB of DRAM could look like
  2734. this:
  2735. 0x0000 0000 Exception Vector code
  2736. :
  2737. 0x0000 1FFF
  2738. 0x0000 2000 Free for Application Use
  2739. :
  2740. :
  2741. :
  2742. :
  2743. 0x00FB FF20 Monitor Stack (Growing downward)
  2744. 0x00FB FFAC Board Info Data and permanent copy of global data
  2745. 0x00FC 0000 Malloc Arena
  2746. :
  2747. 0x00FD FFFF
  2748. 0x00FE 0000 RAM Copy of Monitor Code
  2749. ... eventually: LCD or video framebuffer
  2750. ... eventually: pRAM (Protected RAM - unchanged by reset)
  2751. 0x00FF FFFF [End of RAM]
  2752. System Initialization:
  2753. ----------------------
  2754. In the reset configuration, U-Boot starts at the reset entry point
  2755. (on most PowerPC systens at address 0x00000100). Because of the reset
  2756. configuration for CS0# this is a mirror of the onboard Flash memory.
  2757. To be able to re-map memory U-Boot then jumps to its link address.
  2758. To be able to implement the initialization code in C, a (small!)
  2759. initial stack is set up in the internal Dual Ported RAM (in case CPUs
  2760. which provide such a feature like MPC8xx or MPC8260), or in a locked
  2761. part of the data cache. After that, U-Boot initializes the CPU core,
  2762. the caches and the SIU.
  2763. Next, all (potentially) available memory banks are mapped using a
  2764. preliminary mapping. For example, we put them on 512 MB boundaries
  2765. (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
  2766. on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
  2767. programmed for SDRAM access. Using the temporary configuration, a
  2768. simple memory test is run that determines the size of the SDRAM
  2769. banks.
  2770. When there is more than one SDRAM bank, and the banks are of
  2771. different size, the largest is mapped first. For equal size, the first
  2772. bank (CS2#) is mapped first. The first mapping is always for address
  2773. 0x00000000, with any additional banks following immediately to create
  2774. contiguous memory starting from 0.
  2775. Then, the monitor installs itself at the upper end of the SDRAM area
  2776. and allocates memory for use by malloc() and for the global Board
  2777. Info data; also, the exception vector code is copied to the low RAM
  2778. pages, and the final stack is set up.
  2779. Only after this relocation will you have a "normal" C environment;
  2780. until that you are restricted in several ways, mostly because you are
  2781. running from ROM, and because the code will have to be relocated to a
  2782. new address in RAM.
  2783. U-Boot Porting Guide:
  2784. ----------------------
  2785. [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
  2786. list, October 2002]
  2787. int main (int argc, char *argv[])
  2788. {
  2789. sighandler_t no_more_time;
  2790. signal (SIGALRM, no_more_time);
  2791. alarm (PROJECT_DEADLINE - toSec (3 * WEEK));
  2792. if (available_money > available_manpower) {
  2793. pay consultant to port U-Boot;
  2794. return 0;
  2795. }
  2796. Download latest U-Boot source;
  2797. Subscribe to u-boot-users mailing list;
  2798. if (clueless) {
  2799. email ("Hi, I am new to U-Boot, how do I get started?");
  2800. }
  2801. while (learning) {
  2802. Read the README file in the top level directory;
  2803. Read http://www.denx.de/twiki/bin/view/DULG/Manual ;
  2804. Read the source, Luke;
  2805. }
  2806. if (available_money > toLocalCurrency ($2500)) {
  2807. Buy a BDI2000;
  2808. } else {
  2809. Add a lot of aggravation and time;
  2810. }
  2811. Create your own board support subdirectory;
  2812. Create your own board config file;
  2813. while (!running) {
  2814. do {
  2815. Add / modify source code;
  2816. } until (compiles);
  2817. Debug;
  2818. if (clueless)
  2819. email ("Hi, I am having problems...");
  2820. }
  2821. Send patch file to Wolfgang;
  2822. return 0;
  2823. }
  2824. void no_more_time (int sig)
  2825. {
  2826. hire_a_guru();
  2827. }
  2828. Coding Standards:
  2829. -----------------
  2830. All contributions to U-Boot should conform to the Linux kernel
  2831. coding style; see the file "Documentation/CodingStyle" and the script
  2832. "scripts/Lindent" in your Linux kernel source directory. In sources
  2833. originating from U-Boot a style corresponding to "Lindent -pcs" (adding
  2834. spaces before parameters to function calls) is actually used.
  2835. Source files originating from a different project (for example the
  2836. MTD subsystem) are generally exempt from these guidelines and are not
  2837. reformated to ease subsequent migration to newer versions of those
  2838. sources.
  2839. Please note that U-Boot is implemented in C (and to some small parts in
  2840. Assembler); no C++ is used, so please do not use C++ style comments (//)
  2841. in your code.
  2842. Please also stick to the following formatting rules:
  2843. - remove any trailing white space
  2844. - use TAB characters for indentation, not spaces
  2845. - make sure NOT to use DOS '\r\n' line feeds
  2846. - do not add more than 2 empty lines to source files
  2847. - do not add trailing empty lines to source files
  2848. Submissions which do not conform to the standards may be returned
  2849. with a request to reformat the changes.
  2850. Submitting Patches:
  2851. -------------------
  2852. Since the number of patches for U-Boot is growing, we need to
  2853. establish some rules. Submissions which do not conform to these rules
  2854. may be rejected, even when they contain important and valuable stuff.
  2855. Patches shall be sent to the u-boot-users mailing list.
  2856. When you send a patch, please include the following information with
  2857. it:
  2858. * For bug fixes: a description of the bug and how your patch fixes
  2859. this bug. Please try to include a way of demonstrating that the
  2860. patch actually fixes something.
  2861. * For new features: a description of the feature and your
  2862. implementation.
  2863. * A CHANGELOG entry as plaintext (separate from the patch)
  2864. * For major contributions, your entry to the CREDITS file
  2865. * When you add support for a new board, don't forget to add this
  2866. board to the MAKEALL script, too.
  2867. * If your patch adds new configuration options, don't forget to
  2868. document these in the README file.
  2869. * The patch itself. If you are accessing the CVS repository use "cvs
  2870. update; cvs diff -puRN"; else, use "diff -purN OLD NEW". If your
  2871. version of diff does not support these options, then get the latest
  2872. version of GNU diff.
  2873. The current directory when running this command shall be the top
  2874. level directory of the U-Boot source tree, or it's parent directory
  2875. (i. e. please make sure that your patch includes sufficient
  2876. directory information for the affected files).
  2877. We accept patches as plain text, MIME attachments or as uuencoded
  2878. gzipped text.
  2879. * If one logical set of modifications affects or creates several
  2880. files, all these changes shall be submitted in a SINGLE patch file.
  2881. * Changesets that contain different, unrelated modifications shall be
  2882. submitted as SEPARATE patches, one patch per changeset.
  2883. Notes:
  2884. * Before sending the patch, run the MAKEALL script on your patched
  2885. source tree and make sure that no errors or warnings are reported
  2886. for any of the boards.
  2887. * Keep your modifications to the necessary minimum: A patch
  2888. containing several unrelated changes or arbitrary reformats will be
  2889. returned with a request to re-formatting / split it.
  2890. * If you modify existing code, make sure that your new code does not
  2891. add to the memory footprint of the code ;-) Small is beautiful!
  2892. When adding new features, these should compile conditionally only
  2893. (using #ifdef), and the resulting code with the new feature
  2894. disabled must not need more memory than the old code without your
  2895. modification.
  2896. * Remember that there is a size limit of 40 kB per message on the
  2897. u-boot-users mailing list. Compression may help.