寻找与WinUSB一起使用的FX3描述符

你好，
你需要添加微软OS字符串描述符，扩展兼容ID descritptor和扩展属性描述符。参考：http：/ / MSDN。微软。COM / EN /图书馆/门窗/五金/ ff537430（V = vs.85 aspx）。
当做，
- Madhu Sudhan



     以下为原文
  Hi,
    You need to add the Microsoft OS String descriptor, Extended Compat ID Descritptor and Extended Properties Descriptor. Ref: https://msdn.microsoft.com/en-in/library/windows/hardware/ff537430(v=vs.85).aspx
    Regards,
    -Madhu Sudhan

经过大量调试，我们最终得到了FX3在WiNoS7和8的WiUSB上工作。我列出了我们的代码添加如下。希望这有助于某人！
- CyfxSLIFTIFNC
/*尝试在WiUSB支持*/Extn const Unt88t CyfxUsBasdScR[]；Extn const Unt8t CyfxUsButoPultCudioStutuxDSCR[]；Extn const Unt8t CyfxUbExtPrimeStExosiDSCR[]；
CYFXSLIFUSSBDSCR C：
/*OS描述符按Win USB要求*/contuuu88t CyfxUsBasdSc[] ][At]（（对齐）（32））＝0x12，/*长度：描述符长度*/CyuU3pU***StrugyDISCR，/*bMultRyType：描述符类型*/m m，0x00，/*qW签名：签名字段*/s s，0x00，'f'，0x00，'t'，0x00，'' 1′0x00、“0”、“0x00”、“0”、0x00、0x00、/*bMSyvavordcode：供应商代码*/0x00 /*bPAD：PAD字段*/}；/*扩展的COMPATE ID OS特征描述符，按照WiUSB要求*/conuutu88t CyfxUsButoPosikDealSudioDSCR[[ ]（Apple（32））＝{//Head节0x28、0x00、0x00、0x00、/*dleNGTH：40＝16＋24 */0x00，0x01，/*bCDVIEST:描述符的版本号*/0x04/0x00，/*WiDEX：扩展的COMPAT ID描述符*/0x01，/*bCube：函数部分*/0x00，0x00，0x00，0x00，0x00，0x00，0x00，/*保留的*//-功能部分0x00，/*bFrsithTopFuffNo.No.*/0x01，/*保留*/''，''，'''，'x'，0x00，0x00，0x00，0x00，0x00，0x00，0x00，0x00，0x00，/*SuffAuthulyId*/0x00，0x00，0x00，0x00，0x00，0x00 /*保留*/}；/*扩展属性OS描述符，按WinUSB（USB 3）要求*/conuutu88t CyfxUsBeXBurst属性OsStutuxDSCR[][AXY]属性（=（32））＝{//Head节0x8e，0x00，0x00，0x00，/*DWFLUT: 142＝10＋132 */0x00，0x01，/*bCDVALTE:描述符的版本号*/0x05/0x00，/*WiDEX：扩展属性OS描述符*/0x01,0x00，/*bCube：属性数*///自定义PR0x00，0x00，/*dWist: 132＝14×40，0x01,0x00，0x00，0x00，/*DWAsPrimeDATA Type：一个空终止的Unicode字符串（ReGysz）*/0x28，0x00，/*WordPythNythLead长度：“Deffice IdFraseGuID”*//d′，0x00，'e’，0x00，'V'，0x00，'i'，0x00，'c'，0x00，'e '，0x00，操作部分1 0x84/0x00'I',0x00,'n',0x00,'t',0x00,'e',0x00,'r',0x00,'f',0x00,'a',0x00,'c',0x00,'e',0x00, 'G',0x00,'U',0x00,'I',0x00,'D',0x00, 0x00,0x00, 0x4E,0x00,0x00,0x00, /* dwPropertyDataLength: 78 */ /* bPropertyData: "{01234567-2A4F-49EE-8DD3-FADEA377234A}" */ '{',0x00, '0',0x00,'1',0x00,'2',0x00,'3',0x00,'4',0x00,'5',0x00,'6',0x00,'7',0x00,'-',0x00, '2',0x00,'A',0x00,'4',0x00,'F',0x00,'-',0x00, '4',0x00,'9',0x00,'E',0x00,'E',0x00,'-',0x00, '8',0x00,'D',0x00,'D',0x00,'3',0x00,'-',0x00, 'F',0x00,'A',0x00,'D',0x00,'E',0x00,'A',0x00,'3',0x00,'7',0x00,'7',0x00,'2',0x00,'3',0x00,'4',0x00,'A',0x00, '}',0x00, 0x00,0x00 }；
CyfxSLFulthCyc.c，IsiDeCyfxSLIFOpAppNuSbSuPuCbb函数：
1）在其他变量中增加变量长度：
UIT88T BRESQUEST，BRQUYTYPE；UTIN 8T T BType，BTAbjt；UTIN 16WT WWORD，WIDEX，WLUTE；CybOLYLT IsHANDLED＝CyFalm；/*从安装请求解码字段。* / breqtype =（setupdat0 &；cy_u3p_u***_request_type_mask）；B组（breqtype &；cy_u3p_u***_type_mask）；btarget =（breqtype &；cy_u3p_u***_target_mask）；brequest =（（setupdat0 &；cy_u3p_u***_request_mask）>；>；cy_u3p_u***_request_pos）；值=（（setupdat0 &；cy_u3p_u***_value_mask）>；>；cy_u3p_u***_value_pos）；该=（（setupdat1 &；cy_u3p_u***_index_mask）>；>；cy_u3p_u***_index_pos）；wlength =（（setupdat1 &；cy_u3p_u***_length_mask）>；>；cy_u3p_u***_length_pos）；
2）添加下面的“如果（B = = cy_u3p_u***_standard_rqt）{ }”部分：
else if（（breqtype = = 0xC0）&；&；（该= = 0x04））{ /*处理OS功能兼容ID描述符请求。*//*确保我们不发送比请求更多的数据。*如果（wlength >；cyfxu***extcompatidosfeaturedscr [零]）wlength = cyfxu***extcompatidosfeaturedscr [0 ]；cyu3pu***sendep0data（wlength，（uint8_t *）cyfxu***extcompatidosfeaturedscr）；都处理了= cytrue；} //如果（（breqtype = = 0xc1）&；&；（该= = 0x05））{ //未遂修复：一些USB驱动收入正确使用breqtype 0xC0到操作系统功能扩展性能/ else if（（（breqtype | 0x01）= = 0xc1）&；&；（该= = 0x05））{如果（该= = 0x05）{ /*处理系统功能扩展属性描述符请求。*//*确保我们不发送比请求更多的数据。*如果（wlength >；cyfxu***extpropertiesosfeaturedscr [ 0 ]）wlength = cyfxu***extpropertiesosfeaturedscr [ 0 ]；cyu3pu***sendep0data（wlength，（uint8_t *）cyfxu***extpropertiesosfeaturedscr）；都处理了= cytrue；}
编辑：这么多的格式化…它在编辑中看起来更好。



     以下为原文
  After a lot of debugging, we finally got the FX3 to work with WinU*** on both Windows 7 and 8. I listed our code additions below. Hope this helps someone!
    - cyfxslfifosync.h:
     
    /* attempt at WinUSB support */ extern const uint8_t CyFxU***OSDscr[]; extern const uint8_t CyFxU***ExtCompatIdOSFeatureDscr[]; extern const uint8_t CyFxU***ExtPropertiesOSFeatureDscr[];     
    - cyfxslfifou***dscr.c:
     
         /* OS descriptor as per WinUSB requirement */ const uint8_t CyFxU***OSDscr[] __attribute__ ((aligned (32))) = {     0x12,                           /* bLength: Length of the descriptor */     CY_U3P_USB_STRING_DESCR,        /* bDescriptorType: Descriptor type */     'M',0x00,                        /* qwSignature: Signature field */     'S',0x00,     'F',0x00,     'T',0x00,     '1',0x00,     '0',0x00,     '0',0x00,     0x00,                           /* bMS_VendorCode: Vendor code */     0x00                            /* bPad: Pad field */ };  /* Extended Compat ID OS Feature Descriptor as per WinUSB requirement */ const uint8_t CyFxU***ExtCompatIdOSFeatureDscr[] __attribute__ ((aligned (32))) = {     // Header Section     0x28,0x00,0x00,0x00,                     /* dwLength: 40 = 16 + 24 */     0x00,0x01,                               /* bcdVersion: The descriptor’s version number */     0x04,0x00,                                 /* wIndex: Extended compat ID descriptor */     0x01,                                    /* bCount: Number of function sections */     0x00,0x00,0x00,0x00,0x00,0x00,0x00,      /* RESERVED */     // Function Sections     0x00,                                    /* bFirstInterfaceNumber */     0x01,                                    /* RESERVED */     'W','I','N','U','S','B',0x00,0x00,       /* compatibleID */     0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, /* subCompatibleID */     0x00,0x00,0x00,0x00,0x00,0x00            /* RESERVED */ };  /* Extended Properties OS Feature Descriptor as per WinUSB (USB 3.0) requirement */ const uint8_t CyFxU***ExtPropertiesOSFeatureDscr[] __attribute__ ((aligned (32))) = {     // Header Section     0x8E,0x00,0x00,0x00,                     /* dwLength: 142 = 10 + 132 */     0x00,0x01,                               /* bcdVersion: The descriptor’s version number */     0x05,0x00,                                 /* wIndex: Extended property OS descriptor */     0x01,0x00,                               /* bCount: Number of properties */     // Custom Property Section 1     0x84,0x00,0x00,0x00,                     /* dwSize: 132 = 14 + 40 + 78 */     0x01,0x00,0x00,0x00,                     /* dwPropertyDataType: A NULL-terminated Unicode String (REG_SZ) */     0x28,0x00,                               /* wPropertyNameLength: 40 */                                              /* bPropertyName: "DeviceInterfaceGUID" */     'D',0x00,'e',0x00,'v',0x00,'i',0x00,'c',0x00,'e',0x00,     'I',0x00,'n',0x00,'t',0x00,'e',0x00,'r',0x00,'f',0x00,'a',0x00,'c',0x00,'e',0x00,     'G',0x00,'U',0x00,'I',0x00,'D',0x00,     0x00,0x00,     0x4E,0x00,0x00,0x00,                     /* dwPropertyDataLength: 78 */                                              /* bPropertyData: "{01234567-2A4F-49EE-8DD3-FADEA377234A}" */     '{',0x00,     '0',0x00,'1',0x00,'2',0x00,'3',0x00,'4',0x00,'5',0x00,'6',0x00,'7',0x00,'-',0x00,     '2',0x00,'A',0x00,'4',0x00,'F',0x00,'-',0x00,     '4',0x00,'9',0x00,'E',0x00,'E',0x00,'-',0x00,     '8',0x00,'D',0x00,'D',0x00,'3',0x00,'-',0x00,     'F',0x00,'A',0x00,'D',0x00,'E',0x00,'A',0x00,'3',0x00,'7',0x00,'7',0x00,'2',0x00,'3',0x00,'4',0x00,'A',0x00,     '}',0x00,     0x00,0x00 };   
     
    - cyfxslfifosync.c, inside CyFxSlFifoApplnUSBSetupCB function:
    1) Add variable for wLength amidst other variables:
     
             uint8_t  bRequest, bReqType;     uint8_t  bType, bTarget;     uint16_t wValue, wIndex, wLength;     CyBool_t isHandled = CyFalse;      /* Decode the fields from the setup request. */     bReqType = (setupdat0 & CY_U3P_USB_REQUEST_TYPE_MASK);     bType    = (bReqType & CY_U3P_USB_TYPE_MASK);     bTarget  = (bReqType & CY_U3P_USB_TARGET_MASK);     bRequest = ((setupdat0 & CY_U3P_USB_REQUEST_MASK) >> CY_U3P_USB_REQUEST_POS);     wValue   = ((setupdat0 & CY_U3P_USB_VALUE_MASK)   >> CY_U3P_USB_VALUE_POS);     wIndex   = ((setupdat1 & CY_U3P_USB_INDEX_MASK)   >> CY_U3P_USB_INDEX_POS);     wLength  = ((setupdat1 & CY_U3P_USB_LENGTH_MASK)  >> CY_U3P_USB_LENGTH_POS);   
     
    2) Add below the "if (bType == CY_U3P_USB_STANDARD_RQT) {}" section:
     
             else if ((bReqType == 0xC0) && (wIndex == 0x04)) {         /* Handle OS Feature Compatible IDs descriptor request. */          /* Make sure we do not send more data than requested. */         if (wLength > CyFxU***ExtCompatIdOSFeatureDscr[0])             wLength = CyFxU***ExtCompatIdOSFeatureDscr[0];          CyU3PU***SendEP0Data (wLength, (uint8_t *)CyFxU***ExtCompatIdOSFeatureDscr);         isHandled = CyTrue;     }     //else if ((bReqType == 0xC1) && (wIndex == 0x05)) {     // attempted fix: some USB drivers incorrectly use bReqType 0xC0 to get OS Feature Extended Properties     //else if (((bReqType | 0x01) == 0xC1) && (wIndex == 0x05)) {     else if (wIndex == 0x05) {         /* Handle OS Feature Extended Properties descriptor request. */          /* Make sure we do not send more data than requested. */         if (wLength > CyFxU***ExtPropertiesOSFeatureDscr[0])             wLength = CyFxU***ExtPropertiesOSFeatureDscr[0];          CyU3PU***SendEP0Data (wLength, (uint8_t *)CyFxU***ExtPropertiesOSFeatureDscr);         isHandled = CyTrue;      }   
     
    Edit: so much the formatting... it looked better in the editor. 

丹尼尔，
出色的工作。非常感谢。
但是，有什么遗漏了吗？（当我试着用我的设计，以前用柏树的司机，还载柏驱动）。MS文件，指着上面，指的是一个需要在index0xee字符串，我不知道在哪里，进场。不可能有一定的要求incyfxslfifoapplninit()功能
cyu3pu***setdesc（cy_u3p_u***_set_fs_config_descr，0，（uint8_t *）…）；
和
cyu3pu***setdesc（cy_u3p_u***_set_string_descr，0xee（是吗？），（UIT88T＊）…
你也能提供代码吗？
另外，你的格式就好了（如果你复制、粘贴你的代码在一个体面的编辑器，它保留了标签！）-亲切的问候，
保罗
更新1：
我实际上添加了这些调用：
/ *扩展兼容ID系统特征描述* / apiretstatus = cyu3pu***setdesc（cy_u3p_u***_set_ss_bos_descr，1（uint8_t *）cyfxu***extcompatidosfeaturedscr）；
/ *每WinUSB性能OS特征描述符扩展（USB 3）要求* / apiretstatus = cyu3pu***setdesc（cy_u3p_u***_set_ss_bos_descr，2，（uint8_t *）cyfxu***extpropertiesosfeaturedscr）；
apiretstatus = cyu3pu***setdesc（cy_u3p_u***_set_string_descr，0xee，（uint8_t *）cyfxu***osdscr）；
但我得到一个错误的时候加入，laststring描述符索引0xee：它给了我acy_u3p_error_bad_index误差。
我需要输入哑字符串才能得到索引0xee吗？
有什么想法吗？



     以下为原文
  Daniel,
    Excellent work. Thank you so much.
    However, isn't there something missing? (when I tried this with my design that previously used the Cypress driver, it still loads the Cypress driver).
The MS document that was pointed to above, was referring to a required string at index 0xEE, and I was wondering where that comes into play.
Shouldn't there maybe be some calls in CyFxSlFifoApplnInit() function to 
    CyU3PU***SetDesc(CY_U3P_USB_SET_FS_CONFIG_DESCR, 0, (uint8_t *) ...);
     
    and
    CyU3PU***SetDesc(CY_U3P_USB_SET_STRING_DESCR, 0xEE (I presume?), (uint8_t *) ...);
    Can you provide the code for that as well?
    Also, your formatting is just fine (if you copy, and paste your code above in a decent editor, it retains the tabs! ;-) )

