UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor dave91
Visitor
411 Views
Registered: ‎06-02-2019

Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hello,

I want to configure the Zynq UltraScale+ MPSoC Base TRD 2018.3 block design. I don't need the USB input and HDMI Rx/Tx in my design, so I removed them from the block design, changed the constraint files and Generate Bitstream without Errors. Furthermore I exported the hardware.

grafik.png

 

For the Linux Image I changed the device three settings in system-user.dtsi to:

#include "zcu102/zcu102-rev1.0.dtsi"
#include "zcu102/pcw.dtsi"
/ {
};
#include "zcu102/system-conf.dtsi"

/* Define design */
#define DESIGN_BASE_TRD

/* Define configuration */
#define CONFIG_USE_TPG
#define CONFIG_USE_CSI

/* Includes */
#include "base_trd/pl.dtsi"
#include "base_trd/qos.dtsi"

But when I run petalinux-build it fails with the error:

[INFO] building project
[INFO] sourcing bitbake
INFO: bitbake petalinux-user-image
Parsing recipes: 100% |#########################################################################################################################| Time: 0:01:30
Parsing of 2576 .bb files complete (0 cached, 2576 parsed). 3468 targets, 136 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Initialising tasks: 100% |######################################################################################################################| Time: 0:00:43
Checking sstate mirror object availability: 100% |##############################################################################################| Time: 0:00:17
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: pmu-firmware-2018.3+gitAUTOINC+56f3da2afb-r0 do_configure: Function failed: do_configure (log file is located at /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.31854)
ERROR: Logfile of failure stored in: /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.31854
Log data follows:
| DEBUG: Executing shell function do_configure
| MISC_ARG is  -yamlconf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/pmu-firmware.yaml
| APP_ARG is  -app "ZynqMP PMU Firmware"
| Using xsct from: /opt/pkg/petalinux/2018.3/tools/xsct/SDK/2018.3/bin/xsct
| cmd is: xsct -sdx -nodisp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/app.tcl -ws /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/build -pname pmu-firmware -rp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/git -processor psu_pmu_0 -hdf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 32  -app "ZynqMP PMU Firmware"  -yamlconf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/pmu-firmware.yaml
| INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
| Opening the hardware design, this may take few seconds.
| /opt/pkg/petalinux/2018.3/tools/xsct/SDK/2018.3/gnu/microblaze/lin
| can't read "source_name(4)": no such element in array
| ERROR: [Hsi 55-1545] Problem running tcl command ::sw_intc_v3_8::generate : can't read "source_name(4)": no such element in array
|     while executing
| "string compare -nocase $source_name($i) "system""
|     ("foreach" body line 18)
|     invoked from within
| "foreach periph $periphs {
|         #update global array of Interrupt sources for this periph
|         intc_update_source_array $periph
| 
|         lappend ..."
|     (procedure "xredefine_intc" line 21)
|     invoked from within
| "xredefine_intc $drv_handle $file_handle"
|     (procedure "xdefine_canonical_xpars" line 72)
|     invoked from within
| "xdefine_canonical_xpars $drv_handle "xparameters.h" "Intc" "DEVICE_ID" "C_BASEADDR" "C_HIGHADDR" "C_KIND_OF_INTR" "C_HAS_FAST" "C_IVAR_RESET_VALUE" "C..."
|     (procedure "::sw_intc_v3_8::generate" line 57)
|     invoked from within
| "::sw_intc_v3_8::generate axi_intc_0"
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
| Failed to generate the platform.
| Reason: Failed to generate the bsp sources for domain.pmu-firmware_domain
|     while executing
| "builtin_platform -generate quick"
|     (procedure "platform" line 221)
|     invoked from within
| "platform generate -quick"
|     invoked from within
| "if { $params(ws) ne "" } {
| 	#Local Work Space available
| 	if { $params(pname) ne "" } {
| 		# hwpname/bspname is empty then default it to pname+_hwproj/b..."
|     (file "/home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/app.tcl" line 139)
| WARNING: /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/temp/run.do_configure.31854:1 exit 1 from 'eval xsct -sdx -nodisp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/app.tcl -ws /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/build -pname pmu-firmware -rp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/git -processor psu_pmu_0 -hdf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 32 ${APP_ARG} ${MISC_ARG}'
| ERROR: Function failed: do_configure (log file is located at /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-firmware/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.31854)
ERROR: Task (/opt/pkg/petalinux/2018.3/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb:do_configure) failed with exit code '1'
ERROR: fsbl-2018.3+gitAUTOINC+56f3da2afb-r0 do_configure: Function failed: do_configure (log file is located at /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.32234)
ERROR: Logfile of failure stored in: /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.32234
Log data follows:
| DEBUG: Executing shell function do_configure
| MISC_ARG is  -yamlconf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/fsbl.yaml
| APP_ARG is  -app "Zynq MP FSBL"
| Using xsct from: /opt/pkg/petalinux/2018.3/tools/xsct/SDK/2018.3/bin/xsct
| cmd is: xsct -sdx -nodisp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/app.tcl -ws /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/build -pname fsbl -rp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/git -processor psu_cortexa53_0 -hdf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 64  -app "Zynq MP FSBL"  -yamlconf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/fsbl.yaml
| INFO: [Hsi 55-1698] elapsed time for repository loading 0 seconds
| Opening the hardware design, this may take few seconds.
| can't read "source_name(4)": no such element in array
| ERROR: [Hsi 55-1545] Problem running tcl command ::sw_intc_v3_8::generate : can't read "source_name(4)": no such element in array
|     while executing
| "string compare -nocase $source_name($i) "system""
|     ("foreach" body line 18)
|     invoked from within
| "foreach periph $periphs {
|         #update global array of Interrupt sources for this periph
|         intc_update_source_array $periph
| 
|         lappend ..."
|     (procedure "xredefine_intc" line 21)
|     invoked from within
| "xredefine_intc $drv_handle $file_handle"
|     (procedure "xdefine_canonical_xpars" line 72)
|     invoked from within
| "xdefine_canonical_xpars $drv_handle "xparameters.h" "Intc" "DEVICE_ID" "C_BASEADDR" "C_HIGHADDR" "C_KIND_OF_INTR" "C_HAS_FAST" "C_IVAR_RESET_VALUE" "C..."
|     (procedure "::sw_intc_v3_8::generate" line 57)
|     invoked from within
| "::sw_intc_v3_8::generate axi_intc_0"
| ERROR: [Hsi 55-1442] Error(s) while running TCL procedure generate()
| Failed to generate the platform.
| Reason: Failed to generate the bsp sources for domain.fsbl_domain
|     while executing
| "builtin_platform -generate quick"
|     (procedure "platform" line 221)
|     invoked from within
| "platform generate -quick"
|     invoked from within
| "if { $params(ws) ne "" } {
| 	#Local Work Space available
| 	if { $params(pname) ne "" } {
| 		# hwpname/bspname is empty then default it to pname+_hwproj/b..."
|     (file "/home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/app.tcl" line 139)
| WARNING: /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/temp/run.do_configure.32234:1 exit 1 from 'eval xsct -sdx -nodisp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/app.tcl -ws /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/build -pname fsbl -rp /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/git -processor psu_cortexa53_0 -hdf /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf -arch 64 ${APP_ARG} ${MISC_ARG}'
| ERROR: Function failed: do_configure (log file is located at /home/user/TRD_HOME/petalinux_new/bsp/build/tmp/work/zcu102_zynqmp-xilinx-linux/fsbl/2018.3+gitAUTOINC+56f3da2afb-r0/temp/log.do_configure.32234)
ERROR: Task (/opt/pkg/petalinux/2018.3/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/fsbl/fsbl_git.bb:do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 7347 tasks of which 7270 didn't need to be rerun and 2 failed.

Summary: 2 tasks failed:
  /opt/pkg/petalinux/2018.3/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/pmu-firmware/pmu-firmware_git.bb:do_configure
  /opt/pkg/petalinux/2018.3/components/yocto/source/aarch64/layers/meta-xilinx-tools/recipes-bsp/fsbl/fsbl_git.bb:do_configure
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
ERROR: Failed to build project

With the provided harware-configuration the build is sucessfull.

Are there addiotional settings which I diddn't considerd?

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
Visitor dave91
Visitor
269 Views
Registered: ‎06-02-2019

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Update:

In addition to the Concat-IP changes the device tree has to be configured.

1. In pl.dtsi set the new interrupt number:

 

...
&amba {

#ifndef DESIGN_RV_MIN
	axi_intc: interrupt-controller@a0010000 {
		#interrupt-cells = <2>;
		compatible = "xlnx,xps-intc-1.00.a";
		interrupt-controller;
		reg = <0x0 0xa0010000 0x0 0x10000>;
		xlnx,kind-of-intr = <0x1>;
		xlnx,num-intr-inputs = <0x4>;
		interrupt-parent = <&gic>;
		interrupts = <0 89 4>;
	};
#endif
...
};

2. In vcap-csi.dtsi change the interrupts to the matching inputs of the Concat-IP:

#include <dt-bindings/media/xilinx-vip.h>

&amba {
	axi_iic_0_sensor: i2c@a00a0000 {
		#address-cells = <1>;
		#size-cells = <0>;
		compatible = "xlnx,xps-iic-2.00.a";
		interrupt-parent = <&axi_intc>;
		interrupts = <3 2>;
		reg = <0x0 0xa00a0000 0x0 0x10000>;
		clocks = <&axi_lite_clk>;
	}; 
        ... 
};
...
csiss_1: csiss@a0060000 { compatible = "xlnx,mipi-csi2-rx-subsystem-3.0"; reg = <0x0 0xa0060000 0x0 0x10000>; clocks = <&axi_stream_clk>; interrupt-parent = <&axi_intc>; interrupts = <1 2>; ... };
...
...
fb_wr_csi: fb_wr@b0020000 { compatible = "xlnx,axi-frmbuf-wr-v2.1"; reg = <0x0 0xb0020000 0x0 0x10000>; #dma-cells = <1>; interrupt-parent = <&axi_intc>; interrupts = <2 2>; #ifdef DESIGN_BASE_TRD xlnx,vid-formats = "yuyv", "uyvy", "y8"; #endif #ifdef DESIGN_RV_SS xlnx,vid-formats = "yuyv", "uyvy", "y8", "rgb888"; #endif reset-gpios = <&gpio 80 1>; xlnx,dma-addr-width = <32>; xlnx,pixels-per-clock = <2>; xlnx,max-width = <3840>; xlnx,max-height = <2160>; };
...

Now the IMX274-sensor is detected by the OS.

 

 

 

0 Kudos
10 Replies
Scholar watari
Scholar
384 Views
Registered: ‎06-16-2013

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hi @dave91 

 

Did you use hdf file ?

It seems taht you use wrong hdf file during petalinux-build flow.

 

Best regards,

0 Kudos
Visitor dave91
Visitor
367 Views
Registered: ‎06-02-2019

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hi @watari,

before building the Linux image I executed the following steps:

1. Creating the Petalinux project with the TRD BSP:

petalinux-create -t project -s zcu102-prod-base-dm10.bsp -n bsp

2. Configuration without the hdf file:

petalinux-config --oldconfig

3. Building the Linux Image without hardware configuration and matching device tree:

#include "zcu102/zcu102-rev1.0.dtsi"
#include "zcu102/pcw.dtsi"
/ {
};
#include "zcu102/system-conf.dtsi"

/* Define design */
#define DESIGN_BASE_TRD

/* Define configuration */

/* Includes */
petalinux-build

4. After a  sucessfull boot I wanted to rebuild the Linux image with my hardware configuration and the optimized device tree:

petalinux-config --get-hw-description=~/TRD_HOME/vivado_new/zcu102_base_trd/zcu102_base_trd.sdk --oldconfig

petalinux-build

Than the error occurs.

 

When you mean I use the wrong hdf, yea that's true, I want to optimize the TRD Block Design for my own application.

Thanks for reply

0 Kudos
Moderator
Moderator
359 Views
Registered: ‎11-09-2015

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hi @dave91 

The recommendation when you want to strip down the TRD design is usually...to start from scratch from the ZCU102 BSP (not even the BSP from the TRD).

The TRD includes many pathes and edits to the DT that it can become difficult to manage. But we are trying to improve it.

Your case could be a good practice. Could you share your hdf file in attachement? I will try to reproduce the issue you are getting

Thanks and Regards


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
Visitor dave91
Visitor
350 Views
Registered: ‎06-02-2019

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hi @florentw,

thanks for the hint, I will check this method.

I have seen there is a way to generate the device tree with SDK or HSM/HSI, but I don't have any experience with that...

 

I attached the hdf without hdmi rx/tx, thanks for the help.

David

0 Kudos
Visitor dave91
Visitor
312 Views
Registered: ‎06-02-2019

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hello @florentw,

I'm still not sure to build my application from scratch.

Basically I just want to remove the HMDI Tx/Rx and the heartbeat application from the TRD. I still want to use the GUI of the TRD with it's functions.

In your opinion is it more work to change the TRD or to make a new Design?

 

Back to the Petalinux-Erorrs:

I also disabled the HDMI driver in the rootfs:

 

petalinux-config -c rootfs

grafik.png

 

 

 

removed the following recipes in  ./meta-user/recipes-core/images/petalinux-image.bbappend

IMAGE_INSTALL_append = " kernel-module-hdmi"

Disabled the CONFIG_DRM_XLNX_MIXER in the kernel settings: (The Video Mixer was removed together with the HDMI IP-Cores)

 

petalinux-config -c kernel

 

grafik.png

 

 

 

 

Changed the device-tree.bbappend-file to:

 

FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI_append ="\
    file://base_trd/pl.dtsi \
    file://base_trd/qos.dtsi \
    file://base_trd/rpu0.dtsi \
    file://base_trd/rpu1.dtsi \
    file://base_trd/vcap-csi.dtsi \
    file://base_trd/vcap-tpg.dtsi \
    file://common/li-imx274mipi-fmc.dtsi \
    file://common/xlnk.dtsi \
    file://system-user.dtsi \
    file://zcu102/pcw.dtsi \
    file://zcu102/system-conf.dtsi \
    file://zcu102/zcu102-rev1.0.dtsi \
    file://zcu104/pcw.dtsi \
    file://zcu104/system-conf.dtsi \

And still got the build error.

Maybe the problems are coming from the interrupts like ERROR: [Hsi 55-1545] Problem running tcl command

Here my .dsa file: dsa-file download

Maybe somebody can find out more.

Thanks for helping,

David

0 Kudos
Highlighted
Visitor dave91
Visitor
299 Views
Registered: ‎06-02-2019

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Update:

In the block design there were some unconnected Concat Inputs for the platform interrupts, which caused the error.

I removed the redundant inputs and connected

  • In0 to tpg_input_s2mm_introut
  • In1 to mipi_csi2_rx_csirxss_csi_irq
  • In2 to mipi_csi2_rx_s2mm_introut
  • In3 to sensor_iic_iic2intc_irpt

Now the petalinux-build was successful.

But now the MIPI camera isn't detected by the OS.

With the TRD hw the camera is detected. It seems there are some more mistakes in the block design...

 

Moderator
Moderator
293 Views
Registered: ‎11-09-2015

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hi @dave91 

Good to know that you were able to make progresses. Sorry I didn't got the time to look at your HDF file yet.

You might want to check the MIPI IP registers to see if it is starting properly. Also look in the log to check if the driver is correctly loaded


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
Visitor dave91
Visitor
286 Views
Registered: ‎06-02-2019

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hi @florentw ,

here my boot log:

...
[   11.584513] usb 2-1: Manufacturer: GenesysLogic
[   11.627019] hub 2-1:1.0: USB hub found
[   11.631033] hub 2-1:1.0: 4 ports detected
[   11.776272] usb 1-1.1: new high-speed USB device number 3 using xhci-hcd
[   12.428276] IMX274 2-001a: imx274_set_test_pattern error = -110
[   12.434193] IMX274 2-001a: Error -110 setup default controls
[   12.439928] IMX274: probe of 2-001a failed with error -110
[   12.445894] xilinx-video amba:vcap_csi: Entity type for entity a0060000.csiss was not initialized!
[   12.454856] xilinx-video amba:vcap_csi: device registered
[   12.460514] xilinx-video amba:vcap_tpg: device registered
[   12.466082] xilinx-video amba:vcap_csi: Entity type for entity b0040000.v_demosaic was not initialized!
[   12.475485] xilinx-demosaic b0040000.v_demosaic: Xilinx Video Demosaic Probe Successful
[   12.483714] xilinx-video amba:vcap_csi: Entity type for entity b0010000.v_gamma was not initialized!
[   12.492852] xilinx-gamma-lut b0010000.v_gamma: Xilinx 8-bit Video Gamma Correction LUT registered
[   12.502112] xilinx-video amba:vcap_csi: Entity type for entity b0060000.csc was not initialized!
[   12.510901] xilinx-vpss-csc b0060000.csc: VPSS CSC 8-bit Color Depth Probe Successful
[   12.518895] xilinx-video amba:vcap_csi: Entity type for entity b0080000.scaler was not initialized!
[   12.527941] xilinx-vpss-scaler b0080000.scaler: Num Hori Taps 8
[   12.533854] xilinx-vpss-scaler b0080000.scaler: Num Vert Taps 8
[   12.539773] xilinx-vpss-scaler b0080000.scaler: VPSS Scaler Probe Successful
[   12.546962] xilinx-vtc a3c20000.vtc: device found, version 6.010
[   12.553379] xilinx-tpg b0030000.tpg: device found, version 0.000
[   12.559390] xilinx-video amba:vcap_tpg: Entity type for entity b0030000.tpg was not initialized!
[   12.569223] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   12.576096] rtc_zynqmp ffa60000.rtc: setting system clock to 2019-06-06 12:47:23 UTC (1559825243)
[   12.584975] of_cfs_init
[   12.587420] of_cfs_init: OK
[   12.590339] clk: Not disabling unused clocks
[   12.594840] ALSA device list:
[   12.597804]   #0: DisplayPort monitor
[   12.601870] Freeing unused kernel memory: 512K
[   12.685950] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   12.724763] udevd[1985]: starting version 3.2.2
[   12.749042] udevd[1986]: starting eudev-3.2.2
[   12.824985] mali: loading out-of-tree module taints kernel.
[   13.264054] EXT4-fs (mmcblk0p2): recovery complete
[   13.268857] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[   14.110172] usb 1-1.1: New USB device found, idVendor=046d, idProduct=082d
[   14.117060] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=1
[   14.124370] usb 1-1.1: Product: HD Pro Webcam C920
[   14.129160] usb 1-1.1: SerialNumber: 7E57376F
[   14.139016] uvcvideo: Found UVC 1.00 device HD Pro Webcam C920 (046d:082d)
[   14.146268] uvcvideo 1-1.1:1.0: Entity type for entity Processing 3 was not initialized!
[   14.154368] uvcvideo 1-1.1:1.0: Entity type for entity Extension 6 was not initialized!
[   14.162366] uvcvideo 1-1.1:1.0: Entity type for entity Extension 12 was not initialized!
[   14.170456] uvcvideo 1-1.1:1.0: Entity type for entity Camera 1 was not initialized!
[   14.178199] uvcvideo 1-1.1:1.0: Entity type for entity Extension 8 was not initialized!
[   14.186203] uvcvideo 1-1.1:1.0: Entity type for entity Extension 9 was not initialized!
[   14.194206] uvcvideo 1-1.1:1.0: Entity type for entity Extension 10 was not initialized!
[   14.202297] uvcvideo 1-1.1:1.0: Entity type for entity Extension 11 was not initialized!
[   14.210544] input: HD Pro Webcam C920 as /devices/platform/amba/ff9d0000.usb0/fe200000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.1/1-1.1:1.0/input/input1
[   14.508276] usb 1-1.2: new low-speed USB device number 4 using xhci-hcd
[   14.616052] usb 1-1.2: New USB device found, idVendor=17ef, idProduct=608d
[   14.622932] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   14.630239] usb 1-1.2: Product: Lenovo USB Optical Mouse
[   14.635548] usb 1-1.2: Manufacturer: PixArt
[   14.653791] input: PixArt Lenovo USB Optical Mouse as /devices/platform/amba/ff9d0000.usb0/fe200000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1.2/1-1.2:1.0/0003:17EF:608D.0001/input/input2
[   14.669782] hid-generic 0003:17EF:608D.0001: input: USB HID v1.11 Mouse [PixArt Lenovo USB Optical Mouse] on usb-xhci-hcd.0.auto-1.2/input0
[   15.225932] pps pps0: new PPS source ptp0
[   15.229962] macb ff0e0000.ethernet: gem-ptp-timer ptp clock registered.
[   15.236664] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   24.606344] PLL: enable
[   26.716077] usb 1-1.1: reset high-speed USB device number 3 using xhci-hcd
[   33.565046] random: crng init done

 

