README 232 KB

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