Analog Devices and 68013A

	willie posted on 20 Aug 2009 3:11 AM PST Member 3 Forum Posts

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?

Re: Analog Devices and 68013A

	aasi posted on 22 Aug 2009 11:48 PM PST Cypress Employee 1090 Forum Posts

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...

Re: Analog Devices and 68013A

	willie posted on 31 Aug 2009 01:33 AM PST Member 3 Forum Posts

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"

Interface="0"
InterfaceNumber="0"
AltSetting="1"
Class="FFh"
Subclass="FFh"
Protocol="255"
Endpoints="6"
DescriptorType="4"
DescriptorLength="9"

Type="BULK"
Direction="OUT"
Address="01h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Type="BULK"
Direction="IN"
Address="81h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Type="BULK"
Direction="OUT"
Address="02h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Type="BULK"
Direction="OUT"
Address="04h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Type="BULK"
Direction="IN"
Address="86h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Type="BULK"
Direction="IN"
Address="88h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Interface="0"
InterfaceNumber="0"
AltSetting="2"
Class="FFh"
Subclass="FFh"
Protocol="255"
Endpoints="6"
DescriptorType="4"
DescriptorLength="9"

Type="INTERRUPT"
Direction="OUT"
Address="01h"
Attributes="03h"
MaxPktSize="64"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="INTERRUPT"
Direction="IN"
Address="81h"
Attributes="03h"
MaxPktSize="64"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="INTERRUPT"
Direction="OUT"
Address="02h"
Attributes="03h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="BULK"
Direction="OUT"
Address="04h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Type="INTERRUPT"
Direction="IN"
Address="86h"
Attributes="03h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="BULK"
Direction="IN"
Address="88h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Interface="0"
InterfaceNumber="0"
AltSetting="3"
Class="FFh"
Subclass="FFh"
Protocol="255"
Endpoints="6"
DescriptorType="4"
DescriptorLength="9"

Type="INTERRUPT"
Direction="OUT"
Address="01h"
Attributes="03h"
MaxPktSize="64"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="INTERRUPT"
Direction="IN"
Address="81h"
Attributes="03h"
MaxPktSize="64"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="ISOC"
Direction="OUT"
Address="02h"
Attributes="01h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="BULK"
Direction="OUT"
Address="04h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Type="ISOC"
Direction="IN"
Address="86h"
Attributes="01h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="1"

Type="BULK"
Direction="IN"
Address="88h"
Attributes="02h"
MaxPktSize="512"
DescriptorType="5"
DescriptorLength="7"
Interval="0"

Re: Analog Devices and 68013A

	aasi posted on 31 Aug 2009 01:50 AM PST Cypress Employee 1090 Forum Posts

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...

Re: Analog Devices and 68013A

	willie posted on 01 Sep 2009 04:41 AM PST Member 3 Forum Posts

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)?

Re: Analog Devices and 68013A

	aasi posted on 01 Sep 2009 06:33 AM PST Cypress Employee 1090 Forum Posts

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????

ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Cypress Perform

Analog Devices and 68013A

Re: Analog Devices and 68013A

Re: Analog Devices and 68013A

Re: Analog Devices and 68013A

Re: Analog Devices and 68013A

Re: Analog Devices and 68013A