TMS320F28377D: verification on C2000 drivers

Muniniteesh

Pls note that these drivers are developed using base quality and not for DO-178C certification.  There  is no kit/docs that can be provided for DO-178C certification.

Best Regards

Siddharth

there was a customer comment as shown below 

we will validate our software using RTRT tool which is a qualified one can you pls suggest your answer for above question 

regards

J.Muniniteesh

I am not sure regarding the RTRT tool .  If you are using this tool , then you should analyze the documents that can be generated using this tool (after validation of the software) and see if they can help in certification.

Best Regards

Siddharth

am really sorry by mistake i have posted wrong question, the actual question asked by them is as shown below

Hi,

Which docs are you expecting to be provided ? 

As mentioned earlierm the drivers are developed using base quality  and not for DO-178C certification.  

Best Regards

Siddharth

we are not expecting any documents just want your suggestion for the question 

thanks

J.Muniniteesh

Hi, 

TI has tested this software using base quality process , functional testing has been done on the requirements and bugs fixed in a partiuclar version of C2000Ware. 

Best Regards

Siddharth

Is there any proof that TI has tested this software if it is there please share with us 

thanks for the update now we linking driver APIs through dynamically is there any way to link statically so our objective is to check the code coverage till the c2000 API level ......

at present RTRT tool can not  able to cover the API in c2000 level like SPI_setTxFifoTransmitDelay,HWREGH(base + SPI_O_FFCT) = delay;.....etc

regards

J.Muniniteesh

Hi, 

These functions are inline functions  and the compiler copies the code from the function definition directly into the code instead   of calling the function.

You can check how RTRT handles such functions. 

Also, are you adding driverlib.lib or the driverlib source files (.c and .h files) in your project?

Best Regards

Siddharth

hi, am linking by including directory i.e..C:\ti\c2000\C2000Ware_4_02_00_00\driverlib\f2837xd\driverlib in my code (dynamic linking)

and compiler settings are as shown below

through RTRT tools can not able to go to .c files not even .h files so in coverage report it is not showing we are covering TI driver APIs 

is there a setting for static linking to driverlib or do we need to add .c and .h files to my code pls give clarity 

regards

J.Muniniteesh

Hi,

Can you share the project explorer view where it shows all the files added to the project ,similar to the below

You can either add the driverlib.lib (which is an archive of all the .c and .h files) or add the driverlib folder which has .c and .h files to the project.

In this case, the drivelrib.lib is added  and the driverib folder is excluded. 

Best Regards

Siddharth

hi sir, please find screenshot of my project explorer below

in Inc and SOURCE folder i implemented our own code so as shown above our RTRT tool can not able to go inside TI drvier API definition  of all functions 

please suggest your response for this issue 

regards

J.Muniniteesh

Hi,

Pls try using the .c and .h files instead of the driverlib.lib file.  Since driverlib.lib is an archive , the tool may not have been able to access them.

Best Regards

Siddharth