Other Parts Discussed in Thread: SYSBIOS
We are in the process of making a solution using the AWR1642 where goal is to make an AutoSAR compliant firmware (will be using the mmwave sdk and associated drivers and RTOS of TI, for the MCAL probably will be talking to TI for support). We are outsourcing the autoSAR glue software from a third party vendor. Have seen the thread about the same topic https://e2e.ti.com/support/sensors/f/1023/t/673386?tisearch=e2e-sitesearch&keymatch=awr1642%2520%2520autosar but answers to few questions were still unclear. Our generic architecture (attached below is similar to the one provided in the thread above).
1. Are the firware codes (for eg. SRR demo) for libraries, DSS, MSS etc. AutoSAR compliant. Apart from the MCAL or AUTOSAR RTE does it require to rewrite the codes in AutoSAR compliant form?
2. How much of the codes (library and support packages for drivers and RTOS) is autoSAR compliant and does not need to be rewritten?