Topic : Ride 7 Change crt0_STM32x.c

Forum : ARM

Original Post
Post Information Post
November 16, 2010 - 11:22pm
Guest

Hello,

I am using the Ride 7 tools with a STM32F107RB16. I noticed that the crt0_STM32x.c file my project is using does not contain vector IRQs for hardware that my chip supports, such as timer 5. The crt0_STM32x_HD.c, found in C:\Program Files\Raisonance\Ride\lib\ARM, file seems to have the correct vector table for my device. How do i update my project to include the HD version of the file.

Thanks,
Matt
Replies
Post Information Post
+1
0
-1
November 17, 2010 - 9:43am
Raisonance Support Team

Hi Matt,

We would like to help you as quickly as possible on this issue, but we need to have more information about the problem before we can help further.

In order to understand the issue you are facing, we need the following information about your configuration:

- Version of Ride7 and RKit that you are using. You can get these from the Ride7 "Help | About" dialog box.

Please check from the Raisonance downloads page at http://www.mcu-raisonance.com/mcu_downloads.html that you are using the latest version of the tools.

Concerning your particular problem:

- Provide the steps you followed to raise the error (how you created your project)

- Does the problem occur when using the examples given with Ride7 (from the Ride7 installation directory, default being "C:\Program Files\Raisonance\Ride\Examples\")?

Regards,
+1
0
-1
November 17, 2010 - 6:18pm
Guest

Tools:
Ride 7 7.24.09/0251
Rkit STM8 2.24.09.0238
STM8 Compiler " "
STM8 Linker " "
STM8 CodeComp. " "
Rkit-Arm for Ride7 1.22.09.0254

- Provide the steps you followed to raise the error (how you created your project)

This project was inherited so i am not aware of the steps to create the problem/project.

- Does the problem occur when using the examples given with Ride7 (from the Ride7 installation directory, default being "C:\Program Files\Raisonance\Ride\Examples\")?

I have not tried using an example. I have tried recreating the project, and got the same results. I do know that the project has the correct microcontroller selected. In Project->Properties->Advanced ARM Options->Devices list the STM32F107RBT6, which we are using.

Can you only set the vector file a project uses during project creation, or is there a way to change which file we are using after the fact?

Currently we have replaced crt0_STM32x.c with the contents of crt0_STM32x_HD.c, and are successfully using the timer 5 interrupt, but our concern is that this is not a easy configuration to maintain.

Thanks for the assistance, and I look forward to your response.

Best,
Matt
+1
0
-1
November 18, 2010 - 11:02am
Raisonance Support Team

Hi,

Your software is outdated, and several problems have been fixed since.

Please uninstall your Raisonance software and install the latest version, which you can download from http://www.mcu-raisonance.com/mcu_downloads.html.

Let us know if this fixes your problem.

Regards,
+1
0
-1
November 18, 2010 - 8:31pm
Guest

Bruno,

I work with Matt. We installed the latest softeware onto a new computer, before updating either of our computers. Our project compiled and it looked to fix our issue.

I removed the Ride 7 compiler, ARM Kit and STM8 Kit from my computer. I install the latest versions and can not get the project to compile.

I get a number of these statements:

'objFSO' is null or not an object
if (!objFSO.FileExists(cfgfile))

I also tried the sample project, STM32F103_toggle, and it gives the same errors.

Do you know what may be causing this?

Regards,
Glenn
+1
0
-1
November 19, 2010 - 9:32am
Raisonance Support Team

Hi,

There is a known issue is about some Windows versions that do not have the script engine properly registered. You can check this from http://forum.raisonance.com/viewtopic.php?id=3296.

Another problem that you may encounter is that you installed or ran Ride7 without being the administrator of the machine: The Ride7 installer checks for admin properties, but for some reason we have seen some Windows installations that pass over this test, and we do not have a clear understanding of why the Windows installer facility violates our install requirements. In such a case Ride7 gets installed but not as administrator, so various problems may happen in the licencing or scripting parts.
To fix this, when installing ensure that you right-click on the Ride7 installation icon and select "Run as administrator".

Regards,