Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > USB Controllers > SuiteUSB and non-cypress GUID

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



SuiteUSB and non-cypress GUID
Moderator:
RSKV

Post Reply
Follow this topic



SuiteUSB and non-cypress GUID

seattleuser posted on 28 May 2011 8:58 AM PST
Member
4 Forum Posts

 Hi

If I have the following inside my INF

[Install.CyUSB.AddReg.Guid]

HKR,,DriverGUID,,"{AE18AA60-7F6A-11d4-97DD-00010229B959}"

 

Then suiteUSB can see my device no problem. 

But my understanding was that I could change that GUID to ensure that other programs using the same GUID could not update the driver I am using.

But when I change the GUID, SuiteUSB cannot see my device any longer. I've tried using SetCustomerGUID and SetClassGUID, but they don't seem to work.

If I delete the lines above from my INF it still works. But if I change the GUID, it stops working.

 

So, my question is: Is SuiteUSB able to work with GUIDs other than the '959 shown above? The article "How does the CyUSB.dll recognize a cypress device" seems to suggest "yes", but the paragraph is poorly written and the grammar unclear exactly what they mean.

 

http://www.cypress.com/?id=4&rID=35281

 

 




Re: SuiteUSB and non-cypress GUID

aasi posted on 29 May 2011 05:11 AM PST
Cypress Employee
1090 Forum Posts

Yep. CyUSB.Net is capable of talking to other DriverGUID values as well.

How are you opening the handle, are you providing your modified DriverGUID when opening the handle?

Control center code available at C:\Cypress\Cypress SuiteUSB 3.4.5\CyUSB.Net\Examples\CyControlCenter would be a good reference to understand how the registry is parsed to collect registered DriverGUID values and then open a handle to those DriverGUIDs.

Regards,

Anand



Re: SuiteUSB and non-cypress GUID

charon posted on 22 Nov 2012 02:15 AM PST
Member
3 Forum Posts

same problem occurred to me now, as I'm actually a hardware engineer so the answer above seems not be specific enough to me. so could you please explain more in detail how could i employ the cyusb.dll to find my device with my own GUID other than {AE18AA60-7F6A-11d4-97DD-00010229B959}? thxs a lot.

charon






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: KXP; Secondary Owner: VWA; Sunset Date: 01/01/20