TMS320F280039C-Q1: Object Code Coverage with PC Trace

Neal Malackowski

Tool/software:

Hello,

We are investigating the use of the C2000 family of MCUs (namely the F280039C to start) and are in the process of determining whether or not we'd be able to certify the software against DO-178C. Part of the certification process is to validate the object code by utilizing trace-base code coverage. Historically, we have achieved this by using Lauterbach TRACE32 and interfacing with a real-time trace module that is routed to the I/O of our target. The C2000s obviously do not support an ETM that is routed to the I/O, however the TRM for the F28003x describes the PC Trace module as means to "trace an entire program execution sequence over a period of time". Our working understanding of this module is that it can be used to perform "on-chip" trace and would enable us to achieve object code coverage.

Can Texas Instruments confirm that our understanding of the PC Trace module is correct and that it can in fact be used to achieve object code coverage?

Thanks!

Neal Malackowski

21 days ago

0 Ozino Odharo 21 days ago

TI__Mastermind 20724 points

Hi Neal,

We have trace analyzer provided by CCS that can enable non-intrusive debug and analysis.

https://www.ti.com/lit/ug/spruhm7b/spruhm7b.pdf

Here's a forum post that provides more information on how code coverage can be done in CCS and with the C2000 Compiler.

how to generate a code coverage report

Regards,

Ozino

0 Neal Malackowski 20 days ago in reply to Ozino Odharo

Prodigy 40 points

Thanks for this Ozino! I'll look into that.

So to confirm, the tools in CCS (with the possible addition of third-party unit testing & code coverage tools like Cantata) in conjunction with the Hardware Trace Analyzer would allow us to achieve the following?

At the source code level:

Modified Condition/Decision Coverage (MCDC)
Decision Coverage
Statement Coverage
Data Coupling and Control Coupling Coverage

Then we'll also need to verify additional code not traceable to source (i.e. compiled assembly code), by performing object code to source code tracing and object code coverage.

Thanks,

Neal

0 Ozino Odharo 18 days ago in reply to Neal Malackowski

TI__Mastermind 20724 points

Hi Neal,

Let me check with the CCS team to understand if what you're asking is feasible within CCS.

Regards,

Ozino

0 Ki 17 days ago in reply to Ozino Odharo

TI__Guru**** 466031 points

Ozino Odharo said:
what you're asking is feasible within CCS.

A few notes:

Hardware Trace Analyzer is an old Trace debug tool in CCS that is no longer supported. It also never supported any C2000 device
F28003x device does have a hardware trace module part of ERAD that can support PC trace. However:
- ERAD trace support in CCS is limited to F28Px and F29 device: https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-trace.html#erad-trace.
- ERAD trace is supported outside of CCS by some other technique. The C2000 experts can provide more details

I will bring this thread to the C2000 experts for further comment.

Thanks

0 Ki 17 days ago in reply to Ki

TI__Guru**** 466031 points

Ki said:
ERAD trace support in CCS is limited to F28Px and F29 device

More details on the above. I checked with CCS engineering and they mentioned that The specific ERAD hardwaere trace features used by CCS trace is only available with F28Px and F29.

0 Ryan Ma 17 days ago in reply to Ki

TI__Mastermind 25966 points

Hi Neal,

Unfortunately for this device, PCTRACE is not available. The TRM has a literature bug which was reported and has been fixed after this release version of the TRM.

PCTRACE is only available for F28P65x, F28P55x and F29x devices.

Apologize for the confusion this may have caused.

Best regards,

Ryan Ma

0 Neal Malackowski 11 days ago in reply to Ryan Ma

Prodigy 40 points

Ryan,

Oh okay, that makes sense considering there was a discrepancy between the F28003x datasheet and the TRM regarding PCTRACE.

So on the devices that do have PCTRACE, it can be used to validate the object code within CCS? Further per the Lauterbach’s TRACE32 website, on-chip trace is supported, can you confirm?

Thanks!

Neal

+1 Ryan Ma 11 days ago in reply to Neal Malackowski

TI__Mastermind 25966 points

Hi Neal,

Neal Malackowski said:
So on the devices that do have PCTRACE, it can be used to validate the object code within CCS? Further per the Lauterbach’s TRACE32 website, on-chip trace is supported, can you confirm?

Yes, PCTRACE can be used to validate code flow within CCS using the PC Trace tool.

I do not have direct contact with Lauterbach, however what you see on their website is supported which are our C28x cores. The on chip trace feature that LAUTERBACH supports is on F28P65x. However I notice that the on chip trace is not not supported on F280039, and only debug feature is available. I would contact LAUTERBACH directly to ensure the on chip trace feature is what you're looking for.

https://www.lauterbach.com/supported-platforms/architectures/c2000