Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > USB Controllers > How to catch a USB standard request to device?

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



How to catch a USB standard request to device?
Moderator:
RSKV

Post Reply
Follow this topic



How to catch a USB standard request to device?

Chris R. posted on 13 Jun 2012 11:37 PM PST
Top Contributor
135 Forum Posts

For backward compatibility we want to react on a USB standard request (set feature) going to device as target. With the FX3 SDK 1.1.1 the unknown standard requests seems to be no longer forwarded to the CyFxSlFifoApplnUSBSetupCB callback function.

How to implement a manual processing of unknown standard requests?




Re: How to catch a USB standard request to device?

aasi posted on 13 Jun 2012 02:00 AM PST
Cypress Employee
1073 Forum Posts

Hi Chris,

SET_FEATURE is being handled by the firmware. Please let us know which particular FEATURE are you trying to set? i.e. value of wIndex and wValue that you're using

Regards,

Anand



Re: How to catch a USB standard request to device?

Chris R. posted on 13 Jun 2012 03:09 AM PST
Top Contributor
135 Forum Posts

At the moment we use a SET_FEATURE request with target device and value = 0x0008, index = 0x0000 for a hardware reset comman to the FPGA due to backward compatibility with an old FX2 design. I know this is a non-standard solution, and the FX3 SDK behavior is a really good point to change the command to a clean vendor request. I triggered our software team and they have a good day today, so they implemented the vendor request command upon failed usb standard request command. Due to this we cannot use old software with the new FX3 design, but this seems to be OK for the moment.



Re: How to catch a USB standard request to device?

aasi posted on 13 Jun 2012 04:45 AM PST
Cypress Employee
1073 Forum Posts

If the target of the SET_FEATURE is device then our SDK stack is handling it by default.

Good to know that you've a workaround implemented.

Regards,

Anand






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.