README 191 KB

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