README 226 KB

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