README 192 KB

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