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