varigit / meta-variscite-imx Goto Github PK

The only reference I found is this branch morty-imx-4.9.51-var01 I tried the following bblayers set-up:

BBLAYERS = " \
  ${BSPDIR}/sources/poky/meta \
  ${BSPDIR}/sources/poky/meta-poky \
  \
  ${BSPDIR}/sources/meta-openembedded/meta-oe \
  ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
  ${BSPDIR}/sources/meta-openembedded/meta-python \
  \
  ${BSPDIR}/sources/meta-swupdate \
  \
  ${BSPDIR}/sources/meta-freescale \
  ${BSPDIR}/sources/meta-freescale-distro \
  \
  ${BSPDIR}/sources/meta-qt5 \
  \
  ${BSPDIR}/sources/meta-variscite-fslc \
  ${BSPDIR}/sources/meta-variscite-imx \
  \
  ${BSPDIR}/sources/meta-walnut \
  \
"

So all of the branches are based on morty the meta-walnut is my branch which more or less adds a image and some bbappends. It looks like the morty branch of meta-freescale is missing some recipes which you are using .bbappends for. So in a naive approach I put those in my meta-walnut which solved the missing base recipe issue. Nevertheless I do feel like I am doing something unintended. I am posting here because I can not find any category for mx8m boards on your forum.

This issue is relative to the branch zeus-imx-5.4.24-var01.

In the var-image-swupdate.bb recipe, there is a reference to the BSPDIR variable:

This is quite problematic when the layers are arranged in a different structure (which is our case): suddenly the path is not valid anymore and even if the recipe is not used an error prevents bitbake from compiling.

The issue should be easily resolved by replacing the line with:

require recipes-fsl/images/fsl-image-gui.bb 

Which works the same way except that it does not use an absolute path, so it works wherever the layer is.

Thank you,
Giulio

Are you planning to upgrade linux kernel to 4.14.98 branch?

Hi,

Do you plan to update this layer to thud or warrior in the future? Could you please provide an estimated date for this?

Regards

Missing WIFI_VSEL_GPIO In connectivity-recipes for imx8mq-var-dart module(zeus 5.4.x), which prevents wifi from starting. After manually adding it to the script everything worked as expected.

Hey,

i get the this failure when following:
http://variwiki.com/index.php?title=VAR-SOM-MX6_Yocto_Fido_R2#Build_your_image

ERROR: Function failed: do_configure (log file is located at /home/volle/var-som-mx6-yocto-fido/build_fb/tmp/work/var_som_mx6-poky-linux-gnueabi/ti-compat-wireless-wl18xx/R8.5-R1/temp/log.do_configure.21832)
ERROR: Logfile of failure stored in: /home/volle/var-som-mx6-yocto-fido/build_fb/tmp/work/var_som_mx6-poky-linux-gnueabi/ti-compat-wireless-wl18xx/R8.5-R1/temp/log.do_configure.21832
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| Copy original source files ...
| Apply patches ...
| Failed to apply changes from backport-adjustments/flow_dissector.patch
| > patching file compat/net-core-flow_dissector.c
| > Hunk #1 FAILED at 177.
| > 1 out of 1 hunk FAILED -- saving rejects to file compat/net-core-flow_dissector.c.rej
| Failed to apply changes from collateral-evolutions/network/85-hid_ll_driver/net_bluetooth_hidp_core.patch
| > patching file net/bluetooth/hidp/core.c
| > Hunk #1 succeeded at 268 with fuzz 1 (offset 45 lines).
| > Hunk #2 succeeded at 353 with fuzz 2 (offset 45 lines).
| > Hunk #3 FAILED at 396.
| > Hunk #4 succeeded at 474 with fuzz 2 (offset 65 lines).
| > Hunk #5 FAILED at 739.
| > 2 out of 5 hunks FAILED -- saving rejects to file net/bluetooth/hidp/core.c.rej
| Failed to apply changes from collateral-evolutions/network/86-qdisc_tx_busylock/ieee802154.patch
| > patching file net/ieee802154/6lowpan.c
| > Hunk #1 FAILED at 530.
| > Hunk #2 FAILED at 545.
| > 2 out of 2 hunks FAILED -- saving rejects to file net/ieee802154/6lowpan.c.rej
| Modify Kconfig tree ...
| Rewrite Makefiles and Kconfig files ...
| Done!
| /--------------
| | Your kernel headers are incomplete/not installed.
| | Please install kernel headers, including a .config
| | file or use the KLIB/KLIB_BUILD make variables to
| | set the kernel to build against, e.g.
| |   make KLIB=/lib/modules/3.1.7/
| | to compile/install for the installed kernel 3.1.7
| | (that isn't currently running.)
| \--
| make: *** [defconfig-wl18xx] Error 1
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /home/volle/var-som-mx6-yocto-fido/build_fb/tmp/work/var_som_mx6-poky-linux-gnueabi/ti-compat-wireless-wl18xx/R8.5-R1/temp/log.do_configure.21832)

