Cannot progress beyond "USB device with DFU capabilities"

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Cannot progress beyond "USB device with DFU capabilities"

2,972件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by VigneshEP on Wed Sep 03 01:19:35 MST 2014
[list]
  [*] LPCXpresso v7.3.0 [Build 186] [2014-07-09]
[*] Win 7, 32-bit
[*] three different LPC-Link boards (11U14, 1114, 1343)
[*] two different USB cables
[*] three different direct USB ports
[*] twice reinstalled LPCXpresso
[/list]

I could not get past beyond "USB device with DFU capabilityes". I tried boot_link1 multiple times. Tried various experiments from previous posts but to no avail. Following is error log. I doubt three boards could go wrong simultaneously.

*****************************************************
*** DFU LOG FILE ***
 Creation Time : C:\Users\e3\AppData\Local\Temp\dfuApp7441537740970716268.log
*****************************************************


Open Device
Get Device Descriptor successful
Get Configuration Descriptor successful
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is operating in the DFU mode and is waiting for requests.

 Device Descriptor 
bLength: 0x12 
bDescriptorType: 0x01 
bcdUSB: 0x0200 
bDeviceClass: 0x00 
bDeviceSubClass: 0x00 
bDeviceProtocol: 0x00 
bMaxPacketSize0: 0x40 
idVendor: 0x0471 
idProduct: 0xdf55 
bcdDevice: 0x0001 
iManufacturer: 0x00 
iProduct: 0x00 
iSerialNumber: 0x00 
bNumConfigurations: 0x01 



DFU Get State successful
---> DFUState: Device is operating in the DFU mode and is waiting for requests.
Download Block Nb 0 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 1 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 2 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 3 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 4 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 5 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 6 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 7 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 8 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 9 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 10 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 11 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 12 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 13 (2048 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 14 (520 Bytes)
DFU Get State successful
---> DFUState: Device has received a block and is waiting for the host to solicit the status via DFU_GETSTATUS.
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device is processing a download operation. Expecting DFU_DNLOAD requests.
Download Block Nb 15 (0 Bytes)
DFU Get State successful
---> DFUState: An error has occurred. Awaiting the DFU_CLRSTATUS request.
DFU Get Status successful
---> DFUStatus: Received DFU_DNLOAD with wLength = 0, but device does not think it has all of the data yet.
---> DFUState: An error has occurred. Awaiting the DFU_CLRSTATUS request.
DFU Clear Status successful



 *** END OF FILE *** 
0 件の賞賛
返信
13 返答(返信)

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgrzywnowicz on Mon Jun 06 06:46:20 MST 2016
Yes - I am using only laptop with lpcxpresso connected directly to it.

I tried to sniff some logs from USB. What I found out is:
000357: Control Transfer (UP), 2016-06-06 14:43:50.0688483 +0.0001633. (1. Device: USB Device with DFU Capabilities) Status: 0x00000000
Pipe Handle: Control Pipe
Setup Packet
000358: PnP Event: Surprise Removal (UP), 2016-06-06 14:43:50.0959062 +0.0270579 (1. Device: USB Device with DFU Capabilities)
The USB device has just been disconnected from the system.

000359: PnP Event: Device Disconnected (UP), 2016-06-06 14:43:50.1134546 +0.0175484 (1. Device: USB Device with DFU Capabilities)
The USB device has just been removed from the system, all drivers unloaded.

000360: PnP Event: Device Connected (UP), 2016-06-06 14:43:50.3382008 +0.2247462 (1. Device: USB Device with DFU Capabilities)
The USB device has just been connected to the system.

After those events I see "USB Device with DFU capabilities" but not the lpc link.

Regarding above logs: Is this "Surprise Removal" expected?

0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Mon Jun 06 05:31:23 MST 2016
So have you tried going through the troubleshooting section towards the bottom of https://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link, which talks about use of hubs, cables, etc ?

Regards,
LPCXpresso Support
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgrzywnowicz on Mon Jun 06 04:49:31 MST 2016
I am attaching log. Hope it will help :)
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgrzywnowicz on Fri Jun 03 07:04:39 MST 2016
I have copy-pasted original post and added my comment below. That's why the path contains old version. I am using LPCXpresso v8.1.4 [Build 606] [2016-03-14].
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Fri Jun 03 06:21:06 MST 2016
How about trying with a more recent version of LPCXpresso? v7.3.0 is pretty old - they are shipping 8.1.4 now (and the last version of the v7 stream was v7.9.2) - you are very out of date.
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by pgrzywnowicz on Fri Jun 03 04:23:33 MST 2016
Hi,

Could you please help me with my issue? I am experiencing timout during Initializing LPC-Link (HID). I am using LPCXpresso LPC1200 RevB. Board works fine on different computer but unfortunatelly not on mine.

1) Disconnect all LPCXpresso / LPC-Link's from your computer.
OK

2) Disconnect all other non-essential USB devices from your computer as well. If your PC is a laptop, please also ensure that you remove the laptop from any form of docking station you may be using.
OK

3) Reboot your machine with minimal USB devices connected
OK

4) Open a DOS command prompt in C:\nxp\LPCXpresso_7.3.0_186\lpcxpresso\bin\Scripts
OK

5) Open a window onto "Devices and Printers", as shown in http://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link
OK

6) Now connect one LPCXpresso board directly to a USB2 port on your computer. Does it appear in "Devices and Printers" as a "USB device with DFU capabilities"?
OK

7) In your DOS command prompt, run the command: usbdiags > preboot.txt
OK

8) Now in your DOS command prompt, run the command: ..\boot_link1 > bootinfo.txt
OK

9) Does your LPC-Link now appear in "Devices and Printers" ?
NOK - There is no device LPC-Link. Only "USB device with DFU capabilities" is seen.

10) Now In your DOS command prompt, run the command:
OK

I have a laptop: dell Latitude E7450 with Windows7 Professional edition.

Best regards.
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by malcolrook on Thu Sep 18 04:15:58 MST 2014
I have had an identical problem.

It was resolved by removing all other USB devices so I don't think that this is a problem with the headset as such.

It looks more as though there is a problem enumerating the LPC link when there are a large number of USB devices

Once the LPC link has been detected once there does not appear to be a problem.

It could be an idea to advise removing all other USB devices while connecting for the first time.
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Sep 03 23:41:48 MST 2014

Quote:
For time being I've not connected the headset but it would be good if it can be fixed.



This is a problem with the Plantronics drivers and so there is nothing that we can do to fix. Please report to Plantronics.
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by VigneshEP on Wed Sep 03 22:23:31 MST 2014
I mentioned in my previous post that sometimes IDE throws an error message. Following is what it says. Instead of blinky, red LED connected to target faintly glows. If I disconnect-reconnect USB cable, then blinky is properly executed and I've to use "boot debug probe" again to get into debug session.

10: Could not start execution from stop
  10: Could not start execution from stop
  IO Error - cable disconnected?
  15: Target error from Register access
  Not connected to emulator.
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by VigneshEP on Wed Sep 03 22:16:05 MST 2014
Hi,

Removing all the USB peripherals did the trick. I had an USB 2.0 hub hosting a mouse, keyboard and a Plantronics Blackwire C320-M  headset. The hub is in turn connected to a USB 3.0 port in Dell Latitude E6420 laptop. Three more USB ports were free on laptop and one was free on the USB hub. I rebooted removing all USB devices. When I executed boot_link1, LPC-Link appeared, and I'm able to successfully debug through IDE.

Out of curiosity, I tried connecting each USB device and see whether boot_link1 would work. The issue is with Plantronics headset. If it is connected, I wont be able to get past DFU mode. Sometimes even after it has successfully become LPC-link and then if I connect the headset, IDE says something similar to "Target not responding".

For time being I've not connected the headset but it would be good if it can be fixed. Thank you for the help so far.

Regards,
Vignesh
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Sep 03 06:34:11 MST 2014
OK, lets take this from first principles.

1) Disconnect all LPCXpresso / LPC-Link's from your computer.

2) Disconnect all other non-essential USB devices from your computer as well. If your PC is a laptop, please also ensure that you remove the laptop from any form of docking station you may be using.

3) Reboot your machine with minimal USB devices connected

4) Open a DOS command prompt in C:\nxp\LPCXpresso_7.3.0_186\lpcxpresso\bin\Scripts

5) Open a window onto "Devices and Printers", as shown in http://www.lpcware.com/content/faq/lpcxpresso/booting-lpc-link

6) Now connect one LPCXpresso board directly to a USB2 port on your computer. Does it appear in "Devices and Printers" as a "USB device with DFU capabilities"?

7) In your DOS command prompt, run the command:

usbdiags > preboot.txt


Now in your DOS command prompt, run the command:

..\boot_link1 > bootinfo.txt


9) Does your LPC-Link now appear in "Devices and Printers" ?

10) Now In your DOS command prompt, run the command:

usbdiags > postboot.txt



If you still don't see your LPC-Link appearing, then please confirm the details of the output seen in all of the above steps, and attach the preboot.txt, bootinfo.txt and postboot.txt to this thread.

Finally, please confirm exactly what model of computer you are using (and whether it is a laptop or desktop).

Regards,
LPCXpresso Support
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by VigneshEP on Wed Sep 03 05:20:40 MST 2014

Quote:
Is this a new machine and booting LPC-Link has never worked, or has it just stopped working?


New machine, first time trying LPC-link.


Quote:
Does the machine have USB2 and USB3 ports? If it has USB2 ports, make sure you plug the LPC-Link into a USB2 port.


It does have both however; I've tried in USB2 ports only


Quote:
If it is USB3 only, try using a USB2 hub.


Tried that also. No success

..and no success with "boot_link1 hidfs". "USB with DFU capabilities" doesnt change to "some HID device".

Regards,
Vignesh
0 件の賞賛
返信

2,683件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Wed Sep 03 01:52:00 MST 2014
[list]
  [*]Is this a new machine and booting LPC-Link has never worked, or has it just stopped working?
  [*]Does the machine have USB2 and USB3 ports? If it has USB2 ports, make sure you plug the LPC-Link into a USB2 port.
  [*]If it is USB3 only, try using a USB2 hub.
[/list]

If none of the above work, try this from the command line:
boot_link1 hidfs

Please report your results
0 件の賞賛
返信