USB superspeed peripherals Forum Discussions

Hi,

I accidentally flashed RAM instead of flashing SPI Flash from Cypress Control Center. I have a Denebola kit from e-con and now the camera doesn't stream image.

Can you please suggest a workaround?

Thanks!

 I have setup a DMA AUTO with two p-port sockets 0 and 3. So I have data rx on 0 and tx on 3. The flag on 3 seems to do something I dont expect although it may be correct. Its the dma rdy flag. It seems to go low when the rx starts. There is a dma rdy on the rx too which goes low then high once the rx ends. The tx dma rdy godes high again once the tx ends. Is this corrrect? Also is there anything wrong with this setup? I realsie its a bit strange to send the rx data back out but I want to test something.

Thanks

     Hi!

For our design using a FX3 I am looking for a FX3 firmware example using 4 endpoints.

The GPIF II interface is used as a sync. FIFO interface were the FPGA is the master.

The GPIF designer contains a predefined project for this. (sync_slave_fifo_2bit)

The SDK also has a predefined project (SlaveFifoSync), but it seems to only support two endpoints.

Is there a firmware example using four endpoints?

Or is the predefined project easily adapted by just creating two additional endpoints?

With regards,

Jacob

Hi,

We want to use our next device (with includes an FX3) with the WinUSB device driver, including the 'WinUSB device' option when using Windows 8.0 and up.

On the DVK, this works fine with a slightly changed SlaveFifoSync sample firmware from the FX3 SDK. It handle the three calls that are necessary in CyFxSlFifoApplnUSBSetupCB.

- The Microsoft OS String Descriptor request

- The Extended Compat ID OS Feature Descriptor (wIndex = 0x04)

- The Extended Properties OS Feature Descriptor (wIndex = 0x05)

For 'Vendor Code' we used either the value 0xAB (which is what Cypress has in its sample) or 0x01 (which is what Microsoft has in its sample). The DVK with this firmware works fine both on Windows 7 and Windows 8.1

Now comes the strange part:

On our prototype, the WinUSB device recognition works fine on Windows 8.1 when using 0x01 as 'Vendor Code'. There is now a problem on Windows 7, the device fails during enumeration.

When using 0xAB as 'Vendor Code', the device works fine on Windows 7, but the WinUSB device recognition on Windows 8.1 does not work.

All this happens using the exact same code that we loaded in the DVK, and which works fine there.

We do not understand how identical code can act differently on both devices, since the connection between PC and FX3 is really straightforward.

Any ideas would be welcome.

Regards, Matt

If you have issues using OpenOCD 0.8.0, try these:

1. rebind the adapter to the WinUSB driver. See this link for instructions.

2. copy the following config into a file called fx3.cfg and put it into the [openocd_install_dir]/scripts/target folder

############################################
# Target:    Cypress EZ-USB FX3 ARM926EJ-S #
############################################

if { [info exists CHIPNAME] } {
 set _CHIPNAME $CHIPNAME
} else {
 set  _CHIPNAME fx3
}

if { [info exists ENDIAN] } {
 set _ENDIAN $ENDIAN
} else {
 set _ENDIAN little
}

if { [info exists CPUTAPID] } {
 set _CPUTAPID $CPUTAPID
} else {
 set _CPUTAPID 0x07926069
}

# Reset configuration
reset_config trst_and_srst srst_pulls_trst
adapter_nsrst_delay 200
jtag_ntrst_delay 200

jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID

########################
# Target configuration #
########################

set _TARGETNAME $_CHIPNAME.cpu
target create $_TARGETNAME arm926ejs -endian $_ENDIAN -chain-position $_TARGETNAME -variant arm926ejs

adapter_khz 1000

3. run openocd.exe as follows:

openocd-x64-0.8.0.exe -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -f target/fx3.cfg

Hi,
urgently looking for FX3 well expirienced developer.
Can work on short projects and lontime as well.

Please send me ur skype for further details.

Yury

 I'm trying to access the SPI block without using the Cypress functions.  I have clk, ssn and mosi working properly.  But the miso line is pulled low as soon as I set the GCTL_IOMATRIX register to either GPIO+SPI or UART+SPI+I2S.  I'm not sure what I'm not doing.  Do I have to explicitly set that pin as an Input in it's GPIO_SIMPLE register or something?

Any help on the sequence needed to bring up the SPI block would be appreciated.  I haven't found any examples that include the register accesses.  If you know of any please let me know.

Thanks.

 Dear All:

I am pretty new to develop USB3.0 on Eclipse platform. after installed the FX3 development tools.

appling Cross ARM compiler for this project, choose arm926ej-s as the processor.

My processing :  1: New C++ project

                               2: import exsiting code 

                              3: start  bulding project.

                              4: 

 it fault to generate ELF file,

is there any thing worng with the setting?

is anybody can give me information for solve the such kind problem?

Thank you for visting my message.

compiler message as below