Kind regards,
    ~ Paul
     
    Update 1:
    I actually added these calls:
        /* Extended Compat ID OS Feature Descriptor */
    apiRetStatus = CyU3PU***SetDesc(CY_U3P_USB_SET_SS_BOS_DESCR, 1, (uint8_t *)CyFxU***ExtCompatIdOSFeatureDscr);
 
        /* Extended Properties OS Feature Descriptor as per WinUSB (USB 3.0) requirement */
    apiRetStatus = CyU3PU***SetDesc(CY_U3P_USB_SET_SS_BOS_DESCR, 2, (uint8_t *)CyFxU***ExtPropertiesOSFeatureDscr);
        apiRetStatus = CyU3PU***SetDesc(CY_U3P_USB_SET_STRING_DESCR, 0xEE, (uint8_t *)CyFxU***OSDscr);
     
    but I get an error when adding that last string descriptor at index 0xEE: It gives me a CY_U3P_ERROR_BAD_INDEX error.
    Do I need to pad dummy strings to get to index 0xEE?
    Any ideas?

你好，
有关USB设备、枚举行为和注册表变量的信息可以创建HTTPS://MSDN。微软/CON/EN /库/ Windows /硬件/ JJ64 99 44（V＝VS 85）。
我面临以下问题：HTTP://www. McCHIP.COM/FUMMS/M80958ASPX
关于String 0xee（238），您可以在UsBasUpCuBuSB设置回调函数中处理字符串描述符请求。看看USB规范。
我使用以下工具来重新设置Windows注册表：Device Cleanup ToolandUSBOblivion。我能够测试所有的枚举过程，并用UB3.0/2.0分析器验证它。



     以下为原文
  Hi,
    Information about USB device, Enumeration behavior and Registry variables can be found https://msdn.microsoft.com/en-us/library/windows/hardware/jj649944(v=vs.85).aspx
    I am faced with the following reported issue : http://www.microchip.com/forums/m802958.aspx
    Concerning the string 0xEE(238), you can handle the string descriptor request yourself in the USBSetupCB USB Setup Callback function. Look at the USB specification.
    I use the following tools to reset the Windows registry : Device Cleanup Tool and USBOblivion. I am able to test all the enumeration process and validate that with the USB3.0/2.0 Analyzer.