0 Kudos
Visitor dave91
Visitor
270 Views
Registered: ‎06-02-2019

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Update:

In addition to the Concat-IP changes the device tree has to be configured.

1. In pl.dtsi set the new interrupt number:

 

...
&amba {

#ifndef DESIGN_RV_MIN
	axi_intc: interrupt-controller@a0010000 {
		#interrupt-cells = <2>;
		compatible = "xlnx,xps-intc-1.00.a";
		interrupt-controller;
		reg = <0x0 0xa0010000 0x0 0x10000>;
		xlnx,kind-of-intr = <0x1>;
		xlnx,num-intr-inputs = <0x4>;
		interrupt-parent = <&gic>;
		interrupts = <0 89 4>;
	};
#endif
...
};

2. In vcap-csi.dtsi change the interrupts to the matching inputs of the Concat-IP:

#include <dt-bindings/media/xilinx-vip.h>

&amba {
	axi_iic_0_sensor: i2c@a00a0000 {
		#address-cells = <1>;
		#size-cells = <0>;
		compatible = "xlnx,xps-iic-2.00.a";
		interrupt-parent = <&axi_intc>;
		interrupts = <3 2>;
		reg = <0x0 0xa00a0000 0x0 0x10000>;
		clocks = <&axi_lite_clk>;
	}; 
        ... 
};
...
csiss_1: csiss@a0060000 { compatible = "xlnx,mipi-csi2-rx-subsystem-3.0"; reg = <0x0 0xa0060000 0x0 0x10000>; clocks = <&axi_stream_clk>; interrupt-parent = <&axi_intc>; interrupts = <1 2>; ... };
...
...
fb_wr_csi: fb_wr@b0020000 { compatible = "xlnx,axi-frmbuf-wr-v2.1"; reg = <0x0 0xb0020000 0x0 0x10000>; #dma-cells = <1>; interrupt-parent = <&axi_intc>; interrupts = <2 2>; #ifdef DESIGN_BASE_TRD xlnx,vid-formats = "yuyv", "uyvy", "y8"; #endif #ifdef DESIGN_RV_SS xlnx,vid-formats = "yuyv", "uyvy", "y8", "rgb888"; #endif reset-gpios = <&gpio 80 1>; xlnx,dma-addr-width = <32>; xlnx,pixels-per-clock = <2>; xlnx,max-width = <3840>; xlnx,max-height = <2160>; };
...

Now the IMX274-sensor is detected by the OS.

 

 

 

0 Kudos
Moderator
Moderator
235 Views
Registered: ‎11-09-2015

Re: Changing Zynq UltraScale+ MPSoC Base TRD 2018.3 Block Design

Jump to solution

Hi @dave91 

Great good to konw to you have it working now.

Regards,


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos