README.omap3 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204
  1. Summary
  2. =======
  3. This README is about U-Boot support for TI's ARM Cortex-A8 based OMAP3 [1]
  4. family of SoCs. TI's OMAP3 SoC family contains an ARM Cortex-A8. Additionally,
  5. some family members contain a TMS320C64x+ DSP and/or an Imagination SGX 2D/3D
  6. graphics processor and various other standard peripherals.
  7. Currently the following boards are supported:
  8. * OMAP3530 BeagleBoard [2]
  9. * Gumstix Overo [3]
  10. * TI EVM [4]
  11. * OpenPandora Ltd. Pandora [5]
  12. * TI/Logic PD Zoom MDK [6]
  13. * TI/Logic PD Zoom 2 [7]
  14. * CompuLab Ltd. CM-T35 [8]
  15. Build
  16. =====
  17. * BeagleBoard:
  18. make omap3_beagle_config
  19. make
  20. * Gumstix Overo:
  21. make omap3_overo_config
  22. make
  23. * TI EVM:
  24. make omap3_evm_config
  25. make
  26. * Zoom MDK:
  27. make omap3_zoom1_config
  28. make
  29. * Zoom 2:
  30. make omap3_zoom2_config
  31. make
  32. * CM-T35:
  33. make cm_t35_config
  34. make
  35. Custom commands
  36. ===============
  37. To make U-Boot for OMAP3 support NAND device SW or HW ECC calculation, U-Boot
  38. for OMAP3 supports custom user command
  39. nandecc hw/sw
  40. To be compatible with NAND drivers using SW ECC (e.g. kernel code)
  41. nandecc sw
  42. enables SW ECC calculation. HW ECC enabled with
  43. nandecc hw
  44. is typically used to write 2nd stage bootloader (known as 'x-loader') which is
  45. executed by OMAP3's boot rom and therefore has to be written with HW ECC.
  46. For all other commands see
  47. help
  48. Interfaces
  49. ==========
  50. gpio
  51. ----
  52. To set a bit :
  53. if (!gpio_request(N, "")) {
  54. gpio_direction_output(N, 0);
  55. gpio_set_value(N, 1);
  56. }
  57. To clear a bit :
  58. if (!gpio_request(N, "")) {
  59. gpio_direction_output(N, 0);
  60. gpio_set_value(N, 0);
  61. }
  62. To read a bit :
  63. if (!gpio_request(N, "")) {
  64. gpio_direction_input(N);
  65. val = gpio_get_value(N);
  66. gpio_free(N);
  67. }
  68. if (val)
  69. printf("GPIO N is set\n");
  70. else
  71. printf("GPIO N is clear\n");
  72. dma
  73. ---
  74. void omap3_dma_init(void)
  75. Init the DMA module
  76. int omap3_dma_get_conf_chan(uint32_t chan, struct dma4_chan *config);
  77. Read config of the channel
  78. int omap3_dma_conf_chan(uint32_t chan, struct dma4_chan *config);
  79. Write config to the channel
  80. int omap3_dma_conf_transfer(uint32_t chan, uint32_t *src, uint32_t *dst,
  81. uint32_t sze)
  82. Config source, destination and size of a transfer
  83. int omap3_dma_wait_for_transfer(uint32_t chan)
  84. Wait for a transfer to end - this hast to be called before a channel
  85. or the data the channel transferd are used.
  86. int omap3_dma_get_revision(uint32_t *minor, uint32_t *major)
  87. Read silicon Revision of the DMA module
  88. NAND
  89. ====
  90. There are some OMAP3 devices out there with NAND attached. Due to the fact that
  91. OMAP3 ROM code can only handle 1-bit hamming ECC for accessing first page
  92. (place where SPL lives) we require this setup for u-boot at least when reading
  93. the second progam within SPL. A lot of newer NAND chips however require more
  94. than 1-bit ECC for the pages, some can live with 1-bit for the first page. To
  95. handle this we can switch to another ECC algorithm after reading the payload
  96. within SPL.
  97. BCH8
  98. ----
  99. To enable hardware assisted BCH8 (8-bit BCH [Bose, Chaudhuri, Hocquenghem]) on
  100. OMAP3 devices we can use the BCH library in lib/bch.c. To do so add CONFIG_BCH
  101. and set CONFIG_NAND_OMAP_ECCSCHEME=5 (refer README.nand) for selecting BCH8_SW.
  102. The NAND OOB layout is the same as in linux kernel, if the linux kernel BCH8
  103. implementation for OMAP3 works for you so the u-boot version should also.
  104. When you require the SPL to read with BCH8 there are two more configs to
  105. change:
  106. * CONFIG_SYS_NAND_ECCPOS (must be the same as .eccpos in
  107. GPMC_NAND_HW_BCH8_ECC_LAYOUT defined in
  108. arch/arm/include/asm/arch-omap3/omap_gpmc.h)
  109. * CONFIG_SYS_NAND_ECCSIZE must be 512
  110. * CONFIG_SYS_NAND_ECCBYTES must be 13 for this BCH8 setup
  111. Acknowledgements
  112. ================
  113. OMAP3 U-Boot is based on U-Boot tar ball [9] for BeagleBoard and EVM done by
  114. several TI employees.
  115. Links
  116. =====
  117. [1] OMAP3:
  118. http://www.ti.com/omap3 (high volume) and
  119. http://www.ti.com/omap35x (broad market)
  120. [2] OMAP3530 BeagleBoard:
  121. http://beagleboard.org/
  122. [3] Gumstix Overo:
  123. http://www.gumstix.net/Overo/
  124. [4] TI EVM:
  125. http://focus.ti.com/docs/toolsw/folders/print/tmdxevm3503.html
  126. [5] OpenPandora Ltd. Pandora:
  127. http://openpandora.org/
  128. [6] TI/Logic PD Zoom MDK:
  129. http://www.logicpd.com/products/devkit/ti/zoom_mobile_development_kit
  130. [7] TI/Logic PD Zoom 2
  131. http://www.logicpd.com/sites/default/files/1012659A_Zoom_OMAP34x-II_MDP_Brief.pdf
  132. [8] CompuLab Ltd. CM-T35:
  133. http://www.compulab.co.il/t3530/html/t3530-cm-datasheet.htm
  134. [9] TI OMAP3 U-Boot:
  135. http://beagleboard.googlecode.com/files/u-boot_beagle_revb.tar.gz