There appears to be a regression with the dss.bat where additional arguments to be passed to the user script is not longer properly supported.

The main issue is with line 50:

Unable to render embedded object: File (DEBUGSERVER) not found.\..\..\eclipse\eclipsec.exe -nosplash -application com.ti.ccstudio.apps.runScript -product com.ti.ccstudio.branding.product %DEBUG_FLAG% -dss.rhinoArgs %WORKSPACE% %OTHERARGS%

The last parameter (%OTHERARGS) should be wrapped in quotes like so:

Unable to render embedded object: File (DEBUGSERVER) not found.\..\..\eclipse\eclipsec.exe -nosplash -application com.ti.ccstudio.apps.runScript -product com.ti.ccstudio.branding.product %DEBUG_FLAG% -dss.rhinoArgs %WORKSPACE%
"%OTHERARGS%"

That will resolve most of the issues.

However, there will still be one remaining issue. If the parameter is an asterisk (such as one wrapped in quotes like: "*" ), then it is treated as a special character instead of one that is to be passed as is to the user script as-is. This will impact how the parameters are passed to the user script.

The key thing is that with older CCS versions (like CCS 10.1.0), there was no issue passing in an asterisk character as a parameter as-is. Hence this is a regression with 10.3.0.

The user case regarding asterisks is when passing in the board name for the DSS openSession() API. The wild card string "*" is very commonly used as the board name. Note that passing in the full name of the board/connection type often does not work because many names have white spaces in it which are also a problem for the bat file.