How to measure task execution time on F28379D target with XDS110 Debug probe from TI?

Hi All,

I would like to measure the real time execution time on my F28379D mcu assembled on the PCB.

I can get such a report then I use an eval. board of F2839D. This eval board has build in XDS100V2 emulator and native ccxml files (f28377D.ccxml and f28379D.ccxml ) do support XDS100 emulators.

Thanks to this thread: https://www.mathworks.com/matlabcentral/answers/405027-how-to-measure-task-execution-time-on-f28379d-target I found out that despite the fact that I have F28379D mcu I should choose f28377D.ccxml file in order to get the report. So it does work well. (In this example XDS100V2 was used ).

The problem appears then I want to get same report from the same type of mcu, soldered to my PCB. For JTAG programming and External mode purpose I have XDS110 emulator. So in order to use with emulator I just created new ccxml in CCSv8 for F28379D. For now it works well (JTAG and External mode only)

But in this case, I get such an report (below) and error ( underlined at the end of the report) , either new ccxml file was made for f28377D or f28379D mcu's. My Matlab version is R2017b (but on R2018A it behaves the same).

Below in this thread I found such a massage: https://www.mathworks.com/help/supportpkg/texasinstrumentsc2000/examples/real-time-code-execution-profiling.html

The shipped target configuration file (ccxml) removes RAM initializations done by the debugger while connecting to the target. Please make sure of this behavior on using a custom target configuration file.

Accually, this report exactly appears then I tryed to get the real time report on XDS100V2 with f28379D.ccxml file on my eval. board.

What should be the possible issues with XDS110 or how can I be sure that my custom ccxml file is the same like native ccxml file ?

Thanks in advance

------------------------------------------------------------------------

codertarget.profile.getData('test')

Attempting to get profile data from hardware

*** Starting into jsProfilData.js ***

*** User inputs:

Target Configuration: C:\Users\alexs\Desktop\NewTargetConfiguration.ccxml

Program Name: test.out

Board Name: *

CPU Name: C28xx_CPU1

*** Get debug session...

*** Start debug session...

*** Debug Session Name: Texas Instruments XDS110 USB Debug Probe_0/C28xx_CPU1

*** Board Name: Texas Instruments XDS110 USB Debug Probe_0

*** CPU Name: C28xx_CPU1

*** Connecting to target...

C28xx_CPU1: GEL Output:

Memory Map Initialization Complete

C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.

*** Loading symbols...

*** Starting the profile data collection...

MATLAB_START

org.mozilla.javascript.WrappedException: Wrapped java.lang.ArrayIndexOutOfBoundsException: 0 (C:\ProgramData\MATLAB\SupportPackages\R2017b\toolbox\target\supportpackages\tic2000\CCS_Config\jsProfileData.js#111)

at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1693)

at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)

at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:204)

at org.mozilla.javascript.optimizer.OptRuntime.callN(OptRuntime.java:86)

at org.mozilla.javascript.gen.c1._c0(C:\ProgramData\MATLAB\SupportPackages\R2017b\toolbox\target\supportpackages\tic2000\CCS_Config\jsProfileData.js:111)

at org.mozilla.javascript.gen.c1.call(C:\ProgramData\MATLAB\SupportPackages\R2017b\toolbox\target\supportpackages\tic2000\CCS_Config\jsProfileData.js)

at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:340)

at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2758)

at org.mozilla.javascript.gen.c1.call(C:\ProgramData\MATLAB\SupportPackages\R2017b\toolbox\target\supportpackages\tic2000\CCS_Config\jsProfileData.js)

at org.mozilla.javascript.gen.c1.exec(C:\ProgramData\MATLAB\SupportPackages\R2017b\toolbox\target\supportpackages\tic2000\CCS_Config\jsProfileData.js)

at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:503)

at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:425)

at org.mozilla.javascript.tools.shell.Main.processFile(Main.java:391)

at org.mozilla.javascript.tools.shell.Main.processSource(Main.java:382)

at org.mozilla.javascript.tools.shell.Main.processFiles(Main.java:179)

at org.mozilla.javascript.tools.shell.Main$IProxy.run(Main.java:100)

at org.mozilla.javascript.Context.call(Context.java:528)

at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:450)

at org.mozilla.javascript.tools.shell.Main.exec(Main.java:162)

at com.ti.ccstudio.apps.internal.scripting.RunScript$1.run(RunScript.java:89)

Caused by: java.lang.ArrayIndexOutOfBoundsException: 0

at com.ti.debug.engine.scripting.APIContainer.loggableArray(APIContainer.java:204)

at com.ti.debug.engine.scripting.Memory.readData(Memory.java:1828)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:145)

... 18 more

Error using codertarget.tic2000.internal.getProfileData (line 74)

Attempt Failed. No profile data received! Please try re-doing the process

Error in codertarget.profile.getData

Answer 1

[Alex Slobodnik]

Hi All,

After some trials I have found the answer to my question so I will post the solution if someone will face to the some problem:

The native f28377D.ccxml and f28379D.ccxml files have a different content, acually f28377D contains more code than the second one:

This is the content of f28379D.ccxml file:

And this is the content of f28377D.ccxml file. Blue colored piece of code is the missing part of the f28379D.ccxml file

So, your custom ccxml file in Code Composer shall be paired to XDS110 USB debug probe and f28377D MCU. The output file does not have the missing code, so you should copy it to your custom ccxml file exactly at the same place like it done in native f28377D.ccxml file and save the new file.