Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > USB Controllers > FIFO READ

Bookmark and Share
Cypress Developer CommunityTM
Forums | Videos | Blogs | Training | Rewards Program | Community Components



FIFO READ
Moderator:
RSKV

Post Reply
Follow this topic



FIFO READ

ABM posted on 21 Feb 2013 8:38 PM PST
Member
9 Forum Posts

 

HI,

        I am currently working on a project to get the video out of a camera using a FX2LP. I am trying to understand the FIFO read using GPIF. I have attached the FSYNC to RDY0 and LSYNC to RDY1. The hardware seems to work right as i able to receive the data out of the camera using a single read byte. I want to FIFO read waveform so that i can get the SYNC frame out of the camera and get the video out of the camera. But i still don't understand completely the transition from the timing diagrams to the state diagrams using GPIF. The following points, I am having confusion with:

1. In my project, FSYNC will rise at least one clock cycle before LSYNC. I want to make sure that FSYNC and LSYNC are both 0 before i activate the data. But if the decision state I can't use if FYSNC = 0 and LSYNC = 0 because the second data value is always 1. 

2. What should i use for the transaction counter? i am receiving 1 byte per pixel and it is 320 x 240 camera. Should i use the transaction counter to be 76800? I am confused that should I get frame in each FIFO read transaction. If yes, i want to use the AUTO IN mode, will the data be transferred automatically once the data buffer filled with 512 bytes?

I am attaching the timing diagram of the camera. Can you suggest any what would be the best way for me to get the video out of the camera.

I would really appreciate if someone can help me with this issue.

Regards,

ABM




Re: FIFO READ

RSKV posted on 24 Feb 2013 12:55 AM PST
Cypress Employee
851 Forum Posts

Hi ABM,

Implementing image sensor interface with Slave FIFO interface of FX2LP would be easier than going for GPIF.

Is there any specific reason for selecting GPIF for your application.

If you go for Slave FIFO interface, I think you just need to connect FSYNC to SLCS and LSYNC to SLWR. When both are valid the image sensor data will be written to the endpoint memory present in FX2LP. Endpoint will be decided based on FIFOADDR lines. You need to connect these FIFOADDR lines to ground If want to use EP2.

Let me know if you have any more questions on this implementation.

Thanks,

Sai Krishna.

 

 



Re: FIFO READ

RSKV posted on 24 Feb 2013 12:58 AM PST
Cypress Employee
851 Forum Posts

Please refer to 9th chapter of EZ-USB TRM to get more details on Slave FIFO interface.

 

Thanks,

Sai Krishna.

 

 



Re: FIFO READ

PRJI posted on 24 Feb 2013 05:03 AM PST
Cypress Employee
333 Forum Posts

 Hi,

Following ANs would be helpful

AN61345 - Implementing an FX2LP™- FPGA Interface 

AN63787 - EZ-USB® FX2LP™ GPIF and Slave FIFO Configuration Examples Using 8-bit Asynchronous Interface 

AN6077 - Implementing an 8-Bit Asynchronous Interface with FX2LP™ 

-PRJI



Re: FIFO READ

ABM posted on 25 Feb 2013 05:46 PM PST
Member
9 Forum Posts

 Hi Sai Krishna,

                               Thanks for you reply. Let me answer your questions:

Implementing image sensor interface with Slave FIFO interface of FX2LP would be easier than going for GPIF.

Ans: - We used GPIF so that we can make sure that frame start with 0,0 when user request for a frame. What i asking that what happen when user request for a frame data transfer is in the middle. Is there any way to check this in SLAVE FIFO mode?

 

Is there any specific reason for selecting GPIF for your application.

Ans:- Why you are suggesting SLAVE FIFO mode? is there any specific reason. Will the performance would be better if we use SLAVE FIFO MODE.

 

Once again thanks for the reply. Please clarify the above points as we are real closed to finish this project.

 

Regards,

Abhishek Madaan



Re: FIFO READ

RSKV posted on 25 Feb 2013 07:02 PM PST
Cypress Employee
851 Forum Posts

Hi Abhishek,

The only advantage of going for Slave FIFO is that the image sensor interface implementation will be easier. That's all. I thought you just started the project. If you had already developed the GPIF waveforms and all then go ahead with the same design. No need to change it now.

I will give my answers to your questions related to GPIF soon.

Thanks,

Sai Krishna.

 

 



Re: FIFO READ

ABM posted on 25 Feb 2013 08:38 PM PST
Member
9 Forum Posts

 Hi rskv,

             Thanks for your reply. We are still in developing phase And changing to slave fifi wouldn't be issue. If you can answer both in GPIF and slave FIFO would be really appreciated.

 

regards

ABM



Re: FIFO READ

Gayathri posted on 26 Feb 2013 09:31 AM PST
Cypress Employee
428 Forum Posts

 Hi,

 

In slave FIFO you can choose to connect FSYNC to any GPIO pin and HSYNC to SLWR. That way, you can check the status of FSYNC inside firmware right? 

 

Regards,

Gayathri



Re: FIFO READ

ABM posted on 26 Feb 2013 04:09 PM PST
Member
9 Forum Posts

 Hi Gayatri,

                    Thanks for your reply. What about AutoIn Mode? We are not trying to use CPU just for perfomance purposes. Is this possible in AutonIn Mode?

 

Regards,

ABM



Re: FIFO READ

Gayathri posted on 26 Feb 2013 09:43 PM PST
Cypress Employee
428 Forum Posts

 Hi, 

 

AUTO mode always gives maximum performance compared to Manual mode as CPU does not come in the data path. Is your application using UVC class? If so, how are the headers being inserted. If there is no data modification required, then you can always choose AUTO mode.

 

Regards,

Gayathri






ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Spec No: None; Sunset Owner: GRAA; Secondary Owner: RAIK; Sunset Date: 01/01/20