你好，
我面临一个关于ReasasxHCIUSB 3主机控制器的问题。某些版本的驱动程序会导致USB扩展属性OS描述符丢失。
系统信息：
瑞萨电子USB 3主机控制器：固件版本：PCIVENY1033和DEV00194＆RVEV04PCIVANY103＆AMP；DeV00194和AsSysSyx 00000000和Rev04驱动程序测试：2.0.32.0：Ext PROP OK 2.0.34.0：Ext PROP OK 2.1.23.0：EXT PROP丢失2.1.37.0：EXT PROP丢失IT很烦人。解决办法是将设备连接到USB 2 EHCConnConrutter，因此可以检索EXT PROP。我希望不会有太多这样的问题。实施规范不具有应对挑战的环境设备。
DRIVE2-2-310-0.PNG
102.2 K
DRIVE2-2-34-0.PNG
108.5 K



     以下为原文
  Hi,
    I faced an issue regarding Renesas XHCI USB 3.0 Host Controller. Some versions of the driver cause the USB Extended Property OS Feature Descriptor to be missing.
    System information : 
   

    

• Renesas Electronics USB 3.0 Host Controller :     
  
        
  
  • Firmware Version : 4015      
    
  • PCIe Card : PCIVEN_1033&DEV_0194&REV_04  PCIVEN_1033&DEV_0194&SUBSYS_00000000&REV_04     
    
      
  
