Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > USB Controllers > Byte Qualifier on Slave FIFO Interface

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



Byte Qualifier on Slave FIFO Interface
Moderator:
RSKV

Post Reply
Follow this topic



Byte Qualifier on Slave FIFO Interface

Dagobert posted on 24 Aug 2011 6:19 AM PST
Member
2 Forum Posts

Hi,

I've got a question concerning the "Synchronous Slave FIFO interface with 32-bit data bus". It’s the interface between the FX3 and a FPGA in our application.  I’m wondering what happens if the USB packet length is not a multiple of 4 that means it fits not completely to the 32 bit bus width.
During the read sequence (from FX3 to FPGA) the last 32-bit-word that is read from the FX3-FIFO will contain less than 4 bytes. Therefore the FPGA doesn't know which bytes of the last word are valid. On the other hand during the write sequence (from FPGA to FX3) the last 32-bit-word that is written to the FX3-FIFO will contain less than 4 bytes. In that case the FX3 doesn't know which bytes are valid. I think there must be a kind of “byte qualifier” signal to mark the valid bytes within the 32-bit-words. Is it possible to configure some flags in the GPIF II as “byte enable”? I didn't find any hint in the application notes.

Best regards...

 




Re: Byte Qualifier on Slave FIFO Interface

aasi posted on 25 Aug 2011 05:14 AM PST
Cypress Employee
1073 Forum Posts

Hi,

We don't have a way of qualifying the data if the size of the last transaction is smaller than the bus width.

Since the requirement and the packet sizes that will be sent are known based on the end design it is up to you to implement a logic by which both sides sync up i.e. pad the data, send the byte count as part of the packet etc.

Regards,

Anand



Re: Byte Qualifier on Slave FIFO Interface

Dagobert posted on 25 Aug 2011 08:11 AM PST
Member
2 Forum Posts

Hi,

OK, I see. So we' have to insert some stuff bytes at the end of the packet if necessary and analyze the packet length in the protocol header.

Thank you for your quick reply!

Best regards...






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.