I recently got my primer and then tried to install the Windows driver. I was running the in the Administrator login of my PC(WindowXP Prof SP3).
I have also install the recent version of Ride7: 7.16
But I was never able to get it connected to my PC and it used to say: There is a problem in the hardware and could not be initialized. Since this was a warning from the Windows so I didnt go forward with Ride7 testing. Then I opened up the hood and checked for the small ground trace. I found that the U9 connection as suggested was alright. But then I found a particular Tantalum capacitor appears to have burnt. Have a look at this image attached.
Think the problem is not in the hard ware but in the driver. Since I checked the capacitor on power on there was not improper voltage. The cap has failed open so there is no danger.
But then I saw in the forum that many people in the forum had some issues with the driver installation. So I tried to uninstall the driver and then load it again. Have a look at the final screen.
As far as i can see the capacitor can not be destroyed by the driver or software easily, if at all.
U9 produces the 2.8V to supply the STM32 and the RLINK (ST7 device). I don't know the voltage of that capacitor, but i believe it has got to much voltage. (When asumming it is not mounted with wrong polarity)
So, it seems the U9 regulator are oscilating and generating af much higher output voltage or the regulator are somehow short from input to output. There is a slightly change the 2uC on the board are dead...
And therefore the driver will not install.
This is just my idea, there can be other solutions or this can be wrong, but your informations are also quite limited
Does your Primer work in stand alone mode ? If yes, the regulators are OK. The problem is only within the communication between RLink and the PC, it could be an issue with the driver installer. For the burnt capacitor (C2), an overvoltage is not probable (the max voltage is 10V whilst the real voltage is 2.8V).
In stand alone mode I am able to make it work. All the Demo programs , Touch screen , MEMs, Tests Program and configuration are working in stand alone mode. These are the ones that come pre-loaded into the board when we buy. I have also tested the MEMS Mouse application in the Test module using USB to PC and it works fine.
I am not sure if the burning of the capacitor is really an issue since I am able to see proper voltage across it. It means that it has failed open. So it shouldn't trouble much. Also I think its part of the debugger circuitry. I am not sure since I don't understand the board schematics well.
From this I guess its a software issue of the Driver Install after all. Additionally I see that the Debug LED Read near to the ST7 is glowing when I attached the Debug USB. I have also attached the picture of the driver failure.
Yes I think so. Today I have downloaded another version of the RIDE 7 from the website. But it seams that its the realease that was available to me even earlier than that in the CD BN14 downloaded from this website Resource section. I have also seen some other people posting regarding this.
Kindly guide me how to get my Primer2 working. I am yearning to make my programs work.
I also can not install the driver of primer 2 in the CD. I downloaded the file Ride7_BN27.exe from the website, but the problem is same. my computer is laptop, and directly plug primer 2 into my laptop. OS: winXP SP3(chinese version) I posted my question, but I have not got feedback till now.
You indeed have a USB driver problem, which is probably purely software, as Windows is able to recognize that the device is a RLink. I don't think it could get to this point if there was a hardware problem on the RLink part. Let's solve this first and then we'll see if you also have a hardware problem...
It seems to me that the WinDriver kernel driver is not installed. It must be preinstalled.
Please try to run the RLinkUSBInstall program in verbose mode and send me the screenshot if it fails, or execute the manual installation for XP explained in this doc: ftp://217.71.112.106/temp/RLink/GettingStartedRLink.pdf
Please also check if the windrvr6 files are present in the Windows directory (inf, system32\drivers, driverstore, etc.)
Thanks for your support. I have downloaded the Help file. I will first uninstall all the required files and then start a fresh with the Install process.
I wish to know which Kernel mode Driver I should use: 1. C:\programFiles\Raisonance\Ride7\driver 2. on the CD with the Kit
Well, these two files should be the same. But due to recent changes in Windows, you should never use the ones on the CD. In fact you should always remove all CDs from the driver before installing the driver. (and the new/future CDs don't have the unpacked files at all) I will change the manual installation procedure in the doc to make that clearer.
Please send me the screenshot of what happens when you run this command in a dos prompt: C:\Program Files\Raisonance\Ride\Driver\RLinkDrv\Jungo_WinDriver_2000_NT_XP> wdreg -inf windrvr6.inf install
Please also check the presence or absence of these windrvr6 files: C:\Windows\inf\Windrvr6.inf C:\Windows\System32\Drivers\Windrvr6.sys C:\Windows\System32\DRVSTORE\Windrvr6*.*
I have checked the driver installation. Here is the picture:
Then I tried to connect to the RLINK using the RFLASHER. Here is the Screen short:
I tried to connect to the target: then I got the voltage error:
Then I power on the STM32 main app and I received the following message:
After that the main app hangs then I have to again Click on the Connect to Rlink to restore control.
But after all this looking at the capacitor I found that it was mounted in Reverse as per the silkscreen comparison with the other Tantalum capacitors. I checked if the U2 was hot but it was also at some normal temperature.
You can read the RLink serial number; That means the USB driver is installed and working, and any other problems you might encounter now are not related to that.
Now, if you have a capa that is soldered in the wrong way and has already seen the dark side of the force, I recommend you stop using the primer until you have replaced it by a new one. (in the correct way ) You don't want to burn other things as a result of keeping this situation.
Then, the error message you receive about MCU device ID just means that the target device you have selected in RFlasher is not the device that is connected to the RLink... And indeed you have selected the STM32F103RBT6, but your Primer2 contains a STM32F103VET6. You need just change the device selection in the software and it should be fine. (be careful not to program the CircleOS for the Primer1 in a Primer2... )
Finally, what do you mean by "the main app hangs"? Do you mean that RFlasher hangs? (which would be a bug in my software ) Or do you mean that CircleOS does not execute any more? (which would be normal because we entered debug mode for reading the device ID )
I installed the Factory Restore OS into the Primer2 and its Circle OS is upgraded to the 3.4 Version. Further I was also able to debug the code in Ride7. All this after I changed the STM32 number in the RFlasher.
Also the Burnt Cap doesnt cause any other problem.
) You don't want to burn other things as a result of keeping this situation.
) Or do you mean that CircleOS does not execute any more? (which would be normal because we entered debug mode for reading the device ID