2016-11-08 09:13 PM
Hi,
In the project properties setting, I am using arm-none-eabi-gcc toolchain.
This time toolchain is Ac6 STM32 MCU GCC and builder CDT internal.
Problem is if I add h files in HAL library that error log suggest me to do, it solved and if I build project again it shows the problem in CMSIS include H files.
Such as,
1. C:\STM32_toolchain\common\Drivers\CMSIS\Device\ST\STM32F0xx\Include/stm32f0xx.h:187:3: error: declaration for parameter 'FunctionalState' but no such parameter
} FunctionalState;
^
..\inc\Src\stm32f0xx_hal_flash_ex.c:990:1: error: expected '{' at end of input
}
^
..\inc\Src\stm32f0xx_hal_flash_ex.c:990:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
APIs, Headers,state machine files are exists in Project branch, but why the compiler showing errors in H files of driver ?
Looking at C code structure related reason, yes I found some style of C coding in CMSIS h files is different.
what should I do now?1. CDT does not showing errors of my main files, there was a return type problem, I solved it.
3. I think compiler is compiling all files listed in project branch , do you want me to remove some of the files from project folder, is it repeating again as I include paths from C driver?
4. Is there any setting for which only compile my c file?
5. Do you believe, updated version of Java/gcc/Eclipse is needed ?
I am using this HAL driver STM32Cube_FW_F0_V1.6.0 downloaded from STM website.
Hope you will give me some good suggestions.
Regards
HASAN
#arm-cmsis-driver-pack #error #error #demonstration-builder #adding-files-to-the-project #arm-gcc #know-your-tools #arm-gcc #gcc Note: this post was migrated and contained many threaded conversations, some content may be missing.Solved! Go to Solution.
2016-12-13 11:10 PM
Hello Mr Kraal,
Thank you for your suggestion.
I will be keep doing things you explains.
Did you mean I should do it for clearing build confusion? Or project settings in Eclipse ?
Besides this stm provided, TM32Cube_FW_F0_V1.6.0.
As far as I remembered I have opened those project, build successfully.
Here we mainly discussed about custom project build errors.
Regards
Hasan
2016-12-14 01:30 AM
Hello Mr. Hasan,
I understood that the thread was about build errors for custom project. In the link I provided, the author goes from scratch to build a custom project (the classic blinky), and you can see all the errors he encounters all along the process.
I used this link to get up and running with a clean eclipse setup, and to be able to make any custom project I want on any F0, F3 or F4 (I'm using the SPL as I don't like Cube at all, and I'm leaning towards direct register access as I used to do on AVR).
Also you seemed to have tried many different IDEs without success. So maybe you should concentrate on 1 IDE and get it running, otherwise you waste your time trying everything for all different IDEs.
Regards,
Carl
2016-12-14 01:42 AM
Thank you to help me.
Right at the moment, 'getting started ' has not finished for me I know.
I got little understanding about , include paths, pre-processor reasons, there are thousands of setting is in Ecilipse I know.
Link you provided is helpful for sure.
I'm using the SPL as I don't like Cube at all,
Give me some reference and institutions.
2016-12-14 06:04 AM
SPL stands for Standard Peripherals Library. You can get the F0 version there :
.Once unzipped, look for the .chm file which provides a few hints on how to use it (the chapter 'How to use the Standard Peripherals Library').
The rest is up to you.
2016-12-15 09:41 PM
Mr, Kraal,
Thank you or this tools.
Have you ever use Cubemx?
If you did so, what difference you feel among two?
2016-12-16 01:17 AM
No I'm sorry but I have never used CubeMX, so I can't comment on this.
2016-12-16 02:07 AM
Ok, then suggest me any example project can open in SPL
/external-link.jspa?url=http%3A%2F%2Fwww.st.com%2Fcontent%2Fst_com%2Fen%2Fproducts%2Fembedded-software%2Fmcus-embedded-software%2Fstm32-embedded-software%2Fstm32-standard-peripheral-libraries%2Fstsw-stm32html
.