• Driver Tested :     
  
        
  
  • 2.0.32.0 : Ext Prop OK      
    
  • 2.0.34.0 : Ext Prop OK      
    
  • 2.1.28.0 : Ext Prop Missing      
    
  • 2.1.39.0 : Ext Prop Missing     
    
     
  

    It is quite annoying. The workaround is to connect the device to a USB 2.0 EHCI controller so the Ext Prop can be retrieved.
I hope there is not too much other issue like this. Implementing specification is hard enough without having to deal with a challenging environment equipment.

•   Driver2-1-39-0.png 102.2 K
  
  
•   Driver2-0-34-0.png 108.5 K
  
  

@ Paul Claessen：这0xee（“微软操作系统字符串”）descriptoris处理在我们的“如果（B = = cy_u3p_u***_standard_rqt）”部分，见下图。
因为我以前的帖子，我们也解决了支持赢10（和8.1）也加入MS OS 2.0描述符我们的FX3，所以我想是时候把我们的解决方案：
编辑：代码巴斯阻止论坛垃圾邮件过滤器。：（



     以下为原文
  @Paul Claessen: The 0xEE ("Miscrosoft OS String") descriptor is handled in our "if (bType == CY_U3P_USB_STANDARD_RQT)" section, see below.
    Since my previous post we also solved support for Win10 (and 8.1) by also adding MS OS 2.0 descriptors to our FX3, so I guess it's time to repost our solution:
    Edit: code paste prevented by forum spam filter.. :(

HI Sbrtand，当我正在处理我们的问题时，我读到一些控制器驱动程序使用不正确的请求来获得描述符：例如错误的ByType、BTAbor、BReQuest.如果你有一个USB分析器，你可以找出控制器的描述符请求的细节。有了这方面的知识，你可以在FX3中修改你的描述符处理，所以它用期望的描述符来响应这个（不正确的）请求，补偿控制器错误。



     以下为原文
  Hi ***ertrand,

Back when I was working on our issue, I read that some controller drivers use incorrect requests to get descriptors: e.g. wrong bType, bTarget, bRequest. If you have an USB analyzer, you can find out the details of your controller's descriptor requests. With this knowledge you can adapt your descriptor handling in the FX3, so it responds to this (incorrect) request with the expected descriptor, compensating for the controller bug?

嗨，丹尼尔，
我看了我的分析仪记录，但没有任何要求。对于Ext PROP的请求与最近的驱动程序没有发生。
通过分析器，我补偿了EXT PROP作为设备请求而不是接口请求发生的请求。
最近的司机不太合适。我的卡固件可能是旧的或不匹配驱动程序。



     以下为原文
  Hi Daniel,
    I looked at my analyzer recording but there is no request at all. The request for the Ext Prop are not happening with the recent driver.
    With the analyzer, I did compensate for the request of the Ext Prop happening as a Device Request instead of a Interface Request.
    The recent drivers are just not suitable. My card firmware may be old or not matching the driver.

我面临一个关于MSFT扩展属性OS描述符和ReSAS XHCI主机控制器的新问题。可以正确地报告Unicode字符串EXT PROP。我为暂停空闲配置定义了DWORDExt Prop（Debug、Debug、TimeLeTimeOutlook、DeVice）。
在英特尔USB主机控制器（EHCI和XHCI）上，注册表值是正确的，并且暂停/恢复测试正确地发生。然而，当设备被ReSAS XHCIHOST控制器完全枚举时，DWord Ext PROP将作为Unicode字符串报告给系统。我的500毫秒OfDebug的超时值显示为“Debug”。“十进制F4 01或500”。
瑞萨电子USB 3主机控制器驱动程序版本2.0.34.0。



     以下为原文
  I am facing a new issue regarding MSFT Extended Property OS Feature Descriptor and Renesas XHCI Host controller.
Unicode String Ext Prop are able to be reported correctly. I am defining DWORD Ext Prop for suspend idle configuration (DefaultIdleState, DefaultIdleTimeout, DeviceIdleEnabled, DeviceIdleIgnoreWakeEnable).
    On Intel USB Host controllers ( EHCI and XHCI ), the registry values are correct and suspend/resume testing occurs correctly. However when the device is fully enumerated by the Renesas XHCI Host controller, the DWORD Ext Prop are reported to the system as unicode strings. My value of 500 ms of DefaultIdleTimeout shows up as "DefaultIdleTimeout"="Ǵ". "Ǵ" is 00 F4 01 or 500 in decimal.
    Renesas Electronics USB 3.0 Host Controller Driver version 2.0.34.0.