• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 101 subscribers
  • Views 118 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TDA4AP-Q1: Certification of MCAL Modules hw_include & Bsw_Stubs

Kevin Peng
Expert 3047 points
Part Number: TDA4AP-Q1

Tool/software:

Hi TI Experts,

Customer is working on TDA4AP SDK9.2.

They found that our MCAL modules hw_include & Bsw_Stubs have not been certificated yet.

May I know does that mean customer needs to get the certification of MCAL modules hw_include & Bsw_Stubs by themselves?

Also, may I know do we have plan to certify MCAL modules hw_include & Bsw_Stubs ?

Thanks,

Kevin

  • +1
    TI__Expert 3047 points

    HI,

    Closing this thread as I got the answer internally below.

    Bsw_Stubs is not an MCAL module. These files are provided as stubs (reference only) in our MCAL as they are used to verify our drivers in a baremetal context. So, these will not be, and are not required to be certified.

    When customers integrate MCALs in AUTOSAR stack, these stubs are replaced with the stack from AUTOSAR Vendor.

    Our MCAL modules themselves only use the header files in hw_include and these are providing only the macro values. Other files are used in MCAL examples. Hw_include is not a separate module, and is not certified as so.

    Thanks,

    Kevin