Forum : Ride IDE
| Post Information | Post |
|---|---|
|
August 17, 2011 - 6:56pm
|
I have been using: Ride7 (7.30.10.0159) on my desktop for some time without any problems. For convenience, I wanted to do debugging on my laptop (XP32) so I downloaded the latest version: Ride7 (7.32.11.0112) and this appeared to load fine. However, when I try to load ANY project, the program crashes-out with a Windows Memory error. I have never had any other instability problems on this computer before. I had previously had some success with an old version (which came on the CD) but this wouldn't compile my project. It would however, load and compile some examples. (It's tempting to try the latest download on my desktop - but this is my only way of working at the moment, so I daren't risk it) |
Hi,
We have recently identified and corrected a problem that was leading to instability on some PCs. We will now need a little time to release new kits. (or patches)
Please anybody who have this same problem write it here if you want to help us by testing the beta version of the patch. (and have it earlier ;) )
Best Regards,
Vincent
Put me down for one ASAP
I get intermittent crashes with the newest version of Ride7- sometimes just after I load a program, sometimes just after I enter debug mode and the watch window pops up but before it's populated. I would say I experience them 40-50% of the times I run the program. Is this the same thing?
Ben
Yes, Stabler, this is probably the same thing.
Please tell us the versions of all the kits (Ride7, ARM, STM8, ...) you installed.
Vincent
Ride7 7.32.11.0112
RKit-ARM 1.32.11.0116
Thanks!
Ben
I also get intermittent crashes with the newest version of Ride7- sometimes just after I load a program, sometimes just after I enter debug mode and the watch window pops up but before it's populated. I would say I experience them 20-40% of the times I run the program. Is this the same thing?
Hi,
Yes indeed it could be the same problem.
I will send you an email.
Best Regards,
Vincent
Same thing here. The bug is a show stopper for my current work right now, I would really apreciate a beta version that fixes this bug. Here is my current configuration:
WindowsXP 32bit SP3
RLink programming adaptor (unlimited code size for debugging enabled)
uC STM32F217VGT
Ride7 7.32.11.0112
RKit-ARM 1.32.11.0116 (Evaluation)
Rlink-Drv installed with Ride7
I observed the following behaviour:
[=*]
I have the same issue. 5 seconds after ride 7 is started , it crashes .
Problem Event Name: APPCRASH
Application Name: Ride7.exe
Application Version: 7.32.11.112
Application Timestamp: 4db12948
Fault Module Name: rp_st7.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4e26ceb2
Exception Code: c0000005
Exception Offset: 062d4163
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1045
Additional Information 1: d41d
Additional Information 2: d41d8cd98f00b204e9800998ecf8427e
Additional Information 3: 3877
Additional Information 4: 38777431b559e015a3ede4cd7134ecf2
I do not even debug or build the project.
Hello,
There are new versions of the Ride7 (7.34) and RKit-ARM (1.34) kits available on our extranet.
They solve all the problems mentioned in this discussion.
Best Regards,
Vincent
I have the same issues as other members. So I downloaded the new versions of the Ride7 (7.34) and RKit-ARM (1.34) kits. It doesn't crash anymore.
But a new problem occurs. All the I2C stopped working. So I unloaded the new version and installed the old version, my firmware works fine. Then I unloaded the old version and reinstalled the new version, it worked fine for one day. Then I2C stop working again.
Your help will be greatly appreciated!
Hi Maggie,
I do not know which version you upgraded from, but :
- The Ride7 and RKit-ARM versions you are using are a bit outdated. You should consider upgrading from http://support-raisonance.com/.
- On older RKit-ARM versions we were using ST Library 2.x, and the interrupt vectors have been renamed with version 3.x. Hence you may have defined an interrupt vector which is not actually referenced by your startup. Double-check your interrupt vectors (from your .map file).
I hope this helps,
Hi,Bruno,
The older version I was using are Ride7 (7.30) and RKit-ARM (1.26) kits.
Sorry, the new version I am using are Ride7 (7.36) and RKit-ARM (1.36) kits.
Also I didn't use any interrupt.
Any progress on the problem about I2C run under new version of Ride7? Now I have to run the older version of Ride7. With this version, I can only compile and debug once, then it crashed and I have to reopen it.This is becoming worse when the code size is becoming larger. Currently, the Hex file size is 722k.
Hi Maggie,
I do not have any idea what may cause this I2C problem.
One track would be that you have a problem with the compiler. Try to reduce the optimization level to "unoptimized" and check whether it fixes your issue.
Another track would be to keep the old library (which was working) and check whether it still works.
Concerning the crashes, it is due to an inconsistency in the Ride7 internal database (where it stores build/make information).
What you can do is as follows:
- Close all instances of Ride7
- Delete intermediate files in your project (.xdb, .o, .xml files) and keep only the .rapp and .rprj (and your sources of course)
- Restart Ride7
- Rebuild your project
You should not have the Ride7 failures anymore after this.
Let me know if you make any progress on this.
Hi,Bruno,
Regarding the crash, I tried the way you mentioned. The problem is after the project is rebuilt, (.xdb, .o, .xml files) appear again.So it still crashes.
About the suggestions to fix the I2C problem, I haven't tried yet. I'll let you know the result after I try it.
Thanks!
Maggie