README 226 KB

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