GithubHelp home page GithubHelp logo

linux4sam / meta-atmel Goto Github PK

View Code? Open in Web Editor NEW
90.0 36.0 117.0 1.78 MB

OpenEmbedded/Yocto Project layer for for Microchip SoC (aka AT91)

Home Page: https://www.linux4sam.org/bin/view/Linux4SAM/YoctoProject

License: MIT License

BitBake 71.86% C 23.46% Shell 4.68%
bitbake yocto-project yocto-layer yocto-meta microchip

meta-atmel's Introduction

This layer provides support for Microchip microprocessors (aka AT91)
====================================================================

For more information about the Microchip MPU product line see:
http://www.microchip.com/design-centers/32-bit-mpus
Linux & Open Source on Microchip microprocessors:
http://www.linux4sam.org


Supported SoCs / MACHINE names
==============================
Note that most of the machine names below, have a SD Card variant that can be
built by adding an "-sd" suffix to the machine name.
- SAMA5D2 product family / sama5d2-xplained, sama5d2-xplained-emmc, sama5d27-som1-ek-sd, sama5d27-som1-ek-optee-sd, sama5d2-ptc-ek, sama5d2-icp, sama5d27-wlsom1-ek-sd, sama5d29-curiosity-sd
- SAMA5D4 product family / sama5d4ek, sama5d4-xplained
- SAMA5D3 product family / sama5d3xek, sama5d3-xplained
- AT91SAM9x5 product family (AT91SAM9G15, AT91SAM9G25, AT91SAM9X25, AT91SAM9G35 and AT91SAM9X35) / at91sam9x5ek
- AT91SAM9RL / at91sam9rlek
- AT91SAM9G45 / at91sam9m10g45ek
- SAM9X60 / sam9x60ek, sam9x60-curiosity
- SAMA7G5 / sama7g5ek-sd, sama7g5ek-emmc, sama7g5ek-ospi
- SAM9X75 / sam9x75eb, sam9x75-curiosity


Sources
=======
- meta-atmel
URI: https://github.com/linux4sam/meta-atmel.git
Branch: kirkstone
Tag:linux4microchip-2024.04

Dependencies
============
This Layer depends on :
- poky
URI: https://git.yoctoproject.org/poky
Branch: kirkstone
Tag:yocto-4.0.17

- meta-openembedded
URI: https://git.openembedded.org/meta-openembedded
Branch: kirkstone
Tag/commit:8bb16533532b6abc2eded7d9961ab2a108fd7a5b

- meta-arm (for optee components)
URI: https://git.yoctoproject.org/meta-arm
Branch: kirkstone
Tag:yocto-4.0.2

Build procedure
===============

0/ Create a directory
mkdir my_dir
cd my_dir

1/ Clone yocto/poky git repository with the proper branch ready
git clone https://git.yoctoproject.org/poky && cd poky && \
git checkout -b kirkstone yocto-4.0.17 && cd -

2/ Clone meta-openembedded git repository with the proper branch ready
git clone git://git.openembedded.org/meta-openembedded && \
cd meta-openembedded && git checkout -b kirkstone 8bb165 && cd -

3/ Clone meta-atmel layer with the proper branch ready
git clone https://github.com/linux4sam/meta-atmel.git
git checkout -b kirkstone linux4microchip-2024.04 && cd -

4/ Clone meta-arm layer with the proper branch ready
git clone https://git.yoctoproject.org/meta-arm && cd meta-arm && \
git checkout -b kirkstone yocto-4.0.2 && cd -

5/ Enter the poky directory to configure the build system and start the build process
cd poky
If not created yet, add a new "build-microchip" directory:
mkdir build-microchip
Else, if it's the first time you use Yocto Project templates, and if the
build-microchip directory remains from a previous use, we advise you to start
from a fresh directory. Keep your build-microchip/conf/local.conf file for
reference.

6/ Inside the .templateconf file, you will need to modify the TEMPLATECONF
variable to match the path to the meta-atmel layer "conf" directory:
export TEMPLATECONF=${TEMPLATECONF:-../meta-atmel/conf}

7/ Initialize build directory
source oe-init-build-env build-microchip

8/ To build a small image provided by Yocto Project:
[MACHINE=<machine>] bitbake core-image-minimal

Example for sama5d2-xplained-sd SD card image:
MACHINE=sama5d2-xplained-sd bitbake core-image-minimal

9/ To build the microchip image with no graphics support:
[MACHINE=<machine>] bitbake microchip-headless-image

Example for sama5d2-xplained-sd SD card image:
MACHINE=sama5d2-xplained-sd bitbake microchip-headless-image

10/ To build the microchip image with graphics support (EGT):
[MACHINE=<machine>] bitbake microchip-graphics-image

Example for sama5d2-xplained-sd SD card image:
MACHINE=sama5d2-xplained-sd bitbake microchip-graphics-image

Typical bitbake output
======================
Build Configuration:
BB_VERSION           = "2.0.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "sam9x75-curiosity-sd"
DISTRO               = "poky-atmel"
DISTRO_VERSION       = "4.0.17"
TUNE_FEATURES        = "arm armv5 thumb dsp"
TARGET_FPU           = "soft"
meta                 
meta-poky            
meta-yocto-bsp       = "heads/kirkstone-4.0.17:6d1a878bbf24c66f7186b270f823fcdf82e35383"
meta-oe
meta-networking
meta-webserver
meta-python
meta-initramfs       = "8bb16533532b6abc2eded7d9961ab2a108fd7a5b:8bb16533532b6abc2eded7d9961ab2a108fd7a5b"
meta-atmel           = "heads/linux4microchip-2024.04-rc2:fd6500c866002b78e8ec752e11e34cff0acbc044"
meta-multimedia      = "8bb16533532b6abc2eded7d9961ab2a108fd7a5b:8bb16533532b6abc2eded7d9961ab2a108fd7a5b"
meta-arm
meta-arm-toolchain   = "heads/yocto-4.0.2:96aad3b29aa7a5ee4df5cf617a6336e5218fa9bd"

Contributing
============
To contribute to this layer you should submit the patches for review to:
the github pull-request facility directly or the forum. Anyway, don't forget to
Cc the maintainers.

Microchip Forum:
https://www.microchip.com/forums/f542.aspx

for some useful guidelines to be followed when submitting patches:
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

Maintainers:
Hari Prasath G E <[email protected]>
Nicolas Ferre <[email protected]>

When creating patches insert the [meta-atmel] tag in the subject, for example
use something like:
git format-patch -s --subject-prefix='meta-atmel][PATCH' <origin>

meta-atmel's People

Contributors

alexandrebelloni avatar atorkhov avatar bala-gunasundar avatar claudiubeznea avatar cleberpeter avatar codrin989 avatar cristibirsan avatar cyrillepitchen avatar dharma-b avatar dvincent1 avatar ehristev avatar fedepell avatar gehariprasath avatar gizero avatar hsnhrn avatar htenkod avatar joshwu avatar koansoftware avatar koenkooi avatar kraj avatar ldesroches avatar nikomauno avatar noglitch avatar oohehir avatar patvilchez avatar qschulz avatar razvanstef avatar sandeep2081 avatar sandeepsm avatar texierp avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

meta-atmel's Issues

Illegal charaster in kernel module with ipk

I'm trying to build with linux-at91_4.4.bb kernel, and get error:

ERROR: linux-at91-4.4+gitAUTOINC+061f02b7aa-r0.0 do_package_write_ipk: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function:
0001:
*** 0002:do_package_ipk(d)
0003:
File: '/work/meta/classes/package_ipk.bbclass', lineno: 87, function: do_package_ipk
0083:
0084: os.chdir(oldcwd)
0085:
0086: if error:
*** 0087: raise error
0088:}
0089:do_package_ipk[vardeps] += "ipk_write_pkg"
0090:do_package_ipk[vardepsexclude] = "BB_NUMBER_THREADS"
0091:
Exception: subprocess.CalledProcessError: Command 'PATH="/work/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/work/scripts:/work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/recipe-sysroot/usr/bin/crossscripts:/work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/recipe-sysroot-native/usr/sbin:/work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/recipe-sysroot-native/usr/bin:/work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/recipe-sysroot-native/sbin:/work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/recipe-sysroot-native/bin:/work/bitbake/bin:/work/build/tmp/hosttools" opkg-build kernel-module-snd-soc-wm8904-4.4.26-linux4sam_5.5 /work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/deploy-ipks/sama5d2_roadrunner' returned non-zero exit status 1

Subprocess output:
kernel-module-snd-soc-wm8904-4.4.26-linux4sam_5.5
*** Error: Package name contains illegal characters, (other than [a-z0-9.+-])

opkg-build: Please fix the above errors and try again.

ERROR: linux-at91-4.4+gitAUTOINC+061f02b7aa-r0.0 do_package_write_ipk: Function failed: do_package_ipk
ERROR: Logfile of failure stored in: /work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi/linux-at91/4.4+gitAUTOINC+061f02b7aa-r0.0/temp/log.do_package_write_ipk.11726
ERROR: Task (/work/meta-atmel/recipes-kernel/linux/linux-at91_4.4.bb:do_package_write_ipk) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1356 tasks of which 1105 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/work/meta-atmel/recipes-kernel/linux/linux-at91_4.4.bb:do_package_write_ipk
Summary: There were 18 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Looks like ipkg did't like 'inux4sam_5.5' in kernel module name.
How I understand problem in linux-at91_4.4.bb with:

SRCREV = "linux4sam_5.5"
I search how to fix ot or for workaround..

Error compiling "The postinstall intercept hook" for sama5d3-xplained

All steps followed as written in README

Step 8 command for my board is given below
MACHINE=sama5d3-xplained-sd bitbake core-image-minimal

  1. Compiling error below given
Initialising tasks: 100% |############################################################################################| Time: 0:00:03
Sstate summary: Wanted 114 Found 104 Missed 10 Current 946 (91% match, 99% complete)
NOTE: Executing Tasks
ERROR: core-image-minimal-1.0-r0 do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed, details in /home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs
ERROR: Logfile of failure stored in: /home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.29400
ERROR: Task (/home/dnk025/my_dir/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3266 tasks of which 3249 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/dnk025/my_dir/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

2) log.do_rootfs.29400 file contain given below

NOTE: Running ['oe-pkgdata-util', '-p', '/home/dnk025/my_dir/poky/build-microchip/tmp/pkgdata/sama5d3-xplained-sd', 'glob', '/tmp/installed-pkgsnqhmgoga', '']
NOTE: Installing complementary packages ...  (skipped already provided packages )
NOTE: Running intercept scripts:
NOTE: > Executing update_gio_module_cache intercept ...
NOTE: Exit code 1. Output:
+ [ True = False -a qemuwrapper-cross != nativesdk-qemuwrapper-cross ]
+ qemu-arm -r 3.2.0 -E LD_LIBRARY_PATH=/home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/usr/lib:/home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/lib -L /home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs /home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/usr/libexec/gio-querymodules /home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs/usr/lib/gio/modules/

ERROR: The postinstall intercept hook 'update_gio_module_cache' failed, details in /home/dnk025/my_dir/poky/build-microchip/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs
DEBUG: Python function do_rootfs finished

3) Note:- I don't have below directories in rootfs/usr

/lib/gio/modules/
/libexec/gio-querymodules

How can i resolve this issue?
Thanks

How to add new packages and libraries from a the demo image

Hi everyone,

I am using a SAMA5D2 board.

I was wondering how I can add additionnal packages and functionnalities to my board. Since the demo Image provides a very basic version of Linux. The only package manager I have is opkg and there is no Atmel opkg repository specified in opkg.conf

Has someone ever tried something like this?

Thanks in adavance for your help.

Anne

Workaround sama5d3_xplained toolchain build error with Yocto-poky

Hullo,

Recently, we unboxed a sama5d3_xplained board. After playing with the embedded linux demo (Yocto-poky based), we then try to cross-compile a C program for this target.

Building a toolchain/sysrootfs for sama5d3_xplained using the recommended Yocto-poky process (bitbake core-image-minimal -c populate_sdk) failed because of the underscore in sama5d3_xplained name, which is not compatible with ipk package builder, leading to this error:

DEBUG: Executing python function do_package_ipk
meta-environment-sama5d3_xplained
*** Error: Package name contains illegal characters, (other than [a-z0-9.+-])

After trials and errors, we found that tweaking meta-atmel receipes to accept sama5d3xplained instead of sama5d3_xplained enable to build the toolchain and we finally were able to compile, upload and run a hello program.

Here are the step-by-step instructions to build the toolchain from scratch. Be aware that it typically require a big amount of memory and many hours to go trough the complete build.


Be sure not to be logged as root (chroot issues of bitbake)
Do not close the terminal during process, or source environment again.

clone yocto poky
git clone git://git.yoctoproject.org/poky
cd poky
git checkout daisy-11.0.1 -b my_branch

clone meta-openembedded
git clone git://git.openembedded.org/meta-openembedded
cd meta-openembedded/
git checkout daisy
cd ..

clone meta-atmel
git clone http://github.com/linux4sam/meta-atmel

source build environnement
source oe-init-build-env build-atmel

tweak config
cd build-atmel/conf
vim bblayers.conf
BBLAYERS ?= "
/poky/meta-atmel
/poky/meta
/poky/meta-yocto
/poky/meta-yocto-bsp
/poky/meta-openembedded/meta-oe
/poky/meta-openembedded/meta-networking \

vim local.conf
MACHINE ??= "sama5d3_xplained"
PACKAGE_CLASSES ?= "package_ipk"

build core minimal image
bitbake core-image-minimal
in case of fetch failure, manually download the archive into the downloads directory of build-atmel and create
a void file named "fullnameofarchive.done".

As an alternative, use bitbake -c fetchall core-image-minimal
to download all packages first and run bitbake core-image-minimal
after.
This enable you to fix fetch issues before build, and therefore not
experiment a build failure 5 hours later.

build cross-compiling toolchain and sysrootfs
bitbake core-image-minimal -c populate_sdk

In the very last tasks (after ages of processing), it will fail with
the following error :

DEBUG: Executing python function do_package_ipk
meta-environment-sama5d3_xplained
*** Error: Package name contains illegal characters, (other than [a-z0-9.+-])

This error is due to presence of uppercase, space or underscore or any other characters other than [a-z0-9.+-] in MACHINE definition.

In this case MACHINE ??= "sama5d3_xplained" is illegal because of the underscore character. It seems that this string is added to packages names, thus triggering the error.

We finally tweak meta-atmel to get working with
build-atmel/conf/local.conf
MACHINE ??= "sama5d3xplained"

meta-atmel/conf/machine
cp sama5d3_xplained.conf sama5d3xplained.conf

meta-atmel/recipes-bsp
vim u-boot-at91_2013.07.bb
COMPATIBLE_MACHINE = "(sama5d3xek|at91sam9x5ek|sama5d3_xplained|sama5d3xplained)"

vim at91bootstrap_3.6.2.bb
COMPATIBLE_MACHINE = '(sama5d3xek|sama5d3_xplained|at91sam9x5ek|at91sam9rlek|sama5d3xplained)'

now build the toolchain again
bitbake core-image-minimal -c populate_sdk

It will issue numerous warnings, but at last the sdk is correctly populated into

