Keil uV5+STM32F407+ChibiOsv3.0 wanted Blink example Topic is solved

[milom]

Hello friends, this is my first speech on the forum and I take this opportunity to greet everyone. I'm absolutely new to ChibiOs and have been used Keil for years. I can not find a recent example in Chibios3 that leads me to start on STM32F407. Creating porting is getting complicated, as there is a lot of difference between the folders and the includes of version 2.6 with 3.0 and I am very confused, not knowing the architecture yet. Does anyone have led blink in Keil for version 3.0 to exchange? thank you ... Marco

[Giovanni]

Hi,

There is one Keil example under /demos/STM32/RT-STM32F303-DISCOVERY/keil, it is for STM32F3, it should be easy to switch it to STM32F4.

Please consider that the easiest way to get started with ChibiOS is to use ChibiStudio, you can practice and understand the system then add a Keil project (no changes to the code required, you can build the same application using any compiler).

Giovanni

[milom]

thanks for the immediate answer Giovanni, I installed the chibistudio correctly and everything works perfectly, I do not like the makefiles, I'm used to IDE I'm lazy to have to add and remove everything manually, and I also have a lot of work on keil ... in short , habits ... and if with a little help I always manage to use my favorite development environment, here is that medicine is sweeter;). However, the example on the C: \ ChibiStudio \ chibios182 \ demos \ STM32 \ RT-STM32F303-DISCOVERY folder does not start with the lack of files included in the tree ... but instead of 176 it works, at least one of the two present is compiled perfectly. I had used the first on 182 and not compiling I thought it was some old demo.
Any advice before starting porting? I thank you for your time.

Marco

[Giovanni]

Hi,

There must be a regression in the Keil project files in 18.x, I need to fix it. This is exactly why I prefer makefiles

When I make a change (paths or new things), I just update one of those .mk files and all projects are updated instantly (because, look into a Makefile, those just include .mk files, there is very little inside).

Now image that all our hundreds demos/projects had a Keil (or IAR or others) XML project files, I would have to manually adjust all of them each time I make a change.

BTW, in next version (19.x) you don't even need to edit Makefiles, everything you place under ./source in your project is compiled and linked automatically.

Giovanni

[milom]

BTW, in next version (19.x) you don't even need to edit Makefiles, everything you place under ./source in your project is compiled and linked automatically.

Giovanni

wow... this is a good idea.. thanks Giovanni

[alexblack]

Hello.

Really current demo for KEIL is not compiled.

I changed it.

ch.zip

Keil Version 5 working demo

(5.41 KiB) Downloaded 276 times

Also need to change the file halconf.h

[alexblack]

For the current trunk the project file must be changed.

ch_trunk_keil.zip

(5.35 KiB) Downloaded 258 times

[Giovanni]

Thanks, I will change as suggested, moving this topic in "bug reports" so it is not lost.

Giovanni