This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Compiler Qualification Kit

Other Parts Discussed in Thread: TMS320F28388D

Hello.

I will use TMS320F28388D for make Functional Safety Module.

And, I will use Compiler version 21.6.0.LTS.

I receive you about 'Validation Results' report include in Compiler Qualification Kit.

I have some question about the option combinations in the report.

First, I use 'fpu64' and 'cla2'. but, there is no such combination in the report. How can I verify it?

Second, F2838xD series' CLA Types is '2' in "3. Identifying Device-Specific CLA Features — C2000Tm CLA Software Guide" .

              F2838xD must be type 2? or can i do select others?

Third, there is no option about 'vcu_support' in the report. How can I verify it?

Thanks.

  • F2838xD must be type 2?

    Yes

    or can i do select others?

    There is no reason to do that.  I hate to admit that I'm not certain about what happens if you build with --cla_support=cla1 or --cla_support=cla0 instead.  I think everything will still work.  But, the compiler will not use features of the CLA that are available on your device.

    Regarding your questions on the Compiler Qualification Kit, I'm getting with an expert from the compiler development team.

    Thanks and regards,

    -George

  • For below QKIT questions:

         First, I use 'fpu64' and 'cla2'. but, there is no such combination in the report. How can I verify it?

         Third, there is no option about 'vcu_support' in the report. How can I verify it?

    For fpu64/cla2, the options are independent. fpu64 applies to the C28 core, and cla2 applies to the CLA cores.  There are multiple entries for both fpu64 and both cla2. No need to combine them.

    For vcu_support, we test this with unit tests so there will not be a corresponding row with an optionset including this.  It is however tested by our unit tests which is where we handle most compiler features that are extensions of the C standard.

    What safety compliance level are you applying the QKIT for?  Are you planning on performing the coverage check? 
    Doing so will ensure there are no gaps in coverage when comparing the portions of the compiler that were used while building your application versus the portions of compiler that were used while running release validations.

    Regards,
    Greg