Summary: 1 task failed:
  /home/volle/var-som-mx6-yocto-fido/sources/meta-variscite-mx6/recipes-connectivity/ti-compat-wireless/ti-compat-wireless-wl18xx_r8.a8.08.bb, do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

running on

uname -a
Linux volle-VirtualBox 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Do you have any idea how to fix this?

Concerns following step 5.3.1 of the Extended SD card creation guide, when the user is building only for fsl-image-qt5 and not fsl-image-gui

Context

• Platform: VAR-SOM-6UL
• Branch: thud-fslc-4.14.78-mx6ul-v1.1
• Image: fsl-image-qt5

Error

The script var-create-yocto-sdcard.sh hardcodes variable: YOCTO_DEFAULT_IMAGE to fsl-image-gui, making it fail later on (after echo "Installing Yocto Root File System:) since it cannot find the build image .tar.gz expected there. This happens when the user has built for fsl-image-qt5. No warning or output is provided to indicate that the default image name may not be what the user intended.

Suggested fix

I suggest perhaps making the image to be used a required input parameter for the script

Hi,

I'm having trouble getting the RPMsg TTY and RPMsg Ping Pong demo to work on the latest commit of sumo-imx-4.14.78-var01. It was still working on this commit . Can someone verify this isn't just me?

Tested on the DART-MX8M dev board

Thank you,
Jonathan

Hi, looking at the zeus-imx-5.4.24-var01 branch, it seems that it uses kernel branch imx_5.4.24_2.1.0_var01 which does not have the device tree for the imx8mm-var-dart. Can you update that kernel branch with the correct dtbs for the imx8mm-var-dart machine?

On a related note, I see there is an even newer kernel, imx_5.4.47_2.2.0_var01. Can this be used for the imx8mm-var-dart? This one is also missing the device tree for this hardware.

Thanks

It would be really great to have an option to use a user-pecified image instead of fsl-image-gui.

Hi,
I see this layer received updates (in the sumo branch) and also contains the BSP for the imx8m machines. Is there any plan on moving the imx8m to the newer repository (https://github.com/varigit/meta-variscite-fslc) ?
Why is this separation for?

Hi,

I'm currently working on imx6q and tried out the new 4.1.15 branch.
I noticed after commit f05e15f, yocto can't build an image anymore.
I get the following error:

ERROR: Fetcher failure: Unable to find revision 5aad9684dde014d47c8c940684ad4b849009395c in branch imx-rel_imx_4.1.15_1.1.0_ga-VAR01-beta even from upstream
ERROR: Function failed: Fetcher failure for URL: 'git://github.com/varigit/linux-2.6-imx.git;protocol=git;branch=imx-rel_imx_4.1.15_1.1.0_ga-VAR01-beta'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /yocto/build/tmp/work/var_som_mx6-poky-linux-gnueabi/linux-variscite/4.1.15-r0/temp/log.do_fetch.13640
ERROR: Task 45 (/yocto/sources/meta-variscite-mx6/recipes-kernel/linux/linux-variscite_4.1.15.bb, do_fetch) failed with exit code '1'

I think a commit is missing in linux-2.6-imx repository that actually includes the bluetooth fix.
Reverting the last commit fixes it now for me.
Could somebody look into this? Thanks in advance 😄.

Kind regards,

Luc

line 22: readonly YOCTO_BUILD=${YOCTO_ROOT}/build_xwayland
there are options, at least build_wayland

Hi, are you planning to release support for Yocto Dunfell?

Thank you

Hi,

I've been trying to get my own custom Linux running on the var-som-mx6. (tutorial @ http://variwiki.com/index.php?title=VAR-SOM-MX6_Yocto_Fido_R2_Build_Yocto_release)
However I have been running into some problems with ti-compat-wireless-wl18xx recipe:

• Initially I tried building core-image-minimal, since my build has to be as minimal as possible, I don't need all the qt stuff, but the build kept failing with the following error: https://gist.github.com/Primordus/7b6fb5f71db80af8d8e7966920775194
• I then tried to see if fsl-image-qt5-minimal would work as expected and build succeeded (gave around 60 warnings though). Isn't the same wifi driver also included in this image??
• After building the qt5-minimal image, I tried core-image-minimal which now also succeeded (probably since wifi driver was now already built)
• Then tried cleaning tmp and sstate-cache, ran core-image-minimal again, failed a few times (with a similar error compared to earlier), kept trying and it succeeded..

Am I doing something wrong that build is only failing sometimes?
(Also noticed another similar issue that was resolved on this repository.., maybe related?)
I can give extra logs if you need, I really would like the build to succeed every time :)

Thanks in advance!