Topic : Errors compiling STM32F10x firmware library v. 2.0.3

Forum : Ride IDE

Original Post
Post Information Post
March 25, 2009 - 1:09pm
Guest

Hi.
I am new in the forum and using RIDE7.
I have tried to compile de STM32F10x firmware library v. 2.0.3 using the ride project.
I get the following error:
C:\Archivos de programa\Raisonance\Ride\arm-gcc\bin\arm-none-eabi-objcopy.exe: 'C:\USERS\STM32\Lib st\FWLib\project\RIDE\STM3210E-EVAL\Project.elf': No such file

I user Ride 7.14.0001 and adn RKit -ARM for ride 7 ver. 1.13.0810
Replies
Post Information Post
+1
0
-1
March 25, 2009 - 1:46pm
Raisonance Support Team

Hi,

I do not have a precise idea why you have this error message.
However, your version is outdated, and you will sure benefit from a refresh of your RKit-ARM and Ride7. Head to the www.raisonance.com Web site, in the download section for free updates.

Also the STM32 firmware library is pre-built with RKit, so from Ride you should just activate the "Use ST FW library" in the linker options, and the library will be linked in with your application. This is faster but you may want to have your own modifications done to the ST library, so it is up to you to decide how to proceed.

Regards,
Bruno
+1
0
-1
March 26, 2009 - 9:05am
Guest

Hi.
Thanks for your fast response. I have updated the RKit-ARM but I also have problems compiling the st library and some sample projects.
I have begin to work with a set of samples delivered by ST that doesn't give me any problem to compile, and when I became expert with RIDE7 and STM32 I will try to generate my own project.

Best regards
+1
0
-1
April 4, 2016 - 4:44pm
Andrea Uguccioni

i have an EvoPrime with STM32f107VC db with RIDE7+Rkit-ARM1.06 When I try to connect to target  the system reply to that RLink not to able becaus timed out why?
+1
0
-1
April 5, 2016 - 10:58am
Etienne Cassin

Dear Andrea,

When connecting the Open4 to the computer, the driver will recognize the open4 but it take some time the first time you pluggled in. You should be sure that the peripheral is well recognized. could you send us a screen shot of the error message and the peripheral installed on your pc?

Did you switch on the open4? could you send us a screen shot of the window which will appear when clicking on "connect to debugger"?

Best regards,