I think there still are signature differences. perhaps try to add incremntally on top of minimal sdk and see where it breaks.

#yocto #sdk

I corrected for the sig warnings, but still have an issue with the extended SDK installing correctly (though I think I am close…) Note: The only issue now appears to be around the “…/poky/meta” layer…

#yocto #sdk

it excludes the variables from checksums see https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#checksums

#yocto #sdk

What is the difference between using “SIGGEN_UNLOCKED_RECIPES +=” and “BB_HASHBASE_WHITELIST_append =” ?

#yocto #sdk

right, the change seems to be happening in task checksums and that happens if some of bitbake variables change when SDK is built built and when it is being installed ( when it will run parse again ) p

#yocto #sdk

Nope, just validated... I build the my kernel image clean and the eSDK image right after, cache should be good, no ? Not sure how to go about resolving... it occurs on the back end of the eSDK install

#yocto #sdk

I am seeing similar issues on line for my eSDK install issue, but no resolutions… Can someone advise on best course of action to debug this ? 11:10 smonsees@yix490016 /disk0/scratch/smonsees/yocto/wor

#yocto #sdk

if you have AUTOREVs e.g. can be problematic, and also using TIME/DATE in recipes which can interfere

#yocto #sdk

Is there a list of certain classes that might interfere with the ability of the eSDK to lock down the configuratiuon ? Thanks, Steve

#yocto #sdk

I still appear to be having an issue with the SXT SDK install… Building for zeus/x86_64 Intel based platform… I build my kernel image clean, fully functional… Standard SDK builds clean and appears fun

#yocto #sdk

Thanks again, these utilities make it much easier to understand and correct the issues...

#yocto #sdk

Thanks, will go through it...

#yocto #sdk

https://wiki.yoctoproject.org/wiki/TipsAndTricks/Understanding_what_changed_(diffsigs_etc) On Tue, Feb 23, 2021 at 10:03 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems

#yocto #sdk

I am trying to understand the warnings/error as seen below… Building for zeus… Built kernel image clean updated my SSTATE_MIRRORS directory with the state_cache generated. Rebuilt my image clean again

#yocto #sdk

Hi, We have a functioning image built for our device/platform based on Ti Processor SDK 04.03.00.05; at this point I'm trying to build an SDK for the image that I can distribute to other members of ou

#toolchain #sdk #qt5

That means it’s having issues with checksums is there any AUTOREV being used ? I would suggest to build without your changes and see if you can get an eSDK

#yocto #zeus #sdk

I configured SDK for: SDK_EXT_TYPE = "minimal" SDK_INCLUDE_TOOLCHAIN = "1" SDK_INCLUDE_PKGDATA = "0" And I still see "Error: Failed to generate filtered task list for extensible SDK..." In my latest l

#yocto #zeus #sdk

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

Hi, My comments are in-line Which version is this? Can it be reproduced? If so you might want to add it to https://bugzilla.yoctoproject.org Regards, Robert > > > >

#sdk

Hello, I build the SDK with bitbake core-image-base -c populate_sdk and it works just fine. But trying to build the eSDK with bitbake core-image-base -c populate_sdk_ext results in this error: ERROR:

#sdk