Ultrazed vcu trd 2019.2 add SDI RX problem

Hello,

I follow the flow from impleting to building petalinux images of ultrazed vcu trd 2019.2 design and it works. I modified the vivado project adding the SDI RX part from zcu106 vcu trd design and I edited device tree adding the entryn for sdi rx part. But in petalinux running on the board I can't find the sdi rx devices. What's I'm wrong?

Thank you very much.

https://xterra2.avnet.com/xilinx/zedboard/ultrazed-ev/vcu-trd-ports/rdf0428-uz7ev-vcu-trd-2019-2

Top Replies

Parents

drozwood90 over 5 years ago

Have you included this in the device tree?

--Dan
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
Former Member over 4 years ago in reply to drozwood90

Hello,

I create a project with Vivado. And export xsa file. I need a .bsp file.
I am using Vivado/Vitis 2019.2. How can I create a .bsp file ? Should I write it myself ?
I want to use this .bsp file with petalinux-create command.

Thanks for reply.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
narrucmot over 4 years ago in reply to Former Member

The .bsp file is a product of the petalinux-package command, which is run after first successfully completing the steps to create, configure, and build the PetaLinux project.

You can get an idea of the steps involved by looking at the BSP build scripts for the Avnet UZ7EV SOM (with EV carrier) in Avnet's petalinux github repository:
https://github.com/Avnet/petalinux/blob/2020.2/scripts/make_uz7ev_evcc_base.sh
https://github.com/Avnet/petalinux/blob/2020.2/scripts/common.sh

You may also want to look at Xilinx UG1144 - PetaLinux Tools Documentation Reference Guide

--Tom
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
Former Member over 4 years ago in reply to narrucmot

Hello,

But there is command like petalinux-create -t project -s .....bsp
if I dont have .bsp file i can not use this command.

Thanks,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
narrucmot over 4 years ago in reply to Former Member

Use the "petalinux-create -t project -s <PATH-TO-BSP>" command only when using a pre-built BSP as the starting point of your PetaLinux development.

When starting a PetaLinux project from scratch the command is more like:
$ petalinux-create --type project --template zynqMP --name <petalinux_project_name>"

Followed by the command to import the .xsa file for your Vivado hw project:
$ petalinux-config --silentconfig --get-hw-description=<path/to/xsa_file> -p </path/to/petalinux_project>

Then follow the rest of the steps described in Xilinx UG1144 and in the Avnet build scripts to build the OS image and package the PetaLinux project into a .bsp file.

--Tom
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Former Member over 4 years ago in reply to narrucmot

Hello,

According to UG1144, I've done
petalinux-create --type project --template zynqMP --name <project_name>"
petalinux-config --silentconfig --get-hw-description=<path/to/xsa_file>
petalinux-build
petalinux-package --boot ....

After these commands all images/linux folder files cretaed. That's ok. But when I boot from SD card (putting BOOT.bin and image.ub), Then I look in serial port with TeraTerm, there is no written lines, and after a while ps_err_out led is red.

Also when I look at the "/project-spec/meta-user/recipes-bsp/device-tree/files/" folder and in this folder there is 2 empty files (pl-custom.dtsi & system-user.dtsi). Should I write anything to dtsi files before any petalinux commands

Thanks,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
narrucmot over 4 years ago in reply to Former Member

You may need to configure your PetaLinux project for the correct boot UART and boot media settings.

It may also be helpful to compare the project configuration settings to a known-good PetaLinux project like that for the TRD you mentioned previously or one of the pre-built BSPs that can be downloaded here:
https://avnet.me/zedsupport

--Tom
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

narrucmot over 4 years ago in reply to Former Member

You may need to configure your PetaLinux project for the correct boot UART and boot media settings.

It may also be helpful to compare the project configuration settings to a known-good PetaLinux project like that for the TRD you mentioned previously or one of the pre-built BSPs that can be downloaded here:
https://avnet.me/zedsupport

--Tom
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

Former Member over 4 years ago in reply to narrucmot

Hello,

When I look at the "/project-spec/meta-user/recipes-bsp/device-tree/files/" folder and in this folder there is 2 empty files (pl-custom.dtsi & system-user.dtsi)
I thinks this was the problem. Should I write anything to .dtsi files before petalinux-build command ?
For example ;

&amba_pl {
vcu_apm: apm@0xa0140000 {
#address-cells = <0x1>;
#size-cells = <0x1>;
compatible = "generic-uio";
reg = <0x0 0xa0140000 0x0 0x10000>;
reg-names = "generic";
};
};

&amba_pl {
xlnk {
compatible = "xlnx,xlnk-1.0";
};
};

Like these.

Thanks,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
narrucmot over 4 years ago in reply to Former Member

It is usually not necessary to write anything to the pl-custom.dtsi file.

It is sometimes necessary to write peripheral configuration/descriptions in the system-user.dtsi file. Take a look at Avnet's system-bsp.dtsi file for the UltraZed-EV SOM + EV carrier:
https://github.com/Avnet/meta-avnet/blob/2020.2/recipes-bsp/device-tree/files/uz7ev-evcc/system-bsp.dtsi

There is a lot in this file - perhaps more than you need. This is just an example of what is sometimes needed, and it is very dependent on the PS and PL configuration for your design.

--Tom
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel