USB3.0开发笔记课件

1、20130819 （周一）..2.13.14. CyU3PMemSet (uint8_t *)&io_cfg, 0, sizeof(io_cfg); io_cfg.isDQ32Bit = CyFalse; io_cfg.useUart = CyTrue; io_cfg.useI2C = CyFalse; io_cfg.useI2S = CyFalse; io_cfg.useSpi = CyFalse; io_cfg.lppMode = CY_U3P_IO_MATRIX_LPP_UART_ONLY; /* GPIO 45 is used as

2、 input pin. GPIO 21 is also used but cannot * be selected here as it is part of the GPIF IOs (CTL4). Since * this IO is not used, it can be overridden to become a GPIO by * invoking the CyU3PDeviceGpioOverride call. */ io_cfg.gpioSimpleEn0 = 0; io_cfg.gpioSimpleEn1 = 0x00002000; /* GPIO 45 */ io_cfg

3、.gpioComplexEn0 = 0; io_cfg.gpioComplexEn1 = 0;status = CyU3PDeviceConfigureIOMatrix (&io_cfg);15. /* Configure GPIO 45 as input with interrupt enabled for both edges */ gpioConfig.outValue = CyTrue; gpioConfig.inputEn = CyTrue; gpioConfig.driveLowEn = CyFalse; gpioConfig.driveHighEn = CyFalse;

4、gpioCrMode = CY_U3P_GPIO_INTR_BOTH_EDGE;apiRetStatus = CyU3PGpioSetSimpleConfig(45, &gpioConfig);16. /* Override GPIO 21 as this pin is associated with GPIF Control signal. * The IO cannot be selected as GPIO by CyU3PDeviceConfigureIOMatrix call * as it is part of the GPIF IOs. Override

5、 API call must be made with * caution as this will change the functionality of the pin. If the IO * line is used as part of GPIF and is connected to some external device, * then the line will no longer behave as a GPIF IO. Here CTL4 line is * not used and so it is safe to override. */ apiRetStatus =

6、 CyU3PDeviceGpioOverride (21, CyTrue); /* Configure GPIO 21 as output */ gpioConfig.outValue = CyFalse; gpioConfig.driveLowEn = CyTrue; gpioConfig.driveHighEn = CyTrue; gpioConfig.inputEn = CyFalse; gpioCrMode = CY_U3P_GPIO_NO_INTR;apiRetStatus = CyU3PGpioSetSimpleConfig(21, &gpioConfig

7、);17. /* Callback funtion for the DMA event notification */voidCyFxUartLpDmaCallback ( CyU3PDmaChannel *chHandle, /* Handle to the DMA channel. */ CyU3PDmaCbType_t type, /* Callback type. */ CyU3PDmaCBInput_t *input) /* Callback status. */ CyU3PReturnStatus_t status; if (type = CY_U3P_DMA_CB_PROD_EV

8、ENT) /* This is a produce event notification to the CPU. This notification is * received upon reception of every buffer. The buffer will not be sent * out unless it is explicitly committed. The call shall fail if there * is any application error. */ status = CyU3PDmaChannelCommitBuffer (chHandle, in

9、put->buffer_p.count, 0); if (status != CY_U3P_SUCCESS) CyFxAppErrorHandler (status); 18. 需要掌握的usb固件，有实现FIFO访问模式的数据传输例子 和实现vendor requests到IIC访问的例子和实现vendor requests到GPIO模拟的SPI访问例子201309011. 今天开始测试直接在开发板上跑通上述三个案例。2. 首先是IIC register mode调试，固件非常完整，可以实现iic到eeprom的访问。但是访问来自于CY_U3P_USB_VENDOR_RQT，这个指令需

10、要上位控制界面发送出来。 /* 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_P

11、OS); 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);调试界面上，bRequest=0xba, case CY_FX_RQT_I2C_EEPROM_WRIT

12、E:, bRequest=0xbb, case CY_FX_RQT_I2C_EEPROM_READ:,wValue i2cAddr = 0xA0 | (wValue & 0x0007) << 1); , CyFxUsbI2cTransfer (wIndex, i2cAddr, wLength, wIndex= iic register address, 16bit;wLength = 64, 3. 然后是SPI GPIO register mode，使用GPIO作为SPI管脚的模式。bRequest=0xc2, CY_FX_RQT_SPI_FLASH_WRITE, bReq

13、uest=0xc3, CY_FX_RQT_SPI_FLASH_READ,bRequest=0xc4, CY_FX_RQT_SPI_FLASH_ERASE_POLL,wValue 在 erase模式下 (wValue) ? CyTrue : CyFalsewIndex =pageAddress for FLASH经过测试，产生错误报告，应该是由于开发板上并不存在gpio口连接到了SPI flash上面。故而改为SPI register mode， 使用CY3014指定的SPI口连接到flash芯片。调试有反应，但是数据返回错误，重新返回详读flash操作手册。 flash的写入需要首先进行erase，然后才可以进行写入。这是器件的物理特性决定的，所有调试的时候也是要先erase该sector。4. 接下来需要调试的是bulk数据传输模式。5. Flag A和Flag B的意思做一个FPGA到PPort的最简单的写入逻辑，if(flag_a) n_sl_wr<=0;6. 官方给出的cmos直接到GPIF 的状态机：USB video class（又称为USB video device class or UVC）就是USB dev