leaflabs / libmaple

[INACTIVE] C and C++ library for STM32 ARM Cortex-M3 development boards.
http://leaflabs.com/docs/libmaple.html
Other
304 stars 218 forks source link

stm32f4discovery and ARM toolchain from launchpad.net #88

Closed kyab closed 10 years ago

kyab commented 10 years ago

I'm working with libmaple in AeroQuad on stm32f4discovery. I plan to change toolchain from sourcery(included in Maple IDE) to https://launchpad.net/gcc-arm-embedded because I want to use C++11 or something new.

I tried to build AeroQuad's libmaple with launchpad toolchain, but failed on linker. I tried to build leaflabs's libmaple with launchpad toolchain, succeeded but seems lack of stm32f4 support..

I've noticed some difference in 2 libmaple but seems difficult for me to merge them.

Could someone give me direction, which way to utilize libmaple with launchpad toolchain on stm32f4discovery?

mbolivar commented 10 years ago

Hi kyab,

You're right that our libmaple currently lacks STM32F4 support. We added gcc-arm-embedded support with these two commits:

51699a1 fixup! Add support for ARM's GCC ARM embedded toolchain. 2424108 Add support for ARM's GCC ARM embedded toolchain.

I'd try cherry-picking those onto the AeroQuad tree and seeing if that works.

Best, Marti

On 04/18/2014 12:17 PM, kyab wrote:

I'm working with libmaple in AeroQuad on stm32f4discovery. I plan to change toolchain from sourcery(included in Maple IDE) to https://launchpad.net/gcc-arm-embedded because I want to use C++11 or something new.

I tried to build AeroQuad's libmaple with launchpad toolchain, but failed on linker. I tried to build leaflabs's libmaple with launchpad toolchain, succeeded but seems lack of stm32f4 support..

I've noticed some difference in 2 libmaple but seems difficult for me to merge them.

Could someone give me direction, which way to utilize libmaple with launchpad toolchain on stm32f4discovery?

— Reply to this email directly or view it on GitHub https://github.com/leaflabs/libmaple/issues/88.

kyab commented 10 years ago

Thanks. Today I tried cherry-pick into AeroQuad by git subtree merge strategy, but some conflict because there are some differences in directory structure and Makefile including orders.

I think the point to support launchpad.net ARM toolchain is to change some part of linker scripts. I feel it will be easy to do some manual cherry-pick from this repo to AeroQuad version.

BTW is there any plan to port back support for stm32f4 from AeroQuad?