AM2434: Heap and Stack Views don't show in ROV

Hello Tushar,
thank you for your answer.
I have to apologize for only getting back to you now.
I was on vaccation.

To answer your question,
as our internal documentation for getting the ROV to run suggests, I have copied the syscfg_c.rov.xs from our template folder:





The content of this file is the following:

Probably I need to provide a full path in line 7.
Our documentation doesn't say anything of the likes.
Will try that.

Hi Philip,

Philip Schröder said:

Probably I need to provide a full path in line 7.
Our documentation doesn't say anything of the likes.
Will try that.

Looking forward to hear from you.

Regards,

Tushar

Sadly using the absolute path doesn't change the error.

Hello Philip,

I can see you have pasted the code in the syscfg_c.rov.xs file from the FreeRTOS.rov.js file. Please remove all the code content from the file and keep the code provided in the above reply.

Please refer https://e2e.ti.com/.../5360220

Also I can see your folder structure and mine looks different. I am using MCU+SDK and the FreeRTOS.rov.js file is located at path ${MCU+SDK}/source/kernel/freertos/rov.

Can you please provide details about your setup?

Regards,

Tushar

I am sorry to say that I have no inside into why the people in our company working on that code decided to put that code inside syscfg_c.rov.xs, but here is my guess:

First of all refering to this guide:

https://software-dl.ti.com/ccs/esd/documents/rov_guide/html/src/rov.html

it says there:

" If you specified a path to the executable when connecting to ROV (rather than using the program currently being debugged in CCS), ROV looks for the <code>.rov.xs</code> file in the same directory that contains the executable and in the <code>configPkg/package/cfg</code> subdirectory."

So to put the rov.xs file in the same place where the executable is, should be fine.
As you have to specify the location of the SDK in CCS -> Preferences -> Code Composer Studio -> Products
the relative path from the SDK root to the FreeRTOS.rov.js should suffice to access the js file.

Next, xs seems to be the XDCScript interpreter as explained here:

https://software-dl.ti.com/targetcontent/legacy_files/targetcontent/rtsc/xdctools_3_10/xdctools_3_10_03/exports/docs/rtscpedia/Command_-_xs/Command_-_xs.html

where the XDCScript language is an extension of JavaScript as explained here:

https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/3_16_02_32/exports/docs/rtscpedia/The_XDCscript_Language/The_XDCscript_Language.html

Therefore putting JavaScript code inside the xs files should be fine.

Now my guess would be that we need some extra memory sections for our specific project. Therefore it would be wrong from a software architecture standpoint to pollute the SDK files with that, so we do not put this into FreeRTOS.rov.js but into the script that we have outside of the SDK-subtree which is the syscfg_c.rov.xs which is put into our build-directory.

I would not say that the code in the syscfg_c.rov.xs file is the same code as that in FreeRTOS.rov.js.
True the Program and Monitor variables are redefined but as they are loaded from modules, I guess that the scripts are run in module scope, therefore variables defined with "let" in JS have module scope and are not global. And my guess would be that syscfg_c.rov.xs and FreeRTOS.rov.js run in different modules. So the variables need to be redefined. Maybe the definitions need to exist somehow for a valid memory image, that I do not know.

As it is explained here:

https://software-dl.ti.com/targetcontent/legacy_files/targetcontent/rtsc/xdctools_3_10/xdctools_3_10_03/exports/docs/rtscpedia/Command_-_xs/Command_-_xs.html

"The xs command is implemented using the Java programming language. The actual JavaScript interpreter is based on the Mozilla Rhino package."

Further my guess would be that internally xs uses jar files for different actions. Probably they are somewhere in the XDC-package. As the paths ti.sysbios.heaps.HeapMem and ti.sysbios.knl.Tasks look like qualified paths to jar files.
And those jar files are what I am missing here somehow.

Update:
It seems that those are not JAR-files:

I am trying to define instances of the heap and task modules as described here:

https://www.ti.com/lit/ug/spruex3v/spruex3v.pdf?ts=1725344342727&ref_url=https%253A%252F%252Fwww.ti.com%252Ftool%252FTI-RTOS-PROC

in my syscfg_c.rov.xs.

I tested it out now with the following script extension of syscfg_c.rov.xs:

and then in CCS-debug I get an error:



So my question basically comes down to where those files are located?
If you do not know, maybe you could put the 2 lines that I added into your file and try if the modules are found.
And if they are, you could do something like this:

https://stackoverflow.com/questions/10111163/how-can-i-get-the-path-of-a-module-i-have-loaded-via-require-that-is-not-mine

to find out the path. That is what I am looking for. Thanks.

Hi Philip,

Philip Schröder said:

If you do not know, maybe you could put the 2 lines that I added into your file and try if the modules are found.
And if they are, you could do something like this:

I can see the lines of code which you highlighted above is from TI-RTOS(SYS/BIOS) which is not part of MCU+SDK.

The TI-RTOS package is for legacy devices and support is not available. Please refer https://www.ti.com/tool/TI-RTOS-MCU for more info.

Regards,

Tushar

But those where the packages that CCS couldn't find for visualization of the heap and stack views in ROV,
compare:

So if those packages are not part of the TI-SDK, which packages can I use instead then please to get those graphics that you see in the documentation of the ROV here:

https://software-dl.ti.com/ccs/esd/documents/rov_guide/html/src/rov.html


Also it says in the documentation (www.ti.com/.../TI-RTOS-MCU) that you linked to:

"The TI-RTOS package on this page is for legacy devices and support is not available. For new devices if TI-RTOS is available it will be included in the software development kit (SDK) for that device."

Thank you for your help.