SAFETI-HERCULES-DIAG-LIB-CSP: Build fails, apparently due to static analysis failure

Part Number: SAFETI-HERCULES-DIAG-LIB-CSP
Other Parts Discussed in Thread: TMS570LC4357

Tool/software:

Hello,

I am trying to execute the Compliance Support Package for the Hercules Diagnostics Library for the TMS570LC4357 but I have encountered a number of problems and the Safety Library TAU reports "Build Failed".

I am using Safety Library TAU (01.00.00) and note that I have set the compiler to ti-cgt-arm_20.2.1.LTS. I have left everything else at the default settings.

The first time that I ran the tests using the Safety Library TAU (01.00.00) the following LDRA dialog box appeared a number of times.

I also got this error for a number of other marcos:

FUNC_PARAM_CHECK_LOG_ENABLED

FUNC_ENTRY_COND_CHECK_ENABLED

FUNC_ENTRY_COND_CHECK_LOG_ENABLED

FUNC_RESULT_LOG_ENABLED

But this dialog box only appeared the first time that the tests were executed. It has not appeared since.

However, the log files there are the following messages: "Macro(s) to be left undefined found in sysppvar.dat" and "Removing 14 macro(s) to be left undefined from sysppvar.dat".

What is the significance of these macros and these messages ?

Then later in the log file the following error is reported.

Static Analysis started
Using penalty file:
C:\Program Files (x86)\LDRA\LDRAunit-TI-Qual_C_CPP_9.4.3\c\cpen.dat
Penalty file modified for Standards Model: TBrun Requires
SOURCE FILE LINE NUMBER = 2274
The TESTBED has failed to successfully identify the header
of the corresponding procedure. The possible reasons are :
1) there are unexpanded macros - check the management or
MAN file to see if all the included files have been opened.
2) there are reuses of proc names which can cause the
TESTBED to become confused. Check the management file
for standards violations to this effect.

TOP OF TREE = 525 PRCDV
FROM TO INFO LENGTH NAME

9 24 1 16SL_SelfTest_SRAM
29 45 2 17SL_SelfTest_Flash
50 66 3 17SL_SelfTest_PBIST
71 94 4 24SL_SelfTest_Status_PBIST
99 130 5 32SL_SelfTest_WaitCompletion_PBIST
135 160 6 26SL_SelfTest_PBIST_StopExec
165 179 7 15SL_SelfTest_STC
184 205 8 22SL_SelfTest_Status_STC
210 226 9 17SL_SelfTest_PSCON
231 254 10 24SL_SelfTest_Status_PSCON
259 275 11 17SL_SelfTest_EFuse
280 303 12 24SL_SelfTest_Status_EFuse
308 322 13 15SL_SelfTest_ADC
327 345 14 19sl_dmaSetCtrlPacket
350 366 15 17sl_dmaSetChEnable
371 394 16 24sl_dmaSetProtectedRegion
399 420 17 22sl_dmaConfigCtrlPacket
425 446 18 22sl_dmaSoftwrTestConfig
451 465 19 15SL_SelfTest_DMA
470 484 20 15SL_SelfTest_VIM
489 506 21 18SL_SelfTest_MibSPI
511 525 22 15SL_SelfTest_CAN


The message below may have been generated as a result
of incorrect LDRA Testbed Analysis Scope settings.
Check that your code compiles and as part of this
process, document the compiler preprocessor settings.
These settings then need to be reflected in the LDRA
Testbed data file SYSPPVAR.DAT. See Macro Expansion in
the User Manual for further details.


0 NUMBER OF ENTRIES
521 NUMBER OF LINES


NO FILES HAVE BEEN OPENED FOR INCLUSION.


The total line number is: 2274
The local line number is: 2274
in the file under test: "c:\ti\hercules\SAFETI~2\24661E~1.0_L\safety_library\source\sl_selftest.c"
*******************************************************************************
****** SYNTACTIC ERROR NO 107 ******
****** STATIC ANALYSIS ******
****** CHECK THAT PROGRAM BEING ANALYSED COMPILES ******
****** THEN CONTACT TESTBED MAINTENANCE EITHER ******
****** LOCALLY, OR ******
****** AT L. D. R. A. LTD. ******
****** TEL. NO. (0151) 649 9300 ******
****** FAX. NO. (0151) 649 9666 ******
****** email: support@ldra.com ******
****** QUOTING THE FOLLOWING ERROR MESSAGE. ******
*******************************************************************************

RETURN STATEMENT WITH NO MATCHING PROC

**********

This error refers to SL_SelfTest_Status_STC().

Can you advise me how I can solve this error?

Thank you.