[yocto] arm-none-eabi toolchain

[Lukas Weiss]

Hello,

i need a arm-none-eabi toolchain on my yocto host/build system. Ive tried
to use the arm-poky-linux-gnueabi, but it does not support the arm version
+ format i need:

arm-poky-linux-gnueabi-ld: unrecognised emulation mode: thumb
| Supported emulations: armelf_linux_eabi armelfb_linux_eabi

My Linux runs on a ARM9 (armv5e, elf), I need cortex-m3 (armv7m, thumb).
Where do I get that? I do not find any documentation about *additional*
toolchains to generate code like peripheral-firmware in my yocto
environment.

a) How do I get the toolchain in by yocto host?
b) How to i tell the bitbake-tool to use that toolchain on a certain
receipe (PACKAGE_ARCH, TARGET_SYS, ... )?

Do you have any hints?

Regards,
Lukas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Add custom tools to yocto build environment

[Lukas Weiss]

Hello yocto friends,

I have a problem with yocto you could help me with. The Background:
Iam working on a yocto-linux for a TI OMAP-L138, which is a ARM9+DSP in one
package. The Linux on ARM is running fine, and does everything I want. I
have implemented a kernel driver to start the DSP-Core from the Linux on
the ARM9-Core, but now I need to generate the Firmware for the DSP with the
Yocto buid system. Main problem is, that I need a compiler/toolchain from
TI to compile the Code for the DSP in the yocto build environment.

At this point I did not understand how to add tools to the yocto build
environment at all. I think there must be a way to add software to my host
(build) system for generating code for my target. But I have no idea how to
do it. When I write a BB-recipe, the architecture of the resulting files is
checked to be from targets type (arm in my case), but host tools are of
type x86... (which is totally correct!)

I think I need a recipe, which downloads the compiler/toolchain for the
DSP, extracts and installs it to my yocto build environment, so that I can
use it in another recipe that compiles my code to a loadable firmware-image
(which is placed to my targets rootfs).

Do you have any suggestions for me how to do that?

Thanks,

Lukas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto