README 116 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601160216031604160516061607160816091610161116121613161416151616161716181619162016211622162316241625162616271628162916301631163216331634163516361637163816391640164116421643164416451646164716481649165016511652165316541655165616571658165916601661166216631664166516661667166816691670167116721673167416751676167716781679168016811682168316841685168616871688168916901691169216931694169516961697169816991700170117021703170417051706170717081709171017111712171317141715171617171718171917201721172217231724172517261727172817291730173117321733173417351736173717381739174017411742174317441745174617471748174917501751175217531754175517561757175817591760176117621763176417651766176717681769177017711772177317741775177617771778177917801781178217831784178517861787178817891790179117921793179417951796179717981799180018011802180318041805180618071808180918101811181218131814181518161817181818191820182118221823182418251826182718281829183018311832183318341835183618371838183918401841184218431844184518461847184818491850185118521853185418551856185718581859186018611862186318641865186618671868186918701871187218731874187518761877187818791880188118821883188418851886188718881889189018911892189318941895189618971898189919001901190219031904190519061907190819091910191119121913191419151916191719181919192019211922192319241925192619271928192919301931193219331934193519361937193819391940194119421943194419451946194719481949195019511952195319541955195619571958195919601961196219631964196519661967196819691970197119721973197419751976197719781979198019811982198319841985198619871988198919901991199219931994199519961997199819992000200120022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027202820292030203120322033203420352036203720382039204020412042204320442045204620472048204920502051205220532054205520562057205820592060206120622063206420652066206720682069207020712072207320742075207620772078207920802081208220832084208520862087208820892090209120922093209420952096209720982099210021012102210321042105210621072108210921102111211221132114211521162117211821192120212121222123212421252126212721282129213021312132213321342135213621372138213921402141214221432144214521462147214821492150215121522153215421552156215721582159216021612162216321642165216621672168216921702171217221732174217521762177217821792180218121822183218421852186218721882189219021912192219321942195219621972198219922002201220222032204220522062207220822092210221122122213221422152216221722182219222022212222222322242225222622272228222922302231223222332234223522362237223822392240224122422243224422452246224722482249225022512252225322542255225622572258225922602261226222632264226522662267226822692270227122722273227422752276227722782279228022812282228322842285228622872288228922902291229222932294229522962297229822992300230123022303230423052306230723082309231023112312231323142315231623172318231923202321232223232324232523262327232823292330233123322333233423352336233723382339234023412342234323442345234623472348234923502351235223532354235523562357235823592360236123622363236423652366236723682369237023712372237323742375237623772378237923802381238223832384238523862387238823892390239123922393239423952396239723982399240024012402240324042405240624072408240924102411241224132414241524162417241824192420242124222423242424252426242724282429243024312432243324342435243624372438243924402441244224432444244524462447244824492450245124522453245424552456245724582459246024612462246324642465246624672468246924702471247224732474247524762477247824792480248124822483248424852486248724882489249024912492249324942495249624972498249925002501250225032504250525062507250825092510251125122513251425152516251725182519252025212522252325242525252625272528252925302531253225332534253525362537253825392540254125422543254425452546254725482549255025512552255325542555255625572558255925602561256225632564256525662567256825692570257125722573257425752576257725782579258025812582258325842585258625872588258925902591259225932594259525962597259825992600260126022603260426052606260726082609261026112612261326142615261626172618261926202621262226232624262526262627262826292630263126322633263426352636263726382639264026412642264326442645264626472648264926502651265226532654265526562657265826592660266126622663266426652666266726682669267026712672267326742675267626772678267926802681268226832684268526862687268826892690269126922693269426952696269726982699270027012702270327042705270627072708270927102711271227132714271527162717271827192720272127222723272427252726272727282729273027312732273327342735273627372738273927402741274227432744274527462747274827492750275127522753275427552756275727582759276027612762276327642765276627672768276927702771277227732774277527762777277827792780278127822783278427852786278727882789279027912792279327942795279627972798279928002801280228032804280528062807280828092810281128122813281428152816281728182819282028212822282328242825282628272828282928302831283228332834283528362837283828392840284128422843284428452846284728482849285028512852285328542855285628572858285928602861286228632864286528662867286828692870287128722873287428752876287728782879288028812882288328842885288628872888288928902891289228932894289528962897289828992900290129022903290429052906290729082909291029112912291329142915291629172918291929202921292229232924292529262927292829292930293129322933293429352936293729382939294029412942294329442945294629472948294929502951295229532954295529562957295829592960296129622963296429652966296729682969297029712972297329742975297629772978297929802981298229832984298529862987298829892990299129922993299429952996299729982999300030013002300330043005300630073008300930103011301230133014301530163017301830193020302130223023302430253026302730283029303030313032303330343035303630373038303930403041304230433044304530463047304830493050305130523053305430553056305730583059306030613062306330643065306630673068306930703071307230733074307530763077307830793080308130823083308430853086308730883089309030913092309330943095309630973098309931003101310231033104310531063107310831093110311131123113311431153116311731183119312031213122312331243125312631273128312931303131313231333134313531363137313831393140314131423143314431453146314731483149315031513152315331543155315631573158315931603161316231633164316531663167316831693170317131723173317431753176317731783179318031813182318331843185318631873188318931903191319231933194319531963197319831993200320132023203320432053206320732083209321032113212321332143215321632173218321932203221322232233224322532263227322832293230323132323233323432353236323732383239324032413242324332443245324632473248324932503251325232533254325532563257325832593260326132623263326432653266326732683269327032713272327332743275327632773278327932803281328232833284328532863287328832893290329132923293329432953296329732983299330033013302330333043305330633073308330933103311331233133314331533163317331833193320332133223323332433253326332733283329333033313332333333343335333633373338333933403341334233433344334533463347334833493350335133523353335433553356335733583359336033613362336333643365336633673368336933703371337233733374337533763377337833793380338133823383338433853386338733883389339033913392339333943395339633973398339934003401340234033404340534063407340834093410341134123413341434153416341734183419342034213422342334243425342634273428342934303431343234333434343534363437343834393440344134423443344434453446344734483449345034513452345334543455345634573458345934603461346234633464346534663467346834693470347134723473347434753476347734783479348034813482348334843485348634873488348934903491349234933494349534963497349834993500350135023503350435053506350735083509351035113512351335143515351635173518351935203521
  1. #
  2. # (C) Copyright 2000 - 2005
  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.
  47. Where to get help:
  48. ==================
  49. In case you have questions about, problems with or contributions for
  50. U-Boot you should send a message to the U-Boot mailing list at
  51. <u-boot-users@lists.sourceforge.net>. There is also an archive of
  52. previous traffic on the mailing list - please search the archive
  53. before asking FAQ's. Please see
  54. http://lists.sourceforge.net/lists/listinfo/u-boot-users/
  55. Where we come from:
  56. ===================
  57. - start from 8xxrom sources
  58. - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
  59. - clean up code
  60. - make it easier to add custom boards
  61. - make it possible to add other [PowerPC] CPUs
  62. - extend functions, especially:
  63. * Provide extended interface to Linux boot loader
  64. * S-Record download
  65. * network boot
  66. * PCMCIA / CompactFLash / ATA disk / SCSI ... boot
  67. - create ARMBoot project (http://sourceforge.net/projects/armboot)
  68. - add other CPU families (starting with ARM)
  69. - create U-Boot project (http://sourceforge.net/projects/u-boot)
  70. Names and Spelling:
  71. ===================
  72. The "official" name of this project is "Das U-Boot". The spelling
  73. "U-Boot" shall be used in all written text (documentation, comments
  74. in source files etc.). Example:
  75. This is the README file for the U-Boot project.
  76. File names etc. shall be based on the string "u-boot". Examples:
  77. include/asm-ppc/u-boot.h
  78. #include <asm/u-boot.h>
  79. Variable names, preprocessor constants etc. shall be either based on
  80. the string "u_boot" or on "U_BOOT". Example:
  81. U_BOOT_VERSION u_boot_logo
  82. IH_OS_U_BOOT u_boot_hush_start
  83. Versioning:
  84. ===========
  85. U-Boot uses a 3 level version number containing a version, a
  86. sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",
  87. sub-version "34", and patchlevel "4".
  88. The patchlevel is used to indicate certain stages of development
  89. between released versions, i. e. officially released versions of
  90. U-Boot will always have a patchlevel of "0".
  91. Directory Hierarchy:
  92. ====================
  93. - board Board dependent files
  94. - common Misc architecture independent functions
  95. - cpu CPU specific files
  96. - 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
  97. - arm720t Files specific to ARM 720 CPUs
  98. - arm920t Files specific to ARM 920 CPUs
  99. - at91rm9200 Files specific to Atmel AT91RM9200 CPU
  100. - imx Files specific to Freescale MC9328 i.MX CPUs
  101. - s3c24x0 Files specific to Samsung S3C24X0 CPUs
  102. - arm925t Files specific to ARM 925 CPUs
  103. - arm926ejs Files specific to ARM 926 CPUs
  104. - arm1136 Files specific to ARM 1136 CPUs
  105. - i386 Files specific to i386 CPUs
  106. - ixp Files specific to Intel XScale IXP CPUs
  107. - mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
  108. - mips Files specific to MIPS CPUs
  109. - mpc5xx Files specific to Freescale MPC5xx CPUs
  110. - mpc5xxx Files specific to Freescale MPC5xxx CPUs
  111. - mpc8xx Files specific to Freescale MPC8xx CPUs
  112. - mpc8220 Files specific to Freescale MPC8220 CPUs
  113. - mpc824x Files specific to Freescale MPC824x CPUs
  114. - mpc8260 Files specific to Freescale MPC8260 CPUs
  115. - mpc85xx Files specific to Freescale MPC85xx CPUs
  116. - nios Files specific to Altera NIOS CPUs
  117. - nios2 Files specific to Altera Nios-II CPUs
  118. - ppc4xx Files specific to AMCC PowerPC 4xx CPUs
  119. - pxa Files specific to Intel XScale PXA CPUs
  120. - s3c44b0 Files specific to Samsung S3C44B0 CPUs
  121. - sa1100 Files specific to Intel StrongARM SA1100 CPUs
  122. - disk Code for disk drive partition handling
  123. - doc Documentation (don't expect too much)
  124. - drivers Commonly used device drivers
  125. - dtt Digital Thermometer and Thermostat drivers
  126. - examples Example code for standalone applications, etc.
  127. - include Header Files
  128. - lib_arm Files generic to ARM architecture
  129. - lib_generic Files generic to all architectures
  130. - lib_i386 Files generic to i386 architecture
  131. - lib_m68k Files generic to m68k architecture
  132. - lib_mips Files generic to MIPS architecture
  133. - lib_nios Files generic to NIOS architecture
  134. - lib_ppc Files generic to PowerPC architecture
  135. - net Networking code
  136. - post Power On Self Test
  137. - rtc Real Time Clock drivers
  138. - tools Tools to build S-Record or U-Boot images, etc.
  139. Software Configuration:
  140. =======================
  141. Configuration is usually done using C preprocessor defines; the
  142. rationale behind that is to avoid dead code whenever possible.
  143. There are two classes of configuration variables:
  144. * Configuration _OPTIONS_:
  145. These are selectable by the user and have names beginning with
  146. "CONFIG_".
  147. * Configuration _SETTINGS_:
  148. These depend on the hardware etc. and should not be meddled with if
  149. you don't know what you're doing; they have names beginning with
  150. "CFG_".
  151. Later we will add a configuration tool - probably similar to or even
  152. identical to what's used for the Linux kernel. Right now, we have to
  153. do the configuration by hand, which means creating some symbolic
  154. links and editing some configuration files. We use the TQM8xxL boards
  155. as an example here.
  156. Selection of Processor Architecture and Board Type:
  157. ---------------------------------------------------
  158. For all supported boards there are ready-to-use default
  159. configurations available; just type "make <board_name>_config".
  160. Example: For a TQM823L module type:
  161. cd u-boot
  162. make TQM823L_config
  163. For the Cogent platform, you need to specify the cpu type as well;
  164. e.g. "make cogent_mpc8xx_config". And also configure the cogent
  165. directory according to the instructions in cogent/README.
  166. Configuration Options:
  167. ----------------------
  168. Configuration depends on the combination of board and CPU type; all
  169. such information is kept in a configuration file
  170. "include/configs/<board_name>.h".
  171. Example: For a TQM823L module, all configuration settings are in
  172. "include/configs/TQM823L.h".
  173. Many of the options are named exactly as the corresponding Linux
  174. kernel configuration options. The intention is to make it easier to
  175. build a config tool - later.
  176. The following options need to be configured:
  177. - CPU Type: Define exactly one of
  178. PowerPC based CPUs:
  179. -------------------
  180. CONFIG_MPC823, CONFIG_MPC850, CONFIG_MPC855, CONFIG_MPC860
  181. or CONFIG_MPC5xx
  182. or CONFIG_MPC8220
  183. or CONFIG_MPC824X, CONFIG_MPC8260
  184. or CONFIG_MPC85xx
  185. or CONFIG_IOP480
  186. or CONFIG_405GP
  187. or CONFIG_405EP
  188. or CONFIG_440
  189. or CONFIG_MPC74xx
  190. or CONFIG_750FX
  191. ARM based CPUs:
  192. ---------------
  193. CONFIG_SA1110
  194. CONFIG_ARM7
  195. CONFIG_PXA250
  196. MicroBlaze based CPUs:
  197. ----------------------
  198. CONFIG_MICROBLAZE
  199. Nios-2 based CPUs:
  200. ----------------------
  201. CONFIG_NIOS2
  202. - Board Type: Define exactly one of
  203. PowerPC based boards:
  204. ---------------------
  205. CONFIG_ADCIOP CONFIG_GEN860T CONFIG_PCI405
  206. CONFIG_ADS860 CONFIG_GENIETV CONFIG_PCIPPC2
  207. CONFIG_AMX860 CONFIG_GTH CONFIG_PCIPPC6
  208. CONFIG_AP1000 CONFIG_gw8260 CONFIG_pcu_e
  209. CONFIG_AR405 CONFIG_hermes CONFIG_PIP405
  210. CONFIG_BAB7xx CONFIG_hymod CONFIG_PM826
  211. CONFIG_c2mon CONFIG_IAD210 CONFIG_ppmc8260
  212. CONFIG_CANBT CONFIG_ICU862 CONFIG_QS823
  213. CONFIG_CCM CONFIG_IP860 CONFIG_QS850
  214. CONFIG_CMI CONFIG_IPHASE4539 CONFIG_QS860T
  215. CONFIG_cogent_mpc8260 CONFIG_IVML24 CONFIG_RBC823
  216. CONFIG_cogent_mpc8xx CONFIG_IVML24_128 CONFIG_RPXClassic
  217. CONFIG_CPCI405 CONFIG_IVML24_256 CONFIG_RPXlite
  218. CONFIG_CPCI4052 CONFIG_IVMS8 CONFIG_RPXsuper
  219. CONFIG_CPCIISER4 CONFIG_IVMS8_128 CONFIG_rsdproto
  220. CONFIG_CPU86 CONFIG_IVMS8_256 CONFIG_sacsng
  221. CONFIG_CRAYL1 CONFIG_JSE CONFIG_Sandpoint8240
  222. CONFIG_CSB272 CONFIG_LANTEC CONFIG_Sandpoint8245
  223. CONFIG_CU824 CONFIG_LITE5200B CONFIG_sbc8260
  224. CONFIG_DASA_SIM CONFIG_lwmon CONFIG_sbc8560
  225. CONFIG_DB64360 CONFIG_MBX CONFIG_SM850
  226. CONFIG_DB64460 CONFIG_MBX860T CONFIG_SPD823TS
  227. CONFIG_DU405 CONFIG_MHPC CONFIG_STXGP3
  228. CONFIG_DUET_ADS CONFIG_MIP405 CONFIG_SXNI855T
  229. CONFIG_EBONY CONFIG_MOUSSE CONFIG_TQM823L
  230. CONFIG_ELPPC CONFIG_MPC8260ADS CONFIG_TQM8260
  231. CONFIG_ELPT860 CONFIG_MPC8540ADS CONFIG_TQM850L
  232. CONFIG_ep8260 CONFIG_MPC8540EVAL CONFIG_TQM855L
  233. CONFIG_ERIC CONFIG_MPC8560ADS CONFIG_TQM860L
  234. CONFIG_ESTEEM192E CONFIG_MUSENKI CONFIG_TTTech
  235. CONFIG_ETX094 CONFIG_MVS1 CONFIG_UTX8245
  236. CONFIG_EVB64260 CONFIG_NETPHONE CONFIG_V37
  237. CONFIG_FADS823 CONFIG_NETTA CONFIG_W7OLMC
  238. CONFIG_FADS850SAR CONFIG_NETVIA CONFIG_W7OLMG
  239. CONFIG_FADS860T CONFIG_NX823 CONFIG_WALNUT
  240. CONFIG_FLAGADM CONFIG_OCRTC CONFIG_ZPC1900
  241. CONFIG_FPS850L CONFIG_ORSG CONFIG_ZUMA
  242. CONFIG_FPS860L CONFIG_OXC
  243. ARM based boards:
  244. -----------------
  245. CONFIG_ARMADILLO, CONFIG_AT91RM9200DK, CONFIG_CERF250,
  246. CONFIG_CSB637, CONFIG_DNP1110, CONFIG_EP7312,
  247. CONFIG_H2_OMAP1610, CONFIG_HHP_CRADLE, CONFIG_IMPA7,
  248. CONFIG_INNOVATOROMAP1510, CONFIG_INNOVATOROMAP1610, CONFIG_KB9202,
  249. CONFIG_LART, CONFIG_LPD7A400, CONFIG_LUBBOCK,
  250. CONFIG_OSK_OMAP5912, CONFIG_OMAP2420H4, CONFIG_SHANNON,
  251. CONFIG_P2_OMAP730, CONFIG_SMDK2400, CONFIG_SMDK2410,
  252. CONFIG_TRAB, CONFIG_VCMA9
  253. MicroBlaze based boards:
  254. ------------------------
  255. CONFIG_SUZAKU
  256. Nios-2 based boards:
  257. ------------------------
  258. CONFIG_PCI5441 CONFIG_PK1C20
  259. - CPU Module Type: (if CONFIG_COGENT is defined)
  260. Define exactly one of
  261. CONFIG_CMA286_60_OLD
  262. --- FIXME --- not tested yet:
  263. CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
  264. CONFIG_CMA287_23, CONFIG_CMA287_50
  265. - Motherboard Type: (if CONFIG_COGENT is defined)
  266. Define exactly one of
  267. CONFIG_CMA101, CONFIG_CMA102
  268. - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
  269. Define one or more of
  270. CONFIG_CMA302
  271. - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
  272. Define one or more of
  273. CONFIG_LCD_HEARTBEAT - update a character position on
  274. the lcd display every second with
  275. a "rotator" |\-/|\-/
  276. - Board flavour: (if CONFIG_MPC8260ADS is defined)
  277. CONFIG_ADSTYPE
  278. Possible values are:
  279. CFG_8260ADS - original MPC8260ADS
  280. CFG_8266ADS - MPC8266ADS
  281. CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
  282. CFG_8272ADS - MPC8272ADS
  283. - MPC824X Family Member (if CONFIG_MPC824X is defined)
  284. Define exactly one of
  285. CONFIG_MPC8240, CONFIG_MPC8245
  286. - 8xx CPU Options: (if using an MPC8xx cpu)
  287. CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
  288. get_gclk_freq() cannot work
  289. e.g. if there is no 32KHz
  290. reference PIT/RTC clock
  291. CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
  292. or XTAL/EXTAL)
  293. - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
  294. CFG_8xx_CPUCLK_MIN
  295. CFG_8xx_CPUCLK_MAX
  296. CONFIG_8xx_CPUCLK_DEFAULT
  297. See doc/README.MPC866
  298. CFG_MEASURE_CPUCLK
  299. Define this to measure the actual CPU clock instead
  300. of relying on the correctness of the configured
  301. values. Mostly useful for board bringup to make sure
  302. the PLL is locked at the intended frequency. Note
  303. that this requires a (stable) reference clock (32 kHz
  304. RTC clock or CFG_8XX_XIN)
  305. - Linux Kernel Interface:
  306. CONFIG_CLOCKS_IN_MHZ
  307. U-Boot stores all clock information in Hz
  308. internally. For binary compatibility with older Linux
  309. kernels (which expect the clocks passed in the
  310. bd_info data to be in MHz) the environment variable
  311. "clocks_in_mhz" can be defined so that U-Boot
  312. converts clock data to MHZ before passing it to the
  313. Linux kernel.
  314. When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
  315. "clocks_in_mhz=1" is automatically included in the
  316. default environment.
  317. CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
  318. When transfering memsize parameter to linux, some versions
  319. expect it to be in bytes, others in MB.
  320. Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
  321. CONFIG_OF_FLAT_TREE
  322. New kernel versions are expecting firmware settings to be
  323. passed using flat open firmware trees.
  324. The environment variable "disable_of", when set, disables this
  325. functionality.
  326. CONFIG_OF_FLAT_TREE_MAX_SIZE
  327. The maximum size of the constructed OF tree.
  328. OF_CPU - The proper name of the cpus node.
  329. OF_SOC - The proper name of the soc node.
  330. OF_TBCLK - The timebase frequency.
  331. OF_STDOUT_PATH - The path to the console device
  332. CONFIG_OF_HAS_BD_T
  333. The resulting flat device tree will have a copy of the bd_t.
  334. Space should be pre-allocated in the dts for the bd_t.
  335. CONFIG_OF_HAS_UBOOT_ENV
  336. The resulting flat device tree will have a copy of u-boot's
  337. environment variables
  338. CONFIG_OF_BOARD_SETUP
  339. Board code has addition modification that it wants to make
  340. to the flat device tree before handing it off to the kernel
  341. - Serial Ports:
  342. CFG_PL010_SERIAL
  343. Define this if you want support for Amba PrimeCell PL010 UARTs.
  344. CFG_PL011_SERIAL
  345. Define this if you want support for Amba PrimeCell PL011 UARTs.
  346. CONFIG_PL011_CLOCK
  347. If you have Amba PrimeCell PL011 UARTs, set this variable to
  348. the clock speed of the UARTs.
  349. CONFIG_PL01x_PORTS
  350. If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
  351. define this to a list of base addresses for each (supported)
  352. port. See e.g. include/configs/versatile.h
  353. - Console Interface:
  354. Depending on board, define exactly one serial port
  355. (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
  356. CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
  357. console by defining CONFIG_8xx_CONS_NONE
  358. Note: if CONFIG_8xx_CONS_NONE is defined, the serial
  359. port routines must be defined elsewhere
  360. (i.e. serial_init(), serial_getc(), ...)
  361. CONFIG_CFB_CONSOLE
  362. Enables console device for a color framebuffer. Needs following
  363. defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
  364. VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
  365. (default big endian)
  366. VIDEO_HW_RECTFILL graphic chip supports
  367. rectangle fill
  368. (cf. smiLynxEM)
  369. VIDEO_HW_BITBLT graphic chip supports
  370. bit-blit (cf. smiLynxEM)
  371. VIDEO_VISIBLE_COLS visible pixel columns
  372. (cols=pitch)
  373. VIDEO_VISIBLE_ROWS visible pixel rows
  374. VIDEO_PIXEL_SIZE bytes per pixel
  375. VIDEO_DATA_FORMAT graphic data format
  376. (0-5, cf. cfb_console.c)
  377. VIDEO_FB_ADRS framebuffer address
  378. VIDEO_KBD_INIT_FCT keyboard int fct
  379. (i.e. i8042_kbd_init())
  380. VIDEO_TSTC_FCT test char fct
  381. (i.e. i8042_tstc)
  382. VIDEO_GETC_FCT get char fct
  383. (i.e. i8042_getc)
  384. CONFIG_CONSOLE_CURSOR cursor drawing on/off
  385. (requires blink timer
  386. cf. i8042.c)
  387. CFG_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
  388. CONFIG_CONSOLE_TIME display time/date info in
  389. upper right corner
  390. (requires CFG_CMD_DATE)
  391. CONFIG_VIDEO_LOGO display Linux logo in
  392. upper left corner
  393. CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
  394. linux_logo.h for logo.
  395. Requires CONFIG_VIDEO_LOGO
  396. CONFIG_CONSOLE_EXTRA_INFO
  397. addional board info beside
  398. the logo
  399. When CONFIG_CFB_CONSOLE is defined, video console is
  400. default i/o. Serial console can be forced with
  401. environment 'console=serial'.
  402. When CONFIG_SILENT_CONSOLE is defined, all console
  403. messages (by U-Boot and Linux!) can be silenced with
  404. the "silent" environment variable. See
  405. doc/README.silent for more information.
  406. - Console Baudrate:
  407. CONFIG_BAUDRATE - in bps
  408. Select one of the baudrates listed in
  409. CFG_BAUDRATE_TABLE, see below.
  410. CFG_BRGCLK_PRESCALE, baudrate prescale
  411. - Interrupt driven serial port input:
  412. CONFIG_SERIAL_SOFTWARE_FIFO
  413. PPC405GP only.
  414. Use an interrupt handler for receiving data on the
  415. serial port. It also enables using hardware handshake
  416. (RTS/CTS) and UART's built-in FIFO. Set the number of
  417. bytes the interrupt driven input buffer should have.
  418. Leave undefined to disable this feature, including
  419. disable the buffer and hardware handshake.
  420. - Console UART Number:
  421. CONFIG_UART1_CONSOLE
  422. AMCC PPC4xx only.
  423. If defined internal UART1 (and not UART0) is used
  424. as default U-Boot console.
  425. - Boot Delay: CONFIG_BOOTDELAY - in seconds
  426. Delay before automatically booting the default image;
  427. set to -1 to disable autoboot.
  428. See doc/README.autoboot for these options that
  429. work with CONFIG_BOOTDELAY. None are required.
  430. CONFIG_BOOT_RETRY_TIME
  431. CONFIG_BOOT_RETRY_MIN
  432. CONFIG_AUTOBOOT_KEYED
  433. CONFIG_AUTOBOOT_PROMPT
  434. CONFIG_AUTOBOOT_DELAY_STR
  435. CONFIG_AUTOBOOT_STOP_STR
  436. CONFIG_AUTOBOOT_DELAY_STR2
  437. CONFIG_AUTOBOOT_STOP_STR2
  438. CONFIG_ZERO_BOOTDELAY_CHECK
  439. CONFIG_RESET_TO_RETRY
  440. - Autoboot Command:
  441. CONFIG_BOOTCOMMAND
  442. Only needed when CONFIG_BOOTDELAY is enabled;
  443. define a command string that is automatically executed
  444. when no character is read on the console interface
  445. within "Boot Delay" after reset.
  446. CONFIG_BOOTARGS
  447. This can be used to pass arguments to the bootm
  448. command. The value of CONFIG_BOOTARGS goes into the
  449. environment value "bootargs".
  450. CONFIG_RAMBOOT and CONFIG_NFSBOOT
  451. The value of these goes into the environment as
  452. "ramboot" and "nfsboot" respectively, and can be used
  453. as a convenience, when switching between booting from
  454. ram and nfs.
  455. - Pre-Boot Commands:
  456. CONFIG_PREBOOT
  457. When this option is #defined, the existence of the
  458. environment variable "preboot" will be checked
  459. immediately before starting the CONFIG_BOOTDELAY
  460. countdown and/or running the auto-boot command resp.
  461. entering interactive mode.
  462. This feature is especially useful when "preboot" is
  463. automatically generated or modified. For an example
  464. see the LWMON board specific code: here "preboot" is
  465. modified when the user holds down a certain
  466. combination of keys on the (special) keyboard when
  467. booting the systems
  468. - Serial Download Echo Mode:
  469. CONFIG_LOADS_ECHO
  470. If defined to 1, all characters received during a
  471. serial download (using the "loads" command) are
  472. echoed back. This might be needed by some terminal
  473. emulations (like "cu"), but may as well just take
  474. time on others. This setting #define's the initial
  475. value of the "loads_echo" environment variable.
  476. - Kgdb Serial Baudrate: (if CFG_CMD_KGDB is defined)
  477. CONFIG_KGDB_BAUDRATE
  478. Select one of the baudrates listed in
  479. CFG_BAUDRATE_TABLE, see below.
  480. - Monitor Functions:
  481. CONFIG_COMMANDS
  482. Most monitor functions can be selected (or
  483. de-selected) by adjusting the definition of
  484. CONFIG_COMMANDS; to select individual functions,
  485. #define CONFIG_COMMANDS by "OR"ing any of the
  486. following values:
  487. #define enables commands:
  488. -------------------------
  489. CFG_CMD_ASKENV * ask for env variable
  490. CFG_CMD_AUTOSCRIPT Autoscript Support
  491. CFG_CMD_BDI bdinfo
  492. CFG_CMD_BEDBUG * Include BedBug Debugger
  493. CFG_CMD_BMP * BMP support
  494. CFG_CMD_BSP * Board specific commands
  495. CFG_CMD_BOOTD bootd
  496. CFG_CMD_CACHE * icache, dcache
  497. CFG_CMD_CONSOLE coninfo
  498. CFG_CMD_DATE * support for RTC, date/time...
  499. CFG_CMD_DHCP * DHCP support
  500. CFG_CMD_DIAG * Diagnostics
  501. CFG_CMD_DOC * Disk-On-Chip Support
  502. CFG_CMD_DTT * Digital Therm and Thermostat
  503. CFG_CMD_ECHO echo arguments
  504. CFG_CMD_EEPROM * EEPROM read/write support
  505. CFG_CMD_ELF * bootelf, bootvx
  506. CFG_CMD_ENV saveenv
  507. CFG_CMD_FDC * Floppy Disk Support
  508. CFG_CMD_FAT * FAT partition support
  509. CFG_CMD_FDOS * Dos diskette Support
  510. CFG_CMD_FLASH flinfo, erase, protect
  511. CFG_CMD_FPGA FPGA device initialization support
  512. CFG_CMD_HWFLOW * RTS/CTS hw flow control
  513. CFG_CMD_I2C * I2C serial bus support
  514. CFG_CMD_IDE * IDE harddisk support
  515. CFG_CMD_IMI iminfo
  516. CFG_CMD_IMLS List all found images
  517. CFG_CMD_IMMAP * IMMR dump support
  518. CFG_CMD_IRQ * irqinfo
  519. CFG_CMD_ITEST Integer/string test of 2 values
  520. CFG_CMD_JFFS2 * JFFS2 Support
  521. CFG_CMD_KGDB * kgdb
  522. CFG_CMD_LOADB loadb
  523. CFG_CMD_LOADS loads
  524. CFG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
  525. loop, loopw, mtest
  526. CFG_CMD_MISC Misc functions like sleep etc
  527. CFG_CMD_MMC * MMC memory mapped support
  528. CFG_CMD_MII * MII utility commands
  529. CFG_CMD_NAND * NAND support
  530. CFG_CMD_NET bootp, tftpboot, rarpboot
  531. CFG_CMD_PCI * pciinfo
  532. CFG_CMD_PCMCIA * PCMCIA support
  533. CFG_CMD_PING * send ICMP ECHO_REQUEST to network host
  534. CFG_CMD_PORTIO * Port I/O
  535. CFG_CMD_REGINFO * Register dump
  536. CFG_CMD_RUN run command in env variable
  537. CFG_CMD_SAVES * save S record dump
  538. CFG_CMD_SCSI * SCSI Support
  539. CFG_CMD_SDRAM * print SDRAM configuration information
  540. (requires CFG_CMD_I2C)
  541. CFG_CMD_SETGETDCR Support for DCR Register access (4xx only)
  542. CFG_CMD_SPI * SPI serial bus support
  543. CFG_CMD_USB * USB support
  544. CFG_CMD_VFD * VFD support (TRAB)
  545. CFG_CMD_BSP * Board SPecific functions
  546. CFG_CMD_CDP * Cisco Discover Protocol support
  547. -----------------------------------------------
  548. CFG_CMD_ALL all
  549. CONFIG_CMD_DFL Default configuration; at the moment
  550. this is includes all commands, except
  551. the ones marked with "*" in the list
  552. above.
  553. If you don't define CONFIG_COMMANDS it defaults to
  554. CONFIG_CMD_DFL in include/cmd_confdefs.h. A board can
  555. override the default settings in the respective
  556. include file.
  557. EXAMPLE: If you want all functions except of network
  558. support you can write:
  559. #define CONFIG_COMMANDS (CFG_CMD_ALL & ~CFG_CMD_NET)
  560. Note: Don't enable the "icache" and "dcache" commands
  561. (configuration option CFG_CMD_CACHE) unless you know
  562. what you (and your U-Boot users) are doing. Data
  563. cache cannot be enabled on systems like the 8xx or
  564. 8260 (where accesses to the IMMR region must be
  565. uncached), and it cannot be disabled on all other
  566. systems where we (mis-) use the data cache to hold an
  567. initial stack and some data.
  568. XXX - this list needs to get updated!
  569. - Watchdog:
  570. CONFIG_WATCHDOG
  571. If this variable is defined, it enables watchdog
  572. support. There must be support in the platform specific
  573. code for a watchdog. For the 8xx and 8260 CPUs, the
  574. SIU Watchdog feature is enabled in the SYPCR
  575. register.
  576. - U-Boot Version:
  577. CONFIG_VERSION_VARIABLE
  578. If this variable is defined, an environment variable
  579. named "ver" is created by U-Boot showing the U-Boot
  580. version as printed by the "version" command.
  581. This variable is readonly.
  582. - Real-Time Clock:
  583. When CFG_CMD_DATE is selected, the type of the RTC
  584. has to be selected, too. Define exactly one of the
  585. following options:
  586. CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
  587. CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
  588. CONFIG_RTC_MC146818 - use MC146818 RTC
  589. CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
  590. CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
  591. CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
  592. CONFIG_RTC_DS164x - use Dallas DS164x RTC
  593. CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
  594. Note that if the RTC uses I2C, then the I2C interface
  595. must also be configured. See I2C Support, below.
  596. - Timestamp Support:
  597. When CONFIG_TIMESTAMP is selected, the timestamp
  598. (date and time) of an image is printed by image
  599. commands like bootm or iminfo. This option is
  600. automatically enabled when you select CFG_CMD_DATE .
  601. - Partition Support:
  602. CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
  603. and/or CONFIG_ISO_PARTITION
  604. If IDE or SCSI support is enabled (CFG_CMD_IDE or
  605. CFG_CMD_SCSI) you must configure support for at least
  606. one partition type as well.
  607. - IDE Reset method:
  608. CONFIG_IDE_RESET_ROUTINE - this is defined in several
  609. board configurations files but used nowhere!
  610. CONFIG_IDE_RESET - is this is defined, IDE Reset will
  611. be performed by calling the function
  612. ide_set_reset(int reset)
  613. which has to be defined in a board specific file
  614. - ATAPI Support:
  615. CONFIG_ATAPI
  616. Set this to enable ATAPI support.
  617. - LBA48 Support
  618. CONFIG_LBA48
  619. Set this to enable support for disks larger than 137GB
  620. Also look at CFG_64BIT_LBA ,CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL
  621. Whithout these , LBA48 support uses 32bit variables and will 'only'
  622. support disks up to 2.1TB.
  623. CFG_64BIT_LBA:
  624. When enabled, makes the IDE subsystem use 64bit sector addresses.
  625. Default is 32bit.
  626. - SCSI Support:
  627. At the moment only there is only support for the
  628. SYM53C8XX SCSI controller; define
  629. CONFIG_SCSI_SYM53C8XX to enable it.
  630. CFG_SCSI_MAX_LUN [8], CFG_SCSI_MAX_SCSI_ID [7] and
  631. CFG_SCSI_MAX_DEVICE [CFG_SCSI_MAX_SCSI_ID *
  632. CFG_SCSI_MAX_LUN] can be adjusted to define the
  633. maximum numbers of LUNs, SCSI ID's and target
  634. devices.
  635. CFG_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
  636. - NETWORK Support (PCI):
  637. CONFIG_E1000
  638. Support for Intel 8254x gigabit chips.
  639. CONFIG_EEPRO100
  640. Support for Intel 82557/82559/82559ER chips.
  641. Optional CONFIG_EEPRO100_SROM_WRITE enables eeprom
  642. write routine for first time initialisation.
  643. CONFIG_TULIP
  644. Support for Digital 2114x chips.
  645. Optional CONFIG_TULIP_SELECT_MEDIA for board specific
  646. modem chip initialisation (KS8761/QS6611).
  647. CONFIG_NATSEMI
  648. Support for National dp83815 chips.
  649. CONFIG_NS8382X
  650. Support for National dp8382[01] gigabit chips.
  651. - NETWORK Support (other):
  652. CONFIG_DRIVER_LAN91C96
  653. Support for SMSC's LAN91C96 chips.
  654. CONFIG_LAN91C96_BASE
  655. Define this to hold the physical address
  656. of the LAN91C96's I/O space
  657. CONFIG_LAN91C96_USE_32_BIT
  658. Define this to enable 32 bit addressing
  659. CONFIG_DRIVER_SMC91111
  660. Support for SMSC's LAN91C111 chip
  661. CONFIG_SMC91111_BASE
  662. Define this to hold the physical address
  663. of the device (I/O space)
  664. CONFIG_SMC_USE_32_BIT
  665. Define this if data bus is 32 bits
  666. CONFIG_SMC_USE_IOFUNCS
  667. Define this to use i/o functions instead of macros
  668. (some hardware wont work with macros)
  669. - USB Support:
  670. At the moment only the UHCI host controller is
  671. supported (PIP405, MIP405, MPC5200); define
  672. CONFIG_USB_UHCI to enable it.
  673. define CONFIG_USB_KEYBOARD to enable the USB Keyboard
  674. and define CONFIG_USB_STORAGE to enable the USB
  675. storage devices.
  676. Note:
  677. Supported are USB Keyboards and USB Floppy drives
  678. (TEAC FD-05PUB).
  679. MPC5200 USB requires additional defines:
  680. CONFIG_USB_CLOCK
  681. for 528 MHz Clock: 0x0001bbbb
  682. CONFIG_USB_CONFIG
  683. for differential drivers: 0x00001000
  684. for single ended drivers: 0x00005000
  685. - MMC Support:
  686. The MMC controller on the Intel PXA is supported. To
  687. enable this define CONFIG_MMC. The MMC can be
  688. accessed from the boot prompt by mapping the device
  689. to physical memory similar to flash. Command line is
  690. enabled with CFG_CMD_MMC. The MMC driver also works with
  691. the FAT fs. This is enabled with CFG_CMD_FAT.
  692. - Journaling Flash filesystem support:
  693. CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
  694. CONFIG_JFFS2_NAND_DEV
  695. Define these for a default partition on a NAND device
  696. CFG_JFFS2_FIRST_SECTOR,
  697. CFG_JFFS2_FIRST_BANK, CFG_JFFS2_NUM_BANKS
  698. Define these for a default partition on a NOR device
  699. CFG_JFFS_CUSTOM_PART
  700. Define this to create an own partition. You have to provide a
  701. function struct part_info* jffs2_part_info(int part_num)
  702. If you define only one JFFS2 partition you may also want to
  703. #define CFG_JFFS_SINGLE_PART 1
  704. to disable the command chpart. This is the default when you
  705. have not defined a custom partition
  706. - Keyboard Support:
  707. CONFIG_ISA_KEYBOARD
  708. Define this to enable standard (PC-Style) keyboard
  709. support
  710. CONFIG_I8042_KBD
  711. Standard PC keyboard driver with US (is default) and
  712. GERMAN key layout (switch via environment 'keymap=de') support.
  713. Export function i8042_kbd_init, i8042_tstc and i8042_getc
  714. for cfb_console. Supports cursor blinking.
  715. - Video support:
  716. CONFIG_VIDEO
  717. Define this to enable video support (for output to
  718. video).
  719. CONFIG_VIDEO_CT69000
  720. Enable Chips & Technologies 69000 Video chip
  721. CONFIG_VIDEO_SMI_LYNXEM
  722. Enable Silicon Motion SMI 712/710/810 Video chip. The
  723. video output is selected via environment 'videoout'
  724. (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
  725. assumed.
  726. For the CT69000 and SMI_LYNXEM drivers, videomode is
  727. selected via environment 'videomode'. Two diferent ways
  728. are possible:
  729. - "videomode=num" 'num' is a standard LiLo mode numbers.
  730. Following standard modes are supported (* is default):
  731. Colors 640x480 800x600 1024x768 1152x864 1280x1024
  732. -------------+---------------------------------------------
  733. 8 bits | 0x301* 0x303 0x305 0x161 0x307
  734. 15 bits | 0x310 0x313 0x316 0x162 0x319
  735. 16 bits | 0x311 0x314 0x317 0x163 0x31A
  736. 24 bits | 0x312 0x315 0x318 ? 0x31B
  737. -------------+---------------------------------------------
  738. (i.e. setenv videomode 317; saveenv; reset;)
  739. - "videomode=bootargs" all the video parameters are parsed
  740. from the bootargs. (See drivers/videomodes.c)
  741. CONFIG_VIDEO_SED13806
  742. Enable Epson SED13806 driver. This driver supports 8bpp
  743. and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
  744. or CONFIG_VIDEO_SED13806_16BPP
  745. - Keyboard Support:
  746. CONFIG_KEYBOARD
  747. Define this to enable a custom keyboard support.
  748. This simply calls drv_keyboard_init() which must be
  749. defined in your board-specific files.
  750. The only board using this so far is RBC823.
  751. - LCD Support: CONFIG_LCD
  752. Define this to enable LCD support (for output to LCD
  753. display); also select one of the supported displays
  754. by defining one of these:
  755. CONFIG_NEC_NL6448AC33:
  756. NEC NL6448AC33-18. Active, color, single scan.
  757. CONFIG_NEC_NL6448BC20
  758. NEC NL6448BC20-08. 6.5", 640x480.
  759. Active, color, single scan.
  760. CONFIG_NEC_NL6448BC33_54
  761. NEC NL6448BC33-54. 10.4", 640x480.
  762. Active, color, single scan.
  763. CONFIG_SHARP_16x9
  764. Sharp 320x240. Active, color, single scan.
  765. It isn't 16x9, and I am not sure what it is.
  766. CONFIG_SHARP_LQ64D341
  767. Sharp LQ64D341 display, 640x480.
  768. Active, color, single scan.
  769. CONFIG_HLD1045
  770. HLD1045 display, 640x480.
  771. Active, color, single scan.
  772. CONFIG_OPTREX_BW
  773. Optrex CBL50840-2 NF-FW 99 22 M5
  774. or
  775. Hitachi LMG6912RPFC-00T
  776. or
  777. Hitachi SP14Q002
  778. 320x240. Black & white.
  779. Normally display is black on white background; define
  780. CFG_WHITE_ON_BLACK to get it inverted.
  781. - Splash Screen Support: CONFIG_SPLASH_SCREEN
  782. If this option is set, the environment is checked for
  783. a variable "splashimage". If found, the usual display
  784. of logo, copyright and system information on the LCD
  785. is suppressed and the BMP image at the address
  786. specified in "splashimage" is loaded instead. The
  787. console is redirected to the "nulldev", too. This
  788. allows for a "silent" boot where a splash screen is
  789. loaded very quickly after power-on.
  790. - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
  791. If this option is set, additionally to standard BMP
  792. images, gzipped BMP images can be displayed via the
  793. splashscreen support or the bmp command.
  794. - Compression support:
  795. CONFIG_BZIP2
  796. If this option is set, support for bzip2 compressed
  797. images is included. If not, only uncompressed and gzip
  798. compressed images are supported.
  799. NOTE: the bzip2 algorithm requires a lot of RAM, so
  800. the malloc area (as defined by CFG_MALLOC_LEN) should
  801. be at least 4MB.
  802. - MII/PHY support:
  803. CONFIG_PHY_ADDR
  804. The address of PHY on MII bus.
  805. CONFIG_PHY_CLOCK_FREQ (ppc4xx)
  806. The clock frequency of the MII bus
  807. CONFIG_PHY_GIGE
  808. If this option is set, support for speed/duplex
  809. detection of Gigabit PHY is included.
  810. CONFIG_PHY_RESET_DELAY
  811. Some PHY like Intel LXT971A need extra delay after
  812. reset before any MII register access is possible.
  813. For such PHY, set this option to the usec delay
  814. required. (minimum 300usec for LXT971A)
  815. CONFIG_PHY_CMD_DELAY (ppc4xx)
  816. Some PHY like Intel LXT971A need extra delay after
  817. command issued before MII status register can be read
  818. - Ethernet address:
  819. CONFIG_ETHADDR
  820. CONFIG_ETH2ADDR
  821. CONFIG_ETH3ADDR
  822. Define a default value for ethernet address to use
  823. for the respective ethernet interface, in case this
  824. is not determined automatically.
  825. - IP address:
  826. CONFIG_IPADDR
  827. Define a default value for the IP address to use for
  828. the default ethernet interface, in case this is not
  829. determined through e.g. bootp.
  830. - Server IP address:
  831. CONFIG_SERVERIP
  832. Defines a default value for theIP address of a TFTP
  833. server to contact when using the "tftboot" command.
  834. - BOOTP Recovery Mode:
  835. CONFIG_BOOTP_RANDOM_DELAY
  836. If you have many targets in a network that try to
  837. boot using BOOTP, you may want to avoid that all
  838. systems send out BOOTP requests at precisely the same
  839. moment (which would happen for instance at recovery
  840. from a power failure, when all systems will try to
  841. boot, thus flooding the BOOTP server. Defining
  842. CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
  843. inserted before sending out BOOTP requests. The
  844. following delays are insterted then:
  845. 1st BOOTP request: delay 0 ... 1 sec
  846. 2nd BOOTP request: delay 0 ... 2 sec
  847. 3rd BOOTP request: delay 0 ... 4 sec
  848. 4th and following
  849. BOOTP requests: delay 0 ... 8 sec
  850. - DHCP Advanced Options:
  851. CONFIG_BOOTP_MASK
  852. You can fine tune the DHCP functionality by adding
  853. these flags to the CONFIG_BOOTP_MASK define:
  854. CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
  855. serverip from a DHCP server, it is possible that more
  856. than one DNS serverip is offered to the client.
  857. If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
  858. serverip will be stored in the additional environment
  859. variable "dnsip2". The first DNS serverip is always
  860. stored in the variable "dnsip", when CONFIG_BOOTP_DNS
  861. is added to the CONFIG_BOOTP_MASK.
  862. CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
  863. to do a dynamic update of a DNS server. To do this, they
  864. need the hostname of the DHCP requester.
  865. If CONFIG_BOOP_SEND_HOSTNAME is added to the
  866. CONFIG_BOOTP_MASK, the content of the "hostname"
  867. environment variable is passed as option 12 to
  868. the DHCP server.
  869. - CDP Options:
  870. CONFIG_CDP_DEVICE_ID
  871. The device id used in CDP trigger frames.
  872. CONFIG_CDP_DEVICE_ID_PREFIX
  873. A two character string which is prefixed to the MAC address
  874. of the device.
  875. CONFIG_CDP_PORT_ID
  876. A printf format string which contains the ascii name of
  877. the port. Normally is set to "eth%d" which sets
  878. eth0 for the first ethernet, eth1 for the second etc.
  879. CONFIG_CDP_CAPABILITIES
  880. A 32bit integer which indicates the device capabilities;
  881. 0x00000010 for a normal host which does not forwards.
  882. CONFIG_CDP_VERSION
  883. An ascii string containing the version of the software.
  884. CONFIG_CDP_PLATFORM
  885. An ascii string containing the name of the platform.
  886. CONFIG_CDP_TRIGGER
  887. A 32bit integer sent on the trigger.
  888. CONFIG_CDP_POWER_CONSUMPTION
  889. A 16bit integer containing the power consumption of the
  890. device in .1 of milliwatts.
  891. CONFIG_CDP_APPLIANCE_VLAN_TYPE
  892. A byte containing the id of the VLAN.
  893. - Status LED: CONFIG_STATUS_LED
  894. Several configurations allow to display the current
  895. status using a LED. For instance, the LED will blink
  896. fast while running U-Boot code, stop blinking as
  897. soon as a reply to a BOOTP request was received, and
  898. start blinking slow once the Linux kernel is running
  899. (supported by a status LED driver in the Linux
  900. kernel). Defining CONFIG_STATUS_LED enables this
  901. feature in U-Boot.
  902. - CAN Support: CONFIG_CAN_DRIVER
  903. Defining CONFIG_CAN_DRIVER enables CAN driver support
  904. on those systems that support this (optional)
  905. feature, like the TQM8xxL modules.
  906. - I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C
  907. These enable I2C serial bus commands. Defining either of
  908. (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
  909. include the appropriate I2C driver for the selected cpu.
  910. This will allow you to use i2c commands at the u-boot
  911. command line (as long as you set CFG_CMD_I2C in
  912. CONFIG_COMMANDS) and communicate with i2c based realtime
  913. clock chips. See common/cmd_i2c.c for a description of the
  914. command line interface.
  915. CONFIG_HARD_I2C selects the CPM hardware driver for I2C.
  916. CONFIG_SOFT_I2C configures u-boot to use a software (aka
  917. bit-banging) driver instead of CPM or similar hardware
  918. support for I2C.
  919. There are several other quantities that must also be
  920. defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
  921. In both cases you will need to define CFG_I2C_SPEED
  922. to be the frequency (in Hz) at which you wish your i2c bus
  923. to run and CFG_I2C_SLAVE to be the address of this node (ie
  924. the cpu's i2c node address).
  925. Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)
  926. sets the cpu up as a master node and so its address should
  927. therefore be cleared to 0 (See, eg, MPC823e User's Manual
  928. p.16-473). So, set CFG_I2C_SLAVE to 0.
  929. That's all that's required for CONFIG_HARD_I2C.
  930. If you use the software i2c interface (CONFIG_SOFT_I2C)
  931. then the following macros need to be defined (examples are
  932. from include/configs/lwmon.h):
  933. I2C_INIT
  934. (Optional). Any commands necessary to enable the I2C
  935. controller or configure ports.
  936. eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
  937. I2C_PORT
  938. (Only for MPC8260 CPU). The I/O port to use (the code
  939. assumes both bits are on the same port). Valid values
  940. are 0..3 for ports A..D.
  941. I2C_ACTIVE
  942. The code necessary to make the I2C data line active
  943. (driven). If the data line is open collector, this
  944. define can be null.
  945. eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
  946. I2C_TRISTATE
  947. The code necessary to make the I2C data line tri-stated
  948. (inactive). If the data line is open collector, this
  949. define can be null.
  950. eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
  951. I2C_READ
  952. Code that returns TRUE if the I2C data line is high,
  953. FALSE if it is low.
  954. eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
  955. I2C_SDA(bit)
  956. If <bit> is TRUE, sets the I2C data line high. If it
  957. is FALSE, it clears it (low).
  958. eg: #define I2C_SDA(bit) \
  959. if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
  960. else immr->im_cpm.cp_pbdat &= ~PB_SDA
  961. I2C_SCL(bit)
  962. If <bit> is TRUE, sets the I2C clock line high. If it
  963. is FALSE, it clears it (low).
  964. eg: #define I2C_SCL(bit) \
  965. if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
  966. else immr->im_cpm.cp_pbdat &= ~PB_SCL
  967. I2C_DELAY
  968. This delay is invoked four times per clock cycle so this
  969. controls the rate of data transfer. The data rate thus
  970. is 1 / (I2C_DELAY * 4). Often defined to be something
  971. like:
  972. #define I2C_DELAY udelay(2)
  973. CFG_I2C_INIT_BOARD
  974. When a board is reset during an i2c bus transfer
  975. chips might think that the current transfer is still
  976. in progress. On some boards it is possible to access
  977. the i2c SCLK line directly, either by using the
  978. processor pin as a GPIO or by having a second pin
  979. connected to the bus. If this option is defined a
  980. custom i2c_init_board() routine in boards/xxx/board.c
  981. is run early in the boot sequence.
  982. CONFIG_I2CFAST (PPC405GP|PPC405EP only)
  983. This option enables configuration of bi_iic_fast[] flags
  984. in u-boot bd_info structure based on u-boot environment
  985. variable "i2cfast". (see also i2cfast)
  986. - SPI Support: CONFIG_SPI
  987. Enables SPI driver (so far only tested with
  988. SPI EEPROM, also an instance works with Crystal A/D and
  989. D/As on the SACSng board)
  990. CONFIG_SPI_X
  991. Enables extended (16-bit) SPI EEPROM addressing.
  992. (symmetrical to CONFIG_I2C_X)
  993. CONFIG_SOFT_SPI
  994. Enables a software (bit-bang) SPI driver rather than
  995. using hardware support. This is a general purpose
  996. driver that only requires three general I/O port pins
  997. (two outputs, one input) to function. If this is
  998. defined, the board configuration must define several
  999. SPI configuration items (port pins to use, etc). For
  1000. an example, see include/configs/sacsng.h.
  1001. - FPGA Support: CONFIG_FPGA_COUNT
  1002. Specify the number of FPGA devices to support.
  1003. CONFIG_FPGA
  1004. Used to specify the types of FPGA devices. For example,
  1005. #define CONFIG_FPGA CFG_XILINX_VIRTEX2
  1006. CFG_FPGA_PROG_FEEDBACK
  1007. Enable printing of hash marks during FPGA configuration.
  1008. CFG_FPGA_CHECK_BUSY
  1009. Enable checks on FPGA configuration interface busy
  1010. status by the configuration function. This option
  1011. will require a board or device specific function to
  1012. be written.
  1013. CONFIG_FPGA_DELAY
  1014. If defined, a function that provides delays in the FPGA
  1015. configuration driver.
  1016. CFG_FPGA_CHECK_CTRLC
  1017. Allow Control-C to interrupt FPGA configuration
  1018. CFG_FPGA_CHECK_ERROR
  1019. Check for configuration errors during FPGA bitfile
  1020. loading. For example, abort during Virtex II
  1021. configuration if the INIT_B line goes low (which
  1022. indicated a CRC error).
  1023. CFG_FPGA_WAIT_INIT
  1024. Maximum time to wait for the INIT_B line to deassert
  1025. after PROB_B has been deasserted during a Virtex II
  1026. FPGA configuration sequence. The default time is 500
  1027. mS.
  1028. CFG_FPGA_WAIT_BUSY
  1029. Maximum time to wait for BUSY to deassert during
  1030. Virtex II FPGA configuration. The default is 5 mS.
  1031. CFG_FPGA_WAIT_CONFIG
  1032. Time to wait after FPGA configuration. The default is
  1033. 200 mS.
  1034. - Configuration Management:
  1035. CONFIG_IDENT_STRING
  1036. If defined, this string will be added to the U-Boot
  1037. version information (U_BOOT_VERSION)
  1038. - Vendor Parameter Protection:
  1039. U-Boot considers the values of the environment
  1040. variables "serial#" (Board Serial Number) and
  1041. "ethaddr" (Ethernet Address) to be parameters that
  1042. are set once by the board vendor / manufacturer, and
  1043. protects these variables from casual modification by
  1044. the user. Once set, these variables are read-only,
  1045. and write or delete attempts are rejected. You can
  1046. change this behviour:
  1047. If CONFIG_ENV_OVERWRITE is #defined in your config
  1048. file, the write protection for vendor parameters is
  1049. completely disabled. Anybody can change or delete
  1050. these parameters.
  1051. Alternatively, if you #define _both_ CONFIG_ETHADDR
  1052. _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
  1053. ethernet address is installed in the environment,
  1054. which can be changed exactly ONCE by the user. [The
  1055. serial# is unaffected by this, i. e. it remains
  1056. read-only.]
  1057. - Protected RAM:
  1058. CONFIG_PRAM
  1059. Define this variable to enable the reservation of
  1060. "protected RAM", i. e. RAM which is not overwritten
  1061. by U-Boot. Define CONFIG_PRAM to hold the number of
  1062. kB you want to reserve for pRAM. You can overwrite
  1063. this default value by defining an environment
  1064. variable "pram" to the number of kB you want to
  1065. reserve. Note that the board info structure will
  1066. still show the full amount of RAM. If pRAM is
  1067. reserved, a new environment variable "mem" will
  1068. automatically be defined to hold the amount of
  1069. remaining RAM in a form that can be passed as boot
  1070. argument to Linux, for instance like that:
  1071. setenv bootargs ... mem=\${mem}
  1072. saveenv
  1073. This way you can tell Linux not to use this memory,
  1074. either, which results in a memory region that will
  1075. not be affected by reboots.
  1076. *WARNING* If your board configuration uses automatic
  1077. detection of the RAM size, you must make sure that
  1078. this memory test is non-destructive. So far, the
  1079. following board configurations are known to be
  1080. "pRAM-clean":
  1081. ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
  1082. HERMES, IP860, RPXlite, LWMON, LANTEC,
  1083. PCU_E, FLAGADM, TQM8260
  1084. - Error Recovery:
  1085. CONFIG_PANIC_HANG
  1086. Define this variable to stop the system in case of a
  1087. fatal error, so that you have to reset it manually.
  1088. This is probably NOT a good idea for an embedded
  1089. system where you want to system to reboot
  1090. automatically as fast as possible, but it may be
  1091. useful during development since you can try to debug
  1092. the conditions that lead to the situation.
  1093. CONFIG_NET_RETRY_COUNT
  1094. This variable defines the number of retries for
  1095. network operations like ARP, RARP, TFTP, or BOOTP
  1096. before giving up the operation. If not defined, a
  1097. default value of 5 is used.
  1098. - Command Interpreter:
  1099. CFG_AUTO_COMPLETE
  1100. Enable auto completion of commands using TAB.
  1101. CFG_HUSH_PARSER
  1102. Define this variable to enable the "hush" shell (from
  1103. Busybox) as command line interpreter, thus enabling
  1104. powerful command line syntax like
  1105. if...then...else...fi conditionals or `&&' and '||'
  1106. constructs ("shell scripts").
  1107. If undefined, you get the old, much simpler behaviour
  1108. with a somewhat smaller memory footprint.
  1109. CFG_PROMPT_HUSH_PS2
  1110. This defines the secondary prompt string, which is
  1111. printed when the command interpreter needs more input
  1112. to complete a command. Usually "> ".
  1113. Note:
  1114. In the current implementation, the local variables
  1115. space and global environment variables space are
  1116. separated. Local variables are those you define by
  1117. simply typing `name=value'. To access a local
  1118. variable later on, you have write `$name' or
  1119. `${name}'; to execute the contents of a variable
  1120. directly type `$name' at the command prompt.
  1121. Global environment variables are those you use
  1122. setenv/printenv to work with. To run a command stored
  1123. in such a variable, you need to use the run command,
  1124. and you must not use the '$' sign to access them.
  1125. To store commands and special characters in a
  1126. variable, please use double quotation marks
  1127. surrounding the whole text of the variable, instead
  1128. of the backslashes before semicolons and special
  1129. symbols.
  1130. - Default Environment:
  1131. CONFIG_EXTRA_ENV_SETTINGS
  1132. Define this to contain any number of null terminated
  1133. strings (variable = value pairs) that will be part of
  1134. the default environment compiled into the boot image.
  1135. For example, place something like this in your
  1136. board's config file:
  1137. #define CONFIG_EXTRA_ENV_SETTINGS \
  1138. "myvar1=value1\0" \
  1139. "myvar2=value2\0"
  1140. Warning: This method is based on knowledge about the
  1141. internal format how the environment is stored by the
  1142. U-Boot code. This is NOT an official, exported
  1143. interface! Although it is unlikely that this format
  1144. will change soon, there is no guarantee either.
  1145. You better know what you are doing here.
  1146. Note: overly (ab)use of the default environment is
  1147. discouraged. Make sure to check other ways to preset
  1148. the environment like the autoscript function or the
  1149. boot command first.
  1150. - DataFlash Support:
  1151. CONFIG_HAS_DATAFLASH
  1152. Defining this option enables DataFlash features and
  1153. allows to read/write in Dataflash via the standard
  1154. commands cp, md...
  1155. - SystemACE Support:
  1156. CONFIG_SYSTEMACE
  1157. Adding this option adds support for Xilinx SystemACE
  1158. chips attached via some sort of local bus. The address
  1159. of the chip must alsh be defined in the
  1160. CFG_SYSTEMACE_BASE macro. For example:
  1161. #define CONFIG_SYSTEMACE
  1162. #define CFG_SYSTEMACE_BASE 0xf0000000
  1163. When SystemACE support is added, the "ace" device type
  1164. becomes available to the fat commands, i.e. fatls.
  1165. - TFTP Fixed UDP Port:
  1166. CONFIG_TFTP_PORT
  1167. If this is defined, the environment variable tftpsrcp
  1168. is used to supply the TFTP UDP source port value.
  1169. If tftpsrcp isn't defined, the normal pseudo-random port
  1170. number generator is used.
  1171. Also, the environment variable tftpdstp is used to supply
  1172. the TFTP UDP destination port value. If tftpdstp isn't
  1173. defined, the normal port 69 is used.
  1174. The purpose for tftpsrcp is to allow a TFTP server to
  1175. blindly start the TFTP transfer using the pre-configured
  1176. target IP address and UDP port. This has the effect of
  1177. "punching through" the (Windows XP) firewall, allowing
  1178. the remainder of the TFTP transfer to proceed normally.
  1179. A better solution is to properly configure the firewall,
  1180. but sometimes that is not allowed.
  1181. - Show boot progress:
  1182. CONFIG_SHOW_BOOT_PROGRESS
  1183. Defining this option allows to add some board-
  1184. specific code (calling a user-provided function
  1185. "show_boot_progress(int)") that enables you to show
  1186. the system's boot progress on some display (for
  1187. example, some LED's) on your board. At the moment,
  1188. the following checkpoints are implemented:
  1189. Arg Where When
  1190. 1 common/cmd_bootm.c before attempting to boot an image
  1191. -1 common/cmd_bootm.c Image header has bad magic number
  1192. 2 common/cmd_bootm.c Image header has correct magic number
  1193. -2 common/cmd_bootm.c Image header has bad checksum
  1194. 3 common/cmd_bootm.c Image header has correct checksum
  1195. -3 common/cmd_bootm.c Image data has bad checksum
  1196. 4 common/cmd_bootm.c Image data has correct checksum
  1197. -4 common/cmd_bootm.c Image is for unsupported architecture
  1198. 5 common/cmd_bootm.c Architecture check OK
  1199. -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
  1200. 6 common/cmd_bootm.c Image Type check OK
  1201. -6 common/cmd_bootm.c gunzip uncompression error
  1202. -7 common/cmd_bootm.c Unimplemented compression type
  1203. 7 common/cmd_bootm.c Uncompression OK
  1204. -8 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
  1205. 8 common/cmd_bootm.c Image Type check OK
  1206. -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
  1207. 9 common/cmd_bootm.c Start initial ramdisk verification
  1208. -10 common/cmd_bootm.c Ramdisk header has bad magic number
  1209. -11 common/cmd_bootm.c Ramdisk header has bad checksum
  1210. 10 common/cmd_bootm.c Ramdisk header is OK
  1211. -12 common/cmd_bootm.c Ramdisk data has bad checksum
  1212. 11 common/cmd_bootm.c Ramdisk data has correct checksum
  1213. 12 common/cmd_bootm.c Ramdisk verification complete, start loading
  1214. -13 common/cmd_bootm.c Wrong Image Type (not PPC Linux Ramdisk)
  1215. 13 common/cmd_bootm.c Start multifile image verification
  1216. 14 common/cmd_bootm.c No initial ramdisk, no multifile, continue.
  1217. 15 common/cmd_bootm.c All preparation done, transferring control to OS
  1218. -30 lib_ppc/board.c Fatal error, hang the system
  1219. -31 post/post.c POST test failed, detected by post_output_backlog()
  1220. -32 post/post.c POST test failed, detected by post_run_single()
  1221. -1 common/cmd_doc.c Bad usage of "doc" command
  1222. -1 common/cmd_doc.c No boot device
  1223. -1 common/cmd_doc.c Unknown Chip ID on boot device
  1224. -1 common/cmd_doc.c Read Error on boot device
  1225. -1 common/cmd_doc.c Image header has bad magic number
  1226. -1 common/cmd_ide.c Bad usage of "ide" command
  1227. -1 common/cmd_ide.c No boot device
  1228. -1 common/cmd_ide.c Unknown boot device
  1229. -1 common/cmd_ide.c Unknown partition table
  1230. -1 common/cmd_ide.c Invalid partition type
  1231. -1 common/cmd_ide.c Read Error on boot device
  1232. -1 common/cmd_ide.c Image header has bad magic number
  1233. -1 common/cmd_nand.c Bad usage of "nand" command
  1234. -1 common/cmd_nand.c No boot device
  1235. -1 common/cmd_nand.c Unknown Chip ID on boot device
  1236. -1 common/cmd_nand.c Read Error on boot device
  1237. -1 common/cmd_nand.c Image header has bad magic number
  1238. -1 common/env_common.c Environment has a bad CRC, using default
  1239. Modem Support:
  1240. --------------
  1241. [so far only for SMDK2400 and TRAB boards]
  1242. - Modem support endable:
  1243. CONFIG_MODEM_SUPPORT
  1244. - RTS/CTS Flow control enable:
  1245. CONFIG_HWFLOW
  1246. - Modem debug support:
  1247. CONFIG_MODEM_SUPPORT_DEBUG
  1248. Enables debugging stuff (char screen[1024], dbg())
  1249. for modem support. Useful only with BDI2000.
  1250. - Interrupt support (PPC):
  1251. There are common interrupt_init() and timer_interrupt()
  1252. for all PPC archs. interrupt_init() calls interrupt_init_cpu()
  1253. for cpu specific initialization. interrupt_init_cpu()
  1254. should set decrementer_count to appropriate value. If
  1255. cpu resets decrementer automatically after interrupt
  1256. (ppc4xx) it should set decrementer_count to zero.
  1257. timer_interrupt() calls timer_interrupt_cpu() for cpu
  1258. specific handling. If board has watchdog / status_led
  1259. / other_activity_monitor it works automatically from
  1260. general timer_interrupt().
  1261. - General:
  1262. In the target system modem support is enabled when a
  1263. specific key (key combination) is pressed during
  1264. power-on. Otherwise U-Boot will boot normally
  1265. (autoboot). The key_pressed() fuction is called from
  1266. board_init(). Currently key_pressed() is a dummy
  1267. function, returning 1 and thus enabling modem
  1268. initialization.
  1269. If there are no modem init strings in the
  1270. environment, U-Boot proceed to autoboot; the
  1271. previous output (banner, info printfs) will be
  1272. supressed, though.
  1273. See also: doc/README.Modem
  1274. Configuration Settings:
  1275. -----------------------
  1276. - CFG_LONGHELP: Defined when you want long help messages included;
  1277. undefine this when you're short of memory.
  1278. - CFG_PROMPT: This is what U-Boot prints on the console to
  1279. prompt for user input.
  1280. - CFG_CBSIZE: Buffer size for input from the Console
  1281. - CFG_PBSIZE: Buffer size for Console output
  1282. - CFG_MAXARGS: max. Number of arguments accepted for monitor commands
  1283. - CFG_BARGSIZE: Buffer size for Boot Arguments which are passed to
  1284. the application (usually a Linux kernel) when it is
  1285. booted
  1286. - CFG_BAUDRATE_TABLE:
  1287. List of legal baudrate settings for this board.
  1288. - CFG_CONSOLE_INFO_QUIET
  1289. Suppress display of console information at boot.
  1290. - CFG_CONSOLE_IS_IN_ENV
  1291. If the board specific function
  1292. extern int overwrite_console (void);
  1293. returns 1, the stdin, stderr and stdout are switched to the
  1294. serial port, else the settings in the environment are used.
  1295. - CFG_CONSOLE_OVERWRITE_ROUTINE
  1296. Enable the call to overwrite_console().
  1297. - CFG_CONSOLE_ENV_OVERWRITE
  1298. Enable overwrite of previous console environment settings.
  1299. - CFG_MEMTEST_START, CFG_MEMTEST_END:
  1300. Begin and End addresses of the area used by the
  1301. simple memory test.
  1302. - CFG_ALT_MEMTEST:
  1303. Enable an alternate, more extensive memory test.
  1304. - CFG_MEMTEST_SCRATCH:
  1305. Scratch address used by the alternate memory test
  1306. You only need to set this if address zero isn't writeable
  1307. - CFG_TFTP_LOADADDR:
  1308. Default load address for network file downloads
  1309. - CFG_LOADS_BAUD_CHANGE:
  1310. Enable temporary baudrate change while serial download
  1311. - CFG_SDRAM_BASE:
  1312. Physical start address of SDRAM. _Must_ be 0 here.
  1313. - CFG_MBIO_BASE:
  1314. Physical start address of Motherboard I/O (if using a
  1315. Cogent motherboard)
  1316. - CFG_FLASH_BASE:
  1317. Physical start address of Flash memory.
  1318. - CFG_MONITOR_BASE:
  1319. Physical start address of boot monitor code (set by
  1320. make config files to be same as the text base address
  1321. (TEXT_BASE) used when linking) - same as
  1322. CFG_FLASH_BASE when booting from flash.
  1323. - CFG_MONITOR_LEN:
  1324. Size of memory reserved for monitor code, used to
  1325. determine _at_compile_time_ (!) if the environment is
  1326. embedded within the U-Boot image, or in a separate
  1327. flash sector.
  1328. - CFG_MALLOC_LEN:
  1329. Size of DRAM reserved for malloc() use.
  1330. - CFG_BOOTM_LEN:
  1331. Normally compressed uImages are limited to an
  1332. uncompressed size of 8 MBytes. If this is not enough,
  1333. you can define CFG_BOOTM_LEN in your board config file
  1334. to adjust this setting to your needs.
  1335. - CFG_BOOTMAPSZ:
  1336. Maximum size of memory mapped by the startup code of
  1337. the Linux kernel; all data that must be processed by
  1338. the Linux kernel (bd_info, boot arguments, eventually
  1339. initrd image) must be put below this limit.
  1340. - CFG_MAX_FLASH_BANKS:
  1341. Max number of Flash memory banks
  1342. - CFG_MAX_FLASH_SECT:
  1343. Max number of sectors on a Flash chip
  1344. - CFG_FLASH_ERASE_TOUT:
  1345. Timeout for Flash erase operations (in ms)
  1346. - CFG_FLASH_WRITE_TOUT:
  1347. Timeout for Flash write operations (in ms)
  1348. - CFG_FLASH_LOCK_TOUT
  1349. Timeout for Flash set sector lock bit operation (in ms)
  1350. - CFG_FLASH_UNLOCK_TOUT
  1351. Timeout for Flash clear lock bits operation (in ms)
  1352. - CFG_FLASH_PROTECTION
  1353. If defined, hardware flash sectors protection is used
  1354. instead of U-Boot software protection.
  1355. - CFG_DIRECT_FLASH_TFTP:
  1356. Enable TFTP transfers directly to flash memory;
  1357. without this option such a download has to be
  1358. performed in two steps: (1) download to RAM, and (2)
  1359. copy from RAM to flash.
  1360. The two-step approach is usually more reliable, since
  1361. you can check if the download worked before you erase
  1362. the flash, but in some situations (when sytem RAM is
  1363. too limited to allow for a tempory copy of the
  1364. downloaded image) this option may be very useful.
  1365. - CFG_FLASH_CFI:
  1366. Define if the flash driver uses extra elements in the
  1367. common flash structure for storing flash geometry.
  1368. - CFG_FLASH_CFI_DRIVER
  1369. This option also enables the building of the cfi_flash driver
  1370. in the drivers directory
  1371. - CFG_FLASH_QUIET_TEST
  1372. If this option is defined, the common CFI flash doesn't
  1373. print it's warning upon not recognized FLASH banks. This
  1374. is useful, if some of the configured banks are only
  1375. optionally available.
  1376. - CFG_RX_ETH_BUFFER:
  1377. Defines the number of ethernet receive buffers. On some
  1378. ethernet controllers it is recommended to set this value
  1379. to 8 or even higher (EEPRO100 or 405 EMAC), since all
  1380. buffers can be full shortly after enabling the interface
  1381. on high ethernet traffic.
  1382. Defaults to 4 if not defined.
  1383. The following definitions that deal with the placement and management
  1384. of environment data (variable area); in general, we support the
  1385. following configurations:
  1386. - CFG_ENV_IS_IN_FLASH:
  1387. Define this if the environment is in flash memory.
  1388. a) The environment occupies one whole flash sector, which is
  1389. "embedded" in the text segment with the U-Boot code. This
  1390. happens usually with "bottom boot sector" or "top boot
  1391. sector" type flash chips, which have several smaller
  1392. sectors at the start or the end. For instance, such a
  1393. layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
  1394. such a case you would place the environment in one of the
  1395. 4 kB sectors - with U-Boot code before and after it. With
  1396. "top boot sector" type flash chips, you would put the
  1397. environment in one of the last sectors, leaving a gap
  1398. between U-Boot and the environment.
  1399. - CFG_ENV_OFFSET:
  1400. Offset of environment data (variable area) to the
  1401. beginning of flash memory; for instance, with bottom boot
  1402. type flash chips the second sector can be used: the offset
  1403. for this sector is given here.
  1404. CFG_ENV_OFFSET is used relative to CFG_FLASH_BASE.
  1405. - CFG_ENV_ADDR:
  1406. This is just another way to specify the start address of
  1407. the flash sector containing the environment (instead of
  1408. CFG_ENV_OFFSET).
  1409. - CFG_ENV_SECT_SIZE:
  1410. Size of the sector containing the environment.
  1411. b) Sometimes flash chips have few, equal sized, BIG sectors.
  1412. In such a case you don't want to spend a whole sector for
  1413. the environment.
  1414. - CFG_ENV_SIZE:
  1415. If you use this in combination with CFG_ENV_IS_IN_FLASH
  1416. and CFG_ENV_SECT_SIZE, you can specify to use only a part
  1417. of this flash sector for the environment. This saves
  1418. memory for the RAM copy of the environment.
  1419. It may also save flash memory if you decide to use this
  1420. when your environment is "embedded" within U-Boot code,
  1421. since then the remainder of the flash sector could be used
  1422. for U-Boot code. It should be pointed out that this is
  1423. STRONGLY DISCOURAGED from a robustness point of view:
  1424. updating the environment in flash makes it always
  1425. necessary to erase the WHOLE sector. If something goes
  1426. wrong before the contents has been restored from a copy in
  1427. RAM, your target system will be dead.
  1428. - CFG_ENV_ADDR_REDUND
  1429. CFG_ENV_SIZE_REDUND
  1430. These settings describe a second storage area used to hold
  1431. a redundand copy of the environment data, so that there is
  1432. a valid backup copy in case there is a power failure during
  1433. a "saveenv" operation.
  1434. BE CAREFUL! Any changes to the flash layout, and some changes to the
  1435. source code will make it necessary to adapt <board>/u-boot.lds*
  1436. accordingly!
  1437. - CFG_ENV_IS_IN_NVRAM:
  1438. Define this if you have some non-volatile memory device
  1439. (NVRAM, battery buffered SRAM) which you want to use for the
  1440. environment.
  1441. - CFG_ENV_ADDR:
  1442. - CFG_ENV_SIZE:
  1443. These two #defines are used to determin the memory area you
  1444. want to use for environment. It is assumed that this memory
  1445. can just be read and written to, without any special
  1446. provision.
  1447. BE CAREFUL! The first access to the environment happens quite early
  1448. in U-Boot initalization (when we try to get the setting of for the
  1449. console baudrate). You *MUST* have mappend your NVRAM area then, or
  1450. U-Boot will hang.
  1451. Please note that even with NVRAM we still use a copy of the
  1452. environment in RAM: we could work on NVRAM directly, but we want to
  1453. keep settings there always unmodified except somebody uses "saveenv"
  1454. to save the current settings.
  1455. - CFG_ENV_IS_IN_EEPROM:
  1456. Use this if you have an EEPROM or similar serial access
  1457. device and a driver for it.
  1458. - CFG_ENV_OFFSET:
  1459. - CFG_ENV_SIZE:
  1460. These two #defines specify the offset and size of the
  1461. environment area within the total memory of your EEPROM.
  1462. - CFG_I2C_EEPROM_ADDR:
  1463. If defined, specified the chip address of the EEPROM device.
  1464. The default address is zero.
  1465. - CFG_EEPROM_PAGE_WRITE_BITS:
  1466. If defined, the number of bits used to address bytes in a
  1467. single page in the EEPROM device. A 64 byte page, for example
  1468. would require six bits.
  1469. - CFG_EEPROM_PAGE_WRITE_DELAY_MS:
  1470. If defined, the number of milliseconds to delay between
  1471. page writes. The default is zero milliseconds.
  1472. - CFG_I2C_EEPROM_ADDR_LEN:
  1473. The length in bytes of the EEPROM memory array address. Note
  1474. that this is NOT the chip address length!
  1475. - CFG_I2C_EEPROM_ADDR_OVERFLOW:
  1476. EEPROM chips that implement "address overflow" are ones
  1477. like Catalyst 24WC04/08/16 which has 9/10/11 bits of
  1478. address and the extra bits end up in the "chip address" bit
  1479. slots. This makes a 24WC08 (1Kbyte) chip look like four 256
  1480. byte chips.
  1481. Note that we consider the length of the address field to
  1482. still be one byte because the extra address bits are hidden
  1483. in the chip address.
  1484. - CFG_EEPROM_SIZE:
  1485. The size in bytes of the EEPROM device.
  1486. - CFG_ENV_IS_IN_DATAFLASH:
  1487. Define this if you have a DataFlash memory device which you
  1488. want to use for the environment.
  1489. - CFG_ENV_OFFSET:
  1490. - CFG_ENV_ADDR:
  1491. - CFG_ENV_SIZE:
  1492. These three #defines specify the offset and size of the
  1493. environment area within the total memory of your DataFlash placed
  1494. at the specified address.
  1495. - CFG_ENV_IS_IN_NAND:
  1496. Define this if you have a NAND device which you want to use
  1497. for the environment.
  1498. - CFG_ENV_OFFSET:
  1499. - CFG_ENV_SIZE:
  1500. These two #defines specify the offset and size of the environment
  1501. area within the first NAND device.
  1502. - CFG_SPI_INIT_OFFSET
  1503. Defines offset to the initial SPI buffer area in DPRAM. The
  1504. area is used at an early stage (ROM part) if the environment
  1505. is configured to reside in the SPI EEPROM: We need a 520 byte
  1506. scratch DPRAM area. It is used between the two initialization
  1507. calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
  1508. to be a good choice since it makes it far enough from the
  1509. start of the data area as well as from the stack pointer.
  1510. Please note that the environment is read-only as long as the monitor
  1511. has been relocated to RAM and a RAM copy of the environment has been
  1512. created; also, when using EEPROM you will have to use getenv_r()
  1513. until then to read environment variables.
  1514. The environment is protected by a CRC32 checksum. Before the monitor
  1515. is relocated into RAM, as a result of a bad CRC you will be working
  1516. with the compiled-in default environment - *silently*!!! [This is
  1517. necessary, because the first environment variable we need is the
  1518. "baudrate" setting for the console - if we have a bad CRC, we don't
  1519. have any device yet where we could complain.]
  1520. Note: once the monitor has been relocated, then it will complain if
  1521. the default environment is used; a new CRC is computed as soon as you
  1522. use the "saveenv" command to store a valid environment.
  1523. - CFG_FAULT_ECHO_LINK_DOWN:
  1524. Echo the inverted Ethernet link state to the fault LED.
  1525. Note: If this option is active, then CFG_FAULT_MII_ADDR
  1526. also needs to be defined.
  1527. - CFG_FAULT_MII_ADDR:
  1528. MII address of the PHY to check for the Ethernet link state.
  1529. - CFG_64BIT_VSPRINTF:
  1530. Makes vsprintf (and all *printf functions) support printing
  1531. of 64bit values by using the L quantifier
  1532. - CFG_64BIT_STRTOUL:
  1533. Adds simple_strtoull that returns a 64bit value
  1534. Low Level (hardware related) configuration options:
  1535. ---------------------------------------------------
  1536. - CFG_CACHELINE_SIZE:
  1537. Cache Line Size of the CPU.
  1538. - CFG_DEFAULT_IMMR:
  1539. Default address of the IMMR after system reset.
  1540. Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
  1541. and RPXsuper) to be able to adjust the position of
  1542. the IMMR register after a reset.
  1543. - Floppy Disk Support:
  1544. CFG_FDC_DRIVE_NUMBER
  1545. the default drive number (default value 0)
  1546. CFG_ISA_IO_STRIDE
  1547. defines the spacing between fdc chipset registers
  1548. (default value 1)
  1549. CFG_ISA_IO_OFFSET
  1550. defines the offset of register from address. It
  1551. depends on which part of the data bus is connected to
  1552. the fdc chipset. (default value 0)
  1553. If CFG_ISA_IO_STRIDE CFG_ISA_IO_OFFSET and
  1554. CFG_FDC_DRIVE_NUMBER are undefined, they take their
  1555. default value.
  1556. if CFG_FDC_HW_INIT is defined, then the function
  1557. fdc_hw_init() is called at the beginning of the FDC
  1558. setup. fdc_hw_init() must be provided by the board
  1559. source code. It is used to make hardware dependant
  1560. initializations.
  1561. - CFG_IMMR: Physical address of the Internal Memory.
  1562. DO NOT CHANGE unless you know exactly what you're
  1563. doing! (11-4) [MPC8xx/82xx systems only]
  1564. - CFG_INIT_RAM_ADDR:
  1565. Start address of memory area that can be used for
  1566. initial data and stack; please note that this must be
  1567. writable memory that is working WITHOUT special
  1568. initialization, i. e. you CANNOT use normal RAM which
  1569. will become available only after programming the
  1570. memory controller and running certain initialization
  1571. sequences.
  1572. U-Boot uses the following memory types:
  1573. - MPC8xx and MPC8260: IMMR (internal memory of the CPU)
  1574. - MPC824X: data cache
  1575. - PPC4xx: data cache
  1576. - CFG_GBL_DATA_OFFSET:
  1577. Offset of the initial data structure in the memory
  1578. area defined by CFG_INIT_RAM_ADDR. Usually
  1579. CFG_GBL_DATA_OFFSET is chosen such that the initial
  1580. data is located at the end of the available space
  1581. (sometimes written as (CFG_INIT_RAM_END -
  1582. CFG_INIT_DATA_SIZE), and the initial stack is just
  1583. below that area (growing from (CFG_INIT_RAM_ADDR +
  1584. CFG_GBL_DATA_OFFSET) downward.
  1585. Note:
  1586. On the MPC824X (or other systems that use the data
  1587. cache for initial memory) the address chosen for
  1588. CFG_INIT_RAM_ADDR is basically arbitrary - it must
  1589. point to an otherwise UNUSED address space between
  1590. the top of RAM and the start of the PCI space.
  1591. - CFG_SIUMCR: SIU Module Configuration (11-6)
  1592. - CFG_SYPCR: System Protection Control (11-9)
  1593. - CFG_TBSCR: Time Base Status and Control (11-26)
  1594. - CFG_PISCR: Periodic Interrupt Status and Control (11-31)
  1595. - CFG_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30)
  1596. - CFG_SCCR: System Clock and reset Control Register (15-27)
  1597. - CFG_OR_TIMING_SDRAM:
  1598. SDRAM timing
  1599. - CFG_MAMR_PTA:
  1600. periodic timer for refresh
  1601. - CFG_DER: Debug Event Register (37-47)
  1602. - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CFG_REMAP_OR_AM,
  1603. CFG_PRELIM_OR_AM, CFG_OR_TIMING_FLASH, CFG_OR0_REMAP,
  1604. CFG_OR0_PRELIM, CFG_BR0_PRELIM, CFG_OR1_REMAP, CFG_OR1_PRELIM,
  1605. CFG_BR1_PRELIM:
  1606. Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
  1607. - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
  1608. CFG_OR_TIMING_SDRAM, CFG_OR2_PRELIM, CFG_BR2_PRELIM,
  1609. CFG_OR3_PRELIM, CFG_BR3_PRELIM:
  1610. Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
  1611. - CFG_MAMR_PTA, CFG_MPTPR_2BK_4K, CFG_MPTPR_1BK_4K, CFG_MPTPR_2BK_8K,
  1612. CFG_MPTPR_1BK_8K, CFG_MAMR_8COL, CFG_MAMR_9COL:
  1613. Machine Mode Register and Memory Periodic Timer
  1614. Prescaler definitions (SDRAM timing)
  1615. - CFG_I2C_UCODE_PATCH, CFG_I2C_DPMEM_OFFSET [0x1FC0]:
  1616. enable I2C microcode relocation patch (MPC8xx);
  1617. define relocation offset in DPRAM [DSP2]
  1618. - CFG_SPI_UCODE_PATCH, CFG_SPI_DPMEM_OFFSET [0x1FC0]:
  1619. enable SPI microcode relocation patch (MPC8xx);
  1620. define relocation offset in DPRAM [SCC4]
  1621. - CFG_USE_OSCCLK:
  1622. Use OSCM clock mode on MBX8xx board. Be careful,
  1623. wrong setting might damage your board. Read
  1624. doc/README.MBX before setting this variable!
  1625. - CFG_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
  1626. Offset of the bootmode word in DPRAM used by post
  1627. (Power On Self Tests). This definition overrides
  1628. #define'd default value in commproc.h resp.
  1629. cpm_8260.h.
  1630. - CFG_PCI_SLV_MEM_LOCAL, CFG_PCI_SLV_MEM_BUS, CFG_PICMR0_MASK_ATTRIB,
  1631. CFG_PCI_MSTR0_LOCAL, CFG_PCIMSK0_MASK, CFG_PCI_MSTR1_LOCAL,
  1632. CFG_PCIMSK1_MASK, CFG_PCI_MSTR_MEM_LOCAL, CFG_PCI_MSTR_MEM_BUS,
  1633. CFG_CPU_PCI_MEM_START, CFG_PCI_MSTR_MEM_SIZE, CFG_POCMR0_MASK_ATTRIB,
  1634. CFG_PCI_MSTR_MEMIO_LOCAL, CFG_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
  1635. CFG_PCI_MSTR_MEMIO_SIZE, CFG_POCMR1_MASK_ATTRIB, CFG_PCI_MSTR_IO_LOCAL,
  1636. CFG_PCI_MSTR_IO_BUS, CFG_CPU_PCI_IO_START, CFG_PCI_MSTR_IO_SIZE,
  1637. CFG_POCMR2_MASK_ATTRIB: (MPC826x only)
  1638. Overrides the default PCI memory map in cpu/mpc8260/pci.c if set.
  1639. - CONFIG_ETHER_ON_FEC[12]
  1640. Define to enable FEC[12] on a 8xx series processor.
  1641. - CONFIG_FEC[12]_PHY
  1642. Define to the hardcoded PHY address which corresponds
  1643. to the given FEC; i. e.
  1644. #define CONFIG_FEC1_PHY 4
  1645. means that the PHY with address 4 is connected to FEC1
  1646. When set to -1, means to probe for first available.
  1647. - CONFIG_FEC[12]_PHY_NORXERR
  1648. The PHY does not have a RXERR line (RMII only).
  1649. (so program the FEC to ignore it).
  1650. - CONFIG_RMII
  1651. Enable RMII mode for all FECs.
  1652. Note that this is a global option, we can't
  1653. have one FEC in standard MII mode and another in RMII mode.
  1654. - CONFIG_CRC32_VERIFY
  1655. Add a verify option to the crc32 command.
  1656. The syntax is:
  1657. => crc32 -v <address> <count> <crc32>
  1658. Where address/count indicate a memory area
  1659. and crc32 is the correct crc32 which the
  1660. area should have.
  1661. - CONFIG_LOOPW
  1662. Add the "loopw" memory command. This only takes effect if
  1663. the memory commands are activated globally (CFG_CMD_MEM).
  1664. - CONFIG_MX_CYCLIC
  1665. Add the "mdc" and "mwc" memory commands. These are cyclic
  1666. "md/mw" commands.
  1667. Examples:
  1668. => mdc.b 10 4 500
  1669. This command will print 4 bytes (10,11,12,13) each 500 ms.
  1670. => mwc.l 100 12345678 10
  1671. This command will write 12345678 to address 100 all 10 ms.
  1672. This only takes effect if the memory commands are activated
  1673. globally (CFG_CMD_MEM).
  1674. - CONFIG_SKIP_LOWLEVEL_INIT
  1675. - CONFIG_SKIP_RELOCATE_UBOOT
  1676. [ARM only] If these variables are defined, then
  1677. certain low level initializations (like setting up
  1678. the memory controller) are omitted and/or U-Boot does
  1679. not relocate itself into RAM.
  1680. Normally these variables MUST NOT be defined. The
  1681. only exception is when U-Boot is loaded (to RAM) by
  1682. some other boot loader or by a debugger which
  1683. performs these intializations itself.
  1684. Building the Software:
  1685. ======================
  1686. Building U-Boot has been tested in native PPC environments (on a
  1687. PowerBook G3 running LinuxPPC 2000) and in cross environments
  1688. (running RedHat 6.x and 7.x Linux on x86, Solaris 2.6 on a SPARC, and
  1689. NetBSD 1.5 on x86).
  1690. If you are not using a native PPC environment, it is assumed that you
  1691. have the GNU cross compiling tools available in your path and named
  1692. with a prefix of "powerpc-linux-". If this is not the case, (e.g. if
  1693. you are using Monta Vista's Hard Hat Linux CDK 1.2) you must change
  1694. the definition of CROSS_COMPILE in Makefile. For HHL on a 4xx CPU,
  1695. change it to:
  1696. CROSS_COMPILE = ppc_4xx-
  1697. U-Boot is intended to be simple to build. After installing the
  1698. sources you must configure U-Boot for one specific board type. This
  1699. is done by typing:
  1700. make NAME_config
  1701. where "NAME_config" is the name of one of the existing
  1702. configurations; the following names are supported:
  1703. ADCIOP_config FPS860L_config omap730p2_config
  1704. ADS860_config GEN860T_config pcu_e_config
  1705. Alaska8220_config
  1706. AR405_config GENIETV_config PIP405_config
  1707. at91rm9200dk_config GTH_config QS823_config
  1708. CANBT_config hermes_config QS850_config
  1709. cmi_mpc5xx_config hymod_config QS860T_config
  1710. cogent_common_config IP860_config RPXlite_config
  1711. cogent_mpc8260_config IVML24_config RPXlite_DW_config
  1712. cogent_mpc8xx_config IVMS8_config RPXsuper_config
  1713. CPCI405_config JSE_config rsdproto_config
  1714. CPCIISER4_config LANTEC_config Sandpoint8240_config
  1715. csb272_config lwmon_config sbc8260_config
  1716. CU824_config MBX860T_config sbc8560_33_config
  1717. DUET_ADS_config MBX_config sbc8560_66_config
  1718. EBONY_config MPC8260ADS_config SM850_config
  1719. ELPT860_config MPC8540ADS_config SPD823TS_config
  1720. ESTEEM192E_config MPC8540EVAL_config stxgp3_config
  1721. ETX094_config MPC8560ADS_config SXNI855T_config
  1722. FADS823_config NETVIA_config TQM823L_config
  1723. FADS850SAR_config omap1510inn_config TQM850L_config
  1724. FADS860T_config omap1610h2_config TQM855L_config
  1725. FPS850L_config omap1610inn_config TQM860L_config
  1726. omap5912osk_config walnut_config
  1727. omap2420h4_config Yukon8220_config
  1728. ZPC1900_config
  1729. Note: for some board special configuration names may exist; check if
  1730. additional information is available from the board vendor; for
  1731. instance, the TQM823L systems are available without (standard)
  1732. or with LCD support. You can select such additional "features"
  1733. when chosing the configuration, i. e.
  1734. make TQM823L_config
  1735. - will configure for a plain TQM823L, i. e. no LCD support
  1736. make TQM823L_LCD_config
  1737. - will configure for a TQM823L with U-Boot console on LCD
  1738. etc.
  1739. Finally, type "make all", and you should get some working U-Boot
  1740. images ready for download to / installation on your system:
  1741. - "u-boot.bin" is a raw binary image
  1742. - "u-boot" is an image in ELF binary format
  1743. - "u-boot.srec" is in Motorola S-Record format
  1744. Please be aware that the Makefiles assume you are using GNU make, so
  1745. for instance on NetBSD you might need to use "gmake" instead of
  1746. native "make".
  1747. If the system board that you have is not listed, then you will need
  1748. to port U-Boot to your hardware platform. To do this, follow these
  1749. steps:
  1750. 1. Add a new configuration option for your board to the toplevel
  1751. "Makefile" and to the "MAKEALL" script, using the existing
  1752. entries as examples. Note that here and at many other places
  1753. boards and other names are listed in alphabetical sort order. Please
  1754. keep this order.
  1755. 2. Create a new directory to hold your board specific code. Add any
  1756. files you need. In your board directory, you will need at least
  1757. the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
  1758. 3. Create a new configuration file "include/configs/<board>.h" for
  1759. your board
  1760. 3. If you're porting U-Boot to a new CPU, then also create a new
  1761. directory to hold your CPU specific code. Add any files you need.
  1762. 4. Run "make <board>_config" with your new name.
  1763. 5. Type "make", and you should get a working "u-boot.srec" file
  1764. to be installed on your target system.
  1765. 6. Debug and solve any problems that might arise.
  1766. [Of course, this last step is much harder than it sounds.]
  1767. Testing of U-Boot Modifications, Ports to New Hardware, etc.:
  1768. ==============================================================
  1769. If you have modified U-Boot sources (for instance added a new board
  1770. or support for new devices, a new CPU, etc.) you are expected to
  1771. provide feedback to the other developers. The feedback normally takes
  1772. the form of a "patch", i. e. a context diff against a certain (latest
  1773. official or latest in CVS) version of U-Boot sources.
  1774. But before you submit such a patch, please verify that your modifi-
  1775. cation did not break existing code. At least make sure that *ALL* of
  1776. the supported boards compile WITHOUT ANY compiler warnings. To do so,
  1777. just run the "MAKEALL" script, which will configure and build U-Boot
  1778. for ALL supported system. Be warned, this will take a while. You can
  1779. select which (cross) compiler to use by passing a `CROSS_COMPILE'
  1780. environment variable to the script, i. e. to use the cross tools from
  1781. MontaVista's Hard Hat Linux you can type
  1782. CROSS_COMPILE=ppc_8xx- MAKEALL
  1783. or to build on a native PowerPC system you can type
  1784. CROSS_COMPILE=' ' MAKEALL
  1785. See also "U-Boot Porting Guide" below.
  1786. Monitor Commands - Overview:
  1787. ============================
  1788. go - start application at address 'addr'
  1789. run - run commands in an environment variable
  1790. bootm - boot application image from memory
  1791. bootp - boot image via network using BootP/TFTP protocol
  1792. tftpboot- boot image via network using TFTP protocol
  1793. and env variables "ipaddr" and "serverip"
  1794. (and eventually "gatewayip")
  1795. rarpboot- boot image via network using RARP/TFTP protocol
  1796. diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
  1797. loads - load S-Record file over serial line
  1798. loadb - load binary file over serial line (kermit mode)
  1799. md - memory display
  1800. mm - memory modify (auto-incrementing)
  1801. nm - memory modify (constant address)
  1802. mw - memory write (fill)
  1803. cp - memory copy
  1804. cmp - memory compare
  1805. crc32 - checksum calculation
  1806. imd - i2c memory display
  1807. imm - i2c memory modify (auto-incrementing)
  1808. inm - i2c memory modify (constant address)
  1809. imw - i2c memory write (fill)
  1810. icrc32 - i2c checksum calculation
  1811. iprobe - probe to discover valid I2C chip addresses
  1812. iloop - infinite loop on address range
  1813. isdram - print SDRAM configuration information
  1814. sspi - SPI utility commands
  1815. base - print or set address offset
  1816. printenv- print environment variables
  1817. setenv - set environment variables
  1818. saveenv - save environment variables to persistent storage
  1819. protect - enable or disable FLASH write protection
  1820. erase - erase FLASH memory
  1821. flinfo - print FLASH memory information
  1822. bdinfo - print Board Info structure
  1823. iminfo - print header information for application image
  1824. coninfo - print console devices and informations
  1825. ide - IDE sub-system
  1826. loop - infinite loop on address range
  1827. loopw - infinite write loop on address range
  1828. mtest - simple RAM test
  1829. icache - enable or disable instruction cache
  1830. dcache - enable or disable data cache
  1831. reset - Perform RESET of the CPU
  1832. echo - echo args to console
  1833. version - print monitor version
  1834. help - print online help
  1835. ? - alias for 'help'
  1836. Monitor Commands - Detailed Description:
  1837. ========================================
  1838. TODO.
  1839. For now: just type "help <command>".
  1840. Environment Variables:
  1841. ======================
  1842. U-Boot supports user configuration using Environment Variables which
  1843. can be made persistent by saving to Flash memory.
  1844. Environment Variables are set using "setenv", printed using
  1845. "printenv", and saved to Flash using "saveenv". Using "setenv"
  1846. without a value can be used to delete a variable from the
  1847. environment. As long as you don't save the environment you are
  1848. working with an in-memory copy. In case the Flash area containing the
  1849. environment is erased by accident, a default environment is provided.
  1850. Some configuration options can be set using Environment Variables:
  1851. baudrate - see CONFIG_BAUDRATE
  1852. bootdelay - see CONFIG_BOOTDELAY
  1853. bootcmd - see CONFIG_BOOTCOMMAND
  1854. bootargs - Boot arguments when booting an RTOS image
  1855. bootfile - Name of the image to load with TFTP
  1856. autoload - if set to "no" (any string beginning with 'n'),
  1857. "bootp" will just load perform a lookup of the
  1858. configuration from the BOOTP server, but not try to
  1859. load any image using TFTP
  1860. autostart - if set to "yes", an image loaded using the "bootp",
  1861. "rarpboot", "tftpboot" or "diskboot" commands will
  1862. be automatically started (by internally calling
  1863. "bootm")
  1864. If set to "no", a standalone image passed to the
  1865. "bootm" command will be copied to the load address
  1866. (and eventually uncompressed), but NOT be started.
  1867. This can be used to load and uncompress arbitrary
  1868. data.
  1869. i2cfast - (PPC405GP|PPC405EP only)
  1870. if set to 'y' configures Linux I2C driver for fast
  1871. mode (400kHZ). This environment variable is used in
  1872. initialization code. So, for changes to be effective
  1873. it must be saved and board must be reset.
  1874. initrd_high - restrict positioning of initrd images:
  1875. If this variable is not set, initrd images will be
  1876. copied to the highest possible address in RAM; this
  1877. is usually what you want since it allows for
  1878. maximum initrd size. If for some reason you want to
  1879. make sure that the initrd image is loaded below the
  1880. CFG_BOOTMAPSZ limit, you can set this environment
  1881. variable to a value of "no" or "off" or "0".
  1882. Alternatively, you can set it to a maximum upper
  1883. address to use (U-Boot will still check that it
  1884. does not overwrite the U-Boot stack and data).
  1885. For instance, when you have a system with 16 MB
  1886. RAM, and want to reserve 4 MB from use by Linux,
  1887. you can do this by adding "mem=12M" to the value of
  1888. the "bootargs" variable. However, now you must make
  1889. sure that the initrd image is placed in the first
  1890. 12 MB as well - this can be done with
  1891. setenv initrd_high 00c00000
  1892. If you set initrd_high to 0xFFFFFFFF, this is an
  1893. indication to U-Boot that all addresses are legal
  1894. for the Linux kernel, including addresses in flash
  1895. memory. In this case U-Boot will NOT COPY the
  1896. ramdisk at all. This may be useful to reduce the
  1897. boot time on your system, but requires that this
  1898. feature is supported by your Linux kernel.
  1899. ipaddr - IP address; needed for tftpboot command
  1900. loadaddr - Default load address for commands like "bootp",
  1901. "rarpboot", "tftpboot", "loadb" or "diskboot"
  1902. loads_echo - see CONFIG_LOADS_ECHO
  1903. serverip - TFTP server IP address; needed for tftpboot command
  1904. bootretry - see CONFIG_BOOT_RETRY_TIME
  1905. bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
  1906. bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
  1907. ethprime - When CONFIG_NET_MULTI is enabled controls which
  1908. interface is used first.
  1909. ethact - When CONFIG_NET_MULTI is enabled controls which
  1910. interface is currently active. For example you
  1911. can do the following
  1912. => setenv ethact FEC ETHERNET
  1913. => ping 192.168.0.1 # traffic sent on FEC ETHERNET
  1914. => setenv ethact SCC ETHERNET
  1915. => ping 10.0.0.1 # traffic sent on SCC ETHERNET
  1916. netretry - When set to "no" each network operation will
  1917. either succeed or fail without retrying.
  1918. When set to "once" the network operation will
  1919. fail when all the available network interfaces
  1920. are tried once without success.
  1921. Useful on scripts which control the retry operation
  1922. themselves.
  1923. tftpsrcport - If this is set, the value is used for TFTP's
  1924. UDP source port.
  1925. tftpdstport - If this is set, the value is used for TFTP's UDP
  1926. destination port instead of the Well Know Port 69.
  1927. vlan - When set to a value < 4095 the traffic over
  1928. ethernet is encapsulated/received over 802.1q
  1929. VLAN tagged frames.
  1930. The following environment variables may be used and automatically
  1931. updated by the network boot commands ("bootp" and "rarpboot"),
  1932. depending the information provided by your boot server:
  1933. bootfile - see above
  1934. dnsip - IP address of your Domain Name Server
  1935. dnsip2 - IP address of your secondary Domain Name Server
  1936. gatewayip - IP address of the Gateway (Router) to use
  1937. hostname - Target hostname
  1938. ipaddr - see above
  1939. netmask - Subnet Mask
  1940. rootpath - Pathname of the root filesystem on the NFS server
  1941. serverip - see above
  1942. There are two special Environment Variables:
  1943. serial# - contains hardware identification information such
  1944. as type string and/or serial number
  1945. ethaddr - Ethernet address
  1946. These variables can be set only once (usually during manufacturing of
  1947. the board). U-Boot refuses to delete or overwrite these variables
  1948. once they have been set once.
  1949. Further special Environment Variables:
  1950. ver - Contains the U-Boot version string as printed
  1951. with the "version" command. This variable is
  1952. readonly (see CONFIG_VERSION_VARIABLE).
  1953. Please note that changes to some configuration parameters may take
  1954. only effect after the next boot (yes, that's just like Windoze :-).
  1955. Command Line Parsing:
  1956. =====================
  1957. There are two different command line parsers available with U-Boot:
  1958. the old "simple" one, and the much more powerful "hush" shell:
  1959. Old, simple command line parser:
  1960. --------------------------------
  1961. - supports environment variables (through setenv / saveenv commands)
  1962. - several commands on one line, separated by ';'
  1963. - variable substitution using "... ${name} ..." syntax
  1964. - special characters ('$', ';') can be escaped by prefixing with '\',
  1965. for example:
  1966. setenv bootcmd bootm \${address}
  1967. - You can also escape text by enclosing in single apostrophes, for example:
  1968. setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
  1969. Hush shell:
  1970. -----------
  1971. - similar to Bourne shell, with control structures like
  1972. if...then...else...fi, for...do...done; while...do...done,
  1973. until...do...done, ...
  1974. - supports environment ("global") variables (through setenv / saveenv
  1975. commands) and local shell variables (through standard shell syntax
  1976. "name=value"); only environment variables can be used with "run"
  1977. command
  1978. General rules:
  1979. --------------
  1980. (1) If a command line (or an environment variable executed by a "run"
  1981. command) contains several commands separated by semicolon, and
  1982. one of these commands fails, then the remaining commands will be
  1983. executed anyway.
  1984. (2) If you execute several variables with one call to run (i. e.
  1985. calling run with a list af variables as arguments), any failing
  1986. command will cause "run" to terminate, i. e. the remaining
  1987. variables are not executed.
  1988. Note for Redundant Ethernet Interfaces:
  1989. =======================================
  1990. Some boards come with redundant ethernet interfaces; U-Boot supports
  1991. such configurations and is capable of automatic selection of a
  1992. "working" interface when needed. MAC assignment works as follows:
  1993. Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
  1994. MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
  1995. "eth1addr" (=>eth1), "eth2addr", ...
  1996. If the network interface stores some valid MAC address (for instance
  1997. in SROM), this is used as default address if there is NO correspon-
  1998. ding setting in the environment; if the corresponding environment
  1999. variable is set, this overrides the settings in the card; that means:
  2000. o If the SROM has a valid MAC address, and there is no address in the
  2001. environment, the SROM's address is used.
  2002. o If there is no valid address in the SROM, and a definition in the
  2003. environment exists, then the value from the environment variable is
  2004. used.
  2005. o If both the SROM and the environment contain a MAC address, and
  2006. both addresses are the same, this MAC address is used.
  2007. o If both the SROM and the environment contain a MAC address, and the
  2008. addresses differ, the value from the environment is used and a
  2009. warning is printed.
  2010. o If neither SROM nor the environment contain a MAC address, an error
  2011. is raised.
  2012. Image Formats:
  2013. ==============
  2014. The "boot" commands of this monitor operate on "image" files which
  2015. can be basicly anything, preceeded by a special header; see the
  2016. definitions in include/image.h for details; basicly, the header
  2017. defines the following image properties:
  2018. * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
  2019. 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
  2020. LynxOS, pSOS, QNX, RTEMS, ARTOS;
  2021. Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS).
  2022. * Target CPU Architecture (Provisions for Alpha, ARM, Intel x86,
  2023. IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
  2024. Currently supported: ARM, Intel x86, MIPS, NIOS, PowerPC).
  2025. * Compression Type (uncompressed, gzip, bzip2)
  2026. * Load Address
  2027. * Entry Point
  2028. * Image Name
  2029. * Image Timestamp
  2030. The header is marked by a special Magic Number, and both the header
  2031. and the data portions of the image are secured against corruption by
  2032. CRC32 checksums.
  2033. Linux Support:
  2034. ==============
  2035. Although U-Boot should support any OS or standalone application
  2036. easily, the main focus has always been on Linux during the design of
  2037. U-Boot.
  2038. U-Boot includes many features that so far have been part of some
  2039. special "boot loader" code within the Linux kernel. Also, any
  2040. "initrd" images to be used are no longer part of one big Linux image;
  2041. instead, kernel and "initrd" are separate images. This implementation
  2042. serves several purposes:
  2043. - the same features can be used for other OS or standalone
  2044. applications (for instance: using compressed images to reduce the
  2045. Flash memory footprint)
  2046. - it becomes much easier to port new Linux kernel versions because
  2047. lots of low-level, hardware dependent stuff are done by U-Boot
  2048. - the same Linux kernel image can now be used with different "initrd"
  2049. images; of course this also means that different kernel images can
  2050. be run with the same "initrd". This makes testing easier (you don't
  2051. have to build a new "zImage.initrd" Linux image when you just
  2052. change a file in your "initrd"). Also, a field-upgrade of the
  2053. software is easier now.
  2054. Linux HOWTO:
  2055. ============
  2056. Porting Linux to U-Boot based systems:
  2057. ---------------------------------------
  2058. U-Boot cannot save you from doing all the necessary modifications to
  2059. configure the Linux device drivers for use with your target hardware
  2060. (no, we don't intend to provide a full virtual machine interface to
  2061. Linux :-).
  2062. But now you can ignore ALL boot loader code (in arch/ppc/mbxboot).
  2063. Just make sure your machine specific header file (for instance
  2064. include/asm-ppc/tqm8xx.h) includes the same definition of the Board
  2065. Information structure as we define in include/u-boot.h, and make
  2066. sure that your definition of IMAP_ADDR uses the same value as your
  2067. U-Boot configuration in CFG_IMMR.
  2068. Configuring the Linux kernel:
  2069. -----------------------------
  2070. No specific requirements for U-Boot. Make sure you have some root
  2071. device (initial ramdisk, NFS) for your target system.
  2072. Building a Linux Image:
  2073. -----------------------
  2074. With U-Boot, "normal" build targets like "zImage" or "bzImage" are
  2075. not used. If you use recent kernel source, a new build target
  2076. "uImage" will exist which automatically builds an image usable by
  2077. U-Boot. Most older kernels also have support for a "pImage" target,
  2078. which was introduced for our predecessor project PPCBoot and uses a
  2079. 100% compatible format.
  2080. Example:
  2081. make TQM850L_config
  2082. make oldconfig
  2083. make dep
  2084. make uImage
  2085. The "uImage" build target uses a special tool (in 'tools/mkimage') to
  2086. encapsulate a compressed Linux kernel image with header information,
  2087. CRC32 checksum etc. for use with U-Boot. This is what we are doing:
  2088. * build a standard "vmlinux" kernel image (in ELF binary format):
  2089. * convert the kernel into a raw binary image:
  2090. ${CROSS_COMPILE}-objcopy -O binary \
  2091. -R .note -R .comment \
  2092. -S vmlinux linux.bin
  2093. * compress the binary image:
  2094. gzip -9 linux.bin
  2095. * package compressed binary image for U-Boot:
  2096. mkimage -A ppc -O linux -T kernel -C gzip \
  2097. -a 0 -e 0 -n "Linux Kernel Image" \
  2098. -d linux.bin.gz uImage
  2099. The "mkimage" tool can also be used to create ramdisk images for use
  2100. with U-Boot, either separated from the Linux kernel image, or
  2101. combined into one file. "mkimage" encapsulates the images with a 64
  2102. byte header containing information about target architecture,
  2103. operating system, image type, compression method, entry points, time
  2104. stamp, CRC32 checksums, etc.
  2105. "mkimage" can be called in two ways: to verify existing images and
  2106. print the header information, or to build new images.
  2107. In the first form (with "-l" option) mkimage lists the information
  2108. contained in the header of an existing U-Boot image; this includes
  2109. checksum verification:
  2110. tools/mkimage -l image
  2111. -l ==> list image header information
  2112. The second form (with "-d" option) is used to build a U-Boot image
  2113. from a "data file" which is used as image payload:
  2114. tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
  2115. -n name -d data_file image
  2116. -A ==> set architecture to 'arch'
  2117. -O ==> set operating system to 'os'
  2118. -T ==> set image type to 'type'
  2119. -C ==> set compression type 'comp'
  2120. -a ==> set load address to 'addr' (hex)
  2121. -e ==> set entry point to 'ep' (hex)
  2122. -n ==> set image name to 'name'
  2123. -d ==> use image data from 'datafile'
  2124. Right now, all Linux kernels for PowerPC systems use the same load
  2125. address (0x00000000), but the entry point address depends on the
  2126. kernel version:
  2127. - 2.2.x kernels have the entry point at 0x0000000C,
  2128. - 2.3.x and later kernels have the entry point at 0x00000000.
  2129. So a typical call to build a U-Boot image would read:
  2130. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2131. > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
  2132. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz \
  2133. > examples/uImage.TQM850L
  2134. Image Name: 2.4.4 kernel for TQM850L
  2135. Created: Wed Jul 19 02:34:59 2000
  2136. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2137. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2138. Load Address: 0x00000000
  2139. Entry Point: 0x00000000
  2140. To verify the contents of the image (or check for corruption):
  2141. -> tools/mkimage -l examples/uImage.TQM850L
  2142. Image Name: 2.4.4 kernel for TQM850L
  2143. Created: Wed Jul 19 02:34:59 2000
  2144. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2145. Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
  2146. Load Address: 0x00000000
  2147. Entry Point: 0x00000000
  2148. NOTE: for embedded systems where boot time is critical you can trade
  2149. speed for memory and install an UNCOMPRESSED image instead: this
  2150. needs more space in Flash, but boots much faster since it does not
  2151. need to be uncompressed:
  2152. -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz
  2153. -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
  2154. > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
  2155. > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux \
  2156. > examples/uImage.TQM850L-uncompressed
  2157. Image Name: 2.4.4 kernel for TQM850L
  2158. Created: Wed Jul 19 02:34:59 2000
  2159. Image Type: PowerPC Linux Kernel Image (uncompressed)
  2160. Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
  2161. Load Address: 0x00000000
  2162. Entry Point: 0x00000000
  2163. Similar you can build U-Boot images from a 'ramdisk.image.gz' file
  2164. when your kernel is intended to use an initial ramdisk:
  2165. -> tools/mkimage -n 'Simple Ramdisk Image' \
  2166. > -A ppc -O linux -T ramdisk -C gzip \
  2167. > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
  2168. Image Name: Simple Ramdisk Image
  2169. Created: Wed Jan 12 14:01:50 2000
  2170. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2171. Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
  2172. Load Address: 0x00000000
  2173. Entry Point: 0x00000000
  2174. Installing a Linux Image:
  2175. -------------------------
  2176. To downloading a U-Boot image over the serial (console) interface,
  2177. you must convert the image to S-Record format:
  2178. objcopy -I binary -O srec examples/image examples/image.srec
  2179. The 'objcopy' does not understand the information in the U-Boot
  2180. image header, so the resulting S-Record file will be relative to
  2181. address 0x00000000. To load it to a given address, you need to
  2182. specify the target address as 'offset' parameter with the 'loads'
  2183. command.
  2184. Example: install the image to address 0x40100000 (which on the
  2185. TQM8xxL is in the first Flash bank):
  2186. => erase 40100000 401FFFFF
  2187. .......... done
  2188. Erased 8 sectors
  2189. => loads 40100000
  2190. ## Ready for S-Record download ...
  2191. ~>examples/image.srec
  2192. 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
  2193. ...
  2194. 15989 15990 15991 15992
  2195. [file transfer complete]
  2196. [connected]
  2197. ## Start Addr = 0x00000000
  2198. You can check the success of the download using the 'iminfo' command;
  2199. this includes a checksum verification so you can be sure no data
  2200. corruption happened:
  2201. => imi 40100000
  2202. ## Checking Image at 40100000 ...
  2203. Image Name: 2.2.13 for initrd on TQM850L
  2204. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2205. Data Size: 335725 Bytes = 327 kB = 0 MB
  2206. Load Address: 00000000
  2207. Entry Point: 0000000c
  2208. Verifying Checksum ... OK
  2209. Boot Linux:
  2210. -----------
  2211. The "bootm" command is used to boot an application that is stored in
  2212. memory (RAM or Flash). In case of a Linux kernel image, the contents
  2213. of the "bootargs" environment variable is passed to the kernel as
  2214. parameters. You can check and modify this variable using the
  2215. "printenv" and "setenv" commands:
  2216. => printenv bootargs
  2217. bootargs=root=/dev/ram
  2218. => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2219. => printenv bootargs
  2220. bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2221. => bootm 40020000
  2222. ## Booting Linux kernel at 40020000 ...
  2223. Image Name: 2.2.13 for NFS on TQM850L
  2224. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2225. Data Size: 381681 Bytes = 372 kB = 0 MB
  2226. Load Address: 00000000
  2227. Entry Point: 0000000c
  2228. Verifying Checksum ... OK
  2229. Uncompressing Kernel Image ... OK
  2230. 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
  2231. Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
  2232. time_init: decrementer frequency = 187500000/60
  2233. Calibrating delay loop... 49.77 BogoMIPS
  2234. Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
  2235. ...
  2236. If you want to boot a Linux kernel with initial ram disk, you pass
  2237. the memory addresses of both the kernel and the initrd image (PPBCOOT
  2238. format!) to the "bootm" command:
  2239. => imi 40100000 40200000
  2240. ## Checking Image at 40100000 ...
  2241. Image Name: 2.2.13 for initrd on TQM850L
  2242. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2243. Data Size: 335725 Bytes = 327 kB = 0 MB
  2244. Load Address: 00000000
  2245. Entry Point: 0000000c
  2246. Verifying Checksum ... OK
  2247. ## Checking Image at 40200000 ...
  2248. Image Name: Simple Ramdisk Image
  2249. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2250. Data Size: 566530 Bytes = 553 kB = 0 MB
  2251. Load Address: 00000000
  2252. Entry Point: 00000000
  2253. Verifying Checksum ... OK
  2254. => bootm 40100000 40200000
  2255. ## Booting Linux kernel at 40100000 ...
  2256. Image Name: 2.2.13 for initrd on TQM850L
  2257. Image Type: PowerPC Linux Kernel Image (gzip compressed)
  2258. Data Size: 335725 Bytes = 327 kB = 0 MB
  2259. Load Address: 00000000
  2260. Entry Point: 0000000c
  2261. Verifying Checksum ... OK
  2262. Uncompressing Kernel Image ... OK
  2263. ## Loading RAMDisk Image at 40200000 ...
  2264. Image Name: Simple Ramdisk Image
  2265. Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
  2266. Data Size: 566530 Bytes = 553 kB = 0 MB
  2267. Load Address: 00000000
  2268. Entry Point: 00000000
  2269. Verifying Checksum ... OK
  2270. Loading Ramdisk ... OK
  2271. 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
  2272. Boot arguments: root=/dev/ram
  2273. time_init: decrementer frequency = 187500000/60
  2274. Calibrating delay loop... 49.77 BogoMIPS
  2275. ...
  2276. RAMDISK: Compressed image found at block 0
  2277. VFS: Mounted root (ext2 filesystem).
  2278. bash#
  2279. More About U-Boot Image Types:
  2280. ------------------------------
  2281. U-Boot supports the following image types:
  2282. "Standalone Programs" are directly runnable in the environment
  2283. provided by U-Boot; it is expected that (if they behave
  2284. well) you can continue to work in U-Boot after return from
  2285. the Standalone Program.
  2286. "OS Kernel Images" are usually images of some Embedded OS which
  2287. will take over control completely. Usually these programs
  2288. will install their own set of exception handlers, device
  2289. drivers, set up the MMU, etc. - this means, that you cannot
  2290. expect to re-enter U-Boot except by resetting the CPU.
  2291. "RAMDisk Images" are more or less just data blocks, and their
  2292. parameters (address, size) are passed to an OS kernel that is
  2293. being started.
  2294. "Multi-File Images" contain several images, typically an OS
  2295. (Linux) kernel image and one or more data images like
  2296. RAMDisks. This construct is useful for instance when you want
  2297. to boot over the network using BOOTP etc., where the boot
  2298. server provides just a single image file, but you want to get
  2299. for instance an OS kernel and a RAMDisk image.
  2300. "Multi-File Images" start with a list of image sizes, each
  2301. image size (in bytes) specified by an "uint32_t" in network
  2302. byte order. This list is terminated by an "(uint32_t)0".
  2303. Immediately after the terminating 0 follow the images, one by
  2304. one, all aligned on "uint32_t" boundaries (size rounded up to
  2305. a multiple of 4 bytes).
  2306. "Firmware Images" are binary images containing firmware (like
  2307. U-Boot or FPGA images) which usually will be programmed to
  2308. flash memory.
  2309. "Script files" are command sequences that will be executed by
  2310. U-Boot's command interpreter; this feature is especially
  2311. useful when you configure U-Boot to use a real shell (hush)
  2312. as command interpreter.
  2313. Standalone HOWTO:
  2314. =================
  2315. One of the features of U-Boot is that you can dynamically load and
  2316. run "standalone" applications, which can use some resources of
  2317. U-Boot like console I/O functions or interrupt services.
  2318. Two simple examples are included with the sources:
  2319. "Hello World" Demo:
  2320. -------------------
  2321. 'examples/hello_world.c' contains a small "Hello World" Demo
  2322. application; it is automatically compiled when you build U-Boot.
  2323. It's configured to run at address 0x00040004, so you can play with it
  2324. like that:
  2325. => loads
  2326. ## Ready for S-Record download ...
  2327. ~>examples/hello_world.srec
  2328. 1 2 3 4 5 6 7 8 9 10 11 ...
  2329. [file transfer complete]
  2330. [connected]
  2331. ## Start Addr = 0x00040004
  2332. => go 40004 Hello World! This is a test.
  2333. ## Starting application at 0x00040004 ...
  2334. Hello World
  2335. argc = 7
  2336. argv[0] = "40004"
  2337. argv[1] = "Hello"
  2338. argv[2] = "World!"
  2339. argv[3] = "This"
  2340. argv[4] = "is"
  2341. argv[5] = "a"
  2342. argv[6] = "test."
  2343. argv[7] = "<NULL>"
  2344. Hit any key to exit ...
  2345. ## Application terminated, rc = 0x0
  2346. Another example, which demonstrates how to register a CPM interrupt
  2347. handler with the U-Boot code, can be found in 'examples/timer.c'.
  2348. Here, a CPM timer is set up to generate an interrupt every second.
  2349. The interrupt service routine is trivial, just printing a '.'
  2350. character, but this is just a demo program. The application can be
  2351. controlled by the following keys:
  2352. ? - print current values og the CPM Timer registers
  2353. b - enable interrupts and start timer
  2354. e - stop timer and disable interrupts
  2355. q - quit application
  2356. => loads
  2357. ## Ready for S-Record download ...
  2358. ~>examples/timer.srec
  2359. 1 2 3 4 5 6 7 8 9 10 11 ...
  2360. [file transfer complete]
  2361. [connected]
  2362. ## Start Addr = 0x00040004
  2363. => go 40004
  2364. ## Starting application at 0x00040004 ...
  2365. TIMERS=0xfff00980
  2366. Using timer 1
  2367. tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
  2368. Hit 'b':
  2369. [q, b, e, ?] Set interval 1000000 us
  2370. Enabling timer
  2371. Hit '?':
  2372. [q, b, e, ?] ........
  2373. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
  2374. Hit '?':
  2375. [q, b, e, ?] .
  2376. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
  2377. Hit '?':
  2378. [q, b, e, ?] .
  2379. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
  2380. Hit '?':
  2381. [q, b, e, ?] .
  2382. tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
  2383. Hit 'e':
  2384. [q, b, e, ?] ...Stopping timer
  2385. Hit 'q':
  2386. [q, b, e, ?] ## Application terminated, rc = 0x0
  2387. Minicom warning:
  2388. ================
  2389. Over time, many people have reported problems when trying to use the
  2390. "minicom" terminal emulation program for serial download. I (wd)
  2391. consider minicom to be broken, and recommend not to use it. Under
  2392. Unix, I recommend to use C-Kermit for general purpose use (and
  2393. especially for kermit binary protocol download ("loadb" command), and
  2394. use "cu" for S-Record download ("loads" command).
  2395. Nevertheless, if you absolutely want to use it try adding this
  2396. configuration to your "File transfer protocols" section:
  2397. Name Program Name U/D FullScr IO-Red. Multi
  2398. X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
  2399. Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
  2400. NetBSD Notes:
  2401. =============
  2402. Starting at version 0.9.2, U-Boot supports NetBSD both as host
  2403. (build U-Boot) and target system (boots NetBSD/mpc8xx).
  2404. Building requires a cross environment; it is known to work on
  2405. NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
  2406. need gmake since the Makefiles are not compatible with BSD make).
  2407. Note that the cross-powerpc package does not install include files;
  2408. attempting to build U-Boot will fail because <machine/ansi.h> is
  2409. missing. This file has to be installed and patched manually:
  2410. # cd /usr/pkg/cross/powerpc-netbsd/include
  2411. # mkdir powerpc
  2412. # ln -s powerpc machine
  2413. # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
  2414. # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
  2415. Native builds *don't* work due to incompatibilities between native
  2416. and U-Boot include files.
  2417. Booting assumes that (the first part of) the image booted is a
  2418. stage-2 loader which in turn loads and then invokes the kernel
  2419. proper. Loader sources will eventually appear in the NetBSD source
  2420. tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
  2421. meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
  2422. Implementation Internals:
  2423. =========================
  2424. The following is not intended to be a complete description of every
  2425. implementation detail. However, it should help to understand the
  2426. inner workings of U-Boot and make it easier to port it to custom
  2427. hardware.
  2428. Initial Stack, Global Data:
  2429. ---------------------------
  2430. The implementation of U-Boot is complicated by the fact that U-Boot
  2431. starts running out of ROM (flash memory), usually without access to
  2432. system RAM (because the memory controller is not initialized yet).
  2433. This means that we don't have writable Data or BSS segments, and BSS
  2434. is not initialized as zero. To be able to get a C environment working
  2435. at all, we have to allocate at least a minimal stack. Implementation
  2436. options for this are defined and restricted by the CPU used: Some CPU
  2437. models provide on-chip memory (like the IMMR area on MPC8xx and
  2438. MPC826x processors), on others (parts of) the data cache can be
  2439. locked as (mis-) used as memory, etc.
  2440. Chris Hallinan posted a good summary of these issues to the
  2441. u-boot-users mailing list:
  2442. Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
  2443. From: "Chris Hallinan" <clh@net1plus.com>
  2444. Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
  2445. ...
  2446. Correct me if I'm wrong, folks, but the way I understand it
  2447. is this: Using DCACHE as initial RAM for Stack, etc, does not
  2448. require any physical RAM backing up the cache. The cleverness
  2449. is that the cache is being used as a temporary supply of
  2450. necessary storage before the SDRAM controller is setup. It's
  2451. beyond the scope of this list to expain the details, but you
  2452. can see how this works by studying the cache architecture and
  2453. operation in the architecture and processor-specific manuals.
  2454. OCM is On Chip Memory, which I believe the 405GP has 4K. It
  2455. is another option for the system designer to use as an
  2456. initial stack/ram area prior to SDRAM being available. Either
  2457. option should work for you. Using CS 4 should be fine if your
  2458. board designers haven't used it for something that would
  2459. cause you grief during the initial boot! It is frequently not
  2460. used.
  2461. CFG_INIT_RAM_ADDR should be somewhere that won't interfere
  2462. with your processor/board/system design. The default value
  2463. you will find in any recent u-boot distribution in
  2464. walnut.h should work for you. I'd set it to a value larger
  2465. than your SDRAM module. If you have a 64MB SDRAM module, set
  2466. it above 400_0000. Just make sure your board has no resources
  2467. that are supposed to respond to that address! That code in
  2468. start.S has been around a while and should work as is when
  2469. you get the config right.
  2470. -Chris Hallinan
  2471. DS4.COM, Inc.
  2472. It is essential to remember this, since it has some impact on the C
  2473. code for the initialization procedures:
  2474. * Initialized global data (data segment) is read-only. Do not attempt
  2475. to write it.
  2476. * Do not use any unitialized global data (or implicitely initialized
  2477. as zero data - BSS segment) at all - this is undefined, initiali-
  2478. zation is performed later (when relocating to RAM).
  2479. * Stack space is very limited. Avoid big data buffers or things like
  2480. that.
  2481. Having only the stack as writable memory limits means we cannot use
  2482. normal global data to share information beween the code. But it
  2483. turned out that the implementation of U-Boot can be greatly
  2484. simplified by making a global data structure (gd_t) available to all
  2485. functions. We could pass a pointer to this data as argument to _all_
  2486. functions, but this would bloat the code. Instead we use a feature of
  2487. the GCC compiler (Global Register Variables) to share the data: we
  2488. place a pointer (gd) to the global data into a register which we
  2489. reserve for this purpose.
  2490. When choosing a register for such a purpose we are restricted by the
  2491. relevant (E)ABI specifications for the current architecture, and by
  2492. GCC's implementation.
  2493. For PowerPC, the following registers have specific use:
  2494. R1: stack pointer
  2495. R2: TOC pointer
  2496. R3-R4: parameter passing and return values
  2497. R5-R10: parameter passing
  2498. R13: small data area pointer
  2499. R30: GOT pointer
  2500. R31: frame pointer
  2501. (U-Boot also uses R14 as internal GOT pointer.)
  2502. ==> U-Boot will use R29 to hold a pointer to the global data
  2503. Note: on PPC, we could use a static initializer (since the
  2504. address of the global data structure is known at compile time),
  2505. but it turned out that reserving a register results in somewhat
  2506. smaller code - although the code savings are not that big (on
  2507. average for all boards 752 bytes for the whole U-Boot image,
  2508. 624 text + 127 data).
  2509. On ARM, the following registers are used:
  2510. R0: function argument word/integer result
  2511. R1-R3: function argument word
  2512. R9: GOT pointer
  2513. R10: stack limit (used only if stack checking if enabled)
  2514. R11: argument (frame) pointer
  2515. R12: temporary workspace
  2516. R13: stack pointer
  2517. R14: link register
  2518. R15: program counter
  2519. ==> U-Boot will use R8 to hold a pointer to the global data
  2520. Memory Management:
  2521. ------------------
  2522. U-Boot runs in system state and uses physical addresses, i.e. the
  2523. MMU is not used either for address mapping nor for memory protection.
  2524. The available memory is mapped to fixed addresses using the memory
  2525. controller. In this process, a contiguous block is formed for each
  2526. memory type (Flash, SDRAM, SRAM), even when it consists of several
  2527. physical memory banks.
  2528. U-Boot is installed in the first 128 kB of the first Flash bank (on
  2529. TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
  2530. booting and sizing and initializing DRAM, the code relocates itself
  2531. to the upper end of DRAM. Immediately below the U-Boot code some
  2532. memory is reserved for use by malloc() [see CFG_MALLOC_LEN
  2533. configuration setting]. Below that, a structure with global Board
  2534. Info data is placed, followed by the stack (growing downward).
  2535. Additionally, some exception handler code is copied to the low 8 kB
  2536. of DRAM (0x00000000 ... 0x00001FFF).
  2537. So a typical memory configuration with 16 MB of DRAM could look like
  2538. this:
  2539. 0x0000 0000 Exception Vector code
  2540. :
  2541. 0x0000 1FFF
  2542. 0x0000 2000 Free for Application Use
  2543. :
  2544. :
  2545. :
  2546. :
  2547. 0x00FB FF20 Monitor Stack (Growing downward)
  2548. 0x00FB FFAC Board Info Data and permanent copy of global data
  2549. 0x00FC 0000 Malloc Arena
  2550. :
  2551. 0x00FD FFFF
  2552. 0x00FE 0000 RAM Copy of Monitor Code
  2553. ... eventually: LCD or video framebuffer
  2554. ... eventually: pRAM (Protected RAM - unchanged by reset)
  2555. 0x00FF FFFF [End of RAM]
  2556. System Initialization:
  2557. ----------------------
  2558. In the reset configuration, U-Boot starts at the reset entry point
  2559. (on most PowerPC systens at address 0x00000100). Because of the reset
  2560. configuration for CS0# this is a mirror of the onboard Flash memory.
  2561. To be able to re-map memory U-Boot then jumps to its link address.
  2562. To be able to implement the initialization code in C, a (small!)
  2563. initial stack is set up in the internal Dual Ported RAM (in case CPUs
  2564. which provide such a feature like MPC8xx or MPC8260), or in a locked
  2565. part of the data cache. After that, U-Boot initializes the CPU core,
  2566. the caches and the SIU.
  2567. Next, all (potentially) available memory banks are mapped using a
  2568. preliminary mapping. For example, we put them on 512 MB boundaries
  2569. (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
  2570. on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
  2571. programmed for SDRAM access. Using the temporary configuration, a
  2572. simple memory test is run that determines the size of the SDRAM
  2573. banks.
  2574. When there is more than one SDRAM bank, and the banks are of
  2575. different size, the largest is mapped first. For equal size, the first
  2576. bank (CS2#) is mapped first. The first mapping is always for address
  2577. 0x00000000, with any additional banks following immediately to create
  2578. contiguous memory starting from 0.
  2579. Then, the monitor installs itself at the upper end of the SDRAM area
  2580. and allocates memory for use by malloc() and for the global Board
  2581. Info data; also, the exception vector code is copied to the low RAM
  2582. pages, and the final stack is set up.
  2583. Only after this relocation will you have a "normal" C environment;
  2584. until that you are restricted in several ways, mostly because you are
  2585. running from ROM, and because the code will have to be relocated to a
  2586. new address in RAM.
  2587. U-Boot Porting Guide:
  2588. ----------------------
  2589. [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
  2590. list, October 2002]
  2591. int main (int argc, char *argv[])
  2592. {
  2593. sighandler_t no_more_time;
  2594. signal (SIGALRM, no_more_time);
  2595. alarm (PROJECT_DEADLINE - toSec (3 * WEEK));
  2596. if (available_money > available_manpower) {
  2597. pay consultant to port U-Boot;
  2598. return 0;
  2599. }
  2600. Download latest U-Boot source;
  2601. Subscribe to u-boot-users mailing list;
  2602. if (clueless) {
  2603. email ("Hi, I am new to U-Boot, how do I get started?");
  2604. }
  2605. while (learning) {
  2606. Read the README file in the top level directory;
  2607. Read http://www.denx.de/twiki/bin/view/DULG/Manual ;
  2608. Read the source, Luke;
  2609. }
  2610. if (available_money > toLocalCurrency ($2500)) {
  2611. Buy a BDI2000;
  2612. } else {
  2613. Add a lot of aggravation and time;
  2614. }
  2615. Create your own board support subdirectory;
  2616. Create your own board config file;
  2617. while (!running) {
  2618. do {
  2619. Add / modify source code;
  2620. } until (compiles);
  2621. Debug;
  2622. if (clueless)
  2623. email ("Hi, I am having problems...");
  2624. }
  2625. Send patch file to Wolfgang;
  2626. return 0;
  2627. }
  2628. void no_more_time (int sig)
  2629. {
  2630. hire_a_guru();
  2631. }
  2632. Coding Standards:
  2633. -----------------
  2634. All contributions to U-Boot should conform to the Linux kernel
  2635. coding style; see the file "Documentation/CodingStyle" in your Linux
  2636. kernel source directory.
  2637. Please note that U-Boot is implemented in C (and to some small parts
  2638. in Assembler); no C++ is used, so please do not use C++ style
  2639. comments (//) in your code.
  2640. Please also stick to the following formatting rules:
  2641. - remove any trailing white space
  2642. - use TAB characters for indentation, not spaces
  2643. - make sure NOT to use DOS '\r\n' line feeds
  2644. - do not add more than 2 empty lines to source files
  2645. - do not add trailing empty lines to source files
  2646. Submissions which do not conform to the standards may be returned
  2647. with a request to reformat the changes.
  2648. Submitting Patches:
  2649. -------------------
  2650. Since the number of patches for U-Boot is growing, we need to
  2651. establish some rules. Submissions which do not conform to these rules
  2652. may be rejected, even when they contain important and valuable stuff.
  2653. Patches shall be sent to the u-boot-users mailing list.
  2654. When you send a patch, please include the following information with
  2655. it:
  2656. * For bug fixes: a description of the bug and how your patch fixes
  2657. this bug. Please try to include a way of demonstrating that the
  2658. patch actually fixes something.
  2659. * For new features: a description of the feature and your
  2660. implementation.
  2661. * A CHANGELOG entry as plaintext (separate from the patch)
  2662. * For major contributions, your entry to the CREDITS file
  2663. * When you add support for a new board, don't forget to add this
  2664. board to the MAKEALL script, too.
  2665. * If your patch adds new configuration options, don't forget to
  2666. document these in the README file.
  2667. * The patch itself. If you are accessing the CVS repository use "cvs
  2668. update; cvs diff -puRN"; else, use "diff -purN OLD NEW". If your
  2669. version of diff does not support these options, then get the latest
  2670. version of GNU diff.
  2671. The current directory when running this command shall be the top
  2672. level directory of the U-Boot source tree, or it's parent directory
  2673. (i. e. please make sure that your patch includes sufficient
  2674. directory information for the affected files).
  2675. We accept patches as plain text, MIME attachments or as uuencoded
  2676. gzipped text.
  2677. * If one logical set of modifications affects or creates several
  2678. files, all these changes shall be submitted in a SINGLE patch file.
  2679. * Changesets that contain different, unrelated modifications shall be
  2680. submitted as SEPARATE patches, one patch per changeset.
  2681. Notes:
  2682. * Before sending the patch, run the MAKEALL script on your patched
  2683. source tree and make sure that no errors or warnings are reported
  2684. for any of the boards.
  2685. * Keep your modifications to the necessary minimum: A patch
  2686. containing several unrelated changes or arbitrary reformats will be
  2687. returned with a request to re-formatting / split it.
  2688. * If you modify existing code, make sure that your new code does not
  2689. add to the memory footprint of the code ;-) Small is beautiful!
  2690. When adding new features, these should compile conditionally only
  2691. (using #ifdef), and the resulting code with the new feature
  2692. disabled must not need more memory than the old code without your
  2693. modification.
  2694. * Remember that there is a size limit of 40 kB per message on the
  2695. u-boot-users mailing list. Compression may help.