kernel-dev | useful kernel modules/patches for tracing/debugging | Code Inspection library

I've fixed the build issue. It required adding meta-python2 as I did; but instead of IMAGE_INSTALL_append = " python-dev", TOOLCHAIN_HOST_TASK_append = " nativesdk-python-core" is needed instead in local.conf.

Since scripts/extract-cert.c is compiled for the host environment, I'd rather try appending TOOLCHAIN_HOST_TASK variable with " openssl-dev ".

See this question: TOOLCHAIN_HOST_TASK Vs TOOLCHAIN_TARGET_TASK

I was able to solve it using this comment from Ian Abbott:

Assuming the I2C controller has been opened, and the I2C_SLAVE ioctl command has been used to set Adr, The read syscall with a length of 2 will perform the above I2C read transaction. – Ian Abbott Oct 4 at 13:45

Here is a Logicanalyzer-Trace of the resulting I2C communication:

It turned out the problem wasn't that I was using the wrong GCC version (not possible) or that I was missing any installed packages (I wasn't). Instead, it was a consequence of how the VirtualBox Guest Additions "auto-run" works. Something about the way it runs results in a "fresh" environment without devtoolset-8 properly sourced. As a result, it cannot find the installed GCC 8.3.

The solution was simple: When the auto-run prompt appeared, I dismissed it and did not run auto-run. Instead, I opened a fresh Terminal window and changed directories to /run/media/[username]/VBox_GAs_6.1.26 (YMMV on the exact location of the mounted disk), then ran this command:

Going by the results of search for this issue, it could be temporary. However for the time being you could change disable the GPG check for the repository in /etc/yum.repos.d/pgdg-redhat-all.repo.

The error indicates GPG verification issue for [pgdg-common] repo, but this could be for other repos in the pgdg-redhat-all.repo file. This is usually enabled with gpgcheck=1.

Changing this to gpgcheck=0 for all occurrences using something like Chef::Util::FileEdit should work in the meantime.

Here is what I found after analyzing Toradex's git projects that can inspire you for a solution:

They have a custom class that handles their device tree files and device tree overlays, here.

The class inherits devicetree that is an official poky class here.

The devicetree class tests if a device tree is an overlay or normal and then it compiles all of them.

So, you can basically use devicetree class in a custom recipe to compile device tree overlays and deploy them manually into your rootfs.

Toradex also has a simple recipe like that here. They have a git project that holds all of their device tree overlays.

That being said, I think Toradex doesn't use the custom recipe, rather they use the custom toradex-devicetree class which inherits from devicetree, compiles all device tree overlays from their device tree overlays git project and then deploy them all into the rootfs.

In that custom class, they append to do_deploy of devicetree class to install the .dtbo files and add them to overlays.txt file under the boot partition.

So finally, you can create a bbappend file for you kernel recipe if you don't have one, and try to follow these steps:

1. Inherit from devicetree
2. Add your dts files that are overlays to SRC_URI via local files or URL
3. Add the path for your overlays to DT_FILES_PATH of the devicetree class
4. In the kernel recipe, append to do_deploy to add them to rootfs.

Now, here is my advice to achieve this step by step:

1. Create a custom recipe that uses devicetree class with dts overlay example file
2. Check if it compiles it correctly
3. If you understand that, you can then apply the 4 steps above.

Missing the module.lds file in the latest kernel. Apply the following source code as a patch in the kernel and build the image.

So, the way I do it is to use Quilt, follow the steps there then good to go: https://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#using-a-quilt-workflow

I don't need to know the SHA (though I still don't know why others in my organization end up writing SHAs in the patch files and how did they know the SHAs).

The fftw recipe is set up to create a few different packages (RPM) like libfftw, libfftwl, libfftwf, fftw-wisdom, fftwl-wisdom, fftwf-wisdom, and fftw-wisdom-to-conf. You probably want to add one or more of those. It seems there is no actual fftw package.

It is important to remember that IMAGE_INSTALL and RDEPEND lists items from the package namespace, while DEPENDS lists items from the recipe namespace.

If you are unsure about which package you want to install you can inspect the packages-split folder for fftw in tmp/work to see which files are included in which package.