README 232 KB

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