README 189 KB

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