README 174 KB

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