Hello, I am in the process of setting up a new build container for TI targets. This section here http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment#Cross-compile_toolchain Seems to

But does somebody has a running config for the described configuration?

Thanks for this. I will plan for migration of meta-processor-sdk using this Regards, Nikhil D

Michael, Sure, you can list extra config fragments via KERNEL_CONFIG_FRAGMENTS variable to pass to linux-ti-staging. As of working SGX - as Nishanth mentioned, 5.10 might not have everything

Hello Denys, yes I have my own defconfig derived from the original kernel settings.But I will do what you mention and use a .config for the settings I change. Maybe that works better. I let you

From: Denys Dmytriyenko <denys@...> Upcoming "honister" release changes the override syntax to improve usability, speed and memory footprint. Update recipes with the new syntax and set

Nikhil, There's a generic script in OE-Core under scripts/contrib/convert-overrides.py that does a bunch of regexps on a

That is because there is a sgx node in device tree, I dont think it has been introduced so far. I remember seeing this before.. I remember there was a bug of SGX support with the driver, essentially

Denys, To do all the override changes without any human errors, is there a tool/script that you used? OR was it done manually? Please share how this can be done for other layers as

Michael, And by custom defconfig, do you mean you pass your own complete defconfig? Any reason not to use supplied defconfig and adjust what you need with config fragments? -- Regards, Denys

The kernel 5.10 and ti-sgx-ddk-km build know and I can create an image. Now I still have two problems and need some advice what I'm doing wrong or how to fix these issues. 1.) The sgx section of my

Hello Denys, I tried with 5.4 and 5.10 both run in the same problem when not set CONFIG_DRM_LEGACY=y in custom defconfig. When open the original source with bitbake -c menuconfig virtual/kernel the

Ok, I have a fix for this - will send tomorrow...

From: Denys Dmytriyenko <denys@...> Upcoming "honister" release changes the override syntax to improve usability, speed and memory footprint. Update recipes with the new syntax and set

Michael, Which kernel are you building? As linux-ti-staging kernel in meta-ti alredy enables DRM_LEGACY by default: $ grep DRM_LEGACY

I found the solution by myself. the Kernel needs to be configured and build with CONFIG_DRM_LEGACY option then ti-sgx-ddk-km will be build.

OK, I can reproduce this with just oe-core, meta-arm and meta-arm-toolchain, using an external toolchain. This is a failure of the external toolchain. I suggest you raise this problem with

Tom, I am running into build issue after integrating this to dunfell-next.(See attachment) Let me know if I am missing anything. Thanks Yogesh

Hello, I'm trying to build Yocto dunfell with meta-ti and ti-sgx-ddk-km. Without ti-sgx-ddk-km it works for me. But when add ti-sgx-ddk-km to the project it fails. That is the configuration I add to

Praneeth, The new override syntax is mandatory for master - it won't accept the old one. But if you update bitbake to the latest from 1.46/dunfell branch, it would be able to parse new syntax as