README 112 KB

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