Having just got this device I can't see how to successfully install the hardware. I get the error message; A service installation section in this INF is invalid. What am I doing wrong?
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi,
What version of Windows do you have?
If in XP32 or Win2000, you must install Ride before you plug the RLink. The Ride installer will install the USB driver, and then when you plug RLink, you just let Windows do the automatic driver search. (PNP installation procedure) You cannot install the driver by plugging the RLink and pointing the Windows wizard to the inf file on the CD. (manual procedure)
If in Vista32 or Vista64, you could use the manual procedure, but still it is better to install Ride first, as there are several drivers and you could be using the wrong one in manual mode. In Vista you must be sure to install the software while logged in with a user account that has admin rights, AND use the 'run as admin' option.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi,
Are you logged in as admin? You must be, even in XP.
You can run the driver installation procedure by executing this file: <RIDEInstallDir>\Driver\RLinkDrv\RLinkUSBInstall.exe And you can run the verbose version (in a command prompt it's better) by executing this file: <RIDEInstallDir>\Driver\RLinkUSBInstall_verbose.bat Please try that and maybe it will tell you what the problem is.
In XP this will install the WinDriver kernel driver (windrvr6.sys/windrvr6.inf) and the RLink driver (RLinkDRV_WDP.inf). Depending on the version and config of Windows, these files can go to <WINDOWS>\SYSTEM32\DRVSTORE\... or directly to <WINDOWS>\SYSTEM32\DRIVERS\... and <WINDOWS>\INF\...
There might be problems if you already have another version of windrvr6 (Jungo's WinDriver) or if you have a bad driver installed for the RLink IDs. Have you looked at the RLink device properties in the device manager after you plug RLink?
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi Vincent,
Navigated to C:\Windows, and searched for Windrvr6.*, deleting all that it found. Then searched for RLink*.*, and deleted all that it found
Used regedit navigated to:- "HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Enum/USB/VID_138E&PID_9000/" then deleted this branch.
Rebooted reinstalled ride7 ide 7.15.0000 & rkit-arm for ride7 1.14.0811
to C:\Program Files\Raisonance\
with no errors reboot plugged in the STM32 Primer2, let the pnp run and...
Cannot install this hardware there was a problem installing this hardware: Raisonance RLINKUSB Dongle An error occurred during the installation of this device A service installation section in this INF is invalid
Click Finish to close the wizard.
Device manager properties says
The drivers for this device are not installed. (Code 28) To reinstall the drivers for this device, click Reinstall Driver.
All fails.
By the way, its XP32 SP3, on a 2.5Ghz Quad core with 2.5Gb free ram, and this is all done as admin rights set to God level!
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Taking apart the RLinkDrv_WDP.inf file I searched the reg for c671678c-82c1-43f3-d700-0049433e9a4b and deleted all occurrences of it
Same with VID_138E&PID_9000 Jungo
Navigated to C:\Windows,
searched for Windrvr6.*, deleting all that was found, Then searched for RLink*.*, deleting all that was found
Used regedit navigated to, HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Enum/USB/ then deleted VID_138E&PID_9000 branch.
Rebooted reinstalled ride7 ide 7.15.0000 rkit-arm for ride7 1.14.0811
to C:\Program Files\Raisonance\
no errors reboot
Same as before.. no luck.
Could it a USB1.1 / USB2.0 lead problem? The lead supplied with it will not charge the box, so I rummaged around and found one that would. But I don't know if it a USB1.1 or a USB2.0.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi Dale, and thanks for taking the trouble.. From the CD supplied with it. The down loaded version gave the same result (Ride7 IDE 7.14.0001 ). I'm not out of the Woods yet, but I have seen a glade!
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi,
I don't think the cable could be a problem. If Windows is able to detect that the device is VID 138E & PID 9000, that pretty much validates the cable. (and also the RLink power, clock, connection to USB, firmware, etc.)
The inf file that should be used for RLink is RLink_WDP.inf, not Windrvr6.inf. (Windrvr6.inf/sys is a kernel driver that is referenced by RLink_WDP.inf.)
I doubt it will work if you have linked the RLink directly to Windrvr6.inf, but still, here is the way to check if the RLink is correctly enumerated by Windows: When you plug the RLink, the Busy LED turns ON. this LED is green on RLink, red on the STM32-Primer2, next to the LCD, ST7 and joystick. This LED turning ON means that the ST7 firmware is executing. Then, when Windows has performed the enumeration, the LED turns OFF. So if you see the LED turning ON when you plug the primer, and then OFF after some time (varies from about half a second to a few seconds), then very probably the USB driver is correctly installed. Then, you can open RFlasher, select the STM32 as target (or open a STM32 example in Ride) and try to read the RLink Serial Number. If that works, then the rest should follow very easily.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi Vincent Having reinstalled ride7 ide 7.15.0000 and rkit-arm for ride7 1.14.0811, (after getting confused with helping with the CircleOS, sorry Francis), I ran the RFlasher7 and my serial is 'dngWNYe00000477', so looks good to me. I'm a little reluctant to uninstall everything (again), as it is now running OK or so I think!
The trick for me is to install ride7 ide, then after a reboot plug the Primer2 in and point it at the Jungo_WinDriver_2000_NT_XP, and chose windrvr6.inf.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Guess What?
I recieved a brand-new Primer2, fresh out the box, Jusc connect it up and away I go. No, it tried to reinstall the same drivers that failed last lime,I had to manualy set it to ..\Jungo_WinDriver_2000_NT_XP\windrvr6.inf just like last time!
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Interesting Vincent. You could be on to something, slight variation in my case though, for the 2nd & 3rd Primer2s, I didn't have the CD in, just expected it to find the drivers on my system, as working fine with Primer2_No1. But it installed the wrong drivers, so had to 'manually' install as per above to get them to work. This is possibly one for Microsoft, but at this moment I have a work around, a bit inconvenient, but not difficult.
I can't comment on the Primer1 as don't have one, but may these steps be part of the F.A.Q. to help newbies?
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi,
The FAQ I referenced earlier should solve these problems.
My guess is you haven't _completely_ uninstalled the wrong driver, as is explained in the old FAQ entry referenced by the new one. For that you must reach the point where when you let Windows search the driver automatically in its driver store files but not in Ride, it doesn't find it. Was that your case?
The problem is that when there has been even only one attempt at installing the wrong driver (because the CD was in the drive or because you asked it to search in <Ride>\Drivers) Windows remembers it in hidden places (oem*.inf, ...) and it will always show up again when you don't want it.
Note that all versions of RLink are the same to Windows and the USB driver. But every RLink is unique by its Serial Number, and Windows remembers which driver is associated to which RLink. That probably explains why you had the problem on your primers 2 and 3 but not 1.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
For Primer1 I got rid of ride+divers, I use Linux & OpenOCD & arm-elf-toolchain without debug limit. Works like a charm.
I had 2 Primer2 running. When I change devices, the wrong driver gets installed and I have to go through the deinstall / manual install procedure every time. That is pest. I currently rewire one primer2 for programming via rs232.
I would definitly prefer a primer2 with openocd compatible interface ....
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi Vincent, On the contrary, I sent a whole weekend struggling to get my first Primer2 working. I went through the FAQ line by line, I dissected the .inf files to extract what they put & went where they lived, I did several restore points to put back my system in a state that it was prior to the installation. Did searches for the files and registry entries deleting them as I found them. The only thing that worked / works for me is to manually choose the Jungo_WinDriver_2000_NT_XP, <windrvr6.inf.> file.
When I got Primer2 and plugged it in I expected it to work with the driver set that was installed, but it wanted to use the set that I knew didn't work, so again I had to point it at Jungo_WinDriver_2000_NT_XP, <windrvr6.inf.>. This is with out use of the CD.
This is not a complaint, more an observation of what worked for me.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi Samarkh,
If you had completely uninstalled the Vista driver, it could not "want to use" it, because it would not find it at all! If it finds it, then that means that it's not completely uninstalled.
Had you reached the point where when you plug the RLink and ask it to install automatically, it tells you 'no compatible driver found' or something equivalent?
That step is required for proper recovery. (maybe there is something missing in the uninstall procedure, or maybe you missed an oem?.inf file or something in the DriverStore)
What did do after that, that made it able to find the wrong driver?
I cannot recommend the 'pointing manually to windrvr6.inf file' solution because it is not a universal solution. It could be working in your particular case, but on most PCs it's more complex than this. And I think that in reality you point to RLink_WDP.inf, which is in the same directory as windrvr6.inf. windrvr6.inf is a kernel driver that is not able to drive RLink on its own. (does not recognize the RLink's VID and PID...)
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
zwieblum,
Bypassing the debug limitation like you did is probably illegal.
There is no way for us to prevent you from doing it, but of course when you do it you lose all support from us, as we only sell RLink for being used with the Raisonance software. (or ST software in some cases)
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
> Bypassing the debug limitation like you did is probably illegal.
no, it isn't. but I think you know that by your own.
anyway, i can calm you: i do not use ride, although i gave it a shot. it's simply too limited (remember, i'm on linux not on windows).
but i do use primer1 and 2 and i do my best to work around the limitations. primer 1 is ok now (openocd), primer 2 is still in rewiring phase. but there is light on the horizon :-)
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
I wouldn't be so sure about the legal issues. (and I wasn't talking about Ride) But we won't waste time to investigate this issue, considering that whatever the result we don't intend to take any legal action, because we understand that some people want to or must work with Linux, and honestly we have other things to do.
My point was just that Raisonance only provides support and guaranty when RLink (or Primer) is used with the Raisonance software. I wanted this to be clear for all forum readers before they decide to use OpenOCD or anything else that might be out there.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Well, I am sure of that. If you are not, ask your lawyer. Maybe you can push that in US, but definitly not here in europe.
Anyway, Primer 1 is a nice hackable devices, now that it has openocd support. I do not think that you will lose any customers on the windows side if you open up primer 2 for openocd. Someday it will be supported, the question is how many folks get distracted and walk to other gadgets in the meantime. That will definitly be lost custumers.
Re: STM3210E-PRIMER2-'Cannot Install this Hardware'
Hi,
We will not pay a lawyer for useless information, as whatever the answer, we will not 'push' anything anywhere. (not in the way that you meant, at least )
Now, unfortunately, your reasoning about customers is incorrect because it is based on incorrect assumptions on our business model. (which is much more complex than you seem to think) If we have to reconsider this business model, (because OpenOCD allows to bypass the debug limitation or because of anything else) it will very probably result in more expensive RLinks and Primers, which I'm sure you don't want any more than us...
)