readme.txt 3.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586
  1. This is the Buildroot support for Zynq boards. Zynq boards are available from
  2. Xilinx and some third party vendors, but the build procedure is very similar.
  3. Currently, three boards are natively supported by Buildroot:
  4. - Xilinx ZC706 board (zynq_zc706_defconfig)
  5. - Avnet ZedBoard (zynq_zed_defconfig)
  6. - Avnet MicroZed (zynq_microzed_defconfig)
  7. Steps to create a working system for a Zynq board:
  8. 1) Configuration (do one of the following)
  9. make zynq_zc706_defconfig (ZC706)
  10. make zynq_zed_defconfig (Zedboard)
  11. make zynq_microzed_defconfig (MicroZed)
  12. 2) make
  13. 3) All needed files will be available in the output/images directory.
  14. The sdcard.img file is a complete bootable image ready to be written
  15. on the boot medium. To install it, simply copy the image to an SD
  16. card:
  17. # dd if=output/images/sdcard.img of=/dev/sdX
  18. Where 'sdX' is the device node of the uSD.
  19. 4) boot your board
  20. You can alter the booting procedure by creating a file uEnv.txt
  21. in the root of the SD card. It is a plain text file in format
  22. <key>=<value> one per line:
  23. kernel_image=myimage
  24. modeboot=myboot
  25. myboot=...
  26. Note:
  27. The DTB for MicroZed is the same as the one for the Zedboard (zynq-zed.dtb),
  28. and this is the recommended solution, see
  29. https://forums.xilinx.com/t5/Embedded-Linux/Microzed-default-device-tree-dts/td-p/432856.
  30. References:
  31. - ZC706 information including schematics, reference designs, and manuals are
  32. available from
  33. http://www.xilinx.com/products/boards-and-kits/ek-z7-zc706-g.html.
  34. - Zedboard/Microzed information including schematics, reference designs, and
  35. manuals are available from http://www.zedboard.org .
  36. Support for other boards:
  37. If you want to build a system for other boards based on the same SoC
  38. (for ex. Digilent Zybo board), and the board is already supported by
  39. the upstream kernel and U-Boot, you simply need to change the
  40. following Buildroot options:
  41. - Kernel Device Tree file name (BR2_LINUX_KERNEL_INTREE_DTS_NAME)
  42. - U-Boot board defconfig (BR2_TARGET_UBOOT_BOARD_DEFCONFIG)
  43. Custom ps7_init_gpl.c/h support:
  44. To generate a working boot.bin image, ps7_init_gpl.c/h are required in
  45. the U-Boot source tree. Without those files, boot.bin will be built
  46. successfully but it will not be functional at all. Those files are
  47. output from the Xilinx tools, but for convenience, U-Boot includes the
  48. default ps7_init_gpl.c/h of popular boards. Those files may need to be
  49. updated for any programmable logic customizations which impact
  50. ps7_init (clock/pin setup & mapping/AXI bridge setup/etc). See
  51. board/xilinx/zynq/ directory of U-Boot for natively supported ps7_init
  52. files. If the ps7_init files for your board are not found in U-Boot,
  53. you need to add them by yourself.
  54. 1) Start with a defconfig supported by Buildroot (e.g. Zedboard)
  55. make zynq_zed_defconfig
  56. 2) make uboot-menuconfig
  57. Visit the following menu and enable CONFIG_ZYNQ_CUSTOM_INIT.
  58. ARM architecture --->
  59. [*] Use custom ps7_init provided by Xilinx tool
  60. 3) Copy ps7_init_gpl.c/h generated by the Xilinx tools into
  61. output/build/uboot-xilinx-<pkg version>/board/xilinx/zynq/custom_hw_platform/
  62. 4) make
  63. Note: The files in step 3 will need to be re-copied after cleaning the
  64. output directory and at this time, there is no way to save them as
  65. part of the buildroot configuration, except as a U-Boot patch.