USB low-full-high speed peripherals Forum Discussions
I would like to develop a firmware for our application. I am manipulating the bulk loop example code. One modification I need is to run the device in high speed mode(our device is fx2lp and is high speed capable). I modified the code this way:
There is a function named HighSpeedCapable(). I manipulated the code in such a way that it always returns true. but when I download the iic file on my device and open the cy console, I notice that the maximum packet size for endpoints is set to 64. I guess in the dscr.a51 file, the descriptor for full speed mode containts maximum packet size 64 and the device dscr table for high speed mode containts the value 1024. So what is wrong with that? does it mean it is not running in high speed mode though I have set the return vaule of HighSpeedCapable function to true?
I have another question : when I want to use the assembly directive " org (($ / 2) +1) * 2" i get the error : bad relocatable expression. what is the problem?
In general, default firmware is loaded, which enumerates Cypress board with specific VID/PID. (04b4 : XXXX type)
I wish to load a short descriptor file from EEPROM, which helps bootloader to enumerate with my chosen VID/PID for loadinf firmware from host via USB. or am i forced to enumerate with Cypress VID/PID for USB boot ?
Thank youShow Less
Iam working with the EzUSB driver since a long time. Now Iam switching to CyUSB Driver. Everything is working fine except reading data through EP1. With the EzUSB it was no problem to read/write the bidir EP1 since there are different IOCTL's for reading/writing and the driver handles the direction. I couldn't find this feature in the CyUSB driver because there is only the xx_SEND_NON_EP0_xx IOCTL. This is OK for EP2..EP8 since the direction is determined in the config but EP1 is BIDIR by nature, writing works perfect but reading doesn't..Question: is there any way to switch the direction of EP1?Show Less
I am using a cy7c68 usb controller. I am using a FPGA to simulate the behavior of an EEprom for cy7c68. I have successfully got C0 boot mode working. ( that is I have revised the inf file with th PID and VID that is stored on EEprom and the usb device is successfully recognized by the computer).
But I couldn't get C2 boot mode working. I have done as exactly as it is said in the document and when I verify the I2C signals they are all working properly that is when EEprom acknowledges C2 boot mode, cy7c68 starts to read the specified bytes and at the end of the data record I assert the specific bytes required to bring 8051 out of reset. but the usb device is not recognized by the computer. Is there anyway to debug the problem? or maybe I have missed out an action required to get 8051 working? ( such as using the "wake up" pin!!?) . as I said when I inspect I2C signals, the behavior of cy7c68 is quite reasonable. I would like to add that I am almost sure about the correctness of the hex data stored on eeprom.
tnx in advanceShow Less
I have the following issue with an USB device working with a Cypress FX2LP: depending on the USB port and the OS (happens mostly on Windows XP SP3), the device fails to recover from the hibernate mode. When the PC exits from the hibernate mode, the device is still recognized by the device manager but the soft I developed (in C++) to manage the device won't reconnect to it.
In the software the communication with the USB driver is managed by Windows (through the method DeviceIOControl). At the exit of hibernate mode, the DeviceIOControl function doen't seem to get any answer from the FX2 (no byte received when sending a command). I tried as well to ask for a reset directly to the cypress driver via the CyUSBDriver class (CyAPI.h), but it didn't work either.
Do you have any knowledge of methods or functionalities of the FX2 that would manage a proper recovering from hibernate mode? Perhaps would it be better not to use the Windows access to the usb driver?
I hope I was clear enough. Don't hesitate to ask for further information or explanation.
Thank you for your answer,
On the CyConsole.pdf user's guide at the very bottom there is a chapter explaining how to use CyConsole to connect to a driver with a different GUID. More precisely there is written:
CyConsole was designed with provision for connecting to other CyUSB.sys drivers that have different GUIDs. On the Misc. tab sheet you will notice a drop-down list labelled Access devices attached to this driver . The drop-down list is populated with the file names of all copies of CyUSB.sys that are installed in the system. (It gathers the list from the Windows registry.)
According to this my first question is: if I want my custom driver (with my custom VID and GUID) is it ok to copy the cyusb.sys and the cyusb.inf, change their name to mydevice.sys and mydevice.inf and modify the INF file with my VID and GUID?
Secondly, I tried this approach, then I signed my driver and I installed it (now it is located under System32\drivers\mydevice.sys) but still I do not see any other driver in the drop-down list in the Misc. tab. What am I missing? (I'm using Windows 7 64bit).Show Less
I want to design a programmer for programming hearing aids.I want to use CY7C64713-128AXC
Suggest me a suitable PCB Desing Software please!
I have the CY3684 kit that i am using as a starting point for implenting the cy7c8013a into our custom boards.
I am trying to load the ledcycle.hex provided with install into the large EEPROM using hex2bix.exe. When I load the hex file it works fine, but when I try to load it from the EEPROM, it's not enumerating.
Here's the command i am using:
hex2bix ledcycle.hex -o ledcycle.iic -f 0xc2 -i
Eventually, I'd like to get to insert a different VID/PID.
Thanks for the help.Show Less
If I have the following inside my INF
Then suiteUSB can see my device no problem.
But my understanding was that I could change that GUID to ensure that other programs using the same GUID could not update the driver I am using.
But when I change the GUID, SuiteUSB cannot see my device any longer. I've tried using SetCustomerGUID and SetClassGUID, but they don't seem to work.
If I delete the lines above from my INF it still works. But if I change the GUID, it stops working.
So, my question is: Is SuiteUSB able to work with GUIDs other than the '959 shown above? The article "How does the CyUSB.dll recognize a cypress device" seems to suggest "yes", but the paragraph is poorly written and the grammar unclear exactly what they mean.
Hello! I'm new in the forum.I want to do a project programmer CY764713-128AXC.Unfortunately I did not find CY7C64713-128 AXC in to the library of the PCoC2 Creator! Help please!