Forum : ST7/STM8
Post Information | Post |
---|---|
October 17, 2010 - 5:35pm
|
I get the above error when I try to start debugging from within Ride7. The title of the dialog box in which this message appears is "OPI Driver Error(1)". After invoking Ride7 (run as Administrator, my project automatically opens), I click the "Start Debugging" button. The loading process stalls with the "Clearing Emulation Memory..." dialog message and then I get the above error. Running as "not Administrator" has no effect on the problem. Cleaning and rebuilding the project also has no effect. My OS specifics are in my previous post. Note that I get a different, earlier error if I don't have power on the target (STM8/128-EVAL) so the RLink dongle appears to see the target. Note also that this procedure worked fine all day yesterday. The target ran all night last night. I moved all the stuff (laptop included) to work because I needed an oscilloscope to try to debug my problems with uart output. On freshly connecting everything at the shop this morning, no joy. Power cycled everything several times. Tried various verbal incantations in several languages. Nope, same error. I did think to check the devices section of Windows 7. It believes that the "device is working properly". |
So then I dragged everything back home and reconnected it all. And then the download worked! I still don't know what, exactly, is going on but here's a guess. I do all my development on a Windows 7 laptop. I can't really type or control the mouse properly with the built in keyboard and touch pad thing so I always connect an external keyboard and mouse via USB. But I only have 2 USB ports on my laptop. One is taken by the keyboard and the other is taken by the USB to serial device. While I used to plug the RLink dongle directly into the side of the laptop, now I have to plug it into the back of the keyboard. I know that the keyboard's USB ports are slower than the ones built into the laptop because Windows 7 fusses about the speed difference when I plug a memory stick into the keyboard. Once I connected the dongle to the slower USB port, going back to the faster one makes the RLink dongle driver angry. Or something like that. I have spent all day trying to decipher the astonishingly poor ST documentation to determine how to make the STM8 use the on-board oscillator so getting a final answer on this issue this may be delayed a bit.