README 147 KB

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