cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Contributor
Contributor
1,787 Views
Registered: ‎08-02-2016

AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

hi, folks

 

I have met an critical warning during connecting VFA and v_vid_in_axi4s:

 

CRITICAL WARNING: [BD 41-237] Bus Interface property TDATA_NUM_BYTES does not match between /v_cfa_0/video_in(1) and /v_vid_in_axi4s_0/video_out(2)

 

The CFA 's axis_tdata is always 8 bits width, and will not auto configured with external components. 

 

 

Tags (1)
mismatch_tdata.PNG
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Voyager
Voyager
2,227 Views
Registered: ‎03-28-2016

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

In PG002, the CFA does claim to auto-configure the Video Component Width.  What is the format and component width of the video output on the vid_in_axi4s?  Only a format of Mono and a component width of 8, 10 or 12 will work with the CFA.

 

Depending upon what version of Vivado you are using, there is also the Sensor Demosaic (v_demosaic) IP which is a newer implementation for Bayer conversion.

 

Ted Booth - Tech. Lead FPGA Design Engineer
https://www.designlinxhs.com

View solution in original post

8 Replies
Highlighted
Voyager
Voyager
2,228 Views
Registered: ‎03-28-2016

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

In PG002, the CFA does claim to auto-configure the Video Component Width.  What is the format and component width of the video output on the vid_in_axi4s?  Only a format of Mono and a component width of 8, 10 or 12 will work with the CFA.

 

Depending upon what version of Vivado you are using, there is also the Sensor Demosaic (v_demosaic) IP which is a newer implementation for Bayer conversion.

 

Ted Booth - Tech. Lead FPGA Design Engineer
https://www.designlinxhs.com

View solution in original post

Highlighted
Contributor
Contributor
1,744 Views
Registered: ‎08-02-2016

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

Thanks, ted.

The video out format is mono, and I made 2 pixels per cycle, so output width is 16 bits.

I don't think CFA can only support 8, 10 ,12 mode, that is too narrow for new high speed camera.

Vivado version is 2015.4.01.

I checked with demosaic, but my device (zynq-7000) is not availble.

0 Kudos
Highlighted
Explorer
Explorer
1,720 Views
Registered: ‎07-18-2011

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

@mcggoal

 

If the CFA can't do two bits per pixel, you can configure your Video In to AXI4-Stream IP for one bit per pixel, and use an AXI4-Stream Width Converter IP after the CFA to get your desired 16-bit 2bpp AXI stream, unless the 1bpp path won't meet your timing requirements.

 

 

Highlighted
Moderator
Moderator
1,692 Views
Registered: ‎11-09-2015

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

Hi @mcggoal,

 

As @tedbooth correctly said, you might want to use the demosaic IP. It is available for Zynq-7000 but you might want to use a newer version of vivado (ideally 2018.1).

 

As said the CFA only supports 8,10 and 12 bits as per its Product Guide (you might want to read it for information):

CFA.JPG

And as @reaiken, the CFA does not support muliple ppc. This is why you cannot use it the way you are trying to. The warning is correct.

 

Regards,


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
Highlighted
Contributor
Contributor
1,677 Views
Registered: ‎08-02-2016

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

hi @florentw

 

Thank you for clarify, I think I have to walk around this. 

 

Some still unclear, in the below topic:

https://forums.xilinx.com/xlnx/board/crawl_message?board.id=DEENBD&message.id=13200

I found the CFA was adapted to external interface to 16bits width.

0 Kudos
Highlighted
Moderator
Moderator
1,674 Views
Registered: ‎11-09-2015

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

Hi @mcggoal,

 

If everything is clear for you, please mark @tedbooth or @reaiken 's reply as accepted solution (select the best in your opinion - I only summurized their reply) by clicking on the button "accept as solution" on the bottom of the reply.

 

Thanks and Regards,


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
Highlighted
Moderator
Moderator
1,661 Views
Registered: ‎11-09-2015

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

Hi @mcggoal,

 

You will get a width of 16 for tdata if the CFA is configured in 10 or 12 bits (as the AXI interface says the tdata width should be a number of byte).

 

You can do it automatically in your BD if you select MONO/SENSORS and 10 or 12 bits (with one ppc):

AXI4S.JPG

 

And after validation:

CFA.JPG

 

However if you try multiple ppc or 16 bpc you will get a critical warning or an error because this is not supported.

 

Regards,


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
Highlighted
Contributor
Contributor
1,658 Views
Registered: ‎08-02-2016

Re: AXI Streaming Switch Tdata mismatch between CFA and v_vid

Jump to solution

@florentw

Got ! thank you again!

0 Kudos