| 1 |
On Sun, May 27, 2018 at 05:06:43AM +0200, tuxic@××××××.de wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> too feed a STM32F103C8T6 MCU (Core-M3) with some code to execute, |
| 5 |
> I want a compiler. For that I did a |
| 6 |
> |
| 7 |
> crossdev arm-unknown-linux-gnu |
| 8 |
> |
| 9 |
> . That one failed to build (gcc, binytils seem to be ok). |
| 10 |
> |
| 11 |
That triplet is not going to work for that hardware for two reasons: |
| 12 |
|
| 13 |
- bare-metal implies no kernel so 'linux' is wrong |
| 14 |
- gnu (== glibc) is not going to work on bare-metal |
| 15 |
|
| 16 |
What you're looking for is 'arm-none-eabi', that's what all the vendor |
| 17 |
supplied prebuilt toolchains use. That triplet will use 'newlib' as the |
| 18 |
libc, which is the correct choice for bare-metal. |
| 19 |
|
| 20 |
I wouldv'e said 'arm-unknown-linux-eabi' or the gentoo specific |
| 21 |
'armv7m-softfloat-none-eabi' but for some reasons the binutils |
| 22 |
build chokes on that. However compared to arm-none-eabi the only thing |
| 23 |
these triplets do is change some of the configured defaults (arch/fpu/..., |
| 24 |
see /usr/portage/eclass/toolchain.eclass), so you should be fine with |
| 25 |
'arm-none-eabi'. |
Archives