Yoctoproject

Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives The goal of this blog post is to look at the mystery of compiler tunes. Since I'm a non believer in micro optimizations I will try to run some benchmarks with different compiler tunes and let them run on the same boards natively as well as inside a docker container. Since I have plenty of i.mx6 quad core boards I will use them for most of the tests. I might run a few tests on other boards as well. We'll only look at CPU/calculations for now and will try to answer a few questions like: What's the difference between armv7a soft float and armv7a hard float? What's the difference between armv7a hard float and code optimized for a cortexa9 hard float? What's the difference between different machines in general - ignoring the compiler tunes? Does code with the same compiler tunes run slower on the native host...

It feels weird to help some get their working build to fail and then for them to be happy about it... (RP) Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives The goal of this blog post is to look into BitBake dependencies. As an example let's take recipe A ( u-boot-phytex-imx ) which needs the output of recipe B ( firmware-imx-8m ) for a successful compilation. (Please don't ask why.) To be more precise here is an excerpt of recipe A ( u-boot-phytex-imx ): # --> this funny u-boot from Phytec needs the ddr_firmware binaries in ${S} # Note: here we copy deployed stuff from another recipe # to the source dir of this recipe! # # DEPENDS deals with build-time depenencies # Read my blog post to find out why DEPENDS does not work here # # DEPENDS += " \ # firmware-imx-8m \ # " # RDEPENDS is wrong anyhow for what I want ...

Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives So you want to get away from the funny golden NXP SDK? I can totally understand that. Now we will be without funny setup scripts, we need to do it the "standard" Yocto/OE way. Are you ready? Install my build environment If not don't complain to me that something didn't work as outlined here. Watch the video on how to install it:   Having said that - it should also work without my build environment. I just didn't test it like that. I will give you hints which layers to check out without it. You didn't follow my instructions - Get two layers manually If you did what I told you to do you already have poky and meta-freescale (and loads of other layers) in /workdir/sources . If not you are on your own and need to check them out manually.   student@e450-tr1:~⟫ cd /workdir/sources student@e450-tr1:/wo...