Hi Jamin, On 2 Dec 2024, at 05:39, Jamin Lin <[email protected]> wrote: > create_its() { > cat << EOF >> ${UBOOT_ITS} > ${USER_FIRMWARE} { > description = ${USER_DESCRIPTION}; > data = /incbin/("${UBOOT_FIT_SSP_IMAGE}"); > type = ${USER_FIRMWARE}; > arch = "${USER_ARCH}"; > os = "${USER_OS}"; > load = <${USER_LOADADDRESS}>; > entry = <${USER_ENTRYPOINT}>; > compression = ${USER_COMPRESS}; > EOF > if [ "${SPL_SIGN_ENABLE}" = "1" ] ; then > cat << EOF >> ${UBOOT_ITS} > signature { > algo = "${UBOOT_FIT_HASH_ALG},${UBOOT_FIT_SIGN_ALG}"; > key-name-hint = "${SPL_SIGN_KEYNAME}"; > }; > EOF > fi > cat << EOF >> ${UBOOT_ITS} > }; > EOF > } > > Then, users set “USER_XXX” variables to create their own ITS file for > u-boot/kernel FIT image generation. > Or can you give me any suggestion about your goal and ITS improvement?
I was actually wondering if it would be sensible to have the user of the class write the .its from scratch. It could support variable expansion to allow the use of variables that are already defined in the machine configuration, but I could see someone wanting more flexibility in your design. Important note: I’ve not used fitimages so I might not be right, this is just an observation from seeing increasing amounts of customisation needed on the existing fit generation. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#208150): https://lists.openembedded.org/g/openembedded-core/message/208150 Mute This Topic: https://lists.openembedded.org/mt/109640118/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
