<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>usb fails to enumarate</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/24279/usb-fails-to-enumarate</link><description> 
I developed a firmware for FX2 . I tested it in a board with fx2
and spartan FPGA. It worked fine . Now I want to use the same
firmware for another board. Iam using cypress driver. When I download
the firmware, the device does not enumarate as cypress</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: usb fails to enumarate</title><link>https://community.arm.com/thread/135593?ContentTypeID=1</link><pubDate>Tue, 18 Nov 2008 06:01:09 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:eca805c9-9b53-4979-8889-e956fcdd90a8</guid><dc:creator>Tsuneo Chinzei</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;I changed the port and it is working fine&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Aha, it was surely a hardware problem, but not on the board
:-)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;&amp;quot;How to get the unique PID and VID for my device?&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
&lt;b&gt;a) For temporary use of development,&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;
you can apply any VID/PID, unless the pair conflicts with existing
pairs on your PC. The VID/PID pairs registered to your PC are listed
up on this registry key.&lt;/p&gt;

&lt;p&gt;

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_????&amp;amp;Pid_????&lt;/p&gt;

&lt;p&gt;
Choose a VID which doesn&amp;#39;t appear on above registry, for example
0xFFFF.&lt;/p&gt;

&lt;p&gt;
Then, search this candidate VID on the registered INF files&lt;br /&gt;
The INF files are held in this folder.&lt;/p&gt;

&lt;p&gt;
C:\Windows\inf\&lt;/p&gt;

&lt;p&gt;
As the default, this folder is invisible. You&amp;#39;ll need to change
the folder option to see this folder on the explorer.&lt;br /&gt;
Search the VID string, for example &amp;quot;VID_FFFF&amp;quot;, in all .inf files in
this folder using an utility like Grep, or multi-file search of your
favorite text editor, or Windows search companion (search
contents).&lt;/p&gt;

&lt;p&gt;
No INF file has the VID string, the candidate VID is free on your
PC.&lt;br /&gt;
You can use any PID under this VID.&lt;/p&gt;

&lt;p&gt;
&lt;b&gt;b) For production,&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;
- Buy a VID from USB.org - US$2,000&lt;br /&gt;
&lt;a href="http://www.usb.org/developers/vendor/"&gt;www.usb.org/.../&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;
- USB device manufacturers distribute unique PID under their VID,
for sales promotion.&lt;br /&gt;
SiLabs, FTDI, Microchip, etc.&lt;/p&gt;

&lt;p&gt;
Tsuneo&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: usb fails to enumarate</title><link>https://community.arm.com/thread/125082?ContentTypeID=1</link><pubDate>Tue, 18 Nov 2008 02:43:01 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f66e27d0-f5a6-4413-8d75-e8142be38a9d</guid><dc:creator>vanitha kutti</dc:creator><description>&lt;p&gt;&lt;p&gt;
I changed the port and it is working fine . I need one more help
also. How to get the unique PID and VID for my device?&lt;br /&gt;
thanks&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: usb fails to enumarate</title><link>https://community.arm.com/thread/114433?ContentTypeID=1</link><pubDate>Tue, 18 Nov 2008 01:06:24 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f08d682f-7350-41a9-b825-9f118d564bb5</guid><dc:creator>vanitha kutti</dc:creator><description>&lt;p&gt;&lt;p&gt;
yes my first board is working good.MY second board is comercial
board purchased newly.so there cannot be any problems as u have
mentioned in (b).&lt;br /&gt;
I tried a USB trace to see what is happening during enumaration .PNP
is not supported it says . i dont know the reasons for it.&lt;/p&gt;

&lt;pre&gt;
PNP 6.443719 QUERY_DEVICE_RELATIONS OUT 0 \Device\USBPDO-7 0x89781008 STATUS_NOT_SUPPORTED 0

#350 PNP 6.443722 QUERY_DEVICE_RELATIONS IN 0 \Device\USBPDO-7 0x89781008 STATUS_NOT_SUPPORTED 0

#351 PNP 6.443725 QUERY_DEVICE_RELATIONS OUT 0 \Device\USBPDO-7 0x89781008 STATUS_NOT_SUPPORTED 0

#352 PNP 6.443726 QUERY_DEVICE_RELATIONS IN 0 \Device\USBPDO-7 0x89781008 STATUS_NOT_SUPPORTED 0

#353 PNP 6.443898 SURPRISE_REMOVAL OUT 0 \Device\USBPDO-7 0x89781008 STATUS_SUCCESS 0

#354 PNP 6.443978 SURPRISE_REMOVAL IN 0 \Device\USBPDO-7 0x89781008 STATUS_SUCCESS 0

#355 CLEANUP 6.452120 - OUT 0 \Device\USBPDO-7 0x89781008 STATUS_SUCCESS 0

#356 PNP 6.465621 REMOVE_DEVICE OUT 0 \Device\USBPDO-7 0x89781008 STATUS_SUCCESS 0

#357 PNP 6.465677 REMOVE_DEVICE IN 0 \Device\USBPDO-7 0x89781008 STATUS_SUCCESS 0

#358 PNP 26.352920 QUERY_ID OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#359 PNP 26.352944 QUERY_ID IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#360 PNP 26.352948 QUERY_CAPABILITIES OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#361 PNP 26.352950 QUERY_CAPABILITIES IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#362 PNP 26.352952 QUERY_DEVICE_TEXT OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#363 PNP 26.352954 QUERY_DEVICE_TEXT IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#364 PNP 26.352956 QUERY_DEVICE_TEXT OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#365 PNP 26.352958 QUERY_DEVICE_TEXT IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#366 PNP 26.352960 QUERY_ID OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#367 PNP 26.352961 QUERY_ID IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#368 PNP 26.353091 QUERY_ID OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#369 PNP 26.353094 QUERY_ID IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#370 PNP 26.353097 QUERY_ID OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#371 PNP 26.353099 QUERY_ID IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#372 PNP 26.353116 QUERY_RESOURCE_REQUIREMENTS OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#373 PNP 26.353147 QUERY_RESOURCE_REQUIREMENTS IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#374 PNP 26.353178 QUERY_BUS_INFORMATION OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#375 PNP 26.353180 QUERY_BUS_INFORMATION IN 0 0x897F96D0 0x89765008 STATUS_SUCCESS 0

