Re-installing LPC-Link

[lpcware]

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.

[lpcware]

Content originally posted in LPCWare by js-nxp on Sat Nov 26 17:00:43 MST 2011
Just to clean up my end with this (hijacked? :) ) thread. I had some corrupted driver database causing all the problems. Trying all the suggestions I could not get things to work. :(

Then a few months ago I purchaed a "PC cleaning" program from AVG as part of their sales push. To my surprise it fixed the database issues somehow and the debugger started to work well.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Thu Dec 02 00:30:14 MST 2010
The last change to this driver was 11th March 2010 (11/3/2010 - you are misreading the date). There have been literally thousands of installs in that time. [That change was to add support for 64-bit Windows which required involved modifications to the catalog and inf file, but not the driver itself - which was written by Philips (the predecessor of NXP) and has been unchanged for YEARS.]

I'm sorry, but without direct access to your computer, to find out what is wrong with your configuration or your hardware, then we are unable to help any further.

Best Regards

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Wed Dec 01 17:30:49 MST 2010

---

Quote: js-nxp
I'm out of ideas. Yes, I have admin privileges and have tried with the virus checker off. When you say the same driver works on other XP machines, the driver I have is dated 3rd Nov 2010.

Is it possible that something went astray recently?

I think this line is telling us what's happening, it shows clearly that the install is being blocked.

#E358 An unsigned or incorrectly signed file "c:\windows\inf\oem26.inf" for driver "USB Device with DFU Capabilities" [B]blocked [/B](server install). Error 1168: Element not found.
#E122 Device install failed. Error 1168: Element not found.

---

I'm not aware of any recent changes to the MassDfu.inf, or the catalog of this driver, but I can look into it. This particular error is one among several related messages from your setupapi.log file, but it's not complaining about the MassDfu.inf (other than it is unsigned) or massdfu.cat. It complains about the .inf file Windows XP created.

[lpcware]

Content originally posted in LPCWare by js-nxp on Wed Dec 01 16:09:59 MST 2010
I'm out of ideas. Yes, I have admin privileges and have tried with the virus checker off. When you say the same driver works on other XP machines, the driver I have is dated 3rd Nov 2010.

Is it possible that something went astray recently?

I think this line is telling us what's happening, it shows clearly that the install is being blocked.

#E358 An unsigned or incorrectly signed file "c:\windows\inf\oem26.inf" for driver "USB Device with DFU Capabilities" [B]blocked [/B](server install). Error 1168: Element not found.
#E122 Device install failed. Error 1168: Element not found.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Nov 30 17:12:38 MST 2010
I presume you have adminstrator privileges. This is grasping, but do you have any virus checkers in place which may intervene with driver installation? Recently, a user discovered his virus check program was set to disallow execution of vbscripts in his TEMP directory. The checker helpfully (but silently) logged these events to a file. It wasn't until he reviewed the log did he realize he needed to modify the protection setting which resolved the problem.

[lpcware]

Content originally posted in LPCWare by js-nxp on Tue Nov 30 16:56:29 MST 2010
I have already default to ignore the signing.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Nov 30 16:38:21 MST 2010
These same drivers install flawlessly on hundreds, if not thousands of Windows XP machines. See if this link helps, and let us know.

http://www.mydigitallife.info/2007/12/07/disable-unsigned-driver-installation-dialog-prompt-in-windo...

[lpcware]

Content originally posted in LPCWare by js-nxp on Tue Nov 30 16:05:11 MST 2010
The command line stuff suggested yesterday only restults in "No device conneted" see picture.

I have found a way of getting it all working temporarily for 1 session.

Plug the board in and perfoms install from DFU folder. Of course it fails and restarst another install. Cancel the second install and go to device manager and force the enable device and click ok. (see property picture posted earlier)

The board MUST NOT be disconnected at any time.

Now start the IDE and it will work OK, I managed to compile and debug a couple of the sample peojects.

Once the board is unplugged the whole procedure must be restarted.

This rules out the board and cable but points to the 32bit drivers not having the correct credentials/signature as shown in the install log. This seems to be the reason for the install not sticking.

I don't think anymore can be done untill the driver files are fixed.

Thank you again for your help.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Nov 30 01:36:26 MST 2010
I have double checked your driver installation log with one from a clean XP SP3 installation, and the messages are the same for driver installation. i.e. driver installation has succeeded.

Where it differs, is once you connect your LPCXpresso board to the PC. If what you say is correct:

---

Quote:

Continuously as long as I have the board plugged in. It fails, detects  the new device, it fails, detects the new device ad nauseum.

---

This suggests to me that the board is continuously power-cycling, which can only be due to:

[LIST]
[*]cable problems
[*]USB connector problems, or
[*]board problems
[/LIST]
If you have ruled out the cable, then it can only mean that you have a board problem.

[lpcware]

Content originally posted in LPCWare by js-nxp on Tue Nov 30 01:04:26 MST 2010
The cable works well with other equipment. The whole issue seems to be that whatever file(s) is/are being installed is not found or bad. At least that's what the install messages keep on saying.

The USB connector is off a desktop PC with plenty of grunt as I run Atmel tools from the same.

A faulty board?? Don't really know, I only got it a few days ago at the Sydney NXP Cortex seminar. The led blinks as I think it should with the default Blinky code installed.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Nov 30 00:46:17 MST 2010
If Windows is continually doing this, it implies that either your USB cable or your board has gone bad - my guess is that there is a bad link and the power, and so the board is continually power-cycling.

[lpcware]

Content originally posted in LPCWare by js-nxp on Tue Nov 30 00:30:45 MST 2010

---

Quote:
does Windows ever prompt you to re-install the device?

---

Continuously as long as I have the board plugged in. It fails, detects the new device, it fails, detects the new device ad nauseum.

I'll try the command line stuff tomorrow. Enough for the day. Thanks.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Tue Nov 30 00:16:46 MST 2010
Disconnect, and reconnect the USB cable to your LPCXpresso. Navigate to the LPCXpresso <install>\bin directory. You'll find the DFUAPP.exe executable. Issue the following command-line:

C:\nxp\lpcxpresso_3.5\bin\DFUAPP /f LPCXpressoWIN.enc /tl 250

If the DFU driver is installed, this should DFU the WinUSB software probe. This shows up in the Device Manager as "LPC-Link Probe v1.0" or "LPC-Link Probe v1.1".

See if you get the same results as before. Typically, we install a HID probe for Windows XP (i.e. LPCXpressoHS.enc or LPCXpressoFS.enc), but these are not clearly marked in the Device Manager.

Edit: By the way, while all this is going on, does Windows ever prompt you to re-install the device?

[lpcware]

Content originally posted in LPCWare by js-nxp on Tue Nov 30 00:00:14 MST 2010
Deleted all 10 files (moved to another folder just in case)
Unistalled IDE
Restarted computer
Reinstalled IDE with driver boxes checked
10 files reinstalled by the IDE install oem23-oem27 (same files as before)
Started IDE all is well
Plugged in the board, Windows detects it, tries to install files and...back to where we were yesterday.

There is something strange in the property for the DFU device. Windows says it's working properly but is disabled and it will be unistalled when powering down. Go figure!!

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Mon Nov 29 23:22:05 MST 2010
It's probably quicker to delete these oem??.inf and associated oem??.pnf. To be sure you're deleting the correct files, look for the following VID/PIDs:

DFU: VID_0471, PID_0000 (and PID_DF55)
LPC-Link: VID_1FC9, PID_0009
RDB-Link: VID_21BD, PID_0001
Red Probe+: VID_21BD, PID_0003
Red Probe: VID_0403, PID_AD08

This should be everything.

Next, disconnect your LPCXpresso and uninstall (run the unins000.exe executable in the LPCXpresso  installation directory), then re-install the IDE. Be sure the check box to install all drivers is checked.

[lpcware]

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.

[lpcware]

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?

[lpcware]

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

[lpcware]

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.

[lpcware]

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

---