Hello!
I`m using Zynq-7100 board with Petalinux 2017.2 project. Petalinux workflow starts project with BSP. It is much more convenient than creating project from the very beginning as you described here: https://wiki.trenz-electronic.de/display/PD/PetaLinux+KICKstart. Before Zynq-7100 I used to work with Zedboard. Xilinx BSP for zedboard contains properly formed configuration files to build fsbl, u-boot, linux kernel and rootfs along with pre-build images. But there are no Xilinx BSP for Zynq-7100.
My question is: could you provide BSP for the board desired?
Hello,
did you mean "TE0782-02-100-2I"? It's currently the only Trenz module with XC7Z100 SoC, see:
- https://shop.trenz-electronic.de/en/Products/Trenz-Electronic/TE07XX-Zynq-SoC/
We have a reference design (with prebuilt files, board part files...) with petalinux template available:
- https://shop.trenz-electronic.de/en/Download/?path=Trenz_Electronic/TE0782/Reference_Design
- https://shop.trenz-electronic.de/en/Download/?path=Trenz_Electronic/TE0782
- https://shop.trenz-electronic.de/en/Download/?path=Trenz_Electronic/TE0782/Reference_Design/2017.1/test_board
Newest is currently for Vivado/SDK/Petalinux 2017.1 but we will update to 2017.2.
You can use petalinux template project from <design folder>/os/petalinux with instruction from:
- https://wiki.trenz-electronic.de/display/PD/PetaLinux+KICKstart#PetaLinuxKICKstart-CreatingaProjectfromVivadoProject.1
br
John
Yes, I mean "TE0782-02-100-2I" with Xilinx Zynq-100 onboard.
I know about template projects at <design folder>/os/petalinux, but I think of BSP as preferable way to start project rather than copy-pasting template project.
Hi,
way? If you change Linux relevant setting (PS, or PL AXI...), you must always regenerate all steps new. And BSP is only a container, with the same project for one given setup.
We sell module instead of complete evaluation boards. So the given reference Designs are only some standard configuration. There are often more options that this one selected on reference design. Depends on the Carrier (in the most cases this are custom carrier) and the application you would implement, you must generate your own design settings.
PS: For 2017.2 design and newer, we will add a wiki documentation, where you can find all changes compared to the default petalinux configuration.
br
John
Thank you for your reply!