#376 PNP 26.353248 QUERY_RESOURCES OUT 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#377 PNP 26.353250 QUERY_RESOURCES IN 0 0x897F96D0 0x89765008 STATUS_NOT_SUPPORTED 0

#378 PNP 45.124684 QUERY_DEVICE_RELATIONS OUT 0 0x897F96D0 0x898726C0 STATUS_NOT_SUPPORTED 0

#379 PNP 45.124687 QUERY_DEVICE_RELATIONS IN 0 0x897F96D0 0x898726C0 STATUS_NOT_SUPPORTED 0

#380 PNP 45.126834 REMOVE_DEVICE OUT 0 0x897F96D0 0x898726C0 STATUS_NOT_SUPPORTED 0

#381 PNP 45.126857 REMOVE_DEVICE IN 0 0x897F96D0 0x898726C0 STATUS_SUCCESS 0

&lt;/pre&gt;

&lt;p&gt;
thanks for lot of information. it was really helpull to me&lt;br /&gt;
punitha&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: usb fails to enumarate</title><link>https://community.arm.com/thread/101325?ContentTypeID=1</link><pubDate>Mon, 17 Nov 2008 12:59:05 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:936f60e7-1e87-4225-89b7-70d0cd930a75</guid><dc:creator>Tsuneo Chinzei</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;Now I want to use the same firmware for another board. ...&lt;br /&gt;
When I download the firmware, the device does not enumarate as
cypress sample device , some times it is taking a long time to
enumarate . When it does not enumarate either it goes as unknown
device or it is not listed in the devices list&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Does your first board still work fine on the PC?&lt;br /&gt;
Then it isn&amp;#39;t a problem of PC side, rather hardware problem on the
new board.&lt;/p&gt;

&lt;p&gt;
a) Rush current on power up&lt;br /&gt;
Is it a bus-powered device?&lt;br /&gt;
Do you see any voltage drop on USB VBUS line caused by the FPGA power
up?&lt;br /&gt;
An external power source may be required, if the power up takes too
much current.&lt;/p&gt;

&lt;p&gt;
b) Other points are,&lt;br /&gt;
- Crystal OSC stability&lt;br /&gt;
- Noise&lt;br /&gt;
- Soldering crack&lt;br /&gt;
etc.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;i&gt;&amp;quot;I used the same PID and VID of the previous board . Can I use the
same PID and VID.?&amp;quot;&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
As long as the same USB configuration (device and configuration
descriptor set) is kept on the firmware, you can apply the same
VID/PID, even to a MCU from another manufacturer.&lt;/p&gt;

&lt;p&gt;
Anyway, isn&amp;#39;t it better to change the VID/PID, as you are using
the VID/PID of cypress sample device :-)&lt;/p&gt;

&lt;p&gt;
If you connect multiple devices of the same VID/PID to single PC,
assign unique serial number to each device, to identify the
devices.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It sound like the enumeration is disturbed.&lt;br /&gt;
Not all of software USB sniffers can catch USB enumeration fully.&lt;br /&gt;
These sniffers can.&lt;/p&gt;

&lt;p&gt;
USBlyzer&lt;br /&gt;
&lt;a href="http://www.usblyzer.com/"&gt;http://www.usblyzer.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;
SourceUSB&lt;br /&gt;
&lt;a href="http://www.sourcequest.com/"&gt;http://www.sourcequest.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;
Most of sniffers attach a probe (filter driver) just to a
high-level device driver. Such a sniffer can&amp;#39;t catch early
enumeration sequence, because high-level device driver is assigned to
the device in the later stage of enumeration. Above sniffers attach
probes to low-level system drivers, too, to catch the early
enumeration stage.&lt;/p&gt;

&lt;p&gt;
Once enumerated, any sniffer can catch the traffic.&lt;/p&gt;

&lt;p&gt;
Tsuneo&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: usb fails to enumarate</title><link>https://community.arm.com/thread/101322?ContentTypeID=1</link><pubDate>Mon, 17 Nov 2008 10:01:48 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:24973f64-73dc-4231-876f-291b4cc07a79</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
Good! You are half-way there :)&lt;/p&gt;

&lt;p&gt;
Now switch over to a Google window and enter &amp;quot;what is a usb
sniffer&amp;quot;.&lt;/p&gt;

&lt;p&gt;
If still wondering after checking out that information, then
please come back with more specific questions.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: usb fails to enumarate</title><link>https://community.arm.com/thread/76886?ContentTypeID=1</link><pubDate>Mon, 17 Nov 2008 09:58:49 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:0e28afd4-d4f6-4c5f-ba07-f02b5c89fbf4</guid><dc:creator>punitha kutti</dc:creator><description>&lt;p&gt;&lt;p&gt;
what is a USB sniffer? I do not know anything about it&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: usb fails to enumarate</title><link>https://community.arm.com/thread/52864?ContentTypeID=1</link><pubDate>Mon, 17 Nov 2008 09:49:24 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:24dd87c5-5f78-4b5d-8dbc-48a0b227f91a</guid><dc:creator>Catcus Blip</dc:creator><description>&lt;p&gt;&lt;p&gt;
have you used a USB sniffer to see what&amp;#39;s happening on the
bus?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>