LPCXpresso IDE中的主题 Re: Re-installing LPC-Link

Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:12 GMT

Content originally posted in LPCWare by david.prentice on Mon Mar 08 04:47:32 MST 2010
I successfully installed LPCXpresso yesterday, and LPC-Link worked fine.
However Windows was unhappy this morning, and I have re-booted as a previous working configuration.

I un-installed LPCxpresso and am now trying to re-install it.

Everything is fine until the loading of the LPC-Link drivers on the first debug session. It seems to copy all the relevant files over. Then fails with:

LPC-Link Debug Probe v1.1

"An error occurred during the installation of the device
The wait operation timed out".

I have also tried the command line DFUAPP.exe with the same results.

David.

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:13 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Mar 08 05:07:05 MST 2010
Hi,

The problem could be that your machine is slow to load the drivers and so LPCXpresso times out waiting for the drivers to appear. It is not clear from your description at what stage the error occurs. If it is during the "initialise LPC-Link" stage, you get a choice of continue to wait or to display the log. Can you try the continue, and if it still failes, get the log and post it.

Other possible causes include:
- is the cable fully inserted into the PC and LPC-Link?
- if you are connecting via a USB hub, try connecting directly to the PC instead.

Also, which version of Windows are you running?

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:14 GMT

Content originally posted in LPCWare by david.prentice on Mon Mar 08 06:13:05 MST 2010

Quote: CodeRedSupport
Hi,

The problem could be that your machine is slow to load the drivers and so LPCXpresso times out waiting for the drivers to appear. It is not clear from your description at what stage the error occurs. If it is during the "initialise LPC-Link" stage, you get a choice of continue to wait or to display the log. Can you try the continue, and if it still failes, get the log and post it.

Other possible causes include:
- is the cable fully inserted into the PC and LPC-Link?
- if you are connecting via a USB hub, try connecting directly to the PC instead.

Also, which version of Windows are you running?

The system prompts for "New Hardware etc" when I start the first "debug Blinky" session.
Yes. I get prompts for Unsigned drivers,   and Waits from the debugger.    Which I respond to immediately.   If the "New Hardware" gets launched via DFUAPP,   then I only get the Unsigned Driver prompt.    But it still fails in the same way.

The USB is connected directly to the PC,   which is running Windows XP SP2.   It runs at a respectable speed.

The installation worked fine yesterday.   And I have un-installed / re-installed about 4 times this morning.   And rebooted the PC too.

[FONT=Courier New] *****************************************************[/FONT]
[FONT=Courier New]*** DFU LOG FILE ***
Creation Time : C:\DOCUME~1\DAVIDP~1\LOCALS~1\Temp\dfuApp5447055151675971449.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 14 (1032 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: Device has received the final block of firmware from the host and is waiting for receipt of DFU_GETSTATUS to begin the Manifestation phase; or device has completed the Manifestation phase and is waiting for receipt of DFU_GETSTATUS. (Devices that can enter this state after the Manifestation phase set bmAttributes bit bitManifestationTolerant to 1.)
DFU Get Status successful
---> DFUStatus: No error condition present.
---> DFUState: Device has programmed its memories and is waiting for a USB reset or a power on reset. (Devices that must enter this state clear bitManifestationTolerant to 0.)
Device Reset after Download successful
Close Device

*** END OF FILE ***

David.
[/FONT]

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:14 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Mar 08 06:57:30 MST 2010
Hi,

Can you try:
disconnect the board
start LPCXpresso
open Window->Preferences
In the left-hand column, expand LPCXpresso and click on Debug
Now, in the Right hand column, ensure "Initialise LPC-Link as Hid" is checked
press OK
connect your board
start a debug session

Thanks

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:15 GMT

Content originally posted in LPCWare by david.prentice on Mon Mar 08 07:33:53 MST 2010
Thankyou very much.

It seems to connect in this mode!

The behaviour is not quite the same as in my original installation.

David.

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:16 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Mar 08 09:37:40 MST 2010
Perhaps there was an error during the driver installation?

Could you zip and post \windows\setupapi.log - this contains detailed information on the installation of drivers by Windows.

Thanks

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:16 GMT

Content originally posted in LPCWare by js-nxp on Sun Nov 28 17:12:00 MST 2010
Some familiar "faces" here.:)

I cannot install lpc-link at all. It keeps on saying that it cannot find the required files.

I have tried both the DFU and LPC-Link driver directories.

Win XP PRO SP3 2.8GHz and 3GB ram

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:17 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Nov 29 00:15:29 MST 2010

Quote: js-nxp
Some familiar "faces" here.:)

I cannot install lpc-link at all. It keeps on saying that it cannot find the required files.