poky/build-atmel/tmp/deploy/sdk/poky-eglibc-x86_64-core-image-minimal-cortexa5t2hf-vfp-toolchain-1.6.1.sh

Copy the script somewhere safe, execute it and it will deploy the full toolchain.

Now cross-compilation may be done with followings steps:

For the hello.c example:


include <stdio.h>

include <stdlib.h>

int main (int argc, char **argv) {
puts("Hello Toto");
return EXIT_SUCCESS;
}


With this simple Makefile:


all: hello
hello: hello.o
clean:
rm hello *.o


[mateous@localhost hello]$ source ../toolchain/environment-setup-cortexa5t2hf-vfp-poky-linux-gnueabi

[mateous@localhost hello]$ make clean

[mateous@localhost hello]$ make
cc -c -o hello.o hello.c
cc hello.o -o hello

[mateous@localhost hello]$ readelf -l hello

Type de fichier ELF est EXEC (fichier exécutable)
Point d'entrée 0x830c
Il y a 8 en-têtes de programme, débutant à l'adresse de décalage52

En-têtes de programme:
Type Décalage Adr. vir. Adr.phys. T.Fich. T.Mém. Fan Alignement
EXIDX 0x0004c0 0x000084c0 0x000084c0 0x00008 0x00008 R 0x4
PHDR 0x000034 0x00008034 0x00008034 0x00100 0x00100 R E 0x4
INTERP 0x000134 0x00008134 0x00008134 0x00019 0x00019 R 0x1
[Réquisition de l'interpréteur de programme: /lib/ld-linux-armhf.so.3]
[...]

On sama5d3_xplained, with usb cable and a serial terminal like minicom or putty:

sama5d3_xplained login: root
root@sama5d3_xplained:~# ifup eth1
udhcpc (v1.21.1) started
Sending discover...
Sending discover...
Sending select for 192.168.1.6...
Lease of 192.168.1.6 obtained, lease time 259200
/etc/udhcpc.d/50default: Adding DNS 192.168.1.1

Now upload hello program trough Ethernet:
[mateous@localhost hello]$ scp hello [email protected]:hello

And now enjoy:
root@sama5d3_xplained:~# ./hello
Hello Toto

++

How to correctly modify kernel configuration?

I'll start out by saying I know this may not be the correct place for this question but I am unable to log into the at91.com message board to post this question - waiting on response from [email protected] to resolve this. If there is an alternative area I can post this then please let me know.

I am using the SAMA5D2-xplained demo board, as a first step I simply want to enable btrfs. Working through a book I have (and looking at a couple of tutorials) they use config fragments but after much trial an error I have realised that for this to work requires that the linux-at91_4.9.bb has to require linux-yocto for this to work.
I have tried adding my own defconfig inside my layer and including this with an appropriate SRC_URI but, even though my layer has a higher priority, I can't get yocto to include my defconfig instead of the meta-atmel one.

Couple of questions:
What is the correct way to alter the meta-atmel configuration using my own layer? I don't know at this stage if I am just barking up the wrong tree or if there is an issue somewhere.
What is the reason behind the linux-at91_4.9.bb only requiring the dtb and not the entire linux-yocto, which would allow the use of fragments?

automatic generation of SD card and flash image - console over ttyACM0

Hello,
I am writing mostly with regard to issue #65, which is closed now.
Will you please apply the changes to the board SAMA5D3 Xplained? (sama5d3-xplained.conf and sama5d3-xplained-sd.conf)
Specially it would be very nice if the flash and SD card images are generated automatically.

Moreover, I want to configure my system for this board, such that the console operates over the USB port (named USB-A, J6 on the board) and I see it on my computer as /dev/ttyACM0. That is how the factory image on the board does, and also the demo images do it that way (see here) . But I do not know how to do it using Yocto, or when I build the kernel myself. It would be great if that (with other console settings like baudrate) is added as an option in the config files.
Thanks

sama5d4ek use soft float toolchain

Hi, i use yocto to build filesystem for sama5d4ek board.And follow your instruction to setup env values, and it build success.Though i found the all packages and sdk is armel(soft float).Here is my build configuration

Build Configuration:
BB_VERSION        = "1.28.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "sama5d4ek"
DISTRO            = "poky-atmel"
DISTRO_VERSION    = "2.0.2"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
TARGET_FPU        = "vfp-neon"
meta              
meta-yocto        
meta-yocto-bsp    = "jethro:40376446904ae3529be41737fed9a0b650ed167d"
meta-oe           
meta-networking   
meta-python       
meta-ruby         
meta-multimedia   = "jethro:8ab04afbffb4bc5184cfe0655049de6f44269990"
meta-atmel        = "jethro:4765d7064e4916784c15095347eda21cc10aabb4"
meta-qt5          = "jethro:ea37a0bc987aa9484937ad68f762b4657c198617"

Here is my question, I found the variable DEFAULTTUNE is cortexa5thf-neon in file sama5d4.inc. But build packages is armel, not armhf.Is something i forgot config? Thanks!

Meta-Atmel not working for SAMA5D3XEK

The next recipe fails in the process to generate core-image-minimal:
../meta-atmel/recipes-kernel/linux/linux-yocto-custom_3.10.bb, do_compile failed with exit code '1', in specific with:
../linux/arch/arm/mach-at91/sleep_sama5.S: Assembler messages:
23: Error: cannot use register index with PC-relative addressing -- `str r0,.saved_lpr'

I followed the procedure indicated in the README for target sama5d3xek.

Yocto build for sama5d27-som1-ek-sd fails to boot into kernel

Hello,

I am currently working with the Atmel/Microchip SAMA5D27-SOM1-EK demo board and was able to get the provided Linux4SAM 6.0 demo image to successfully boot from SD card. I then followed the readme file from meta-atmel layer for step by step Yocto build procedure and the build completed successfully. I then flashed the SD card via SAM-BA with the generated .wic file and it completed successfully as well. However, whenever I attempt to boot up into the built image, it fails to load the kernel.

SD/MMC: Image: Read file u-boot.bin to 0x23f00000
MMC: ADMA supported
SD: Card Capacity: High or Extended
SD: Specification Version 3.0X
SD/MMC: Done to load image
<debug_uart>

U-Boot 2018.07-linux4sam_6.0 (Jan 23 2019 - 14:27:07 +0000)

CPU: SAMA5D27 1G bits DDR2 SDRAM
Crystal frequency: 24 MHz
CPU clock : 492 MHz
Master clock : 164 MHz
DRAM: 128 MiB
MMC: sdio-host@a0000000: 0, sdio-host@b0000000: 1
Loading Environment from FAT... OK
In: serial@f8020000
Out: serial@f8020000
Err: serial@f8020000
Net: eth0: ethernet@f8008000
Hit any key to stop autoboot: 0
** Unable to read file at91-sama5d27_som1_ek.dtb **
** Unable to read file zImage **
=>

I see that the machine configuration file for sama5d27-som1-ek-sd contains:

KERNEL_DEVICETREE = "
at91-sama5d27_som1_ek.dtb
"

IMAGE_BOOT_FILES = "BOOT.BIN u-boot.bin sama5d27_som1_ek.itb"

MACHINE_ESSENTIAL_EXTRA_RDEPENDS = " dt-overlay-at91"

Why would it try to read file at91-sama5d27_som1_ek.dtb and not sama5d27_som1_ek.itb? Perhaps I'm missing something.

Is angstrom-sdk and arm sdk necessary for at91sam9m10 compilation?

Hi,

in older versions of u-boot the angstrom-sdk ( for compiling u-boot) and arm sdk ( for compiling bootstrap) was needed if I understood it correctly.

I did not find any depenency to this sdk's so they are not needed anymore using current yocto releases?

SOC: at91sam9m10

u-boot-at91: unreachable SRC_URI in 2018.07

The server SRC_URI points to in u-boot-at91_2018.07.bb does not seem to be publicly available. Was this meant to be SRC_URI = "git://github.com/linux4sam/u-boot-at91.git;protocol=https;branch=${UBRANCH}" instead?

Here there seem to be the corresponding branch which I'm giving a test right now...

Automated generation of u-boot environment files

I would like to discuss a feature I am interested in implementing: automated generation of u-boot environment binary files, similar to https://github.com/koenkooi/meta-edison/blob/master/recipes-bsp/u-boot/u-boot-target-env.inc

There are at least two options to go about this:

  • The same as in meta-edison layer, that is, u-boot recipe sources file defining commands which generate u-boot environment files
  • Separate recipe file, say "u-boot-env-gen", which would handle solely environment generation.

I would prefer to go the first way, as logically this should be part of u-boot recipe, the same as kernel recipes handle device tree compilation.

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

atmel@ubuntu:~/my_dir/poky/build-atmel$ bitbake atmel-qt5-demo-image
Parsing recipes: 100% |#########################################| Time: 00:00:37
Parsing of 1934 .bb files complete (0 cached, 1934 parsed). 2490 targets, 362 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.30.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "sama5d2-xplained"
DISTRO = "poky-atmel"
DISTRO_VERSION = "2.1.2"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "krogoth:3bf928a3b6354bc09c87fcbf9e3972c8d368aaa3"
meta-atmel = "krogoth:af0fb3550bba8bbcdecef9e1d40a435a83b74335"
meta-oe
meta-networking
meta-python
meta-ruby
meta-multimedia = "krogoth:851a064b53dca3b14dd33eaaaca9573b1a36bf0e"
meta-qt5 = "krogoth:2b1871f0d139dc3caaa779a32a1931409c245a36"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: qtbase-5.6.2+gitAUTOINC+b4ada3f0d8-r0 do_patch: Command Error: 'quilt --quiltrc /home/atmel/my_dir/poky/build-atmel/tmp/sysroots/x86_64-linux/etc/quiltrc push' exited with 1 Output:
Applying patch 0001-Fix-building-without-OpenGL-support.patch
patching file src/widgets/kernel/qwidgetbackingstore.cpp
Hunk #1 FAILED at 61.
1 out of 1 hunk FAILED -- rejects in file src/widgets/kernel/qwidgetbackingstore.cpp
Patch 0001-Fix-building-without-OpenGL-support.patch can be reverse-applied
ERROR: qtbase-5.6.2+gitAUTOINC+b4ada3f0d8-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/atmel/my_dir/poky/build-atmel/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/qtbase/5.6.2+gitAUTOINC+b4ada3f0d8-r0/temp/log.do_patch.24614
ERROR: Task 646 (/home/atmel/my_dir/meta-qt5/recipes-qt/qt5/qtbase_git.bb, do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 782 tasks of which 765 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
/home/atmel/my_dir/meta-qt5/recipes-qt/qt5/qtbase_git.bb, do_patch
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

qtbase patch error on Thud branch

I get the following errors when apply the patch's from qtbase on Thud branch:

Applying patch 0004-Provide-access-to-linuxfb-dri-fd-through-platform.patch patching file src/platformsupport/fbconvenience/qfbscreen_p.h patching file src/plugins/platforms/linuxfb/qlinuxfbdrmscreen.cpp patching file src/plugins/platforms/linuxfb/qlinuxfbdrmscreen.h patching file src/plugins/platforms/linuxfb/qlinuxfbintegration.cpp Hunk #1 FAILED at 172. 1 out of 1 hunk FAILED -- rejects in file src/plugins/platforms/linuxfb/qlinuxfbintegration.cpp patching file src/plugins/platforms/linuxfb/qlinuxfbscreen.h Patch 0004-Provide-access-to-linuxfb-dri-fd-through-platform.patch does not apply (enforce with -f)

*Using patch's from master branch the error is solved.

meta-qt5: On Thud branch the version of QT is 5.11.

Qt5 doesn't build with warrior branch

The warrior branch of meta-atmel doesn't patch and build correctly against Qt 5.12.3.

The patches in meta-atmel/dynamic-layers/qt5-layer/recipes-qt/qt5/files need to be updated to match those in the thud branch.

-Andy.

Duplicated/overridden recipes from meta-oe and core

meta-atmel has duplicated few recipes from meta-oe

swig:
  meta                 3.0.12
  meta-atmel           3.0.8

cjson:
  meta-atmel           1.7.4
  meta-oe              1.7.14

first one is easy, please start using the version coming from oe-core
for second issue, I think only layer you want to depend on is oe-core
which means if you do not keep a copy of cjson in this layer then you have to
add a dependency on meta-oe which is actually preferred to status quo
because currently if meta-atmel is used then it silently overrides the version
from meta-oe since it has higher layer priority.

Other option is to try to move cjson recipe to oe-core and that way you don't
have to add dependency on meta-oe, but you still have to start using the version
from oe-core

sama5d2 config files have inconsistencies

The documentation available here :

http://www.at91.com/linux4sam/bin/view/Linux4SAM/Sama5d2XplainedMainPage#Build_Yocto_Poky_rootfs_from_sou

Describes how to rebuild a full linux system for the xplained boardusing the "sama5d2-xplained" config file

However the given example produces images which are hard to use, in particular the resulting u-boot binary ships with an "ubi" command line while the rootfs is provided in .tar.gz format

  • It seems odd that the main image would expect an UBI rootfs while there is no flash-based mass storage on the board
  • If the bootloader expects an ubi root, an .ubi product file would be better suited than a tarball
  • Considering the documentation only describes how to use a system hosted on the sdcard, it should rather reference the sama5d2-sd machine

Regarding the sama5d2-xplained-sd MACHINE,

  • It generates binaries + a tarball, it would be useful to add "ext3" to IMAGE_FSTYPES or generate a full .sdcard image.
  • By default /etc/inittab is populated with : S0:12345:respawn:/sbin/getty -L 115200 ttyS0, however u-boot is setup with baudrate=56700, and boots the kernel with "bootargs=console=ttyS0,57600", therefore once the kernel has booted, the console outputs garbage.

Remove dtc 1.4.x recipe

I see this layer is housing an older version of dtc 1.4.x than core (OE-Core 1.5.x ), this causes problems due to this layer having higher priority this one gets picked up. So I would like to ask

  1. Do we still need to use dtc 1.4.x in meta-atmel ? if no then delete it
  2. If we need to use it for some reason, then lets rename it to something like dtc-145.bb and convert all references to use that PN inside this layer, so this does not spread around t other layers in multi-BSP setup.

I can cook up the patch, I just need to know the above two points

EGL Implementation

I've been trying to compile Qt Webengine for sama5d27 through the Thud branch without success a few days :(

I checked through the Qt page that one of the requirements of it is OpenGL ES 2.0. I also noticed that the recipe qtbase_%.bbappend in this layer removes the EGLFS plugin if x11 is not defined and unconditionally remove the virtual/egl, both of which are responsible for the interface between OpenGL and the adopted window system.

With a recipe of its own I removed the above definitions and added "gles2" and "eglfs" to PACKAGECONFIG, but I still get errors regarding the atmel-hlcdc driver. Looking again at the Qt page there is a comment regarding the need for each vendor to develop their own adaptation to support the EGL.

Anyway, is there support for EGL for the SAMA5 family? Is it possible to use Qt Webengine with the same?

Could someone suggest me some material (book, presentation, source code, anything) to read about the graphical issues related to linux embedded, I read several materials and so far I have not been able to understand several aspects on that topic.

Thank you.

./scripts/get_sram_size.sh: bc: not found

I have this error:

| LD sama5d2_roadrunner-dataflashboot-linux--dt-3.8.9.elf
| ./scripts/get_sram_size.sh: 1: ./scripts/get_sram_size.sh: bc: not found
| Makefile:338: recipe for target 'ChkFileSize' failed
| make: *** [ChkFileSize] Error 3
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /work/build/tmp/work/sama5d2_roadrunner-poky-linux-gnueabi
/at91bootstrap/3.8+gitAUTOINC+d7a52fbf2b-r0.0/temp/log.do_compile.20910)
ERROR: Task (/work/meta-atmel/recipes-bsp/at91bootstrap/at91bootstrap_git.bb:do_compile) failed with exit code '1'

Adding

DEPENDS += "bc-native"

to at91bootstrap*.bb helps

machines use CPU tunes instead of ISA tunes

The machine configs have:

DEFAULTTUNE = "arm926ejs"

instead of using the default 'armv5te'. This breaks distributions that support multiple armv5te machines since the package architecture will be 'arm926ejs' instead of 'armv5te'

The cortexa5 machines also get it wrong, but the tune file saves the day :)

Control a LED with BUTTON on SAMA5D27-SOM1-EK1 board

Hello!

I think that my question is a little bit dumb but i am really stuck in this problem. I have an embedded SAMA5D27-SOM1-EK1 board which i build Linux OS image version 4.14 with YOCTO project. Now i want to control a RBG LED ( one of the three existing in the shematics of the board ) using a push USER BUTTON existing both on the board. I must make the LED Lights when I push the Button. For the moment i have only the PINS of the Led and the Button. I don't know what i must do now. But i think that i must modify dts file. I don't know how.

Thank you for your help!

meta-atmel support for at91sam9m10g45ek

Are meta-atmel and the other linux4sam repositories still supporting at91sam9m10g45ek in version zeus?

Should the following configuration work out of the box with the evaluation kit?
meta-atmel --> zeus
linux --> 4.19
u-boot --> 2019.04
at91bootstrap --> master

Thanks

Why does a core-image-minimal need qt?

layer                 path                                      priority
==========================================================================
meta                  /home/student/poky/meta                   5
meta-yocto            /home/student/poky/meta-yocto             5
meta-yocto-bsp        /home/student/poky/meta-yocto-bsp         5
meta-atmel            /home/student/poky/meta-atmel             10
MACHINE=sama5d3-xplained bitbake core-image-minimal
ERROR: ParseError at /home/student/poky/meta-atmel/recipes-qt/apps/applicationlauncher_1.5.bb:17: Could not inherit file classes/qmake5.bbclass                         

This fixed it, but I think qt recipes should not be required by default:

layer                 path                                      priority
==========================================================================
meta                  /home/student/poky/meta                   5
meta-yocto            /home/student/poky/meta-yocto             5
meta-yocto-bsp        /home/student/poky/meta-yocto-bsp         5
meta-atmel            /home/student/poky/meta-atmel             10
meta-qt5              /home/student/poky/meta-qt5               7

arm-poky-linux-gnueabi-g++: error: cec-follower.cpp: No such file or directory

Hello:
So i was following the readme file from this meta layer for yocto-poky and all went good up to step:

11/ Build Atmel demo images
bitbake atmel-qt5-demo-image

I added the lines in conf/local.conf

then started build, and got this error. Ill put the whole log now:

DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 1
make all-recursive
make[1]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build'
Making all in v4l-utils-po
make[2]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/v4l-utils-po'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/v4l-utils-po'
Making all in libdvbv5-po
make[2]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/libdvbv5-po'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/libdvbv5-po'
Making all in lib
make[2]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib'
Making all in libv4lconvert
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4lconvert'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4lconvert'
Making all in libv4l2
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l2'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l2'
Making all in libv4l1
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l1'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l1'
Making all in libv4l2rds
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l2rds'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l2rds'
Making all in libv4l-mplane
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l-mplane'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libv4l-mplane'
Making all in libdvbv5
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libdvbv5'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib/libdvbv5'
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib'
make[2]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/lib'
Making all in utils
make[2]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils'
Making all in libv4l2util
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/libv4l2util'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/libv4l2util'
Making all in libmedia_dev
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/libmedia_dev'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/libmedia_dev'
Making all in decode_tm6000
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/decode_tm6000'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/decode_tm6000'
Making all in ivtv-ctl
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/ivtv-ctl'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/ivtv-ctl'
Making all in ir-ctl
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/ir-ctl'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/ir-ctl'
Making all in cx18-ctl
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cx18-ctl'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cx18-ctl'
Making all in keytable
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/keytable'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/keytable'
Making all in media-ctl
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/media-ctl'
make all-am
make[4]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/media-ctl'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/media-ctl'
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/media-ctl'
Making all in v4l2-compliance
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-compliance'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-compliance'
Making all in v4l2-ctl
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-ctl'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-ctl'
Making all in v4l2-dbg
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-dbg'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-dbg'
Making all in v4l2-sysfs-path
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-sysfs-path'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/v4l2-sysfs-path'
Making all in cec-ctl
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cec-ctl'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cec-ctl'
Making all in cec-compliance
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cec-compliance'
arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../v4l-utils-1.12.3/utils/cec-compliance -I../.. -I../../../v4l-utils-1.12.3/lib/include -Wall -Wpointer-arith -D_GNU_SOURCE -I../../../v4l-utils-1.12.3/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -c -o cec-compliance.o ../../../v4l-utils-1.12.3/utils/cec-compliance/cec-compliance.cpp
arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../v4l-utils-1.12.3/utils/cec-compliance -I../.. -I../../../v4l-utils-1.12.3/lib/include -Wall -Wpointer-arith -D_GNU_SOURCE -I../../../v4l-utils-1.12.3/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -c -o cec-test.o ../../../v4l-utils-1.12.3/utils/cec-compliance/cec-test.cpp
arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../v4l-utils-1.12.3/utils/cec-compliance -I../.. -I../../../v4l-utils-1.12.3/lib/include -Wall -Wpointer-arith -D_GNU_SOURCE -I../../../v4l-utils-1.12.3/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -c -o cec-test-adapter.o ../../../v4l-utils-1.12.3/utils/cec-compliance/cec-test-adapter.cpp
arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../v4l-utils-1.12.3/utils/cec-compliance -I../.. -I../../../v4l-utils-1.12.3/lib/include -Wall -Wpointer-arith -D_GNU_SOURCE -I../../../v4l-utils-1.12.3/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -c -o cec-test-audio.o ../../../v4l-utils-1.12.3/utils/cec-compliance/cec-test-audio.cpp
arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../v4l-utils-1.12.3/utils/cec-compliance -I../.. -I../../../v4l-utils-1.12.3/lib/include -Wall -Wpointer-arith -D_GNU_SOURCE -I../../../v4l-utils-1.12.3/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -c -o cec-test-power.o ../../../v4l-utils-1.12.3/utils/cec-compliance/cec-test-power.cpp
../../arm-poky-linux-gnueabi-libtool --tag=CXX --mode=link arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -lrt -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -pthread -o cec-compliance cec-compliance.o cec-test.o cec-test-adapter.o cec-test-audio.o cec-test-power.o
arm-poky-linux-gnueabi-libtool: link: arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -pthread -o cec-compliance cec-compliance.o cec-test.o cec-test-adapter.o cec-test-audio.o cec-test-power.o -lrt -pthread
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cec-compliance'
Making all in cec-follower
make[3]: Entering directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cec-follower'
../../../v4l-utils-1.12.3/utils/cec-ctl/msg2ctl.pl 2 ../../../v4l-utils-1.12.3/include/linux/cec.h ../../../v4l-utils-1.12.3/include/linux/cec-funcs.h >cec-table.h
arm-poky-linux-gnueabi-g++ -march=armv5e -marm --sysroot=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot -DHAVE_CONFIG_H -I. -I../../../v4l-utils-1.12.3/utils/cec-follower -I../.. -I../../../v4l-utils-1.12.3/lib/include -Wall -Wpointer-arith -D_GNU_SOURCE -I../../../v4l-utils-1.12.3/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0=/usr/src/debug/v4l-utils/1.12.3-r0 -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot-native= -fdebug-prefix-map=/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/recipe-sysroot= -fvisibility-inlines-hidden -c -o cec-follower.o cec-follower.cpp
arm-poky-linux-gnueabi-g++: error: cec-follower.cpp: No such file or directory
arm-poky-linux-gnueabi-g++: fatal error: no input files
compilation terminated.
ERROR: oe_runmake failed
Makefile:556: recipe for target 'cec-follower.o' failed
make[3]: *** [cec-follower.o] Error 1
make[3]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils/cec-follower'
Makefile:468: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build/utils'
Makefile:574: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/build'
Makefile:501: recipe for target 'all' failed
make: *** [all] Error 2
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_compile (log file is located at /home/afachini/poky/build-atmel/tmp/work/armv5e-poky-linux-gnueabi/v4l-utils/1.12.3-r0/temp/log.do_compile.26453)

Can you tell me what might be wrong?, the Hardware is SAM9x35 Ronetix Evaluation Kit with LCD. So the MACHINE is "at91sam9x5ek"

Regards.-

nano.specs support

Hi,

Im trying to re-compile binaries for SAM-BA using the Cross compiler exposed by Yocto (Krogoth).

Ive found that there is no support for nano.specs. Is this support to be added for Atmel targets?

Ive downloaded example recipes for "newlib" ie https://github.com/jurobystricky/meta-zephyr/tree/master/recipes-core/newlib

Id like to use the CC generated by Yocto rather that the downloaded version. Could someone help please.

Thanking you in advance..

Yocto build for machine sama5d27-som1-ek-sd fails to build at do_image_wic

I've tried building core-image-minimal using the sumo branch of meta-atmel but it fails at do_image_wic

| output: install: cannot stat '/home/rufilla/projects/luminite/luminite-build-sys/data/build-areas/build-area-sumo/build/tmp/deploy/images/sama5d27-som1-ek-sd/sama5d27_som1_ek.itb': No such file or directory

I've checked and no itb file exists in the deploy directory.

After looking through meta-atmel I think this error occurs because of
IMAGE_BOOT_FILES = "BOOT.BIN u-boot.bin sama5d27_som1_ek.itb"
in the machine configuration file.

If I revert the latest commit, 45cf7c8, so that the machine configuration now contains:
IMAGE_BOOT_FILES = "BOOT.BIN u-boot.bin zImage
zImage-at91-sama5d27_som1_ek.dtb;at91-sama5d27_som1_ek.dtb
"
It builds fine.

So should it be creating the itb file (which I assume means the kernel and device tree are in a FIT image) or was the commit incorrect for this machine and it should be using zImage?

I would prefer to use FIT images if possible so what would I need to do to ensure this machine builds FIT images?

Import error cryptoauthlib.

i am trying to run these examples https://github.com/MicrochipTech/cryptoauthtools/tree/master/python/examples
but i am not able to import cryptoauthlib and got this error below :
File "/usr/lib/python3.8/site-packages/cryptoauthlib/init.py". line 16. in load_cryptoauthlib()
File "/usr/lib/python3.8/site-packages/cryptoauthlib/library.py". line 83. in load_cryptoauthlib()
_CRYPTO_LIB =ctypes.cdll.LoadLibrary(os.path.join(curr_path. "libcryptoauth.so"))
File "/usr/lib/python3.8/ctypes/init.py". line 451. in LoadLibrary return self._dlltype(name)
File "/usr/lib/python3.8/ctypes/init.py". line 373. in init self._handle = _dlopen(self._name mode)
OSError : /usr/lib/python3.8/site-packages/cryptoauthlib/libcryptoauth.so: undefined symbol: hid_open

How can i fix this? thanks a lot!

sumo wic generation fail

While trying to build the core-image-minimal for the sama5d3_xplained (sd) i got the following error:

| DEBUG: Executing shell function do_image_wic | INFO: Creating image(s)... | | WARNING: bootloader config not specified, using defaults | | ERROR: _exec_cmd: install -m 0644 -D /media/floris/1TB_WD/eoi-datalogger/poky/build/tmp/deploy/images/sama5d3-xplained-sd/sama5d3_xplained.itb /media/floris/1TB_WD/eoi-datalogger/poky/build/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-sama5d3-xplained-sd-20181103164502/tmp.wic.fplzietd/boot.1/sama5d3_xplained.itb returned '1' instead of 0 | output: install: cannot stat '/media/floris/1TB_WD/eoi-datalogger/poky/build/tmp/deploy/images/sama5d3-xplained-sd/sama5d3_xplained.itb': No such file or directory | | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_image_wic (log file is located at /media/floris/1TB_WD/eoi-datalogger/poky/build/tmp/work/sama5d3_xplained_sd-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_image_wic.3597) ERROR: Task (/media/floris/1TB_WD/eoi-datalogger/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_wic) failed with exit code '1' NOTE: Tasks Summary: Attempted 2439 tasks of which 5 didn't need to be rerun and 1 failed.

probably something got broken, not sure how to fix this
commit 4d4276b

Build issue with QtWebEngine

Hi Razvan,

Thanks for letting me know. I have taken the files from the thud branch and replaced the ones in my working directory and QtBase now builds correctly.

I have found another build issue with QtWebEngine. Looking in the log files directory it seems as though the only error I can see is in log.do_configure:

khronos development headers appear to be missing (mesa/libegl1-mesa-dev)
QtWebEngine will not be built.

Is this there another patch I need to cherrypick from thud to fix this?

-Andy.

Originally posted by @andy-sdc in #142 (comment)

Can't build kernel fitImage on morty

Added two lines, in to my local.conf file

KERNEL_CLASSES ?= " kernel-fitimage "
KERNEL_IMAGETYPE ?= "fitImage"

Error message:

ERROR: Nothing PROVIDES 'u-boot'
ERROR: u-boot was skipped: PREFERRED_PROVIDER_virtual/bootloader set to u-boot-at91, not u-boot
ERROR: Required build target 'virtual/kernel' has no buildable providers.
Missing or unbuildable dependency chain was: ['virtual/kernel', 'u-boot']

Without those lines Kernel compiles without errors

Qtbase version desyncronizaton for 'thud' branch

Hi all,

There's desynchronization between 'thud' branches of 'meta-atmel' and 'meta-qt5' layers.
I use meta-qt5 layer - commit 1520d5b2b2beec5e1c3209d3178219e93ef08bca (HEAD -> thud, origin/thud-next, origin/thud, origin/jansa/thud),
where's used qtbase of 5.11.3 version.

But in the meta-atmel layer - commit 5d8d83e (HEAD -> thud, tag: linux4sam_6.1-rc5, tag: linux4sam_6.1, origin/thud)
is used .bbappend file with a patch for qtbase 5.12.2 (0004-Provide-access-to-linuxfb-dri-fd-through-platform.patch):

commit cbda4ed
Author: Razvan Stefanescu [email protected]
Date: Fri May 17 12:54:18 2019 +0300

qtbase: Fix compilation issue for QT5.12.2

Signed-off-by: Razvan Stefanescu <[email protected]>

Bitbake log:

Build Configuration:
BB_VERSION = "1.40.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "sama5d27-som1-ek-sd"
DISTRO = "poky-atmel"
DISTRO_VERSION = "2.6.2"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa5"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:2dd610cc27c606f731f83047b4766787aab6e6b2"
meta-oe
meta-python
meta-networking = "HEAD:9b3b907f30b0d5b92d58c7e68289184fda733d3e"
meta-mender-atmel = "HEAD:efc8ae3c460f93f8ecbce1f76024a0a266e2992e"
meta-mender-core
meta-mender-demo = "thud:352cd81fe4dd6e44ba0819da1d8e189109e805e6"
meta-iot-cloud = "feature/bsp_porting_RLPR-64:7b0765f55fc5aa1dc55e15e415145e5d2c3c345f"
meta-qt5 = "thud:1520d5b2b2beec5e1c3209d3178219e93ef08bca"
meta-atmel = "thud:5d8d83e656246c8ca534c6288bbb7fbb7afda683"
meta-rollo = "feature/bsp_porting_RLPR-64:7b0765f55fc5aa1dc55e15e415145e5d2c3c345f"

Initialising tasks: 100% |###############################################################################| Time: 0:00:01
Sstate summary: Wanted 477 Found 12 Missed 465 Current 240 (2% match, 35% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: qtbase-5.11.3+gitAUTOINC+08de243eaa-r0 do_patch: Command Error: 'quilt --quiltrc /home/timandr/projects/rollo/rollo-firmware/build_sama5d27/tmp/work/cortexa5t2hf-neon-poky-linux-gnueabi/qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output:
Applying patch 0004-Provide-access-to-linuxfb-dri-fd-through-platform.patch
patching file src/platformsupport/fbconvenience/qfbscreen_p.h
patching file src/plugins/platforms/linuxfb/qlinuxfbdrmscreen.cpp
patching file src/plugins/platforms/linuxfb/qlinuxfbdrmscreen.h
patching file src/plugins/platforms/linuxfb/qlinuxfbintegration.cpp
Hunk #1 FAILED at 173.
1 out of 1 hunk FAILED -- rejects in file src/plugins/platforms/linuxfb/qlinuxfbintegration.cpp
patching file src/plugins/platforms/linuxfb/qlinuxfbscreen.h
Patch 0004-Provide-access-to-linuxfb-dri-fd-through-platform.patch does not apply (enforce with -f)
ERROR: qtbase-5.11.3+gitAUTOINC+08de243eaa-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/timandr/projects/rollo/rollo-firmware/build_sama5d27/tmp/work/cortexa5t2hf-neon-poky-linux-gnueabi/qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/temp/log.do_patch.9063
ERROR: Task (/home/timandr/projects/rollo/rollo-firmware/build_sama5d27/../meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1672 tasks of which 673 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/timandr/projects/rollo/rollo-firmware/build_sama5d27/../meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Is there currently a solution to this issue?

Thanks.

Are the tools under scripts/ still relevant?

I am currently working with a sam9x20ek and was looking into having a simplified flashing procedure with what meta-atmel offers. I've been therefore looking to improve the scripts (shell and tcl) under scripts/ for the board I'm using but after some studing my feeling is that the code there is totally obsolete now, as I would think that the way it is calling sam-ba is wrong (ie. all missing command options) and that now sam-ba automation is not TCL based anymore but uses QML (I cannot see the whole history of the sam-ba tool as in GitHub I can only got back as far as 3.0 or so).

Am I correct or did I really overlook something? If I'm correct I would suggest (I will gladly do a PR) to remove that scripts as they can be very confusing for newcomers and are obviously not working. If I'm wrong I'd appreciate if you can give me some pointers as I'd gladly improve it for the sam9x20ek I'm using.

Should my understanding that that code is obsolete, would replacing those scripts with something similar but QML based (as offered in the demo images already) be worth an inclusion into meta-atmel?

Thanks!
Federico

Error by building core minimal image

Hello,
I got an error by step 9 of the README file, namely by executing
bitbake core-image-minimal
I get
... fatal error: linux/compiler-gcc6.h: No such file or directory | #include gcc_header(__GNUC__) | ^ ...
Apparently there is a problem with compiling the kernel with GCC 6, and a file linux/compiler-gcc6.h is missing. A similar issue is addressed here for meta-fsl-arm.

I also add the complete output:

~/mcg/poky/build-atmel$ bitbake core-image-minimal
WARNING: /home/rooholah/mcg/meta-atmel/recipes-kernel/linux/linux-at91_3.10.bb: Unable to get checksum for linux-at91 SRC_URI entry defconfig: file could not be found                                                                      
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/u-boot/u-boot-at91_2015.01.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/u-boot/u-boot-at91_2014.07.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/u-boot/u-boot-at91_2013.07.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/at91bootstrap/at91bootstrap_3.7.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/at91bootstrap/at91bootstrap_3.7.2.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/at91bootstrap/at91bootstrap_3.7.1.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/at91bootstrap/at91bootstrap_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/u-boot/u-boot-at91_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-qt5/recipes-qt/qt5/qtbase_git.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/at91bootstrap/at91bootstrap_3.8.4.bb: base_contains is deprecated, please use bb.utils.contains instead.
NOTE: /home/rooholah/mcg/meta-atmel/recipes-bsp/at91bootstrap/at91bootstrap_3.8.3.bb: base_contains is deprecated, please use bb.utils.contains instead.
Parsing recipes: 100% |################################################################################| Time: 0:01:28
Parsing of 1964 .bb files complete (0 cached, 1964 parsed). 2544 targets, 395 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.31.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Debian-8.5"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "sama5d3-xplained"
DISTRO            = "poky-atmel"
DISTRO_VERSION    = "2.1+snapshot-20160728"
TUNE_FEATURES     = "arm armv7a vfp thumb            callconvention-hard            cortexa5"
TARGET_FPU        = "hard"
meta              
meta-poky         
meta-yocto-bsp    = "master:039f47ad197a9a53109c9f3deadd9c35e62c056d"
meta-atmel        = "master:df10071966a78f0a808216bd02cf961b171cbb0c"
meta-oe           
meta-networking   
meta-python       
meta-ruby         
meta-multimedia   = "master:5c69367d848271cdf3a3bd1a087665f324d3fd34"
meta-qt5          = "master:ecf7db0bd5012162d5fff5cb25f9a07a1a6e084a"

NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.1/x86_64-nativesdk-libc.tar.bz2;sha256sum=84e89ed675156d13a27fe56e8433f5fa9662802349bb0bbe9e6eba577fc140d3
--2016-07-28 15:38:53--  http://downloads.yoctoproject.org/releases/uninative/1.1/x86_64-nativesdk-libc.tar.bz2
Resolving downloads.yoctoproject.org (downloads.yoctoproject.org)... 198.145.20.127
Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.20.127|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2481482 (2.4M) [application/octet-stream]
Saving to: ‘/home/rooholah/mcg/poky/build-atmel/downloads/uninative/84e89ed675156d13a27fe56e8433f5fa9662802349bb0bbe9e6eba577fc140d3/x86_64-nativesdk-libc.tar.bz2’


2016-07-28 15:38:57 (585 KB/s) - ‘/home/rooholah/mcg/poky/build-atmel/downloads/uninative/84e89ed675156d13a27fe56e8433f5fa9662802349bb0bbe9e6eba577fc140d3/x86_64-nativesdk-libc.tar.bz2’ saved [2481482/2481482]

Initialising tasks: 100% |#############################################################################| Time: 0:00:03
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: linux-at91-4.1+gitAUTOINC+00ea8f3f67-r0 do_compile: oe_runmake failed
ERROR: linux-at91-4.1+gitAUTOINC+00ea8f3f67-r0 do_compile: Function failed: do_compile (log file is located at /home/rooholah/mcg/poky/build-atmel/tmp/work/sama5d3_xplained-poky-linux-gnueabi/linux-at91/4.1+gitAUTOINC+00ea8f3f67-r0/temp/log.do_compile.13779)
ERROR: Logfile of failure stored in: /home/rooholah/mcg/poky/build-atmel/tmp/work/sama5d3_xplained-poky-linux-gnueabi/linux-at91/4.1+gitAUTOINC+00ea8f3f67-r0/temp/log.do_compile.13779
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 zImage CC=arm-poky-linux-gnueabi-gcc  -mno-thumb-interwork -marm -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd
| ERROR: oe_runmake failed
|   GEN     ./Makefile
| scripts/kconfig/conf  --silentoldconfig Kconfig
|   CHK     include/config/kernel.release
|   GEN     ./Makefile
|   WRAP    arch/arm/include/generated/asm/bitsperlong.h
|   CHK     include/generated/uapi/linux/version.h
|   WRAP    arch/arm/include/generated/asm/cputime.h
|   UPD     include/generated/uapi/linux/version.h
|   WRAP    arch/arm/include/generated/asm/current.h
|   WRAP    arch/arm/include/generated/asm/emergency-restart.h
|   WRAP    arch/arm/include/generated/asm/errno.h
|   WRAP    arch/arm/include/generated/asm/exec.h
|   WRAP    arch/arm/include/generated/asm/ioctl.h
|   WRAP    arch/arm/include/generated/asm/ipcbuf.h
|   WRAP    arch/arm/include/generated/asm/irq_regs.h
|   WRAP    arch/arm/include/generated/asm/local.h
|   WRAP    arch/arm/include/generated/asm/kdebug.h
|   WRAP    arch/arm/include/generated/asm/mcs_spinlock.h
|   WRAP    arch/arm/include/generated/asm/local64.h
|   WRAP    arch/arm/include/generated/asm/msgbuf.h
|   WRAP    arch/arm/include/generated/asm/parport.h
|   WRAP    arch/arm/include/generated/asm/poll.h
|   WRAP    arch/arm/include/generated/asm/param.h
|   WRAP    arch/arm/include/generated/asm/preempt.h
|   WRAP    arch/arm/include/generated/asm/resource.h
|   WRAP    arch/arm/include/generated/asm/rwsem.h
|   WRAP    arch/arm/include/generated/asm/scatterlist.h
|   WRAP    arch/arm/include/generated/asm/seccomp.h
|   WRAP    arch/arm/include/generated/asm/sections.h
|   WRAP    arch/arm/include/generated/asm/segment.h
|   WRAP    arch/arm/include/generated/asm/sembuf.h
|   WRAP    arch/arm/include/generated/asm/serial.h
|   WRAP    arch/arm/include/generated/asm/shmbuf.h
|   WRAP    arch/arm/include/generated/asm/siginfo.h
|   WRAP    arch/arm/include/generated/asm/simd.h
|   WRAP    arch/arm/include/generated/asm/sizes.h
|   WRAP    arch/arm/include/generated/asm/sockios.h
|   WRAP    arch/arm/include/generated/asm/termbits.h
|   WRAP    arch/arm/include/generated/asm/termios.h
|   WRAP    arch/arm/include/generated/asm/timex.h
|   WRAP    arch/arm/include/generated/asm/trace_clock.h
|   WRAP    arch/arm/include/generated/asm/unaligned.h
|   WRAP    arch/arm/include/generated/asm/socket.h
|   HOSTCC  scripts/kallsyms
|   HOSTCC  scripts/dtc/dtc.o
|   CC      scripts/mod/empty.o
|   HOSTCC  scripts/mod/mk_elfconfig
|   CC      scripts/mod/devicetable-offsets.s
|   HOSTCC  scripts/dtc/flattree.o
| In file included from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/linux/compiler.h:54:0,
|                  from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/uapi/linux/stddef.h:1,
|                  from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/linux/stddef.h:4,
|                  from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/uapi/linux/posix_types.h:4,
|                  from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/uapi/linux/types.h:13,
|                  from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/linux/types.h:5,
|                  from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/linux/mod_devicetable.h:11,
|                  from /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/scripts/mod/devicetable-offsets.c:2:
| /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/include/linux/compiler-gcc.h:121:30: fatal error: linux/compiler-gcc6.h: No such file or directory
|  #include gcc_header(__GNUC__)
|                               ^
| compilation terminated.
| /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/scripts/Makefile.build:153: recipe for target 'scripts/mod/devicetable-offsets.s' failed
| make[4]: *** [scripts/mod/devicetable-offsets.s] Error 1
| /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/scripts/Makefile.build:403: recipe for target 'scripts/mod' failed
| make[3]: *** [scripts/mod] Error 2
| make[3]: *** Waiting for unfinished jobs....
|   HOSTCC  scripts/dtc/fstree.o
|   HOSTCC  scripts/dtc/data.o
|   HOSTCC  scripts/dtc/livetree.o
|   HOSTCC  scripts/dtc/treesource.o
|   HOSTCC  scripts/dtc/srcpos.o
|   HOSTCC  scripts/dtc/checks.o
|   HOSTCC  scripts/dtc/util.o
|   SHIPPED scripts/dtc/dtc-lexer.lex.c
|   SHIPPED scripts/dtc/dtc-parser.tab.h
|   SHIPPED scripts/dtc/dtc-parser.tab.c
|   HOSTCC  scripts/dtc/dtc-lexer.lex.o
|   HOSTCC  scripts/dtc/dtc-parser.tab.o
|   HOSTLD  scripts/dtc/dtc
| /home/rooholah/mcg/poky/build-atmel/tmp/work-shared/sama5d3-xplained/kernel-source/Makefile:555: recipe for target 'scripts' failed
| make[2]: *** [scripts] Error 2
| make[2]: *** Waiting for unfinished jobs....
|   UPD     include/config/kernel.release
| Makefile:146: recipe for target 'sub-make' failed
| make[1]: *** [sub-make] Error 2
| Makefile:24: recipe for target '__sub-make' failed
| make: *** [__sub-make] Error 2
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/rooholah/mcg/poky/build-atmel/tmp/work/sama5d3_xplained-poky-linux-gnueabi/linux-at91/4.1+gitAUTOINC+00ea8f3f67-r0/temp/log.do_compile.13779)
ERROR: Task /home/rooholah/mcg/meta-atmel/recipes-kernel/linux/linux-at91_4.1.bb:do_compile (/home/rooholah/mcg/meta-atmel/recipes-kernel/linux/linux-at91_4.1.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1229 tasks of which 8 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/rooholah/mcg/meta-atmel/recipes-kernel/linux/linux-at91_4.1.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

u-boot bbappend breaks other machines

e.g. MACHINE=om-gta04 will get the at91 SRC_URI and fail to build. The best way to use custom u-boot recipes is to namespace them, e.g. u-boot-at91_2013.07.bb

bitbake cryptoauthlib doesnt found the recipe?

Hi i have cloned the layer and trying to build it using bitbake. But the recipes in dynamic-layers are not being found with bitbake command. How can i add recipes which are in dynamic-layers folder into my image?

atmel-wireless-firmware_git.bb has invalid repo

The Dizzy Branch has an invalid recipe in it.
recipes-kernel/linux/atmel-wireless-firmware_git.bb fails to expand SRCPV with a "Repository not found." error.

We do not use this firmware in our build, but the failure halts the build process.
We can solve the issue by deleting the file, but a proper solution should be found.
(If the repo no longer exists perhaps a frozen zip of the firmware or a forked repo should be selected).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.