README 150 KB

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