ChibiOS Free Embedded RTOS

It would be neat with a similar hook for the clean recipe so I could clean up my generated files as well.

I solved it, wasn't that difficult.

Added this to the project makefile:

Any example of how this is used? My makefile-fu is a little low at this time.

I want to run a python-script to generate some *.c and *.h files before compilation and the PRE_MAKE_ALL_RULE_HOOK seems lite the way to accomplish that without hacking anything other than the project makefile.

Ahh, nice, can't believe I didn't think of that

Thanks

Hi,

When creating a new chibios project i usually keep the board folder in the root of my project workspace instead of referring to the os/hal/boards/#boardname#/ since you can set the output path to .. this works fine. the annoying thing is that the path in the generated makefile points to the ...

What is the benefit of doing this in __early_init() instead of in the beginning of main() I can the that the former is called first by the bootup code but will it make any difference?`

I would rather have the bootloader check in main() for two reasons, the __early_init() will be overwritten each ...

I noticed this in the chibios3 release in ChibiStudio14 (3.0.2 i think)

File: chibios3/hal/ports/STM32/STM32F0xx/stm32_registry.h

813: /* USART attributes.*/
814: #define STM32_HAS_USART1 TRUE
815: #define STM32_UART_USART1_RX_DMA_STREAM STM32_DMA_STREAM_ID(1, 3)
816: #define ...

How will I then get enumeration to begin? The pull-up on the data line on this particular board is enabled by GPIOC_11, is there some way I can make the driver point to this pin for enabling the pull-up?

I'm currently playing around with a Olimex STM32-P405 board together with ChibiOS 3.0.0p5. The board is essentialy the same as the P103 but with an STM32F405RG micro instead. I made my own board definition based on the included one for P103 mixed up with the one for STM32F4Discovery.

I've run into ...

Nice!

Will give GCC a try this weekend if I have the time.