Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Based on the context provided, when working with Torizon OS custom builds, it is recommended to align the tcb.packageName with the OSTree branch naming convention. This means that the tcb.packageName should reflect changes in the Torizon OS major version, SoM, carrier board, and image name. This alignment ensures consistency and clarity, making it easier to manage and identify your builds.
The tcb.packageName is indeed similar to the OSTree branch, and it should ideally match the OSTree branch. If you upgrade your OSTree branch, for example, to Torizon OS 7, you should also update the tcb.packageName to reflect this change. This helps maintain a clear relationship between the package and its corresponding OSTree branch.
In summary, you should not use a “fixed” name for tcb.packageName. Instead, it should dynamically change to match the OSTree branch, ensuring that your package name remains relevant and organized as you update your builds.
Please, also check if these links can help you solve your problem:
Help to integrate a custom kernel into a Torizon Core Image.