Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > USB Controllers > Sync Slave FIFO: Partial full flag not updated after short packet

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



Sync Slave FIFO: Partial full flag not updated after short packet
Moderator:
RSKV

Post Reply
Follow this topic



Sync Slave FIFO: Partial full flag not updated after short packet

Chris R. posted on 11 Jan 2012 11:25 PM PST
Top Contributor
135 Forum Posts

Hello,

I have to configure the slave fifo interface with partial full flag due to the flag latency. If I do this, the flag latency can be managed, but the flag isn´t updated after writing a short packet and all further data is lost until the buffers are commited to the host. If I use the dedicated flag, the flag goes low right after writing 2 short packets to the fifo (2 DMA buffers, no host read). This is the expected behavior. No data is lost. But how can I get this behavior together with the partial full flag?

I changed the GPIF descriptor PIB_GPIF_CTRL_BUS_SELECT(5) to 0x00000014 for partial flag and configured the flag with: apiRetStatus = CyU3PGpifSocketConfigure(0, CY_FX_PRODUCER_PPORT_SOCKET, 2, CyFalse, 0);

Another issue is the flag watermark value. In the description and slave fifo app not is written, the value indicates the number of words, where the word width is the GPIF width. But I cannot set up three 16 bit words, the granularity is always four words, also in 16 bit GPIF with. How can I handle this?

I use the 1.0 SDK with the DVK board Rev 2.




Re: Sync Slave FIFO: Partial full flag not updated after short packet

aasi posted on 13 Jan 2012 05:14 AM PST
Cypress Employee
1073 Forum Posts

Hi Chris,

You've to monitor both Partial flag and full flag if short packet is expected in non-burst mode.

I didn't get the full picture of the granularity issue you've mentioned, Please explain a bit more.

Thanks,

Anand



Re: Sync Slave FIFO: Partial full flag not updated after short packet

Chris R. posted on 13 Jan 2012 05:54 AM PST
Top Contributor
135 Forum Posts

Thank you.

This was my workaround too, (CNTRL[6] as Full Flag), it works, but is a dirty solution. :(

 

The other problem is: The watermark level always results in 4-byte steps, regardless of the width setting on GPIF II. It´s not possible to set it to 3 16 bit words, if I set the level to 2 the flag goes active 4 16 bit words before full. If I set the watermark to 1 the flag goes low 2 16 bit words before full. In the descripts is to be read, the value represents always words in the width og GPIF, but the behavior isn´t so.






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.