I have tried both the DFU and LPC-Link driver directories.

Win XP PRO SP3 2.8GHz and 3GB ram

Sorry, you haven't provided us enough information in order to help you, including the LPCXpresso IDE version you've installed. The LPCXpresso installation installs the required drivers. Your system must provide access to the cscript.exe utility for our installation scripts. On Windows XP, this is utility is located in the \WINDOWS\SYSTEM32 directory. Please post the exact error text you see to at least provide some idea of the failure mode.

Regards,

CodeRedSupport

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:17 GMT

Content originally posted in LPCWare by js-nxp on Mon Nov 29 01:32:14 MST 2010
I'm using
[LEFT][SIZE=1][SIZE=3]LPCXpresso: [/SIZE][/LEFT]
[SIZE=3]Version: LPCXpresso v3.5.6 [Build 234] [04/11/2010] [/SIZE]
[SIZE=3]

Quote:
The LPCXpresso installation installs the required drivers

Interesting, it must be failing. I get an ever ending Windows prompts to install the drivers when I plug in the board, it fails installation, says it can't find the files, rinse and repeat for ever.[/SIZE]
[SIZE=3][/SIZE]
[SIZE=3]I get the impression of this being a common problem?[/SIZE]
[/SIZE]

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:18 GMT

Content originally posted in LPCWare by js-nxp on Mon Nov 29 01:52:17 MST 2010
I have unistalled and reinstalled the IDE. The boxes to install the driver were both ticked. The same thing happens, as soon as I try to debug and plug the board in windows tries to reinstall the drivers and it fails saying it cannot find the files and it keeps on going forever. Message from IDE:

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:18 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Nov 29 02:04:05 MST 2010

Quote: js-nxp
I have unistalled and reinstalled the IDE. The boxes to install the driver were both ticked. The same thing happens, as soon as I try to debug and plug the board in windows tries to reinstall the drivers and it fails saying it cannot find the files and it keeps on going forever.

PLease zip up and post the file c:\windows\setupapi.log

This is a windows log file that records all driver installation messages.

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:19 GMT

Content originally posted in LPCWare by js-nxp on Mon Nov 29 13:51:36 MST 2010
Here it is. Thank you.

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:19 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Nov 29 18:34:49 MST 2010
Looking at your setupapi log that you sent, it appears the DFU device installation may be a problem. If it were me, I'd try the following. I've never encountered a problem doing this on Windows XP, but it's sort of a last resort.

1. Disconnect the USB cable from your LPCXpresso, and leave it unpowered.
2. In the ' \WINDOWS\INF' directory, search for "Philips" and be certain any .inf file(s) found has the string "VID_0471&PID_0000". Delete these, and any associated .pnf files. In your case, the files oem126.inf/oem126.pdf are likely present.
3. Plug the USB cable back into your LPCXpresso, and power it on. You should be be prompted that a new device is found. You'll want to handle the installation yourself, so when prompted, navigate to the LPCXpresso "<install>\Drivers\DFU" directory.

Once the DFU device driver has installed, the LPCXpresso IDE should be able to use it's scripts to DFU the LPC-Link software probe onto the LPC-Link.

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:20 GMT

Content originally posted in LPCWare by js-nxp on Mon Nov 29 20:35:06 MST 2010
It's all getting too hard :confused:

Quote:

2. In the ' \WINDOWS\INF' directory, search for "Philips" and be certain any .inf file(s) found has the string "VID_0471&PID_0000". Delete these, and any associated .pnf files. In your case, the files oem126.inf/oem126.pdf are likely present.

the directory has lower case \inf, no files called "Philips" or oem126.inf/oem126.pdf (pnf??)

I renamed ALL .inf and .pnf files created yesterday to see if new ones would be created. I also renamed the files in the DFU directory to match the case of the .cat files (some were all in lower case but it should not matter). Disabled virus scanner just in case. Still no good.

Renamed the setupapi.log to old so that I could see what happened with today's install and among other things I see

Quote:

#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#E360 An unsigned or incorrectly signed file "c:\nxp\lpcxpresso_3.5\drivers\dfu\MassDfu.cat" for driver "USB Device with DFU Capabilities" will be installed (Policy=Ignore). Error 0x800b0110: The certificate is not valid for the requested usage.
#E122 Device install failed. Error 2: The system cannot find the file specified.
#E157 Default installer failed. Error 2: The system cannot find the file specified.

so it seem that there are some issues somewhere.

I think I give up for now, maybe my local friendly NXP FAE can sort this out.

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:21 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Nov 29 21:31:47 MST 2010
Ok, in C:\WINDOWS\inf\certclas.inf, is there an entry such as:

