Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Hi, I have an Analog Devices iSensor evaluation board with an onboard 68013A. The default driver coming with the board is the EzUsb.sys. The samples communicate via the bulk transfer interface. I would like to replace the EzUsb.sys driver with the CyUsb.sys driver. I test signed the 64bit CyUSB.sys driver and installed it on my Windows 7 machine. I can install the device and enumerate it. The CyUSBDevice object contains a control interface but BulkInEndPt and BulkOutEndPt is null. I can get bulk interfaces via AltInt but they do not seem to work; calling XferData on any of them always return false. Any ideas?
How many alternate interfaces does the device have???? does all of them display the same behaviour... can you hook up a CATC and check whether the endpoint stalls or NAKs..... the most possible reason behind this is that most probably the device has some header or initial transaction by which the device detects whether it is connected to the right application.... this is something you may not be sending...
The device descriptor as extracted by the USB Control Center. I think you are right about the device initialization. How can I send the initialization bytes, using the control endpoint? In the EzUsb.sys implimentation, it was also send via the bulk interface. FriendlyName="AD iSensor" Manufacturer="" Product="" SerialNumber="" Configurations="1" MaxPacketSize="64" VendorID="04 56" ProductID="EF 02" Class="FFh" SubClass="FFh" Protocol="FFh" BcdDevice="00 01" BcdUSB="02 00" Configuration="0" ConfigurationValue="1" Attributes="80h" Interfaces="1" DescriptorType="2" DescriptorLength="9" TotalLength="171" MaxPower="50" Interface="0" InterfaceNumber="0" AltSetting="0" Class="FFh" Subclass="FFh" Protocol="255" Endpoints="0" DescriptorType="4" DescriptorLength="9"
If you are able to observe and figure out the initialization part from the CATC trace then send those values by expanding the device tree in control center then selecting the endpoint over which the transfer is sent and then send the necessary data over that endpoint... it is just replicating the initialization behaviour so you'll have to use the same endpoint that is being used with ezusb.sys...
I see that Analog Devices uses a mcp_spi.sys (ezloader, firmware??) driver and load the ezusb.sys driver on top of that. If I do the same, first loading the mcp_spi.sys driver and then the cyusb driver, it works. Is there a way that I can get rid of the mcp_spi.sys driver (currently only in 32bit)?
when you hover the cursor over the sys file it would give out information right.... what does that say???? i too have the same opinion as you do... i too think it is ezloader driver... if that is the case it would contain the firmware.... what did u actually observe on the CATC trace????