README 230 KB

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