README 192 KB

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