README 231 KB

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