Home Explore Help
Register Sign In
phyus
/
uboot-vybrid_public
8
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 9b880bd4d8
Branches Tags
uboot-vybrid_pu...
/
doc
/
README-integrator

README-integrator 2.3 KB
History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364 
  1. 

  2. 		U-Boot for ARM Integrator Development Platforms
    3. 

  3. 

  4. 			Peter Pearse, ARM Ltd.
    5. 

  5. 			peter.pearse@arm.com
    6. 

  6. 			     www.arm.com
    7. 

  7. 

  8. Manuals available from :-
    9. 

  9. http://www.arm.com/products/DevTools/Hardware_Platforms.html
    10. 

  10. 

  11. Overview :
    12. 

  12. --------
    13. 

  13. There are two Integrator variants - Integrator/AP and Integrator/CP.
    14. 

  14. Each may be fitted with a variety of core modules (CMs).
    15. 

  15. Each CM consists of a ARM processor core and associated hardware e.g
    16. 

  16. 	FPGA implementing various controllers and/or register
    17. 

  17. 	SSRAM
    18. 

  18. 	SDRAM
    19. 

  19. 	RAM controllers
    20. 

  20. 	clock generators etc.
    21. 

  21. CMs may be fitted with varying amounts of SDRAM using a DIMM socket.
    22. 

  22. 

  23. Boot Methods :
    24. 

  24. ------------
    25. 

  25. Integrator platforms can be configured to use U-Boot in at least three ways :-
    26. 

  26. a) Run ARM boot monitor, manually run U-Boot image from flash
    27. 

  27. b) Run ARM boot monitor, automatically run U-Boot image from flash
    28. 

  28. c) Run U-Boot image direct from flash.
    29. 

  29. 

  30. In cases a) and b) the ARM boot monitor will have configured the CM and mapped
    31. 

  31. writeable memory to 0x00000000 in the Integrator address space.
    32. 

  32. U-Boot has to carry out minimal configration before standard code is run.
    33. 

  33. 

  34. In case c) it may be necessary for U-Boot to perform CM dependent initialization.
    35. 

  35. 

  36. Configuring U-Boot :
    37. 

  37. ------------------
    38. 

  38. 	The makefile contains targets for Integrator platforms of both types
    39. 

  39. fitted with all current variants of CM. If these targets are to be used with
    40. 

  40. boot process c) above then CONFIG_INIT_CRITICAL may need to be defined to ensure
    41. 

  41. that the CM is correctly configured.
    42. 

  42. 

  43. 	There are also targets independent of CM. These may not be suitable for
    44. 

  44. boot process c) above. They have been preserved for backward compatibility with
    45. 

  45. existing build processes.
    46. 

  46. 

  47. Code Hierarchy Applied :
    48. 

  48. ----------------------
    49. 

  49. Code specific to initialization of a particular ARM processor has been placed in
    50. 

  50. cpu/arm<>/start.S so that it may be used by other boards.
    51. 

  51. 

  52. However, to avoid duplicating code through all processor files, a generic core
    53. 

  53. for ARM Integrator CMs has been added
    54. 

  54. 

  55. 	cpu/arm_intcm
    56. 

  56. 

  57. Otherwise. for example,  the standard CM reset via the CM control register would
    58. 

  58. need placing in each CM processor file......
    59. 

  59. 

  60. Code specific to the initialization of the CM, rather than the cpu, and initialization
    61. 

  61. of the Integrator board itself, has been placed in
    62. 

  62. 

  63. 	board/integrator<>/platform.S
    64. 

  64. 	board/integrator<>/integrator<>.c
    65.