Hi, all!
So, for development I had been using Torizon 4.0 but as our release gets closer, I had to test Torizon 5.0 out. Long story short, my workflow is not working anymore.
In order to build the 4.0 image, I followed the Build Torizoncore with Yocto article, and after running bitbake torizon-core-docker
I added another extra layer for a kernel driver I need. So, I went to the layers directory, created a new directory with the needed files (layer is found at: github.com/santxo/meta-silead). After adding the layer, I added the layer to the bblayers.conf file in the BUILD directory by adding:
$ {OEROOT}/layers/meta-silead \
After adding the layer to the conf file, I ran bitbake sld-mod
.
Finally, to install the module I added IMAGE_INSTALL_append=sld-mod
to the local.conf file to run bitbake torizon-core-docker
once again.
After the whole process, followed by blacklisting the silead driver by adding a /etc/modprobe.d/blacklist.conf
file , and creating another one to enable the driver at boot in /etc/modules-load.d/gslx680.conf
I was able to use the driver as intended. However, if I use the same workflow for Torizon 5.0, I am not getting the same result.
Do I have to use the bitbake add-layer
instruction in Torizon 5.0 to create the layer structure? Is it related to the git commit requirement? I am pretty sure I did that but still did not get the driver to work.
Thanks in advance!
Jaime