README 168 KB

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