I am following the "Getting started with the STM32VL-Discovery board and ChibiOS/RT
" tutorial, and am getting the following error when trying to build [ARMCM3-STM32F100-DISCOVERY]:
"../../os/ports/GCC/ARMCMx/STM32/vectors.c:283: fatal error: opening dependency file .dep/vectors.o.d: No such file or directory"
I am using Eclipse (Helios Service Release 2) and CodeSourcery. cs-make -version => "(G++ Lite 2010q1-188) 3.81".
I am succesful at compiling another project (call this project #2), from the MutiPilot32 repo.
Project #2 [MP32-TESTPROGRAM]:
Is in a different CHibiOS folder (workspace).
Workspace is here:
"C:\Files\Eclipse\Projects\Kernel 2.2.0\ChibiOS_2.2.0\Project"
Project is here:
"C:\Files\Eclipse\Projects\Kernel 2.2.0\ChibiOS_2.2.0\Project\MP32-TESTPROGRAM"
This projects is creating the "vectors.o" file here:
C:\Files\Eclipse\Projects\Kernel 2.2.0\ChibiOS_2.2.0\Project\MP32-TESTPROGRAM\.dep
as well as here:
"C:\Files\Eclipse\Projects\Kernel 2.2.0\ChibiOS_2.2.0\os\ports\GCC\ARMCMx\STM32"
Project #1 (ARMCM3-STM32F100-DISCOVERY):
Workspace is here:
C:\Files\Eclipse\Libs\ChibiOS_2.2.2
Project is Here:
"C:\Files\Eclipse\Libs\ChibiOS_2.2.2\demos\ARMCM3-STM32F100-DISCOVERY"
I am not getting any errors because of missing includes. In otherwords I added ./include from the hal and kernal, as well as changed the default "make" to "cs-make".
I am new to Eclipse, gcc, and of coarse ChibiOS. I am sure it is a simple problem, why one project works and another one doesn't (maybe in the makefile), but I am falling short of where to look.
One final question: the tutorial outlines the location of the project as "./demos/ARMCM3-STM32F100-DISCOVERY-GCC ", but in the download I have "./demos/ARMCM3-STM32F100-DISCOVERY ". Was this a type, or did I get the wrong file?
Thanks,
Jim Tompkins
STM2 Discover Board Build Problem
Moderators: RoccoMarco, lbednarz, tfAteba
- Giovanni
- Site Admin
- Posts: 14891
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: STM2 Discover Board Build Problem
Hi Jim,
The tutorial covers an older version, the folder name is now the one you mentioned, the demo now also supports the IAR and RVCT compilers so the -GCC suffix has been removed.
Not sure about the error you are getting, could you try to download the latest version again the compile the demo using just "cs-make" ? I just compiled the demo in version 2.2.2 using CS without problems.
Note that if you are working with multiple project is is advisable to "clean" the previous project before building the new one or the object files will get mixed.
Giovanni
The tutorial covers an older version, the folder name is now the one you mentioned, the demo now also supports the IAR and RVCT compilers so the -GCC suffix has been removed.
Not sure about the error you are getting, could you try to download the latest version again the compile the demo using just "cs-make" ? I just compiled the demo in version 2.2.2 using CS without problems.
Note that if you are working with multiple project is is advisable to "clean" the previous project before building the new one or the object files will get mixed.
Giovanni
Re: STM2 Discover Board Build Problem
I think I isolated the problem to my installation of CodeSourcery, or at least the interaction of Eclispe w/ Codesourcery.
I did a fresh install of everything in a new Vmware VM (XP Pro) and installed Yagarto instead of Cs. I installed "Yagarto GNU ARM Toolchain" + "Yagarto Tools version 20100813". I am able to compile now. In fact the .hex is now residing and running on the discovery board: http://www.virtualrobotix.com/forum/top ... e=activity
I went back to my original dev box (VM) and removed CS, and installed Yagarto, and can compile there as well, so it is not Eclipse or the actual project (ChibiOS). I am not sure what the problem was with CS. I did notice just now that I had installed an outdated version of cs (Sourcery G++ Lite 2010q1-188) instead of (Sourcery G++ Lite 2010.09-51). Maybe that was the problem, or maybe it was a path problem of some sort. I was reading a pdf from the CS site that made reference to unix paths and Windows paths and Cygwin.
Thanks for the help btw.
I did a fresh install of everything in a new Vmware VM (XP Pro) and installed Yagarto instead of Cs. I installed "Yagarto GNU ARM Toolchain" + "Yagarto Tools version 20100813". I am able to compile now. In fact the .hex is now residing and running on the discovery board: http://www.virtualrobotix.com/forum/top ... e=activity
I went back to my original dev box (VM) and removed CS, and installed Yagarto, and can compile there as well, so it is not Eclipse or the actual project (ChibiOS). I am not sure what the problem was with CS. I did notice just now that I had installed an outdated version of cs (Sourcery G++ Lite 2010q1-188) instead of (Sourcery G++ Lite 2010.09-51). Maybe that was the problem, or maybe it was a path problem of some sort. I was reading a pdf from the CS site that made reference to unix paths and Windows paths and Cygwin.
Thanks for the help btw.
- Giovanni
- Site Admin
- Posts: 14891
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: STM2 Discover Board Build Problem
It could be a problem with paths containing spaces.
Anyway, there are no problems with YAGARTO, it is my default toolchain too.
Giovanni
Anyway, there are no problems with YAGARTO, it is my default toolchain too.
Giovanni
Re: STM2 Discover Board Build Problem
Giovanni, "liamstask" gave the answer already, see http://sourceforge.net/projects/chibios ... ic/3996570
The problem is that CodeSourcery is lacking some unix commands, which Yagarto offers as a seprate "Tools" package, see http://www.yagarto.de/#download
I am actually able to compile/link with CodeSourcery plus the Yagarto tools.
Stephan
The problem is that CodeSourcery is lacking some unix commands, which Yagarto offers as a seprate "Tools" package, see http://www.yagarto.de/#download
I am actually able to compile/link with CodeSourcery plus the Yagarto tools.
Stephan
Re: STM2 Discover Board Build Problem
Thanksfor the post Stewo,
Although I have been using Yagarto for the last several days, its been bothering me that I couldn't get CodeSourcery to work. I thought I was doing something wrong (I am a gcc newbie).
Not sure if I mentioned on the thread :
I used Yagarto Tools 20100703 which has binutils 2.20.1 because binutils 2.21 was giving me: "(Error: SVC is not permitted on this architecture)".
I Guess this is a know issue:
http://sourceware.org/bugzilla/show_bug.cgi?id=12296
- JimT
Although I have been using Yagarto for the last several days, its been bothering me that I couldn't get CodeSourcery to work. I thought I was doing something wrong (I am a gcc newbie).
Not sure if I mentioned on the thread :
I used Yagarto Tools 20100703 which has binutils 2.20.1 because binutils 2.21 was giving me: "(Error: SVC is not permitted on this architecture)".
I Guess this is a know issue:
http://sourceware.org/bugzilla/show_bug.cgi?id=12296
- JimT
- Giovanni
- Site Admin
- Posts: 14891
- Joined: Wed May 27, 2009 8:48 am
- Has thanked: 1202 times
- Been thanked: 996 times
Re: STM2 Discover Board Build Problem
Just a note, a new YAGARTO version has been released, it fixes that problem.
I wish CodeSourcery included something like the YAGARTO tools in their free package, a lot of people would have less problems. I think they assume the user has cygwin installed which also provides those tools (among many other useful utilities).
Giovanni
I wish CodeSourcery included something like the YAGARTO tools in their free package, a lot of people would have less problems. I think they assume the user has cygwin installed which also provides those tools (among many other useful utilities).
Giovanni
Re: STM2 Discover Board Build Problem
Thanks for the update. I will try the Yagarto update. I thought about trying to install cygwin and getting CS to work, but I am too entrenched playing with CHibiOS and don't want to get side tracked. I copied and modified the board config (board.h) to map usart3. I also modified main.c and mcuconf.h to use SD2 and SD3, and have succesfully added a thread to print data out sd3. For some reason it causes the test thread to not finish when run. I don't have any question about that right now, as I need to review what I was doing (It was very late/early and I probably typoed something).
I had another question regarding jtag, but I will start a different thread.
Thanks again,
JimT
I had another question regarding jtag, but I will start a different thread.
Thanks again,
JimT