Posted on November 09, 2016 at 06:13 
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.
1 ACCEPTED SOLUTION
Accepted Solutions
Posted on November 09, 2016 at 11:06
The generated (preprocessed) source ends up somewhere in the Debug sub-path (for the Debug build). > 4. For code generation, dont you suggest cubemx? For several F0 variants, you should (still) have the option to download and use the ''old'' SPL. It is a much thinner and ''much less awkward'' library, and proven to be less buggy than Cube. The free EmBlocks/EmBitz toolchain supports this SPL ''out-of-the-box''. For newer MCUs, you can just resort to ''register-hacking'', or free libs (if you find one ...). IMHO CubeMX is an twisted mess - but this is just my personal opinion.
> Still working in 3 different, IDE, Eclipse, Coocox and Keil.
Coocox is also Eclipse-based, at least it was the last time I had a look (and discarded it).> 1.Do you talking about setting in Preferences> c/c++>makefile error persor?
I never tried to mess with the parser settings, and simply ignored those parser remarks. Just to clarify, I experienced the same issue with Eclipse-based toolchains for the x86 family ...> 2. Where you wanted to adding -E?
> 3.Preprocessed output setting is where?
On a plain Eclipse it looks like this (right-click on the project, select ''Options...''):
The generated (preprocessed) source ends up somewhere in the Debug sub-path (for the Debug build). > 4. For code generation, dont you suggest cubemx? For several F0 variants, you should (still) have the option to download and use the ''old'' SPL. It is a much thinner and ''much less awkward'' library, and proven to be less buggy than Cube. The free EmBlocks/EmBitz toolchain supports this SPL ''out-of-the-box''. For newer MCUs, you can just resort to ''register-hacking'', or free libs (if you find one ...). IMHO CubeMX is an twisted mess - but this is just my personal opinion.
