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.

MMWAVE-SDK: ISO26262 enabled code

Part Number: MMWAVE-SDK
Other Parts Discussed in Thread: MATHLIB

Hello mmWave expert,

Regarding MMWave SDK,

This video ( https://training.ti.com/jp/introduction-mmwave-sdk ) shows

Radar SS Firmware、MSS Bootloader、mmWaveLink is enabled with ISO26262.

Here is 2 questions.

1) What is the meaning of "enabled"? The same meaning with the "compiant"?

2) This video was made in 2017, so our customer wants to confirm with  the newer version.

That means above 3 SW components are enabled on MMWAVE-SDK 02_01_00_04 and MMWAVE-SDK  03_03_00_03 also?

Regards, Fujinaka

  • Hello Fujinaka-san,

    A1: We use "enabled" as we do not perform any formal certification on these code. But the SW is developed as per the ISO26262 process . The customer can use the quality artifacts that are available as part of the SW (Compliance Support Package aka CSP) and  use this during their certification process at system level SW.

    As TI does not do any certification for this SW we do not want to call it compliant.

    A2: There are no new version of the SDK training . Please note none of the components of the MMWAVE-SDK are ISO26262 enabled. Only the MSS bootloader and the Radar SS Firmware are ISO26262 enabled.

    -Raghu

  • Hello Raghu,

    Thanks for your reply. OK for your ansewrs, then I received related questions as follows.

    Can you please follw up for these questions?

    1. That document says, the blue block is “Production Quality TI code”.

    Does this mean the customer can use these code for their final products?

    2. Does these code compliant with MISRA?

    3. Can TI provide the information what kind of test has been done before the release, ie, unit test, integration test, qualification test etc?

    4. Did TI execute the “code coverage analysis”? If yes, how TI set the target ?

    5. Will TI execute the issue analysis or modification and patch release in case the issue happening?

    6. If the customer will not modify the “mmWave API “ block of the SW, will this module being treated as the "TI code" colored with blue?

    Regards, A.Fujinaka

  • Fujinaka-san,

    Please see the reply below.

    A1: This is just reference code from TI. Customers can use this code as a starting point and make required modifications to make it production quality.

    A2: MMWAVE-SDK code are not MISRA compliant. The boot code /firmware/MCAL are MISRA compliant.

    A3: Compliance Support package can be provided to some of the modules that follow the ISO26262 development process. Can be shared with specific NDA.

    A4: We use the LDRA to perform the code coverage analysis. Most of the test setups are automated to get the analysis report.

    A5: This is done case by case based on the severity of the issues or if there are no workarounds.

    A6: As mentioned earlier, all the code is reference code . 

    Thanks,

    Raghu

  • Hello Raghu,

    I received an additional questions. 

    1) xWR16xx demo application uses C64Px DSPLIB and C674x MATHLIB.

    As which are these SW block treated , TI foundation code, Customer Code or ISO26262 enabled code?

    2) We understand the code coverage analysis is done by LDRA.

    Does TI target 100% for statement coverage、branch coverage、MC/DC coverage?

    https://ldra.com/wp-content/uploads/2017/05/79b8f66286357f26f907c1e6ac3c1758-LDRA-Newsletter-Iss-19.pdf

    Can you please support?

    Regards, A.Fujinaka

  • Fujinaka-san,

    A1: The DSPLIB , MATHLIB are all TI foundation code for reference. They are not ISO26262 enabled code.

    A2: Some of the modules are 100% and there are some waivers. 

    -Raghu