README 184 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952953954955956957958959960961962963964965966967968969970971972973974975976977978979980981982983984985986987988989990991992993994995996997998999100010011002100310041005100610071008100910101011101210131014101510161017101810191020102110221023102410251026102710281029103010311032103310341035103610371038103910401041104210431044104510461047104810491050105110521053105410551056105710581059106010611062106310641065106610671068106910701071107210731074107510761077107810791080108110821083108410851086108710881089109010911092109310941095109610971098109911001101110211031104110511061107110811091110111111121113111411151116111711181119112011211122112311241125112611271128112911301131113211331134113511361137113811391140114111421143114411451146114711481149115011511152115311541155115611571158115911601161116211631164116511661167116811691170117111721173117411751176117711781179118011811182118311841185118611871188118911901191119211931194119511961197119811991200120112021203120412051206120712081209121012111212121312141215121612171218121912201221122212231224122512261227122812291230123112321233123412351236123712381239124012411242124312441245124612471248124912501251125212531254125512561257125812591260126112621263126412651266126712681269127012711272127312741275127612771278127912801281128212831284128512861287128812891290129112921293129412951296129712981299130013011302130313041305130613071308130913101311131213131314131513161317131813191320132113221323132413251326132713281329133013311332133313341335133613371338133913401341134213431344134513461347134813491350135113521353135413551356135713581359136013611362136313641365136613671368136913701371137213731374137513761377137813791380138113821383138413851386138713881389139013911392139313941395139613971398139914001401140214031404140514061407140814091410141114121413141414151416141714181419142014211422142314241425142614271428142914301431143214331434143514361437143814391440144114421443144414451446144714481449145014511452145314541455145614571458145914601461146214631464146514661467146814691470147114721473147414751476147714781479148014811482148314841485148614871488148914901491149214931494149514961497149814991500150115021503150415051506150715081509151015111512151315141515151615171518151915201521152215231524152515261527152815291530153115321533153415351536153715381539154015411542154315441545154615471548154915501551155215531554155515561557155815591560156115621563156415651566156715681569157015711572157315741575157615771578157915801581158215831584158515861587158815891590159115921593159415951596159715981599160016011602160316041605160616071608160916101611161216131614161516161617161816191620162116221623162416251626162716281629163016311632163316341635163616371638163916401641164216431644164516461647164816491650165116521653165416551656165716581659166016611662166316641665166616671668166916701671167216731674167516761677167816791680168116821683168416851686168716881689169016911692169316941695169616971698169917001701170217031704170517061707170817091710171117121713171417151716171717181719172017211722172317241725172617271728172917301731173217331734173517361737173817391740174117421743174417451746174717481749175017511752175317541755175617571758175917601761176217631764176517661767176817691770177117721773177417751776177717781779178017811782178317841785178617871788178917901791179217931794179517961797179817991800180118021803180418051806180718081809181018111812181318141815181618171818181918201821182218231824182518261827182818291830183118321833183418351836183718381839184018411842184318441845184618471848184918501851185218531854185518561857185818591860186118621863186418651866186718681869187018711872187318741875187618771878187918801881188218831884188518861887188818891890189118921893189418951896189718981899190019011902190319041905190619071908190919101911191219131914191519161917191819191920192119221923192419251926192719281929193019311932193319341935193619371938193919401941194219431944194519461947194819491950195119521953195419551956195719581959196019611962196319641965196619671968196919701971197219731974197519761977197819791980198119821983198419851986198719881989199019911992199319941995199619971998199920002001200220032004200520062007200820092010201120122013201420152016201720182019202020212022202320242025202620272028202920302031203220332034203520362037203820392040204120422043204420452046204720482049205020512052205320542055205620572058205920602061206220632064206520662067206820692070207120722073207420752076207720782079208020812082208320842085208620872088208920902091209220932094209520962097209820992100210121022103210421052106210721082109211021112112211321142115211621172118211921202121212221232124212521262127212821292130213121322133213421352136213721382139214021412142214321442145214621472148214921502151215221532154215521562157215821592160216121622163216421652166216721682169217021712172217321742175217621772178217921802181218221832184218521862187218821892190219121922193219421952196219721982199220022012202220322042205220622072208220922102211221222132214221522162217221822192220222122222223222422252226222722282229223022312232223322342235223622372238223922402241224222432244224522462247224822492250225122522253225422552256225722582259226022612262226322642265226622672268226922702271227222732274227522762277227822792280228122822283228422852286228722882289229022912292229322942295229622972298229923002301230223032304230523062307230823092310231123122313231423152316231723182319232023212322232323242325232623272328232923302331233223332334233523362337233823392340234123422343234423452346234723482349235023512352235323542355235623572358235923602361236223632364236523662367236823692370237123722373237423752376237723782379238023812382238323842385238623872388238923902391239223932394239523962397239823992400240124022403240424052406240724082409241024112412241324142415241624172418241924202421242224232424242524262427242824292430243124322433243424352436243724382439244024412442244324442445244624472448244924502451245224532454245524562457245824592460246124622463246424652466246724682469247024712472247324742475247624772478247924802481248224832484248524862487248824892490249124922493249424952496249724982499250025012502250325042505250625072508250925102511251225132514251525162517251825192520252125222523252425252526252725282529253025312532253325342535253625372538253925402541254225432544254525462547254825492550255125522553255425552556255725582559256025612562256325642565256625672568256925702571257225732574257525762577257825792580258125822583258425852586258725882589259025912592259325942595259625972598259926002601260226032604260526062607260826092610261126122613261426152616261726182619262026212622262326242625262626272628262926302631263226332634263526362637263826392640264126422643264426452646264726482649265026512652265326542655265626572658265926602661266226632664266526662667266826692670267126722673267426752676267726782679268026812682268326842685268626872688268926902691269226932694269526962697269826992700270127022703270427052706270727082709271027112712271327142715271627172718271927202721272227232724272527262727272827292730273127322733273427352736273727382739274027412742274327442745274627472748274927502751275227532754275527562757275827592760276127622763276427652766276727682769277027712772277327742775277627772778277927802781278227832784278527862787278827892790279127922793279427952796279727982799280028012802280328042805280628072808280928102811281228132814281528162817281828192820282128222823282428252826282728282829283028312832283328342835283628372838283928402841284228432844284528462847284828492850285128522853285428552856285728582859286028612862286328642865286628672868286928702871287228732874287528762877287828792880288128822883288428852886288728882889289028912892289328942895289628972898289929002901290229032904290529062907290829092910291129122913291429152916291729182919292029212922292329242925292629272928292929302931293229332934293529362937293829392940294129422943294429452946294729482949295029512952295329542955295629572958295929602961296229632964296529662967296829692970297129722973297429752976297729782979298029812982298329842985298629872988298929902991299229932994299529962997299829993000300130023003300430053006300730083009301030113012301330143015301630173018301930203021302230233024302530263027302830293030303130323033303430353036303730383039304030413042304330443045304630473048304930503051305230533054305530563057305830593060306130623063306430653066306730683069307030713072307330743075307630773078307930803081308230833084308530863087308830893090309130923093309430953096309730983099310031013102310331043105310631073108310931103111311231133114311531163117311831193120312131223123312431253126312731283129313031313132313331343135313631373138313931403141314231433144314531463147314831493150315131523153315431553156315731583159316031613162316331643165316631673168316931703171317231733174317531763177317831793180318131823183318431853186318731883189319031913192319331943195319631973198319932003201320232033204320532063207320832093210321132123213321432153216321732183219322032213222322332243225322632273228322932303231323232333234323532363237323832393240324132423243324432453246324732483249325032513252325332543255325632573258325932603261326232633264326532663267326832693270327132723273327432753276327732783279328032813282328332843285328632873288328932903291329232933294329532963297329832993300330133023303330433053306330733083309331033113312331333143315331633173318331933203321332233233324332533263327332833293330333133323333333433353336333733383339334033413342334333443345334633473348334933503351335233533354335533563357335833593360336133623363336433653366336733683369337033713372337333743375337633773378337933803381338233833384338533863387338833893390339133923393339433953396339733983399340034013402340334043405340634073408340934103411341234133414341534163417341834193420342134223423342434253426342734283429343034313432343334343435343634373438343934403441344234433444344534463447344834493450345134523453345434553456345734583459346034613462346334643465346634673468346934703471347234733474347534763477347834793480348134823483348434853486348734883489349034913492349334943495349634973498349935003501350235033504350535063507350835093510351135123513351435153516351735183519352035213522352335243525352635273528352935303531353235333534353535363537353835393540354135423543354435453546354735483549355035513552355335543555355635573558355935603561356235633564356535663567356835693570357135723573357435753576357735783579358035813582358335843585358635873588358935903591359235933594359535963597359835993600360136023603360436053606360736083609361036113612361336143615361636173618361936203621362236233624362536263627362836293630363136323633363436353636363736383639364036413642364336443645364636473648364936503651365236533654365536563657365836593660366136623663366436653666366736683669367036713672367336743675367636773678367936803681368236833684368536863687368836893690369136923693369436953696369736983699370037013702370337043705370637073708370937103711371237133714371537163717371837193720372137223723372437253726372737283729373037313732373337343735373637373738373937403741374237433744374537463747374837493750375137523753375437553756375737583759376037613762376337643765376637673768376937703771377237733774377537763777377837793780378137823783378437853786378737883789379037913792379337943795379637973798379938003801380238033804380538063807380838093810381138123813381438153816381738183819382038213822382338243825382638273828382938303831383238333834383538363837383838393840384138423843384438453846384738483849385038513852385338543855385638573858385938603861386238633864386538663867386838693870387138723873387438753876387738783879388038813882388338843885388638873888388938903891389238933894389538963897389838993900390139023903390439053906390739083909391039113912391339143915391639173918391939203921392239233924392539263927392839293930393139323933393439353936393739383939394039413942394339443945394639473948394939503951395239533954395539563957395839593960396139623963396439653966396739683969397039713972397339743975397639773978397939803981398239833984398539863987398839893990399139923993399439953996399739983999400040014002400340044005400640074008400940104011401240134014401540164017401840194020402140224023402440254026402740284029403040314032403340344035403640374038403940404041404240434044404540464047404840494050405140524053405440554056405740584059406040614062406340644065406640674068406940704071407240734074407540764077407840794080408140824083408440854086408740884089409040914092409340944095409640974098409941004101410241034104410541064107410841094110411141124113411441154116411741184119412041214122412341244125412641274128412941304131413241334134413541364137413841394140414141424143414441454146414741484149415041514152415341544155415641574158415941604161416241634164416541664167416841694170417141724173417441754176417741784179418041814182418341844185418641874188418941904191419241934194419541964197419841994200420142024203420442054206420742084209421042114212421342144215421642174218421942204221422242234224422542264227422842294230423142324233423442354236423742384239424042414242424342444245424642474248424942504251425242534254425542564257425842594260426142624263426442654266426742684269427042714272427342744275427642774278427942804281428242834284428542864287428842894290429142924293429442954296429742984299430043014302430343044305430643074308430943104311431243134314431543164317431843194320432143224323432443254326432743284329433043314332433343344335433643374338433943404341434243434344434543464347434843494350435143524353435443554356435743584359436043614362436343644365436643674368436943704371437243734374437543764377437843794380438143824383438443854386438743884389439043914392439343944395439643974398439944004401440244034404440544064407440844094410441144124413441444154416441744184419442044214422442344244425442644274428442944304431443244334434443544364437443844394440444144424443444444454446444744484449445044514452445344544455445644574458445944604461446244634464446544664467446844694470447144724473447444754476447744784479448044814482448344844485448644874488448944904491449244934494449544964497449844994500450145024503450445054506450745084509451045114512451345144515451645174518451945204521452245234524452545264527452845294530453145324533453445354536453745384539454045414542454345444545454645474548454945504551455245534554455545564557455845594560456145624563456445654566456745684569457045714572457345744575457645774578457945804581458245834584458545864587458845894590459145924593459445954596459745984599460046014602460346044605460646074608460946104611461246134614461546164617461846194620462146224623462446254626462746284629463046314632463346344635463646374638463946404641464246434644464546464647464846494650465146524653465446554656465746584659466046614662466346644665466646674668466946704671467246734674467546764677467846794680468146824683468446854686468746884689469046914692469346944695469646974698469947004701470247034704470547064707470847094710471147124713471447154716471747184719472047214722472347244725472647274728472947304731473247334734473547364737473847394740474147424743474447454746474747484749475047514752475347544755475647574758475947604761476247634764476547664767476847694770477147724773477447754776477747784779478047814782478347844785478647874788478947904791479247934794479547964797479847994800480148024803480448054806480748084809481048114812481348144815481648174818481948204821482248234824482548264827482848294830483148324833483448354836483748384839484048414842484348444845484648474848484948504851485248534854485548564857485848594860486148624863486448654866486748684869487048714872487348744875487648774878487948804881488248834884488548864887488848894890489148924893489448954896489748984899490049014902490349044905490649074908490949104911491249134914491549164917491849194920492149224923492449254926492749284929493049314932493349344935493649374938493949404941494249434944494549464947494849494950495149524953495449554956495749584959496049614962496349644965496649674968496949704971497249734974497549764977497849794980498149824983498449854986498749884989499049914992499349944995499649974998499950005001500250035004500550065007500850095010501150125013501450155016501750185019502050215022502350245025502650275028502950305031503250335034503550365037503850395040504150425043504450455046504750485049505050515052505350545055505650575058505950605061506250635064506550665067506850695070507150725073507450755076507750785079508050815082508350845085508650875088508950905091509250935094509550965097509850995100510151025103510451055106510751085109511051115112511351145115511651175118511951205121512251235124512551265127512851295130513151325133513451355136513751385139514051415142514351445145514651475148514951505151515251535154515551565157515851595160516151625163516451655166516751685169517051715172517351745175517651775178517951805181518251835184518551865187518851895190519151925193519451955196519751985199520052015202520352045205520652075208520952105211521252135214521552165217521852195220522152225223522452255226522752285229523052315232523352345235523652375238523952405241524252435244524552465247524852495250525152525253525452555256525752585259526052615262526352645265526652675268526952705271527252735274527552765277527852795280
  1. #
  2. # (C) Copyright 2000 - 2013
  3. # Wolfgang Denk, DENX Software Engineering, wd@denx.de.
  4. #
  5. # SPDX-License-Identifier: GPL-2.0+
  6. #
  7. Summary:
  8. ========
  9. This directory contains the source code for U-Boot, a boot loader for
  10. Embedded boards based on PowerPC, ARM, MIPS and several other
  11. processors, which can be installed in a boot ROM and used to
  12. initialize and test the hardware or to download and run application
  13. code.
  14. The development of U-Boot is closely related to Linux: some parts of
  15. the source code originate in the Linux source tree, we have some
  16. header files in common, and special provision has been made to
  17. support booting of Linux images.
  18. Some attention has been paid to make this software easily
  19. configurable and extendable. For instance, all monitor commands are
  20. implemented with the same call interface, so that it's very easy to
  21. add new commands. Also, instead of permanently adding rarely used
  22. code (for instance hardware test utilities) to the monitor, you can
  23. load and run it dynamically.
  24. Status:
  25. =======
  26. In general, all boards for which a configuration option exists in the
  27. Makefile have been tested to some extent and can be considered
  28. "working". In fact, many of them are used in production systems.
  29. In case of problems see the CHANGELOG file to find out who contributed
  30. the specific port. In addition, there are various MAINTAINERS files
  31. scattered throughout the U-Boot source identifying the people or
  32. companies responsible for various boards and subsystems.
  33. Note: As of August, 2010, there is no longer a CHANGELOG file in the
  34. actual U-Boot source tree; however, it can be created dynamically
  35. from the Git log using:
  36. make CHANGELOG
  37. Where to get help:
  38. ==================
  39. In case you have questions about, problems with or contributions for
  40. U-Boot, you should send a message to the U-Boot mailing list at
  41. <u-boot@lists.denx.de>. There is also an archive of previous traffic
  42. on the mailing list - please search the archive before asking FAQ's.
  43. Please see http://lists.denx.de/pipermail/u-boot and
  44. http://dir.gmane.org/gmane.comp.boot-loaders.u-boot
  45. Where to get source code:
  46. =========================
  47. The U-Boot source code is maintained in the Git repository at
  48. git://www.denx.de/git/u-boot.git ; you can browse it online at
  49. http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary
  50. The "snapshot" links on this page allow you to download tarballs of
  51. any version you might be interested in. Official releases are also
  52. available for FTP download from the ftp://ftp.denx.de/pub/u-boot/
  53. directory.
  54. Pre-built (and tested) images are available from
  55. ftp://ftp.denx.de/pub/u-boot/images/
  56. Where we come from:
  57. ===================
  58. - start from 8xxrom sources
  59. - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
  60. - clean up code
  61. - make it easier to add custom boards
  62. - make it possible to add other [PowerPC] CPUs
  63. - extend functions, especially:
  64. * Provide extended interface to Linux boot loader
  65. * S-Record download
  66. * network boot
  67. * PCMCIA / CompactFlash / ATA disk / SCSI ... boot
  68. - create ARMBoot project (http://sourceforge.net/projects/armboot)
  69. - add other CPU families (starting with ARM)
  70. - create U-Boot project (http://sourceforge.net/projects/u-boot)
  71. - current project page: see http://www.denx.de/wiki/U-Boot
  72. Names and Spelling:
  73. ===================
  74. The "official" name of this project is "Das U-Boot". The spelling
  75. "U-Boot" shall be used in all written text (documentation, comments
  76. in source files etc.). Example:
  77. This is the README file for the U-Boot project.
  78. File names etc. shall be based on the string "u-boot". Examples:
  79. include/asm-ppc/u-boot.h
  80. #include <asm/u-boot.h>
  81. Variable names, preprocessor constants etc. shall be either based on
  82. the string "u_boot" or on "U_BOOT". Example:
  83. U_BOOT_VERSION u_boot_logo
  84. IH_OS_U_BOOT u_boot_hush_start
  85. Versioning:
  86. ===========
  87. Starting with the release in October 2008, the names of the releases
  88. were changed from numerical release numbers without deeper meaning
  89. into a time stamp based numbering. Regular releases are identified by
  90. names consisting of the calendar year and month of the release date.
  91. Additional fields (if present) indicate release candidates or bug fix
  92. releases in "stable" maintenance trees.
  93. Examples:
  94. U-Boot v2009.11 - Release November 2009
  95. U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree
  96. U-Boot v2010.09-rc1 - Release candidate 1 for September 2010 release
  97. Directory Hierarchy:
  98. ====================
  99. /arch Architecture specific files
  100. /arc Files generic to ARC architecture
  101. /arm Files generic to ARM architecture
  102. /m68k Files generic to m68k architecture
  103. /microblaze Files generic to microblaze architecture
  104. /mips Files generic to MIPS architecture
  105. /nds32 Files generic to NDS32 architecture
  106. /nios2 Files generic to Altera NIOS2 architecture
  107. /openrisc Files generic to OpenRISC architecture
  108. /powerpc Files generic to PowerPC architecture
  109. /sandbox Files generic to HW-independent "sandbox"
  110. /sh Files generic to SH architecture
  111. /x86 Files generic to x86 architecture
  112. /api Machine/arch independent API for external apps
  113. /board Board dependent files
  114. /cmd U-Boot commands functions
  115. /common Misc architecture independent functions
  116. /configs Board default configuration files
  117. /disk Code for disk drive partition handling
  118. /doc Documentation (don't expect too much)
  119. /drivers Commonly used device drivers
  120. /dts Contains Makefile for building internal U-Boot fdt.
  121. /examples Example code for standalone applications, etc.
  122. /fs Filesystem code (cramfs, ext2, jffs2, etc.)
  123. /include Header Files
  124. /lib Library routines generic to all architectures
  125. /Licenses Various license files
  126. /net Networking code
  127. /post Power On Self Test
  128. /scripts Various build scripts and Makefiles
  129. /test Various unit test files
  130. /tools Tools to build S-Record or U-Boot images, etc.
  131. Software Configuration:
  132. =======================
  133. Configuration is usually done using C preprocessor defines; the
  134. rationale behind that is to avoid dead code whenever possible.
  135. There are two classes of configuration variables:
  136. * Configuration _OPTIONS_:
  137. These are selectable by the user and have names beginning with
  138. "CONFIG_".
  139. * Configuration _SETTINGS_:
  140. These depend on the hardware etc. and should not be meddled with if
  141. you don't know what you're doing; they have names beginning with
  142. "CONFIG_SYS_".
  143. Previously, all configuration was done by hand, which involved creating
  144. symbolic links and editing configuration files manually. More recently,
  145. U-Boot has added the Kbuild infrastructure used by the Linux kernel,
  146. allowing you to use the "make menuconfig" command to configure your
  147. build.
  148. Selection of Processor Architecture and Board Type:
  149. ---------------------------------------------------
  150. For all supported boards there are ready-to-use default
  151. configurations available; just type "make <board_name>_defconfig".
  152. Example: For a TQM823L module type:
  153. cd u-boot
  154. make TQM823L_defconfig
  155. Note: If you're looking for the default configuration file for a board
  156. you're sure used to be there but is now missing, check the file
  157. doc/README.scrapyard for a list of no longer supported boards.
  158. Sandbox Environment:
  159. --------------------
  160. U-Boot can be built natively to run on a Linux host using the 'sandbox'
  161. board. This allows feature development which is not board- or architecture-
  162. specific to be undertaken on a native platform. The sandbox is also used to
  163. run some of U-Boot's tests.
  164. See board/sandbox/README.sandbox for more details.
  165. Board Initialisation Flow:
  166. --------------------------
  167. This is the intended start-up flow for boards. This should apply for both
  168. SPL and U-Boot proper (i.e. they both follow the same rules).
  169. Note: "SPL" stands for "Secondary Program Loader," which is explained in
  170. more detail later in this file.
  171. At present, SPL mostly uses a separate code path, but the function names
  172. and roles of each function are the same. Some boards or architectures
  173. may not conform to this. At least most ARM boards which use
  174. CONFIG_SPL_FRAMEWORK conform to this.
  175. Execution typically starts with an architecture-specific (and possibly
  176. CPU-specific) start.S file, such as:
  177. - arch/arm/cpu/armv7/start.S
  178. - arch/powerpc/cpu/mpc83xx/start.S
  179. - arch/mips/cpu/start.S
  180. and so on. From there, three functions are called; the purpose and
  181. limitations of each of these functions are described below.
  182. lowlevel_init():
  183. - purpose: essential init to permit execution to reach board_init_f()
  184. - no global_data or BSS
  185. - there is no stack (ARMv7 may have one but it will soon be removed)
  186. - must not set up SDRAM or use console
  187. - must only do the bare minimum to allow execution to continue to
  188. board_init_f()
  189. - this is almost never needed
  190. - return normally from this function
  191. board_init_f():
  192. - purpose: set up the machine ready for running board_init_r():
  193. i.e. SDRAM and serial UART
  194. - global_data is available
  195. - stack is in SRAM
  196. - BSS is not available, so you cannot use global/static variables,
  197. only stack variables and global_data
  198. Non-SPL-specific notes:
  199. - dram_init() is called to set up DRAM. If already done in SPL this
  200. can do nothing
  201. SPL-specific notes:
  202. - you can override the entire board_init_f() function with your own
  203. version as needed.
  204. - preloader_console_init() can be called here in extremis
  205. - should set up SDRAM, and anything needed to make the UART work
  206. - these is no need to clear BSS, it will be done by crt0.S
  207. - must return normally from this function (don't call board_init_r()
  208. directly)
  209. Here the BSS is cleared. For SPL, if CONFIG_SPL_STACK_R is defined, then at
  210. this point the stack and global_data are relocated to below
  211. CONFIG_SPL_STACK_R_ADDR. For non-SPL, U-Boot is relocated to run at the top of
  212. memory.
  213. board_init_r():
  214. - purpose: main execution, common code
  215. - global_data is available
  216. - SDRAM is available
  217. - BSS is available, all static/global variables can be used
  218. - execution eventually continues to main_loop()
  219. Non-SPL-specific notes:
  220. - U-Boot is relocated to the top of memory and is now running from
  221. there.
  222. SPL-specific notes:
  223. - stack is optionally in SDRAM, if CONFIG_SPL_STACK_R is defined and
  224. CONFIG_SPL_STACK_R_ADDR points into SDRAM
  225. - preloader_console_init() can be called here - typically this is
  226. done by selecting CONFIG_SPL_BOARD_INIT and then supplying a
  227. spl_board_init() function containing this call
  228. - loads U-Boot or (in falcon mode) Linux
  229. Configuration Options:
  230. ----------------------
  231. Configuration depends on the combination of board and CPU type; all
  232. such information is kept in a configuration file
  233. "include/configs/<board_name>.h".
  234. Example: For a TQM823L module, all configuration settings are in
  235. "include/configs/TQM823L.h".
  236. Many of the options are named exactly as the corresponding Linux
  237. kernel configuration options. The intention is to make it easier to
  238. build a config tool - later.
  239. The following options need to be configured:
  240. - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
  241. - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
  242. - Marvell Family Member
  243. CONFIG_SYS_MVFS - define it if you want to enable
  244. multiple fs option at one time
  245. for marvell soc family
  246. - 85xx CPU Options:
  247. CONFIG_SYS_PPC64
  248. Specifies that the core is a 64-bit PowerPC implementation (implements
  249. the "64" category of the Power ISA). This is necessary for ePAPR
  250. compliance, among other possible reasons.
  251. CONFIG_SYS_FSL_TBCLK_DIV
  252. Defines the core time base clock divider ratio compared to the
  253. system clock. On most PQ3 devices this is 8, on newer QorIQ
  254. devices it can be 16 or 32. The ratio varies from SoC to Soc.
  255. CONFIG_SYS_FSL_PCIE_COMPAT
  256. Defines the string to utilize when trying to match PCIe device
  257. tree nodes for the given platform.
  258. CONFIG_SYS_FSL_ERRATUM_A004510
  259. Enables a workaround for erratum A004510. If set,
  260. then CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and
  261. CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set.
  262. CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV
  263. CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional)
  264. Defines one or two SoC revisions (low 8 bits of SVR)
  265. for which the A004510 workaround should be applied.
  266. The rest of SVR is either not relevant to the decision
  267. of whether the erratum is present (e.g. p2040 versus
  268. p2041) or is implied by the build target, which controls
  269. whether CONFIG_SYS_FSL_ERRATUM_A004510 is set.
  270. See Freescale App Note 4493 for more information about
  271. this erratum.
  272. CONFIG_A003399_NOR_WORKAROUND
  273. Enables a workaround for IFC erratum A003399. It is only
  274. required during NOR boot.
  275. CONFIG_A008044_WORKAROUND
  276. Enables a workaround for T1040/T1042 erratum A008044. It is only
  277. required during NAND boot and valid for Rev 1.0 SoC revision
  278. CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY
  279. This is the value to write into CCSR offset 0x18600
  280. according to the A004510 workaround.
  281. CONFIG_SYS_FSL_DSP_DDR_ADDR
  282. This value denotes start offset of DDR memory which is
  283. connected exclusively to the DSP cores.
  284. CONFIG_SYS_FSL_DSP_M2_RAM_ADDR
  285. This value denotes start offset of M2 memory
  286. which is directly connected to the DSP core.
  287. CONFIG_SYS_FSL_DSP_M3_RAM_ADDR
  288. This value denotes start offset of M3 memory which is directly
  289. connected to the DSP core.
  290. CONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT
  291. This value denotes start offset of DSP CCSR space.
  292. CONFIG_SYS_FSL_SINGLE_SOURCE_CLK
  293. Single Source Clock is clocking mode present in some of FSL SoC's.
  294. In this mode, a single differential clock is used to supply
  295. clocks to the sysclock, ddrclock and usbclock.
  296. CONFIG_SYS_CPC_REINIT_F
  297. This CONFIG is defined when the CPC is configured as SRAM at the
  298. time of U-Boot entry and is required to be re-initialized.
  299. CONFIG_DEEP_SLEEP
  300. Indicates this SoC supports deep sleep feature. If deep sleep is
  301. supported, core will start to execute uboot when wakes up.
  302. - Generic CPU options:
  303. CONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN
  304. Defines the endianess of the CPU. Implementation of those
  305. values is arch specific.
  306. CONFIG_SYS_FSL_DDR
  307. Freescale DDR driver in use. This type of DDR controller is
  308. found in mpc83xx, mpc85xx, mpc86xx as well as some ARM core
  309. SoCs.
  310. CONFIG_SYS_FSL_DDR_ADDR
  311. Freescale DDR memory-mapped register base.
  312. CONFIG_SYS_FSL_DDR_EMU
  313. Specify emulator support for DDR. Some DDR features such as
  314. deskew training are not available.
  315. CONFIG_SYS_FSL_DDRC_GEN1
  316. Freescale DDR1 controller.
  317. CONFIG_SYS_FSL_DDRC_GEN2
  318. Freescale DDR2 controller.
  319. CONFIG_SYS_FSL_DDRC_GEN3
  320. Freescale DDR3 controller.
  321. CONFIG_SYS_FSL_DDRC_GEN4
  322. Freescale DDR4 controller.
  323. CONFIG_SYS_FSL_DDRC_ARM_GEN3
  324. Freescale DDR3 controller for ARM-based SoCs.
  325. CONFIG_SYS_FSL_DDR1
  326. Board config to use DDR1. It can be enabled for SoCs with
  327. Freescale DDR1 or DDR2 controllers, depending on the board
  328. implemetation.
  329. CONFIG_SYS_FSL_DDR2
  330. Board config to use DDR2. It can be enabled for SoCs with
  331. Freescale DDR2 or DDR3 controllers, depending on the board
  332. implementation.
  333. CONFIG_SYS_FSL_DDR3
  334. Board config to use DDR3. It can be enabled for SoCs with
  335. Freescale DDR3 or DDR3L controllers.
  336. CONFIG_SYS_FSL_DDR3L
  337. Board config to use DDR3L. It can be enabled for SoCs with
  338. DDR3L controllers.
  339. CONFIG_SYS_FSL_DDR4
  340. Board config to use DDR4. It can be enabled for SoCs with
  341. DDR4 controllers.
  342. CONFIG_SYS_FSL_IFC_BE
  343. Defines the IFC controller register space as Big Endian
  344. CONFIG_SYS_FSL_IFC_LE
  345. Defines the IFC controller register space as Little Endian
  346. CONFIG_SYS_FSL_IFC_CLK_DIV
  347. Defines divider of platform clock(clock input to IFC controller).
  348. CONFIG_SYS_FSL_LBC_CLK_DIV
  349. Defines divider of platform clock(clock input to eLBC controller).
  350. CONFIG_SYS_FSL_PBL_PBI
  351. It enables addition of RCW (Power on reset configuration) in built image.
  352. Please refer doc/README.pblimage for more details
  353. CONFIG_SYS_FSL_PBL_RCW
  354. It adds PBI(pre-boot instructions) commands in u-boot build image.
  355. PBI commands can be used to configure SoC before it starts the execution.
  356. Please refer doc/README.pblimage for more details
  357. CONFIG_SPL_FSL_PBL
  358. It adds a target to create boot binary having SPL binary in PBI format
  359. concatenated with u-boot binary.
  360. CONFIG_SYS_FSL_DDR_BE
  361. Defines the DDR controller register space as Big Endian
  362. CONFIG_SYS_FSL_DDR_LE
  363. Defines the DDR controller register space as Little Endian
  364. CONFIG_SYS_FSL_DDR_SDRAM_BASE_PHY
  365. Physical address from the view of DDR controllers. It is the
  366. same as CONFIG_SYS_DDR_SDRAM_BASE for all Power SoCs. But
  367. it could be different for ARM SoCs.
  368. CONFIG_SYS_FSL_DDR_INTLV_256B
  369. DDR controller interleaving on 256-byte. This is a special
  370. interleaving mode, handled by Dickens for Freescale layerscape
  371. SoCs with ARM core.
  372. CONFIG_SYS_FSL_DDR_MAIN_NUM_CTRLS
  373. Number of controllers used as main memory.
  374. CONFIG_SYS_FSL_OTHER_DDR_NUM_CTRLS
  375. Number of controllers used for other than main memory.
  376. CONFIG_SYS_FSL_HAS_DP_DDR
  377. Defines the SoC has DP-DDR used for DPAA.
  378. CONFIG_SYS_FSL_SEC_BE
  379. Defines the SEC controller register space as Big Endian
  380. CONFIG_SYS_FSL_SEC_LE
  381. Defines the SEC controller register space as Little Endian
  382. - MIPS CPU options:
  383. CONFIG_SYS_INIT_SP_OFFSET
  384. Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack
  385. pointer. This is needed for the temporary stack before
  386. relocation.
  387. CONFIG_SYS_MIPS_CACHE_MODE
  388. Cache operation mode for the MIPS CPU.
  389. See also arch/mips/include/asm/mipsregs.h.
  390. Possible values are:
  391. CONF_CM_CACHABLE_NO_WA
  392. CONF_CM_CACHABLE_WA
  393. CONF_CM_UNCACHED
  394. CONF_CM_CACHABLE_NONCOHERENT
  395. CONF_CM_CACHABLE_CE
  396. CONF_CM_CACHABLE_COW
  397. CONF_CM_CACHABLE_CUW
  398. CONF_CM_CACHABLE_ACCELERATED
  399. CONFIG_SYS_XWAY_EBU_BOOTCFG
  400. Special option for Lantiq XWAY SoCs for booting from NOR flash.
  401. See also arch/mips/cpu/mips32/start.S.
  402. CONFIG_XWAY_SWAP_BYTES
  403. Enable compilation of tools/xway-swap-bytes needed for Lantiq
  404. XWAY SoCs for booting from NOR flash. The U-Boot image needs to
  405. be swapped if a flash programmer is used.
  406. - ARM options:
  407. CONFIG_SYS_EXCEPTION_VECTORS_HIGH
  408. Select high exception vectors of the ARM core, e.g., do not
  409. clear the V bit of the c1 register of CP15.
  410. COUNTER_FREQUENCY
  411. Generic timer clock source frequency.
  412. COUNTER_FREQUENCY_REAL
  413. Generic timer clock source frequency if the real clock is
  414. different from COUNTER_FREQUENCY, and can only be determined
  415. at run time.
  416. - Tegra SoC options:
  417. CONFIG_TEGRA_SUPPORT_NON_SECURE
  418. Support executing U-Boot in non-secure (NS) mode. Certain
  419. impossible actions will be skipped if the CPU is in NS mode,
  420. such as ARM architectural timer initialization.
  421. - Linux Kernel Interface:
  422. CONFIG_CLOCKS_IN_MHZ
  423. U-Boot stores all clock information in Hz
  424. internally. For binary compatibility with older Linux
  425. kernels (which expect the clocks passed in the
  426. bd_info data to be in MHz) the environment variable
  427. "clocks_in_mhz" can be defined so that U-Boot
  428. converts clock data to MHZ before passing it to the
  429. Linux kernel.
  430. When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
  431. "clocks_in_mhz=1" is automatically included in the
  432. default environment.
  433. CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
  434. When transferring memsize parameter to Linux, some versions
  435. expect it to be in bytes, others in MB.
  436. Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
  437. CONFIG_OF_LIBFDT
  438. New kernel versions are expecting firmware settings to be
  439. passed using flattened device trees (based on open firmware
  440. concepts).
  441. CONFIG_OF_LIBFDT
  442. * New libfdt-based support
  443. * Adds the "fdt" command
  444. * The bootm command automatically updates the fdt
  445. OF_TBCLK - The timebase frequency.
  446. OF_STDOUT_PATH - The path to the console device
  447. boards with QUICC Engines require OF_QE to set UCC MAC
  448. addresses
  449. CONFIG_OF_BOARD_SETUP
  450. Board code has addition modification that it wants to make
  451. to the flat device tree before handing it off to the kernel
  452. CONFIG_OF_SYSTEM_SETUP
  453. Other code has addition modification that it wants to make
  454. to the flat device tree before handing it off to the kernel.
  455. This causes ft_system_setup() to be called before booting
  456. the kernel.
  457. CONFIG_OF_IDE_FIXUP
  458. U-Boot can detect if an IDE device is present or not.
  459. If not, and this new config option is activated, U-Boot
  460. removes the ATA node from the DTS before booting Linux,
  461. so the Linux IDE driver does not probe the device and
  462. crash. This is needed for buggy hardware (uc101) where
  463. no pull down resistor is connected to the signal IDE5V_DD7.
  464. CONFIG_MACH_TYPE [relevant for ARM only][mandatory]
  465. This setting is mandatory for all boards that have only one
  466. machine type and must be used to specify the machine type
  467. number as it appears in the ARM machine registry
  468. (see http://www.arm.linux.org.uk/developer/machines/).
  469. Only boards that have multiple machine types supported
  470. in a single configuration file and the machine type is
  471. runtime discoverable, do not have to use this setting.
  472. - vxWorks boot parameters:
  473. bootvx constructs a valid bootline using the following
  474. environments variables: bootdev, bootfile, ipaddr, netmask,
  475. serverip, gatewayip, hostname, othbootargs.
  476. It loads the vxWorks image pointed bootfile.
  477. Note: If a "bootargs" environment is defined, it will overwride
  478. the defaults discussed just above.
  479. - Cache Configuration:
  480. CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot
  481. CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot
  482. CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
  483. - Cache Configuration for ARM:
  484. CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache
  485. controller
  486. CONFIG_SYS_PL310_BASE - Physical base address of PL310
  487. controller register space
  488. - Serial Ports:
  489. CONFIG_PL010_SERIAL
  490. Define this if you want support for Amba PrimeCell PL010 UARTs.
  491. CONFIG_PL011_SERIAL
  492. Define this if you want support for Amba PrimeCell PL011 UARTs.
  493. CONFIG_PL011_CLOCK
  494. If you have Amba PrimeCell PL011 UARTs, set this variable to
  495. the clock speed of the UARTs.
  496. CONFIG_PL01x_PORTS
  497. If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
  498. define this to a list of base addresses for each (supported)
  499. port. See e.g. include/configs/versatile.h
  500. CONFIG_SERIAL_HW_FLOW_CONTROL
  501. Define this variable to enable hw flow control in serial driver.
  502. Current user of this option is drivers/serial/nsl16550.c driver
  503. - Console Baudrate:
  504. CONFIG_BAUDRATE - in bps
  505. Select one of the baudrates listed in
  506. CONFIG_SYS_BAUDRATE_TABLE, see below.
  507. - Autoboot Command:
  508. CONFIG_BOOTCOMMAND
  509. Only needed when CONFIG_BOOTDELAY is enabled;
  510. define a command string that is automatically executed
  511. when no character is read on the console interface
  512. within "Boot Delay" after reset.
  513. CONFIG_RAMBOOT and CONFIG_NFSBOOT
  514. The value of these goes into the environment as
  515. "ramboot" and "nfsboot" respectively, and can be used
  516. as a convenience, when switching between booting from
  517. RAM and NFS.
  518. - Bootcount:
  519. CONFIG_BOOTCOUNT_LIMIT
  520. Implements a mechanism for detecting a repeating reboot
  521. cycle, see:
  522. http://www.denx.de/wiki/view/DULG/UBootBootCountLimit
  523. CONFIG_BOOTCOUNT_ENV
  524. If no softreset save registers are found on the hardware
  525. "bootcount" is stored in the environment. To prevent a
  526. saveenv on all reboots, the environment variable
  527. "upgrade_available" is used. If "upgrade_available" is
  528. 0, "bootcount" is always 0, if "upgrade_available" is
  529. 1 "bootcount" is incremented in the environment.
  530. So the Userspace Applikation must set the "upgrade_available"
  531. and "bootcount" variable to 0, if a boot was successfully.
  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. - Removal of commands
  558. If no commands are needed to boot, you can disable
  559. CONFIG_CMDLINE to remove them. In this case, the command line
  560. will not be available, and when U-Boot wants to execute the
  561. boot command (on start-up) it will call board_run_command()
  562. instead. This can reduce image size significantly for very
  563. simple boot procedures.
  564. - Regular expression support:
  565. CONFIG_REGEX
  566. If this variable is defined, U-Boot is linked against
  567. the SLRE (Super Light Regular Expression) library,
  568. which adds regex support to some commands, as for
  569. example "env grep" and "setexpr".
  570. - Device tree:
  571. CONFIG_OF_CONTROL
  572. If this variable is defined, U-Boot will use a device tree
  573. to configure its devices, instead of relying on statically
  574. compiled #defines in the board file. This option is
  575. experimental and only available on a few boards. The device
  576. tree is available in the global data as gd->fdt_blob.
  577. U-Boot needs to get its device tree from somewhere. This can
  578. be done using one of the three options below:
  579. CONFIG_OF_EMBED
  580. If this variable is defined, U-Boot will embed a device tree
  581. binary in its image. This device tree file should be in the
  582. board directory and called <soc>-<board>.dts. The binary file
  583. is then picked up in board_init_f() and made available through
  584. the global data structure as gd->blob.
  585. CONFIG_OF_SEPARATE
  586. If this variable is defined, U-Boot will build a device tree
  587. binary. It will be called u-boot.dtb. Architecture-specific
  588. code will locate it at run-time. Generally this works by:
  589. cat u-boot.bin u-boot.dtb >image.bin
  590. and in fact, U-Boot does this for you, creating a file called
  591. u-boot-dtb.bin which is useful in the common case. You can
  592. still use the individual files if you need something more
  593. exotic.
  594. CONFIG_OF_BOARD
  595. If this variable is defined, U-Boot will use the device tree
  596. provided by the board at runtime instead of embedding one with
  597. the image. Only boards defining board_fdt_blob_setup() support
  598. this option (see include/fdtdec.h file).
  599. - Watchdog:
  600. CONFIG_WATCHDOG
  601. If this variable is defined, it enables watchdog
  602. support for the SoC. There must be support in the SoC
  603. specific code for a watchdog. For the 8xx
  604. CPUs, the SIU Watchdog feature is enabled in the SYPCR
  605. register. When supported for a specific SoC is
  606. available, then no further board specific code should
  607. be needed to use it.
  608. CONFIG_HW_WATCHDOG
  609. When using a watchdog circuitry external to the used
  610. SoC, then define this variable and provide board
  611. specific code for the "hw_watchdog_reset" function.
  612. CONFIG_AT91_HW_WDT_TIMEOUT
  613. specify the timeout in seconds. default 2 seconds.
  614. - U-Boot Version:
  615. CONFIG_VERSION_VARIABLE
  616. If this variable is defined, an environment variable
  617. named "ver" is created by U-Boot showing the U-Boot
  618. version as printed by the "version" command.
  619. Any change to this variable will be reverted at the
  620. next reset.
  621. - Real-Time Clock:
  622. When CONFIG_CMD_DATE is selected, the type of the RTC
  623. has to be selected, too. Define exactly one of the
  624. following options:
  625. CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
  626. CONFIG_RTC_MC13XXX - use MC13783 or MC13892 RTC
  627. CONFIG_RTC_MC146818 - use MC146818 RTC
  628. CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
  629. CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
  630. CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
  631. CONFIG_RTC_DS1339 - use Maxim, Inc. DS1339 RTC
  632. CONFIG_RTC_DS164x - use Dallas DS164x RTC
  633. CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
  634. CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
  635. CONFIG_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337
  636. CONFIG_SYS_RV3029_TCR - enable trickle charger on
  637. RV3029 RTC.
  638. Note that if the RTC uses I2C, then the I2C interface
  639. must also be configured. See I2C Support, below.
  640. - GPIO Support:
  641. CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO
  642. The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
  643. chip-ngpio pairs that tell the PCA953X driver the number of
  644. pins supported by a particular chip.
  645. Note that if the GPIO device uses I2C, then the I2C interface
  646. must also be configured. See I2C Support, below.
  647. - I/O tracing:
  648. When CONFIG_IO_TRACE is selected, U-Boot intercepts all I/O
  649. accesses and can checksum them or write a list of them out
  650. to memory. See the 'iotrace' command for details. This is
  651. useful for testing device drivers since it can confirm that
  652. the driver behaves the same way before and after a code
  653. change. Currently this is supported on sandbox and arm. To
  654. add support for your architecture, add '#include <iotrace.h>'
  655. to the bottom of arch/<arch>/include/asm/io.h and test.
  656. Example output from the 'iotrace stats' command is below.
  657. Note that if the trace buffer is exhausted, the checksum will
  658. still continue to operate.
  659. iotrace is enabled
  660. Start: 10000000 (buffer start address)
  661. Size: 00010000 (buffer size)
  662. Offset: 00000120 (current buffer offset)
  663. Output: 10000120 (start + offset)
  664. Count: 00000018 (number of trace records)
  665. CRC32: 9526fb66 (CRC32 of all trace records)
  666. - Timestamp Support:
  667. When CONFIG_TIMESTAMP is selected, the timestamp
  668. (date and time) of an image is printed by image
  669. commands like bootm or iminfo. This option is
  670. automatically enabled when you select CONFIG_CMD_DATE .
  671. - Partition Labels (disklabels) Supported:
  672. Zero or more of the following:
  673. CONFIG_MAC_PARTITION Apple's MacOS partition table.
  674. CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc.
  675. CONFIG_EFI_PARTITION GPT partition table, common when EFI is the
  676. bootloader. Note 2TB partition limit; see
  677. disk/part_efi.c
  678. CONFIG_MTD_PARTITIONS Memory Technology Device partition table.
  679. If IDE or SCSI support is enabled (CONFIG_IDE or
  680. CONFIG_SCSI) you must configure support for at
  681. least one non-MTD partition type as well.
  682. - IDE Reset method:
  683. CONFIG_IDE_RESET_ROUTINE - this is defined in several
  684. board configurations files but used nowhere!
  685. CONFIG_IDE_RESET - is this is defined, IDE Reset will
  686. be performed by calling the function
  687. ide_set_reset(int reset)
  688. which has to be defined in a board specific file
  689. - ATAPI Support:
  690. CONFIG_ATAPI
  691. Set this to enable ATAPI support.
  692. - LBA48 Support
  693. CONFIG_LBA48
  694. Set this to enable support for disks larger than 137GB
  695. Also look at CONFIG_SYS_64BIT_LBA.
  696. Whithout these , LBA48 support uses 32bit variables and will 'only'
  697. support disks up to 2.1TB.
  698. CONFIG_SYS_64BIT_LBA:
  699. When enabled, makes the IDE subsystem use 64bit sector addresses.
  700. Default is 32bit.
  701. - SCSI Support:
  702. CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
  703. CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
  704. CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
  705. maximum numbers of LUNs, SCSI ID's and target
  706. devices.
  707. The environment variable 'scsidevs' is set to the number of
  708. SCSI devices found during the last scan.
  709. - NETWORK Support (PCI):
  710. CONFIG_E1000
  711. Support for Intel 8254x/8257x gigabit chips.
  712. CONFIG_E1000_SPI
  713. Utility code for direct access to the SPI bus on Intel 8257x.
  714. This does not do anything useful unless you set at least one
  715. of CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC.
  716. CONFIG_E1000_SPI_GENERIC
  717. Allow generic access to the SPI bus on the Intel 8257x, for
  718. example with the "sspi" command.
  719. CONFIG_EEPRO100
  720. Support for Intel 82557/82559/82559ER chips.
  721. Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM
  722. write routine for first time initialisation.
  723. CONFIG_TULIP
  724. Support for Digital 2114x chips.
  725. Optional CONFIG_TULIP_SELECT_MEDIA for board specific
  726. modem chip initialisation (KS8761/QS6611).
  727. CONFIG_NATSEMI
  728. Support for National dp83815 chips.
  729. CONFIG_NS8382X
  730. Support for National dp8382[01] gigabit chips.
  731. - NETWORK Support (other):
  732. CONFIG_DRIVER_AT91EMAC
  733. Support for AT91RM9200 EMAC.
  734. CONFIG_RMII
  735. Define this to use reduced MII inteface
  736. CONFIG_DRIVER_AT91EMAC_QUIET
  737. If this defined, the driver is quiet.
  738. The driver doen't show link status messages.
  739. CONFIG_CALXEDA_XGMAC
  740. Support for the Calxeda XGMAC device
  741. CONFIG_LAN91C96
  742. Support for SMSC's LAN91C96 chips.
  743. CONFIG_LAN91C96_USE_32_BIT
  744. Define this to enable 32 bit addressing
  745. CONFIG_SMC91111
  746. Support for SMSC's LAN91C111 chip
  747. CONFIG_SMC91111_BASE
  748. Define this to hold the physical address
  749. of the device (I/O space)
  750. CONFIG_SMC_USE_32_BIT
  751. Define this if data bus is 32 bits
  752. CONFIG_SMC_USE_IOFUNCS
  753. Define this to use i/o functions instead of macros
  754. (some hardware wont work with macros)
  755. CONFIG_DRIVER_TI_EMAC
  756. Support for davinci emac
  757. CONFIG_SYS_DAVINCI_EMAC_PHY_COUNT
  758. Define this if you have more then 3 PHYs.
  759. CONFIG_FTGMAC100
  760. Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
  761. CONFIG_FTGMAC100_EGIGA
  762. Define this to use GE link update with gigabit PHY.
  763. Define this if FTGMAC100 is connected to gigabit PHY.
  764. If your system has 10/100 PHY only, it might not occur
  765. wrong behavior. Because PHY usually return timeout or
  766. useless data when polling gigabit status and gigabit
  767. control registers. This behavior won't affect the
  768. correctnessof 10/100 link speed update.
  769. CONFIG_SMC911X
  770. Support for SMSC's LAN911x and LAN921x chips
  771. CONFIG_SMC911X_BASE
  772. Define this to hold the physical address
  773. of the device (I/O space)
  774. CONFIG_SMC911X_32_BIT
  775. Define this if data bus is 32 bits
  776. CONFIG_SMC911X_16_BIT
  777. Define this if data bus is 16 bits. If your processor
  778. automatically converts one 32 bit word to two 16 bit
  779. words you may also try CONFIG_SMC911X_32_BIT.
  780. CONFIG_SH_ETHER
  781. Support for Renesas on-chip Ethernet controller
  782. CONFIG_SH_ETHER_USE_PORT
  783. Define the number of ports to be used
  784. CONFIG_SH_ETHER_PHY_ADDR
  785. Define the ETH PHY's address
  786. CONFIG_SH_ETHER_CACHE_WRITEBACK
  787. If this option is set, the driver enables cache flush.
  788. - PWM Support:
  789. CONFIG_PWM_IMX
  790. Support for PWM module on the imx6.
  791. - TPM Support:
  792. CONFIG_TPM
  793. Support TPM devices.
  794. CONFIG_TPM_TIS_INFINEON
  795. Support for Infineon i2c bus TPM devices. Only one device
  796. per system is supported at this time.
  797. CONFIG_TPM_TIS_I2C_BURST_LIMITATION
  798. Define the burst count bytes upper limit
  799. CONFIG_TPM_ST33ZP24
  800. Support for STMicroelectronics TPM devices. Requires DM_TPM support.
  801. CONFIG_TPM_ST33ZP24_I2C
  802. Support for STMicroelectronics ST33ZP24 I2C devices.
  803. Requires TPM_ST33ZP24 and I2C.
  804. CONFIG_TPM_ST33ZP24_SPI
  805. Support for STMicroelectronics ST33ZP24 SPI devices.
  806. Requires TPM_ST33ZP24 and SPI.
  807. CONFIG_TPM_ATMEL_TWI
  808. Support for Atmel TWI TPM device. Requires I2C support.
  809. CONFIG_TPM_TIS_LPC
  810. Support for generic parallel port TPM devices. Only one device
  811. per system is supported at this time.
  812. CONFIG_TPM_TIS_BASE_ADDRESS
  813. Base address where the generic TPM device is mapped
  814. to. Contemporary x86 systems usually map it at
  815. 0xfed40000.
  816. CONFIG_TPM
  817. Define this to enable the TPM support library which provides
  818. functional interfaces to some TPM commands.
  819. Requires support for a TPM device.
  820. CONFIG_TPM_AUTH_SESSIONS
  821. Define this to enable authorized functions in the TPM library.
  822. Requires CONFIG_TPM and CONFIG_SHA1.
  823. - USB Support:
  824. At the moment only the UHCI host controller is
  825. supported (PIP405, MIP405); define
  826. CONFIG_USB_UHCI to enable it.
  827. define CONFIG_USB_KEYBOARD to enable the USB Keyboard
  828. and define CONFIG_USB_STORAGE to enable the USB
  829. storage devices.
  830. Note:
  831. Supported are USB Keyboards and USB Floppy drives
  832. (TEAC FD-05PUB).
  833. CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the
  834. txfilltuning field in the EHCI controller on reset.
  835. CONFIG_USB_DWC2_REG_ADDR the physical CPU address of the DWC2
  836. HW module registers.
  837. - USB Device:
  838. Define the below if you wish to use the USB console.
  839. Once firmware is rebuilt from a serial console issue the
  840. command "setenv stdin usbtty; setenv stdout usbtty" and
  841. attach your USB cable. The Unix command "dmesg" should print
  842. it has found a new device. The environment variable usbtty
  843. can be set to gserial or cdc_acm to enable your device to
  844. appear to a USB host as a Linux gserial device or a
  845. Common Device Class Abstract Control Model serial device.
  846. If you select usbtty = gserial you should be able to enumerate
  847. a Linux host by
  848. # modprobe usbserial vendor=0xVendorID product=0xProductID
  849. else if using cdc_acm, simply setting the environment
  850. variable usbtty to be cdc_acm should suffice. The following
  851. might be defined in YourBoardName.h
  852. CONFIG_USB_DEVICE
  853. Define this to build a UDC device
  854. CONFIG_USB_TTY
  855. Define this to have a tty type of device available to
  856. talk to the UDC device
  857. CONFIG_USBD_HS
  858. Define this to enable the high speed support for usb
  859. device and usbtty. If this feature is enabled, a routine
  860. int is_usbd_high_speed(void)
  861. also needs to be defined by the driver to dynamically poll
  862. whether the enumeration has succeded at high speed or full
  863. speed.
  864. CONFIG_SYS_CONSOLE_IS_IN_ENV
  865. Define this if you want stdin, stdout &/or stderr to
  866. be set to usbtty.
  867. If you have a USB-IF assigned VendorID then you may wish to
  868. define your own vendor specific values either in BoardName.h
  869. or directly in usbd_vendor_info.h. If you don't define
  870. CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
  871. CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
  872. should pretend to be a Linux device to it's target host.
  873. CONFIG_USBD_MANUFACTURER
  874. Define this string as the name of your company for
  875. - CONFIG_USBD_MANUFACTURER "my company"
  876. CONFIG_USBD_PRODUCT_NAME
  877. Define this string as the name of your product
  878. - CONFIG_USBD_PRODUCT_NAME "acme usb device"
  879. CONFIG_USBD_VENDORID
  880. Define this as your assigned Vendor ID from the USB
  881. Implementors Forum. This *must* be a genuine Vendor ID
  882. to avoid polluting the USB namespace.
  883. - CONFIG_USBD_VENDORID 0xFFFF
  884. CONFIG_USBD_PRODUCTID
  885. Define this as the unique Product ID
  886. for your device
  887. - CONFIG_USBD_PRODUCTID 0xFFFF
  888. - ULPI Layer Support:
  889. The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via
  890. the generic ULPI layer. The generic layer accesses the ULPI PHY
  891. via the platform viewport, so you need both the genric layer and
  892. the viewport enabled. Currently only Chipidea/ARC based
  893. viewport is supported.
  894. To enable the ULPI layer support, define CONFIG_USB_ULPI and
  895. CONFIG_USB_ULPI_VIEWPORT in your board configuration file.
  896. If your ULPI phy needs a different reference clock than the
  897. standard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to
  898. the appropriate value in Hz.
  899. - MMC Support:
  900. The MMC controller on the Intel PXA is supported. To
  901. enable this define CONFIG_MMC. The MMC can be
  902. accessed from the boot prompt by mapping the device
  903. to physical memory similar to flash. Command line is
  904. enabled with CONFIG_CMD_MMC. The MMC driver also works with
  905. the FAT fs. This is enabled with CONFIG_CMD_FAT.
  906. CONFIG_SH_MMCIF
  907. Support for Renesas on-chip MMCIF controller
  908. CONFIG_SH_MMCIF_ADDR
  909. Define the base address of MMCIF registers
  910. CONFIG_SH_MMCIF_CLK
  911. Define the clock frequency for MMCIF
  912. CONFIG_SUPPORT_EMMC_BOOT
  913. Enable some additional features of the eMMC boot partitions.
  914. CONFIG_SUPPORT_EMMC_RPMB
  915. Enable the commands for reading, writing and programming the
  916. key for the Replay Protection Memory Block partition in eMMC.
  917. - USB Device Firmware Update (DFU) class support:
  918. CONFIG_USB_FUNCTION_DFU
  919. This enables the USB portion of the DFU USB class
  920. CONFIG_DFU_MMC
  921. This enables support for exposing (e)MMC devices via DFU.
  922. CONFIG_DFU_NAND
  923. This enables support for exposing NAND devices via DFU.
  924. CONFIG_DFU_RAM
  925. This enables support for exposing RAM via DFU.
  926. Note: DFU spec refer to non-volatile memory usage, but
  927. allow usages beyond the scope of spec - here RAM usage,
  928. one that would help mostly the developer.
  929. CONFIG_SYS_DFU_DATA_BUF_SIZE
  930. Dfu transfer uses a buffer before writing data to the
  931. raw storage device. Make the size (in bytes) of this buffer
  932. configurable. The size of this buffer is also configurable
  933. through the "dfu_bufsiz" environment variable.
  934. CONFIG_SYS_DFU_MAX_FILE_SIZE
  935. When updating files rather than the raw storage device,
  936. we use a static buffer to copy the file into and then write
  937. the buffer once we've been given the whole file. Define
  938. this to the maximum filesize (in bytes) for the buffer.
  939. Default is 4 MiB if undefined.
  940. DFU_DEFAULT_POLL_TIMEOUT
  941. Poll timeout [ms], is the timeout a device can send to the
  942. host. The host must wait for this timeout before sending
  943. a subsequent DFU_GET_STATUS request to the device.
  944. DFU_MANIFEST_POLL_TIMEOUT
  945. Poll timeout [ms], which the device sends to the host when
  946. entering dfuMANIFEST state. Host waits this timeout, before
  947. sending again an USB request to the device.
  948. - USB Device Android Fastboot support:
  949. CONFIG_USB_FUNCTION_FASTBOOT
  950. This enables the USB part of the fastboot gadget
  951. CONFIG_ANDROID_BOOT_IMAGE
  952. This enables support for booting images which use the Android
  953. image format header.
  954. CONFIG_FASTBOOT_BUF_ADDR
  955. The fastboot protocol requires a large memory buffer for
  956. downloads. Define this to the starting RAM address to use for
  957. downloaded images.
  958. CONFIG_FASTBOOT_BUF_SIZE
  959. The fastboot protocol requires a large memory buffer for
  960. downloads. This buffer should be as large as possible for a
  961. platform. Define this to the size available RAM for fastboot.
  962. CONFIG_FASTBOOT_FLASH
  963. The fastboot protocol includes a "flash" command for writing
  964. the downloaded image to a non-volatile storage device. Define
  965. this to enable the "fastboot flash" command.
  966. CONFIG_FASTBOOT_FLASH_MMC_DEV
  967. The fastboot "flash" command requires additional information
  968. regarding the non-volatile storage device. Define this to
  969. the eMMC device that fastboot should use to store the image.
  970. CONFIG_FASTBOOT_GPT_NAME
  971. The fastboot "flash" command supports writing the downloaded
  972. image to the Protective MBR and the Primary GUID Partition
  973. Table. (Additionally, this downloaded image is post-processed
  974. to generate and write the Backup GUID Partition Table.)
  975. This occurs when the specified "partition name" on the
  976. "fastboot flash" command line matches this value.
  977. The default is "gpt" if undefined.
  978. CONFIG_FASTBOOT_MBR_NAME
  979. The fastboot "flash" command supports writing the downloaded
  980. image to DOS MBR.
  981. This occurs when the "partition name" specified on the
  982. "fastboot flash" command line matches this value.
  983. If not defined the default value "mbr" is used.
  984. - Journaling Flash filesystem support:
  985. CONFIG_JFFS2_NAND
  986. Define these for a default partition on a NAND device
  987. CONFIG_SYS_JFFS2_FIRST_SECTOR,
  988. CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
  989. Define these for a default partition on a NOR device
  990. - Keyboard Support:
  991. See Kconfig help for available keyboard drivers.
  992. CONFIG_KEYBOARD
  993. Define this to enable a custom keyboard support.
  994. This simply calls drv_keyboard_init() which must be
  995. defined in your board-specific files. This option is deprecated
  996. and is only used by novena. For new boards, use driver model
  997. instead.
  998. - Video support:
  999. CONFIG_FSL_DIU_FB
  1000. Enable the Freescale DIU video driver. Reference boards for
  1001. SOCs that have a DIU should define this macro to enable DIU
  1002. support, and should also define these other macros:
  1003. CONFIG_SYS_DIU_ADDR
  1004. CONFIG_VIDEO
  1005. CONFIG_CFB_CONSOLE
  1006. CONFIG_VIDEO_SW_CURSOR
  1007. CONFIG_VGA_AS_SINGLE_DEVICE
  1008. CONFIG_VIDEO_LOGO
  1009. CONFIG_VIDEO_BMP_LOGO
  1010. The DIU driver will look for the 'video-mode' environment
  1011. variable, and if defined, enable the DIU as a console during
  1012. boot. See the documentation file doc/README.video for a
  1013. description of this variable.
  1014. - LCD Support: CONFIG_LCD
  1015. Define this to enable LCD support (for output to LCD
  1016. display); also select one of the supported displays
  1017. by defining one of these:
  1018. CONFIG_ATMEL_LCD:
  1019. HITACHI TX09D70VM1CCA, 3.5", 240x320.
  1020. CONFIG_NEC_NL6448AC33:
  1021. NEC NL6448AC33-18. Active, color, single scan.
  1022. CONFIG_NEC_NL6448BC20
  1023. NEC NL6448BC20-08. 6.5", 640x480.
  1024. Active, color, single scan.
  1025. CONFIG_NEC_NL6448BC33_54
  1026. NEC NL6448BC33-54. 10.4", 640x480.
  1027. Active, color, single scan.
  1028. CONFIG_SHARP_16x9
  1029. Sharp 320x240. Active, color, single scan.
  1030. It isn't 16x9, and I am not sure what it is.
  1031. CONFIG_SHARP_LQ64D341
  1032. Sharp LQ64D341 display, 640x480.
  1033. Active, color, single scan.
  1034. CONFIG_HLD1045
  1035. HLD1045 display, 640x480.
  1036. Active, color, single scan.
  1037. CONFIG_OPTREX_BW
  1038. Optrex CBL50840-2 NF-FW 99 22 M5
  1039. or
  1040. Hitachi LMG6912RPFC-00T
  1041. or
  1042. Hitachi SP14Q002
  1043. 320x240. Black & white.
  1044. CONFIG_LCD_ALIGNMENT
  1045. Normally the LCD is page-aligned (typically 4KB). If this is
  1046. defined then the LCD will be aligned to this value instead.
  1047. For ARM it is sometimes useful to use MMU_SECTION_SIZE
  1048. here, since it is cheaper to change data cache settings on
  1049. a per-section basis.
  1050. CONFIG_LCD_ROTATION
  1051. Sometimes, for example if the display is mounted in portrait
  1052. mode or even if it's mounted landscape but rotated by 180degree,
  1053. we need to rotate our content of the display relative to the
  1054. framebuffer, so that user can read the messages which are
  1055. printed out.
  1056. Once CONFIG_LCD_ROTATION is defined, the lcd_console will be
  1057. initialized with a given rotation from "vl_rot" out of
  1058. "vidinfo_t" which is provided by the board specific code.
  1059. The value for vl_rot is coded as following (matching to
  1060. fbcon=rotate:<n> linux-kernel commandline):
  1061. 0 = no rotation respectively 0 degree
  1062. 1 = 90 degree rotation
  1063. 2 = 180 degree rotation
  1064. 3 = 270 degree rotation
  1065. If CONFIG_LCD_ROTATION is not defined, the console will be
  1066. initialized with 0degree rotation.
  1067. CONFIG_LCD_BMP_RLE8
  1068. Support drawing of RLE8-compressed bitmaps on the LCD.
  1069. CONFIG_I2C_EDID
  1070. Enables an 'i2c edid' command which can read EDID
  1071. information over I2C from an attached LCD display.
  1072. - Splash Screen Support: CONFIG_SPLASH_SCREEN
  1073. If this option is set, the environment is checked for
  1074. a variable "splashimage". If found, the usual display
  1075. of logo, copyright and system information on the LCD
  1076. is suppressed and the BMP image at the address
  1077. specified in "splashimage" is loaded instead. The
  1078. console is redirected to the "nulldev", too. This
  1079. allows for a "silent" boot where a splash screen is
  1080. loaded very quickly after power-on.
  1081. CONFIG_SPLASHIMAGE_GUARD
  1082. If this option is set, then U-Boot will prevent the environment
  1083. variable "splashimage" from being set to a problematic address
  1084. (see doc/README.displaying-bmps).
  1085. This option is useful for targets where, due to alignment
  1086. restrictions, an improperly aligned BMP image will cause a data
  1087. abort. If you think you will not have problems with unaligned
  1088. accesses (for example because your toolchain prevents them)
  1089. there is no need to set this option.
  1090. CONFIG_SPLASH_SCREEN_ALIGN
  1091. If this option is set the splash image can be freely positioned
  1092. on the screen. Environment variable "splashpos" specifies the
  1093. position as "x,y". If a positive number is given it is used as
  1094. number of pixel from left/top. If a negative number is given it
  1095. is used as number of pixel from right/bottom. You can also
  1096. specify 'm' for centering the image.
  1097. Example:
  1098. setenv splashpos m,m
  1099. => image at center of screen
  1100. setenv splashpos 30,20
  1101. => image at x = 30 and y = 20
  1102. setenv splashpos -10,m
  1103. => vertically centered image
  1104. at x = dspWidth - bmpWidth - 9
  1105. - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
  1106. If this option is set, additionally to standard BMP
  1107. images, gzipped BMP images can be displayed via the
  1108. splashscreen support or the bmp command.
  1109. - Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
  1110. If this option is set, 8-bit RLE compressed BMP images
  1111. can be displayed via the splashscreen support or the
  1112. bmp command.
  1113. - Compression support:
  1114. CONFIG_GZIP
  1115. Enabled by default to support gzip compressed images.
  1116. CONFIG_BZIP2
  1117. If this option is set, support for bzip2 compressed
  1118. images is included. If not, only uncompressed and gzip
  1119. compressed images are supported.
  1120. NOTE: the bzip2 algorithm requires a lot of RAM, so
  1121. the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
  1122. be at least 4MB.
  1123. - MII/PHY support:
  1124. CONFIG_PHY_ADDR
  1125. The address of PHY on MII bus.
  1126. CONFIG_PHY_CLOCK_FREQ (ppc4xx)
  1127. The clock frequency of the MII bus
  1128. CONFIG_PHY_RESET_DELAY
  1129. Some PHY like Intel LXT971A need extra delay after
  1130. reset before any MII register access is possible.
  1131. For such PHY, set this option to the usec delay
  1132. required. (minimum 300usec for LXT971A)
  1133. CONFIG_PHY_CMD_DELAY (ppc4xx)
  1134. Some PHY like Intel LXT971A need extra delay after
  1135. command issued before MII status register can be read
  1136. - IP address:
  1137. CONFIG_IPADDR
  1138. Define a default value for the IP address to use for
  1139. the default Ethernet interface, in case this is not
  1140. determined through e.g. bootp.
  1141. (Environment variable "ipaddr")
  1142. - Server IP address:
  1143. CONFIG_SERVERIP
  1144. Defines a default value for the IP address of a TFTP
  1145. server to contact when using the "tftboot" command.
  1146. (Environment variable "serverip")
  1147. CONFIG_KEEP_SERVERADDR
  1148. Keeps the server's MAC address, in the env 'serveraddr'
  1149. for passing to bootargs (like Linux's netconsole option)
  1150. - Gateway IP address:
  1151. CONFIG_GATEWAYIP
  1152. Defines a default value for the IP address of the
  1153. default router where packets to other networks are
  1154. sent to.
  1155. (Environment variable "gatewayip")
  1156. - Subnet mask:
  1157. CONFIG_NETMASK
  1158. Defines a default value for the subnet mask (or
  1159. routing prefix) which is used to determine if an IP
  1160. address belongs to the local subnet or needs to be
  1161. forwarded through a router.
  1162. (Environment variable "netmask")
  1163. - Multicast TFTP Mode:
  1164. CONFIG_MCAST_TFTP
  1165. Defines whether you want to support multicast TFTP as per
  1166. rfc-2090; for example to work with atftp. Lets lots of targets
  1167. tftp down the same boot image concurrently. Note: the Ethernet
  1168. driver in use must provide a function: mcast() to join/leave a
  1169. multicast group.
  1170. - BOOTP Recovery Mode:
  1171. CONFIG_BOOTP_RANDOM_DELAY
  1172. If you have many targets in a network that try to
  1173. boot using BOOTP, you may want to avoid that all
  1174. systems send out BOOTP requests at precisely the same
  1175. moment (which would happen for instance at recovery
  1176. from a power failure, when all systems will try to
  1177. boot, thus flooding the BOOTP server. Defining
  1178. CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
  1179. inserted before sending out BOOTP requests. The
  1180. following delays are inserted then:
  1181. 1st BOOTP request: delay 0 ... 1 sec
  1182. 2nd BOOTP request: delay 0 ... 2 sec
  1183. 3rd BOOTP request: delay 0 ... 4 sec
  1184. 4th and following
  1185. BOOTP requests: delay 0 ... 8 sec
  1186. CONFIG_BOOTP_ID_CACHE_SIZE
  1187. BOOTP packets are uniquely identified using a 32-bit ID. The
  1188. server will copy the ID from client requests to responses and
  1189. U-Boot will use this to determine if it is the destination of
  1190. an incoming response. Some servers will check that addresses
  1191. aren't in use before handing them out (usually using an ARP
  1192. ping) and therefore take up to a few hundred milliseconds to
  1193. respond. Network congestion may also influence the time it
  1194. takes for a response to make it back to the client. If that
  1195. time is too long, U-Boot will retransmit requests. In order
  1196. to allow earlier responses to still be accepted after these
  1197. retransmissions, U-Boot's BOOTP client keeps a small cache of
  1198. IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
  1199. cache. The default is to keep IDs for up to four outstanding
  1200. requests. Increasing this will allow U-Boot to accept offers
  1201. from a BOOTP client in networks with unusually high latency.
  1202. - DHCP Advanced Options:
  1203. You can fine tune the DHCP functionality by defining
  1204. CONFIG_BOOTP_* symbols:
  1205. CONFIG_BOOTP_SUBNETMASK
  1206. CONFIG_BOOTP_GATEWAY
  1207. CONFIG_BOOTP_HOSTNAME
  1208. CONFIG_BOOTP_NISDOMAIN
  1209. CONFIG_BOOTP_BOOTPATH
  1210. CONFIG_BOOTP_BOOTFILESIZE
  1211. CONFIG_BOOTP_DNS
  1212. CONFIG_BOOTP_DNS2
  1213. CONFIG_BOOTP_SEND_HOSTNAME
  1214. CONFIG_BOOTP_NTPSERVER
  1215. CONFIG_BOOTP_TIMEOFFSET
  1216. CONFIG_BOOTP_VENDOREX
  1217. CONFIG_BOOTP_MAY_FAIL
  1218. CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
  1219. environment variable, not the BOOTP server.
  1220. CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found
  1221. after the configured retry count, the call will fail
  1222. instead of starting over. This can be used to fail over
  1223. to Link-local IP address configuration if the DHCP server
  1224. is not available.
  1225. CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
  1226. serverip from a DHCP server, it is possible that more
  1227. than one DNS serverip is offered to the client.
  1228. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
  1229. serverip will be stored in the additional environment
  1230. variable "dnsip2". The first DNS serverip is always
  1231. stored in the variable "dnsip", when CONFIG_BOOTP_DNS
  1232. is defined.
  1233. CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
  1234. to do a dynamic update of a DNS server. To do this, they
  1235. need the hostname of the DHCP requester.
  1236. If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
  1237. of the "hostname" environment variable is passed as
  1238. option 12 to the DHCP server.
  1239. CONFIG_BOOTP_DHCP_REQUEST_DELAY
  1240. A 32bit value in microseconds for a delay between
  1241. receiving a "DHCP Offer" and sending the "DHCP Request".
  1242. This fixes a problem with certain DHCP servers that don't
  1243. respond 100% of the time to a "DHCP request". E.g. On an
  1244. AT91RM9200 processor running at 180MHz, this delay needed
  1245. to be *at least* 15,000 usec before a Windows Server 2003
  1246. DHCP server would reply 100% of the time. I recommend at
  1247. least 50,000 usec to be safe. The alternative is to hope
  1248. that one of the retries will be successful but note that
  1249. the DHCP timeout and retry process takes a longer than
  1250. this delay.
  1251. - Link-local IP address negotiation:
  1252. Negotiate with other link-local clients on the local network
  1253. for an address that doesn't require explicit configuration.
  1254. This is especially useful if a DHCP server cannot be guaranteed
  1255. to exist in all environments that the device must operate.
  1256. See doc/README.link-local for more information.
  1257. - CDP Options:
  1258. CONFIG_CDP_DEVICE_ID
  1259. The device id used in CDP trigger frames.
  1260. CONFIG_CDP_DEVICE_ID_PREFIX
  1261. A two character string which is prefixed to the MAC address
  1262. of the device.
  1263. CONFIG_CDP_PORT_ID
  1264. A printf format string which contains the ascii name of
  1265. the port. Normally is set to "eth%d" which sets
  1266. eth0 for the first Ethernet, eth1 for the second etc.
  1267. CONFIG_CDP_CAPABILITIES
  1268. A 32bit integer which indicates the device capabilities;
  1269. 0x00000010 for a normal host which does not forwards.
  1270. CONFIG_CDP_VERSION
  1271. An ascii string containing the version of the software.
  1272. CONFIG_CDP_PLATFORM
  1273. An ascii string containing the name of the platform.
  1274. CONFIG_CDP_TRIGGER
  1275. A 32bit integer sent on the trigger.
  1276. CONFIG_CDP_POWER_CONSUMPTION
  1277. A 16bit integer containing the power consumption of the
  1278. device in .1 of milliwatts.
  1279. CONFIG_CDP_APPLIANCE_VLAN_TYPE
  1280. A byte containing the id of the VLAN.
  1281. - Status LED: CONFIG_LED_STATUS
  1282. Several configurations allow to display the current
  1283. status using a LED. For instance, the LED will blink
  1284. fast while running U-Boot code, stop blinking as
  1285. soon as a reply to a BOOTP request was received, and
  1286. start blinking slow once the Linux kernel is running
  1287. (supported by a status LED driver in the Linux
  1288. kernel). Defining CONFIG_LED_STATUS enables this
  1289. feature in U-Boot.
  1290. Additional options:
  1291. CONFIG_LED_STATUS_GPIO
  1292. The status LED can be connected to a GPIO pin.
  1293. In such cases, the gpio_led driver can be used as a
  1294. status LED backend implementation. Define CONFIG_LED_STATUS_GPIO
  1295. to include the gpio_led driver in the U-Boot binary.
  1296. CONFIG_GPIO_LED_INVERTED_TABLE
  1297. Some GPIO connected LEDs may have inverted polarity in which
  1298. case the GPIO high value corresponds to LED off state and
  1299. GPIO low value corresponds to LED on state.
  1300. In such cases CONFIG_GPIO_LED_INVERTED_TABLE may be defined
  1301. with a list of GPIO LEDs that have inverted polarity.
  1302. - I2C Support: CONFIG_SYS_I2C
  1303. This enable the NEW i2c subsystem, and will allow you to use
  1304. i2c commands at the u-boot command line (as long as you set
  1305. CONFIG_CMD_I2C in CONFIG_COMMANDS) and communicate with i2c
  1306. based realtime clock chips or other i2c devices. See
  1307. common/cmd_i2c.c for a description of the command line
  1308. interface.
  1309. ported i2c driver to the new framework:
  1310. - drivers/i2c/soft_i2c.c:
  1311. - activate first bus with CONFIG_SYS_I2C_SOFT define
  1312. CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE
  1313. for defining speed and slave address
  1314. - activate second bus with I2C_SOFT_DECLARATIONS2 define
  1315. CONFIG_SYS_I2C_SOFT_SPEED_2 and CONFIG_SYS_I2C_SOFT_SLAVE_2
  1316. for defining speed and slave address
  1317. - activate third bus with I2C_SOFT_DECLARATIONS3 define
  1318. CONFIG_SYS_I2C_SOFT_SPEED_3 and CONFIG_SYS_I2C_SOFT_SLAVE_3
  1319. for defining speed and slave address
  1320. - activate fourth bus with I2C_SOFT_DECLARATIONS4 define
  1321. CONFIG_SYS_I2C_SOFT_SPEED_4 and CONFIG_SYS_I2C_SOFT_SLAVE_4
  1322. for defining speed and slave address
  1323. - drivers/i2c/fsl_i2c.c:
  1324. - activate i2c driver with CONFIG_SYS_I2C_FSL
  1325. define CONFIG_SYS_FSL_I2C_OFFSET for setting the register
  1326. offset CONFIG_SYS_FSL_I2C_SPEED for the i2c speed and
  1327. CONFIG_SYS_FSL_I2C_SLAVE for the slave addr of the first
  1328. bus.
  1329. - If your board supports a second fsl i2c bus, define
  1330. CONFIG_SYS_FSL_I2C2_OFFSET for the register offset
  1331. CONFIG_SYS_FSL_I2C2_SPEED for the speed and
  1332. CONFIG_SYS_FSL_I2C2_SLAVE for the slave address of the
  1333. second bus.
  1334. - drivers/i2c/tegra_i2c.c:
  1335. - activate this driver with CONFIG_SYS_I2C_TEGRA
  1336. - This driver adds 4 i2c buses with a fix speed from
  1337. 100000 and the slave addr 0!
  1338. - drivers/i2c/ppc4xx_i2c.c
  1339. - activate this driver with CONFIG_SYS_I2C_PPC4XX
  1340. - CONFIG_SYS_I2C_PPC4XX_CH0 activate hardware channel 0
  1341. - CONFIG_SYS_I2C_PPC4XX_CH1 activate hardware channel 1
  1342. - drivers/i2c/i2c_mxc.c
  1343. - activate this driver with CONFIG_SYS_I2C_MXC
  1344. - enable bus 1 with CONFIG_SYS_I2C_MXC_I2C1
  1345. - enable bus 2 with CONFIG_SYS_I2C_MXC_I2C2
  1346. - enable bus 3 with CONFIG_SYS_I2C_MXC_I2C3
  1347. - enable bus 4 with CONFIG_SYS_I2C_MXC_I2C4
  1348. - define speed for bus 1 with CONFIG_SYS_MXC_I2C1_SPEED
  1349. - define slave for bus 1 with CONFIG_SYS_MXC_I2C1_SLAVE
  1350. - define speed for bus 2 with CONFIG_SYS_MXC_I2C2_SPEED
  1351. - define slave for bus 2 with CONFIG_SYS_MXC_I2C2_SLAVE
  1352. - define speed for bus 3 with CONFIG_SYS_MXC_I2C3_SPEED
  1353. - define slave for bus 3 with CONFIG_SYS_MXC_I2C3_SLAVE
  1354. - define speed for bus 4 with CONFIG_SYS_MXC_I2C4_SPEED
  1355. - define slave for bus 4 with CONFIG_SYS_MXC_I2C4_SLAVE
  1356. If those defines are not set, default value is 100000
  1357. for speed, and 0 for slave.
  1358. - drivers/i2c/rcar_i2c.c:
  1359. - activate this driver with CONFIG_SYS_I2C_RCAR
  1360. - This driver adds 4 i2c buses
  1361. - CONFIG_SYS_RCAR_I2C0_BASE for setting the register channel 0
  1362. - CONFIG_SYS_RCAR_I2C0_SPEED for for the speed channel 0
  1363. - CONFIG_SYS_RCAR_I2C1_BASE for setting the register channel 1
  1364. - CONFIG_SYS_RCAR_I2C1_SPEED for for the speed channel 1
  1365. - CONFIG_SYS_RCAR_I2C2_BASE for setting the register channel 2
  1366. - CONFIG_SYS_RCAR_I2C2_SPEED for for the speed channel 2
  1367. - CONFIG_SYS_RCAR_I2C3_BASE for setting the register channel 3
  1368. - CONFIG_SYS_RCAR_I2C3_SPEED for for the speed channel 3
  1369. - CONFIF_SYS_RCAR_I2C_NUM_CONTROLLERS for number of i2c buses
  1370. - drivers/i2c/sh_i2c.c:
  1371. - activate this driver with CONFIG_SYS_I2C_SH
  1372. - This driver adds from 2 to 5 i2c buses
  1373. - CONFIG_SYS_I2C_SH_BASE0 for setting the register channel 0
  1374. - CONFIG_SYS_I2C_SH_SPEED0 for for the speed channel 0
  1375. - CONFIG_SYS_I2C_SH_BASE1 for setting the register channel 1
  1376. - CONFIG_SYS_I2C_SH_SPEED1 for for the speed channel 1
  1377. - CONFIG_SYS_I2C_SH_BASE2 for setting the register channel 2
  1378. - CONFIG_SYS_I2C_SH_SPEED2 for for the speed channel 2
  1379. - CONFIG_SYS_I2C_SH_BASE3 for setting the register channel 3
  1380. - CONFIG_SYS_I2C_SH_SPEED3 for for the speed channel 3
  1381. - CONFIG_SYS_I2C_SH_BASE4 for setting the register channel 4
  1382. - CONFIG_SYS_I2C_SH_SPEED4 for for the speed channel 4
  1383. - CONFIG_SYS_I2C_SH_NUM_CONTROLLERS for number of i2c buses
  1384. - drivers/i2c/omap24xx_i2c.c
  1385. - activate this driver with CONFIG_SYS_I2C_OMAP24XX
  1386. - CONFIG_SYS_OMAP24_I2C_SPEED speed channel 0
  1387. - CONFIG_SYS_OMAP24_I2C_SLAVE slave addr channel 0
  1388. - CONFIG_SYS_OMAP24_I2C_SPEED1 speed channel 1
  1389. - CONFIG_SYS_OMAP24_I2C_SLAVE1 slave addr channel 1
  1390. - CONFIG_SYS_OMAP24_I2C_SPEED2 speed channel 2
  1391. - CONFIG_SYS_OMAP24_I2C_SLAVE2 slave addr channel 2
  1392. - CONFIG_SYS_OMAP24_I2C_SPEED3 speed channel 3
  1393. - CONFIG_SYS_OMAP24_I2C_SLAVE3 slave addr channel 3
  1394. - CONFIG_SYS_OMAP24_I2C_SPEED4 speed channel 4
  1395. - CONFIG_SYS_OMAP24_I2C_SLAVE4 slave addr channel 4
  1396. - drivers/i2c/zynq_i2c.c
  1397. - activate this driver with CONFIG_SYS_I2C_ZYNQ
  1398. - set CONFIG_SYS_I2C_ZYNQ_SPEED for speed setting
  1399. - set CONFIG_SYS_I2C_ZYNQ_SLAVE for slave addr
  1400. - drivers/i2c/s3c24x0_i2c.c:
  1401. - activate this driver with CONFIG_SYS_I2C_S3C24X0
  1402. - This driver adds i2c buses (11 for Exynos5250, Exynos5420
  1403. 9 i2c buses for Exynos4 and 1 for S3C24X0 SoCs from Samsung)
  1404. with a fix speed from 100000 and the slave addr 0!
  1405. - drivers/i2c/ihs_i2c.c
  1406. - activate this driver with CONFIG_SYS_I2C_IHS
  1407. - CONFIG_SYS_I2C_IHS_CH0 activate hardware channel 0
  1408. - CONFIG_SYS_I2C_IHS_SPEED_0 speed channel 0
  1409. - CONFIG_SYS_I2C_IHS_SLAVE_0 slave addr channel 0
  1410. - CONFIG_SYS_I2C_IHS_CH1 activate hardware channel 1
  1411. - CONFIG_SYS_I2C_IHS_SPEED_1 speed channel 1
  1412. - CONFIG_SYS_I2C_IHS_SLAVE_1 slave addr channel 1
  1413. - CONFIG_SYS_I2C_IHS_CH2 activate hardware channel 2
  1414. - CONFIG_SYS_I2C_IHS_SPEED_2 speed channel 2
  1415. - CONFIG_SYS_I2C_IHS_SLAVE_2 slave addr channel 2
  1416. - CONFIG_SYS_I2C_IHS_CH3 activate hardware channel 3
  1417. - CONFIG_SYS_I2C_IHS_SPEED_3 speed channel 3
  1418. - CONFIG_SYS_I2C_IHS_SLAVE_3 slave addr channel 3
  1419. - activate dual channel with CONFIG_SYS_I2C_IHS_DUAL
  1420. - CONFIG_SYS_I2C_IHS_SPEED_0_1 speed channel 0_1
  1421. - CONFIG_SYS_I2C_IHS_SLAVE_0_1 slave addr channel 0_1
  1422. - CONFIG_SYS_I2C_IHS_SPEED_1_1 speed channel 1_1
  1423. - CONFIG_SYS_I2C_IHS_SLAVE_1_1 slave addr channel 1_1
  1424. - CONFIG_SYS_I2C_IHS_SPEED_2_1 speed channel 2_1
  1425. - CONFIG_SYS_I2C_IHS_SLAVE_2_1 slave addr channel 2_1
  1426. - CONFIG_SYS_I2C_IHS_SPEED_3_1 speed channel 3_1
  1427. - CONFIG_SYS_I2C_IHS_SLAVE_3_1 slave addr channel 3_1
  1428. additional defines:
  1429. CONFIG_SYS_NUM_I2C_BUSES
  1430. Hold the number of i2c buses you want to use.
  1431. CONFIG_SYS_I2C_DIRECT_BUS
  1432. define this, if you don't use i2c muxes on your hardware.
  1433. if CONFIG_SYS_I2C_MAX_HOPS is not defined or == 0 you can
  1434. omit this define.
  1435. CONFIG_SYS_I2C_MAX_HOPS
  1436. define how many muxes are maximal consecutively connected
  1437. on one i2c bus. If you not use i2c muxes, omit this
  1438. define.
  1439. CONFIG_SYS_I2C_BUSES
  1440. hold a list of buses you want to use, only used if
  1441. CONFIG_SYS_I2C_DIRECT_BUS is not defined, for example
  1442. a board with CONFIG_SYS_I2C_MAX_HOPS = 1 and
  1443. CONFIG_SYS_NUM_I2C_BUSES = 9:
  1444. CONFIG_SYS_I2C_BUSES {{0, {I2C_NULL_HOP}}, \
  1445. {0, {{I2C_MUX_PCA9547, 0x70, 1}}}, \
  1446. {0, {{I2C_MUX_PCA9547, 0x70, 2}}}, \
  1447. {0, {{I2C_MUX_PCA9547, 0x70, 3}}}, \
  1448. {0, {{I2C_MUX_PCA9547, 0x70, 4}}}, \
  1449. {0, {{I2C_MUX_PCA9547, 0x70, 5}}}, \
  1450. {1, {I2C_NULL_HOP}}, \
  1451. {1, {{I2C_MUX_PCA9544, 0x72, 1}}}, \
  1452. {1, {{I2C_MUX_PCA9544, 0x72, 2}}}, \
  1453. }
  1454. which defines
  1455. bus 0 on adapter 0 without a mux
  1456. bus 1 on adapter 0 with a PCA9547 on address 0x70 port 1
  1457. bus 2 on adapter 0 with a PCA9547 on address 0x70 port 2
  1458. bus 3 on adapter 0 with a PCA9547 on address 0x70 port 3
  1459. bus 4 on adapter 0 with a PCA9547 on address 0x70 port 4
  1460. bus 5 on adapter 0 with a PCA9547 on address 0x70 port 5
  1461. bus 6 on adapter 1 without a mux
  1462. bus 7 on adapter 1 with a PCA9544 on address 0x72 port 1
  1463. bus 8 on adapter 1 with a PCA9544 on address 0x72 port 2
  1464. If you do not have i2c muxes on your board, omit this define.
  1465. - Legacy I2C Support:
  1466. If you use the software i2c interface (CONFIG_SYS_I2C_SOFT)
  1467. then the following macros need to be defined (examples are
  1468. from include/configs/lwmon.h):
  1469. I2C_INIT
  1470. (Optional). Any commands necessary to enable the I2C
  1471. controller or configure ports.
  1472. eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
  1473. I2C_ACTIVE
  1474. The code necessary to make the I2C data line active
  1475. (driven). If the data line is open collector, this
  1476. define can be null.
  1477. eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
  1478. I2C_TRISTATE
  1479. The code necessary to make the I2C data line tri-stated
  1480. (inactive). If the data line is open collector, this
  1481. define can be null.
  1482. eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
  1483. I2C_READ
  1484. Code that returns true if the I2C data line is high,
  1485. false if it is low.
  1486. eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
  1487. I2C_SDA(bit)
  1488. If <bit> is true, sets the I2C data line high. If it
  1489. is false, it clears it (low).
  1490. eg: #define I2C_SDA(bit) \
  1491. if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
  1492. else immr->im_cpm.cp_pbdat &= ~PB_SDA
  1493. I2C_SCL(bit)
  1494. If <bit> is true, sets the I2C clock line high. If it
  1495. is false, it clears it (low).
  1496. eg: #define I2C_SCL(bit) \
  1497. if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
  1498. else immr->im_cpm.cp_pbdat &= ~PB_SCL
  1499. I2C_DELAY
  1500. This delay is invoked four times per clock cycle so this
  1501. controls the rate of data transfer. The data rate thus
  1502. is 1 / (I2C_DELAY * 4). Often defined to be something
  1503. like:
  1504. #define I2C_DELAY udelay(2)
  1505. CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
  1506. If your arch supports the generic GPIO framework (asm/gpio.h),
  1507. then you may alternatively define the two GPIOs that are to be
  1508. used as SCL / SDA. Any of the previous I2C_xxx macros will
  1509. have GPIO-based defaults assigned to them as appropriate.
  1510. You should define these to the GPIO value as given directly to
  1511. the generic GPIO functions.
  1512. CONFIG_SYS_I2C_INIT_BOARD
  1513. When a board is reset during an i2c bus transfer
  1514. chips might think that the current transfer is still
  1515. in progress. On some boards it is possible to access
  1516. the i2c SCLK line directly, either by using the
  1517. processor pin as a GPIO or by having a second pin
  1518. connected to the bus. If this option is defined a
  1519. custom i2c_init_board() routine in boards/xxx/board.c
  1520. is run early in the boot sequence.
  1521. CONFIG_I2C_MULTI_BUS
  1522. This option allows the use of multiple I2C buses, each of which
  1523. must have a controller. At any point in time, only one bus is
  1524. active. To switch to a different bus, use the 'i2c dev' command.
  1525. Note that bus numbering is zero-based.
  1526. CONFIG_SYS_I2C_NOPROBES
  1527. This option specifies a list of I2C devices that will be skipped
  1528. when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS
  1529. is set, specify a list of bus-device pairs. Otherwise, specify
  1530. a 1D array of device addresses
  1531. e.g.
  1532. #undef CONFIG_I2C_MULTI_BUS
  1533. #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}
  1534. will skip addresses 0x50 and 0x68 on a board with one I2C bus
  1535. #define CONFIG_I2C_MULTI_BUS
  1536. #define CONFIG_SYS_I2C_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
  1537. will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
  1538. CONFIG_SYS_SPD_BUS_NUM
  1539. If defined, then this indicates the I2C bus number for DDR SPD.
  1540. If not defined, then U-Boot assumes that SPD is on I2C bus 0.
  1541. CONFIG_SYS_RTC_BUS_NUM
  1542. If defined, then this indicates the I2C bus number for the RTC.
  1543. If not defined, then U-Boot assumes that RTC is on I2C bus 0.
  1544. CONFIG_SOFT_I2C_READ_REPEATED_START
  1545. defining this will force the i2c_read() function in
  1546. the soft_i2c driver to perform an I2C repeated start
  1547. between writing the address pointer and reading the
  1548. data. If this define is omitted the default behaviour
  1549. of doing a stop-start sequence will be used. Most I2C
  1550. devices can use either method, but some require one or
  1551. the other.
  1552. - SPI Support: CONFIG_SPI
  1553. Enables SPI driver (so far only tested with
  1554. SPI EEPROM, also an instance works with Crystal A/D and
  1555. D/As on the SACSng board)
  1556. CONFIG_SH_SPI
  1557. Enables the driver for SPI controller on SuperH. Currently
  1558. only SH7757 is supported.
  1559. CONFIG_SOFT_SPI
  1560. Enables a software (bit-bang) SPI driver rather than
  1561. using hardware support. This is a general purpose
  1562. driver that only requires three general I/O port pins
  1563. (two outputs, one input) to function. If this is
  1564. defined, the board configuration must define several
  1565. SPI configuration items (port pins to use, etc). For
  1566. an example, see include/configs/sacsng.h.
  1567. CONFIG_HARD_SPI
  1568. Enables a hardware SPI driver for general-purpose reads
  1569. and writes. As with CONFIG_SOFT_SPI, the board configuration
  1570. must define a list of chip-select function pointers.
  1571. Currently supported on some MPC8xxx processors. For an
  1572. example, see include/configs/mpc8349emds.h.
  1573. CONFIG_MXC_SPI
  1574. Enables the driver for the SPI controllers on i.MX and MXC
  1575. SoCs. Currently i.MX31/35/51 are supported.
  1576. CONFIG_SYS_SPI_MXC_WAIT
  1577. Timeout for waiting until spi transfer completed.
  1578. default: (CONFIG_SYS_HZ/100) /* 10 ms */
  1579. - FPGA Support: CONFIG_FPGA
  1580. Enables FPGA subsystem.
  1581. CONFIG_FPGA_<vendor>
  1582. Enables support for specific chip vendors.
  1583. (ALTERA, XILINX)
  1584. CONFIG_FPGA_<family>
  1585. Enables support for FPGA family.
  1586. (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
  1587. CONFIG_FPGA_COUNT
  1588. Specify the number of FPGA devices to support.
  1589. CONFIG_SYS_FPGA_PROG_FEEDBACK
  1590. Enable printing of hash marks during FPGA configuration.
  1591. CONFIG_SYS_FPGA_CHECK_BUSY
  1592. Enable checks on FPGA configuration interface busy
  1593. status by the configuration function. This option
  1594. will require a board or device specific function to
  1595. be written.
  1596. CONFIG_FPGA_DELAY
  1597. If defined, a function that provides delays in the FPGA
  1598. configuration driver.
  1599. CONFIG_SYS_FPGA_CHECK_CTRLC
  1600. Allow Control-C to interrupt FPGA configuration
  1601. CONFIG_SYS_FPGA_CHECK_ERROR
  1602. Check for configuration errors during FPGA bitfile
  1603. loading. For example, abort during Virtex II
  1604. configuration if the INIT_B line goes low (which
  1605. indicated a CRC error).
  1606. CONFIG_SYS_FPGA_WAIT_INIT
  1607. Maximum time to wait for the INIT_B line to de-assert
  1608. after PROB_B has been de-asserted during a Virtex II
  1609. FPGA configuration sequence. The default time is 500
  1610. ms.
  1611. CONFIG_SYS_FPGA_WAIT_BUSY
  1612. Maximum time to wait for BUSY to de-assert during
  1613. Virtex II FPGA configuration. The default is 5 ms.
  1614. CONFIG_SYS_FPGA_WAIT_CONFIG
  1615. Time to wait after FPGA configuration. The default is
  1616. 200 ms.
  1617. - Configuration Management:
  1618. CONFIG_BUILD_TARGET
  1619. Some SoCs need special image types (e.g. U-Boot binary
  1620. with a special header) as build targets. By defining
  1621. CONFIG_BUILD_TARGET in the SoC / board header, this
  1622. special image will be automatically built upon calling
  1623. make / buildman.
  1624. CONFIG_IDENT_STRING
  1625. If defined, this string will be added to the U-Boot
  1626. version information (U_BOOT_VERSION)
  1627. - Vendor Parameter Protection:
  1628. U-Boot considers the values of the environment
  1629. variables "serial#" (Board Serial Number) and
  1630. "ethaddr" (Ethernet Address) to be parameters that
  1631. are set once by the board vendor / manufacturer, and
  1632. protects these variables from casual modification by
  1633. the user. Once set, these variables are read-only,
  1634. and write or delete attempts are rejected. You can
  1635. change this behaviour:
  1636. If CONFIG_ENV_OVERWRITE is #defined in your config
  1637. file, the write protection for vendor parameters is
  1638. completely disabled. Anybody can change or delete
  1639. these parameters.
  1640. Alternatively, if you define _both_ an ethaddr in the
  1641. default env _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
  1642. Ethernet address is installed in the environment,
  1643. which can be changed exactly ONCE by the user. [The
  1644. serial# is unaffected by this, i. e. it remains
  1645. read-only.]
  1646. The same can be accomplished in a more flexible way
  1647. for any variable by configuring the type of access
  1648. to allow for those variables in the ".flags" variable
  1649. or define CONFIG_ENV_FLAGS_LIST_STATIC.
  1650. - Protected RAM:
  1651. CONFIG_PRAM
  1652. Define this variable to enable the reservation of
  1653. "protected RAM", i. e. RAM which is not overwritten
  1654. by U-Boot. Define CONFIG_PRAM to hold the number of
  1655. kB you want to reserve for pRAM. You can overwrite
  1656. this default value by defining an environment
  1657. variable "pram" to the number of kB you want to
  1658. reserve. Note that the board info structure will
  1659. still show the full amount of RAM. If pRAM is
  1660. reserved, a new environment variable "mem" will
  1661. automatically be defined to hold the amount of
  1662. remaining RAM in a form that can be passed as boot
  1663. argument to Linux, for instance like that:
  1664. setenv bootargs ... mem=\${mem}
  1665. saveenv
  1666. This way you can tell Linux not to use this memory,
  1667. either, which results in a memory region that will
  1668. not be affected by reboots.
  1669. *WARNING* If your board configuration uses automatic
  1670. detection of the RAM size, you must make sure that
  1671. this memory test is non-destructive. So far, the
  1672. following board configurations are known to be
  1673. "pRAM-clean":
  1674. IVMS8, IVML24, SPD8xx,
  1675. HERMES, IP860, RPXlite, LWMON,
  1676. FLAGADM
  1677. - Access to physical memory region (> 4GB)
  1678. Some basic support is provided for operations on memory not
  1679. normally accessible to U-Boot - e.g. some architectures
  1680. support access to more than 4GB of memory on 32-bit
  1681. machines using physical address extension or similar.
  1682. Define CONFIG_PHYSMEM to access this basic support, which
  1683. currently only supports clearing the memory.
  1684. - Error Recovery:
  1685. CONFIG_PANIC_HANG
  1686. Define this variable to stop the system in case of a
  1687. fatal error, so that you have to reset it manually.
  1688. This is probably NOT a good idea for an embedded
  1689. system where you want the system to reboot
  1690. automatically as fast as possible, but it may be
  1691. useful during development since you can try to debug
  1692. the conditions that lead to the situation.
  1693. CONFIG_NET_RETRY_COUNT
  1694. This variable defines the number of retries for
  1695. network operations like ARP, RARP, TFTP, or BOOTP
  1696. before giving up the operation. If not defined, a
  1697. default value of 5 is used.
  1698. CONFIG_ARP_TIMEOUT
  1699. Timeout waiting for an ARP reply in milliseconds.
  1700. CONFIG_NFS_TIMEOUT
  1701. Timeout in milliseconds used in NFS protocol.
  1702. If you encounter "ERROR: Cannot umount" in nfs command,
  1703. try longer timeout such as
  1704. #define CONFIG_NFS_TIMEOUT 10000UL
  1705. - Command Interpreter:
  1706. CONFIG_AUTO_COMPLETE
  1707. Enable auto completion of commands using TAB.
  1708. CONFIG_SYS_PROMPT_HUSH_PS2
  1709. This defines the secondary prompt string, which is
  1710. printed when the command interpreter needs more input
  1711. to complete a command. Usually "> ".
  1712. Note:
  1713. In the current implementation, the local variables
  1714. space and global environment variables space are
  1715. separated. Local variables are those you define by
  1716. simply typing `name=value'. To access a local
  1717. variable later on, you have write `$name' or
  1718. `${name}'; to execute the contents of a variable
  1719. directly type `$name' at the command prompt.
  1720. Global environment variables are those you use
  1721. setenv/printenv to work with. To run a command stored
  1722. in such a variable, you need to use the run command,
  1723. and you must not use the '$' sign to access them.
  1724. To store commands and special characters in a
  1725. variable, please use double quotation marks
  1726. surrounding the whole text of the variable, instead
  1727. of the backslashes before semicolons and special
  1728. symbols.
  1729. - Command Line Editing and History:
  1730. CONFIG_CMDLINE_EDITING
  1731. Enable editing and History functions for interactive
  1732. command line input operations
  1733. - Command Line PS1/PS2 support:
  1734. CONFIG_CMDLINE_PS_SUPPORT
  1735. Enable support for changing the command prompt string
  1736. at run-time. Only static string is supported so far.
  1737. The string is obtained from environment variables PS1
  1738. and PS2.
  1739. - Default Environment:
  1740. CONFIG_EXTRA_ENV_SETTINGS
  1741. Define this to contain any number of null terminated
  1742. strings (variable = value pairs) that will be part of
  1743. the default environment compiled into the boot image.
  1744. For example, place something like this in your
  1745. board's config file:
  1746. #define CONFIG_EXTRA_ENV_SETTINGS \
  1747. "myvar1=value1\0" \
  1748. "myvar2=value2\0"
  1749. Warning: This method is based on knowledge about the
  1750. internal format how the environment is stored by the
  1751. U-Boot code. This is NOT an official, exported
  1752. interface! Although it is unlikely that this format
  1753. will change soon, there is no guarantee either.
  1754. You better know what you are doing here.
  1755. Note: overly (ab)use of the default environment is
  1756. discouraged. Make sure to check other ways to preset
  1757. the environment like the "source" command or the
  1758. boot command first.
  1759. CONFIG_ENV_VARS_UBOOT_CONFIG
  1760. Define this in order to add variables describing the
  1761. U-Boot build configuration to the default environment.
  1762. These will be named arch, cpu, board, vendor, and soc.
  1763. Enabling this option will cause the following to be defined:
  1764. - CONFIG_SYS_ARCH
  1765. - CONFIG_SYS_CPU
  1766. - CONFIG_SYS_BOARD
  1767. - CONFIG_SYS_VENDOR
  1768. - CONFIG_SYS_SOC
  1769. CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG
  1770. Define this in order to add variables describing certain
  1771. run-time determined information about the hardware to the
  1772. environment. These will be named board_name, board_rev.
  1773. CONFIG_DELAY_ENVIRONMENT
  1774. Normally the environment is loaded when the board is
  1775. initialised so that it is available to U-Boot. This inhibits
  1776. that so that the environment is not available until
  1777. explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL
  1778. this is instead controlled by the value of
  1779. /config/load-environment.
  1780. - DataFlash Support:
  1781. CONFIG_HAS_DATAFLASH
  1782. Defining this option enables DataFlash features and
  1783. allows to read/write in Dataflash via the standard
  1784. commands cp, md...
  1785. - Serial Flash support
  1786. Usage requires an initial 'sf probe' to define the serial
  1787. flash parameters, followed by read/write/erase/update
  1788. commands.
  1789. The following defaults may be provided by the platform
  1790. to handle the common case when only a single serial
  1791. flash is present on the system.
  1792. CONFIG_SF_DEFAULT_BUS Bus identifier
  1793. CONFIG_SF_DEFAULT_CS Chip-select
  1794. CONFIG_SF_DEFAULT_MODE (see include/spi.h)
  1795. CONFIG_SF_DEFAULT_SPEED in Hz
  1796. CONFIG_SYSTEMACE
  1797. Adding this option adds support for Xilinx SystemACE
  1798. chips attached via some sort of local bus. The address
  1799. of the chip must also be defined in the
  1800. CONFIG_SYS_SYSTEMACE_BASE macro. For example:
  1801. #define CONFIG_SYSTEMACE
  1802. #define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000
  1803. When SystemACE support is added, the "ace" device type
  1804. becomes available to the fat commands, i.e. fatls.
  1805. - TFTP Fixed UDP Port:
  1806. CONFIG_TFTP_PORT
  1807. If this is defined, the environment variable tftpsrcp
  1808. is used to supply the TFTP UDP source port value.
  1809. If tftpsrcp isn't defined, the normal pseudo-random port
  1810. number generator is used.
  1811. Also, the environment variable tftpdstp is used to supply
  1812. the TFTP UDP destination port value. If tftpdstp isn't
  1813. defined, the normal port 69 is used.
  1814. The purpose for tftpsrcp is to allow a TFTP server to
  1815. blindly start the TFTP transfer using the pre-configured
  1816. target IP address and UDP port. This has the effect of
  1817. "punching through" the (Windows XP) firewall, allowing
  1818. the remainder of the TFTP transfer to proceed normally.
  1819. A better solution is to properly configure the firewall,
  1820. but sometimes that is not allowed.
  1821. - bootcount support:
  1822. CONFIG_BOOTCOUNT_LIMIT
  1823. This enables the bootcounter support, see:
  1824. http://www.denx.de/wiki/DULG/UBootBootCountLimit
  1825. CONFIG_AT91SAM9XE
  1826. enable special bootcounter support on at91sam9xe based boards.
  1827. CONFIG_SOC_DA8XX
  1828. enable special bootcounter support on da850 based boards.
  1829. CONFIG_BOOTCOUNT_RAM
  1830. enable support for the bootcounter in RAM
  1831. CONFIG_BOOTCOUNT_I2C
  1832. enable support for the bootcounter on an i2c (like RTC) device.
  1833. CONFIG_SYS_I2C_RTC_ADDR = i2c chip address
  1834. CONFIG_SYS_BOOTCOUNT_ADDR = i2c addr which is used for
  1835. the bootcounter.
  1836. CONFIG_BOOTCOUNT_ALEN = address len
  1837. - Show boot progress:
  1838. CONFIG_SHOW_BOOT_PROGRESS
  1839. Defining this option allows to add some board-
  1840. specific code (calling a user-provided function
  1841. "show_boot_progress(int)") that enables you to show
  1842. the system's boot progress on some display (for
  1843. example, some LED's) on your board. At the moment,
  1844. the following checkpoints are implemented:
  1845. Legacy uImage format:
  1846. Arg Where When
  1847. 1 common/cmd_bootm.c before attempting to boot an image
  1848. -1 common/cmd_bootm.c Image header has bad magic number
  1849. 2 common/cmd_bootm.c Image header has correct magic number
  1850. -2 common/cmd_bootm.c Image header has bad checksum
  1851. 3 common/cmd_bootm.c Image header has correct checksum
  1852. -3 common/cmd_bootm.c Image data has bad checksum
  1853. 4 common/cmd_bootm.c Image data has correct checksum
  1854. -4 common/cmd_bootm.c Image is for unsupported architecture
  1855. 5 common/cmd_bootm.c Architecture check OK
  1856. -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
  1857. 6 common/cmd_bootm.c Image Type check OK
  1858. -6 common/cmd_bootm.c gunzip uncompression error
  1859. -7 common/cmd_bootm.c Unimplemented compression type
  1860. 7 common/cmd_bootm.c Uncompression OK
  1861. 8 common/cmd_bootm.c No uncompress/copy overwrite error
  1862. -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
  1863. 9 common/image.c Start initial ramdisk verification
  1864. -10 common/image.c Ramdisk header has bad magic number
  1865. -11 common/image.c Ramdisk header has bad checksum
  1866. 10 common/image.c Ramdisk header is OK
  1867. -12 common/image.c Ramdisk data has bad checksum
  1868. 11 common/image.c Ramdisk data has correct checksum
  1869. 12 common/image.c Ramdisk verification complete, start loading
  1870. -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
  1871. 13 common/image.c Start multifile image verification
  1872. 14 common/image.c No initial ramdisk, no multifile, continue.
  1873. 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
  1874. -30 arch/powerpc/lib/board.c Fatal error, hang the system
  1875. -31 post/post.c POST test failed, detected by post_output_backlog()
  1876. -32 post/post.c POST test failed, detected by post_run_single()
  1877. 34 common/cmd_doc.c before loading a Image from a DOC device
  1878. -35 common/cmd_doc.c Bad usage of "doc" command
  1879. 35 common/cmd_doc.c correct usage of "doc" command
  1880. -36 common/cmd_doc.c No boot device
  1881. 36 common/cmd_doc.c correct boot device
  1882. -37 common/cmd_doc.c Unknown Chip ID on boot device
  1883. 37 common/cmd_doc.c correct chip ID found, device available
  1884. -38 common/cmd_doc.c Read Error on boot device
  1885. 38 common/cmd_doc.c reading Image header from DOC device OK
  1886. -39 common/cmd_doc.c Image header has bad magic number
  1887. 39 common/cmd_doc.c Image header has correct magic number
  1888. -40 common/cmd_doc.c Error reading Image from DOC device
  1889. 40 common/cmd_doc.c Image header has correct magic number
  1890. 41 common/cmd_ide.c before loading a Image from a IDE device
  1891. -42 common/cmd_ide.c Bad usage of "ide" command
  1892. 42 common/cmd_ide.c correct usage of "ide" command
  1893. -43 common/cmd_ide.c No boot device
  1894. 43 common/cmd_ide.c boot device found
  1895. -44 common/cmd_ide.c Device not available
  1896. 44 common/cmd_ide.c Device available
  1897. -45 common/cmd_ide.c wrong partition selected
  1898. 45 common/cmd_ide.c partition selected
  1899. -46 common/cmd_ide.c Unknown partition table
  1900. 46 common/cmd_ide.c valid partition table found
  1901. -47 common/cmd_ide.c Invalid partition type
  1902. 47 common/cmd_ide.c correct partition type
  1903. -48 common/cmd_ide.c Error reading Image Header on boot device
  1904. 48 common/cmd_ide.c reading Image Header from IDE device OK
  1905. -49 common/cmd_ide.c Image header has bad magic number
  1906. 49 common/cmd_ide.c Image header has correct magic number
  1907. -50 common/cmd_ide.c Image header has bad checksum
  1908. 50 common/cmd_ide.c Image header has correct checksum
  1909. -51 common/cmd_ide.c Error reading Image from IDE device
  1910. 51 common/cmd_ide.c reading Image from IDE device OK
  1911. 52 common/cmd_nand.c before loading a Image from a NAND device
  1912. -53 common/cmd_nand.c Bad usage of "nand" command
  1913. 53 common/cmd_nand.c correct usage of "nand" command
  1914. -54 common/cmd_nand.c No boot device
  1915. 54 common/cmd_nand.c boot device found
  1916. -55 common/cmd_nand.c Unknown Chip ID on boot device
  1917. 55 common/cmd_nand.c correct chip ID found, device available
  1918. -56 common/cmd_nand.c Error reading Image Header on boot device
  1919. 56 common/cmd_nand.c reading Image Header from NAND device OK
  1920. -57 common/cmd_nand.c Image header has bad magic number
  1921. 57 common/cmd_nand.c Image header has correct magic number
  1922. -58 common/cmd_nand.c Error reading Image from NAND device
  1923. 58 common/cmd_nand.c reading Image from NAND device OK
  1924. -60 common/env_common.c Environment has a bad CRC, using default
  1925. 64 net/eth.c starting with Ethernet configuration.
  1926. -64 net/eth.c no Ethernet found.
  1927. 65 net/eth.c Ethernet found.
  1928. -80 common/cmd_net.c usage wrong
  1929. 80 common/cmd_net.c before calling net_loop()
  1930. -81 common/cmd_net.c some error in net_loop() occurred
  1931. 81 common/cmd_net.c net_loop() back without error
  1932. -82 common/cmd_net.c size == 0 (File with size 0 loaded)
  1933. 82 common/cmd_net.c trying automatic boot
  1934. 83 common/cmd_net.c running "source" command
  1935. -83 common/cmd_net.c some error in automatic boot or "source" command
  1936. 84 common/cmd_net.c end without errors
  1937. FIT uImage format:
  1938. Arg Where When
  1939. 100 common/cmd_bootm.c Kernel FIT Image has correct format
  1940. -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
  1941. 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
  1942. -101 common/cmd_bootm.c Can't get configuration for kernel subimage
  1943. 102 common/cmd_bootm.c Kernel unit name specified
  1944. -103 common/cmd_bootm.c Can't get kernel subimage node offset
  1945. 103 common/cmd_bootm.c Found configuration node
  1946. 104 common/cmd_bootm.c Got kernel subimage node offset
  1947. -104 common/cmd_bootm.c Kernel subimage hash verification failed
  1948. 105 common/cmd_bootm.c Kernel subimage hash verification OK
  1949. -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
  1950. 106 common/cmd_bootm.c Architecture check OK
  1951. -106 common/cmd_bootm.c Kernel subimage has wrong type
  1952. 107 common/cmd_bootm.c Kernel subimage type OK
  1953. -107 common/cmd_bootm.c Can't get kernel subimage data/size
  1954. 108 common/cmd_bootm.c Got kernel subimage data/size
  1955. -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
  1956. -109 common/cmd_bootm.c Can't get kernel subimage type
  1957. -110 common/cmd_bootm.c Can't get kernel subimage comp
  1958. -111 common/cmd_bootm.c Can't get kernel subimage os
  1959. -112 common/cmd_bootm.c Can't get kernel subimage load address
  1960. -113 common/cmd_bootm.c Image uncompress/copy overwrite error
  1961. 120 common/image.c Start initial ramdisk verification
  1962. -120 common/image.c Ramdisk FIT image has incorrect format
  1963. 121 common/image.c Ramdisk FIT image has correct format
  1964. 122 common/image.c No ramdisk subimage unit name, using configuration
  1965. -122 common/image.c Can't get configuration for ramdisk subimage
  1966. 123 common/image.c Ramdisk unit name specified
  1967. -124 common/image.c Can't get ramdisk subimage node offset
  1968. 125 common/image.c Got ramdisk subimage node offset
  1969. -125 common/image.c Ramdisk subimage hash verification failed
  1970. 126 common/image.c Ramdisk subimage hash verification OK
  1971. -126 common/image.c Ramdisk subimage for unsupported architecture
  1972. 127 common/image.c Architecture check OK
  1973. -127 common/image.c Can't get ramdisk subimage data/size
  1974. 128 common/image.c Got ramdisk subimage data/size
  1975. 129 common/image.c Can't get ramdisk load address
  1976. -129 common/image.c Got ramdisk load address
  1977. -130 common/cmd_doc.c Incorrect FIT image format
  1978. 131 common/cmd_doc.c FIT image format OK
  1979. -140 common/cmd_ide.c Incorrect FIT image format
  1980. 141 common/cmd_ide.c FIT image format OK
  1981. -150 common/cmd_nand.c Incorrect FIT image format
  1982. 151 common/cmd_nand.c FIT image format OK
  1983. - legacy image format:
  1984. CONFIG_IMAGE_FORMAT_LEGACY
  1985. enables the legacy image format support in U-Boot.
  1986. Default:
  1987. enabled if CONFIG_FIT_SIGNATURE is not defined.
  1988. CONFIG_DISABLE_IMAGE_LEGACY
  1989. disable the legacy image format
  1990. This define is introduced, as the legacy image format is
  1991. enabled per default for backward compatibility.
  1992. - Standalone program support:
  1993. CONFIG_STANDALONE_LOAD_ADDR
  1994. This option defines a board specific value for the
  1995. address where standalone program gets loaded, thus
  1996. overwriting the architecture dependent default
  1997. settings.
  1998. - Frame Buffer Address:
  1999. CONFIG_FB_ADDR
  2000. Define CONFIG_FB_ADDR if you want to use specific
  2001. address for frame buffer. This is typically the case
  2002. when using a graphics controller has separate video
  2003. memory. U-Boot will then place the frame buffer at
  2004. the given address instead of dynamically reserving it
  2005. in system RAM by calling lcd_setmem(), which grabs
  2006. the memory for the frame buffer depending on the
  2007. configured panel size.
  2008. Please see board_init_f function.
  2009. - Automatic software updates via TFTP server
  2010. CONFIG_UPDATE_TFTP
  2011. CONFIG_UPDATE_TFTP_CNT_MAX
  2012. CONFIG_UPDATE_TFTP_MSEC_MAX
  2013. These options enable and control the auto-update feature;
  2014. for a more detailed description refer to doc/README.update.
  2015. - MTD Support (mtdparts command, UBI support)
  2016. CONFIG_MTD_DEVICE
  2017. Adds the MTD device infrastructure from the Linux kernel.
  2018. Needed for mtdparts command support.
  2019. CONFIG_MTD_PARTITIONS
  2020. Adds the MTD partitioning infrastructure from the Linux
  2021. kernel. Needed for UBI support.
  2022. - UBI support
  2023. CONFIG_UBI_SILENCE_MSG
  2024. Make the verbose messages from UBI stop printing. This leaves
  2025. warnings and errors enabled.
  2026. CONFIG_MTD_UBI_WL_THRESHOLD
  2027. This parameter defines the maximum difference between the highest
  2028. erase counter value and the lowest erase counter value of eraseblocks
  2029. of UBI devices. When this threshold is exceeded, UBI starts performing
  2030. wear leveling by means of moving data from eraseblock with low erase
  2031. counter to eraseblocks with high erase counter.
  2032. The default value should be OK for SLC NAND flashes, NOR flashes and
  2033. other flashes which have eraseblock life-cycle 100000 or more.
  2034. However, in case of MLC NAND flashes which typically have eraseblock
  2035. life-cycle less than 10000, the threshold should be lessened (e.g.,
  2036. to 128 or 256, although it does not have to be power of 2).
  2037. default: 4096
  2038. CONFIG_MTD_UBI_BEB_LIMIT
  2039. This option specifies the maximum bad physical eraseblocks UBI
  2040. expects on the MTD device (per 1024 eraseblocks). If the
  2041. underlying flash does not admit of bad eraseblocks (e.g. NOR
  2042. flash), this value is ignored.
  2043. NAND datasheets often specify the minimum and maximum NVM
  2044. (Number of Valid Blocks) for the flashes' endurance lifetime.
  2045. The maximum expected bad eraseblocks per 1024 eraseblocks
  2046. then can be calculated as "1024 * (1 - MinNVB / MaxNVB)",
  2047. which gives 20 for most NANDs (MaxNVB is basically the total
  2048. count of eraseblocks on the chip).
  2049. To put it differently, if this value is 20, UBI will try to
  2050. reserve about 1.9% of physical eraseblocks for bad blocks
  2051. handling. And that will be 1.9% of eraseblocks on the entire
  2052. NAND chip, not just the MTD partition UBI attaches. This means
  2053. that if you have, say, a NAND flash chip admits maximum 40 bad
  2054. eraseblocks, and it is split on two MTD partitions of the same
  2055. size, UBI will reserve 40 eraseblocks when attaching a
  2056. partition.
  2057. default: 20
  2058. CONFIG_MTD_UBI_FASTMAP
  2059. Fastmap is a mechanism which allows attaching an UBI device
  2060. in nearly constant time. Instead of scanning the whole MTD device it
  2061. only has to locate a checkpoint (called fastmap) on the device.
  2062. The on-flash fastmap contains all information needed to attach
  2063. the device. Using fastmap makes only sense on large devices where
  2064. attaching by scanning takes long. UBI will not automatically install
  2065. a fastmap on old images, but you can set the UBI parameter
  2066. CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT to 1 if you want so. Please note
  2067. that fastmap-enabled images are still usable with UBI implementations
  2068. without fastmap support. On typical flash devices the whole fastmap
  2069. fits into one PEB. UBI will reserve PEBs to hold two fastmaps.
  2070. CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT
  2071. Set this parameter to enable fastmap automatically on images
  2072. without a fastmap.
  2073. default: 0
  2074. CONFIG_MTD_UBI_FM_DEBUG
  2075. Enable UBI fastmap debug
  2076. default: 0
  2077. - UBIFS support
  2078. CONFIG_UBIFS_SILENCE_MSG
  2079. Make the verbose messages from UBIFS stop printing. This leaves
  2080. warnings and errors enabled.
  2081. - SPL framework
  2082. CONFIG_SPL
  2083. Enable building of SPL globally.
  2084. CONFIG_SPL_LDSCRIPT
  2085. LDSCRIPT for linking the SPL binary.
  2086. CONFIG_SPL_MAX_FOOTPRINT
  2087. Maximum size in memory allocated to the SPL, BSS included.
  2088. When defined, the linker checks that the actual memory
  2089. used by SPL from _start to __bss_end does not exceed it.
  2090. CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
  2091. must not be both defined at the same time.
  2092. CONFIG_SPL_MAX_SIZE
  2093. Maximum size of the SPL image (text, data, rodata, and
  2094. linker lists sections), BSS excluded.
  2095. When defined, the linker checks that the actual size does
  2096. not exceed it.
  2097. CONFIG_SPL_TEXT_BASE
  2098. TEXT_BASE for linking the SPL binary.
  2099. CONFIG_SPL_RELOC_TEXT_BASE
  2100. Address to relocate to. If unspecified, this is equal to
  2101. CONFIG_SPL_TEXT_BASE (i.e. no relocation is done).
  2102. CONFIG_SPL_BSS_START_ADDR
  2103. Link address for the BSS within the SPL binary.
  2104. CONFIG_SPL_BSS_MAX_SIZE
  2105. Maximum size in memory allocated to the SPL BSS.
  2106. When defined, the linker checks that the actual memory used
  2107. by SPL from __bss_start to __bss_end does not exceed it.
  2108. CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
  2109. must not be both defined at the same time.
  2110. CONFIG_SPL_STACK
  2111. Adress of the start of the stack SPL will use
  2112. CONFIG_SPL_PANIC_ON_RAW_IMAGE
  2113. When defined, SPL will panic() if the image it has
  2114. loaded does not have a signature.
  2115. Defining this is useful when code which loads images
  2116. in SPL cannot guarantee that absolutely all read errors
  2117. will be caught.
  2118. An example is the LPC32XX MLC NAND driver, which will
  2119. consider that a completely unreadable NAND block is bad,
  2120. and thus should be skipped silently.
  2121. CONFIG_SPL_RELOC_STACK
  2122. Adress of the start of the stack SPL will use after
  2123. relocation. If unspecified, this is equal to
  2124. CONFIG_SPL_STACK.
  2125. CONFIG_SYS_SPL_MALLOC_START
  2126. Starting address of the malloc pool used in SPL.
  2127. When this option is set the full malloc is used in SPL and
  2128. it is set up by spl_init() and before that, the simple malloc()
  2129. can be used if CONFIG_SYS_MALLOC_F is defined.
  2130. CONFIG_SYS_SPL_MALLOC_SIZE
  2131. The size of the malloc pool used in SPL.
  2132. CONFIG_SPL_FRAMEWORK
  2133. Enable the SPL framework under common/. This framework
  2134. supports MMC, NAND and YMODEM loading of U-Boot and NAND
  2135. NAND loading of the Linux Kernel.
  2136. CONFIG_SPL_OS_BOOT
  2137. Enable booting directly to an OS from SPL.
  2138. See also: doc/README.falcon
  2139. CONFIG_SPL_DISPLAY_PRINT
  2140. For ARM, enable an optional function to print more information
  2141. about the running system.
  2142. CONFIG_SPL_INIT_MINIMAL
  2143. Arch init code should be built for a very small image
  2144. CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
  2145. Partition on the MMC to load U-Boot from when the MMC is being
  2146. used in raw mode
  2147. CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
  2148. Sector to load kernel uImage from when MMC is being
  2149. used in raw mode (for Falcon mode)
  2150. CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR,
  2151. CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS
  2152. Sector and number of sectors to load kernel argument
  2153. parameters from when MMC is being used in raw mode
  2154. (for falcon mode)
  2155. CONFIG_SYS_MMCSD_FS_BOOT_PARTITION
  2156. Partition on the MMC to load U-Boot from when the MMC is being
  2157. used in fs mode
  2158. CONFIG_SPL_FS_LOAD_PAYLOAD_NAME
  2159. Filename to read to load U-Boot when reading from filesystem
  2160. CONFIG_SPL_FS_LOAD_KERNEL_NAME
  2161. Filename to read to load kernel uImage when reading
  2162. from filesystem (for Falcon mode)
  2163. CONFIG_SPL_FS_LOAD_ARGS_NAME
  2164. Filename to read to load kernel argument parameters
  2165. when reading from filesystem (for Falcon mode)
  2166. CONFIG_SPL_MPC83XX_WAIT_FOR_NAND
  2167. Set this for NAND SPL on PPC mpc83xx targets, so that
  2168. start.S waits for the rest of the SPL to load before
  2169. continuing (the hardware starts execution after just
  2170. loading the first page rather than the full 4K).
  2171. CONFIG_SPL_SKIP_RELOCATE
  2172. Avoid SPL relocation
  2173. CONFIG_SPL_NAND_BASE
  2174. Include nand_base.c in the SPL. Requires
  2175. CONFIG_SPL_NAND_DRIVERS.
  2176. CONFIG_SPL_NAND_DRIVERS
  2177. SPL uses normal NAND drivers, not minimal drivers.
  2178. CONFIG_SPL_NAND_ECC
  2179. Include standard software ECC in the SPL
  2180. CONFIG_SPL_NAND_SIMPLE
  2181. Support for NAND boot using simple NAND drivers that
  2182. expose the cmd_ctrl() interface.
  2183. CONFIG_SPL_UBI
  2184. Support for a lightweight UBI (fastmap) scanner and
  2185. loader
  2186. CONFIG_SPL_NAND_RAW_ONLY
  2187. Support to boot only raw u-boot.bin images. Use this only
  2188. if you need to save space.
  2189. CONFIG_SPL_COMMON_INIT_DDR
  2190. Set for common ddr init with serial presence detect in
  2191. SPL binary.
  2192. CONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT,
  2193. CONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE,
  2194. CONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS,
  2195. CONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE,
  2196. CONFIG_SYS_NAND_ECCBYTES
  2197. Defines the size and behavior of the NAND that SPL uses
  2198. to read U-Boot
  2199. CONFIG_SPL_NAND_BOOT
  2200. Add support NAND boot
  2201. CONFIG_SYS_NAND_U_BOOT_OFFS
  2202. Location in NAND to read U-Boot from
  2203. CONFIG_SYS_NAND_U_BOOT_DST
  2204. Location in memory to load U-Boot to
  2205. CONFIG_SYS_NAND_U_BOOT_SIZE
  2206. Size of image to load
  2207. CONFIG_SYS_NAND_U_BOOT_START
  2208. Entry point in loaded image to jump to
  2209. CONFIG_SYS_NAND_HW_ECC_OOBFIRST
  2210. Define this if you need to first read the OOB and then the
  2211. data. This is used, for example, on davinci platforms.
  2212. CONFIG_SPL_OMAP3_ID_NAND
  2213. Support for an OMAP3-specific set of functions to return the
  2214. ID and MFR of the first attached NAND chip, if present.
  2215. CONFIG_SPL_RAM_DEVICE
  2216. Support for running image already present in ram, in SPL binary
  2217. CONFIG_SPL_PAD_TO
  2218. Image offset to which the SPL should be padded before appending
  2219. the SPL payload. By default, this is defined as
  2220. CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
  2221. CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
  2222. payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
  2223. CONFIG_SPL_TARGET
  2224. Final target image containing SPL and payload. Some SPLs
  2225. use an arch-specific makefile fragment instead, for
  2226. example if more than one image needs to be produced.
  2227. CONFIG_FIT_SPL_PRINT
  2228. Printing information about a FIT image adds quite a bit of
  2229. code to SPL. So this is normally disabled in SPL. Use this
  2230. option to re-enable it. This will affect the output of the
  2231. bootm command when booting a FIT image.
  2232. - TPL framework
  2233. CONFIG_TPL
  2234. Enable building of TPL globally.
  2235. CONFIG_TPL_PAD_TO
  2236. Image offset to which the TPL should be padded before appending
  2237. the TPL payload. By default, this is defined as
  2238. CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
  2239. CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
  2240. payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
  2241. - Interrupt support (PPC):
  2242. There are common interrupt_init() and timer_interrupt()
  2243. for all PPC archs. interrupt_init() calls interrupt_init_cpu()
  2244. for CPU specific initialization. interrupt_init_cpu()
  2245. should set decrementer_count to appropriate value. If
  2246. CPU resets decrementer automatically after interrupt
  2247. (ppc4xx) it should set decrementer_count to zero.
  2248. timer_interrupt() calls timer_interrupt_cpu() for CPU
  2249. specific handling. If board has watchdog / status_led
  2250. / other_activity_monitor it works automatically from
  2251. general timer_interrupt().
  2252. Board initialization settings:
  2253. ------------------------------
  2254. During Initialization u-boot calls a number of board specific functions
  2255. to allow the preparation of board specific prerequisites, e.g. pin setup
  2256. before drivers are initialized. To enable these callbacks the
  2257. following configuration macros have to be defined. Currently this is
  2258. architecture specific, so please check arch/your_architecture/lib/board.c
  2259. typically in board_init_f() and board_init_r().
  2260. - CONFIG_BOARD_EARLY_INIT_F: Call board_early_init_f()
  2261. - CONFIG_BOARD_EARLY_INIT_R: Call board_early_init_r()
  2262. - CONFIG_BOARD_LATE_INIT: Call board_late_init()
  2263. - CONFIG_BOARD_POSTCLK_INIT: Call board_postclk_init()
  2264. Configuration Settings:
  2265. -----------------------
  2266. - CONFIG_SYS_SUPPORT_64BIT_DATA: Defined automatically if compiled as 64-bit.
  2267. Optionally it can be defined to support 64-bit memory commands.
  2268. - CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
  2269. undefine this when you're short of memory.
  2270. - CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default
  2271. width of the commands listed in the 'help' command output.
  2272. - CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to
  2273. prompt for user input.
  2274. - CONFIG_SYS_CBSIZE: Buffer size for input from the Console
  2275. - CONFIG_SYS_PBSIZE: Buffer size for Console output
  2276. - CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands
  2277. - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
  2278. the application (usually a Linux kernel) when it is
  2279. booted
  2280. - CONFIG_SYS_BAUDRATE_TABLE:
  2281. List of legal baudrate settings for this board.
  2282. - CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END:
  2283. Begin and End addresses of the area used by the
  2284. simple memory test.
  2285. - CONFIG_SYS_ALT_MEMTEST:
  2286. Enable an alternate, more extensive memory test.
  2287. - CONFIG_SYS_MEMTEST_SCRATCH:
  2288. Scratch address used by the alternate memory test
  2289. You only need to set this if address zero isn't writeable
  2290. - CONFIG_SYS_MEM_RESERVE_SECURE
  2291. Only implemented for ARMv8 for now.
  2292. If defined, the size of CONFIG_SYS_MEM_RESERVE_SECURE memory
  2293. is substracted from total RAM and won't be reported to OS.
  2294. This memory can be used as secure memory. A variable
  2295. gd->arch.secure_ram is used to track the location. In systems
  2296. the RAM base is not zero, or RAM is divided into banks,
  2297. this variable needs to be recalcuated to get the address.
  2298. - CONFIG_SYS_MEM_TOP_HIDE:
  2299. If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,
  2300. this specified memory area will get subtracted from the top
  2301. (end) of RAM and won't get "touched" at all by U-Boot. By
  2302. fixing up gd->ram_size the Linux kernel should gets passed
  2303. the now "corrected" memory size and won't touch it either.
  2304. This should work for arch/ppc and arch/powerpc. Only Linux
  2305. board ports in arch/powerpc with bootwrapper support that
  2306. recalculate the memory size from the SDRAM controller setup
  2307. will have to get fixed in Linux additionally.
  2308. This option can be used as a workaround for the 440EPx/GRx
  2309. CHIP 11 errata where the last 256 bytes in SDRAM shouldn't
  2310. be touched.
  2311. WARNING: Please make sure that this value is a multiple of
  2312. the Linux page size (normally 4k). If this is not the case,
  2313. then the end address of the Linux memory will be located at a
  2314. non page size aligned address and this could cause major
  2315. problems.
  2316. - CONFIG_SYS_LOADS_BAUD_CHANGE:
  2317. Enable temporary baudrate change while serial download
  2318. - CONFIG_SYS_SDRAM_BASE:
  2319. Physical start address of SDRAM. _Must_ be 0 here.
  2320. - CONFIG_SYS_FLASH_BASE:
  2321. Physical start address of Flash memory.
  2322. - CONFIG_SYS_MONITOR_BASE:
  2323. Physical start address of boot monitor code (set by
  2324. make config files to be same as the text base address
  2325. (CONFIG_SYS_TEXT_BASE) used when linking) - same as
  2326. CONFIG_SYS_FLASH_BASE when booting from flash.
  2327. - CONFIG_SYS_MONITOR_LEN:
  2328. Size of memory reserved for monitor code, used to
  2329. determine _at_compile_time_ (!) if the environment is
  2330. embedded within the U-Boot image, or in a separate
  2331. flash sector.
  2332. - CONFIG_SYS_MALLOC_LEN:
  2333. Size of DRAM reserved for malloc() use.
  2334. - CONFIG_SYS_MALLOC_F_LEN
  2335. Size of the malloc() pool for use before relocation. If
  2336. this is defined, then a very simple malloc() implementation
  2337. will become available before relocation. The address is just
  2338. below the global data, and the stack is moved down to make
  2339. space.
  2340. This feature allocates regions with increasing addresses
  2341. within the region. calloc() is supported, but realloc()
  2342. is not available. free() is supported but does nothing.
  2343. The memory will be freed (or in fact just forgotten) when
  2344. U-Boot relocates itself.
  2345. - CONFIG_SYS_MALLOC_SIMPLE
  2346. Provides a simple and small malloc() and calloc() for those
  2347. boards which do not use the full malloc in SPL (which is
  2348. enabled with CONFIG_SYS_SPL_MALLOC_START).
  2349. - CONFIG_SYS_NONCACHED_MEMORY:
  2350. Size of non-cached memory area. This area of memory will be
  2351. typically located right below the malloc() area and mapped
  2352. uncached in the MMU. This is useful for drivers that would
  2353. otherwise require a lot of explicit cache maintenance. For
  2354. some drivers it's also impossible to properly maintain the
  2355. cache. For example if the regions that need to be flushed
  2356. are not a multiple of the cache-line size, *and* padding
  2357. cannot be allocated between the regions to align them (i.e.
  2358. if the HW requires a contiguous array of regions, and the
  2359. size of each region is not cache-aligned), then a flush of
  2360. one region may result in overwriting data that hardware has
  2361. written to another region in the same cache-line. This can
  2362. happen for example in network drivers where descriptors for
  2363. buffers are typically smaller than the CPU cache-line (e.g.
  2364. 16 bytes vs. 32 or 64 bytes).
  2365. Non-cached memory is only supported on 32-bit ARM at present.
  2366. - CONFIG_SYS_BOOTM_LEN:
  2367. Normally compressed uImages are limited to an
  2368. uncompressed size of 8 MBytes. If this is not enough,
  2369. you can define CONFIG_SYS_BOOTM_LEN in your board config file
  2370. to adjust this setting to your needs.
  2371. - CONFIG_SYS_BOOTMAPSZ:
  2372. Maximum size of memory mapped by the startup code of
  2373. the Linux kernel; all data that must be processed by
  2374. the Linux kernel (bd_info, boot arguments, FDT blob if
  2375. used) must be put below this limit, unless "bootm_low"
  2376. environment variable is defined and non-zero. In such case
  2377. all data for the Linux kernel must be between "bootm_low"
  2378. and "bootm_low" + CONFIG_SYS_BOOTMAPSZ. The environment
  2379. variable "bootm_mapsize" will override the value of
  2380. CONFIG_SYS_BOOTMAPSZ. If CONFIG_SYS_BOOTMAPSZ is undefined,
  2381. then the value in "bootm_size" will be used instead.
  2382. - CONFIG_SYS_BOOT_RAMDISK_HIGH:
  2383. Enable initrd_high functionality. If defined then the
  2384. initrd_high feature is enabled and the bootm ramdisk subcommand
  2385. is enabled.
  2386. - CONFIG_SYS_BOOT_GET_CMDLINE:
  2387. Enables allocating and saving kernel cmdline in space between
  2388. "bootm_low" and "bootm_low" + BOOTMAPSZ.
  2389. - CONFIG_SYS_BOOT_GET_KBD:
  2390. Enables allocating and saving a kernel copy of the bd_info in
  2391. space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
  2392. - CONFIG_SYS_MAX_FLASH_BANKS:
  2393. Max number of Flash memory banks
  2394. - CONFIG_SYS_MAX_FLASH_SECT:
  2395. Max number of sectors on a Flash chip
  2396. - CONFIG_SYS_FLASH_ERASE_TOUT:
  2397. Timeout for Flash erase operations (in ms)
  2398. - CONFIG_SYS_FLASH_WRITE_TOUT:
  2399. Timeout for Flash write operations (in ms)
  2400. - CONFIG_SYS_FLASH_LOCK_TOUT
  2401. Timeout for Flash set sector lock bit operation (in ms)
  2402. - CONFIG_SYS_FLASH_UNLOCK_TOUT
  2403. Timeout for Flash clear lock bits operation (in ms)
  2404. - CONFIG_SYS_FLASH_PROTECTION
  2405. If defined, hardware flash sectors protection is used
  2406. instead of U-Boot software protection.
  2407. - CONFIG_SYS_DIRECT_FLASH_TFTP:
  2408. Enable TFTP transfers directly to flash memory;
  2409. without this option such a download has to be
  2410. performed in two steps: (1) download to RAM, and (2)
  2411. copy from RAM to flash.
  2412. The two-step approach is usually more reliable, since
  2413. you can check if the download worked before you erase
  2414. the flash, but in some situations (when system RAM is
  2415. too limited to allow for a temporary copy of the
  2416. downloaded image) this option may be very useful.
  2417. - CONFIG_SYS_FLASH_CFI:
  2418. Define if the flash driver uses extra elements in the
  2419. common flash structure for storing flash geometry.
  2420. - CONFIG_FLASH_CFI_DRIVER
  2421. This option also enables the building of the cfi_flash driver
  2422. in the drivers directory
  2423. - CONFIG_FLASH_CFI_MTD
  2424. This option enables the building of the cfi_mtd driver
  2425. in the drivers directory. The driver exports CFI flash
  2426. to the MTD layer.
  2427. - CONFIG_SYS_FLASH_USE_BUFFER_WRITE
  2428. Use buffered writes to flash.
  2429. - CONFIG_FLASH_SPANSION_S29WS_N
  2430. s29ws-n MirrorBit flash has non-standard addresses for buffered
  2431. write commands.
  2432. - CONFIG_SYS_FLASH_QUIET_TEST
  2433. If this option is defined, the common CFI flash doesn't
  2434. print it's warning upon not recognized FLASH banks. This
  2435. is useful, if some of the configured banks are only
  2436. optionally available.
  2437. - CONFIG_FLASH_SHOW_PROGRESS
  2438. If defined (must be an integer), print out countdown
  2439. digits and dots. Recommended value: 45 (9..1) for 80
  2440. column displays, 15 (3..1) for 40 column displays.
  2441. - CONFIG_FLASH_VERIFY
  2442. If defined, the content of the flash (destination) is compared
  2443. against the source after the write operation. An error message
  2444. will be printed when the contents are not identical.
  2445. Please note that this option is useless in nearly all cases,
  2446. since such flash programming errors usually are detected earlier
  2447. while unprotecting/erasing/programming. Please only enable
  2448. this option if you really know what you are doing.
  2449. - CONFIG_SYS_RX_ETH_BUFFER:
  2450. Defines the number of Ethernet receive buffers. On some
  2451. Ethernet controllers it is recommended to set this value
  2452. to 8 or even higher (EEPRO100 or 405 EMAC), since all
  2453. buffers can be full shortly after enabling the interface
  2454. on high Ethernet traffic.
  2455. Defaults to 4 if not defined.
  2456. - CONFIG_ENV_MAX_ENTRIES
  2457. Maximum number of entries in the hash table that is used
  2458. internally to store the environment settings. The default
  2459. setting is supposed to be generous and should work in most
  2460. cases. This setting can be used to tune behaviour; see
  2461. lib/hashtable.c for details.
  2462. - CONFIG_ENV_FLAGS_LIST_DEFAULT
  2463. - CONFIG_ENV_FLAGS_LIST_STATIC
  2464. Enable validation of the values given to environment variables when
  2465. calling env set. Variables can be restricted to only decimal,
  2466. hexadecimal, or boolean. If CONFIG_CMD_NET is also defined,
  2467. the variables can also be restricted to IP address or MAC address.
  2468. The format of the list is:
  2469. type_attribute = [s|d|x|b|i|m]
  2470. access_attribute = [a|r|o|c]
  2471. attributes = type_attribute[access_attribute]
  2472. entry = variable_name[:attributes]
  2473. list = entry[,list]
  2474. The type attributes are:
  2475. s - String (default)
  2476. d - Decimal
  2477. x - Hexadecimal
  2478. b - Boolean ([1yYtT|0nNfF])
  2479. i - IP address
  2480. m - MAC address
  2481. The access attributes are:
  2482. a - Any (default)
  2483. r - Read-only
  2484. o - Write-once
  2485. c - Change-default
  2486. - CONFIG_ENV_FLAGS_LIST_DEFAULT
  2487. Define this to a list (string) to define the ".flags"
  2488. environment variable in the default or embedded environment.
  2489. - CONFIG_ENV_FLAGS_LIST_STATIC
  2490. Define this to a list (string) to define validation that
  2491. should be done if an entry is not found in the ".flags"
  2492. environment variable. To override a setting in the static
  2493. list, simply add an entry for the same variable name to the
  2494. ".flags" variable.
  2495. If CONFIG_REGEX is defined, the variable_name above is evaluated as a
  2496. regular expression. This allows multiple variables to define the same
  2497. flags without explicitly listing them for each variable.
  2498. - CONFIG_ENV_ACCESS_IGNORE_FORCE
  2499. If defined, don't allow the -f switch to env set override variable
  2500. access flags.
  2501. - CONFIG_USE_STDINT
  2502. If stdint.h is available with your toolchain you can define this
  2503. option to enable it. You can provide option 'USE_STDINT=1' when
  2504. building U-Boot to enable this.
  2505. The following definitions that deal with the placement and management
  2506. of environment data (variable area); in general, we support the
  2507. following configurations:
  2508. - CONFIG_BUILD_ENVCRC:
  2509. Builds up envcrc with the target environment so that external utils
  2510. may easily extract it and embed it in final U-Boot images.
  2511. BE CAREFUL! The first access to the environment happens quite early
  2512. in U-Boot initialization (when we try to get the setting of for the
  2513. console baudrate). You *MUST* have mapped your NVRAM area then, or
  2514. U-Boot will hang.
  2515. Please note that even with NVRAM we still use a copy of the
  2516. environment in RAM: we could work on NVRAM directly, but we want to
  2517. keep settings there always unmodified except somebody uses "saveenv"
  2518. to save the current settings.
  2519. BE CAREFUL! For some special cases, the local device can not use
  2520. "saveenv" command. For example, the local device will get the
  2521. environment stored in a remote NOR flash by SRIO or PCIE link,
  2522. but it can not erase, write this NOR flash by SRIO or PCIE interface.
  2523. - CONFIG_NAND_ENV_DST
  2524. Defines address in RAM to which the nand_spl code should copy the
  2525. environment. If redundant environment is used, it will be copied to
  2526. CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE.
  2527. Please note that the environment is read-only until the monitor
  2528. has been relocated to RAM and a RAM copy of the environment has been
  2529. created; also, when using EEPROM you will have to use env_get_f()
  2530. until then to read environment variables.
  2531. The environment is protected by a CRC32 checksum. Before the monitor
  2532. is relocated into RAM, as a result of a bad CRC you will be working
  2533. with the compiled-in default environment - *silently*!!! [This is
  2534. necessary, because the first environment variable we need is the
  2535. "baudrate" setting for the console - if we have a bad CRC, we don't
  2536. have any device yet where we could complain.]
  2537. Note: once the monitor has been relocated, then it will complain if
  2538. the default environment is used; a new CRC is computed as soon as you
  2539. use the "saveenv" command to store a valid environment.
  2540. - CONFIG_SYS_FAULT_ECHO_LINK_DOWN:
  2541. Echo the inverted Ethernet link state to the fault LED.
  2542. Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR
  2543. also needs to be defined.
  2544. - CONFIG_SYS_FAULT_MII_ADDR:
  2545. MII address of the PHY to check for the Ethernet link state.
  2546. - CONFIG_NS16550_MIN_FUNCTIONS:
  2547. Define this if you desire to only have use of the NS16550_init
  2548. and NS16550_putc functions for the serial driver located at
  2549. drivers/serial/ns16550.c. This option is useful for saving
  2550. space for already greatly restricted images, including but not
  2551. limited to NAND_SPL configurations.
  2552. - CONFIG_DISPLAY_BOARDINFO
  2553. Display information about the board that U-Boot is running on
  2554. when U-Boot starts up. The board function checkboard() is called
  2555. to do this.
  2556. - CONFIG_DISPLAY_BOARDINFO_LATE
  2557. Similar to the previous option, but display this information
  2558. later, once stdio is running and output goes to the LCD, if
  2559. present.
  2560. - CONFIG_BOARD_SIZE_LIMIT:
  2561. Maximum size of the U-Boot image. When defined, the
  2562. build system checks that the actual size does not
  2563. exceed it.
  2564. Low Level (hardware related) configuration options:
  2565. ---------------------------------------------------
  2566. - CONFIG_SYS_CACHELINE_SIZE:
  2567. Cache Line Size of the CPU.
  2568. - CONFIG_SYS_CCSRBAR_DEFAULT:
  2569. Default (power-on reset) physical address of CCSR on Freescale
  2570. PowerPC SOCs.
  2571. - CONFIG_SYS_CCSRBAR:
  2572. Virtual address of CCSR. On a 32-bit build, this is typically
  2573. the same value as CONFIG_SYS_CCSRBAR_DEFAULT.
  2574. - CONFIG_SYS_CCSRBAR_PHYS:
  2575. Physical address of CCSR. CCSR can be relocated to a new
  2576. physical address, if desired. In this case, this macro should
  2577. be set to that address. Otherwise, it should be set to the
  2578. same value as CONFIG_SYS_CCSRBAR_DEFAULT. For example, CCSR
  2579. is typically relocated on 36-bit builds. It is recommended
  2580. that this macro be defined via the _HIGH and _LOW macros:
  2581. #define CONFIG_SYS_CCSRBAR_PHYS ((CONFIG_SYS_CCSRBAR_PHYS_HIGH
  2582. * 1ull) << 32 | CONFIG_SYS_CCSRBAR_PHYS_LOW)
  2583. - CONFIG_SYS_CCSRBAR_PHYS_HIGH:
  2584. Bits 33-36 of CONFIG_SYS_CCSRBAR_PHYS. This value is typically
  2585. either 0 (32-bit build) or 0xF (36-bit build). This macro is
  2586. used in assembly code, so it must not contain typecasts or
  2587. integer size suffixes (e.g. "ULL").
  2588. - CONFIG_SYS_CCSRBAR_PHYS_LOW:
  2589. Lower 32-bits of CONFIG_SYS_CCSRBAR_PHYS. This macro is
  2590. used in assembly code, so it must not contain typecasts or
  2591. integer size suffixes (e.g. "ULL").
  2592. - CONFIG_SYS_CCSR_DO_NOT_RELOCATE:
  2593. If this macro is defined, then CONFIG_SYS_CCSRBAR_PHYS will be
  2594. forced to a value that ensures that CCSR is not relocated.
  2595. - Floppy Disk Support:
  2596. CONFIG_SYS_FDC_DRIVE_NUMBER
  2597. the default drive number (default value 0)
  2598. CONFIG_SYS_ISA_IO_STRIDE
  2599. defines the spacing between FDC chipset registers
  2600. (default value 1)
  2601. CONFIG_SYS_ISA_IO_OFFSET
  2602. defines the offset of register from address. It
  2603. depends on which part of the data bus is connected to
  2604. the FDC chipset. (default value 0)
  2605. If CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and
  2606. CONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their
  2607. default value.
  2608. if CONFIG_SYS_FDC_HW_INIT is defined, then the function
  2609. fdc_hw_init() is called at the beginning of the FDC
  2610. setup. fdc_hw_init() must be provided by the board
  2611. source code. It is used to make hardware-dependent
  2612. initializations.
  2613. - CONFIG_IDE_AHB:
  2614. Most IDE controllers were designed to be connected with PCI
  2615. interface. Only few of them were designed for AHB interface.
  2616. When software is doing ATA command and data transfer to
  2617. IDE devices through IDE-AHB controller, some additional
  2618. registers accessing to these kind of IDE-AHB controller
  2619. is required.
  2620. - CONFIG_SYS_IMMR: Physical address of the Internal Memory.
  2621. DO NOT CHANGE unless you know exactly what you're
  2622. doing! (11-4) [MPC8xx systems only]
  2623. - CONFIG_SYS_INIT_RAM_ADDR:
  2624. Start address of memory area that can be used for
  2625. initial data and stack; please note that this must be
  2626. writable memory that is working WITHOUT special
  2627. initialization, i. e. you CANNOT use normal RAM which
  2628. will become available only after programming the
  2629. memory controller and running certain initialization
  2630. sequences.
  2631. U-Boot uses the following memory types:
  2632. - MPC8xx: IMMR (internal memory of the CPU)
  2633. - CONFIG_SYS_GBL_DATA_OFFSET:
  2634. Offset of the initial data structure in the memory
  2635. area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually
  2636. CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial
  2637. data is located at the end of the available space
  2638. (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE -
  2639. GENERATED_GBL_DATA_SIZE), and the initial stack is just
  2640. below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR +
  2641. CONFIG_SYS_GBL_DATA_OFFSET) downward.
  2642. Note:
  2643. On the MPC824X (or other systems that use the data
  2644. cache for initial memory) the address chosen for
  2645. CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must
  2646. point to an otherwise UNUSED address space between
  2647. the top of RAM and the start of the PCI space.
  2648. - CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27)
  2649. - CONFIG_SYS_OR_TIMING_SDRAM:
  2650. SDRAM timing
  2651. - CONFIG_SYS_MAMR_PTA:
  2652. periodic timer for refresh
  2653. - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM,
  2654. CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP,
  2655. CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM,
  2656. CONFIG_SYS_BR1_PRELIM:
  2657. Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
  2658. - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
  2659. CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM,
  2660. CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM:
  2661. Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
  2662. - CONFIG_PCI_ENUM_ONLY
  2663. Only scan through and get the devices on the buses.
  2664. Don't do any setup work, presumably because someone or
  2665. something has already done it, and we don't need to do it
  2666. a second time. Useful for platforms that are pre-booted
  2667. by coreboot or similar.
  2668. - CONFIG_PCI_INDIRECT_BRIDGE:
  2669. Enable support for indirect PCI bridges.
  2670. - CONFIG_SYS_SRIO:
  2671. Chip has SRIO or not
  2672. - CONFIG_SRIO1:
  2673. Board has SRIO 1 port available
  2674. - CONFIG_SRIO2:
  2675. Board has SRIO 2 port available
  2676. - CONFIG_SRIO_PCIE_BOOT_MASTER
  2677. Board can support master function for Boot from SRIO and PCIE
  2678. - CONFIG_SYS_SRIOn_MEM_VIRT:
  2679. Virtual Address of SRIO port 'n' memory region
  2680. - CONFIG_SYS_SRIOn_MEM_PHYS:
  2681. Physical Address of SRIO port 'n' memory region
  2682. - CONFIG_SYS_SRIOn_MEM_SIZE:
  2683. Size of SRIO port 'n' memory region
  2684. - CONFIG_SYS_NAND_BUSWIDTH_16BIT
  2685. Defined to tell the NAND controller that the NAND chip is using
  2686. a 16 bit bus.
  2687. Not all NAND drivers use this symbol.
  2688. Example of drivers that use it:
  2689. - drivers/mtd/nand/ndfc.c
  2690. - drivers/mtd/nand/mxc_nand.c
  2691. - CONFIG_SYS_NDFC_EBC0_CFG
  2692. Sets the EBC0_CFG register for the NDFC. If not defined
  2693. a default value will be used.
  2694. - CONFIG_SPD_EEPROM
  2695. Get DDR timing information from an I2C EEPROM. Common
  2696. with pluggable memory modules such as SODIMMs
  2697. SPD_EEPROM_ADDRESS
  2698. I2C address of the SPD EEPROM
  2699. - CONFIG_SYS_SPD_BUS_NUM
  2700. If SPD EEPROM is on an I2C bus other than the first
  2701. one, specify here. Note that the value must resolve
  2702. to something your driver can deal with.
  2703. - CONFIG_SYS_DDR_RAW_TIMING
  2704. Get DDR timing information from other than SPD. Common with
  2705. soldered DDR chips onboard without SPD. DDR raw timing
  2706. parameters are extracted from datasheet and hard-coded into
  2707. header files or board specific files.
  2708. - CONFIG_FSL_DDR_INTERACTIVE
  2709. Enable interactive DDR debugging. See doc/README.fsl-ddr.
  2710. - CONFIG_FSL_DDR_SYNC_REFRESH
  2711. Enable sync of refresh for multiple controllers.
  2712. - CONFIG_FSL_DDR_BIST
  2713. Enable built-in memory test for Freescale DDR controllers.
  2714. - CONFIG_SYS_83XX_DDR_USES_CS0
  2715. Only for 83xx systems. If specified, then DDR should
  2716. be configured using CS0 and CS1 instead of CS2 and CS3.
  2717. - CONFIG_RMII
  2718. Enable RMII mode for all FECs.
  2719. Note that this is a global option, we can't
  2720. have one FEC in standard MII mode and another in RMII mode.
  2721. - CONFIG_CRC32_VERIFY
  2722. Add a verify option to the crc32 command.
  2723. The syntax is:
  2724. => crc32 -v <address> <count> <crc32>
  2725. Where address/count indicate a memory area
  2726. and crc32 is the correct crc32 which the
  2727. area should have.
  2728. - CONFIG_LOOPW
  2729. Add the "loopw" memory command. This only takes effect if
  2730. the memory commands are activated globally (CONFIG_CMD_MEMORY).
  2731. - CONFIG_MX_CYCLIC
  2732. Add the "mdc" and "mwc" memory commands. These are cyclic
  2733. "md/mw" commands.
  2734. Examples:
  2735. => mdc.b 10 4 500
  2736. This command will print 4 bytes (10,11,12,13) each 500 ms.
  2737. => mwc.l 100 12345678 10
  2738. This command will write 12345678 to address 100 all 10 ms.
  2739. This only takes effect if the memory commands are activated
  2740. globally (CONFIG_CMD_MEMORY).
  2741. - CONFIG_SKIP_LOWLEVEL_INIT
  2742. [ARM, NDS32, MIPS only] If this variable is defined, then certain
  2743. low level initializations (like setting up the memory
  2744. controller) are omitted and/or U-Boot does not
  2745. relocate itself into RAM.
  2746. Normally this variable MUST NOT be defined. The only
  2747. exception is when U-Boot is loaded (to RAM) by some
  2748. other boot loader or by a debugger which performs
  2749. these initializations itself.
  2750. - CONFIG_SKIP_LOWLEVEL_INIT_ONLY
  2751. [ARM926EJ-S only] This allows just the call to lowlevel_init()
  2752. to be skipped. The normal CP15 init (such as enabling the
  2753. instruction cache) is still performed.
  2754. - CONFIG_SPL_BUILD
  2755. Modifies the behaviour of start.S when compiling a loader
  2756. that is executed before the actual U-Boot. E.g. when
  2757. compiling a NAND SPL.
  2758. - CONFIG_TPL_BUILD
  2759. Modifies the behaviour of start.S when compiling a loader
  2760. that is executed after the SPL and before the actual U-Boot.
  2761. It is loaded by the SPL.
  2762. - CONFIG_SYS_MPC85XX_NO_RESETVEC
  2763. Only for 85xx systems. If this variable is specified, the section
  2764. .resetvec is not kept and the section .bootpg is placed in the
  2765. previous 4k of the .text section.
  2766. - CONFIG_ARCH_MAP_SYSMEM
  2767. Generally U-Boot (and in particular the md command) uses
  2768. effective address. It is therefore not necessary to regard
  2769. U-Boot address as virtual addresses that need to be translated
  2770. to physical addresses. However, sandbox requires this, since
  2771. it maintains its own little RAM buffer which contains all
  2772. addressable memory. This option causes some memory accesses
  2773. to be mapped through map_sysmem() / unmap_sysmem().
  2774. - CONFIG_X86_RESET_VECTOR
  2775. If defined, the x86 reset vector code is included. This is not
  2776. needed when U-Boot is running from Coreboot.
  2777. - CONFIG_SPL_AM33XX_ENABLE_RTC32K_OSC:
  2778. Enables the RTC32K OSC on AM33xx based plattforms
  2779. - CONFIG_SYS_NAND_NO_SUBPAGE_WRITE
  2780. Option to disable subpage write in NAND driver
  2781. driver that uses this:
  2782. drivers/mtd/nand/davinci_nand.c
  2783. Freescale QE/FMAN Firmware Support:
  2784. -----------------------------------
  2785. The Freescale QUICCEngine (QE) and Frame Manager (FMAN) both support the
  2786. loading of "firmware", which is encoded in the QE firmware binary format.
  2787. This firmware often needs to be loaded during U-Boot booting, so macros
  2788. are used to identify the storage device (NOR flash, SPI, etc) and the address
  2789. within that device.
  2790. - CONFIG_SYS_FMAN_FW_ADDR
  2791. The address in the storage device where the FMAN microcode is located. The
  2792. meaning of this address depends on which CONFIG_SYS_QE_FW_IN_xxx macro
  2793. is also specified.
  2794. - CONFIG_SYS_QE_FW_ADDR
  2795. The address in the storage device where the QE microcode is located. The
  2796. meaning of this address depends on which CONFIG_SYS_QE_FW_IN_xxx macro
  2797. is also specified.
  2798. - CONFIG_SYS_QE_FMAN_FW_LENGTH
  2799. The maximum possible size of the firmware. The firmware binary format
  2800. has a field that specifies the actual size of the firmware, but it
  2801. might not be possible to read any part of the firmware unless some
  2802. local storage is allocated to hold the entire firmware first.
  2803. - CONFIG_SYS_QE_FMAN_FW_IN_NOR
  2804. Specifies that QE/FMAN firmware is located in NOR flash, mapped as
  2805. normal addressable memory via the LBC. CONFIG_SYS_FMAN_FW_ADDR is the
  2806. virtual address in NOR flash.
  2807. - CONFIG_SYS_QE_FMAN_FW_IN_NAND
  2808. Specifies that QE/FMAN firmware is located in NAND flash.
  2809. CONFIG_SYS_FMAN_FW_ADDR is the offset within NAND flash.
  2810. - CONFIG_SYS_QE_FMAN_FW_IN_MMC
  2811. Specifies that QE/FMAN firmware is located on the primary SD/MMC
  2812. device. CONFIG_SYS_FMAN_FW_ADDR is the byte offset on that device.
  2813. - CONFIG_SYS_QE_FMAN_FW_IN_REMOTE
  2814. Specifies that QE/FMAN firmware is located in the remote (master)
  2815. memory space. CONFIG_SYS_FMAN_FW_ADDR is a virtual address which
  2816. can be mapped from slave TLB->slave LAW->slave SRIO or PCIE outbound
  2817. window->master inbound window->master LAW->the ucode address in
  2818. master's memory space.
  2819. Freescale Layerscape Management Complex Firmware Support:
  2820. ---------------------------------------------------------
  2821. The Freescale Layerscape Management Complex (MC) supports the loading of
  2822. "firmware".
  2823. This firmware often needs to be loaded during U-Boot booting, so macros
  2824. are used to identify the storage device (NOR flash, SPI, etc) and the address
  2825. within that device.
  2826. - CONFIG_FSL_MC_ENET
  2827. Enable the MC driver for Layerscape SoCs.
  2828. Freescale Layerscape Debug Server Support:
  2829. -------------------------------------------
  2830. The Freescale Layerscape Debug Server Support supports the loading of
  2831. "Debug Server firmware" and triggering SP boot-rom.
  2832. This firmware often needs to be loaded during U-Boot booting.
  2833. - CONFIG_SYS_MC_RSV_MEM_ALIGN
  2834. Define alignment of reserved memory MC requires
  2835. Reproducible builds
  2836. -------------------
  2837. In order to achieve reproducible builds, timestamps used in the U-Boot build
  2838. process have to be set to a fixed value.
  2839. This is done using the SOURCE_DATE_EPOCH environment variable.
  2840. SOURCE_DATE_EPOCH is to be set on the build host's shell, not as a configuration
  2841. option for U-Boot or an environment variable in U-Boot.
  2842. SOURCE_DATE_EPOCH should be set to a number of seconds since the epoch, in UTC.
  2843. Building the Software:
  2844. ======================
  2845. Building U-Boot has been tested in several native build environments
  2846. and in many different cross environments. Of course we cannot support
  2847. all possibly existing versions of cross development tools in all
  2848. (potentially obsolete) versions. In case of tool chain problems we
  2849. recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK)
  2850. which is extensively used to build and test U-Boot.
  2851. If you are not using a native environment, it is assumed that you
  2852. have GNU cross compiling tools available in your path. In this case,
  2853. you must set the environment variable CROSS_COMPILE in your shell.
  2854. Note that no changes to the Makefile or any other source files are
  2855. necessary. For example using the ELDK on a 4xx CPU, please enter:
  2856. $ CROSS_COMPILE=ppc_4xx-
  2857. $ export CROSS_COMPILE
  2858. Note: If you wish to generate Windows versions of the utilities in
  2859. the tools directory you can use the MinGW toolchain
  2860. (http://www.mingw.org). Set your HOST tools to the MinGW
  2861. toolchain and execute 'make tools'. For example:
  2862. $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools
  2863. Binaries such as tools/mkimage.exe will be created which can
  2864. be executed on computers running Windows.
  2865. U-Boot is intended to be simple to build. After installing the
  2866. sources you must configure U-Boot for one specific board type. This
  2867. is done by typing:
  2868. make NAME_defconfig
  2869. where "NAME_defconfig" is the name of one of the existing configu-
  2870. rations; see boards.cfg for supported names.
  2871. Note: for some board special configuration names may exist; check if
  2872. additional information is available from the board vendor; for
  2873. instance, the TQM823L systems are available without (standard)
  2874. or with LCD support. You can select such additional "features"
  2875. when choosing the configuration, i. e.
  2876. make TQM823L_defconfig
  2877. - will configure for a plain TQM823L, i. e. no LCD support
  2878. make TQM823L_LCD_defconfig
  2879. - will configure for a TQM823L with U-Boot console on LCD
  2880. etc.
  2881. Finally, type "make all", and you should get some working U-Boot
  2882. images ready for download to / installation on your system:
  2883. - "u-boot.bin" is a raw binary image
  2884. - "u-boot" is an image in ELF binary format
  2885. - "u-boot.srec" is in Motorola S-Record format
  2886. By default the build is performed locally and the objects are saved
  2887. in the source directory. One of the two methods can be used to change
  2888. this behavior and build U-Boot to some external directory:
  2889. 1. Add O= to the make command line invocations:
  2890. make O=/tmp/build distclean
  2891. make O=/tmp/build NAME_defconfig
  2892. make O=/tmp/build all
  2893. 2. Set environment variable KBUILD_OUTPUT to point to the desired location:
  2894. export KBUILD_OUTPUT=/tmp/build
  2895. make distclean
  2896. make NAME_defconfig
  2897. make all
  2898. Note that the command line "O=" setting overrides the KBUILD_OUTPUT environment
  2899. variable.
  2900. Please be aware that the Makefiles assume you are using GNU make, so
  2901. for instance on NetBSD you might need to use "gmake" instead of
  2902. native "make".
  2903. If the system board that you have is not listed, then you will need
  2904. to port U-Boot to your hardware platform. To do this, follow these
  2905. steps:
  2906. 1. Create a new directory to hold your board specific code. Add any
  2907. files you need. In your board directory, you will need at least
  2908. the "Makefile" and a "<board>.c".
  2909. 2. Create a new configuration file "include/configs/<board>.h" for
  2910. your board.
  2911. 3. If you're porting U-Boot to a new CPU, then also create a new
  2912. directory to hold your CPU specific code. Add any files you need.
  2913. 4. Run "make <board>_defconfig" with your new name.
  2914. 5. Type "make", and you should get a working "u-boot.srec" file
  2915. to be installed on your target system.
  2916. 6. Debug and solve any problems that might arise.
  2917. [Of course, this last step is much harder than it sounds.]
  2918. Testing of U-Boot Modifications, Ports to New Hardware, etc.:
  2919. ==============================================================
  2920. If you have modified U-Boot sources (for instance added a new board
  2921. or support for new devices, a new CPU, etc.) you are expected to
  2922. provide feedback to the other developers. The feedback normally takes
  2923. the form of a "patch", i. e. a context diff against a certain (latest
  2924. official or latest in the git repository) version of U-Boot sources.
  2925. But before you submit such a patch, please verify that your modifi-
  2926. cation did not break existing code. At least make sure that *ALL* of
  2927. the supported boards compile WITHOUT ANY compiler warnings. To do so,
  2928. just run the buildman script (tools/buildman/buildman), which will
  2929. configure and build U-Boot for ALL supported system. Be warned, this
  2930. will take a while. Please see the buildman README, or run 'buildman -H'
  2931. for documentation.
  2932. See also "U-Boot Porting Guide" below.
  2933. Monitor Commands - Overview:
  2934. ============================
  2935. go - start application at address 'addr'
  2936. run - run commands in an environment variable
  2937. bootm - boot application image from memory
  2938. bootp - boot image via network using BootP/TFTP protocol
  2939. bootz - boot zImage from memory
  2940. tftpboot- boot image via network using TFTP protocol
  2941. and env variables "ipaddr" and "serverip"
  2942. (and eventually "gatewayip")
  2943. tftpput - upload a file via network using TFTP protocol
  2944. rarpboot- boot image via network using RARP/TFTP protocol
  2945. diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
  2946. loads - load S-Record file over serial line
  2947. loadb - load binary file over serial line (kermit mode)
  2948. md - memory display
  2949. mm - memory modify (auto-incrementing)
  2950. nm - memory modify (constant address)
  2951. mw - memory write (fill)
  2952. cp - memory copy
  2953. cmp - memory compare
  2954. crc32 - checksum calculation
  2955. i2c - I2C sub-system
  2956. sspi - SPI utility commands
  2957. base - print or set address offset
  2958. printenv- print environment variables
  2959. setenv - set environment variables
  2960. saveenv - save environment variables to persistent storage
  2961. protect - enable or disable FLASH write protection
  2962. erase - erase FLASH memory
  2963. flinfo - print FLASH memory information
  2964. nand - NAND memory operations (see doc/README.nand)
  2965. bdinfo - print Board Info structure
  2966. iminfo - print header information for application image
  2967. coninfo - print console devices and informations
  2968. ide - IDE sub-system
  2969. loop - infinite loop on address range
  2970. loopw - infinite write loop on address range
  2971. mtest - simple RAM test
  2972. icache - enable or disable instruction cache
  2973. dcache - enable or disable data cache
  2974. reset - Perform RESET of the CPU
  2975. echo - echo args to console
  2976. version - print monitor version
  2977. help - print online help
  2978. ? - alias for 'help'
  2979. Monitor Commands - Detailed Description:
  2980. ========================================
  2981. TODO.
  2982. For now: just type "help <command>".
  2983. Environment Variables:
  2984. ======================
  2985. U-Boot supports user configuration using Environment Variables which
  2986. can be made persistent by saving to Flash memory.
  2987. Environment Variables are set using "setenv", printed using
  2988. "printenv", and saved to Flash using "saveenv". Using "setenv"
  2989. without a value can be used to delete a variable from the
  2990. environment. As long as you don't save the environment you are
  2991. working with an in-memory copy. In case the Flash area containing the
  2992. environment is erased by accident, a default environment is provided.
  2993. Some configuration options can be set using Environment Variables.
  2994. List of environment variables (most likely not complete):
  2995. baudrate - see CONFIG_BAUDRATE
  2996. bootdelay - see CONFIG_BOOTDELAY
  2997. bootcmd - see CONFIG_BOOTCOMMAND
  2998. bootargs - Boot arguments when booting an RTOS image
  2999. bootfile - Name of the image to load with TFTP
  3000. bootm_low - Memory range available for image processing in the bootm
  3001. command can be restricted. This variable is given as
  3002. a hexadecimal number and defines lowest address allowed
  3003. for use by the bootm command. See also "bootm_size"
  3004. environment variable. Address defined by "bootm_low" is
  3005. also the base of the initial memory mapping for the Linux
  3006. kernel -- see the description of CONFIG_SYS_BOOTMAPSZ and
  3007. bootm_mapsize.
  3008. bootm_mapsize - Size of the initial memory mapping for the Linux kernel.
  3009. This variable is given as a hexadecimal number and it
  3010. defines the size of the memory region starting at base
  3011. address bootm_low that is accessible by the Linux kernel
  3012. during early boot. If unset, CONFIG_SYS_BOOTMAPSZ is used
  3013. as the default value if it is defined, and bootm_size is
  3014. used otherwise.
  3015. bootm_size - Memory range available for image processing in the bootm
  3016. command can be restricted. This variable is given as
  3017. a hexadecimal number and defines the size of the region
  3018. allowed for use by the bootm command. See also "bootm_low"
  3019. environment variable.
  3020. updatefile - Location of the software update file on a TFTP server, used
  3021. by the automatic software update feature. Please refer to
  3022. documentation in doc/README.update for more details.
  3023. autoload - if set to "no" (any string beginning with 'n'),
  3024. "bootp" will just load perform a lookup of the
  3025. configuration from the BOOTP server, but not try to
  3026. load any image using TFTP
  3027. autostart - if set to "yes", an image loaded using the "bootp",
  3028. "rarpboot", "tftpboot" or "diskboot" commands will
  3029. be automatically started (by internally calling
  3030. "bootm")
  3031. If set to "no", a standalone image passed to the
  3032. "bootm" command will be copied to the load address
  3033. (and eventually uncompressed), but NOT be started.
  3034. This can be used to load and uncompress arbitrary
  3035. data.
  3036. fdt_high - if set this restricts the maximum address that the
  3037. flattened device tree will be copied into upon boot.
  3038. For example, if you have a system with 1 GB memory
  3039. at physical address 0x10000000, while Linux kernel
  3040. only recognizes the first 704 MB as low memory, you
  3041. may need to set fdt_high as 0x3C000000 to have the
  3042. device tree blob be copied to the maximum address
  3043. of the 704 MB low memory, so that Linux kernel can
  3044. access it during the boot procedure.
  3045. If this is set to the special value 0xFFFFFFFF then
  3046. the fdt will not be copied at all on boot. For this
  3047. to work it must reside in writable memory, have
  3048. sufficient padding on the end of it for u-boot to
  3049. add the information it needs into it, and the memory
  3050. must be accessible by the kernel.
  3051. fdtcontroladdr- if set this is the address of the control flattened
  3052. device tree used by U-Boot when CONFIG_OF_CONTROL is
  3053. defined.
  3054. i2cfast - (PPC405GP|PPC405EP only)
  3055. if set to 'y' configures Linux I2C driver for fast
  3056. mode (400kHZ). This environment variable is used in
  3057. initialization code. So, for changes to be effective
  3058. it must be saved and board must be reset.
  3059. initrd_high - restrict positioning of initrd images:
  3060. If this variable is not set, initrd images will be
  3061. copied to the highest possible address in RAM; this
  3062. is usually what you want since it allows for
  3063. maximum initrd size. If for some reason you want to
  3064. make sure that the initrd image is loaded below the
  3065. CONFIG_SYS_BOOTMAPSZ limit, you can set this environment
  3066. variable to a value of "no" or "off" or "0".
  3067. Alternatively, you can set it to a maximum upper
  3068. address to use (U-Boot will still check that it
  3069. does not overwrite the U-Boot stack and data).
  3070. For instance, when you have a system with 16 MB
  3071. RAM, and want to reserve 4 MB from use by Linux,
  3072. you can do this by adding "mem=12M" to the value of
  3073. the "bootargs" variable. However, now you must make
  3074. sure that the initrd image is placed in the first
  3075. 12 MB as well - this can be done with
  3076. setenv initrd_high 00c00000
  3077. If you set initrd_high to 0xFFFFFFFF, this is an
  3078. indication to U-Boot that all addresses are legal
  3079. for the Linux kernel, including addresses in flash
  3080. memory. In this case U-Boot will NOT COPY the
  3081. ramdisk at all. This may be useful to reduce the
  3082. boot time on your system, but requires that this
  3083. feature is supported by your Linux kernel.
  3084. ipaddr - IP address; needed for tftpboot command
  3085. loadaddr - Default load address for commands like "bootp",
  3086. "rarpboot", "tftpboot", "loadb" or "diskboot"
  3087. loads_echo - see CONFIG_LOADS_ECHO
  3088. serverip - TFTP server IP address; needed for tftpboot command
  3089. bootretry - see CONFIG_BOOT_RETRY_TIME
  3090. bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
  3091. bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
  3092. ethprime - controls which interface is used first.
  3093. ethact - controls which interface is currently active.
  3094. For example you can do the following
  3095. => setenv ethact FEC
  3096. => ping 192.168.0.1 # traffic sent on FEC
  3097. => setenv ethact SCC
  3098. => ping 10.0.0.1 # traffic sent on SCC
  3099. ethrotate - When set to "no" U-Boot does not go through all
  3100. available network interfaces.
  3101. It just stays at the currently selected interface.
  3102. netretry - When set to "no" each network operation will
  3103. either succeed or fail without retrying.
  3104. When set to "once" the network operation will
  3105. fail when all the available network interfaces
  3106. are tried once without success.
  3107. Useful on scripts which control the retry operation
  3108. themselves.
  3109. npe_ucode - set load address for the NPE microcode
  3110. silent_linux - If set then Linux will be told to boot silently, by
  3111. changing the console to be empty. If "yes" it will be
  3112. made silent. If "no" it will not be made silent. If
  3113. unset, then it will be made silent if the U-Boot console
  3114. is silent.
  3115. tftpsrcp - If this is set, the value is used for TFTP's
  3116. UDP source port.
  3117. tftpdstp - If this is set, the value is used for TFTP's UDP
  3118. destination port instead of the Well Know Port 69.
  3119. tftpblocksize - Block size to use for TFTP transfers; if not set,
  3120. we use the TFTP server's default block size
  3121. tftptimeout - Retransmission timeout for TFTP packets (in milli-
  3122. seconds, minimum value is 1000 = 1 second). Defines
  3123. when a packet is considered to be lost so it has to
  3124. be retransmitted. The default is 5000 = 5 seconds.
  3125. Lowering this value may make downloads succeed
  3126. faster in networks with high packet loss rates or
  3127. with unreliable TFTP servers.
  3128. tftptimeoutcountmax - maximum count of TFTP timeouts (no
  3129. unit, minimum value = 0). Defines how many timeouts
  3130. can happen during a single file transfer before that
  3131. transfer is aborted. The default is 10, and 0 means
  3132. 'no timeouts allowed'. Increasing this value may help
  3133. downloads succeed with high packet loss rates, or with
  3134. unreliable TFTP servers or client hardware.
  3135. vlan - When set to a value < 4095 the traffic over
  3136. Ethernet is encapsulated/received over 802.1q
  3137. VLAN tagged frames.
  3138. bootpretryperiod - Period during which BOOTP/DHCP sends retries.
  3139. Unsigned value, in milliseconds. If not set, the period will
  3140. be either the default (28000), or a value based on
  3141. CONFIG_NET_RETRY_COUNT, if defined. This value has
  3142. precedence over the valu based on CONFIG_NET_RETRY_COUNT.
  3143. The following image location variables contain the location of images
  3144. used in booting. The "Image" column gives the role of the image and is
  3145. not an environment variable name. The other columns are environment
  3146. variable names. "File Name" gives the name of the file on a TFTP
  3147. server, "RAM Address" gives the location in RAM the image will be
  3148. loaded to, and "Flash Location" gives the image's address in NOR
  3149. flash or offset in NAND flash.
  3150. *Note* - these variables don't have to be defined for all boards, some
  3151. boards currently use other variables for these purposes, and some
  3152. boards use these variables for other purposes.
  3153. Image File Name RAM Address Flash Location
  3154. ----- --------- ----------- --------------
  3155. u-boot u-boot u-boot_addr_r u-boot_addr
  3156. Linux kernel bootfile kernel_addr_r kernel_addr
  3157. device tree blob fdtfile fdt_addr_r fdt_addr
  3158. ramdisk ramdiskfile ramdisk_addr_r ramdisk_addr
  3159. The following environment variables may be used and automatically
  3160. updated by the network boot commands ("bootp" and "rarpboot"),
  3161. depending the information provided by your boot server:
  3162. bootfile - see above
  3163. dnsip - IP address of your Domain Name Server
  3164. dnsip2 - IP address of your secondary Domain Name Server
  3165. gatewayip - IP address of the Gateway (Router) to use
  3166. hostname - Target hostname
  3167. ipaddr - see above
  3168. netmask - Subnet Mask
  3169. rootpath - Pathname of the root filesystem on the NFS server
  3170. serverip - see above
  3171. There are two special Environment Variables:
  3172. serial# - contains hardware identification information such
  3173. as type string and/or serial number
  3174. ethaddr - Ethernet address
  3175. These variables can be set only once (usually during manufacturing of
  3176. the board). U-Boot refuses to delete or overwrite these variables
  3177. once they have been set once.
  3178. Further special Environment Variables:
  3179. ver - Contains the U-Boot version string as printed
  3180. with the "version" command. This variable is
  3181. readonly (see CONFIG_VERSION_VARIABLE).
  3182. Please note that changes to some configuration parameters may take
  3183. only effect after the next boot (yes, that's just like Windoze :-).
  3184. Callback functions for environment variables:
  3185. ---------------------------------------------
  3186. For some environment variables, the behavior of u-boot needs to change
  3187. when their values are changed. This functionality allows functions to
  3188. be associated with arbitrary variables. On creation, overwrite, or
  3189. deletion, the callback will provide the opportunity for some side
  3190. effect to happen or for the change to be rejected.
  3191. The callbacks are named and associated with a function using the
  3192. U_BOOT_ENV_CALLBACK macro in your board or driver code.
  3193. These callbacks are associated with variables in one of two ways. The
  3194. static list can be added to by defining CONFIG_ENV_CALLBACK_LIST_STATIC
  3195. in the board configuration to a string that defines a list of
  3196. associations. The list must be in the following format:
  3197. entry = variable_name[:callback_name]
  3198. list = entry[,list]
  3199. If the callback name is not specified, then the callback is deleted.
  3200. Spaces are also allowed anywhere in the list.
  3201. Callbacks can also be associated by defining the ".callbacks" variable
  3202. with the same list format above. Any association in ".callbacks" will
  3203. override any association in the static list. You can define
  3204. CONFIG_ENV_CALLBACK_LIST_DEFAULT to a list (string) to define the
  3205. ".callbacks" environment variable in the default or embedded environment.
  3206. If CONFIG_REGEX is defined, the variable_name above is evaluated as a
  3207. regular expression. This allows multiple variables to be connected to
  3208. the same callback without explicitly listing them all out.
  3209. Command Line Parsing:
  3210. =====================
  3211. There are two different command line parsers available with U-Boot:
  3212. the old "simple" one, and the much more powerful "hush" shell:
  3213. Old, simple command line parser:
  3214. --------------------------------
  3215. - supports environment variables (through setenv / saveenv commands)
  3216. - several commands on one line, separated by ';'
  3217. - variable substitution using "... ${name} ..." syntax
  3218. - special characters ('$', ';') can be escaped by prefixing with '\',
  3219. for example:
  3220. setenv bootcmd bootm \${address}
  3221. - You can also escape text by enclosing in single apostrophes, for example:
  3222. setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
  3223. Hush shell:
  3224. -----------
  3225. - similar to Bourne shell, with control structures like
  3226. if...then...else...fi, for...do...done; while...do...done,
  3227. until...do...done, ...
  3228. - supports environment ("global") variables (through setenv / saveenv
  3229. commands) and local shell variables (through standard shell syntax
  3230. "name=value"); only environment variables can be used with "run"
  3231. command
  3232. General rules:
  3233. --------------
  3234. (1) If a command line (or an environment variable executed by a "run"
  3235. command) contains several commands separated by semicolon, and
  3236. one of these commands fails, then the remaining commands will be
  3237. executed anyway.
  3238. (2) If you execute several variables with one call to run (i. e.
  3239. calling run with a list of variables as arguments), any failing
  3240. command will cause "run" to terminate, i. e. the remaining
  3241. variables are not executed.
  3242. Note for Redundant Ethernet Interfaces:
  3243. =======================================
  3244. Some boards come with redundant Ethernet interfaces; U-Boot supports
  3245. such configurations and is capable of automatic selection of a
  3246. "working" interface when needed. MAC assignment works as follows:
  3247. Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
  3248. MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
  3249. "eth1addr" (=>eth1), "eth2addr", ...
  3250. If the network interface stores some valid MAC address (for instance
  3251. in SROM), this is used as default address if there is NO correspon-
  3252. ding setting in the environment; if the corresponding environment
  3253. variable is set, this overrides the settings in the card; that means:
  3254. o If the SROM has a valid MAC address, and there is no address in the
  3255. environment, the SROM's address is used.
  3256. o If there is no valid address in the SROM, and a definition in the
  3257. environment exists, then the value from the environment variable is
  3258. used.
  3259. o If both the SROM and the environment contain a MAC address, and
  3260. both addresses are the same, this MAC address is used.
  3261. o If both the SROM and the environment contain a MAC address, and the
  3262. addresses differ, the value from the environment is used and a
  3263. warning is printed.
  3264. o If neither SROM nor the environment contain a MAC address, an error
  3265. is raised. If CONFIG_NET_RANDOM_ETHADDR is defined, then in this case
  3266. a random, locally-assigned MAC is used.
  3267. If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses
  3268. will be programmed into hardware as part of the initialization process. This
  3269. may be skipped by setting the appropriate 'ethmacskip' environment variable.
  3270. The naming convention is as follows:
  3271. "ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc.
  3272. Image Formats:
  3273. ==============
  3274. U-Boot is capable of booting (and performing other auxiliary operations on)
  3275. images in two formats:
  3276. New uImage format (FIT)
  3277. -----------------------
  3278. Flexible and powerful format based on Flattened Image Tree -- FIT (similar
  3279. to Flattened Device Tree). It allows the use of images with multiple
  3280. components (several kernels, ramdisks, etc.), with contents protected by
  3281. SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory.
  3282. Old uImage format
  3283. -----------------
  3284. Old image format is based on binary files which can be basically anything,
  3285. preceded by a special header; see the definitions in include/image.h for
  3286. details; basically, the header defines the following image properties:
  3287. * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
  3288. 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
  3289. LynxOS, pSOS, QNX, RTEMS, INTEGRITY;
  3290. Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS,
  3291. INTEGRITY).
  3292. * Target CPU Architecture (Provisions for Alpha, ARM, Intel x86,
  3293. IA64, MIPS, NDS32, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
  3294. Currently supported: ARM, Intel x86, MIPS, NDS32, Nios II, PowerPC).
  3295. * Compression Type (uncompressed, gzip, bzip2)
  3296. * Load Address
  3297. * Entry Point
  3298. * Image Name
  3299. * Image Timestamp
  3300. The header is marked by a special Magic Number, and both the header
  3301. and the data portions of the image are secured against corruption by
  3302. CRC32 checksums.
  3303. Linux Support:
  3304. ==============
  3305. Although U-Boot should support any OS or standalone application
  3306. easily, the main focus has always been on Linux during the design of
  3307. U-Boot.
  3308. U-Boot includes many features that so far have been part of some
  3309. special "boot loader" code within the Linux kernel. Also, any
  3310. "initrd" images to be used are no longer part of one big Linux image;
  3311. instead, kernel and "initrd" are separate images. This implementation
  3312. serves several purposes:
  3313. - the same features can be used for other OS or standalone
  3314. applications (for instance: using compressed images to reduce the
  3315. Flash memory footprint)
  3316. - it becomes much easier to port new Linux kernel versions because
  3317. lots of low-level, hardware dependent stuff are done by U-Boot
  3318. - the same Linux kernel image can now be used with different "initrd"
  3319. images; of course this also means that different kernel images can
  3320. be run with the same "initrd". This makes testing easier (you don't
  3321. have to build a new "zImage.initrd" Linux image when you just
  3322. change a file in your "initrd"). Also, a field-upgrade of the
  3323. software is easier now.
  3324. Linux HOWTO:
  3325. ============
  3326. Porting Linux to U-Boot based systems:
  3327. ---------------------------------------
  3328. U-Boot cannot save you from doing all the necessary modifications to
  3329. configure the Linux device drivers for use with your target hardware
  3330. (no, we don't intend to provide a full virtual machine interface to
  3331. Linux :-).
  3332. But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot).
  3333. Just make sure your machine specific header file (for instance
  3334. include/asm-ppc/tqm8xx.h) includes the same definition of the Board
  3335. Information structure as we define in include/asm-<arch>/u-boot.h,
  3336. and make sure that your definition of IMAP_ADDR uses the same value
  3337. as your U-Boot configuration in CONFIG_SYS_IMMR.
  3338. Note that U-Boot now has a driver model, a unified model for drivers.
  3339. If you are adding a new driver, plumb it into driver model. If there
  3340. is no uclass available, you are encouraged to create one. See
  3341. doc/driver-model.
  3342. Configuring the Linux kernel:
  3343. -----------------------------
  3344. No specific requirements for U-Boot. Make sure you have some root
  3345. device (initial ramdisk, NFS) for your target system.
  3346. Building a Linux Image:
  3347. -----------------------
  3348. With U-Boot, "normal" build targets like "zImage" or "bzImage" are
  3349. not used. If you use recent kernel source, a new build target
  3350. "uImage" will exist which automatically builds an image usable by
  3351. U-Boot. Most older kernels also have support for a "pImage" target,
  3352. which was introduced for our predecessor project PPCBoot and uses a
  3353. 100% compatible format.
  3354. Example:
  3355. make TQM850L_defconfig
  3356. make oldconfig
  3357. make dep
  3358. make uImage
  3359. The "uImage" build target uses a special tool (in 'tools/mkimage') to
  3360. encapsulate a compressed Linux kernel image with header information,
  3361. CRC32 checksum etc. for use with U-Boot. This is what we are doing:
  3362. * build a standard "vmlinux" kernel image (in ELF binary format):
  3363. * convert the kernel into a raw binary image:
  3364. ${CROSS_COMPILE}-objcopy -O binary \
  3365. -R .note -R .comment \
  3366. -S vmlinux linux.bin
  3367. * compress the binary image:
  3368. gzip -9 linux.bin
  3369. * package compressed binary image for U-Boot:
  3370. mkimage -A ppc -O linux -T kernel -C gzip \
  3371. -a 0 -e 0 -n "Linux Kernel Image" \
  3372. -d linux.bin.gz uImage
  3373. The "mkimage" tool can also be used to create ramdisk images for use
  3374. with U-Boot, either separated from the Linux kernel image, or
  3375. combined into one file. "mkimage" encapsulates the images with a 64
  3376. byte header containing information about target architecture,
  3377. operating system, image type, compression method, entry points, time
  3378. stamp, CRC32 checksums, etc.
  3379. "mkimage" can be called in two ways: to verify existing images and
  3380. print the header information, or to build new images.
  3381. In the first form (with "-l" option) mkimage lists the information
  3382. contained in the header of an existing U-Boot image; this includes
  3383. checksum verification:
  3384. tools/mkimage -l image
  3385. -l ==> list image header information
  3386. The second form (with "-d" option) is used to build a U-Boot image
  3387. from a "data file" which is used as image payload:
  3388. tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
  3389. -n name -d data_file image
  3390. -A ==> set architecture to 'arch'
  3391. -O ==> set operating system to 'os'
  3392. -T ==> set image type to 'type'
  3393. -C ==> set compression type 'comp'
  3394. -a ==> set load address to 'addr' (hex)
  3395. -e ==> set entry point to 'ep' (hex)
  3396. -n ==> set image name to 'name'
  3397. -d ==> use image data from 'datafile'
  3398. Right now, all Linux kernels for PowerPC systems use the same load
  3399. address (0x00000000), but the entry point address depends on the
  3400. kernel version:
  3401. - 2.2.x kernels have the entry point at 0x0000000C,
  3402. - 2.3.x and later kernels have the entry point at 0x00000000.
  3403. So a typical call to build a U-Boot image would read:
  3404. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  3405. > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
  3406. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \
  3407. > examples/uImage.TQM850L
  3408. Image Name: 2.4.4 kernel for TQM850L
  3409. Created: Wed Jul 19 02:34:59 2000
  3410. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3411. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  3412. Load Address: 0x00000000
  3413. Entry Point: 0x00000000
  3414. To verify the contents of the image (or check for corruption):
  3415. -> tools/mkimage -l examples/uImage.TQM850L
  3416. Image Name: 2.4.4 kernel for TQM850L
  3417. Created: Wed Jul 19 02:34:59 2000
  3418. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3419. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  3420. Load Address: 0x00000000
  3421. Entry Point: 0x00000000
  3422. NOTE: for embedded systems where boot time is critical you can trade
  3423. speed for memory and install an UNCOMPRESSED image instead: this
  3424. needs more space in Flash, but boots much faster since it does not
  3425. need to be uncompressed:
  3426. -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz
  3427. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  3428. > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
  3429. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \
  3430. > examples/uImage.TQM850L-uncompressed
  3431. Image Name: 2.4.4 kernel for TQM850L
  3432. Created: Wed Jul 19 02:34:59 2000
  3433. Image Type: PowerPC Linux Kernel Image (uncompressed)
  3434. Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
  3435. Load Address: 0x00000000
  3436. Entry Point: 0x00000000
  3437. Similar you can build U-Boot images from a 'ramdisk.image.gz' file
  3438. when your kernel is intended to use an initial ramdisk:
  3439. -> tools/mkimage -n 'Simple Ramdisk Image' \
  3440. > -A ppc -O linux -T ramdisk -C gzip \
  3441. > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
  3442. Image Name: Simple Ramdisk Image
  3443. Created: Wed Jan 12 14:01:50 2000
  3444. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  3445. Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
  3446. Load Address: 0x00000000
  3447. Entry Point: 0x00000000
  3448. The "dumpimage" is a tool to disassemble images built by mkimage. Its "-i"
  3449. option performs the converse operation of the mkimage's second form (the "-d"
  3450. option). Given an image built by mkimage, the dumpimage extracts a "data file"
  3451. from the image:
  3452. tools/dumpimage -i image -T type -p position data_file
  3453. -i ==> extract from the 'image' a specific 'data_file'
  3454. -T ==> set image type to 'type'
  3455. -p ==> 'position' (starting at 0) of the 'data_file' inside the 'image'
  3456. Installing a Linux Image:
  3457. -------------------------
  3458. To downloading a U-Boot image over the serial (console) interface,
  3459. you must convert the image to S-Record format:
  3460. objcopy -I binary -O srec examples/image examples/image.srec
  3461. The 'objcopy' does not understand the information in the U-Boot
  3462. image header, so the resulting S-Record file will be relative to
  3463. address 0x00000000. To load it to a given address, you need to
  3464. specify the target address as 'offset' parameter with the 'loads'
  3465. command.
  3466. Example: install the image to address 0x40100000 (which on the
  3467. TQM8xxL is in the first Flash bank):
  3468. => erase 40100000 401FFFFF
  3469. .......... done
  3470. Erased 8 sectors
  3471. => loads 40100000
  3472. ## Ready for S-Record download ...
  3473. ~>examples/image.srec
  3474. 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
  3475. ...
  3476. 15989 15990 15991 15992
  3477. [file transfer complete]
  3478. [connected]
  3479. ## Start Addr = 0x00000000
  3480. You can check the success of the download using the 'iminfo' command;
  3481. this includes a checksum verification so you can be sure no data
  3482. corruption happened:
  3483. => imi 40100000
  3484. ## Checking Image at 40100000 ...
  3485. Image Name: 2.2.13 for initrd on TQM850L
  3486. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3487. Data Size: 335725 Bytes = 327 kB = 0 MB
  3488. Load Address: 00000000
  3489. Entry Point: 0000000c
  3490. Verifying Checksum ... OK
  3491. Boot Linux:
  3492. -----------
  3493. The "bootm" command is used to boot an application that is stored in
  3494. memory (RAM or Flash). In case of a Linux kernel image, the contents
  3495. of the "bootargs" environment variable is passed to the kernel as
  3496. parameters. You can check and modify this variable using the
  3497. "printenv" and "setenv" commands:
  3498. => printenv bootargs
  3499. bootargs=root=/dev/ram
  3500. => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  3501. => printenv bootargs
  3502. bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  3503. => bootm 40020000
  3504. ## Booting Linux kernel at 40020000 ...
  3505. Image Name: 2.2.13 for NFS on TQM850L
  3506. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3507. Data Size: 381681 Bytes = 372 kB = 0 MB
  3508. Load Address: 00000000
  3509. Entry Point: 0000000c
  3510. Verifying Checksum ... OK
  3511. Uncompressing Kernel Image ... OK
  3512. 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
  3513. Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  3514. time_init: decrementer frequency = 187500000/60
  3515. Calibrating delay loop... 49.77 BogoMIPS
  3516. Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
  3517. ...
  3518. If you want to boot a Linux kernel with initial RAM disk, you pass
  3519. the memory addresses of both the kernel and the initrd image (PPBCOOT
  3520. format!) to the "bootm" command:
  3521. => imi 40100000 40200000
  3522. ## Checking Image at 40100000 ...
  3523. Image Name: 2.2.13 for initrd on TQM850L
  3524. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3525. Data Size: 335725 Bytes = 327 kB = 0 MB
  3526. Load Address: 00000000
  3527. Entry Point: 0000000c
  3528. Verifying Checksum ... OK
  3529. ## Checking Image at 40200000 ...
  3530. Image Name: Simple Ramdisk Image
  3531. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  3532. Data Size: 566530 Bytes = 553 kB = 0 MB
  3533. Load Address: 00000000
  3534. Entry Point: 00000000
  3535. Verifying Checksum ... OK
  3536. => bootm 40100000 40200000
  3537. ## Booting Linux kernel at 40100000 ...
  3538. Image Name: 2.2.13 for initrd on TQM850L
  3539. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3540. Data Size: 335725 Bytes = 327 kB = 0 MB
  3541. Load Address: 00000000
  3542. Entry Point: 0000000c
  3543. Verifying Checksum ... OK
  3544. Uncompressing Kernel Image ... OK
  3545. ## Loading RAMDisk Image at 40200000 ...
  3546. Image Name: Simple Ramdisk Image
  3547. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  3548. Data Size: 566530 Bytes = 553 kB = 0 MB
  3549. Load Address: 00000000
  3550. Entry Point: 00000000
  3551. Verifying Checksum ... OK
  3552. Loading Ramdisk ... OK
  3553. 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
  3554. Boot arguments: root=/dev/ram
  3555. time_init: decrementer frequency = 187500000/60
  3556. Calibrating delay loop... 49.77 BogoMIPS
  3557. ...
  3558. RAMDISK: Compressed image found at block 0
  3559. VFS: Mounted root (ext2 filesystem).
  3560. bash#
  3561. Boot Linux and pass a flat device tree:
  3562. -----------
  3563. First, U-Boot must be compiled with the appropriate defines. See the section
  3564. titled "Linux Kernel Interface" above for a more in depth explanation. The
  3565. following is an example of how to start a kernel and pass an updated
  3566. flat device tree:
  3567. => print oftaddr
  3568. oftaddr=0x300000
  3569. => print oft
  3570. oft=oftrees/mpc8540ads.dtb
  3571. => tftp $oftaddr $oft
  3572. Speed: 1000, full duplex
  3573. Using TSEC0 device
  3574. TFTP from server 192.168.1.1; our IP address is 192.168.1.101
  3575. Filename 'oftrees/mpc8540ads.dtb'.
  3576. Load address: 0x300000
  3577. Loading: #
  3578. done
  3579. Bytes transferred = 4106 (100a hex)
  3580. => tftp $loadaddr $bootfile
  3581. Speed: 1000, full duplex
  3582. Using TSEC0 device
  3583. TFTP from server 192.168.1.1; our IP address is 192.168.1.2
  3584. Filename 'uImage'.
  3585. Load address: 0x200000
  3586. Loading:############
  3587. done
  3588. Bytes transferred = 1029407 (fb51f hex)
  3589. => print loadaddr
  3590. loadaddr=200000
  3591. => print oftaddr
  3592. oftaddr=0x300000
  3593. => bootm $loadaddr - $oftaddr
  3594. ## Booting image at 00200000 ...
  3595. Image Name: Linux-2.6.17-dirty
  3596. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  3597. Data Size: 1029343 Bytes = 1005.2 kB
  3598. Load Address: 00000000
  3599. Entry Point: 00000000
  3600. Verifying Checksum ... OK
  3601. Uncompressing Kernel Image ... OK
  3602. Booting using flat device tree at 0x300000
  3603. Using MPC85xx ADS machine description
  3604. Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
  3605. [snip]
  3606. More About U-Boot Image Types:
  3607. ------------------------------
  3608. U-Boot supports the following image types:
  3609. "Standalone Programs" are directly runnable in the environment
  3610. provided by U-Boot; it is expected that (if they behave
  3611. well) you can continue to work in U-Boot after return from
  3612. the Standalone Program.
  3613. "OS Kernel Images" are usually images of some Embedded OS which
  3614. will take over control completely. Usually these programs
  3615. will install their own set of exception handlers, device
  3616. drivers, set up the MMU, etc. - this means, that you cannot
  3617. expect to re-enter U-Boot except by resetting the CPU.
  3618. "RAMDisk Images" are more or less just data blocks, and their
  3619. parameters (address, size) are passed to an OS kernel that is
  3620. being started.
  3621. "Multi-File Images" contain several images, typically an OS
  3622. (Linux) kernel image and one or more data images like
  3623. RAMDisks. This construct is useful for instance when you want
  3624. to boot over the network using BOOTP etc., where the boot
  3625. server provides just a single image file, but you want to get
  3626. for instance an OS kernel and a RAMDisk image.
  3627. "Multi-File Images" start with a list of image sizes, each
  3628. image size (in bytes) specified by an "uint32_t" in network
  3629. byte order. This list is terminated by an "(uint32_t)0".
  3630. Immediately after the terminating 0 follow the images, one by
  3631. one, all aligned on "uint32_t" boundaries (size rounded up to
  3632. a multiple of 4 bytes).
  3633. "Firmware Images" are binary images containing firmware (like
  3634. U-Boot or FPGA images) which usually will be programmed to
  3635. flash memory.
  3636. "Script files" are command sequences that will be executed by
  3637. U-Boot's command interpreter; this feature is especially
  3638. useful when you configure U-Boot to use a real shell (hush)
  3639. as command interpreter.
  3640. Booting the Linux zImage:
  3641. -------------------------
  3642. On some platforms, it's possible to boot Linux zImage. This is done
  3643. using the "bootz" command. The syntax of "bootz" command is the same
  3644. as the syntax of "bootm" command.
  3645. Note, defining the CONFIG_SUPPORT_RAW_INITRD allows user to supply
  3646. kernel with raw initrd images. The syntax is slightly different, the
  3647. address of the initrd must be augmented by it's size, in the following
  3648. format: "<initrd addres>:<initrd size>".
  3649. Standalone HOWTO:
  3650. =================
  3651. One of the features of U-Boot is that you can dynamically load and
  3652. run "standalone" applications, which can use some resources of
  3653. U-Boot like console I/O functions or interrupt services.
  3654. Two simple examples are included with the sources:
  3655. "Hello World" Demo:
  3656. -------------------
  3657. 'examples/hello_world.c' contains a small "Hello World" Demo
  3658. application; it is automatically compiled when you build U-Boot.
  3659. It's configured to run at address 0x00040004, so you can play with it
  3660. like that:
  3661. => loads
  3662. ## Ready for S-Record download ...
  3663. ~>examples/hello_world.srec
  3664. 1 2 3 4 5 6 7 8 9 10 11 ...
  3665. [file transfer complete]
  3666. [connected]
  3667. ## Start Addr = 0x00040004
  3668. => go 40004 Hello World! This is a test.
  3669. ## Starting application at 0x00040004 ...
  3670. Hello World
  3671. argc = 7
  3672. argv[0] = "40004"
  3673. argv[1] = "Hello"
  3674. argv[2] = "World!"
  3675. argv[3] = "This"
  3676. argv[4] = "is"
  3677. argv[5] = "a"
  3678. argv[6] = "test."
  3679. argv[7] = "<NULL>"
  3680. Hit any key to exit ...
  3681. ## Application terminated, rc = 0x0
  3682. Another example, which demonstrates how to register a CPM interrupt
  3683. handler with the U-Boot code, can be found in 'examples/timer.c'.
  3684. Here, a CPM timer is set up to generate an interrupt every second.
  3685. The interrupt service routine is trivial, just printing a '.'
  3686. character, but this is just a demo program. The application can be
  3687. controlled by the following keys:
  3688. ? - print current values og the CPM Timer registers
  3689. b - enable interrupts and start timer
  3690. e - stop timer and disable interrupts
  3691. q - quit application
  3692. => loads
  3693. ## Ready for S-Record download ...
  3694. ~>examples/timer.srec
  3695. 1 2 3 4 5 6 7 8 9 10 11 ...
  3696. [file transfer complete]
  3697. [connected]
  3698. ## Start Addr = 0x00040004
  3699. => go 40004
  3700. ## Starting application at 0x00040004 ...
  3701. TIMERS=0xfff00980
  3702. Using timer 1
  3703. tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
  3704. Hit 'b':
  3705. [q, b, e, ?] Set interval 1000000 us
  3706. Enabling timer
  3707. Hit '?':
  3708. [q, b, e, ?] ........
  3709. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
  3710. Hit '?':
  3711. [q, b, e, ?] .
  3712. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
  3713. Hit '?':
  3714. [q, b, e, ?] .
  3715. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
  3716. Hit '?':
  3717. [q, b, e, ?] .
  3718. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
  3719. Hit 'e':
  3720. [q, b, e, ?] ...Stopping timer
  3721. Hit 'q':
  3722. [q, b, e, ?] ## Application terminated, rc = 0x0
  3723. Minicom warning:
  3724. ================
  3725. Over time, many people have reported problems when trying to use the
  3726. "minicom" terminal emulation program for serial download. I (wd)
  3727. consider minicom to be broken, and recommend not to use it. Under
  3728. Unix, I recommend to use C-Kermit for general purpose use (and
  3729. especially for kermit binary protocol download ("loadb" command), and
  3730. use "cu" for S-Record download ("loads" command). See
  3731. http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3.
  3732. for help with kermit.
  3733. Nevertheless, if you absolutely want to use it try adding this
  3734. configuration to your "File transfer protocols" section:
  3735. Name Program Name U/D FullScr IO-Red. Multi
  3736. X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
  3737. Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
  3738. NetBSD Notes:
  3739. =============
  3740. Starting at version 0.9.2, U-Boot supports NetBSD both as host
  3741. (build U-Boot) and target system (boots NetBSD/mpc8xx).
  3742. Building requires a cross environment; it is known to work on
  3743. NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
  3744. need gmake since the Makefiles are not compatible with BSD make).
  3745. Note that the cross-powerpc package does not install include files;
  3746. attempting to build U-Boot will fail because <machine/ansi.h> is
  3747. missing. This file has to be installed and patched manually:
  3748. # cd /usr/pkg/cross/powerpc-netbsd/include
  3749. # mkdir powerpc
  3750. # ln -s powerpc machine
  3751. # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
  3752. # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
  3753. Native builds *don't* work due to incompatibilities between native
  3754. and U-Boot include files.
  3755. Booting assumes that (the first part of) the image booted is a
  3756. stage-2 loader which in turn loads and then invokes the kernel
  3757. proper. Loader sources will eventually appear in the NetBSD source
  3758. tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
  3759. meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
  3760. Implementation Internals:
  3761. =========================
  3762. The following is not intended to be a complete description of every
  3763. implementation detail. However, it should help to understand the
  3764. inner workings of U-Boot and make it easier to port it to custom
  3765. hardware.
  3766. Initial Stack, Global Data:
  3767. ---------------------------
  3768. The implementation of U-Boot is complicated by the fact that U-Boot
  3769. starts running out of ROM (flash memory), usually without access to
  3770. system RAM (because the memory controller is not initialized yet).
  3771. This means that we don't have writable Data or BSS segments, and BSS
  3772. is not initialized as zero. To be able to get a C environment working
  3773. at all, we have to allocate at least a minimal stack. Implementation
  3774. options for this are defined and restricted by the CPU used: Some CPU
  3775. models provide on-chip memory (like the IMMR area on MPC8xx and
  3776. MPC826x processors), on others (parts of) the data cache can be
  3777. locked as (mis-) used as memory, etc.
  3778. Chris Hallinan posted a good summary of these issues to the
  3779. U-Boot mailing list:
  3780. Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
  3781. From: "Chris Hallinan" <clh@net1plus.com>
  3782. Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
  3783. ...
  3784. Correct me if I'm wrong, folks, but the way I understand it
  3785. is this: Using DCACHE as initial RAM for Stack, etc, does not
  3786. require any physical RAM backing up the cache. The cleverness
  3787. is that the cache is being used as a temporary supply of
  3788. necessary storage before the SDRAM controller is setup. It's
  3789. beyond the scope of this list to explain the details, but you
  3790. can see how this works by studying the cache architecture and
  3791. operation in the architecture and processor-specific manuals.
  3792. OCM is On Chip Memory, which I believe the 405GP has 4K. It
  3793. is another option for the system designer to use as an
  3794. initial stack/RAM area prior to SDRAM being available. Either
  3795. option should work for you. Using CS 4 should be fine if your
  3796. board designers haven't used it for something that would
  3797. cause you grief during the initial boot! It is frequently not
  3798. used.
  3799. CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere
  3800. with your processor/board/system design. The default value
  3801. you will find in any recent u-boot distribution in
  3802. walnut.h should work for you. I'd set it to a value larger
  3803. than your SDRAM module. If you have a 64MB SDRAM module, set
  3804. it above 400_0000. Just make sure your board has no resources
  3805. that are supposed to respond to that address! That code in
  3806. start.S has been around a while and should work as is when
  3807. you get the config right.
  3808. -Chris Hallinan
  3809. DS4.COM, Inc.
  3810. It is essential to remember this, since it has some impact on the C
  3811. code for the initialization procedures:
  3812. * Initialized global data (data segment) is read-only. Do not attempt
  3813. to write it.
  3814. * Do not use any uninitialized global data (or implicitly initialized
  3815. as zero data - BSS segment) at all - this is undefined, initiali-
  3816. zation is performed later (when relocating to RAM).
  3817. * Stack space is very limited. Avoid big data buffers or things like
  3818. that.
  3819. Having only the stack as writable memory limits means we cannot use
  3820. normal global data to share information between the code. But it
  3821. turned out that the implementation of U-Boot can be greatly
  3822. simplified by making a global data structure (gd_t) available to all
  3823. functions. We could pass a pointer to this data as argument to _all_
  3824. functions, but this would bloat the code. Instead we use a feature of
  3825. the GCC compiler (Global Register Variables) to share the data: we
  3826. place a pointer (gd) to the global data into a register which we
  3827. reserve for this purpose.
  3828. When choosing a register for such a purpose we are restricted by the
  3829. relevant (E)ABI specifications for the current architecture, and by
  3830. GCC's implementation.
  3831. For PowerPC, the following registers have specific use:
  3832. R1: stack pointer
  3833. R2: reserved for system use
  3834. R3-R4: parameter passing and return values
  3835. R5-R10: parameter passing
  3836. R13: small data area pointer
  3837. R30: GOT pointer
  3838. R31: frame pointer
  3839. (U-Boot also uses R12 as internal GOT pointer. r12
  3840. is a volatile register so r12 needs to be reset when
  3841. going back and forth between asm and C)
  3842. ==> U-Boot will use R2 to hold a pointer to the global data
  3843. Note: on PPC, we could use a static initializer (since the
  3844. address of the global data structure is known at compile time),
  3845. but it turned out that reserving a register results in somewhat
  3846. smaller code - although the code savings are not that big (on
  3847. average for all boards 752 bytes for the whole U-Boot image,
  3848. 624 text + 127 data).
  3849. On ARM, the following registers are used:
  3850. R0: function argument word/integer result
  3851. R1-R3: function argument word
  3852. R9: platform specific
  3853. R10: stack limit (used only if stack checking is enabled)
  3854. R11: argument (frame) pointer
  3855. R12: temporary workspace
  3856. R13: stack pointer
  3857. R14: link register
  3858. R15: program counter
  3859. ==> U-Boot will use R9 to hold a pointer to the global data
  3860. Note: on ARM, only R_ARM_RELATIVE relocations are supported.
  3861. On Nios II, the ABI is documented here:
  3862. http://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf
  3863. ==> U-Boot will use gp to hold a pointer to the global data
  3864. Note: on Nios II, we give "-G0" option to gcc and don't use gp
  3865. to access small data sections, so gp is free.
  3866. On NDS32, the following registers are used:
  3867. R0-R1: argument/return
  3868. R2-R5: argument
  3869. R15: temporary register for assembler
  3870. R16: trampoline register
  3871. R28: frame pointer (FP)
  3872. R29: global pointer (GP)
  3873. R30: link register (LP)
  3874. R31: stack pointer (SP)
  3875. PC: program counter (PC)
  3876. ==> U-Boot will use R10 to hold a pointer to the global data
  3877. NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
  3878. or current versions of GCC may "optimize" the code too much.
  3879. Memory Management:
  3880. ------------------
  3881. U-Boot runs in system state and uses physical addresses, i.e. the
  3882. MMU is not used either for address mapping nor for memory protection.
  3883. The available memory is mapped to fixed addresses using the memory
  3884. controller. In this process, a contiguous block is formed for each
  3885. memory type (Flash, SDRAM, SRAM), even when it consists of several
  3886. physical memory banks.
  3887. U-Boot is installed in the first 128 kB of the first Flash bank (on
  3888. TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
  3889. booting and sizing and initializing DRAM, the code relocates itself
  3890. to the upper end of DRAM. Immediately below the U-Boot code some
  3891. memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN
  3892. configuration setting]. Below that, a structure with global Board
  3893. Info data is placed, followed by the stack (growing downward).
  3894. Additionally, some exception handler code is copied to the low 8 kB
  3895. of DRAM (0x00000000 ... 0x00001FFF).
  3896. So a typical memory configuration with 16 MB of DRAM could look like
  3897. this:
  3898. 0x0000 0000 Exception Vector code
  3899. :
  3900. 0x0000 1FFF
  3901. 0x0000 2000 Free for Application Use
  3902. :
  3903. :
  3904. :
  3905. :
  3906. 0x00FB FF20 Monitor Stack (Growing downward)
  3907. 0x00FB FFAC Board Info Data and permanent copy of global data
  3908. 0x00FC 0000 Malloc Arena
  3909. :
  3910. 0x00FD FFFF
  3911. 0x00FE 0000 RAM Copy of Monitor Code
  3912. ... eventually: LCD or video framebuffer
  3913. ... eventually: pRAM (Protected RAM - unchanged by reset)
  3914. 0x00FF FFFF [End of RAM]
  3915. System Initialization:
  3916. ----------------------
  3917. In the reset configuration, U-Boot starts at the reset entry point
  3918. (on most PowerPC systems at address 0x00000100). Because of the reset
  3919. configuration for CS0# this is a mirror of the on board Flash memory.
  3920. To be able to re-map memory U-Boot then jumps to its link address.
  3921. To be able to implement the initialization code in C, a (small!)
  3922. initial stack is set up in the internal Dual Ported RAM (in case CPUs
  3923. which provide such a feature like), or in a locked part of the data
  3924. cache. After that, U-Boot initializes the CPU core, the caches and
  3925. the SIU.
  3926. Next, all (potentially) available memory banks are mapped using a
  3927. preliminary mapping. For example, we put them on 512 MB boundaries
  3928. (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
  3929. on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
  3930. programmed for SDRAM access. Using the temporary configuration, a
  3931. simple memory test is run that determines the size of the SDRAM
  3932. banks.
  3933. When there is more than one SDRAM bank, and the banks are of
  3934. different size, the largest is mapped first. For equal size, the first
  3935. bank (CS2#) is mapped first. The first mapping is always for address
  3936. 0x00000000, with any additional banks following immediately to create
  3937. contiguous memory starting from 0.
  3938. Then, the monitor installs itself at the upper end of the SDRAM area
  3939. and allocates memory for use by malloc() and for the global Board
  3940. Info data; also, the exception vector code is copied to the low RAM
  3941. pages, and the final stack is set up.
  3942. Only after this relocation will you have a "normal" C environment;
  3943. until that you are restricted in several ways, mostly because you are
  3944. running from ROM, and because the code will have to be relocated to a
  3945. new address in RAM.
  3946. U-Boot Porting Guide:
  3947. ----------------------
  3948. [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
  3949. list, October 2002]
  3950. int main(int argc, char *argv[])
  3951. {
  3952. sighandler_t no_more_time;
  3953. signal(SIGALRM, no_more_time);
  3954. alarm(PROJECT_DEADLINE - toSec (3 * WEEK));
  3955. if (available_money > available_manpower) {
  3956. Pay consultant to port U-Boot;
  3957. return 0;
  3958. }
  3959. Download latest U-Boot source;
  3960. Subscribe to u-boot mailing list;
  3961. if (clueless)
  3962. email("Hi, I am new to U-Boot, how do I get started?");
  3963. while (learning) {
  3964. Read the README file in the top level directory;
  3965. Read http://www.denx.de/twiki/bin/view/DULG/Manual;
  3966. Read applicable doc/*.README;
  3967. Read the source, Luke;
  3968. /* find . -name "*.[chS]" | xargs grep -i <keyword> */
  3969. }
  3970. if (available_money > toLocalCurrency ($2500))
  3971. Buy a BDI3000;
  3972. else
  3973. Add a lot of aggravation and time;
  3974. if (a similar board exists) { /* hopefully... */
  3975. cp -a board/<similar> board/<myboard>
  3976. cp include/configs/<similar>.h include/configs/<myboard>.h
  3977. } else {
  3978. Create your own board support subdirectory;
  3979. Create your own board include/configs/<myboard>.h file;
  3980. }
  3981. Edit new board/<myboard> files
  3982. Edit new include/configs/<myboard>.h
  3983. while (!accepted) {
  3984. while (!running) {
  3985. do {
  3986. Add / modify source code;
  3987. } until (compiles);
  3988. Debug;
  3989. if (clueless)
  3990. email("Hi, I am having problems...");
  3991. }
  3992. Send patch file to the U-Boot email list;
  3993. if (reasonable critiques)
  3994. Incorporate improvements from email list code review;
  3995. else
  3996. Defend code as written;
  3997. }
  3998. return 0;
  3999. }
  4000. void no_more_time (int sig)
  4001. {
  4002. hire_a_guru();
  4003. }
  4004. Coding Standards:
  4005. -----------------
  4006. All contributions to U-Boot should conform to the Linux kernel
  4007. coding style; see the file "Documentation/CodingStyle" and the script
  4008. "scripts/Lindent" in your Linux kernel source directory.
  4009. Source files originating from a different project (for example the
  4010. MTD subsystem) are generally exempt from these guidelines and are not
  4011. reformatted to ease subsequent migration to newer versions of those
  4012. sources.
  4013. Please note that U-Boot is implemented in C (and to some small parts in
  4014. Assembler); no C++ is used, so please do not use C++ style comments (//)
  4015. in your code.
  4016. Please also stick to the following formatting rules:
  4017. - remove any trailing white space
  4018. - use TAB characters for indentation and vertical alignment, not spaces
  4019. - make sure NOT to use DOS '\r\n' line feeds
  4020. - do not add more than 2 consecutive empty lines to source files
  4021. - do not add trailing empty lines to source files
  4022. Submissions which do not conform to the standards may be returned
  4023. with a request to reformat the changes.
  4024. Submitting Patches:
  4025. -------------------
  4026. Since the number of patches for U-Boot is growing, we need to
  4027. establish some rules. Submissions which do not conform to these rules
  4028. may be rejected, even when they contain important and valuable stuff.
  4029. Please see http://www.denx.de/wiki/U-Boot/Patches for details.
  4030. Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>;
  4031. see http://lists.denx.de/mailman/listinfo/u-boot
  4032. When you send a patch, please include the following information with
  4033. it:
  4034. * For bug fixes: a description of the bug and how your patch fixes
  4035. this bug. Please try to include a way of demonstrating that the
  4036. patch actually fixes something.
  4037. * For new features: a description of the feature and your
  4038. implementation.
  4039. * A CHANGELOG entry as plaintext (separate from the patch)
  4040. * For major contributions, add a MAINTAINERS file with your
  4041. information and associated file and directory references.
  4042. * When you add support for a new board, don't forget to add a
  4043. maintainer e-mail address to the boards.cfg file, too.
  4044. * If your patch adds new configuration options, don't forget to
  4045. document these in the README file.
  4046. * The patch itself. If you are using git (which is *strongly*
  4047. recommended) you can easily generate the patch using the
  4048. "git format-patch". If you then use "git send-email" to send it to
  4049. the U-Boot mailing list, you will avoid most of the common problems
  4050. with some other mail clients.
  4051. If you cannot use git, use "diff -purN OLD NEW". If your version of
  4052. diff does not support these options, then get the latest version of
  4053. GNU diff.
  4054. The current directory when running this command shall be the parent
  4055. directory of the U-Boot source tree (i. e. please make sure that
  4056. your patch includes sufficient directory information for the
  4057. affected files).
  4058. We prefer patches as plain text. MIME attachments are discouraged,
  4059. and compressed attachments must not be used.
  4060. * If one logical set of modifications affects or creates several
  4061. files, all these changes shall be submitted in a SINGLE patch file.
  4062. * Changesets that contain different, unrelated modifications shall be
  4063. submitted as SEPARATE patches, one patch per changeset.
  4064. Notes:
  4065. * Before sending the patch, run the buildman script on your patched
  4066. source tree and make sure that no errors or warnings are reported
  4067. for any of the boards.
  4068. * Keep your modifications to the necessary minimum: A patch
  4069. containing several unrelated changes or arbitrary reformats will be
  4070. returned with a request to re-formatting / split it.
  4071. * If you modify existing code, make sure that your new code does not
  4072. add to the memory footprint of the code ;-) Small is beautiful!
  4073. When adding new features, these should compile conditionally only
  4074. (using #ifdef), and the resulting code with the new feature
  4075. disabled must not need more memory than the old code without your
  4076. modification.
  4077. * Remember that there is a size limit of 100 kB per message on the
  4078. u-boot mailing list. Bigger patches will be moderated. If they are
  4079. reasonable and not too big, they will be acknowledged. But patches
  4080. bigger than the size limit should be avoided.