Are there any limitations to the clock frequency that can be used with 32 bit DQ width?

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
MaAr_2545856
Level 4
Level 4
5 sign-ins 5 solutions authored First solution authored

GPIF 32 bit interface does not work with 54MHz. Are there any limitations to the clock frequency that can be used with 32 bit DQ width?

When we use 16bit interface to send video to UVC with PCLK up to 104MHz it works well. The 32-bit interface works with 27MHz. But it does not work well with a 32-bit interface with 54MHz. Kindly confirm is there any clock limitations for a 32-bit interface.

0 Likes
1 Solution

>> 1. We generated a test pattern data "12345678". When we cross verified with USBlyzer data received was "02345678".

>> 2. We generated a test pattern data "FFFFFFFF". When we cross verified with USBlyzer data received was "AFFFFFFF".

If this is the case, we can say that 962x766@60fps, PCLK54MHz is working but there is a error is received data.

As per the above two lines, it looks like first four bits are being sampled wrong.

Can you please send 0FFFFFFF pattern and confirm this?

View solution in original post

0 Likes
3 Replies
YangyangC_06
Employee
Employee
750 replies posted 500 replies posted 250 replies posted

Hi ,

I didn't hear about that it will be a problem working with 54M Hz clcok(32 bits). Could you please describe more on your question?

0 Likes

Hi,

The 32bit GPIF interface (962x383@60fps, PCLK27MHz) is working fine. I am able to stream image in AMcap.

The working GPIF 32 project (962x383@60fps, PCLK27MHz) is modified to (962x766@60fps, PCLK54MHz) instead of 27MHz. This is not working. I am not able to see the output in the AMcap and the application hangs.

I analyzed the communication using USBlyzer.I have attached the report.

https://drive.google.com/open?id=1mwmxkvKn-FoL07GLHq_LWKrbVZlxf6p0

https://drive.google.com/open?id=1E29TuSP3NhSbABdiK-Is80g8d-bvkHWW

1. We generated a test pattern data "12345678". When we cross verified with USBlyzer data received was "02345678".

2. We generated a test pattern data "FFFFFFFF". When we cross verified with USBlyzer data received was "AFFFFFFF".

when we tried to play with amcap. The application hangs. Kindly help me to resolve this issue.

0 Likes

>> 1. We generated a test pattern data "12345678". When we cross verified with USBlyzer data received was "02345678".

>> 2. We generated a test pattern data "FFFFFFFF". When we cross verified with USBlyzer data received was "AFFFFFFF".

If this is the case, we can say that 962x766@60fps, PCLK54MHz is working but there is a error is received data.

As per the above two lines, it looks like first four bits are being sampled wrong.

Can you please send 0FFFFFFF pattern and confirm this?

0 Likes