README 206 KB

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