Disabling CIO breakpoint through dss java script

Venkat Ramanan

Hi,

I'm using DSS javascripts to run some test cases. It seems the CIO Function use is enabled by default. How to disable the CIO breakpoint through java script.

I'm not sure which option to use to disable it.

Thanks,

Venkat

over 11 years ago

0 desouza over 11 years ago

TI__Guru**** 169894 points

Venkat,

I did not test this, but one way that you can do is use the DSS API to remove breakpoints. As shown in the example file Breakpoints.js (inside ccsv6/ccs_base/scripting/examples/DebugServerExamples) you can check the sequence to enable a breakpoint:

// Set another breakpoint
var address = debugSession.symbol.getAddress("ReadNextData")
var bp2 = debugSession.breakpoint.add(address)

A breakpoint.remove() method exists for the object above. Check section DebugServer --> Breakpoint class of the DS API documentation link of the documentation below:

ccsv6/ccs_base/scripting/docs/GettingStarted.htm

And pass the CIO symbols as shown in the link below:

http://processors.wiki.ti.com/index.php/Tips_for_using_printf#Special_Breakpoints

Hope this helps,

Rafael

0 Venkat Ramanan over 11 years ago in reply to desouza

Intellectual 270 points

Thanks for the reply desouza

I tried using breakpoint.remove(), but it didn't work. Actually I'm using debugSession.breakpoint.removeAll(); before adding a new breakpoint. But this doesn't seem to have any effect on the CIO breakpoint.

I'm specifically looking for properties under

debugSession.options.setBoolean(java.lang.String propertyName, boolean value);

I do not know what is the propertyName that enables/disables the CIO breakpoint.

Where do I get the list of propertyName for debugSession.options.

0 Venkat Ramanan over 11 years ago in reply to Venkat Ramanan

Intellectual 270 points

Kind of solved the issue by moving the CIO buffer section to RAM as mentioned in

http://processors.wiki.ti.com/index.php/Tips_for_using_printf#Special_Breakpoints

.text:cio : { rts*.lib<trgmsg.obj ankmsg.obj>(.text) } > RAM

But still would like to know the information about the propertyNames under debuSession.options