USB superspeed peripherals Forum Discussions

Hi,

In new revision *W of document "CYUSB301X/CYUSB201X, EZ-USB® FX3: SuperSpeed USB Controller"

pin D11 or GPIO[60], which was an output is now labled as NC pin without any explanations.

I successfully used this pin as output earlier. Why is it NC now? Can I continue to use in with new revisions of fx3 chip silicon?

Regards

Previously I have developed the windows application. It import cyAPI.lib file when linking. Now I developed the FX3 windows application, can I use cyAPI.lib for FX2LP. I compare the cyAPI.lib for FX2LP and FX3 byte by byte, I find differences. Does cyAPI.lib contains implementation or it links to other file in running phase?

What decides friendly name of FX3 devices. I search in the firmware and can not find the setting of the friendly name.But the cy console shows the friendly name.

If I modify the product ID in the descriptor for USB2.0 and USB3.0 in the firmware example. After I download the firmware, windows begins to install driver for new device, but it fails, cy cosole displays nothong. If I modify the product ID to equal to that of a FX2LP based device developed previously, cy consolel recoganises it as a FX2LP device. How to explain these?

What is big endian and little endian for FX3 Firmware? When I debug FX3 firmware using segger GDB, I should choose little endian or bit endian in the GDB GUI.

Hi,

I've downloaded Linux SDK; cd cyusb_linux_1.0.5, make; cd cyusb_linux_1.0.5/src, make.

dgc@ensigma-lab: ~/shared/USB/FX3_SDK_1.3.4_Linux/cyusb_linux_1.0.5/src$ make

g++ -o 00_fwload            00_fwload.cpp            -L ../lib -l cyusb

g++ -o 01_getdesc           01_getdesc.cpp           -L ../lib -l cyusb

g++ -o 03_getconfig         03_getconfig.cpp         -L ../lib -l cyusb

g++ -o 04_kerneldriver      04_kerneldriver.cpp      -L ../lib -l cyusb

g++ -o 05_claiminterface    05_claiminterface.cpp    -L ../lib -l cyusb

g++ -o 06_setalternate      06_setalternate.cpp      -L ../lib -l cyusb

g++ -o 08_cybulk            08_cybulk.cpp            -L ../lib -l cyusb -l pthread

g++ -o 09_cyusb_performance 09_cyusb_performance.cpp -L ../lib -l cyusb -l usb-1.0

g++ -o download_fx2         download_fx2.cpp         -L ../lib -l cyusb

g++ -o download_fx3         download_fx3.cpp         -L ../lib -l cyusb

g++ -o cyusbd               cyusbd.cpp               -L ../lib -l cyusb

gcc -o config_parser        config_parser.c          -L ../lib -l cyusb

01_getdesc reports "No device found".

dgc@ensigma-lab: ~/shared/USB/FX3_SDK_1.3.4_Linux/cyusb_linux_1.0.5/src$ ./01_getdesc

No device found

HW is running fine in Windows environment. How to solve this issue?

Hi all,

I am working on Cypress fx3 GPIF II . I have doubt on "CyFxSlFifoApplnStart" and "CyFxSlFifoApplnStop" funtion in slave FIFO. This function is called inside USB event of

CyFxSlFifoApplnUSBEventCB (CyU3PUsbEventType_t  evtype, uint16_t evdata).

Q1. is it possible to call "CyFxSlFifoApplnStart" in SlFifoAppThread_Entry?. and what will happen ?.

Q2. is it need to call every time CyFxSlFifoApplnStop funtion?. if it is not calling what will happen?.

Thank you

Best Regards,

Thrimurthi M

We are beginning a FX3 design where the FX3 back end interface is an FPGA and the preferred use case is :

  -    Boot from GPIF II, presumably Sync ADMux.

  -    After loading of an image, the FX3 changes GPIF configuration to Sync Slave FIFO (the required data interface).

It appears to me that selection of PMODE = F00 (Sync ADMux) must define some amount of the GPIF interface, but it is unclear to me if, after firmware loading, the FX3 can override the GPIF interface definition to Sync Slave FIFO.  Is this possible?  Or is there a different suggested mechanism for loading the FX3 but operating as a sync slave fifo?

I cannot find this scenario detailed in any app notes.  If there is one, please point me to it.

Thanks

Hi,

How to solve below error?

dgc@ensigma-lab: ~/shared/USB/FX3_SDK_1.3.4_Linux/cyusb_linux_1.0.5$ sudo ./install.sh

Your current directory is /user/dgc/shared/USB/FX3_SDK_1.3.4_Linux/cyusb_linux_1.0.5. This is where the cyusb_suite software will be installed...

g++ -fPIC -o lib/libcyusb.o -c lib/libcyusb.cpp

g++ -shared -Wl,-soname,libcyusb.so -o lib/libcyusb.so.1 lib/libcyusb.o -l usb-1.0 -l rt

cd lib; ln -sf libcyusb.so.1 libcyusb.so

rm -f lib/libcyusb.o

rm -f moc_controlcenter.cpp

rm -f ui_controlcenter.h

rm -f controlcenter.o main.o fx2_download.o fx3_download.o streamer.o moc_controlcenter.o

rm -f *~ core *.core

/usr/lib/x86_64-linux-gnu/qt4/bin/uic controlcenter.ui -o ui_controlcenter.h

g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o controlcenter.o controlcenter.cpp

controlcenter.cpp:1:18: fatal error: QtCore: No such file or directory

compilation terminated.

Makefile:221: recipe for target 'controlcenter.o' failed

make: *** [controlcenter.o] Error 1