README 171 KB

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