TriCore Inspector: Disable issue detection for issues resolved in a patch level

24-Jan-2025

This article is applicable only for TriCore VX-toolset Patch levels above v6.2r2 patch 2 and v6.3r1 patch 2.


The TriCore v6.2r2 Inspector v1.0r7 is based on the TASKING VX-toolset for TriCore v6.2r2 Patch 2,  and the TriCore v6.3r1 Inspector v1.0r6 is based on the TASKING VX-toolset for TriCore v6.3r1 Patch 2.

The Inspector operates identically to the VX-toolset (except for issue detection) down to the linker. Patch levels above patch 2 include fixes for known issues, with a list of these fixed issues provided in the release notes for the respective patch.

If a higher patch level is used to build a user application, there is no need to have the Inspector tool emit diagnostic messages related to issue detection for issues that have been resolved in the applied patch.

To adapt issue detection to the patch level used, the Inspector tool executables can be invoked by adding an --ignore entry to the invocation.

The ignore entries for different patch levels are included in the zip files named TriCore_Inspector_v6.3r1_v1.0r6_ignore_files.zip and TriCore_Inspector_v6.2r2_v1.0r7_ignore_files.zip.


Examples

Example 1: Using TriCore_Inspector_v6.2r2_v1.0r7_ignore_files.zip

Here, TriCore v6.2r2 Patch 5 is used to build an application. The application code can be verified using the Inspector Tool v1.0r7 for TriCore v6.2r2. The invocation of individual Inspector Tool toolsets can be extended by adding an option file that includes the ignore entries to disable the detection of fixed issues in Patch 5. 

insp_ctc  -f TC_v6.2r2p5_ignore.txt <C compiler option list used to build the TriCore project> filename.c
insp_astc -f TC_v6.2r2p5_ignore.txt <assembler option list used to build the TriCore project> filename.src
insp_ltc -f TC_v6.2r2p5_ignore.txt <linker option list used to build the TriCore project> <object file and library list>

 The -f TC_v6.2r2p5_ignore.txt option can be used in combination with the control program invocation (insp_cctc) as well.


Example 2: Using TriCore_Inspector_v6.3r1_v1.0r6_ignore_files.zip

Here, TriCore v6.3r1 Patch 9 is used to build an application. The application code can be verified using the Inspector Tool v1.0r6 for TriCore v6.3r1. The invocation of individual Inspector Tool toolsets can be extended by adding an option file that includes the ignore entries to disable the detection of fixed issues in Patch 9.

insp_ctc  -f TC_v6.3r1p9_ignore.txt <C compiler option list used to build the TriCore project> filename.c
insp_astc -f TC_v6.3r1p9_ignore.txt <assembler option list used to build the TriCore project> filename.src
insp_ltc -f TC_v6.3r1p9_ignore.txt <linker option list used to build the TriCore project> <object file and library list>

The -f TC_v6.3r1p9_ignore.txt option may be used in combination with the control program invocation (insp_cctc) as well.

More resources


Was this answer helpful?
Same category topics
No topics found
Similar topics