README 209 KB

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