Cross-Linking in the TASKING VX-toolset for TriCore

Cross-Link­ing in the TASKING VX-toolset for Tri­Core How can you move to a newer TASKING tool­chain release with­out rebuild­ing every val­i­dat­ed soft­ware com­po­nent? In this Tech Tues­day, Vivek Jolly from the TASKING Appli­ca­tion Engi­neer­ing team explains cross-link­ing in the TASKING VX-toolset for Tri­Core. The ses­sion cov­ers how pre-com­piled objects from sup­port­ed older releas­es can be linked into an appli­ca­tion built with VX-toolset ver­sion 6.4r1, pro­vid­ed the required com­pat­i­bil­i­ty con­di­tions are met. You will learn why cross-link­ing mat­ters for long-life­cy­cle auto­mo­tive and safe­ty-crit­i­cal projects, how it can reduce migra­tion effort and val­i­da­tion risk, and what checks are need­ed before using lega­cy bina­ries with a newer link­er and libraries.

What you will learn:

• What cross-link­ing is and when to use it
• How lega­cy object files and new appli­ca­tion code can be linked into one exe­cutable
• Why the newer VX-toolset link­er and libraries must be used
• Which com­pil­er options must match across the whole appli­ca­tion
• Why EABI con­sis­ten­cy mat­ters more than full EABI com­pli­ance when cross-link­ing
• How glob­al type check­ing can catch some mis­match­es
• Which com­pat­i­bil­i­ty issues the tools can­not detect auto­mat­i­cal­ly
• Why release inven­to­ry is the first step before plan­ning migra­tion