USB Forum Discussions

Is it possible to use a pull-up or pull-down on a GPIO that is used by the GPIF?  If so, how do I go about implementing this?

I am using the GPIF as a 32-bit Slave FIFO with 2-bit addressing.  I would like to know if there is a way to determine if the GPIF interface goes "dry" or empty while waiting for data from the GPIF master.

Hi,

I am trying to get SPI boot to work on the DVK board. I already have setup the PMODE pins to 1F0, to boot from SPI and on fail boot via USB. The Jumpers 101,102,103,104 are all set to [2<->3].

When I try to upload a firmware .img file through the Cypress Control Center, I can see on the lines SCK and SSN that the upload is in progress, but the SPIMISO and SPIMOSI lines are all the time low. The same issue I can see after I press the reset button on the FX3 DVK board. FX3 is trying to load data from the SPI flash. The SSN and SCK is working fine but the MOSI and MISO also always low.

The resistors R246 and R252 are both not on the board as described in the ...

CYUSB3KIT-001 EZ-USB FX3 Development Kit Guide, Doc. #: 001-70237 Rev. *B

.. document.

I also have the same result when I upload the firmware through j-link debugger. Is there a hardware failure or are the GPIO pins defect?

thanks,

lumpi

Hello All,

If I load the default configuration file provided by Cypress (when I installed the drivers) from the directory C:\Cypress\USB\CY4605-HX2LP\1.0\Software\Config_file\2_port.iic for CY7C65620 into the CY7C65630 part, will it function correctly?

Since CY7C65620 is 2-port hub and when the same config file is loaded into a 4-port hub part, will only 2 ports be enabled?

If a config file has already been loaded into a device using Primer.exe, how can I load different config file into the same device. When I use Blaster.exe to do a Read From EEPROM, I get a message " Cannot Open Device" and I cannot erase the EEPROM also using the blaster application.

Thank you for the support.

I am working to create firmware for USB Video class, and I am using the USB VideoClassBulk and the HD example to send uncompressed data.  So far, I seem to be succesful in transmitting test patterns (using the DMA as the source), but when I use USB Device Viewer (from Visual Studio) to view the USB descriptors, I see some errors related to the Endpoint compansion descriptor.  Here is the suspect code:

    /* Video control status interrupt endpoint descriptor */
    0x07,                                                             /* Descriptor size */
    CY_U3P_USB_ENDPNT_DESCR,        /* Endpoint descriptor type */
    CY_FX_EP_CONTROL_STATUS,           /* Endpoint address and description */
    CY_U3P_USB_EP_INTR,                        /* Interrupt end point type */
    0x00,0x04,                                                   /* Max packet size = 1024 bytes */
    0x01,                                                            /* Servicing interval */

    /* Super speed endpoint companion descriptor */
    0x06,                                                            /* Descriptor size */
    CY_U3P_SS_EP_COMPN_DESCR,    /* SS endpoint companion descriptor type */
    0x00,                                                            /* Max no. of packets in a Burst : 1 */
    0x00,                                                            /* Mult.: Max number of packets : 1 */
    0x00,0x04,                                                  /* Bytes per interval : 1024 */

This is what USB Device Viewer shows:

          ===>Endpoint Descriptor<===
bLength:                                  0x07
bDescriptorType:                   0x05
bEndpointAddress:               0x82  -> Direction: IN - EndpointID: 2
bmAttributes:                          0x03  -> Interrupt Transfer Type, Usage Type = Periodic

*!*ERROR:     Endpoint Companion Descriptor missing
wMaxPacketSize:                  0x0400
bInterval:                                 0x01
*!*CAUTION:  Unknown bDescriptorSubtype
          ===>Descriptor Hex Dump<===
bLength:                                  0x06
bDescriptorType:                   0x30
06 30 00 00 00 04

Any thoughts for why this is happening?  I tried this with the supplied code, and I see the same error. 

As I said, I am still getting video, so this is not a fatal error, but I get concerned when I see these things.  Any ideas?

Thanks

MM

 Hey all -

I'm attempting to write an *.img file to the FX3 (sitting on the FX3 DVK board) from the command-line on a GNU/Linux system, and am receiving a return code of -9.  I have a couple of questions:

1) Can bix, hex, ihx, etc., files be written to the FX3 RAM / EEPROM, as you could with the FX2, or do they need to be img files?

2) Are these the only instructions regarding how to write firmware directly to the FX3 RAM?  

     http://www.cypress.com/?app=forum&id=167&rID=53176

I would love to see a more in-depth instruction list, but that is the only thing I have been able to find so far.

3) Is there a location that I can look up the error codes, e.g., the '-9' that I am seeing now?

Thanks!

Cheers,

Ben