Hello Alessio, Good question. I know Xilinx has put effort to support their MCUs with Yocto. However, define what you mean by SDK? Which libraries or programming languages are you thinking of beyond t

Hello Steven, No, that remark is completely wrong and is mixing up things. "RTLinux" has nothing to do with the mainstream Linux kernel (except that RTLinux can run the Linux kernel underneath) Forget

Hello Robert, Alexander, No. There is a sweet middle ground called FPGAs. You buy a board, with an IC on it, that is expensive as hell, empty like air, but fully re-configurable with almost any RISC-V

Hello Steve, Depends, no mainline kernel? Vendor kernel? Can you share the machine name? Might be supported already in a layer with -rt. Regards, Leon

And adding to that, besides the Yocto maintained kernel, meta-intel has it's own kernel GIT repo/branch for the kernel and -rt kernel maintained by Intel. (There might be some overlap in the maintaine

Hello Steve, I have been running the PREEMPT_RT for Intel platforms for a few releases, I remember it fetched sources from a GIT branch for -rt (PREEMPT_RT). So it does not need to apply separate patc

Hello Steve, Is the approach where you remove the recipes from the image an option? Is there a reason why you want to build the recipes that you do not want to appear in your image? Regards, Leon.

Hello, What is your output from the ZC702 (USB) serial console? I had similar issue on ZCU102 and debugged my issue: "the U-Boot not showing anything I have debugged to be an issue where DEVICE_TREE d

#gatesgarth #linux #yocto

Hello all, In some other build systems the generated SDK can be used to also generate an image. Thus the SDK allows development against the target sysroot using the prebuilt host and target tools, as

Hello Steven, Yocto does support switching kernels and configurations, so yes Yocto does "support" it. However, providing a well-tested PREEMPT_RT kernel might be more an architectural meta layer topi

Hello Robert, all, $grep -re '[A-Z_]\+_[a-z0-9]\+_append' poky/meta* poky/meta/recipes-support/gmp/gmp_6.2.0.bb:EXTRA_OECONF_mipsarchr6_append = " --disable-assembly" poky/meta/recipes-core/images/bui

Marek, This might indeed indicate a configuration mismatch. Lots of stuff comes up on Google that you might want to check. One is a change in systemd that affects this. Sorry I don't have a link ready

Hi Kent, Most of these providers provide an IMAP interface as well, such as gmail. Also, in gmail you can tag messages to move into a separate folder for easy delete. For devs and users, the patches a

Hello, What's obvious? There are no package names there, only recipe names that I am aware of. So for the non-obvious packages it still is a bit of guesswork, or the responses in this thread. Regards,

#yocto

Hello Alexander, I have two ideas that might get you closer. 1) First, I noticed that using TOOLCHAIN_HOST_TASK += "xxx" is broken on Yocto dunfell for me (non-extensible SDK). The issue is that even

#sdk

Hello Dave, I copied that error report into Google. Maybe you are hitting a similar case to this? https://www.yoctoproject.org/pipermail/meta-xilinx/2018-January/003638.html Regards, Leon,

Hello Damien, I have this in my local.conf: IMAGE_FSTYPES = "tar ext4" INITRAMFS_FSTYPES = "cpio.xz" It does depend a bit on your image recipes and classes if this works for you. Regards, Leon.

Hello Henrik, As far as I known: - The -dev packages do not end up in target rootfs, unless you specify them in your target image. - The -dev packages end up in the standard SDK target sysroot if you

#yocto #sdk

Hello Aashik, I recognize the issue that CTRL-C does not pass from the console, but only with *very* minimal configurations. How does your local.conf look like, or better yet how can we reproduce your

Hi Aashik, Zoran, Aashik, how are you sending the signal? Using CTRL-C or using the "kill" command? That reads to use sigaction() instead of signal() I would assume. Zoran, are you suggesting that pro