- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The SDK 1.2 Release Notes mention CyU3PUsbInitEventLog() and CyU3PUsbGetEventLogIndex(). I cannot find them mentioned anywhere in the documentation or the code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can find the description of these APIs in page number 411 and 412.
Usage is given in USBBulkSourceSink example project.
Regards,
sai krishna.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The FX3APIGuide.pdf (Revision 1.1) I have has Y_U3P_USB_HOST_EPS_ISO_ORUN_ERROR on page 411 and CY_U3P_USB_HOST_EPS_IOC_INT on page 412.
The USB Event Log stuff is not used in any of the examples supplied with SDK 1.2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Cypress Update Manager does not do a good job installing a new version of the SDK if a previous version is installed. When I uninstalled the old SDK and reinstall the new one, the pdfs, etc. are updated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can see that the output is a circurlare buffe. but how to interpret the data in the buffer ?
Poul-Erik.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found the answer in "cyu3usb.h". starting af "CYU3P_USB_LOG_VBUS_OFF".
Poul-Erik.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the info, Poul-Erik.
Do you know what the values for CYU3P_USB_LOG_LTSSM_CHG are? My understanding from the comment is that any value over 0x80 is an LTSSM state number. Are these state numbers summarized somewhere? I can see the state machine in the USB 3.0 spec, but there are no numbers for them. I presume Cypress has some mapping of these states to log numbers?
I see a lot of log events over 0x80 when running the USBBulkSourceSink example:
USB LOG: 6
USB LOG: 88
USB LOG: 12
USB LOG: 89
USB LOG: 90
USB LOG: 90
USB LOG: None
USB LOG: 90
USB LOG: None
USB LOG: None
USB LOG: 98
USB LOG: 90
USB LOG: None
USB LOG: None
USB LOG: 90
USB LOG: None
USB LOG: None
USB LOG: 98
USB LOG: 84
USB LOG: 81
USB LOG: 11
USB LOG: 88
USB LOG: 89
USB LOG: 8A
USB LOG: 90
USB LOG: 90
USB LOG: None
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I'm currently tring to understen how the CyU3PUsbInitEventLog() and CyU3PUsbGetEventLogIndex() functions works.
In the cyu3usb I found some of the description related to the hex code present in the buffer (see following list):
#define CYU3P_USB_LOG_VBUS_OFF (0x01) /* Indicates VBus turned off. */
#define CYU3P_USB_LOG_VBUS_ON (0x02) /* Indicates VBus turned on. */
#define CYU3P_USB_LOG_USB2_PHY_OFF (0x03) /* Indicates that the 2.0 PHY has been turned off. */
#define CYU3P_USB_LOG_USB3_PHY_OFF (0x04) /* Indicates that the 3.0 PHY has been turned off. */
#define CYU3P_USB_LOG_USB2_PHY_ON (0x05) /* Indicates that the 2.0 PHY has been turned on. */
#define CYU3P_USB_LOG_USB3_PHY_ON (0x06) /* Indicates that the 3.0 PHY has been turned on. */
#define CYU3P_USB_LOG_USBSS_DISCONNECT (0x10) /* Indicates that the USB 3.0 link has been disabled. */
#define CYU3P_USB_LOG_USBSS_RESET (0x11) /* Indicates that a USB 3.0 reset (warm/hot) has happened. */
#define CYU3P_USB_LOG_USBSS_CONNECT (0x12) /* Indicates that USB 3.0 Rx Termination has been detected. */
#define CYU3P_USB_LOG_USBSS_CTRL (0x14) /* Indicates that a USB 3.0 control request has been received. */
#define CYU3P_USB_LOG_USBSS_STATUS (0x15) /* Indicates completion of status stage for a 3.0 control request. */
#define CYU3P_USB_LOG_USBSS_ACKSETUP (0x16) /* Indicates that the CyU3PUsbAckSetup API has been called. */
#define CYU3P_USB_LOG_LGO_U1 (0x21) /* Indicates that a LGO_U1 command has been received. */
#define CYU3P_USB_LOG_LGO_U2 (0x22) /* Indicates that a LGO_U2 command has been received. */
#define CYU3P_USB_LOG_LGO_U3 (0x23) /* Indicates that a LGO_U3 command has been received. */
#define CYU3P_USB_LOG_USB2_SUSP (0x40) /* Indicates that a USB 2.0 suspend condition has been detected. */
#define CYU3P_USB_LOG_USB2_RESET (0x41) /* Indicates that a USB 2.0 bus reset has been detected. */
#define CYU3P_USB_LOG_USB2_HSGRANT (0x42) /* Indicates that the USB High-Speed handshake has been completed. */
#define CYU3P_USB_LOG_USB2_CTRL (0x44) /* Indicates that a FS/HS control request has been received. */
#define CYU3P_USB_LOG_USB2_STATUS (0x45) /* Indicates completion of status stage for a FS/HS control transfer. */
#define CYU3P_USB_LOG_USB_FALLBACK (0x50) /* Indicates that the USB connection is dropping from 3.0 to 2.0 */
#define CYU3P_USB_LOG_USBSS_ENABLE (0x51) /* Indicates that a USB 3.0 connection is being attempted again. */
#define CYU3P_USB_LOG_USBSS_LNKERR (0x52) /* The number of link errors has crossed the threshold. */
#define CYU3P_USB_LOG_LTSSM_CHG (0x80) /* Base of values that indicate a USB 3.0 LTSSM state change. */
but his list not contain all the hex code has is shown in the following log make by me:
0x89: ???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I'd also appreciate to have a complete documentation about the USB-logs. Without having this the logs are a quite senseless.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content