README 156 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602160316041605160616071608160916101611161216131614161516161617161816191620162116221623162416251626162716281629163016311632163316341635163616371638163916401641164216431644164516461647164816491650165116521653165416551656165716581659166016611662166316641665166616671668166916701671167216731674167516761677167816791680168116821683168416851686168716881689169016911692169316941695169616971698169917001701170217031704170517061707170817091710171117121713171417151716171717181719172017211722172317241725172617271728172917301731173217331734173517361737173817391740174117421743174417451746174717481749175017511752175317541755175617571758175917601761176217631764176517661767176817691770177117721773177417751776177717781779178017811782178317841785178617871788178917901791179217931794179517961797179817991800180118021803180418051806180718081809181018111812181318141815181618171818181918201821182218231824182518261827182818291830183118321833183418351836183718381839184018411842184318441845184618471848184918501851185218531854185518561857185818591860186118621863186418651866186718681869187018711872187318741875187618771878187918801881188218831884188518861887188818891890189118921893189418951896189718981899190019011902190319041905190619071908190919101911191219131914191519161917191819191920192119221923192419251926192719281929193019311932193319341935193619371938193919401941194219431944194519461947194819491950195119521953195419551956195719581959196019611962196319641965196619671968196919701971197219731974197519761977197819791980198119821983198419851986198719881989199019911992199319941995199619971998199920002001200220032004200520062007200820092010201120122013201420152016201720182019202020212022202320242025202620272028202920302031203220332034203520362037203820392040204120422043204420452046204720482049205020512052205320542055205620572058205920602061206220632064206520662067206820692070207120722073207420752076207720782079208020812082208320842085208620872088208920902091209220932094209520962097209820992100210121022103210421052106210721082109211021112112211321142115211621172118211921202121212221232124212521262127212821292130213121322133213421352136213721382139214021412142214321442145214621472148214921502151215221532154215521562157215821592160216121622163216421652166216721682169217021712172217321742175217621772178217921802181218221832184218521862187218821892190219121922193219421952196219721982199220022012202220322042205220622072208220922102211221222132214221522162217221822192220222122222223222422252226222722282229223022312232223322342235223622372238223922402241224222432244224522462247224822492250225122522253225422552256225722582259226022612262226322642265226622672268226922702271227222732274227522762277227822792280228122822283228422852286228722882289229022912292229322942295229622972298229923002301230223032304230523062307230823092310231123122313231423152316231723182319232023212322232323242325232623272328232923302331233223332334233523362337233823392340234123422343234423452346234723482349235023512352235323542355235623572358235923602361236223632364236523662367236823692370237123722373237423752376237723782379238023812382238323842385238623872388238923902391239223932394239523962397239823992400240124022403240424052406240724082409241024112412241324142415241624172418241924202421242224232424242524262427242824292430243124322433243424352436243724382439244024412442244324442445244624472448244924502451245224532454245524562457245824592460246124622463246424652466246724682469247024712472247324742475247624772478247924802481248224832484248524862487248824892490249124922493249424952496249724982499250025012502250325042505250625072508250925102511251225132514251525162517251825192520252125222523252425252526252725282529253025312532253325342535253625372538253925402541254225432544254525462547254825492550255125522553255425552556255725582559256025612562256325642565256625672568256925702571257225732574257525762577257825792580258125822583258425852586258725882589259025912592259325942595259625972598259926002601260226032604260526062607260826092610261126122613261426152616261726182619262026212622262326242625262626272628262926302631263226332634263526362637263826392640264126422643264426452646264726482649265026512652265326542655265626572658265926602661266226632664266526662667266826692670267126722673267426752676267726782679268026812682268326842685268626872688268926902691269226932694269526962697269826992700270127022703270427052706270727082709271027112712271327142715271627172718271927202721272227232724272527262727272827292730273127322733273427352736273727382739274027412742274327442745274627472748274927502751275227532754275527562757275827592760276127622763276427652766276727682769277027712772277327742775277627772778277927802781278227832784278527862787278827892790279127922793279427952796279727982799280028012802280328042805280628072808280928102811281228132814281528162817281828192820282128222823282428252826282728282829283028312832283328342835283628372838283928402841284228432844284528462847284828492850285128522853285428552856285728582859286028612862286328642865286628672868286928702871287228732874287528762877287828792880288128822883288428852886288728882889289028912892289328942895289628972898289929002901290229032904290529062907290829092910291129122913291429152916291729182919292029212922292329242925292629272928292929302931293229332934293529362937293829392940294129422943294429452946294729482949295029512952295329542955295629572958295929602961296229632964296529662967296829692970297129722973297429752976297729782979298029812982298329842985298629872988298929902991299229932994299529962997299829993000300130023003300430053006300730083009301030113012301330143015301630173018301930203021302230233024302530263027302830293030303130323033303430353036303730383039304030413042304330443045304630473048304930503051305230533054305530563057305830593060306130623063306430653066306730683069307030713072307330743075307630773078307930803081308230833084308530863087308830893090309130923093309430953096309730983099310031013102310331043105310631073108310931103111311231133114311531163117311831193120312131223123312431253126312731283129313031313132313331343135313631373138313931403141314231433144314531463147314831493150315131523153315431553156315731583159316031613162316331643165316631673168316931703171317231733174317531763177317831793180318131823183318431853186318731883189319031913192319331943195319631973198319932003201320232033204320532063207320832093210321132123213321432153216321732183219322032213222322332243225322632273228322932303231323232333234323532363237323832393240324132423243324432453246324732483249325032513252325332543255325632573258325932603261326232633264326532663267326832693270327132723273327432753276327732783279328032813282328332843285328632873288328932903291329232933294329532963297329832993300330133023303330433053306330733083309331033113312331333143315331633173318331933203321332233233324332533263327332833293330333133323333333433353336333733383339334033413342334333443345334633473348334933503351335233533354335533563357335833593360336133623363336433653366336733683369337033713372337333743375337633773378337933803381338233833384338533863387338833893390339133923393339433953396339733983399340034013402340334043405340634073408340934103411341234133414341534163417341834193420342134223423342434253426342734283429343034313432343334343435343634373438343934403441344234433444344534463447344834493450345134523453345434553456345734583459346034613462346334643465346634673468346934703471347234733474347534763477347834793480348134823483348434853486348734883489349034913492349334943495349634973498349935003501350235033504350535063507350835093510351135123513351435153516351735183519352035213522352335243525352635273528352935303531353235333534353535363537353835393540354135423543354435453546354735483549355035513552355335543555355635573558355935603561356235633564356535663567356835693570357135723573357435753576357735783579358035813582358335843585358635873588358935903591359235933594359535963597359835993600360136023603360436053606360736083609361036113612361336143615361636173618361936203621362236233624362536263627362836293630363136323633363436353636363736383639364036413642364336443645364636473648364936503651365236533654365536563657365836593660366136623663366436653666366736683669367036713672367336743675367636773678367936803681368236833684368536863687368836893690369136923693369436953696369736983699370037013702370337043705370637073708370937103711371237133714371537163717371837193720372137223723372437253726372737283729373037313732373337343735373637373738373937403741374237433744374537463747374837493750375137523753375437553756375737583759376037613762376337643765376637673768376937703771377237733774377537763777377837793780378137823783378437853786378737883789379037913792379337943795379637973798379938003801380238033804380538063807380838093810381138123813381438153816381738183819382038213822382338243825382638273828382938303831383238333834383538363837383838393840384138423843384438453846384738483849385038513852385338543855385638573858385938603861386238633864386538663867386838693870387138723873387438753876387738783879388038813882388338843885388638873888388938903891389238933894389538963897389838993900390139023903390439053906390739083909391039113912391339143915391639173918391939203921392239233924392539263927392839293930393139323933393439353936393739383939394039413942394339443945394639473948394939503951395239533954395539563957395839593960396139623963396439653966396739683969397039713972397339743975397639773978397939803981398239833984398539863987398839893990399139923993399439953996399739983999400040014002400340044005400640074008400940104011401240134014401540164017401840194020402140224023402440254026402740284029403040314032403340344035403640374038403940404041404240434044404540464047404840494050405140524053405440554056405740584059406040614062406340644065406640674068406940704071407240734074407540764077407840794080408140824083408440854086408740884089409040914092409340944095409640974098409941004101410241034104410541064107410841094110411141124113411441154116411741184119412041214122412341244125412641274128412941304131413241334134413541364137413841394140414141424143414441454146414741484149415041514152415341544155415641574158415941604161416241634164416541664167416841694170417141724173417441754176417741784179418041814182418341844185418641874188418941904191419241934194419541964197419841994200420142024203420442054206420742084209421042114212421342144215421642174218421942204221422242234224422542264227422842294230423142324233423442354236423742384239424042414242424342444245424642474248424942504251425242534254425542564257425842594260426142624263426442654266426742684269427042714272427342744275427642774278427942804281428242834284428542864287428842894290429142924293429442954296429742984299430043014302430343044305430643074308430943104311431243134314431543164317431843194320432143224323432443254326432743284329433043314332433343344335433643374338433943404341434243434344434543464347434843494350435143524353435443554356435743584359436043614362436343644365436643674368436943704371437243734374437543764377437843794380438143824383438443854386438743884389439043914392439343944395439643974398439944004401440244034404440544064407440844094410441144124413441444154416441744184419442044214422442344244425442644274428442944304431443244334434443544364437443844394440444144424443444444454446444744484449445044514452445344544455445644574458445944604461446244634464446544664467446844694470447144724473447444754476447744784479448044814482448344844485448644874488448944904491449244934494449544964497449844994500450145024503450445054506450745084509451045114512451345144515451645174518451945204521452245234524452545264527452845294530453145324533453445354536453745384539454045414542454345444545454645474548454945504551455245534554455545564557455845594560456145624563456445654566456745684569457045714572457345744575457645774578457945804581
  1. #
  2. # (C) Copyright 2000 - 2011
  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. The MAINTAINERS file lists board
  47. maintainers.
  48. Where to get help:
  49. ==================
  50. In case you have questions about, problems with or contributions for
  51. U-Boot you should send a message to the U-Boot mailing list at
  52. <u-boot@lists.denx.de>. There is also an archive of previous traffic
  53. on the mailing list - please search the archive before asking FAQ's.
  54. Please see http://lists.denx.de/pipermail/u-boot and
  55. http://dir.gmane.org/gmane.comp.boot-loaders.u-boot
  56. Where to get source code:
  57. =========================
  58. The U-Boot source code is maintained in the git repository at
  59. git://www.denx.de/git/u-boot.git ; you can browse it online at
  60. http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary
  61. The "snapshot" links on this page allow you to download tarballs of
  62. any version you might be interested in. Official releases are also
  63. available for FTP download from the ftp://ftp.denx.de/pub/u-boot/
  64. directory.
  65. Pre-built (and tested) images are available from
  66. ftp://ftp.denx.de/pub/u-boot/images/
  67. Where we come from:
  68. ===================
  69. - start from 8xxrom sources
  70. - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
  71. - clean up code
  72. - make it easier to add custom boards
  73. - make it possible to add other [PowerPC] CPUs
  74. - extend functions, especially:
  75. * Provide extended interface to Linux boot loader
  76. * S-Record download
  77. * network boot
  78. * PCMCIA / CompactFlash / ATA disk / SCSI ... boot
  79. - create ARMBoot project (http://sourceforge.net/projects/armboot)
  80. - add other CPU families (starting with ARM)
  81. - create U-Boot project (http://sourceforge.net/projects/u-boot)
  82. - current project page: see http://www.denx.de/wiki/U-Boot
  83. Names and Spelling:
  84. ===================
  85. The "official" name of this project is "Das U-Boot". The spelling
  86. "U-Boot" shall be used in all written text (documentation, comments
  87. in source files etc.). Example:
  88. This is the README file for the U-Boot project.
  89. File names etc. shall be based on the string "u-boot". Examples:
  90. include/asm-ppc/u-boot.h
  91. #include <asm/u-boot.h>
  92. Variable names, preprocessor constants etc. shall be either based on
  93. the string "u_boot" or on "U_BOOT". Example:
  94. U_BOOT_VERSION u_boot_logo
  95. IH_OS_U_BOOT u_boot_hush_start
  96. Versioning:
  97. ===========
  98. Starting with the release in October 2008, the names of the releases
  99. were changed from numerical release numbers without deeper meaning
  100. into a time stamp based numbering. Regular releases are identified by
  101. names consisting of the calendar year and month of the release date.
  102. Additional fields (if present) indicate release candidates or bug fix
  103. releases in "stable" maintenance trees.
  104. Examples:
  105. U-Boot v2009.11 - Release November 2009
  106. U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree
  107. U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release
  108. Directory Hierarchy:
  109. ====================
  110. /arch Architecture specific files
  111. /arm Files generic to ARM architecture
  112. /cpu CPU specific files
  113. /arm720t Files specific to ARM 720 CPUs
  114. /arm920t Files specific to ARM 920 CPUs
  115. /at91rm9200 Files specific to Atmel AT91RM9200 CPU
  116. /imx Files specific to Freescale MC9328 i.MX CPUs
  117. /s3c24x0 Files specific to Samsung S3C24X0 CPUs
  118. /arm925t Files specific to ARM 925 CPUs
  119. /arm926ejs Files specific to ARM 926 CPUs
  120. /arm1136 Files specific to ARM 1136 CPUs
  121. /ixp Files specific to Intel XScale IXP CPUs
  122. /pxa Files specific to Intel XScale PXA CPUs
  123. /s3c44b0 Files specific to Samsung S3C44B0 CPUs
  124. /sa1100 Files specific to Intel StrongARM SA1100 CPUs
  125. /lib Architecture specific library files
  126. /avr32 Files generic to AVR32 architecture
  127. /cpu CPU specific files
  128. /lib Architecture specific library files
  129. /blackfin Files generic to Analog Devices Blackfin architecture
  130. /cpu CPU specific files
  131. /lib Architecture specific library files
  132. /x86 Files generic to x86 architecture
  133. /cpu CPU specific files
  134. /lib Architecture specific library files
  135. /m68k Files generic to m68k architecture
  136. /cpu CPU specific files
  137. /mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
  138. /mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs
  139. /mcf532x Files specific to Freescale ColdFire MCF5329 CPUs
  140. /mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs
  141. /mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs
  142. /lib Architecture specific library files
  143. /microblaze Files generic to microblaze architecture
  144. /cpu CPU specific files
  145. /lib Architecture specific library files
  146. /mips Files generic to MIPS architecture
  147. /cpu CPU specific files
  148. /lib Architecture specific library files
  149. /nios2 Files generic to Altera NIOS2 architecture
  150. /cpu CPU specific files
  151. /lib Architecture specific library files
  152. /powerpc Files generic to PowerPC architecture
  153. /cpu CPU specific files
  154. /74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
  155. /mpc5xx Files specific to Freescale MPC5xx CPUs
  156. /mpc5xxx Files specific to Freescale MPC5xxx CPUs
  157. /mpc8xx Files specific to Freescale MPC8xx CPUs
  158. /mpc8220 Files specific to Freescale MPC8220 CPUs
  159. /mpc824x Files specific to Freescale MPC824x CPUs
  160. /mpc8260 Files specific to Freescale MPC8260 CPUs
  161. /mpc85xx Files specific to Freescale MPC85xx CPUs
  162. /ppc4xx Files specific to AMCC PowerPC 4xx CPUs
  163. /lib Architecture specific library files
  164. /sh Files generic to SH architecture
  165. /cpu CPU specific files
  166. /sh2 Files specific to sh2 CPUs
  167. /sh3 Files specific to sh3 CPUs
  168. /sh4 Files specific to sh4 CPUs
  169. /lib Architecture specific library files
  170. /sparc Files generic to SPARC architecture
  171. /cpu CPU specific files
  172. /leon2 Files specific to Gaisler LEON2 SPARC CPU
  173. /leon3 Files specific to Gaisler LEON3 SPARC CPU
  174. /lib Architecture specific library files
  175. /api Machine/arch independent API for external apps
  176. /board Board dependent files
  177. /common Misc architecture independent functions
  178. /disk Code for disk drive partition handling
  179. /doc Documentation (don't expect too much)
  180. /drivers Commonly used device drivers
  181. /examples Example code for standalone applications, etc.
  182. /fs Filesystem code (cramfs, ext2, jffs2, etc.)
  183. /include Header Files
  184. /lib Files generic to all architectures
  185. /libfdt Library files to support flattened device trees
  186. /lzma Library files to support LZMA decompression
  187. /lzo Library files to support LZO decompression
  188. /net Networking code
  189. /post Power On Self Test
  190. /rtc Real Time Clock drivers
  191. /tools Tools to build S-Record or U-Boot images, etc.
  192. Software Configuration:
  193. =======================
  194. Configuration is usually done using C preprocessor defines; the
  195. rationale behind that is to avoid dead code whenever possible.
  196. There are two classes of configuration variables:
  197. * Configuration _OPTIONS_:
  198. These are selectable by the user and have names beginning with
  199. "CONFIG_".
  200. * Configuration _SETTINGS_:
  201. These depend on the hardware etc. and should not be meddled with if
  202. you don't know what you're doing; they have names beginning with
  203. "CONFIG_SYS_".
  204. Later we will add a configuration tool - probably similar to or even
  205. identical to what's used for the Linux kernel. Right now, we have to
  206. do the configuration by hand, which means creating some symbolic
  207. links and editing some configuration files. We use the TQM8xxL boards
  208. as an example here.
  209. Selection of Processor Architecture and Board Type:
  210. ---------------------------------------------------
  211. For all supported boards there are ready-to-use default
  212. configurations available; just type "make <board_name>_config".
  213. Example: For a TQM823L module type:
  214. cd u-boot
  215. make TQM823L_config
  216. For the Cogent platform, you need to specify the CPU type as well;
  217. e.g. "make cogent_mpc8xx_config". And also configure the cogent
  218. directory according to the instructions in cogent/README.
  219. Configuration Options:
  220. ----------------------
  221. Configuration depends on the combination of board and CPU type; all
  222. such information is kept in a configuration file
  223. "include/configs/<board_name>.h".
  224. Example: For a TQM823L module, all configuration settings are in
  225. "include/configs/TQM823L.h".
  226. Many of the options are named exactly as the corresponding Linux
  227. kernel configuration options. The intention is to make it easier to
  228. build a config tool - later.
  229. The following options need to be configured:
  230. - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
  231. - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
  232. - CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)
  233. Define exactly one, e.g. CONFIG_ATSTK1002
  234. - CPU Module Type: (if CONFIG_COGENT is defined)
  235. Define exactly one of
  236. CONFIG_CMA286_60_OLD
  237. --- FIXME --- not tested yet:
  238. CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
  239. CONFIG_CMA287_23, CONFIG_CMA287_50
  240. - Motherboard Type: (if CONFIG_COGENT is defined)
  241. Define exactly one of
  242. CONFIG_CMA101, CONFIG_CMA102
  243. - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
  244. Define one or more of
  245. CONFIG_CMA302
  246. - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
  247. Define one or more of
  248. CONFIG_LCD_HEARTBEAT - update a character position on
  249. the LCD display every second with
  250. a "rotator" |\-/|\-/
  251. - Board flavour: (if CONFIG_MPC8260ADS is defined)
  252. CONFIG_ADSTYPE
  253. Possible values are:
  254. CONFIG_SYS_8260ADS - original MPC8260ADS
  255. CONFIG_SYS_8266ADS - MPC8266ADS
  256. CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
  257. CONFIG_SYS_8272ADS - MPC8272ADS
  258. - Marvell Family Member
  259. CONFIG_SYS_MVFS - define it if you want to enable
  260. multiple fs option at one time
  261. for marvell soc family
  262. - MPC824X Family Member (if CONFIG_MPC824X is defined)
  263. Define exactly one of
  264. CONFIG_MPC8240, CONFIG_MPC8245
  265. - 8xx CPU Options: (if using an MPC8xx CPU)
  266. CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
  267. get_gclk_freq() cannot work
  268. e.g. if there is no 32KHz
  269. reference PIT/RTC clock
  270. CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
  271. or XTAL/EXTAL)
  272. - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
  273. CONFIG_SYS_8xx_CPUCLK_MIN
  274. CONFIG_SYS_8xx_CPUCLK_MAX
  275. CONFIG_8xx_CPUCLK_DEFAULT
  276. See doc/README.MPC866
  277. CONFIG_SYS_MEASURE_CPUCLK
  278. Define this to measure the actual CPU clock instead
  279. of relying on the correctness of the configured
  280. values. Mostly useful for board bringup to make sure
  281. the PLL is locked at the intended frequency. Note
  282. that this requires a (stable) reference clock (32 kHz
  283. RTC clock or CONFIG_SYS_8XX_XIN)
  284. CONFIG_SYS_DELAYED_ICACHE
  285. Define this option if you want to enable the
  286. ICache only when Code runs from RAM.
  287. - 85xx CPU Options:
  288. CONFIG_SYS_FSL_TBCLK_DIV
  289. Defines the core time base clock divider ratio compared to the
  290. system clock. On most PQ3 devices this is 8, on newer QorIQ
  291. devices it can be 16 or 32. The ratio varies from SoC to Soc.
  292. CONFIG_SYS_FSL_PCIE_COMPAT
  293. Defines the string to utilize when trying to match PCIe device
  294. tree nodes for the given platform.
  295. - Intel Monahans options:
  296. CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO
  297. Defines the Monahans run mode to oscillator
  298. ratio. Valid values are 8, 16, 24, 31. The core
  299. frequency is this value multiplied by 13 MHz.
  300. CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO
  301. Defines the Monahans turbo mode to oscillator
  302. ratio. Valid values are 1 (default if undefined) and
  303. 2. The core frequency as calculated above is multiplied
  304. by this value.
  305. - Linux Kernel Interface:
  306. CONFIG_CLOCKS_IN_MHZ
  307. U-Boot stores all clock information in Hz
  308. internally. For binary compatibility with older Linux
  309. kernels (which expect the clocks passed in the
  310. bd_info data to be in MHz) the environment variable
  311. "clocks_in_mhz" can be defined so that U-Boot
  312. converts clock data to MHZ before passing it to the
  313. Linux kernel.
  314. When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
  315. "clocks_in_mhz=1" is automatically included in the
  316. default environment.
  317. CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
  318. When transferring memsize parameter to linux, some versions
  319. expect it to be in bytes, others in MB.
  320. Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
  321. CONFIG_OF_LIBFDT
  322. New kernel versions are expecting firmware settings to be
  323. passed using flattened device trees (based on open firmware
  324. concepts).
  325. CONFIG_OF_LIBFDT
  326. * New libfdt-based support
  327. * Adds the "fdt" command
  328. * The bootm command automatically updates the fdt
  329. OF_CPU - The proper name of the cpus node (only required for
  330. MPC512X and MPC5xxx based boards).
  331. OF_SOC - The proper name of the soc node (only required for
  332. MPC512X and MPC5xxx based boards).
  333. OF_TBCLK - The timebase frequency.
  334. OF_STDOUT_PATH - The path to the console device
  335. boards with QUICC Engines require OF_QE to set UCC MAC
  336. addresses
  337. CONFIG_OF_BOARD_SETUP
  338. Board code has addition modification that it wants to make
  339. to the flat device tree before handing it off to the kernel
  340. CONFIG_OF_BOOT_CPU
  341. This define fills in the correct boot CPU in the boot
  342. param header, the default value is zero if undefined.
  343. CONFIG_OF_IDE_FIXUP
  344. U-Boot can detect if an IDE device is present or not.
  345. If not, and this new config option is activated, U-Boot
  346. removes the ATA node from the DTS before booting Linux,
  347. so the Linux IDE driver does not probe the device and
  348. crash. This is needed for buggy hardware (uc101) where
  349. no pull down resistor is connected to the signal IDE5V_DD7.
  350. CONFIG_MACH_TYPE [relevant for ARM only][mandatory]
  351. This setting is mandatory for all boards that have only one
  352. machine type and must be used to specify the machine type
  353. number as it appears in the ARM machine registry
  354. (see http://www.arm.linux.org.uk/developer/machines/).
  355. Only boards that have multiple machine types supported
  356. in a single configuration file and the machine type is
  357. runtime discoverable, do not have to use this setting.
  358. - vxWorks boot parameters:
  359. bootvx constructs a valid bootline using the following
  360. environments variables: bootfile, ipaddr, serverip, hostname.
  361. It loads the vxWorks image pointed bootfile.
  362. CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name
  363. CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address
  364. CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server
  365. CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters
  366. CONFIG_SYS_VXWORKS_ADD_PARAMS
  367. Add it at the end of the bootline. E.g "u=username pw=secret"
  368. Note: If a "bootargs" environment is defined, it will overwride
  369. the defaults discussed just above.
  370. - Cache Configuration:
  371. CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot
  372. CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot
  373. CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
  374. - Cache Configuration for ARM:
  375. CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache
  376. controller
  377. CONFIG_SYS_PL310_BASE - Physical base address of PL310
  378. controller register space
  379. - Serial Ports:
  380. CONFIG_PL010_SERIAL
  381. Define this if you want support for Amba PrimeCell PL010 UARTs.
  382. CONFIG_PL011_SERIAL
  383. Define this if you want support for Amba PrimeCell PL011 UARTs.
  384. CONFIG_PL011_CLOCK
  385. If you have Amba PrimeCell PL011 UARTs, set this variable to
  386. the clock speed of the UARTs.
  387. CONFIG_PL01x_PORTS
  388. If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
  389. define this to a list of base addresses for each (supported)
  390. port. See e.g. include/configs/versatile.h
  391. CONFIG_PL011_SERIAL_RLCR
  392. Some vendor versions of PL011 serial ports (e.g. ST-Ericsson U8500)
  393. have separate receive and transmit line control registers. Set
  394. this variable to initialize the extra register.
  395. CONFIG_PL011_SERIAL_FLUSH_ON_INIT
  396. On some platforms (e.g. U8500) U-Boot is loaded by a second stage
  397. boot loader that has already initialized the UART. Define this
  398. variable to flush the UART at init time.
  399. - Console Interface:
  400. Depending on board, define exactly one serial port
  401. (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
  402. CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
  403. console by defining CONFIG_8xx_CONS_NONE
  404. Note: if CONFIG_8xx_CONS_NONE is defined, the serial
  405. port routines must be defined elsewhere
  406. (i.e. serial_init(), serial_getc(), ...)
  407. CONFIG_CFB_CONSOLE
  408. Enables console device for a color framebuffer. Needs following
  409. defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
  410. VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
  411. (default big endian)
  412. VIDEO_HW_RECTFILL graphic chip supports
  413. rectangle fill
  414. (cf. smiLynxEM)
  415. VIDEO_HW_BITBLT graphic chip supports
  416. bit-blit (cf. smiLynxEM)
  417. VIDEO_VISIBLE_COLS visible pixel columns
  418. (cols=pitch)
  419. VIDEO_VISIBLE_ROWS visible pixel rows
  420. VIDEO_PIXEL_SIZE bytes per pixel
  421. VIDEO_DATA_FORMAT graphic data format
  422. (0-5, cf. cfb_console.c)
  423. VIDEO_FB_ADRS framebuffer address
  424. VIDEO_KBD_INIT_FCT keyboard int fct
  425. (i.e. i8042_kbd_init())
  426. VIDEO_TSTC_FCT test char fct
  427. (i.e. i8042_tstc)
  428. VIDEO_GETC_FCT get char fct
  429. (i.e. i8042_getc)
  430. CONFIG_CONSOLE_CURSOR cursor drawing on/off
  431. (requires blink timer
  432. cf. i8042.c)
  433. CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
  434. CONFIG_CONSOLE_TIME display time/date info in
  435. upper right corner
  436. (requires CONFIG_CMD_DATE)
  437. CONFIG_VIDEO_LOGO display Linux logo in
  438. upper left corner
  439. CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
  440. linux_logo.h for logo.
  441. Requires CONFIG_VIDEO_LOGO
  442. CONFIG_CONSOLE_EXTRA_INFO
  443. additional board info beside
  444. the logo
  445. When CONFIG_CFB_CONSOLE is defined, video console is
  446. default i/o. Serial console can be forced with
  447. environment 'console=serial'.
  448. When CONFIG_SILENT_CONSOLE is defined, all console
  449. messages (by U-Boot and Linux!) can be silenced with
  450. the "silent" environment variable. See
  451. doc/README.silent for more information.
  452. - Console Baudrate:
  453. CONFIG_BAUDRATE - in bps
  454. Select one of the baudrates listed in
  455. CONFIG_SYS_BAUDRATE_TABLE, see below.
  456. CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale
  457. - Console Rx buffer length
  458. With CONFIG_SYS_SMC_RXBUFLEN it is possible to define
  459. the maximum receive buffer length for the SMC.
  460. This option is actual only for 82xx and 8xx possible.
  461. If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE
  462. must be defined, to setup the maximum idle timeout for
  463. the SMC.
  464. - Boot Delay: CONFIG_BOOTDELAY - in seconds
  465. Delay before automatically booting the default image;
  466. set to -1 to disable autoboot.
  467. See doc/README.autoboot for these options that
  468. work with CONFIG_BOOTDELAY. None are required.
  469. CONFIG_BOOT_RETRY_TIME
  470. CONFIG_BOOT_RETRY_MIN
  471. CONFIG_AUTOBOOT_KEYED
  472. CONFIG_AUTOBOOT_PROMPT
  473. CONFIG_AUTOBOOT_DELAY_STR
  474. CONFIG_AUTOBOOT_STOP_STR
  475. CONFIG_AUTOBOOT_DELAY_STR2
  476. CONFIG_AUTOBOOT_STOP_STR2
  477. CONFIG_ZERO_BOOTDELAY_CHECK
  478. CONFIG_RESET_TO_RETRY
  479. - Autoboot Command:
  480. CONFIG_BOOTCOMMAND
  481. Only needed when CONFIG_BOOTDELAY is enabled;
  482. define a command string that is automatically executed
  483. when no character is read on the console interface
  484. within "Boot Delay" after reset.
  485. CONFIG_BOOTARGS
  486. This can be used to pass arguments to the bootm
  487. command. The value of CONFIG_BOOTARGS goes into the
  488. environment value "bootargs".
  489. CONFIG_RAMBOOT and CONFIG_NFSBOOT
  490. The value of these goes into the environment as
  491. "ramboot" and "nfsboot" respectively, and can be used
  492. as a convenience, when switching between booting from
  493. RAM and NFS.
  494. - Pre-Boot Commands:
  495. CONFIG_PREBOOT
  496. When this option is #defined, the existence of the
  497. environment variable "preboot" will be checked
  498. immediately before starting the CONFIG_BOOTDELAY
  499. countdown and/or running the auto-boot command resp.
  500. entering interactive mode.
  501. This feature is especially useful when "preboot" is
  502. automatically generated or modified. For an example
  503. see the LWMON board specific code: here "preboot" is
  504. modified when the user holds down a certain
  505. combination of keys on the (special) keyboard when
  506. booting the systems
  507. - Serial Download Echo Mode:
  508. CONFIG_LOADS_ECHO
  509. If defined to 1, all characters received during a
  510. serial download (using the "loads" command) are
  511. echoed back. This might be needed by some terminal
  512. emulations (like "cu"), but may as well just take
  513. time on others. This setting #define's the initial
  514. value of the "loads_echo" environment variable.
  515. - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
  516. CONFIG_KGDB_BAUDRATE
  517. Select one of the baudrates listed in
  518. CONFIG_SYS_BAUDRATE_TABLE, see below.
  519. - Monitor Functions:
  520. Monitor commands can be included or excluded
  521. from the build by using the #include files
  522. "config_cmd_all.h" and #undef'ing unwanted
  523. commands, or using "config_cmd_default.h"
  524. and augmenting with additional #define's
  525. for wanted commands.
  526. The default command configuration includes all commands
  527. except those marked below with a "*".
  528. CONFIG_CMD_ASKENV * ask for env variable
  529. CONFIG_CMD_BDI bdinfo
  530. CONFIG_CMD_BEDBUG * Include BedBug Debugger
  531. CONFIG_CMD_BMP * BMP support
  532. CONFIG_CMD_BSP * Board specific commands
  533. CONFIG_CMD_BOOTD bootd
  534. CONFIG_CMD_CACHE * icache, dcache
  535. CONFIG_CMD_CONSOLE coninfo
  536. CONFIG_CMD_CRC32 * crc32
  537. CONFIG_CMD_DATE * support for RTC, date/time...
  538. CONFIG_CMD_DHCP * DHCP support
  539. CONFIG_CMD_DIAG * Diagnostics
  540. CONFIG_CMD_DS4510 * ds4510 I2C gpio commands
  541. CONFIG_CMD_DS4510_INFO * ds4510 I2C info command
  542. CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd
  543. CONFIG_CMD_DS4510_RST * ds4510 I2C rst command
  544. CONFIG_CMD_DTT * Digital Therm and Thermostat
  545. CONFIG_CMD_ECHO echo arguments
  546. CONFIG_CMD_EDITENV edit env variable
  547. CONFIG_CMD_EEPROM * EEPROM read/write support
  548. CONFIG_CMD_ELF * bootelf, bootvx
  549. CONFIG_CMD_EXPORTENV * export the environment
  550. CONFIG_CMD_SAVEENV saveenv
  551. CONFIG_CMD_FDC * Floppy Disk Support
  552. CONFIG_CMD_FAT * FAT partition support
  553. CONFIG_CMD_FDOS * Dos diskette Support
  554. CONFIG_CMD_FLASH flinfo, erase, protect
  555. CONFIG_CMD_FPGA FPGA device initialization support
  556. CONFIG_CMD_GO * the 'go' command (exec code)
  557. CONFIG_CMD_GREPENV * search environment
  558. CONFIG_CMD_HWFLOW * RTS/CTS hw flow control
  559. CONFIG_CMD_I2C * I2C serial bus support
  560. CONFIG_CMD_IDE * IDE harddisk support
  561. CONFIG_CMD_IMI iminfo
  562. CONFIG_CMD_IMLS List all found images
  563. CONFIG_CMD_IMMAP * IMMR dump support
  564. CONFIG_CMD_IMPORTENV * import an environment
  565. CONFIG_CMD_IRQ * irqinfo
  566. CONFIG_CMD_ITEST Integer/string test of 2 values
  567. CONFIG_CMD_JFFS2 * JFFS2 Support
  568. CONFIG_CMD_KGDB * kgdb
  569. CONFIG_CMD_LDRINFO ldrinfo (display Blackfin loader)
  570. CONFIG_CMD_LOADB loadb
  571. CONFIG_CMD_LOADS loads
  572. CONFIG_CMD_MD5SUM print md5 message digest
  573. (requires CONFIG_CMD_MEMORY and CONFIG_MD5)
  574. CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
  575. loop, loopw, mtest
  576. CONFIG_CMD_MISC Misc functions like sleep etc
  577. CONFIG_CMD_MMC * MMC memory mapped support
  578. CONFIG_CMD_MII * MII utility commands
  579. CONFIG_CMD_MTDPARTS * MTD partition support
  580. CONFIG_CMD_NAND * NAND support
  581. CONFIG_CMD_NET bootp, tftpboot, rarpboot
  582. CONFIG_CMD_PCA953X * PCA953x I2C gpio commands
  583. CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command
  584. CONFIG_CMD_PCI * pciinfo
  585. CONFIG_CMD_PCMCIA * PCMCIA support
  586. CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network
  587. host
  588. CONFIG_CMD_PORTIO * Port I/O
  589. CONFIG_CMD_REGINFO * Register dump
  590. CONFIG_CMD_RUN run command in env variable
  591. CONFIG_CMD_SAVES * save S record dump
  592. CONFIG_CMD_SCSI * SCSI Support
  593. CONFIG_CMD_SDRAM * print SDRAM configuration information
  594. (requires CONFIG_CMD_I2C)
  595. CONFIG_CMD_SETGETDCR Support for DCR Register access
  596. (4xx only)
  597. CONFIG_CMD_SHA1SUM print sha1 memory digest
  598. (requires CONFIG_CMD_MEMORY)
  599. CONFIG_CMD_SOURCE "source" command Support
  600. CONFIG_CMD_SPI * SPI serial bus support
  601. CONFIG_CMD_TFTPSRV * TFTP transfer in server mode
  602. CONFIG_CMD_USB * USB support
  603. CONFIG_CMD_CDP * Cisco Discover Protocol support
  604. CONFIG_CMD_FSL * Microblaze FSL support
  605. EXAMPLE: If you want all functions except of network
  606. support you can write:
  607. #include "config_cmd_all.h"
  608. #undef CONFIG_CMD_NET
  609. Other Commands:
  610. fdt (flattened device tree) command: CONFIG_OF_LIBFDT
  611. Note: Don't enable the "icache" and "dcache" commands
  612. (configuration option CONFIG_CMD_CACHE) unless you know
  613. what you (and your U-Boot users) are doing. Data
  614. cache cannot be enabled on systems like the 8xx or
  615. 8260 (where accesses to the IMMR region must be
  616. uncached), and it cannot be disabled on all other
  617. systems where we (mis-) use the data cache to hold an
  618. initial stack and some data.
  619. XXX - this list needs to get updated!
  620. - Watchdog:
  621. CONFIG_WATCHDOG
  622. If this variable is defined, it enables watchdog
  623. support for the SoC. There must be support in the SoC
  624. specific code for a watchdog. For the 8xx and 8260
  625. CPUs, the SIU Watchdog feature is enabled in the SYPCR
  626. register. When supported for a specific SoC is
  627. available, then no further board specific code should
  628. be needed to use it.
  629. CONFIG_HW_WATCHDOG
  630. When using a watchdog circuitry external to the used
  631. SoC, then define this variable and provide board
  632. specific code for the "hw_watchdog_reset" function.
  633. - U-Boot Version:
  634. CONFIG_VERSION_VARIABLE
  635. If this variable is defined, an environment variable
  636. named "ver" is created by U-Boot showing the U-Boot
  637. version as printed by the "version" command.
  638. This variable is readonly.
  639. - Real-Time Clock:
  640. When CONFIG_CMD_DATE is selected, the type of the RTC
  641. has to be selected, too. Define exactly one of the
  642. following options:
  643. CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
  644. CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
  645. CONFIG_RTC_MC13783 - use MC13783 RTC
  646. CONFIG_RTC_MC146818 - use MC146818 RTC
  647. CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
  648. CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
  649. CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
  650. CONFIG_RTC_DS164x - use Dallas DS164x RTC
  651. CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
  652. CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
  653. CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337
  654. CONFIG_SYS_RV3029_TCR - enable trickle charger on
  655. RV3029 RTC.
  656. Note that if the RTC uses I2C, then the I2C interface
  657. must also be configured. See I2C Support, below.
  658. - GPIO Support:
  659. CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO
  660. CONFIG_PCA953X_INFO - enable pca953x info command
  661. The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
  662. chip-ngpio pairs that tell the PCA953X driver the number of
  663. pins supported by a particular chip.
  664. Note that if the GPIO device uses I2C, then the I2C interface
  665. must also be configured. See I2C Support, below.
  666. - Timestamp Support:
  667. When CONFIG_TIMESTAMP is selected, the timestamp
  668. (date and time) of an image is printed by image
  669. commands like bootm or iminfo. This option is
  670. automatically enabled when you select CONFIG_CMD_DATE .
  671. - Partition Support:
  672. CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
  673. and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION
  674. If IDE or SCSI support is enabled (CONFIG_CMD_IDE or
  675. CONFIG_CMD_SCSI) you must configure support for at
  676. least one partition type as well.
  677. - IDE Reset method:
  678. CONFIG_IDE_RESET_ROUTINE - this is defined in several
  679. board configurations files but used nowhere!
  680. CONFIG_IDE_RESET - is this is defined, IDE Reset will
  681. be performed by calling the function
  682. ide_set_reset(int reset)
  683. which has to be defined in a board specific file
  684. - ATAPI Support:
  685. CONFIG_ATAPI
  686. Set this to enable ATAPI support.
  687. - LBA48 Support
  688. CONFIG_LBA48
  689. Set this to enable support for disks larger than 137GB
  690. Also look at CONFIG_SYS_64BIT_LBA.
  691. Whithout these , LBA48 support uses 32bit variables and will 'only'
  692. support disks up to 2.1TB.
  693. CONFIG_SYS_64BIT_LBA:
  694. When enabled, makes the IDE subsystem use 64bit sector addresses.
  695. Default is 32bit.
  696. - SCSI Support:
  697. At the moment only there is only support for the
  698. SYM53C8XX SCSI controller; define
  699. CONFIG_SCSI_SYM53C8XX to enable it.
  700. CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
  701. CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
  702. CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
  703. maximum numbers of LUNs, SCSI ID's and target
  704. devices.
  705. CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
  706. - NETWORK Support (PCI):
  707. CONFIG_E1000
  708. Support for Intel 8254x gigabit chips.
  709. CONFIG_E1000_FALLBACK_MAC
  710. default MAC for empty EEPROM after production.
  711. CONFIG_EEPRO100
  712. Support for Intel 82557/82559/82559ER chips.
  713. Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM
  714. write routine for first time initialisation.
  715. CONFIG_TULIP
  716. Support for Digital 2114x chips.
  717. Optional CONFIG_TULIP_SELECT_MEDIA for board specific
  718. modem chip initialisation (KS8761/QS6611).
  719. CONFIG_NATSEMI
  720. Support for National dp83815 chips.
  721. CONFIG_NS8382X
  722. Support for National dp8382[01] gigabit chips.
  723. - NETWORK Support (other):
  724. CONFIG_DRIVER_AT91EMAC
  725. Support for AT91RM9200 EMAC.
  726. CONFIG_RMII
  727. Define this to use reduced MII inteface
  728. CONFIG_DRIVER_AT91EMAC_QUIET
  729. If this defined, the driver is quiet.
  730. The driver doen't show link status messages.
  731. CONFIG_DRIVER_LAN91C96
  732. Support for SMSC's LAN91C96 chips.
  733. CONFIG_LAN91C96_BASE
  734. Define this to hold the physical address
  735. of the LAN91C96's I/O space
  736. CONFIG_LAN91C96_USE_32_BIT
  737. Define this to enable 32 bit addressing
  738. CONFIG_DRIVER_SMC91111
  739. Support for SMSC's LAN91C111 chip
  740. CONFIG_SMC91111_BASE
  741. Define this to hold the physical address
  742. of the device (I/O space)
  743. CONFIG_SMC_USE_32_BIT
  744. Define this if data bus is 32 bits
  745. CONFIG_SMC_USE_IOFUNCS
  746. Define this to use i/o functions instead of macros
  747. (some hardware wont work with macros)
  748. CONFIG_FTGMAC100
  749. Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
  750. CONFIG_FTGMAC100_EGIGA
  751. Define this to use GE link update with gigabit PHY.
  752. Define this if FTGMAC100 is connected to gigabit PHY.
  753. If your system has 10/100 PHY only, it might not occur
  754. wrong behavior. Because PHY usually return timeout or
  755. useless data when polling gigabit status and gigabit
  756. control registers. This behavior won't affect the
  757. correctnessof 10/100 link speed update.
  758. CONFIG_SMC911X
  759. Support for SMSC's LAN911x and LAN921x chips
  760. CONFIG_SMC911X_BASE
  761. Define this to hold the physical address
  762. of the device (I/O space)
  763. CONFIG_SMC911X_32_BIT
  764. Define this if data bus is 32 bits
  765. CONFIG_SMC911X_16_BIT
  766. Define this if data bus is 16 bits. If your processor
  767. automatically converts one 32 bit word to two 16 bit
  768. words you may also try CONFIG_SMC911X_32_BIT.
  769. CONFIG_SH_ETHER
  770. Support for Renesas on-chip Ethernet controller
  771. CONFIG_SH_ETHER_USE_PORT
  772. Define the number of ports to be used
  773. CONFIG_SH_ETHER_PHY_ADDR
  774. Define the ETH PHY's address
  775. CONFIG_SH_ETHER_CACHE_WRITEBACK
  776. If this option is set, the driver enables cache flush.
  777. - USB Support:
  778. At the moment only the UHCI host controller is
  779. supported (PIP405, MIP405, MPC5200); define
  780. CONFIG_USB_UHCI to enable it.
  781. define CONFIG_USB_KEYBOARD to enable the USB Keyboard
  782. and define CONFIG_USB_STORAGE to enable the USB
  783. storage devices.
  784. Note:
  785. Supported are USB Keyboards and USB Floppy drives
  786. (TEAC FD-05PUB).
  787. MPC5200 USB requires additional defines:
  788. CONFIG_USB_CLOCK
  789. for 528 MHz Clock: 0x0001bbbb
  790. CONFIG_PSC3_USB
  791. for USB on PSC3
  792. CONFIG_USB_CONFIG
  793. for differential drivers: 0x00001000
  794. for single ended drivers: 0x00005000
  795. for differential drivers on PSC3: 0x00000100
  796. for single ended drivers on PSC3: 0x00004100
  797. CONFIG_SYS_USB_EVENT_POLL
  798. May be defined to allow interrupt polling
  799. instead of using asynchronous interrupts
  800. - USB Device:
  801. Define the below if you wish to use the USB console.
  802. Once firmware is rebuilt from a serial console issue the
  803. command "setenv stdin usbtty; setenv stdout usbtty" and
  804. attach your USB cable. The Unix command "dmesg" should print
  805. it has found a new device. The environment variable usbtty
  806. can be set to gserial or cdc_acm to enable your device to
  807. appear to a USB host as a Linux gserial device or a
  808. Common Device Class Abstract Control Model serial device.
  809. If you select usbtty = gserial you should be able to enumerate
  810. a Linux host by
  811. # modprobe usbserial vendor=0xVendorID product=0xProductID
  812. else if using cdc_acm, simply setting the environment
  813. variable usbtty to be cdc_acm should suffice. The following
  814. might be defined in YourBoardName.h
  815. CONFIG_USB_DEVICE
  816. Define this to build a UDC device
  817. CONFIG_USB_TTY
  818. Define this to have a tty type of device available to
  819. talk to the UDC device
  820. CONFIG_SYS_CONSOLE_IS_IN_ENV
  821. Define this if you want stdin, stdout &/or stderr to
  822. be set to usbtty.
  823. mpc8xx:
  824. CONFIG_SYS_USB_EXTC_CLK 0xBLAH
  825. Derive USB clock from external clock "blah"
  826. - CONFIG_SYS_USB_EXTC_CLK 0x02
  827. CONFIG_SYS_USB_BRG_CLK 0xBLAH
  828. Derive USB clock from brgclk
  829. - CONFIG_SYS_USB_BRG_CLK 0x04
  830. If you have a USB-IF assigned VendorID then you may wish to
  831. define your own vendor specific values either in BoardName.h
  832. or directly in usbd_vendor_info.h. If you don't define
  833. CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
  834. CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
  835. should pretend to be a Linux device to it's target host.
  836. CONFIG_USBD_MANUFACTURER
  837. Define this string as the name of your company for
  838. - CONFIG_USBD_MANUFACTURER "my company"
  839. CONFIG_USBD_PRODUCT_NAME
  840. Define this string as the name of your product
  841. - CONFIG_USBD_PRODUCT_NAME "acme usb device"
  842. CONFIG_USBD_VENDORID
  843. Define this as your assigned Vendor ID from the USB
  844. Implementors Forum. This *must* be a genuine Vendor ID
  845. to avoid polluting the USB namespace.
  846. - CONFIG_USBD_VENDORID 0xFFFF
  847. CONFIG_USBD_PRODUCTID
  848. Define this as the unique Product ID
  849. for your device
  850. - CONFIG_USBD_PRODUCTID 0xFFFF
  851. - MMC Support:
  852. The MMC controller on the Intel PXA is supported. To
  853. enable this define CONFIG_MMC. The MMC can be
  854. accessed from the boot prompt by mapping the device
  855. to physical memory similar to flash. Command line is
  856. enabled with CONFIG_CMD_MMC. The MMC driver also works with
  857. the FAT fs. This is enabled with CONFIG_CMD_FAT.
  858. CONFIG_SH_MMCIF
  859. Support for Renesas on-chip MMCIF controller
  860. CONFIG_SH_MMCIF_ADDR
  861. Define the base address of MMCIF registers
  862. CONFIG_SH_MMCIF_CLK
  863. Define the clock frequency for MMCIF
  864. - Journaling Flash filesystem support:
  865. CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
  866. CONFIG_JFFS2_NAND_DEV
  867. Define these for a default partition on a NAND device
  868. CONFIG_SYS_JFFS2_FIRST_SECTOR,
  869. CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
  870. Define these for a default partition on a NOR device
  871. CONFIG_SYS_JFFS_CUSTOM_PART
  872. Define this to create an own partition. You have to provide a
  873. function struct part_info* jffs2_part_info(int part_num)
  874. If you define only one JFFS2 partition you may also want to
  875. #define CONFIG_SYS_JFFS_SINGLE_PART 1
  876. to disable the command chpart. This is the default when you
  877. have not defined a custom partition
  878. - Keyboard Support:
  879. CONFIG_ISA_KEYBOARD
  880. Define this to enable standard (PC-Style) keyboard
  881. support
  882. CONFIG_I8042_KBD
  883. Standard PC keyboard driver with US (is default) and
  884. GERMAN key layout (switch via environment 'keymap=de') support.
  885. Export function i8042_kbd_init, i8042_tstc and i8042_getc
  886. for cfb_console. Supports cursor blinking.
  887. - Video support:
  888. CONFIG_VIDEO
  889. Define this to enable video support (for output to
  890. video).
  891. CONFIG_VIDEO_CT69000
  892. Enable Chips & Technologies 69000 Video chip
  893. CONFIG_VIDEO_SMI_LYNXEM
  894. Enable Silicon Motion SMI 712/710/810 Video chip. The
  895. video output is selected via environment 'videoout'
  896. (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
  897. assumed.
  898. For the CT69000 and SMI_LYNXEM drivers, videomode is
  899. selected via environment 'videomode'. Two different ways
  900. are possible:
  901. - "videomode=num" 'num' is a standard LiLo mode numbers.
  902. Following standard modes are supported (* is default):
  903. Colors 640x480 800x600 1024x768 1152x864 1280x1024
  904. -------------+---------------------------------------------
  905. 8 bits | 0x301* 0x303 0x305 0x161 0x307
  906. 15 bits | 0x310 0x313 0x316 0x162 0x319
  907. 16 bits | 0x311 0x314 0x317 0x163 0x31A
  908. 24 bits | 0x312 0x315 0x318 ? 0x31B
  909. -------------+---------------------------------------------
  910. (i.e. setenv videomode 317; saveenv; reset;)
  911. - "videomode=bootargs" all the video parameters are parsed
  912. from the bootargs. (See drivers/video/videomodes.c)
  913. CONFIG_VIDEO_SED13806
  914. Enable Epson SED13806 driver. This driver supports 8bpp
  915. and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
  916. or CONFIG_VIDEO_SED13806_16BPP
  917. CONFIG_FSL_DIU_FB
  918. Enable the Freescale DIU video driver. Reference boards for
  919. SOCs that have a DIU should define this macro to enable DIU
  920. support, and should also define these other macros:
  921. CONFIG_SYS_DIU_ADDR
  922. CONFIG_VIDEO
  923. CONFIG_CMD_BMP
  924. CONFIG_CFB_CONSOLE
  925. CONFIG_VIDEO_SW_CURSOR
  926. CONFIG_VGA_AS_SINGLE_DEVICE
  927. CONFIG_VIDEO_LOGO
  928. CONFIG_VIDEO_BMP_LOGO
  929. The DIU driver will look for the 'video-mode' environment
  930. variable, and if defined, enable the DIU as a console during
  931. boot. See the documentation file README.video for a
  932. description of this variable.
  933. - Keyboard Support:
  934. CONFIG_KEYBOARD
  935. Define this to enable a custom keyboard support.
  936. This simply calls drv_keyboard_init() which must be
  937. defined in your board-specific files.
  938. The only board using this so far is RBC823.
  939. - LCD Support: CONFIG_LCD
  940. Define this to enable LCD support (for output to LCD
  941. display); also select one of the supported displays
  942. by defining one of these:
  943. CONFIG_ATMEL_LCD:
  944. HITACHI TX09D70VM1CCA, 3.5", 240x320.
  945. CONFIG_NEC_NL6448AC33:
  946. NEC NL6448AC33-18. Active, color, single scan.
  947. CONFIG_NEC_NL6448BC20
  948. NEC NL6448BC20-08. 6.5", 640x480.
  949. Active, color, single scan.
  950. CONFIG_NEC_NL6448BC33_54
  951. NEC NL6448BC33-54. 10.4", 640x480.
  952. Active, color, single scan.
  953. CONFIG_SHARP_16x9
  954. Sharp 320x240. Active, color, single scan.
  955. It isn't 16x9, and I am not sure what it is.
  956. CONFIG_SHARP_LQ64D341
  957. Sharp LQ64D341 display, 640x480.
  958. Active, color, single scan.
  959. CONFIG_HLD1045
  960. HLD1045 display, 640x480.
  961. Active, color, single scan.
  962. CONFIG_OPTREX_BW
  963. Optrex CBL50840-2 NF-FW 99 22 M5
  964. or
  965. Hitachi LMG6912RPFC-00T
  966. or
  967. Hitachi SP14Q002
  968. 320x240. Black & white.
  969. Normally display is black on white background; define
  970. CONFIG_SYS_WHITE_ON_BLACK to get it inverted.
  971. - Splash Screen Support: CONFIG_SPLASH_SCREEN
  972. If this option is set, the environment is checked for
  973. a variable "splashimage". If found, the usual display
  974. of logo, copyright and system information on the LCD
  975. is suppressed and the BMP image at the address
  976. specified in "splashimage" is loaded instead. The
  977. console is redirected to the "nulldev", too. This
  978. allows for a "silent" boot where a splash screen is
  979. loaded very quickly after power-on.
  980. CONFIG_SPLASH_SCREEN_ALIGN
  981. If this option is set the splash image can be freely positioned
  982. on the screen. Environment variable "splashpos" specifies the
  983. position as "x,y". If a positive number is given it is used as
  984. number of pixel from left/top. If a negative number is given it
  985. is used as number of pixel from right/bottom. You can also
  986. specify 'm' for centering the image.
  987. Example:
  988. setenv splashpos m,m
  989. => image at center of screen
  990. setenv splashpos 30,20
  991. => image at x = 30 and y = 20
  992. setenv splashpos -10,m
  993. => vertically centered image
  994. at x = dspWidth - bmpWidth - 9
  995. - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
  996. If this option is set, additionally to standard BMP
  997. images, gzipped BMP images can be displayed via the
  998. splashscreen support or the bmp command.
  999. - Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
  1000. If this option is set, 8-bit RLE compressed BMP images
  1001. can be displayed via the splashscreen support or the
  1002. bmp command.
  1003. - Compression support:
  1004. CONFIG_BZIP2
  1005. If this option is set, support for bzip2 compressed
  1006. images is included. If not, only uncompressed and gzip
  1007. compressed images are supported.
  1008. NOTE: the bzip2 algorithm requires a lot of RAM, so
  1009. the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
  1010. be at least 4MB.
  1011. CONFIG_LZMA
  1012. If this option is set, support for lzma compressed
  1013. images is included.
  1014. Note: The LZMA algorithm adds between 2 and 4KB of code and it
  1015. requires an amount of dynamic memory that is given by the
  1016. formula:
  1017. (1846 + 768 << (lc + lp)) * sizeof(uint16)
  1018. Where lc and lp stand for, respectively, Literal context bits
  1019. and Literal pos bits.
  1020. This value is upper-bounded by 14MB in the worst case. Anyway,
  1021. for a ~4MB large kernel image, we have lc=3 and lp=0 for a
  1022. total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is
  1023. a very small buffer.
  1024. Use the lzmainfo tool to determinate the lc and lp values and
  1025. then calculate the amount of needed dynamic memory (ensuring
  1026. the appropriate CONFIG_SYS_MALLOC_LEN value).
  1027. - MII/PHY support:
  1028. CONFIG_PHY_ADDR
  1029. The address of PHY on MII bus.
  1030. CONFIG_PHY_CLOCK_FREQ (ppc4xx)
  1031. The clock frequency of the MII bus
  1032. CONFIG_PHY_GIGE
  1033. If this option is set, support for speed/duplex
  1034. detection of gigabit PHY is included.
  1035. CONFIG_PHY_RESET_DELAY
  1036. Some PHY like Intel LXT971A need extra delay after
  1037. reset before any MII register access is possible.
  1038. For such PHY, set this option to the usec delay
  1039. required. (minimum 300usec for LXT971A)
  1040. CONFIG_PHY_CMD_DELAY (ppc4xx)
  1041. Some PHY like Intel LXT971A need extra delay after
  1042. command issued before MII status register can be read
  1043. - Ethernet address:
  1044. CONFIG_ETHADDR
  1045. CONFIG_ETH1ADDR
  1046. CONFIG_ETH2ADDR
  1047. CONFIG_ETH3ADDR
  1048. CONFIG_ETH4ADDR
  1049. CONFIG_ETH5ADDR
  1050. Define a default value for Ethernet address to use
  1051. for the respective Ethernet interface, in case this
  1052. is not determined automatically.
  1053. - IP address:
  1054. CONFIG_IPADDR
  1055. Define a default value for the IP address to use for
  1056. the default Ethernet interface, in case this is not
  1057. determined through e.g. bootp.
  1058. - Server IP address:
  1059. CONFIG_SERVERIP
  1060. Defines a default value for the IP address of a TFTP
  1061. server to contact when using the "tftboot" command.
  1062. CONFIG_KEEP_SERVERADDR
  1063. Keeps the server's MAC address, in the env 'serveraddr'
  1064. for passing to bootargs (like Linux's netconsole option)
  1065. - Multicast TFTP Mode:
  1066. CONFIG_MCAST_TFTP
  1067. Defines whether you want to support multicast TFTP as per
  1068. rfc-2090; for example to work with atftp. Lets lots of targets
  1069. tftp down the same boot image concurrently. Note: the Ethernet
  1070. driver in use must provide a function: mcast() to join/leave a
  1071. multicast group.
  1072. - BOOTP Recovery Mode:
  1073. CONFIG_BOOTP_RANDOM_DELAY
  1074. If you have many targets in a network that try to
  1075. boot using BOOTP, you may want to avoid that all
  1076. systems send out BOOTP requests at precisely the same
  1077. moment (which would happen for instance at recovery
  1078. from a power failure, when all systems will try to
  1079. boot, thus flooding the BOOTP server. Defining
  1080. CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
  1081. inserted before sending out BOOTP requests. The
  1082. following delays are inserted then:
  1083. 1st BOOTP request: delay 0 ... 1 sec
  1084. 2nd BOOTP request: delay 0 ... 2 sec
  1085. 3rd BOOTP request: delay 0 ... 4 sec
  1086. 4th and following
  1087. BOOTP requests: delay 0 ... 8 sec
  1088. - DHCP Advanced Options:
  1089. You can fine tune the DHCP functionality by defining
  1090. CONFIG_BOOTP_* symbols:
  1091. CONFIG_BOOTP_SUBNETMASK
  1092. CONFIG_BOOTP_GATEWAY
  1093. CONFIG_BOOTP_HOSTNAME
  1094. CONFIG_BOOTP_NISDOMAIN
  1095. CONFIG_BOOTP_BOOTPATH
  1096. CONFIG_BOOTP_BOOTFILESIZE
  1097. CONFIG_BOOTP_DNS
  1098. CONFIG_BOOTP_DNS2
  1099. CONFIG_BOOTP_SEND_HOSTNAME
  1100. CONFIG_BOOTP_NTPSERVER
  1101. CONFIG_BOOTP_TIMEOFFSET
  1102. CONFIG_BOOTP_VENDOREX
  1103. CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
  1104. environment variable, not the BOOTP server.
  1105. CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
  1106. serverip from a DHCP server, it is possible that more
  1107. than one DNS serverip is offered to the client.
  1108. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
  1109. serverip will be stored in the additional environment
  1110. variable "dnsip2". The first DNS serverip is always
  1111. stored in the variable "dnsip", when CONFIG_BOOTP_DNS
  1112. is defined.
  1113. CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
  1114. to do a dynamic update of a DNS server. To do this, they
  1115. need the hostname of the DHCP requester.
  1116. If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
  1117. of the "hostname" environment variable is passed as
  1118. option 12 to the DHCP server.
  1119. CONFIG_BOOTP_DHCP_REQUEST_DELAY
  1120. A 32bit value in microseconds for a delay between
  1121. receiving a "DHCP Offer" and sending the "DHCP Request".
  1122. This fixes a problem with certain DHCP servers that don't
  1123. respond 100% of the time to a "DHCP request". E.g. On an
  1124. AT91RM9200 processor running at 180MHz, this delay needed
  1125. to be *at least* 15,000 usec before a Windows Server 2003
  1126. DHCP server would reply 100% of the time. I recommend at
  1127. least 50,000 usec to be safe. The alternative is to hope
  1128. that one of the retries will be successful but note that
  1129. the DHCP timeout and retry process takes a longer than
  1130. this delay.
  1131. - CDP Options:
  1132. CONFIG_CDP_DEVICE_ID
  1133. The device id used in CDP trigger frames.
  1134. CONFIG_CDP_DEVICE_ID_PREFIX
  1135. A two character string which is prefixed to the MAC address
  1136. of the device.
  1137. CONFIG_CDP_PORT_ID
  1138. A printf format string which contains the ascii name of
  1139. the port. Normally is set to "eth%d" which sets
  1140. eth0 for the first Ethernet, eth1 for the second etc.
  1141. CONFIG_CDP_CAPABILITIES
  1142. A 32bit integer which indicates the device capabilities;
  1143. 0x00000010 for a normal host which does not forwards.
  1144. CONFIG_CDP_VERSION
  1145. An ascii string containing the version of the software.
  1146. CONFIG_CDP_PLATFORM
  1147. An ascii string containing the name of the platform.
  1148. CONFIG_CDP_TRIGGER
  1149. A 32bit integer sent on the trigger.
  1150. CONFIG_CDP_POWER_CONSUMPTION
  1151. A 16bit integer containing the power consumption of the
  1152. device in .1 of milliwatts.
  1153. CONFIG_CDP_APPLIANCE_VLAN_TYPE
  1154. A byte containing the id of the VLAN.
  1155. - Status LED: CONFIG_STATUS_LED
  1156. Several configurations allow to display the current
  1157. status using a LED. For instance, the LED will blink
  1158. fast while running U-Boot code, stop blinking as
  1159. soon as a reply to a BOOTP request was received, and
  1160. start blinking slow once the Linux kernel is running
  1161. (supported by a status LED driver in the Linux
  1162. kernel). Defining CONFIG_STATUS_LED enables this
  1163. feature in U-Boot.
  1164. - CAN Support: CONFIG_CAN_DRIVER
  1165. Defining CONFIG_CAN_DRIVER enables CAN driver support
  1166. on those systems that support this (optional)
  1167. feature, like the TQM8xxL modules.
  1168. - I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C
  1169. These enable I2C serial bus commands. Defining either of
  1170. (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
  1171. include the appropriate I2C driver for the selected CPU.
  1172. This will allow you to use i2c commands at the u-boot
  1173. command line (as long as you set CONFIG_CMD_I2C in
  1174. CONFIG_COMMANDS) and communicate with i2c based realtime
  1175. clock chips. See common/cmd_i2c.c for a description of the
  1176. command line interface.
  1177. CONFIG_HARD_I2C selects a hardware I2C controller.
  1178. CONFIG_SOFT_I2C configures u-boot to use a software (aka
  1179. bit-banging) driver instead of CPM or similar hardware
  1180. support for I2C.
  1181. There are several other quantities that must also be
  1182. defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
  1183. In both cases you will need to define CONFIG_SYS_I2C_SPEED
  1184. to be the frequency (in Hz) at which you wish your i2c bus
  1185. to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie
  1186. the CPU's i2c node address).
  1187. Now, the u-boot i2c code for the mpc8xx
  1188. (arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node
  1189. and so its address should therefore be cleared to 0 (See,
  1190. eg, MPC823e User's Manual p.16-473). So, set
  1191. CONFIG_SYS_I2C_SLAVE to 0.
  1192. CONFIG_SYS_I2C_INIT_MPC5XXX
  1193. When a board is reset during an i2c bus transfer
  1194. chips might think that the current transfer is still
  1195. in progress. Reset the slave devices by sending start
  1196. commands until the slave device responds.
  1197. That's all that's required for CONFIG_HARD_I2C.
  1198. If you use the software i2c interface (CONFIG_SOFT_I2C)
  1199. then the following macros need to be defined (examples are
  1200. from include/configs/lwmon.h):
  1201. I2C_INIT
  1202. (Optional). Any commands necessary to enable the I2C
  1203. controller or configure ports.
  1204. eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
  1205. I2C_PORT
  1206. (Only for MPC8260 CPU). The I/O port to use (the code
  1207. assumes both bits are on the same port). Valid values
  1208. are 0..3 for ports A..D.
  1209. I2C_ACTIVE
  1210. The code necessary to make the I2C data line active
  1211. (driven). If the data line is open collector, this
  1212. define can be null.
  1213. eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
  1214. I2C_TRISTATE
  1215. The code necessary to make the I2C data line tri-stated
  1216. (inactive). If the data line is open collector, this
  1217. define can be null.
  1218. eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
  1219. I2C_READ
  1220. Code that returns TRUE if the I2C data line is high,
  1221. FALSE if it is low.
  1222. eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
  1223. I2C_SDA(bit)
  1224. If <bit> is TRUE, sets the I2C data line high. If it
  1225. is FALSE, it clears it (low).
  1226. eg: #define I2C_SDA(bit) \
  1227. if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
  1228. else immr->im_cpm.cp_pbdat &= ~PB_SDA
  1229. I2C_SCL(bit)
  1230. If <bit> is TRUE, sets the I2C clock line high. If it
  1231. is FALSE, it clears it (low).
  1232. eg: #define I2C_SCL(bit) \
  1233. if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
  1234. else immr->im_cpm.cp_pbdat &= ~PB_SCL
  1235. I2C_DELAY
  1236. This delay is invoked four times per clock cycle so this
  1237. controls the rate of data transfer. The data rate thus
  1238. is 1 / (I2C_DELAY * 4). Often defined to be something
  1239. like:
  1240. #define I2C_DELAY udelay(2)
  1241. CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
  1242. If your arch supports the generic GPIO framework (asm/gpio.h),
  1243. then you may alternatively define the two GPIOs that are to be
  1244. used as SCL / SDA. Any of the previous I2C_xxx macros will
  1245. have GPIO-based defaults assigned to them as appropriate.
  1246. You should define these to the GPIO value as given directly to
  1247. the generic GPIO functions.
  1248. CONFIG_SYS_I2C_INIT_BOARD
  1249. When a board is reset during an i2c bus transfer
  1250. chips might think that the current transfer is still
  1251. in progress. On some boards it is possible to access
  1252. the i2c SCLK line directly, either by using the
  1253. processor pin as a GPIO or by having a second pin
  1254. connected to the bus. If this option is defined a
  1255. custom i2c_init_board() routine in boards/xxx/board.c
  1256. is run early in the boot sequence.
  1257. CONFIG_SYS_I2C_BOARD_LATE_INIT
  1258. An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is
  1259. defined a custom i2c_board_late_init() routine in
  1260. boards/xxx/board.c is run AFTER the operations in i2c_init()
  1261. is completed. This callpoint can be used to unreset i2c bus
  1262. using CPU i2c controller register accesses for CPUs whose i2c
  1263. controller provide such a method. It is called at the end of
  1264. i2c_init() to allow i2c_init operations to setup the i2c bus
  1265. controller on the CPU (e.g. setting bus speed & slave address).
  1266. CONFIG_I2CFAST (PPC405GP|PPC405EP only)
  1267. This option enables configuration of bi_iic_fast[] flags
  1268. in u-boot bd_info structure based on u-boot environment
  1269. variable "i2cfast". (see also i2cfast)
  1270. CONFIG_I2C_MULTI_BUS
  1271. This option allows the use of multiple I2C buses, each of which
  1272. must have a controller. At any point in time, only one bus is
  1273. active. To switch to a different bus, use the 'i2c dev' command.
  1274. Note that bus numbering is zero-based.
  1275. CONFIG_SYS_I2C_NOPROBES
  1276. This option specifies a list of I2C devices that will be skipped
  1277. when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS
  1278. is set, specify a list of bus-device pairs. Otherwise, specify
  1279. a 1D array of device addresses
  1280. e.g.
  1281. #undef CONFIG_I2C_MULTI_BUS
  1282. #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}
  1283. will skip addresses 0x50 and 0x68 on a board with one I2C bus
  1284. #define CONFIG_I2C_MULTI_BUS
  1285. #define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
  1286. will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
  1287. CONFIG_SYS_SPD_BUS_NUM
  1288. If defined, then this indicates the I2C bus number for DDR SPD.
  1289. If not defined, then U-Boot assumes that SPD is on I2C bus 0.
  1290. CONFIG_SYS_RTC_BUS_NUM
  1291. If defined, then this indicates the I2C bus number for the RTC.
  1292. If not defined, then U-Boot assumes that RTC is on I2C bus 0.
  1293. CONFIG_SYS_DTT_BUS_NUM
  1294. If defined, then this indicates the I2C bus number for the DTT.
  1295. If not defined, then U-Boot assumes that DTT is on I2C bus 0.
  1296. CONFIG_SYS_I2C_DTT_ADDR:
  1297. If defined, specifies the I2C address of the DTT device.
  1298. If not defined, then U-Boot uses predefined value for
  1299. specified DTT device.
  1300. CONFIG_FSL_I2C
  1301. Define this option if you want to use Freescale's I2C driver in
  1302. drivers/i2c/fsl_i2c.c.
  1303. CONFIG_I2C_MUX
  1304. Define this option if you have I2C devices reached over 1 .. n
  1305. I2C Muxes like the pca9544a. This option addes a new I2C
  1306. Command "i2c bus [muxtype:muxaddr:muxchannel]" which adds a
  1307. new I2C Bus to the existing I2C Busses. If you select the
  1308. new Bus with "i2c dev", u-bbot sends first the commandos for
  1309. the muxes to activate this new "bus".
  1310. CONFIG_I2C_MULTI_BUS must be also defined, to use this
  1311. feature!
  1312. Example:
  1313. Adding a new I2C Bus reached over 2 pca9544a muxes
  1314. The First mux with address 70 and channel 6
  1315. The Second mux with address 71 and channel 4
  1316. => i2c bus pca9544a:70:6:pca9544a:71:4
  1317. Use the "i2c bus" command without parameter, to get a list
  1318. of I2C Busses with muxes:
  1319. => i2c bus
  1320. Busses reached over muxes:
  1321. Bus ID: 2
  1322. reached over Mux(es):
  1323. pca9544a@70 ch: 4
  1324. Bus ID: 3
  1325. reached over Mux(es):
  1326. pca9544a@70 ch: 6
  1327. pca9544a@71 ch: 4
  1328. =>
  1329. If you now switch to the new I2C Bus 3 with "i2c dev 3"
  1330. u-boot first sends the command to the mux@70 to enable
  1331. channel 6, and then the command to the mux@71 to enable
  1332. the channel 4.
  1333. After that, you can use the "normal" i2c commands as
  1334. usual to communicate with your I2C devices behind
  1335. the 2 muxes.
  1336. This option is actually implemented for the bitbanging
  1337. algorithm in common/soft_i2c.c and for the Hardware I2C
  1338. Bus on the MPC8260. But it should be not so difficult
  1339. to add this option to other architectures.
  1340. CONFIG_SOFT_I2C_READ_REPEATED_START
  1341. defining this will force the i2c_read() function in
  1342. the soft_i2c driver to perform an I2C repeated start
  1343. between writing the address pointer and reading the
  1344. data. If this define is omitted the default behaviour
  1345. of doing a stop-start sequence will be used. Most I2C
  1346. devices can use either method, but some require one or
  1347. the other.
  1348. - SPI Support: CONFIG_SPI
  1349. Enables SPI driver (so far only tested with
  1350. SPI EEPROM, also an instance works with Crystal A/D and
  1351. D/As on the SACSng board)
  1352. CONFIG_SH_SPI
  1353. Enables the driver for SPI controller on SuperH. Currently
  1354. only SH7757 is supported.
  1355. CONFIG_SPI_X
  1356. Enables extended (16-bit) SPI EEPROM addressing.
  1357. (symmetrical to CONFIG_I2C_X)
  1358. CONFIG_SOFT_SPI
  1359. Enables a software (bit-bang) SPI driver rather than
  1360. using hardware support. This is a general purpose
  1361. driver that only requires three general I/O port pins
  1362. (two outputs, one input) to function. If this is
  1363. defined, the board configuration must define several
  1364. SPI configuration items (port pins to use, etc). For
  1365. an example, see include/configs/sacsng.h.
  1366. CONFIG_HARD_SPI
  1367. Enables a hardware SPI driver for general-purpose reads
  1368. and writes. As with CONFIG_SOFT_SPI, the board configuration
  1369. must define a list of chip-select function pointers.
  1370. Currently supported on some MPC8xxx processors. For an
  1371. example, see include/configs/mpc8349emds.h.
  1372. CONFIG_MXC_SPI
  1373. Enables the driver for the SPI controllers on i.MX and MXC
  1374. SoCs. Currently only i.MX31 is supported.
  1375. - FPGA Support: CONFIG_FPGA
  1376. Enables FPGA subsystem.
  1377. CONFIG_FPGA_<vendor>
  1378. Enables support for specific chip vendors.
  1379. (ALTERA, XILINX)
  1380. CONFIG_FPGA_<family>
  1381. Enables support for FPGA family.
  1382. (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
  1383. CONFIG_FPGA_COUNT
  1384. Specify the number of FPGA devices to support.
  1385. CONFIG_SYS_FPGA_PROG_FEEDBACK
  1386. Enable printing of hash marks during FPGA configuration.
  1387. CONFIG_SYS_FPGA_CHECK_BUSY
  1388. Enable checks on FPGA configuration interface busy
  1389. status by the configuration function. This option
  1390. will require a board or device specific function to
  1391. be written.
  1392. CONFIG_FPGA_DELAY
  1393. If defined, a function that provides delays in the FPGA
  1394. configuration driver.
  1395. CONFIG_SYS_FPGA_CHECK_CTRLC
  1396. Allow Control-C to interrupt FPGA configuration
  1397. CONFIG_SYS_FPGA_CHECK_ERROR
  1398. Check for configuration errors during FPGA bitfile
  1399. loading. For example, abort during Virtex II
  1400. configuration if the INIT_B line goes low (which
  1401. indicated a CRC error).
  1402. CONFIG_SYS_FPGA_WAIT_INIT
  1403. Maximum time to wait for the INIT_B line to deassert
  1404. after PROB_B has been deasserted during a Virtex II
  1405. FPGA configuration sequence. The default time is 500
  1406. ms.
  1407. CONFIG_SYS_FPGA_WAIT_BUSY
  1408. Maximum time to wait for BUSY to deassert during
  1409. Virtex II FPGA configuration. The default is 5 ms.
  1410. CONFIG_SYS_FPGA_WAIT_CONFIG
  1411. Time to wait after FPGA configuration. The default is
  1412. 200 ms.
  1413. - Configuration Management:
  1414. CONFIG_IDENT_STRING
  1415. If defined, this string will be added to the U-Boot
  1416. version information (U_BOOT_VERSION)
  1417. - Vendor Parameter Protection:
  1418. U-Boot considers the values of the environment
  1419. variables "serial#" (Board Serial Number) and
  1420. "ethaddr" (Ethernet Address) to be parameters that
  1421. are set once by the board vendor / manufacturer, and
  1422. protects these variables from casual modification by
  1423. the user. Once set, these variables are read-only,
  1424. and write or delete attempts are rejected. You can
  1425. change this behaviour:
  1426. If CONFIG_ENV_OVERWRITE is #defined in your config
  1427. file, the write protection for vendor parameters is
  1428. completely disabled. Anybody can change or delete
  1429. these parameters.
  1430. Alternatively, if you #define _both_ CONFIG_ETHADDR
  1431. _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
  1432. Ethernet address is installed in the environment,
  1433. which can be changed exactly ONCE by the user. [The
  1434. serial# is unaffected by this, i. e. it remains
  1435. read-only.]
  1436. - Protected RAM:
  1437. CONFIG_PRAM
  1438. Define this variable to enable the reservation of
  1439. "protected RAM", i. e. RAM which is not overwritten
  1440. by U-Boot. Define CONFIG_PRAM to hold the number of
  1441. kB you want to reserve for pRAM. You can overwrite
  1442. this default value by defining an environment
  1443. variable "pram" to the number of kB you want to
  1444. reserve. Note that the board info structure will
  1445. still show the full amount of RAM. If pRAM is
  1446. reserved, a new environment variable "mem" will
  1447. automatically be defined to hold the amount of
  1448. remaining RAM in a form that can be passed as boot
  1449. argument to Linux, for instance like that:
  1450. setenv bootargs ... mem=\${mem}
  1451. saveenv
  1452. This way you can tell Linux not to use this memory,
  1453. either, which results in a memory region that will
  1454. not be affected by reboots.
  1455. *WARNING* If your board configuration uses automatic
  1456. detection of the RAM size, you must make sure that
  1457. this memory test is non-destructive. So far, the
  1458. following board configurations are known to be
  1459. "pRAM-clean":
  1460. ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
  1461. HERMES, IP860, RPXlite, LWMON, LANTEC,
  1462. FLAGADM, TQM8260
  1463. - Error Recovery:
  1464. CONFIG_PANIC_HANG
  1465. Define this variable to stop the system in case of a
  1466. fatal error, so that you have to reset it manually.
  1467. This is probably NOT a good idea for an embedded
  1468. system where you want the system to reboot
  1469. automatically as fast as possible, but it may be
  1470. useful during development since you can try to debug
  1471. the conditions that lead to the situation.
  1472. CONFIG_NET_RETRY_COUNT
  1473. This variable defines the number of retries for
  1474. network operations like ARP, RARP, TFTP, or BOOTP
  1475. before giving up the operation. If not defined, a
  1476. default value of 5 is used.
  1477. CONFIG_ARP_TIMEOUT
  1478. Timeout waiting for an ARP reply in milliseconds.
  1479. - Command Interpreter:
  1480. CONFIG_AUTO_COMPLETE
  1481. Enable auto completion of commands using TAB.
  1482. Note that this feature has NOT been implemented yet
  1483. for the "hush" shell.
  1484. CONFIG_SYS_HUSH_PARSER
  1485. Define this variable to enable the "hush" shell (from
  1486. Busybox) as command line interpreter, thus enabling
  1487. powerful command line syntax like
  1488. if...then...else...fi conditionals or `&&' and '||'
  1489. constructs ("shell scripts").
  1490. If undefined, you get the old, much simpler behaviour
  1491. with a somewhat smaller memory footprint.
  1492. CONFIG_SYS_PROMPT_HUSH_PS2
  1493. This defines the secondary prompt string, which is
  1494. printed when the command interpreter needs more input
  1495. to complete a command. Usually "> ".
  1496. Note:
  1497. In the current implementation, the local variables
  1498. space and global environment variables space are
  1499. separated. Local variables are those you define by
  1500. simply typing `name=value'. To access a local
  1501. variable later on, you have write `$name' or
  1502. `${name}'; to execute the contents of a variable
  1503. directly type `$name' at the command prompt.
  1504. Global environment variables are those you use
  1505. setenv/printenv to work with. To run a command stored
  1506. in such a variable, you need to use the run command,
  1507. and you must not use the '$' sign to access them.
  1508. To store commands and special characters in a
  1509. variable, please use double quotation marks
  1510. surrounding the whole text of the variable, instead
  1511. of the backslashes before semicolons and special
  1512. symbols.
  1513. - Commandline Editing and History:
  1514. CONFIG_CMDLINE_EDITING
  1515. Enable editing and History functions for interactive
  1516. commandline input operations
  1517. - Default Environment:
  1518. CONFIG_EXTRA_ENV_SETTINGS
  1519. Define this to contain any number of null terminated
  1520. strings (variable = value pairs) that will be part of
  1521. the default environment compiled into the boot image.
  1522. For example, place something like this in your
  1523. board's config file:
  1524. #define CONFIG_EXTRA_ENV_SETTINGS \
  1525. "myvar1=value1\0" \
  1526. "myvar2=value2\0"
  1527. Warning: This method is based on knowledge about the
  1528. internal format how the environment is stored by the
  1529. U-Boot code. This is NOT an official, exported
  1530. interface! Although it is unlikely that this format
  1531. will change soon, there is no guarantee either.
  1532. You better know what you are doing here.
  1533. Note: overly (ab)use of the default environment is
  1534. discouraged. Make sure to check other ways to preset
  1535. the environment like the "source" command or the
  1536. boot command first.
  1537. - DataFlash Support:
  1538. CONFIG_HAS_DATAFLASH
  1539. Defining this option enables DataFlash features and
  1540. allows to read/write in Dataflash via the standard
  1541. commands cp, md...
  1542. - SystemACE Support:
  1543. CONFIG_SYSTEMACE
  1544. Adding this option adds support for Xilinx SystemACE
  1545. chips attached via some sort of local bus. The address
  1546. of the chip must also be defined in the
  1547. CONFIG_SYS_SYSTEMACE_BASE macro. For example:
  1548. #define CONFIG_SYSTEMACE
  1549. #define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000
  1550. When SystemACE support is added, the "ace" device type
  1551. becomes available to the fat commands, i.e. fatls.
  1552. - TFTP Fixed UDP Port:
  1553. CONFIG_TFTP_PORT
  1554. If this is defined, the environment variable tftpsrcp
  1555. is used to supply the TFTP UDP source port value.
  1556. If tftpsrcp isn't defined, the normal pseudo-random port
  1557. number generator is used.
  1558. Also, the environment variable tftpdstp is used to supply
  1559. the TFTP UDP destination port value. If tftpdstp isn't
  1560. defined, the normal port 69 is used.
  1561. The purpose for tftpsrcp is to allow a TFTP server to
  1562. blindly start the TFTP transfer using the pre-configured
  1563. target IP address and UDP port. This has the effect of
  1564. "punching through" the (Windows XP) firewall, allowing
  1565. the remainder of the TFTP transfer to proceed normally.
  1566. A better solution is to properly configure the firewall,
  1567. but sometimes that is not allowed.
  1568. - Show boot progress:
  1569. CONFIG_SHOW_BOOT_PROGRESS
  1570. Defining this option allows to add some board-
  1571. specific code (calling a user-provided function
  1572. "show_boot_progress(int)") that enables you to show
  1573. the system's boot progress on some display (for
  1574. example, some LED's) on your board. At the moment,
  1575. the following checkpoints are implemented:
  1576. - Standalone program support:
  1577. CONFIG_STANDALONE_LOAD_ADDR
  1578. This option allows to define board specific values
  1579. for the address where standalone program gets loaded,
  1580. thus overwriting the architecutre dependent default
  1581. settings.
  1582. - Frame Buffer Address:
  1583. CONFIG_FB_ADDR
  1584. Define CONFIG_FB_ADDR if you want to use specific address for
  1585. frame buffer.
  1586. Then system will reserve the frame buffer address to defined address
  1587. instead of lcd_setmem (this function grab the memory for frame buffer
  1588. by panel's size).
  1589. Please see board_init_f function.
  1590. If you want this config option then,
  1591. please define it at your board config file
  1592. Legacy uImage format:
  1593. Arg Where When
  1594. 1 common/cmd_bootm.c before attempting to boot an image
  1595. -1 common/cmd_bootm.c Image header has bad magic number
  1596. 2 common/cmd_bootm.c Image header has correct magic number
  1597. -2 common/cmd_bootm.c Image header has bad checksum
  1598. 3 common/cmd_bootm.c Image header has correct checksum
  1599. -3 common/cmd_bootm.c Image data has bad checksum
  1600. 4 common/cmd_bootm.c Image data has correct checksum
  1601. -4 common/cmd_bootm.c Image is for unsupported architecture
  1602. 5 common/cmd_bootm.c Architecture check OK
  1603. -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
  1604. 6 common/cmd_bootm.c Image Type check OK
  1605. -6 common/cmd_bootm.c gunzip uncompression error
  1606. -7 common/cmd_bootm.c Unimplemented compression type
  1607. 7 common/cmd_bootm.c Uncompression OK
  1608. 8 common/cmd_bootm.c No uncompress/copy overwrite error
  1609. -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
  1610. 9 common/image.c Start initial ramdisk verification
  1611. -10 common/image.c Ramdisk header has bad magic number
  1612. -11 common/image.c Ramdisk header has bad checksum
  1613. 10 common/image.c Ramdisk header is OK
  1614. -12 common/image.c Ramdisk data has bad checksum
  1615. 11 common/image.c Ramdisk data has correct checksum
  1616. 12 common/image.c Ramdisk verification complete, start loading
  1617. -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
  1618. 13 common/image.c Start multifile image verification
  1619. 14 common/image.c No initial ramdisk, no multifile, continue.
  1620. 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
  1621. -30 arch/powerpc/lib/board.c Fatal error, hang the system
  1622. -31 post/post.c POST test failed, detected by post_output_backlog()
  1623. -32 post/post.c POST test failed, detected by post_run_single()
  1624. 34 common/cmd_doc.c before loading a Image from a DOC device
  1625. -35 common/cmd_doc.c Bad usage of "doc" command
  1626. 35 common/cmd_doc.c correct usage of "doc" command
  1627. -36 common/cmd_doc.c No boot device
  1628. 36 common/cmd_doc.c correct boot device
  1629. -37 common/cmd_doc.c Unknown Chip ID on boot device
  1630. 37 common/cmd_doc.c correct chip ID found, device available
  1631. -38 common/cmd_doc.c Read Error on boot device
  1632. 38 common/cmd_doc.c reading Image header from DOC device OK
  1633. -39 common/cmd_doc.c Image header has bad magic number
  1634. 39 common/cmd_doc.c Image header has correct magic number
  1635. -40 common/cmd_doc.c Error reading Image from DOC device
  1636. 40 common/cmd_doc.c Image header has correct magic number
  1637. 41 common/cmd_ide.c before loading a Image from a IDE device
  1638. -42 common/cmd_ide.c Bad usage of "ide" command
  1639. 42 common/cmd_ide.c correct usage of "ide" command
  1640. -43 common/cmd_ide.c No boot device
  1641. 43 common/cmd_ide.c boot device found
  1642. -44 common/cmd_ide.c Device not available
  1643. 44 common/cmd_ide.c Device available
  1644. -45 common/cmd_ide.c wrong partition selected
  1645. 45 common/cmd_ide.c partition selected
  1646. -46 common/cmd_ide.c Unknown partition table
  1647. 46 common/cmd_ide.c valid partition table found
  1648. -47 common/cmd_ide.c Invalid partition type
  1649. 47 common/cmd_ide.c correct partition type
  1650. -48 common/cmd_ide.c Error reading Image Header on boot device
  1651. 48 common/cmd_ide.c reading Image Header from IDE device OK
  1652. -49 common/cmd_ide.c Image header has bad magic number
  1653. 49 common/cmd_ide.c Image header has correct magic number
  1654. -50 common/cmd_ide.c Image header has bad checksum
  1655. 50 common/cmd_ide.c Image header has correct checksum
  1656. -51 common/cmd_ide.c Error reading Image from IDE device
  1657. 51 common/cmd_ide.c reading Image from IDE device OK
  1658. 52 common/cmd_nand.c before loading a Image from a NAND device
  1659. -53 common/cmd_nand.c Bad usage of "nand" command
  1660. 53 common/cmd_nand.c correct usage of "nand" command
  1661. -54 common/cmd_nand.c No boot device
  1662. 54 common/cmd_nand.c boot device found
  1663. -55 common/cmd_nand.c Unknown Chip ID on boot device
  1664. 55 common/cmd_nand.c correct chip ID found, device available
  1665. -56 common/cmd_nand.c Error reading Image Header on boot device
  1666. 56 common/cmd_nand.c reading Image Header from NAND device OK
  1667. -57 common/cmd_nand.c Image header has bad magic number
  1668. 57 common/cmd_nand.c Image header has correct magic number
  1669. -58 common/cmd_nand.c Error reading Image from NAND device
  1670. 58 common/cmd_nand.c reading Image from NAND device OK
  1671. -60 common/env_common.c Environment has a bad CRC, using default
  1672. 64 net/eth.c starting with Ethernet configuration.
  1673. -64 net/eth.c no Ethernet found.
  1674. 65 net/eth.c Ethernet found.
  1675. -80 common/cmd_net.c usage wrong
  1676. 80 common/cmd_net.c before calling NetLoop()
  1677. -81 common/cmd_net.c some error in NetLoop() occurred
  1678. 81 common/cmd_net.c NetLoop() back without error
  1679. -82 common/cmd_net.c size == 0 (File with size 0 loaded)
  1680. 82 common/cmd_net.c trying automatic boot
  1681. 83 common/cmd_net.c running "source" command
  1682. -83 common/cmd_net.c some error in automatic boot or "source" command
  1683. 84 common/cmd_net.c end without errors
  1684. FIT uImage format:
  1685. Arg Where When
  1686. 100 common/cmd_bootm.c Kernel FIT Image has correct format
  1687. -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
  1688. 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
  1689. -101 common/cmd_bootm.c Can't get configuration for kernel subimage
  1690. 102 common/cmd_bootm.c Kernel unit name specified
  1691. -103 common/cmd_bootm.c Can't get kernel subimage node offset
  1692. 103 common/cmd_bootm.c Found configuration node
  1693. 104 common/cmd_bootm.c Got kernel subimage node offset
  1694. -104 common/cmd_bootm.c Kernel subimage hash verification failed
  1695. 105 common/cmd_bootm.c Kernel subimage hash verification OK
  1696. -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
  1697. 106 common/cmd_bootm.c Architecture check OK
  1698. -106 common/cmd_bootm.c Kernel subimage has wrong type
  1699. 107 common/cmd_bootm.c Kernel subimage type OK
  1700. -107 common/cmd_bootm.c Can't get kernel subimage data/size
  1701. 108 common/cmd_bootm.c Got kernel subimage data/size
  1702. -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
  1703. -109 common/cmd_bootm.c Can't get kernel subimage type
  1704. -110 common/cmd_bootm.c Can't get kernel subimage comp
  1705. -111 common/cmd_bootm.c Can't get kernel subimage os
  1706. -112 common/cmd_bootm.c Can't get kernel subimage load address
  1707. -113 common/cmd_bootm.c Image uncompress/copy overwrite error
  1708. 120 common/image.c Start initial ramdisk verification
  1709. -120 common/image.c Ramdisk FIT image has incorrect format
  1710. 121 common/image.c Ramdisk FIT image has correct format
  1711. 122 common/image.c No ramdisk subimage unit name, using configuration
  1712. -122 common/image.c Can't get configuration for ramdisk subimage
  1713. 123 common/image.c Ramdisk unit name specified
  1714. -124 common/image.c Can't get ramdisk subimage node offset
  1715. 125 common/image.c Got ramdisk subimage node offset
  1716. -125 common/image.c Ramdisk subimage hash verification failed
  1717. 126 common/image.c Ramdisk subimage hash verification OK
  1718. -126 common/image.c Ramdisk subimage for unsupported architecture
  1719. 127 common/image.c Architecture check OK
  1720. -127 common/image.c Can't get ramdisk subimage data/size
  1721. 128 common/image.c Got ramdisk subimage data/size
  1722. 129 common/image.c Can't get ramdisk load address
  1723. -129 common/image.c Got ramdisk load address
  1724. -130 common/cmd_doc.c Incorrect FIT image format
  1725. 131 common/cmd_doc.c FIT image format OK
  1726. -140 common/cmd_ide.c Incorrect FIT image format
  1727. 141 common/cmd_ide.c FIT image format OK
  1728. -150 common/cmd_nand.c Incorrect FIT image format
  1729. 151 common/cmd_nand.c FIT image format OK
  1730. - Automatic software updates via TFTP server
  1731. CONFIG_UPDATE_TFTP
  1732. CONFIG_UPDATE_TFTP_CNT_MAX
  1733. CONFIG_UPDATE_TFTP_MSEC_MAX
  1734. These options enable and control the auto-update feature;
  1735. for a more detailed description refer to doc/README.update.
  1736. - MTD Support (mtdparts command, UBI support)
  1737. CONFIG_MTD_DEVICE
  1738. Adds the MTD device infrastructure from the Linux kernel.
  1739. Needed for mtdparts command support.
  1740. CONFIG_MTD_PARTITIONS
  1741. Adds the MTD partitioning infrastructure from the Linux
  1742. kernel. Needed for UBI support.
  1743. - SPL framework
  1744. CONFIG_SPL
  1745. Enable building of SPL globally.
  1746. CONFIG_SPL_TEXT_BASE
  1747. TEXT_BASE for linking the SPL binary.
  1748. CONFIG_SPL_LDSCRIPT
  1749. LDSCRIPT for linking the SPL binary.
  1750. CONFIG_SPL_LIBCOMMON_SUPPORT
  1751. Support for common/libcommon.o in SPL binary
  1752. CONFIG_SPL_LIBDISK_SUPPORT
  1753. Support for disk/libdisk.o in SPL binary
  1754. CONFIG_SPL_I2C_SUPPORT
  1755. Support for drivers/i2c/libi2c.o in SPL binary
  1756. CONFIG_SPL_GPIO_SUPPORT
  1757. Support for drivers/gpio/libgpio.o in SPL binary
  1758. CONFIG_SPL_MMC_SUPPORT
  1759. Support for drivers/mmc/libmmc.o in SPL binary
  1760. CONFIG_SPL_SERIAL_SUPPORT
  1761. Support for drivers/serial/libserial.o in SPL binary
  1762. CONFIG_SPL_SPI_FLASH_SUPPORT
  1763. Support for drivers/mtd/spi/libspi_flash.o in SPL binary
  1764. CONFIG_SPL_SPI_SUPPORT
  1765. Support for drivers/spi/libspi.o in SPL binary
  1766. CONFIG_SPL_FAT_SUPPORT
  1767. Support for fs/fat/libfat.o in SPL binary
  1768. CONFIG_SPL_LIBGENERIC_SUPPORT
  1769. Support for lib/libgeneric.o in SPL binary
  1770. Modem Support:
  1771. --------------
  1772. [so far only for SMDK2400 boards]
  1773. - Modem support enable:
  1774. CONFIG_MODEM_SUPPORT
  1775. - RTS/CTS Flow control enable:
  1776. CONFIG_HWFLOW
  1777. - Modem debug support:
  1778. CONFIG_MODEM_SUPPORT_DEBUG
  1779. Enables debugging stuff (char screen[1024], dbg())
  1780. for modem support. Useful only with BDI2000.
  1781. - Interrupt support (PPC):
  1782. There are common interrupt_init() and timer_interrupt()
  1783. for all PPC archs. interrupt_init() calls interrupt_init_cpu()
  1784. for CPU specific initialization. interrupt_init_cpu()
  1785. should set decrementer_count to appropriate value. If
  1786. CPU resets decrementer automatically after interrupt
  1787. (ppc4xx) it should set decrementer_count to zero.
  1788. timer_interrupt() calls timer_interrupt_cpu() for CPU
  1789. specific handling. If board has watchdog / status_led
  1790. / other_activity_monitor it works automatically from
  1791. general timer_interrupt().
  1792. - General:
  1793. In the target system modem support is enabled when a
  1794. specific key (key combination) is pressed during
  1795. power-on. Otherwise U-Boot will boot normally
  1796. (autoboot). The key_pressed() function is called from
  1797. board_init(). Currently key_pressed() is a dummy
  1798. function, returning 1 and thus enabling modem
  1799. initialization.
  1800. If there are no modem init strings in the
  1801. environment, U-Boot proceed to autoboot; the
  1802. previous output (banner, info printfs) will be
  1803. suppressed, though.
  1804. See also: doc/README.Modem
  1805. Configuration Settings:
  1806. -----------------------
  1807. - CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
  1808. undefine this when you're short of memory.
  1809. - CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default
  1810. width of the commands listed in the 'help' command output.
  1811. - CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to
  1812. prompt for user input.
  1813. - CONFIG_SYS_CBSIZE: Buffer size for input from the Console
  1814. - CONFIG_SYS_PBSIZE: Buffer size for Console output
  1815. - CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands
  1816. - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
  1817. the application (usually a Linux kernel) when it is
  1818. booted
  1819. - CONFIG_SYS_BAUDRATE_TABLE:
  1820. List of legal baudrate settings for this board.
  1821. - CONFIG_SYS_CONSOLE_INFO_QUIET
  1822. Suppress display of console information at boot.
  1823. - CONFIG_SYS_CONSOLE_IS_IN_ENV
  1824. If the board specific function
  1825. extern int overwrite_console (void);
  1826. returns 1, the stdin, stderr and stdout are switched to the
  1827. serial port, else the settings in the environment are used.
  1828. - CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE
  1829. Enable the call to overwrite_console().
  1830. - CONFIG_SYS_CONSOLE_ENV_OVERWRITE
  1831. Enable overwrite of previous console environment settings.
  1832. - CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END:
  1833. Begin and End addresses of the area used by the
  1834. simple memory test.
  1835. - CONFIG_SYS_ALT_MEMTEST:
  1836. Enable an alternate, more extensive memory test.
  1837. - CONFIG_SYS_MEMTEST_SCRATCH:
  1838. Scratch address used by the alternate memory test
  1839. You only need to set this if address zero isn't writeable
  1840. - CONFIG_SYS_MEM_TOP_HIDE (PPC only):
  1841. If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,
  1842. this specified memory area will get subtracted from the top
  1843. (end) of RAM and won't get "touched" at all by U-Boot. By
  1844. fixing up gd->ram_size the Linux kernel should gets passed
  1845. the now "corrected" memory size and won't touch it either.
  1846. This should work for arch/ppc and arch/powerpc. Only Linux
  1847. board ports in arch/powerpc with bootwrapper support that
  1848. recalculate the memory size from the SDRAM controller setup
  1849. will have to get fixed in Linux additionally.
  1850. This option can be used as a workaround for the 440EPx/GRx
  1851. CHIP 11 errata where the last 256 bytes in SDRAM shouldn't
  1852. be touched.
  1853. WARNING: Please make sure that this value is a multiple of
  1854. the Linux page size (normally 4k). If this is not the case,
  1855. then the end address of the Linux memory will be located at a
  1856. non page size aligned address and this could cause major
  1857. problems.
  1858. - CONFIG_SYS_TFTP_LOADADDR:
  1859. Default load address for network file downloads
  1860. - CONFIG_SYS_LOADS_BAUD_CHANGE:
  1861. Enable temporary baudrate change while serial download
  1862. - CONFIG_SYS_SDRAM_BASE:
  1863. Physical start address of SDRAM. _Must_ be 0 here.
  1864. - CONFIG_SYS_MBIO_BASE:
  1865. Physical start address of Motherboard I/O (if using a
  1866. Cogent motherboard)
  1867. - CONFIG_SYS_FLASH_BASE:
  1868. Physical start address of Flash memory.
  1869. - CONFIG_SYS_MONITOR_BASE:
  1870. Physical start address of boot monitor code (set by
  1871. make config files to be same as the text base address
  1872. (CONFIG_SYS_TEXT_BASE) used when linking) - same as
  1873. CONFIG_SYS_FLASH_BASE when booting from flash.
  1874. - CONFIG_SYS_MONITOR_LEN:
  1875. Size of memory reserved for monitor code, used to
  1876. determine _at_compile_time_ (!) if the environment is
  1877. embedded within the U-Boot image, or in a separate
  1878. flash sector.
  1879. - CONFIG_SYS_MALLOC_LEN:
  1880. Size of DRAM reserved for malloc() use.
  1881. - CONFIG_SYS_BOOTM_LEN:
  1882. Normally compressed uImages are limited to an
  1883. uncompressed size of 8 MBytes. If this is not enough,
  1884. you can define CONFIG_SYS_BOOTM_LEN in your board config file
  1885. to adjust this setting to your needs.
  1886. - CONFIG_SYS_BOOTMAPSZ:
  1887. Maximum size of memory mapped by the startup code of
  1888. the Linux kernel; all data that must be processed by
  1889. the Linux kernel (bd_info, boot arguments, FDT blob if
  1890. used) must be put below this limit, unless "bootm_low"
  1891. enviroment variable is defined and non-zero. In such case
  1892. all data for the Linux kernel must be between "bootm_low"
  1893. and "bootm_low" + CONFIG_SYS_BOOTMAPSZ. The environment
  1894. variable "bootm_mapsize" will override the value of
  1895. CONFIG_SYS_BOOTMAPSZ. If CONFIG_SYS_BOOTMAPSZ is undefined,
  1896. then the value in "bootm_size" will be used instead.
  1897. - CONFIG_SYS_BOOT_RAMDISK_HIGH:
  1898. Enable initrd_high functionality. If defined then the
  1899. initrd_high feature is enabled and the bootm ramdisk subcommand
  1900. is enabled.
  1901. - CONFIG_SYS_BOOT_GET_CMDLINE:
  1902. Enables allocating and saving kernel cmdline in space between
  1903. "bootm_low" and "bootm_low" + BOOTMAPSZ.
  1904. - CONFIG_SYS_BOOT_GET_KBD:
  1905. Enables allocating and saving a kernel copy of the bd_info in
  1906. space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
  1907. - CONFIG_SYS_MAX_FLASH_BANKS:
  1908. Max number of Flash memory banks
  1909. - CONFIG_SYS_MAX_FLASH_SECT:
  1910. Max number of sectors on a Flash chip
  1911. - CONFIG_SYS_FLASH_ERASE_TOUT:
  1912. Timeout for Flash erase operations (in ms)
  1913. - CONFIG_SYS_FLASH_WRITE_TOUT:
  1914. Timeout for Flash write operations (in ms)
  1915. - CONFIG_SYS_FLASH_LOCK_TOUT
  1916. Timeout for Flash set sector lock bit operation (in ms)
  1917. - CONFIG_SYS_FLASH_UNLOCK_TOUT
  1918. Timeout for Flash clear lock bits operation (in ms)
  1919. - CONFIG_SYS_FLASH_PROTECTION
  1920. If defined, hardware flash sectors protection is used
  1921. instead of U-Boot software protection.
  1922. - CONFIG_SYS_DIRECT_FLASH_TFTP:
  1923. Enable TFTP transfers directly to flash memory;
  1924. without this option such a download has to be
  1925. performed in two steps: (1) download to RAM, and (2)
  1926. copy from RAM to flash.
  1927. The two-step approach is usually more reliable, since
  1928. you can check if the download worked before you erase
  1929. the flash, but in some situations (when system RAM is
  1930. too limited to allow for a temporary copy of the
  1931. downloaded image) this option may be very useful.
  1932. - CONFIG_SYS_FLASH_CFI:
  1933. Define if the flash driver uses extra elements in the
  1934. common flash structure for storing flash geometry.
  1935. - CONFIG_FLASH_CFI_DRIVER
  1936. This option also enables the building of the cfi_flash driver
  1937. in the drivers directory
  1938. - CONFIG_FLASH_CFI_MTD
  1939. This option enables the building of the cfi_mtd driver
  1940. in the drivers directory. The driver exports CFI flash
  1941. to the MTD layer.
  1942. - CONFIG_SYS_FLASH_USE_BUFFER_WRITE
  1943. Use buffered writes to flash.
  1944. - CONFIG_FLASH_SPANSION_S29WS_N
  1945. s29ws-n MirrorBit flash has non-standard addresses for buffered
  1946. write commands.
  1947. - CONFIG_SYS_FLASH_QUIET_TEST
  1948. If this option is defined, the common CFI flash doesn't
  1949. print it's warning upon not recognized FLASH banks. This
  1950. is useful, if some of the configured banks are only
  1951. optionally available.
  1952. - CONFIG_FLASH_SHOW_PROGRESS
  1953. If defined (must be an integer), print out countdown
  1954. digits and dots. Recommended value: 45 (9..1) for 80
  1955. column displays, 15 (3..1) for 40 column displays.
  1956. - CONFIG_SYS_RX_ETH_BUFFER:
  1957. Defines the number of Ethernet receive buffers. On some
  1958. Ethernet controllers it is recommended to set this value
  1959. to 8 or even higher (EEPRO100 or 405 EMAC), since all
  1960. buffers can be full shortly after enabling the interface
  1961. on high Ethernet traffic.
  1962. Defaults to 4 if not defined.
  1963. - CONFIG_ENV_MAX_ENTRIES
  1964. Maximum number of entries in the hash table that is used
  1965. internally to store the environment settings. The default
  1966. setting is supposed to be generous and should work in most
  1967. cases. This setting can be used to tune behaviour; see
  1968. lib/hashtable.c for details.
  1969. The following definitions that deal with the placement and management
  1970. of environment data (variable area); in general, we support the
  1971. following configurations:
  1972. - CONFIG_BUILD_ENVCRC:
  1973. Builds up envcrc with the target environment so that external utils
  1974. may easily extract it and embed it in final U-Boot images.
  1975. - CONFIG_ENV_IS_IN_FLASH:
  1976. Define this if the environment is in flash memory.
  1977. a) The environment occupies one whole flash sector, which is
  1978. "embedded" in the text segment with the U-Boot code. This
  1979. happens usually with "bottom boot sector" or "top boot
  1980. sector" type flash chips, which have several smaller
  1981. sectors at the start or the end. For instance, such a
  1982. layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
  1983. such a case you would place the environment in one of the
  1984. 4 kB sectors - with U-Boot code before and after it. With
  1985. "top boot sector" type flash chips, you would put the
  1986. environment in one of the last sectors, leaving a gap
  1987. between U-Boot and the environment.
  1988. - CONFIG_ENV_OFFSET:
  1989. Offset of environment data (variable area) to the
  1990. beginning of flash memory; for instance, with bottom boot
  1991. type flash chips the second sector can be used: the offset
  1992. for this sector is given here.
  1993. CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
  1994. - CONFIG_ENV_ADDR:
  1995. This is just another way to specify the start address of
  1996. the flash sector containing the environment (instead of
  1997. CONFIG_ENV_OFFSET).
  1998. - CONFIG_ENV_SECT_SIZE:
  1999. Size of the sector containing the environment.
  2000. b) Sometimes flash chips have few, equal sized, BIG sectors.
  2001. In such a case you don't want to spend a whole sector for
  2002. the environment.
  2003. - CONFIG_ENV_SIZE:
  2004. If you use this in combination with CONFIG_ENV_IS_IN_FLASH
  2005. and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
  2006. of this flash sector for the environment. This saves
  2007. memory for the RAM copy of the environment.
  2008. It may also save flash memory if you decide to use this
  2009. when your environment is "embedded" within U-Boot code,
  2010. since then the remainder of the flash sector could be used
  2011. for U-Boot code. It should be pointed out that this is
  2012. STRONGLY DISCOURAGED from a robustness point of view:
  2013. updating the environment in flash makes it always
  2014. necessary to erase the WHOLE sector. If something goes
  2015. wrong before the contents has been restored from a copy in
  2016. RAM, your target system will be dead.
  2017. - CONFIG_ENV_ADDR_REDUND
  2018. CONFIG_ENV_SIZE_REDUND
  2019. These settings describe a second storage area used to hold
  2020. a redundant copy of the environment data, so that there is
  2021. a valid backup copy in case there is a power failure during
  2022. a "saveenv" operation.
  2023. BE CAREFUL! Any changes to the flash layout, and some changes to the
  2024. source code will make it necessary to adapt <board>/u-boot.lds*
  2025. accordingly!
  2026. - CONFIG_ENV_IS_IN_NVRAM:
  2027. Define this if you have some non-volatile memory device
  2028. (NVRAM, battery buffered SRAM) which you want to use for the
  2029. environment.
  2030. - CONFIG_ENV_ADDR:
  2031. - CONFIG_ENV_SIZE:
  2032. These two #defines are used to determine the memory area you
  2033. want to use for environment. It is assumed that this memory
  2034. can just be read and written to, without any special
  2035. provision.
  2036. BE CAREFUL! The first access to the environment happens quite early
  2037. in U-Boot initalization (when we try to get the setting of for the
  2038. console baudrate). You *MUST* have mapped your NVRAM area then, or
  2039. U-Boot will hang.
  2040. Please note that even with NVRAM we still use a copy of the
  2041. environment in RAM: we could work on NVRAM directly, but we want to
  2042. keep settings there always unmodified except somebody uses "saveenv"
  2043. to save the current settings.
  2044. - CONFIG_ENV_IS_IN_EEPROM:
  2045. Use this if you have an EEPROM or similar serial access
  2046. device and a driver for it.
  2047. - CONFIG_ENV_OFFSET:
  2048. - CONFIG_ENV_SIZE:
  2049. These two #defines specify the offset and size of the
  2050. environment area within the total memory of your EEPROM.
  2051. - CONFIG_SYS_I2C_EEPROM_ADDR:
  2052. If defined, specified the chip address of the EEPROM device.
  2053. The default address is zero.
  2054. - CONFIG_SYS_EEPROM_PAGE_WRITE_BITS:
  2055. If defined, the number of bits used to address bytes in a
  2056. single page in the EEPROM device. A 64 byte page, for example
  2057. would require six bits.
  2058. - CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS:
  2059. If defined, the number of milliseconds to delay between
  2060. page writes. The default is zero milliseconds.
  2061. - CONFIG_SYS_I2C_EEPROM_ADDR_LEN:
  2062. The length in bytes of the EEPROM memory array address. Note
  2063. that this is NOT the chip address length!
  2064. - CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW:
  2065. EEPROM chips that implement "address overflow" are ones
  2066. like Catalyst 24WC04/08/16 which has 9/10/11 bits of
  2067. address and the extra bits end up in the "chip address" bit
  2068. slots. This makes a 24WC08 (1Kbyte) chip look like four 256
  2069. byte chips.
  2070. Note that we consider the length of the address field to
  2071. still be one byte because the extra address bits are hidden
  2072. in the chip address.
  2073. - CONFIG_SYS_EEPROM_SIZE:
  2074. The size in bytes of the EEPROM device.
  2075. - CONFIG_ENV_EEPROM_IS_ON_I2C
  2076. define this, if you have I2C and SPI activated, and your
  2077. EEPROM, which holds the environment, is on the I2C bus.
  2078. - CONFIG_I2C_ENV_EEPROM_BUS
  2079. if you have an Environment on an EEPROM reached over
  2080. I2C muxes, you can define here, how to reach this
  2081. EEPROM. For example:
  2082. #define CONFIG_I2C_ENV_EEPROM_BUS "pca9547:70:d\0"
  2083. EEPROM which holds the environment, is reached over
  2084. a pca9547 i2c mux with address 0x70, channel 3.
  2085. - CONFIG_ENV_IS_IN_DATAFLASH:
  2086. Define this if you have a DataFlash memory device which you
  2087. want to use for the environment.
  2088. - CONFIG_ENV_OFFSET:
  2089. - CONFIG_ENV_ADDR:
  2090. - CONFIG_ENV_SIZE:
  2091. These three #defines specify the offset and size of the
  2092. environment area within the total memory of your DataFlash placed
  2093. at the specified address.
  2094. - CONFIG_ENV_IS_IN_NAND:
  2095. Define this if you have a NAND device which you want to use
  2096. for the environment.
  2097. - CONFIG_ENV_OFFSET:
  2098. - CONFIG_ENV_SIZE:
  2099. These two #defines specify the offset and size of the environment
  2100. area within the first NAND device. CONFIG_ENV_OFFSET must be
  2101. aligned to an erase block boundary.
  2102. - CONFIG_ENV_OFFSET_REDUND (optional):
  2103. This setting describes a second storage area of CONFIG_ENV_SIZE
  2104. size used to hold a redundant copy of the environment data, so
  2105. that there is a valid backup copy in case there is a power failure
  2106. during a "saveenv" operation. CONFIG_ENV_OFFSET_RENDUND must be
  2107. aligned to an erase block boundary.
  2108. - CONFIG_ENV_RANGE (optional):
  2109. Specifies the length of the region in which the environment
  2110. can be written. This should be a multiple of the NAND device's
  2111. block size. Specifying a range with more erase blocks than
  2112. are needed to hold CONFIG_ENV_SIZE allows bad blocks within
  2113. the range to be avoided.
  2114. - CONFIG_ENV_OFFSET_OOB (optional):
  2115. Enables support for dynamically retrieving the offset of the
  2116. environment from block zero's out-of-band data. The
  2117. "nand env.oob" command can be used to record this offset.
  2118. Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
  2119. using CONFIG_ENV_OFFSET_OOB.
  2120. - CONFIG_NAND_ENV_DST
  2121. Defines address in RAM to which the nand_spl code should copy the
  2122. environment. If redundant environment is used, it will be copied to
  2123. CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE.
  2124. - CONFIG_SYS_SPI_INIT_OFFSET
  2125. Defines offset to the initial SPI buffer area in DPRAM. The
  2126. area is used at an early stage (ROM part) if the environment
  2127. is configured to reside in the SPI EEPROM: We need a 520 byte
  2128. scratch DPRAM area. It is used between the two initialization
  2129. calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
  2130. to be a good choice since it makes it far enough from the
  2131. start of the data area as well as from the stack pointer.
  2132. Please note that the environment is read-only until the monitor
  2133. has been relocated to RAM and a RAM copy of the environment has been
  2134. created; also, when using EEPROM you will have to use getenv_f()
  2135. until then to read environment variables.
  2136. The environment is protected by a CRC32 checksum. Before the monitor
  2137. is relocated into RAM, as a result of a bad CRC you will be working
  2138. with the compiled-in default environment - *silently*!!! [This is
  2139. necessary, because the first environment variable we need is the
  2140. "baudrate" setting for the console - if we have a bad CRC, we don't
  2141. have any device yet where we could complain.]
  2142. Note: once the monitor has been relocated, then it will complain if
  2143. the default environment is used; a new CRC is computed as soon as you
  2144. use the "saveenv" command to store a valid environment.
  2145. - CONFIG_SYS_FAULT_ECHO_LINK_DOWN:
  2146. Echo the inverted Ethernet link state to the fault LED.
  2147. Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR
  2148. also needs to be defined.
  2149. - CONFIG_SYS_FAULT_MII_ADDR:
  2150. MII address of the PHY to check for the Ethernet link state.
  2151. - CONFIG_NS16550_MIN_FUNCTIONS:
  2152. Define this if you desire to only have use of the NS16550_init
  2153. and NS16550_putc functions for the serial driver located at
  2154. drivers/serial/ns16550.c. This option is useful for saving
  2155. space for already greatly restricted images, including but not
  2156. limited to NAND_SPL configurations.
  2157. Low Level (hardware related) configuration options:
  2158. ---------------------------------------------------
  2159. - CONFIG_SYS_CACHELINE_SIZE:
  2160. Cache Line Size of the CPU.
  2161. - CONFIG_SYS_DEFAULT_IMMR:
  2162. Default address of the IMMR after system reset.
  2163. Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
  2164. and RPXsuper) to be able to adjust the position of
  2165. the IMMR register after a reset.
  2166. - Floppy Disk Support:
  2167. CONFIG_SYS_FDC_DRIVE_NUMBER
  2168. the default drive number (default value 0)
  2169. CONFIG_SYS_ISA_IO_STRIDE
  2170. defines the spacing between FDC chipset registers
  2171. (default value 1)
  2172. CONFIG_SYS_ISA_IO_OFFSET
  2173. defines the offset of register from address. It
  2174. depends on which part of the data bus is connected to
  2175. the FDC chipset. (default value 0)
  2176. If CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and
  2177. CONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their
  2178. default value.
  2179. if CONFIG_SYS_FDC_HW_INIT is defined, then the function
  2180. fdc_hw_init() is called at the beginning of the FDC
  2181. setup. fdc_hw_init() must be provided by the board
  2182. source code. It is used to make hardware dependant
  2183. initializations.
  2184. - CONFIG_IDE_AHB:
  2185. Most IDE controllers were designed to be connected with PCI
  2186. interface. Only few of them were designed for AHB interface.
  2187. When software is doing ATA command and data transfer to
  2188. IDE devices through IDE-AHB controller, some additional
  2189. registers accessing to these kind of IDE-AHB controller
  2190. is requierd.
  2191. - CONFIG_SYS_IMMR: Physical address of the Internal Memory.
  2192. DO NOT CHANGE unless you know exactly what you're
  2193. doing! (11-4) [MPC8xx/82xx systems only]
  2194. - CONFIG_SYS_INIT_RAM_ADDR:
  2195. Start address of memory area that can be used for
  2196. initial data and stack; please note that this must be
  2197. writable memory that is working WITHOUT special
  2198. initialization, i. e. you CANNOT use normal RAM which
  2199. will become available only after programming the
  2200. memory controller and running certain initialization
  2201. sequences.
  2202. U-Boot uses the following memory types:
  2203. - MPC8xx and MPC8260: IMMR (internal memory of the CPU)
  2204. - MPC824X: data cache
  2205. - PPC4xx: data cache
  2206. - CONFIG_SYS_GBL_DATA_OFFSET:
  2207. Offset of the initial data structure in the memory
  2208. area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually
  2209. CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial
  2210. data is located at the end of the available space
  2211. (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE -
  2212. CONFIG_SYS_INIT_DATA_SIZE), and the initial stack is just
  2213. below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR +
  2214. CONFIG_SYS_GBL_DATA_OFFSET) downward.
  2215. Note:
  2216. On the MPC824X (or other systems that use the data
  2217. cache for initial memory) the address chosen for
  2218. CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must
  2219. point to an otherwise UNUSED address space between
  2220. the top of RAM and the start of the PCI space.
  2221. - CONFIG_SYS_SIUMCR: SIU Module Configuration (11-6)
  2222. - CONFIG_SYS_SYPCR: System Protection Control (11-9)
  2223. - CONFIG_SYS_TBSCR: Time Base Status and Control (11-26)
  2224. - CONFIG_SYS_PISCR: Periodic Interrupt Status and Control (11-31)
  2225. - CONFIG_SYS_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30)
  2226. - CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27)
  2227. - CONFIG_SYS_OR_TIMING_SDRAM:
  2228. SDRAM timing
  2229. - CONFIG_SYS_MAMR_PTA:
  2230. periodic timer for refresh
  2231. - CONFIG_SYS_DER: Debug Event Register (37-47)
  2232. - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM,
  2233. CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP,
  2234. CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM,
  2235. CONFIG_SYS_BR1_PRELIM:
  2236. Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
  2237. - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
  2238. CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM,
  2239. CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM:
  2240. Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
  2241. - CONFIG_SYS_MAMR_PTA, CONFIG_SYS_MPTPR_2BK_4K, CONFIG_SYS_MPTPR_1BK_4K, CONFIG_SYS_MPTPR_2BK_8K,
  2242. CONFIG_SYS_MPTPR_1BK_8K, CONFIG_SYS_MAMR_8COL, CONFIG_SYS_MAMR_9COL:
  2243. Machine Mode Register and Memory Periodic Timer
  2244. Prescaler definitions (SDRAM timing)
  2245. - CONFIG_SYS_I2C_UCODE_PATCH, CONFIG_SYS_I2C_DPMEM_OFFSET [0x1FC0]:
  2246. enable I2C microcode relocation patch (MPC8xx);
  2247. define relocation offset in DPRAM [DSP2]
  2248. - CONFIG_SYS_SMC_UCODE_PATCH, CONFIG_SYS_SMC_DPMEM_OFFSET [0x1FC0]:
  2249. enable SMC microcode relocation patch (MPC8xx);
  2250. define relocation offset in DPRAM [SMC1]
  2251. - CONFIG_SYS_SPI_UCODE_PATCH, CONFIG_SYS_SPI_DPMEM_OFFSET [0x1FC0]:
  2252. enable SPI microcode relocation patch (MPC8xx);
  2253. define relocation offset in DPRAM [SCC4]
  2254. - CONFIG_SYS_USE_OSCCLK:
  2255. Use OSCM clock mode on MBX8xx board. Be careful,
  2256. wrong setting might damage your board. Read
  2257. doc/README.MBX before setting this variable!
  2258. - CONFIG_SYS_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
  2259. Offset of the bootmode word in DPRAM used by post
  2260. (Power On Self Tests). This definition overrides
  2261. #define'd default value in commproc.h resp.
  2262. cpm_8260.h.
  2263. - CONFIG_SYS_PCI_SLV_MEM_LOCAL, CONFIG_SYS_PCI_SLV_MEM_BUS, CONFIG_SYS_PICMR0_MASK_ATTRIB,
  2264. CONFIG_SYS_PCI_MSTR0_LOCAL, CONFIG_SYS_PCIMSK0_MASK, CONFIG_SYS_PCI_MSTR1_LOCAL,
  2265. CONFIG_SYS_PCIMSK1_MASK, CONFIG_SYS_PCI_MSTR_MEM_LOCAL, CONFIG_SYS_PCI_MSTR_MEM_BUS,
  2266. CONFIG_SYS_CPU_PCI_MEM_START, CONFIG_SYS_PCI_MSTR_MEM_SIZE, CONFIG_SYS_POCMR0_MASK_ATTRIB,
  2267. CONFIG_SYS_PCI_MSTR_MEMIO_LOCAL, CONFIG_SYS_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
  2268. CONFIG_SYS_PCI_MSTR_MEMIO_SIZE, CONFIG_SYS_POCMR1_MASK_ATTRIB, CONFIG_SYS_PCI_MSTR_IO_LOCAL,
  2269. CONFIG_SYS_PCI_MSTR_IO_BUS, CONFIG_SYS_CPU_PCI_IO_START, CONFIG_SYS_PCI_MSTR_IO_SIZE,
  2270. CONFIG_SYS_POCMR2_MASK_ATTRIB: (MPC826x only)
  2271. Overrides the default PCI memory map in arch/powerpc/cpu/mpc8260/pci.c if set.
  2272. - CONFIG_PCI_DISABLE_PCIE:
  2273. Disable PCI-Express on systems where it is supported but not
  2274. required.
  2275. - CONFIG_SYS_SRIO:
  2276. Chip has SRIO or not
  2277. - CONFIG_SRIO1:
  2278. Board has SRIO 1 port available
  2279. - CONFIG_SRIO2:
  2280. Board has SRIO 2 port available
  2281. - CONFIG_SYS_SRIOn_MEM_VIRT:
  2282. Virtual Address of SRIO port 'n' memory region
  2283. - CONFIG_SYS_SRIOn_MEM_PHYS:
  2284. Physical Address of SRIO port 'n' memory region
  2285. - CONFIG_SYS_SRIOn_MEM_SIZE:
  2286. Size of SRIO port 'n' memory region
  2287. - CONFIG_SYS_NDFC_16
  2288. Defined to tell the NDFC that the NAND chip is using a
  2289. 16 bit bus.
  2290. - CONFIG_SYS_NDFC_EBC0_CFG
  2291. Sets the EBC0_CFG register for the NDFC. If not defined
  2292. a default value will be used.
  2293. - CONFIG_SPD_EEPROM
  2294. Get DDR timing information from an I2C EEPROM. Common
  2295. with pluggable memory modules such as SODIMMs
  2296. SPD_EEPROM_ADDRESS
  2297. I2C address of the SPD EEPROM
  2298. - CONFIG_SYS_SPD_BUS_NUM
  2299. If SPD EEPROM is on an I2C bus other than the first
  2300. one, specify here. Note that the value must resolve
  2301. to something your driver can deal with.
  2302. - CONFIG_SYS_DDR_RAW_TIMING
  2303. Get DDR timing information from other than SPD. Common with
  2304. soldered DDR chips onboard without SPD. DDR raw timing
  2305. parameters are extracted from datasheet and hard-coded into
  2306. header files or board specific files.
  2307. - CONFIG_SYS_83XX_DDR_USES_CS0
  2308. Only for 83xx systems. If specified, then DDR should
  2309. be configured using CS0 and CS1 instead of CS2 and CS3.
  2310. - CONFIG_ETHER_ON_FEC[12]
  2311. Define to enable FEC[12] on a 8xx series processor.
  2312. - CONFIG_FEC[12]_PHY
  2313. Define to the hardcoded PHY address which corresponds
  2314. to the given FEC; i. e.
  2315. #define CONFIG_FEC1_PHY 4
  2316. means that the PHY with address 4 is connected to FEC1
  2317. When set to -1, means to probe for first available.
  2318. - CONFIG_FEC[12]_PHY_NORXERR
  2319. The PHY does not have a RXERR line (RMII only).
  2320. (so program the FEC to ignore it).
  2321. - CONFIG_RMII
  2322. Enable RMII mode for all FECs.
  2323. Note that this is a global option, we can't
  2324. have one FEC in standard MII mode and another in RMII mode.
  2325. - CONFIG_CRC32_VERIFY
  2326. Add a verify option to the crc32 command.
  2327. The syntax is:
  2328. => crc32 -v <address> <count> <crc32>
  2329. Where address/count indicate a memory area
  2330. and crc32 is the correct crc32 which the
  2331. area should have.
  2332. - CONFIG_LOOPW
  2333. Add the "loopw" memory command. This only takes effect if
  2334. the memory commands are activated globally (CONFIG_CMD_MEM).
  2335. - CONFIG_MX_CYCLIC
  2336. Add the "mdc" and "mwc" memory commands. These are cyclic
  2337. "md/mw" commands.
  2338. Examples:
  2339. => mdc.b 10 4 500
  2340. This command will print 4 bytes (10,11,12,13) each 500 ms.
  2341. => mwc.l 100 12345678 10
  2342. This command will write 12345678 to address 100 all 10 ms.
  2343. This only takes effect if the memory commands are activated
  2344. globally (CONFIG_CMD_MEM).
  2345. - CONFIG_SKIP_LOWLEVEL_INIT
  2346. [ARM only] If this variable is defined, then certain
  2347. low level initializations (like setting up the memory
  2348. controller) are omitted and/or U-Boot does not
  2349. relocate itself into RAM.
  2350. Normally this variable MUST NOT be defined. The only
  2351. exception is when U-Boot is loaded (to RAM) by some
  2352. other boot loader or by a debugger which performs
  2353. these initializations itself.
  2354. - CONFIG_SPL_BUILD
  2355. Modifies the behaviour of start.S when compiling a loader
  2356. that is executed before the actual U-Boot. E.g. when
  2357. compiling a NAND SPL.
  2358. - CONFIG_USE_ARCH_MEMCPY
  2359. CONFIG_USE_ARCH_MEMSET
  2360. If these options are used a optimized version of memcpy/memset will
  2361. be used if available. These functions may be faster under some
  2362. conditions but may increase the binary size.
  2363. Building the Software:
  2364. ======================
  2365. Building U-Boot has been tested in several native build environments
  2366. and in many different cross environments. Of course we cannot support
  2367. all possibly existing versions of cross development tools in all
  2368. (potentially obsolete) versions. In case of tool chain problems we
  2369. recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK)
  2370. which is extensively used to build and test U-Boot.
  2371. If you are not using a native environment, it is assumed that you
  2372. have GNU cross compiling tools available in your path. In this case,
  2373. you must set the environment variable CROSS_COMPILE in your shell.
  2374. Note that no changes to the Makefile or any other source files are
  2375. necessary. For example using the ELDK on a 4xx CPU, please enter:
  2376. $ CROSS_COMPILE=ppc_4xx-
  2377. $ export CROSS_COMPILE
  2378. Note: If you wish to generate Windows versions of the utilities in
  2379. the tools directory you can use the MinGW toolchain
  2380. (http://www.mingw.org). Set your HOST tools to the MinGW
  2381. toolchain and execute 'make tools'. For example:
  2382. $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools
  2383. Binaries such as tools/mkimage.exe will be created which can
  2384. be executed on computers running Windows.
  2385. U-Boot is intended to be simple to build. After installing the
  2386. sources you must configure U-Boot for one specific board type. This
  2387. is done by typing:
  2388. make NAME_config
  2389. where "NAME_config" is the name of one of the existing configu-
  2390. rations; see the main Makefile for supported names.
  2391. Note: for some board special configuration names may exist; check if
  2392. additional information is available from the board vendor; for
  2393. instance, the TQM823L systems are available without (standard)
  2394. or with LCD support. You can select such additional "features"
  2395. when choosing the configuration, i. e.
  2396. make TQM823L_config
  2397. - will configure for a plain TQM823L, i. e. no LCD support
  2398. make TQM823L_LCD_config
  2399. - will configure for a TQM823L with U-Boot console on LCD
  2400. etc.
  2401. Finally, type "make all", and you should get some working U-Boot
  2402. images ready for download to / installation on your system:
  2403. - "u-boot.bin" is a raw binary image
  2404. - "u-boot" is an image in ELF binary format
  2405. - "u-boot.srec" is in Motorola S-Record format
  2406. By default the build is performed locally and the objects are saved
  2407. in the source directory. One of the two methods can be used to change
  2408. this behavior and build U-Boot to some external directory:
  2409. 1. Add O= to the make command line invocations:
  2410. make O=/tmp/build distclean
  2411. make O=/tmp/build NAME_config
  2412. make O=/tmp/build all
  2413. 2. Set environment variable BUILD_DIR to point to the desired location:
  2414. export BUILD_DIR=/tmp/build
  2415. make distclean
  2416. make NAME_config
  2417. make all
  2418. Note that the command line "O=" setting overrides the BUILD_DIR environment
  2419. variable.
  2420. Please be aware that the Makefiles assume you are using GNU make, so
  2421. for instance on NetBSD you might need to use "gmake" instead of
  2422. native "make".
  2423. If the system board that you have is not listed, then you will need
  2424. to port U-Boot to your hardware platform. To do this, follow these
  2425. steps:
  2426. 1. Add a new configuration option for your board to the toplevel
  2427. "Makefile" and to the "MAKEALL" script, using the existing
  2428. entries as examples. Note that here and at many other places
  2429. boards and other names are listed in alphabetical sort order. Please
  2430. keep this order.
  2431. 2. Create a new directory to hold your board specific code. Add any
  2432. files you need. In your board directory, you will need at least
  2433. the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
  2434. 3. Create a new configuration file "include/configs/<board>.h" for
  2435. your board
  2436. 3. If you're porting U-Boot to a new CPU, then also create a new
  2437. directory to hold your CPU specific code. Add any files you need.
  2438. 4. Run "make <board>_config" with your new name.
  2439. 5. Type "make", and you should get a working "u-boot.srec" file
  2440. to be installed on your target system.
  2441. 6. Debug and solve any problems that might arise.
  2442. [Of course, this last step is much harder than it sounds.]
  2443. Testing of U-Boot Modifications, Ports to New Hardware, etc.:
  2444. ==============================================================
  2445. If you have modified U-Boot sources (for instance added a new board
  2446. or support for new devices, a new CPU, etc.) you are expected to
  2447. provide feedback to the other developers. The feedback normally takes
  2448. the form of a "patch", i. e. a context diff against a certain (latest
  2449. official or latest in the git repository) version of U-Boot sources.
  2450. But before you submit such a patch, please verify that your modifi-
  2451. cation did not break existing code. At least make sure that *ALL* of
  2452. the supported boards compile WITHOUT ANY compiler warnings. To do so,
  2453. just run the "MAKEALL" script, which will configure and build U-Boot
  2454. for ALL supported system. Be warned, this will take a while. You can
  2455. select which (cross) compiler to use by passing a `CROSS_COMPILE'
  2456. environment variable to the script, i. e. to use the ELDK cross tools
  2457. you can type
  2458. CROSS_COMPILE=ppc_8xx- MAKEALL
  2459. or to build on a native PowerPC system you can type
  2460. CROSS_COMPILE=' ' MAKEALL
  2461. When using the MAKEALL script, the default behaviour is to build
  2462. U-Boot in the source directory. This location can be changed by
  2463. setting the BUILD_DIR environment variable. Also, for each target
  2464. built, the MAKEALL script saves two log files (<target>.ERR and
  2465. <target>.MAKEALL) in the <source dir>/LOG directory. This default
  2466. location can be changed by setting the MAKEALL_LOGDIR environment
  2467. variable. For example:
  2468. export BUILD_DIR=/tmp/build
  2469. export MAKEALL_LOGDIR=/tmp/log
  2470. CROSS_COMPILE=ppc_8xx- MAKEALL
  2471. With the above settings build objects are saved in the /tmp/build,
  2472. log files are saved in the /tmp/log and the source tree remains clean
  2473. during the whole build process.
  2474. See also "U-Boot Porting Guide" below.
  2475. Monitor Commands - Overview:
  2476. ============================
  2477. go - start application at address 'addr'
  2478. run - run commands in an environment variable
  2479. bootm - boot application image from memory
  2480. bootp - boot image via network using BootP/TFTP protocol
  2481. tftpboot- boot image via network using TFTP protocol
  2482. and env variables "ipaddr" and "serverip"
  2483. (and eventually "gatewayip")
  2484. rarpboot- boot image via network using RARP/TFTP protocol
  2485. diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
  2486. loads - load S-Record file over serial line
  2487. loadb - load binary file over serial line (kermit mode)
  2488. md - memory display
  2489. mm - memory modify (auto-incrementing)
  2490. nm - memory modify (constant address)
  2491. mw - memory write (fill)
  2492. cp - memory copy
  2493. cmp - memory compare
  2494. crc32 - checksum calculation
  2495. i2c - I2C sub-system
  2496. sspi - SPI utility commands
  2497. base - print or set address offset
  2498. printenv- print environment variables
  2499. setenv - set environment variables
  2500. saveenv - save environment variables to persistent storage
  2501. protect - enable or disable FLASH write protection
  2502. erase - erase FLASH memory
  2503. flinfo - print FLASH memory information
  2504. bdinfo - print Board Info structure
  2505. iminfo - print header information for application image
  2506. coninfo - print console devices and informations
  2507. ide - IDE sub-system
  2508. loop - infinite loop on address range
  2509. loopw - infinite write loop on address range
  2510. mtest - simple RAM test
  2511. icache - enable or disable instruction cache
  2512. dcache - enable or disable data cache
  2513. reset - Perform RESET of the CPU
  2514. echo - echo args to console
  2515. version - print monitor version
  2516. help - print online help
  2517. ? - alias for 'help'
  2518. Monitor Commands - Detailed Description:
  2519. ========================================
  2520. TODO.
  2521. For now: just type "help <command>".
  2522. Environment Variables:
  2523. ======================
  2524. U-Boot supports user configuration using Environment Variables which
  2525. can be made persistent by saving to Flash memory.
  2526. Environment Variables are set using "setenv", printed using
  2527. "printenv", and saved to Flash using "saveenv". Using "setenv"
  2528. without a value can be used to delete a variable from the
  2529. environment. As long as you don't save the environment you are
  2530. working with an in-memory copy. In case the Flash area containing the
  2531. environment is erased by accident, a default environment is provided.
  2532. Some configuration options can be set using Environment Variables.
  2533. List of environment variables (most likely not complete):
  2534. baudrate - see CONFIG_BAUDRATE
  2535. bootdelay - see CONFIG_BOOTDELAY
  2536. bootcmd - see CONFIG_BOOTCOMMAND
  2537. bootargs - Boot arguments when booting an RTOS image
  2538. bootfile - Name of the image to load with TFTP
  2539. bootm_low - Memory range available for image processing in the bootm
  2540. command can be restricted. This variable is given as
  2541. a hexadecimal number and defines lowest address allowed
  2542. for use by the bootm command. See also "bootm_size"
  2543. environment variable. Address defined by "bootm_low" is
  2544. also the base of the initial memory mapping for the Linux
  2545. kernel -- see the description of CONFIG_SYS_BOOTMAPSZ and
  2546. bootm_mapsize.
  2547. bootm_mapsize - Size of the initial memory mapping for the Linux kernel.
  2548. This variable is given as a hexadecimal number and it
  2549. defines the size of the memory region starting at base
  2550. address bootm_low that is accessible by the Linux kernel
  2551. during early boot. If unset, CONFIG_SYS_BOOTMAPSZ is used
  2552. as the default value if it is defined, and bootm_size is
  2553. used otherwise.
  2554. bootm_size - Memory range available for image processing in the bootm
  2555. command can be restricted. This variable is given as
  2556. a hexadecimal number and defines the size of the region
  2557. allowed for use by the bootm command. See also "bootm_low"
  2558. environment variable.
  2559. updatefile - Location of the software update file on a TFTP server, used
  2560. by the automatic software update feature. Please refer to
  2561. documentation in doc/README.update for more details.
  2562. autoload - if set to "no" (any string beginning with 'n'),
  2563. "bootp" will just load perform a lookup of the
  2564. configuration from the BOOTP server, but not try to
  2565. load any image using TFTP
  2566. autostart - if set to "yes", an image loaded using the "bootp",
  2567. "rarpboot", "tftpboot" or "diskboot" commands will
  2568. be automatically started (by internally calling
  2569. "bootm")
  2570. If set to "no", a standalone image passed to the
  2571. "bootm" command will be copied to the load address
  2572. (and eventually uncompressed), but NOT be started.
  2573. This can be used to load and uncompress arbitrary
  2574. data.
  2575. fdt_high - if set this restricts the maximum address that the
  2576. flattened device tree will be copied into upon boot.
  2577. If this is set to the special value 0xFFFFFFFF then
  2578. the fdt will not be copied at all on boot. For this
  2579. to work it must reside in writable memory, have
  2580. sufficient padding on the end of it for u-boot to
  2581. add the information it needs into it, and the memory
  2582. must be accessible by the kernel.
  2583. i2cfast - (PPC405GP|PPC405EP only)
  2584. if set to 'y' configures Linux I2C driver for fast
  2585. mode (400kHZ). This environment variable is used in
  2586. initialization code. So, for changes to be effective
  2587. it must be saved and board must be reset.
  2588. initrd_high - restrict positioning of initrd images:
  2589. If this variable is not set, initrd images will be
  2590. copied to the highest possible address in RAM; this
  2591. is usually what you want since it allows for
  2592. maximum initrd size. If for some reason you want to
  2593. make sure that the initrd image is loaded below the
  2594. CONFIG_SYS_BOOTMAPSZ limit, you can set this environment
  2595. variable to a value of "no" or "off" or "0".
  2596. Alternatively, you can set it to a maximum upper
  2597. address to use (U-Boot will still check that it
  2598. does not overwrite the U-Boot stack and data).
  2599. For instance, when you have a system with 16 MB
  2600. RAM, and want to reserve 4 MB from use by Linux,
  2601. you can do this by adding "mem=12M" to the value of
  2602. the "bootargs" variable. However, now you must make
  2603. sure that the initrd image is placed in the first
  2604. 12 MB as well - this can be done with
  2605. setenv initrd_high 00c00000
  2606. If you set initrd_high to 0xFFFFFFFF, this is an
  2607. indication to U-Boot that all addresses are legal
  2608. for the Linux kernel, including addresses in flash
  2609. memory. In this case U-Boot will NOT COPY the
  2610. ramdisk at all. This may be useful to reduce the
  2611. boot time on your system, but requires that this
  2612. feature is supported by your Linux kernel.
  2613. ipaddr - IP address; needed for tftpboot command
  2614. loadaddr - Default load address for commands like "bootp",
  2615. "rarpboot", "tftpboot", "loadb" or "diskboot"
  2616. loads_echo - see CONFIG_LOADS_ECHO
  2617. serverip - TFTP server IP address; needed for tftpboot command
  2618. bootretry - see CONFIG_BOOT_RETRY_TIME
  2619. bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
  2620. bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
  2621. ethprime - When CONFIG_NET_MULTI is enabled controls which
  2622. interface is used first.
  2623. ethact - When CONFIG_NET_MULTI is enabled controls which
  2624. interface is currently active. For example you
  2625. can do the following
  2626. => setenv ethact FEC
  2627. => ping 192.168.0.1 # traffic sent on FEC
  2628. => setenv ethact SCC
  2629. => ping 10.0.0.1 # traffic sent on SCC
  2630. ethrotate - When set to "no" U-Boot does not go through all
  2631. available network interfaces.
  2632. It just stays at the currently selected interface.
  2633. netretry - When set to "no" each network operation will
  2634. either succeed or fail without retrying.
  2635. When set to "once" the network operation will
  2636. fail when all the available network interfaces
  2637. are tried once without success.
  2638. Useful on scripts which control the retry operation
  2639. themselves.
  2640. npe_ucode - set load address for the NPE microcode
  2641. tftpsrcport - If this is set, the value is used for TFTP's
  2642. UDP source port.
  2643. tftpdstport - If this is set, the value is used for TFTP's UDP
  2644. destination port instead of the Well Know Port 69.
  2645. tftpblocksize - Block size to use for TFTP transfers; if not set,
  2646. we use the TFTP server's default block size
  2647. tftptimeout - Retransmission timeout for TFTP packets (in milli-
  2648. seconds, minimum value is 1000 = 1 second). Defines
  2649. when a packet is considered to be lost so it has to
  2650. be retransmitted. The default is 5000 = 5 seconds.
  2651. Lowering this value may make downloads succeed
  2652. faster in networks with high packet loss rates or
  2653. with unreliable TFTP servers.
  2654. vlan - When set to a value < 4095 the traffic over
  2655. Ethernet is encapsulated/received over 802.1q
  2656. VLAN tagged frames.
  2657. The following environment variables may be used and automatically
  2658. updated by the network boot commands ("bootp" and "rarpboot"),
  2659. depending the information provided by your boot server:
  2660. bootfile - see above
  2661. dnsip - IP address of your Domain Name Server
  2662. dnsip2 - IP address of your secondary Domain Name Server
  2663. gatewayip - IP address of the Gateway (Router) to use
  2664. hostname - Target hostname
  2665. ipaddr - see above
  2666. netmask - Subnet Mask
  2667. rootpath - Pathname of the root filesystem on the NFS server
  2668. serverip - see above
  2669. There are two special Environment Variables:
  2670. serial# - contains hardware identification information such
  2671. as type string and/or serial number
  2672. ethaddr - Ethernet address
  2673. These variables can be set only once (usually during manufacturing of
  2674. the board). U-Boot refuses to delete or overwrite these variables
  2675. once they have been set once.
  2676. Further special Environment Variables:
  2677. ver - Contains the U-Boot version string as printed
  2678. with the "version" command. This variable is
  2679. readonly (see CONFIG_VERSION_VARIABLE).
  2680. Please note that changes to some configuration parameters may take
  2681. only effect after the next boot (yes, that's just like Windoze :-).
  2682. Command Line Parsing:
  2683. =====================
  2684. There are two different command line parsers available with U-Boot:
  2685. the old "simple" one, and the much more powerful "hush" shell:
  2686. Old, simple command line parser:
  2687. --------------------------------
  2688. - supports environment variables (through setenv / saveenv commands)
  2689. - several commands on one line, separated by ';'
  2690. - variable substitution using "... ${name} ..." syntax
  2691. - special characters ('$', ';') can be escaped by prefixing with '\',
  2692. for example:
  2693. setenv bootcmd bootm \${address}
  2694. - You can also escape text by enclosing in single apostrophes, for example:
  2695. setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
  2696. Hush shell:
  2697. -----------
  2698. - similar to Bourne shell, with control structures like
  2699. if...then...else...fi, for...do...done; while...do...done,
  2700. until...do...done, ...
  2701. - supports environment ("global") variables (through setenv / saveenv
  2702. commands) and local shell variables (through standard shell syntax
  2703. "name=value"); only environment variables can be used with "run"
  2704. command
  2705. General rules:
  2706. --------------
  2707. (1) If a command line (or an environment variable executed by a "run"
  2708. command) contains several commands separated by semicolon, and
  2709. one of these commands fails, then the remaining commands will be
  2710. executed anyway.
  2711. (2) If you execute several variables with one call to run (i. e.
  2712. calling run with a list of variables as arguments), any failing
  2713. command will cause "run" to terminate, i. e. the remaining
  2714. variables are not executed.
  2715. Note for Redundant Ethernet Interfaces:
  2716. =======================================
  2717. Some boards come with redundant Ethernet interfaces; U-Boot supports
  2718. such configurations and is capable of automatic selection of a
  2719. "working" interface when needed. MAC assignment works as follows:
  2720. Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
  2721. MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
  2722. "eth1addr" (=>eth1), "eth2addr", ...
  2723. If the network interface stores some valid MAC address (for instance
  2724. in SROM), this is used as default address if there is NO correspon-
  2725. ding setting in the environment; if the corresponding environment
  2726. variable is set, this overrides the settings in the card; that means:
  2727. o If the SROM has a valid MAC address, and there is no address in the
  2728. environment, the SROM's address is used.
  2729. o If there is no valid address in the SROM, and a definition in the
  2730. environment exists, then the value from the environment variable is
  2731. used.
  2732. o If both the SROM and the environment contain a MAC address, and
  2733. both addresses are the same, this MAC address is used.
  2734. o If both the SROM and the environment contain a MAC address, and the
  2735. addresses differ, the value from the environment is used and a
  2736. warning is printed.
  2737. o If neither SROM nor the environment contain a MAC address, an error
  2738. is raised.
  2739. If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses
  2740. will be programmed into hardware as part of the initialization process. This
  2741. may be skipped by setting the appropriate 'ethmacskip' environment variable.
  2742. The naming convention is as follows:
  2743. "ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc.
  2744. Image Formats:
  2745. ==============
  2746. U-Boot is capable of booting (and performing other auxiliary operations on)
  2747. images in two formats:
  2748. New uImage format (FIT)
  2749. -----------------------
  2750. Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  2751. to Flattened Device Tree). It allows the use of images with multiple
  2752. components (several kernels, ramdisks, etc.), with contents protected by
  2753. SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory.
  2754. Old uImage format
  2755. -----------------
  2756. Old image format is based on binary files which can be basically anything,
  2757. preceded by a special header; see the definitions in include/image.h for
  2758. details; basically, the header defines the following image properties:
  2759. * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
  2760. 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
  2761. LynxOS, pSOS, QNX, RTEMS, INTEGRITY;
  2762. Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS,
  2763. INTEGRITY).
  2764. * Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86,
  2765. IA64, MIPS, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
  2766. Currently supported: ARM, AVR32, Intel x86, MIPS, Nios II, PowerPC).
  2767. * Compression Type (uncompressed, gzip, bzip2)
  2768. * Load Address
  2769. * Entry Point
  2770. * Image Name
  2771. * Image Timestamp
  2772. The header is marked by a special Magic Number, and both the header
  2773. and the data portions of the image are secured against corruption by
  2774. CRC32 checksums.
  2775. Linux Support:
  2776. ==============
  2777. Although U-Boot should support any OS or standalone application
  2778. easily, the main focus has always been on Linux during the design of
  2779. U-Boot.
  2780. U-Boot includes many features that so far have been part of some
  2781. special "boot loader" code within the Linux kernel. Also, any
  2782. "initrd" images to be used are no longer part of one big Linux image;
  2783. instead, kernel and "initrd" are separate images. This implementation
  2784. serves several purposes:
  2785. - the same features can be used for other OS or standalone
  2786. applications (for instance: using compressed images to reduce the
  2787. Flash memory footprint)
  2788. - it becomes much easier to port new Linux kernel versions because
  2789. lots of low-level, hardware dependent stuff are done by U-Boot
  2790. - the same Linux kernel image can now be used with different "initrd"
  2791. images; of course this also means that different kernel images can
  2792. be run with the same "initrd". This makes testing easier (you don't
  2793. have to build a new "zImage.initrd" Linux image when you just
  2794. change a file in your "initrd"). Also, a field-upgrade of the
  2795. software is easier now.
  2796. Linux HOWTO:
  2797. ============
  2798. Porting Linux to U-Boot based systems:
  2799. ---------------------------------------
  2800. U-Boot cannot save you from doing all the necessary modifications to
  2801. configure the Linux device drivers for use with your target hardware
  2802. (no, we don't intend to provide a full virtual machine interface to
  2803. Linux :-).
  2804. But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot).
  2805. Just make sure your machine specific header file (for instance
  2806. include/asm-ppc/tqm8xx.h) includes the same definition of the Board
  2807. Information structure as we define in include/asm-<arch>/u-boot.h,
  2808. and make sure that your definition of IMAP_ADDR uses the same value
  2809. as your U-Boot configuration in CONFIG_SYS_IMMR.
  2810. Configuring the Linux kernel:
  2811. -----------------------------
  2812. No specific requirements for U-Boot. Make sure you have some root
  2813. device (initial ramdisk, NFS) for your target system.
  2814. Building a Linux Image:
  2815. -----------------------
  2816. With U-Boot, "normal" build targets like "zImage" or "bzImage" are
  2817. not used. If you use recent kernel source, a new build target
  2818. "uImage" will exist which automatically builds an image usable by
  2819. U-Boot. Most older kernels also have support for a "pImage" target,
  2820. which was introduced for our predecessor project PPCBoot and uses a
  2821. 100% compatible format.
  2822. Example:
  2823. make TQM850L_config
  2824. make oldconfig
  2825. make dep
  2826. make uImage
  2827. The "uImage" build target uses a special tool (in 'tools/mkimage') to
  2828. encapsulate a compressed Linux kernel image with header information,
  2829. CRC32 checksum etc. for use with U-Boot. This is what we are doing:
  2830. * build a standard "vmlinux" kernel image (in ELF binary format):
  2831. * convert the kernel into a raw binary image:
  2832. ${CROSS_COMPILE}-objcopy -O binary \
  2833. -R .note -R .comment \
  2834. -S vmlinux linux.bin
  2835. * compress the binary image:
  2836. gzip -9 linux.bin
  2837. * package compressed binary image for U-Boot:
  2838. mkimage -A ppc -O linux -T kernel -C gzip \
  2839. -a 0 -e 0 -n "Linux Kernel Image" \
  2840. -d linux.bin.gz uImage
  2841. The "mkimage" tool can also be used to create ramdisk images for use
  2842. with U-Boot, either separated from the Linux kernel image, or
  2843. combined into one file. "mkimage" encapsulates the images with a 64
  2844. byte header containing information about target architecture,
  2845. operating system, image type, compression method, entry points, time
  2846. stamp, CRC32 checksums, etc.
  2847. "mkimage" can be called in two ways: to verify existing images and
  2848. print the header information, or to build new images.
  2849. In the first form (with "-l" option) mkimage lists the information
  2850. contained in the header of an existing U-Boot image; this includes
  2851. checksum verification:
  2852. tools/mkimage -l image
  2853. -l ==> list image header information
  2854. The second form (with "-d" option) is used to build a U-Boot image
  2855. from a "data file" which is used as image payload:
  2856. tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
  2857. -n name -d data_file image
  2858. -A ==> set architecture to 'arch'
  2859. -O ==> set operating system to 'os'
  2860. -T ==> set image type to 'type'
  2861. -C ==> set compression type 'comp'
  2862. -a ==> set load address to 'addr' (hex)
  2863. -e ==> set entry point to 'ep' (hex)
  2864. -n ==> set image name to 'name'
  2865. -d ==> use image data from 'datafile'
  2866. Right now, all Linux kernels for PowerPC systems use the same load
  2867. address (0x00000000), but the entry point address depends on the
  2868. kernel version:
  2869. - 2.2.x kernels have the entry point at 0x0000000C,
  2870. - 2.3.x and later kernels have the entry point at 0x00000000.
  2871. So a typical call to build a U-Boot image would read:
  2872. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2873. > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
  2874. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \
  2875. > examples/uImage.TQM850L
  2876. Image Name: 2.4.4 kernel for TQM850L
  2877. Created: Wed Jul 19 02:34:59 2000
  2878. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2879. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2880. Load Address: 0x00000000
  2881. Entry Point: 0x00000000
  2882. To verify the contents of the image (or check for corruption):
  2883. -> tools/mkimage -l examples/uImage.TQM850L
  2884. Image Name: 2.4.4 kernel for TQM850L
  2885. Created: Wed Jul 19 02:34:59 2000
  2886. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2887. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2888. Load Address: 0x00000000
  2889. Entry Point: 0x00000000
  2890. NOTE: for embedded systems where boot time is critical you can trade
  2891. speed for memory and install an UNCOMPRESSED image instead: this
  2892. needs more space in Flash, but boots much faster since it does not
  2893. need to be uncompressed:
  2894. -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz
  2895. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2896. > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
  2897. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \
  2898. > examples/uImage.TQM850L-uncompressed
  2899. Image Name: 2.4.4 kernel for TQM850L
  2900. Created: Wed Jul 19 02:34:59 2000
  2901. Image Type: PowerPC Linux Kernel Image (uncompressed)
  2902. Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
  2903. Load Address: 0x00000000
  2904. Entry Point: 0x00000000
  2905. Similar you can build U-Boot images from a 'ramdisk.image.gz' file
  2906. when your kernel is intended to use an initial ramdisk:
  2907. -> tools/mkimage -n 'Simple Ramdisk Image' \
  2908. > -A ppc -O linux -T ramdisk -C gzip \
  2909. > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
  2910. Image Name: Simple Ramdisk Image
  2911. Created: Wed Jan 12 14:01:50 2000
  2912. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2913. Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
  2914. Load Address: 0x00000000
  2915. Entry Point: 0x00000000
  2916. Installing a Linux Image:
  2917. -------------------------
  2918. To downloading a U-Boot image over the serial (console) interface,
  2919. you must convert the image to S-Record format:
  2920. objcopy -I binary -O srec examples/image examples/image.srec
  2921. The 'objcopy' does not understand the information in the U-Boot
  2922. image header, so the resulting S-Record file will be relative to
  2923. address 0x00000000. To load it to a given address, you need to
  2924. specify the target address as 'offset' parameter with the 'loads'
  2925. command.
  2926. Example: install the image to address 0x40100000 (which on the
  2927. TQM8xxL is in the first Flash bank):
  2928. => erase 40100000 401FFFFF
  2929. .......... done
  2930. Erased 8 sectors
  2931. => loads 40100000
  2932. ## Ready for S-Record download ...
  2933. ~>examples/image.srec
  2934. 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
  2935. ...
  2936. 15989 15990 15991 15992
  2937. [file transfer complete]
  2938. [connected]
  2939. ## Start Addr = 0x00000000
  2940. You can check the success of the download using the 'iminfo' command;
  2941. this includes a checksum verification so you can be sure no data
  2942. corruption happened:
  2943. => imi 40100000
  2944. ## Checking Image at 40100000 ...
  2945. Image Name: 2.2.13 for initrd on TQM850L
  2946. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2947. Data Size: 335725 Bytes = 327 kB = 0 MB
  2948. Load Address: 00000000
  2949. Entry Point: 0000000c
  2950. Verifying Checksum ... OK
  2951. Boot Linux:
  2952. -----------
  2953. The "bootm" command is used to boot an application that is stored in
  2954. memory (RAM or Flash). In case of a Linux kernel image, the contents
  2955. of the "bootargs" environment variable is passed to the kernel as
  2956. parameters. You can check and modify this variable using the
  2957. "printenv" and "setenv" commands:
  2958. => printenv bootargs
  2959. bootargs=root=/dev/ram
  2960. => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2961. => printenv bootargs
  2962. bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2963. => bootm 40020000
  2964. ## Booting Linux kernel at 40020000 ...
  2965. Image Name: 2.2.13 for NFS on TQM850L
  2966. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2967. Data Size: 381681 Bytes = 372 kB = 0 MB
  2968. Load Address: 00000000
  2969. Entry Point: 0000000c
  2970. Verifying Checksum ... OK
  2971. Uncompressing Kernel Image ... OK
  2972. 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
  2973. Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2974. time_init: decrementer frequency = 187500000/60
  2975. Calibrating delay loop... 49.77 BogoMIPS
  2976. Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
  2977. ...
  2978. If you want to boot a Linux kernel with initial RAM disk, you pass
  2979. the memory addresses of both the kernel and the initrd image (PPBCOOT
  2980. format!) to the "bootm" command:
  2981. => imi 40100000 40200000
  2982. ## Checking Image at 40100000 ...
  2983. Image Name: 2.2.13 for initrd on TQM850L
  2984. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2985. Data Size: 335725 Bytes = 327 kB = 0 MB
  2986. Load Address: 00000000
  2987. Entry Point: 0000000c
  2988. Verifying Checksum ... OK
  2989. ## Checking Image at 40200000 ...
  2990. Image Name: Simple Ramdisk Image
  2991. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2992. Data Size: 566530 Bytes = 553 kB = 0 MB
  2993. Load Address: 00000000
  2994. Entry Point: 00000000
  2995. Verifying Checksum ... OK
  2996. => bootm 40100000 40200000
  2997. ## Booting Linux kernel at 40100000 ...
  2998. Image Name: 2.2.13 for initrd on TQM850L
  2999. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3000. Data Size: 335725 Bytes = 327 kB = 0 MB
  3001. Load Address: 00000000
  3002. Entry Point: 0000000c
  3003. Verifying Checksum ... OK
  3004. Uncompressing Kernel Image ... OK
  3005. ## Loading RAMDisk Image at 40200000 ...
  3006. Image Name: Simple Ramdisk Image
  3007. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  3008. Data Size: 566530 Bytes = 553 kB = 0 MB
  3009. Load Address: 00000000
  3010. Entry Point: 00000000
  3011. Verifying Checksum ... OK
  3012. Loading Ramdisk ... OK
  3013. 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
  3014. Boot arguments: root=/dev/ram
  3015. time_init: decrementer frequency = 187500000/60
  3016. Calibrating delay loop... 49.77 BogoMIPS
  3017. ...
  3018. RAMDISK: Compressed image found at block 0
  3019. VFS: Mounted root (ext2 filesystem).
  3020. bash#
  3021. Boot Linux and pass a flat device tree:
  3022. -----------
  3023. First, U-Boot must be compiled with the appropriate defines. See the section
  3024. titled "Linux Kernel Interface" above for a more in depth explanation. The
  3025. following is an example of how to start a kernel and pass an updated
  3026. flat device tree:
  3027. => print oftaddr
  3028. oftaddr=0x300000
  3029. => print oft
  3030. oft=oftrees/mpc8540ads.dtb
  3031. => tftp $oftaddr $oft
  3032. Speed: 1000, full duplex
  3033. Using TSEC0 device
  3034. TFTP from server 192.168.1.1; our IP address is 192.168.1.101
  3035. Filename 'oftrees/mpc8540ads.dtb'.
  3036. Load address: 0x300000
  3037. Loading: #
  3038. done
  3039. Bytes transferred = 4106 (100a hex)
  3040. => tftp $loadaddr $bootfile
  3041. Speed: 1000, full duplex
  3042. Using TSEC0 device
  3043. TFTP from server 192.168.1.1; our IP address is 192.168.1.2
  3044. Filename 'uImage'.
  3045. Load address: 0x200000
  3046. Loading:############
  3047. done
  3048. Bytes transferred = 1029407 (fb51f hex)
  3049. => print loadaddr
  3050. loadaddr=200000
  3051. => print oftaddr
  3052. oftaddr=0x300000
  3053. => bootm $loadaddr - $oftaddr
  3054. ## Booting image at 00200000 ...
  3055. Image Name: Linux-2.6.17-dirty
  3056. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3057. Data Size: 1029343 Bytes = 1005.2 kB
  3058. Load Address: 00000000
  3059. Entry Point: 00000000
  3060. Verifying Checksum ... OK
  3061. Uncompressing Kernel Image ... OK
  3062. Booting using flat device tree at 0x300000
  3063. Using MPC85xx ADS machine description
  3064. Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
  3065. [snip]
  3066. More About U-Boot Image Types:
  3067. ------------------------------
  3068. U-Boot supports the following image types:
  3069. "Standalone Programs" are directly runnable in the environment
  3070. provided by U-Boot; it is expected that (if they behave
  3071. well) you can continue to work in U-Boot after return from
  3072. the Standalone Program.
  3073. "OS Kernel Images" are usually images of some Embedded OS which
  3074. will take over control completely. Usually these programs
  3075. will install their own set of exception handlers, device
  3076. drivers, set up the MMU, etc. - this means, that you cannot
  3077. expect to re-enter U-Boot except by resetting the CPU.
  3078. "RAMDisk Images" are more or less just data blocks, and their
  3079. parameters (address, size) are passed to an OS kernel that is
  3080. being started.
  3081. "Multi-File Images" contain several images, typically an OS
  3082. (Linux) kernel image and one or more data images like
  3083. RAMDisks. This construct is useful for instance when you want
  3084. to boot over the network using BOOTP etc., where the boot
  3085. server provides just a single image file, but you want to get
  3086. for instance an OS kernel and a RAMDisk image.
  3087. "Multi-File Images" start with a list of image sizes, each
  3088. image size (in bytes) specified by an "uint32_t" in network
  3089. byte order. This list is terminated by an "(uint32_t)0".
  3090. Immediately after the terminating 0 follow the images, one by
  3091. one, all aligned on "uint32_t" boundaries (size rounded up to
  3092. a multiple of 4 bytes).
  3093. "Firmware Images" are binary images containing firmware (like
  3094. U-Boot or FPGA images) which usually will be programmed to
  3095. flash memory.
  3096. "Script files" are command sequences that will be executed by
  3097. U-Boot's command interpreter; this feature is especially
  3098. useful when you configure U-Boot to use a real shell (hush)
  3099. as command interpreter.
  3100. Standalone HOWTO:
  3101. =================
  3102. One of the features of U-Boot is that you can dynamically load and
  3103. run "standalone" applications, which can use some resources of
  3104. U-Boot like console I/O functions or interrupt services.
  3105. Two simple examples are included with the sources:
  3106. "Hello World" Demo:
  3107. -------------------
  3108. 'examples/hello_world.c' contains a small "Hello World" Demo
  3109. application; it is automatically compiled when you build U-Boot.
  3110. It's configured to run at address 0x00040004, so you can play with it
  3111. like that:
  3112. => loads
  3113. ## Ready for S-Record download ...
  3114. ~>examples/hello_world.srec
  3115. 1 2 3 4 5 6 7 8 9 10 11 ...
  3116. [file transfer complete]
  3117. [connected]
  3118. ## Start Addr = 0x00040004
  3119. => go 40004 Hello World! This is a test.
  3120. ## Starting application at 0x00040004 ...
  3121. Hello World
  3122. argc = 7
  3123. argv[0] = "40004"
  3124. argv[1] = "Hello"
  3125. argv[2] = "World!"
  3126. argv[3] = "This"
  3127. argv[4] = "is"
  3128. argv[5] = "a"
  3129. argv[6] = "test."
  3130. argv[7] = "<NULL>"
  3131. Hit any key to exit ...
  3132. ## Application terminated, rc = 0x0
  3133. Another example, which demonstrates how to register a CPM interrupt
  3134. handler with the U-Boot code, can be found in 'examples/timer.c'.
  3135. Here, a CPM timer is set up to generate an interrupt every second.
  3136. The interrupt service routine is trivial, just printing a '.'
  3137. character, but this is just a demo program. The application can be
  3138. controlled by the following keys:
  3139. ? - print current values og the CPM Timer registers
  3140. b - enable interrupts and start timer
  3141. e - stop timer and disable interrupts
  3142. q - quit application
  3143. => loads
  3144. ## Ready for S-Record download ...
  3145. ~>examples/timer.srec
  3146. 1 2 3 4 5 6 7 8 9 10 11 ...
  3147. [file transfer complete]
  3148. [connected]
  3149. ## Start Addr = 0x00040004
  3150. => go 40004
  3151. ## Starting application at 0x00040004 ...
  3152. TIMERS=0xfff00980
  3153. Using timer 1
  3154. tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
  3155. Hit 'b':
  3156. [q, b, e, ?] Set interval 1000000 us
  3157. Enabling timer
  3158. Hit '?':
  3159. [q, b, e, ?] ........
  3160. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
  3161. Hit '?':
  3162. [q, b, e, ?] .
  3163. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
  3164. Hit '?':
  3165. [q, b, e, ?] .
  3166. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
  3167. Hit '?':
  3168. [q, b, e, ?] .
  3169. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
  3170. Hit 'e':
  3171. [q, b, e, ?] ...Stopping timer
  3172. Hit 'q':
  3173. [q, b, e, ?] ## Application terminated, rc = 0x0
  3174. Minicom warning:
  3175. ================
  3176. Over time, many people have reported problems when trying to use the
  3177. "minicom" terminal emulation program for serial download. I (wd)
  3178. consider minicom to be broken, and recommend not to use it. Under
  3179. Unix, I recommend to use C-Kermit for general purpose use (and
  3180. especially for kermit binary protocol download ("loadb" command), and
  3181. use "cu" for S-Record download ("loads" command).
  3182. Nevertheless, if you absolutely want to use it try adding this
  3183. configuration to your "File transfer protocols" section:
  3184. Name Program Name U/D FullScr IO-Red. Multi
  3185. X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
  3186. Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
  3187. NetBSD Notes:
  3188. =============
  3189. Starting at version 0.9.2, U-Boot supports NetBSD both as host
  3190. (build U-Boot) and target system (boots NetBSD/mpc8xx).
  3191. Building requires a cross environment; it is known to work on
  3192. NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
  3193. need gmake since the Makefiles are not compatible with BSD make).
  3194. Note that the cross-powerpc package does not install include files;
  3195. attempting to build U-Boot will fail because <machine/ansi.h> is
  3196. missing. This file has to be installed and patched manually:
  3197. # cd /usr/pkg/cross/powerpc-netbsd/include
  3198. # mkdir powerpc
  3199. # ln -s powerpc machine
  3200. # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
  3201. # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
  3202. Native builds *don't* work due to incompatibilities between native
  3203. and U-Boot include files.
  3204. Booting assumes that (the first part of) the image booted is a
  3205. stage-2 loader which in turn loads and then invokes the kernel
  3206. proper. Loader sources will eventually appear in the NetBSD source
  3207. tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
  3208. meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
  3209. Implementation Internals:
  3210. =========================
  3211. The following is not intended to be a complete description of every
  3212. implementation detail. However, it should help to understand the
  3213. inner workings of U-Boot and make it easier to port it to custom
  3214. hardware.
  3215. Initial Stack, Global Data:
  3216. ---------------------------
  3217. The implementation of U-Boot is complicated by the fact that U-Boot
  3218. starts running out of ROM (flash memory), usually without access to
  3219. system RAM (because the memory controller is not initialized yet).
  3220. This means that we don't have writable Data or BSS segments, and BSS
  3221. is not initialized as zero. To be able to get a C environment working
  3222. at all, we have to allocate at least a minimal stack. Implementation
  3223. options for this are defined and restricted by the CPU used: Some CPU
  3224. models provide on-chip memory (like the IMMR area on MPC8xx and
  3225. MPC826x processors), on others (parts of) the data cache can be
  3226. locked as (mis-) used as memory, etc.
  3227. Chris Hallinan posted a good summary of these issues to the
  3228. U-Boot mailing list:
  3229. Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
  3230. From: "Chris Hallinan" <clh@net1plus.com>
  3231. Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
  3232. ...
  3233. Correct me if I'm wrong, folks, but the way I understand it
  3234. is this: Using DCACHE as initial RAM for Stack, etc, does not
  3235. require any physical RAM backing up the cache. The cleverness
  3236. is that the cache is being used as a temporary supply of
  3237. necessary storage before the SDRAM controller is setup. It's
  3238. beyond the scope of this list to explain the details, but you
  3239. can see how this works by studying the cache architecture and
  3240. operation in the architecture and processor-specific manuals.
  3241. OCM is On Chip Memory, which I believe the 405GP has 4K. It
  3242. is another option for the system designer to use as an
  3243. initial stack/RAM area prior to SDRAM being available. Either
  3244. option should work for you. Using CS 4 should be fine if your
  3245. board designers haven't used it for something that would
  3246. cause you grief during the initial boot! It is frequently not
  3247. used.
  3248. CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere
  3249. with your processor/board/system design. The default value
  3250. you will find in any recent u-boot distribution in
  3251. walnut.h should work for you. I'd set it to a value larger
  3252. than your SDRAM module. If you have a 64MB SDRAM module, set
  3253. it above 400_0000. Just make sure your board has no resources
  3254. that are supposed to respond to that address! That code in
  3255. start.S has been around a while and should work as is when
  3256. you get the config right.
  3257. -Chris Hallinan
  3258. DS4.COM, Inc.
  3259. It is essential to remember this, since it has some impact on the C
  3260. code for the initialization procedures:
  3261. * Initialized global data (data segment) is read-only. Do not attempt
  3262. to write it.
  3263. * Do not use any uninitialized global data (or implicitely initialized
  3264. as zero data - BSS segment) at all - this is undefined, initiali-
  3265. zation is performed later (when relocating to RAM).
  3266. * Stack space is very limited. Avoid big data buffers or things like
  3267. that.
  3268. Having only the stack as writable memory limits means we cannot use
  3269. normal global data to share information beween the code. But it
  3270. turned out that the implementation of U-Boot can be greatly
  3271. simplified by making a global data structure (gd_t) available to all
  3272. functions. We could pass a pointer to this data as argument to _all_
  3273. functions, but this would bloat the code. Instead we use a feature of
  3274. the GCC compiler (Global Register Variables) to share the data: we
  3275. place a pointer (gd) to the global data into a register which we
  3276. reserve for this purpose.
  3277. When choosing a register for such a purpose we are restricted by the
  3278. relevant (E)ABI specifications for the current architecture, and by
  3279. GCC's implementation.
  3280. For PowerPC, the following registers have specific use:
  3281. R1: stack pointer
  3282. R2: reserved for system use
  3283. R3-R4: parameter passing and return values
  3284. R5-R10: parameter passing
  3285. R13: small data area pointer
  3286. R30: GOT pointer
  3287. R31: frame pointer
  3288. (U-Boot also uses R12 as internal GOT pointer. r12
  3289. is a volatile register so r12 needs to be reset when
  3290. going back and forth between asm and C)
  3291. ==> U-Boot will use R2 to hold a pointer to the global data
  3292. Note: on PPC, we could use a static initializer (since the
  3293. address of the global data structure is known at compile time),
  3294. but it turned out that reserving a register results in somewhat
  3295. smaller code - although the code savings are not that big (on
  3296. average for all boards 752 bytes for the whole U-Boot image,
  3297. 624 text + 127 data).
  3298. On Blackfin, the normal C ABI (except for P3) is followed as documented here:
  3299. http://docs.blackfin.uclinux.org/doku.php?id=application_binary_interface
  3300. ==> U-Boot will use P3 to hold a pointer to the global data
  3301. On ARM, the following registers are used:
  3302. R0: function argument word/integer result
  3303. R1-R3: function argument word
  3304. R9: GOT pointer
  3305. R10: stack limit (used only if stack checking if enabled)
  3306. R11: argument (frame) pointer
  3307. R12: temporary workspace
  3308. R13: stack pointer
  3309. R14: link register
  3310. R15: program counter
  3311. ==> U-Boot will use R8 to hold a pointer to the global data
  3312. On Nios II, the ABI is documented here:
  3313. http://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf
  3314. ==> U-Boot will use gp to hold a pointer to the global data
  3315. Note: on Nios II, we give "-G0" option to gcc and don't use gp
  3316. to access small data sections, so gp is free.
  3317. NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
  3318. or current versions of GCC may "optimize" the code too much.
  3319. Memory Management:
  3320. ------------------
  3321. U-Boot runs in system state and uses physical addresses, i.e. the
  3322. MMU is not used either for address mapping nor for memory protection.
  3323. The available memory is mapped to fixed addresses using the memory
  3324. controller. In this process, a contiguous block is formed for each
  3325. memory type (Flash, SDRAM, SRAM), even when it consists of several
  3326. physical memory banks.
  3327. U-Boot is installed in the first 128 kB of the first Flash bank (on
  3328. TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
  3329. booting and sizing and initializing DRAM, the code relocates itself
  3330. to the upper end of DRAM. Immediately below the U-Boot code some
  3331. memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN
  3332. configuration setting]. Below that, a structure with global Board
  3333. Info data is placed, followed by the stack (growing downward).
  3334. Additionally, some exception handler code is copied to the low 8 kB
  3335. of DRAM (0x00000000 ... 0x00001FFF).
  3336. So a typical memory configuration with 16 MB of DRAM could look like
  3337. this:
  3338. 0x0000 0000 Exception Vector code
  3339. :
  3340. 0x0000 1FFF
  3341. 0x0000 2000 Free for Application Use
  3342. :
  3343. :
  3344. :
  3345. :
  3346. 0x00FB FF20 Monitor Stack (Growing downward)
  3347. 0x00FB FFAC Board Info Data and permanent copy of global data
  3348. 0x00FC 0000 Malloc Arena
  3349. :
  3350. 0x00FD FFFF
  3351. 0x00FE 0000 RAM Copy of Monitor Code
  3352. ... eventually: LCD or video framebuffer
  3353. ... eventually: pRAM (Protected RAM - unchanged by reset)
  3354. 0x00FF FFFF [End of RAM]
  3355. System Initialization:
  3356. ----------------------
  3357. In the reset configuration, U-Boot starts at the reset entry point
  3358. (on most PowerPC systems at address 0x00000100). Because of the reset
  3359. configuration for CS0# this is a mirror of the onboard Flash memory.
  3360. To be able to re-map memory U-Boot then jumps to its link address.
  3361. To be able to implement the initialization code in C, a (small!)
  3362. initial stack is set up in the internal Dual Ported RAM (in case CPUs
  3363. which provide such a feature like MPC8xx or MPC8260), or in a locked
  3364. part of the data cache. After that, U-Boot initializes the CPU core,
  3365. the caches and the SIU.
  3366. Next, all (potentially) available memory banks are mapped using a
  3367. preliminary mapping. For example, we put them on 512 MB boundaries
  3368. (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
  3369. on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
  3370. programmed for SDRAM access. Using the temporary configuration, a
  3371. simple memory test is run that determines the size of the SDRAM
  3372. banks.
  3373. When there is more than one SDRAM bank, and the banks are of
  3374. different size, the largest is mapped first. For equal size, the first
  3375. bank (CS2#) is mapped first. The first mapping is always for address
  3376. 0x00000000, with any additional banks following immediately to create
  3377. contiguous memory starting from 0.
  3378. Then, the monitor installs itself at the upper end of the SDRAM area
  3379. and allocates memory for use by malloc() and for the global Board
  3380. Info data; also, the exception vector code is copied to the low RAM
  3381. pages, and the final stack is set up.
  3382. Only after this relocation will you have a "normal" C environment;
  3383. until that you are restricted in several ways, mostly because you are
  3384. running from ROM, and because the code will have to be relocated to a
  3385. new address in RAM.
  3386. U-Boot Porting Guide:
  3387. ----------------------
  3388. [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
  3389. list, October 2002]
  3390. int main(int argc, char *argv[])
  3391. {
  3392. sighandler_t no_more_time;
  3393. signal(SIGALRM, no_more_time);
  3394. alarm(PROJECT_DEADLINE - toSec (3 * WEEK));
  3395. if (available_money > available_manpower) {
  3396. Pay consultant to port U-Boot;
  3397. return 0;
  3398. }
  3399. Download latest U-Boot source;
  3400. Subscribe to u-boot mailing list;
  3401. if (clueless)
  3402. email("Hi, I am new to U-Boot, how do I get started?");
  3403. while (learning) {
  3404. Read the README file in the top level directory;
  3405. Read http://www.denx.de/twiki/bin/view/DULG/Manual;
  3406. Read applicable doc/*.README;
  3407. Read the source, Luke;
  3408. /* find . -name "*.[chS]" | xargs grep -i <keyword> */
  3409. }
  3410. if (available_money > toLocalCurrency ($2500))
  3411. Buy a BDI3000;
  3412. else
  3413. Add a lot of aggravation and time;
  3414. if (a similar board exists) { /* hopefully... */
  3415. cp -a board/<similar> board/<myboard>
  3416. cp include/configs/<similar>.h include/configs/<myboard>.h
  3417. } else {
  3418. Create your own board support subdirectory;
  3419. Create your own board include/configs/<myboard>.h file;
  3420. }
  3421. Edit new board/<myboard> files
  3422. Edit new include/configs/<myboard>.h
  3423. while (!accepted) {
  3424. while (!running) {
  3425. do {
  3426. Add / modify source code;
  3427. } until (compiles);
  3428. Debug;
  3429. if (clueless)
  3430. email("Hi, I am having problems...");
  3431. }
  3432. Send patch file to the U-Boot email list;
  3433. if (reasonable critiques)
  3434. Incorporate improvements from email list code review;
  3435. else
  3436. Defend code as written;
  3437. }
  3438. return 0;
  3439. }
  3440. void no_more_time (int sig)
  3441. {
  3442. hire_a_guru();
  3443. }
  3444. Coding Standards:
  3445. -----------------
  3446. All contributions to U-Boot should conform to the Linux kernel
  3447. coding style; see the file "Documentation/CodingStyle" and the script
  3448. "scripts/Lindent" in your Linux kernel source directory.
  3449. Source files originating from a different project (for example the
  3450. MTD subsystem) are generally exempt from these guidelines and are not
  3451. reformated to ease subsequent migration to newer versions of those
  3452. sources.
  3453. Please note that U-Boot is implemented in C (and to some small parts in
  3454. Assembler); no C++ is used, so please do not use C++ style comments (//)
  3455. in your code.
  3456. Please also stick to the following formatting rules:
  3457. - remove any trailing white space
  3458. - use TAB characters for indentation and vertical alignment, not spaces
  3459. - make sure NOT to use DOS '\r\n' line feeds
  3460. - do not add more than 2 consecutive empty lines to source files
  3461. - do not add trailing empty lines to source files
  3462. Submissions which do not conform to the standards may be returned
  3463. with a request to reformat the changes.
  3464. Submitting Patches:
  3465. -------------------
  3466. Since the number of patches for U-Boot is growing, we need to
  3467. establish some rules. Submissions which do not conform to these rules
  3468. may be rejected, even when they contain important and valuable stuff.
  3469. Please see http://www.denx.de/wiki/U-Boot/Patches for details.
  3470. Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>;
  3471. see http://lists.denx.de/mailman/listinfo/u-boot
  3472. When you send a patch, please include the following information with
  3473. it:
  3474. * For bug fixes: a description of the bug and how your patch fixes
  3475. this bug. Please try to include a way of demonstrating that the
  3476. patch actually fixes something.
  3477. * For new features: a description of the feature and your
  3478. implementation.
  3479. * A CHANGELOG entry as plaintext (separate from the patch)
  3480. * For major contributions, your entry to the CREDITS file
  3481. * When you add support for a new board, don't forget to add this
  3482. board to the MAINTAINERS file, too.
  3483. * If your patch adds new configuration options, don't forget to
  3484. document these in the README file.
  3485. * The patch itself. If you are using git (which is *strongly*
  3486. recommended) you can easily generate the patch using the
  3487. "git format-patch". If you then use "git send-email" to send it to
  3488. the U-Boot mailing list, you will avoid most of the common problems
  3489. with some other mail clients.
  3490. If you cannot use git, use "diff -purN OLD NEW". If your version of
  3491. diff does not support these options, then get the latest version of
  3492. GNU diff.
  3493. The current directory when running this command shall be the parent
  3494. directory of the U-Boot source tree (i. e. please make sure that
  3495. your patch includes sufficient directory information for the
  3496. affected files).
  3497. We prefer patches as plain text. MIME attachments are discouraged,
  3498. and compressed attachments must not be used.
  3499. * If one logical set of modifications affects or creates several
  3500. files, all these changes shall be submitted in a SINGLE patch file.
  3501. * Changesets that contain different, unrelated modifications shall be
  3502. submitted as SEPARATE patches, one patch per changeset.
  3503. Notes:
  3504. * Before sending the patch, run the MAKEALL script on your patched
  3505. source tree and make sure that no errors or warnings are reported
  3506. for any of the boards.
  3507. * Keep your modifications to the necessary minimum: A patch
  3508. containing several unrelated changes or arbitrary reformats will be
  3509. returned with a request to re-formatting / split it.
  3510. * If you modify existing code, make sure that your new code does not
  3511. add to the memory footprint of the code ;-) Small is beautiful!
  3512. When adding new features, these should compile conditionally only
  3513. (using #ifdef), and the resulting code with the new feature
  3514. disabled must not need more memory than the old code without your
  3515. modification.
  3516. * Remember that there is a size limit of 100 kB per message on the
  3517. u-boot mailing list. Bigger patches will be moderated. If they are
  3518. reasonable and not too big, they will be acknowledged. But patches
  3519. bigger than the size limit should be avoided.