{36fc9e60-c465-11cf-8056-444553540000} ; Universal Serial Bus controllers

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:21 GMT

Content originally posted in LPCWare by js-nxp on Mon Nov 29 21:37:21 MST 2010
Yep, 2nd last line

Quote:

[Version]
signature="$Windows NT$"
ClassGUID={00000000-0000-0000-0000-000000000000}
DriverVer=07/01/2001,5.1.2535.0
[DriverSigningClasses]
{B1D1A169-C54F-4379-81DB-BEE7D88D7454}        ; Anti-virus file system filter
{72631e54-78a4-11d0-bcf7-00aa00b7b32a} = 5, 0 ; Batteries
{4D36E966-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Computer
{4d36e967-e325-11ce-bfc1-08002be10318} = 5, 0 ; Disk drives
{4D36E968-E325-11CE-BFC1-08002BE10318}        ; Display
{48721b56-6795-11d2-b1a8-0080c72e74a2} = 5, 0 ; Dot4
{49ce6ac8-6f86-11d2-b1e5-0080c72e74a2} = 5, 0 ; Dot4Print
{4d36e980-e325-11ce-bfc1-08002be10318} = 5, 0 ; Floppy disk drives
{4D36E96B-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Keyboard
{4D36E96A-E325-11CE-BFC1-08002BE10318} = 5, 0 ; HDC
{745A17A0-74D3-11D0-B6FE-00A0C90F57DA} = 5, 0 ; HID
{4658EE7E-F050-11D1-B6BD-00C04FA372A7}        ; IEEE 1394 and SCSI printers
{6bdd1fc1-810f-11d0-bec7-08002be2092f}        ; IEEE 1394 Bus host controllers
{6bdd1fc5-810f-11d0-bec7-08002be2092f}        ; Infrared devices
{6BDD1FC6-810F-11D0-BEC7-08002BE2092F} = 5, 0 ; Image
{4D36E96C-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Media
{CE5939AE-EBDE-11D0-B181-0000F8753EC4} = 5, 0 ; Medium Changers
{4D36E96D-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Modem
{4D36E96E-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Monitor
{4D36E96F-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Mouse
{4d36e971-e325-11ce-bfc1-08002be10318} = 5, 0 ; Multifunction adapters
{50906CB8-BA12-11D1-BF5D-0000F805F530} = 5, 0 ; MultiPortSerial
{4D36E972-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Net
{4d36e977-e325-11ce-bfc1-08002be10318} = 5, 0 ; PCMCIA adapters
{4d36e978-e325-11ce-bfc1-08002be10318} = 5, 0 ; Ports (COM & LPT)
{4D36E979-E325-11CE-BFC1-08002BE10318} = 5, 0 ; Printer
{4D36E97B-E325-11CE-BFC1-08002BE10318} = 5, 0 ; SCSI Adapter
{50DD5230-BA8A-11D1-BF5D-0000F805F530} = 5, 0 ; Smart Cart Reader
{71a27cdd-812a-11d0-bec7-08002be2092f} = 5, 0 ; Storage volumes
{6d807884-7d21-11cf-801c-08002be10318} = 5, 0 ; Tape drives
{36fc9e60-c465-11cf-8056-444553540000}        ; Universal Serial Bus controllers
{4D36E97E-E325-11CE-BFC1-08002BE10318}        ; "Unknown"--make sure nobody is using this class

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:22 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Nov 29 22:01:27 MST 2010
Very curious. XP is complaining about a driver signing issue. Some people have had success deleting INFCACHE.1 in \WINDOWS\inf, but I wouldn't recommend it. In your setupapi.log I had the logged .inf name incorrect. Please search through oem26.inf for the presence of the Philips DFU driver VID/PID, and post your results.

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:23 GMT

Content originally posted in LPCWare by js-nxp on Mon Nov 29 22:09:44 MST 2010
I renamed oem26.inf and .PNF back to what they should be. Posting files

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:23 GMT

Content originally posted in LPCWare by CodeRedSupport on Mon Nov 29 22:36:17 MST 2010
Is this the only .inf file with the Philips DFU VID/PID?

Re: Re-installing LPC-Link

lpcware — Thu, 16 Jun 2016 00:21:24 GMT

Content originally posted in LPCWare by js-nxp on Mon Nov 29 23:02:19 MST 2010
There were 6 lots of .inf and .PNF files created yesterday, oem23 to oem27.

oem23 and 24 are FTDI related files. Don't know how it ties up with NXP but there is something about "Red Probe" so I guess they must be related.

oem25 has RDB-Link.inf as a header.

oem27 has LPC-Link.inf as a header.

I can zip them all up and post them if it helps.

Thank you very much for trying hard to help.