README 158 KB

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