program_evm ccxml does not work "out of the box" with TMDXEVM6678

Gordon Deane

Other Parts Discussed in Thread: CCSTUDIO

I was trying to use the MCSDK 2.0.5 "program_evm" utility to flash an Advantech TMDXEVM6678LE eval board, and the default ("out of the box") CCXML target files don't work. I get errors as below. Similar errors arose when I tried with the XDS100 onboard emulator as well.

I was about to post this complaint and give up, but decided to try setting "PROGRAM_EVM_TARGET_CONFIG_FILE" to a CCXML I created with CCS 5.1. This seems to have worked.

Therefore the program_evm_userguide.pdf is incorrect to state that "This step is required only if you are using an emulator other than the one that came with your board."

c:\ti\mcsdk_2_00_05_17\tools\program_evm>%DSS_SCRIPT_DIR%\dss.bat program_evm.js tmdxevm6678le-le
board: evm6678l
endian: Little
emulation: XDS560 mezzanine
binaries: c:\ti\mcsdk_2_00_05_17\tools\program_evm/binaries/evm6678l/
ccxml: c:\ti\mcsdk_2_00_05_17\tools\program_evm/configs/evm6678l/evm6678le.ccxml
SEVERE: Can't generate board data file C:\Users\GD4\AppData\Local\.TI\213602635\0\0\BrdDat\ccBoard0
dat
An invalid processor ID has been found.

SEVERE: Could not start server: DebugServer.1: Can't generate board data file C:\Users\GD4\AppData\
ocal\.TI\213602635\0\0\BrdDat\ccBoard0.dat
An invalid processor ID has been found.

org.mozilla.javascript.WrappedException: Wrapped com.ti.ccstudio.scripting.environment.ScriptingExc
ption: Could not start server: DebugServer.1: Can't generate board data file C:\Users\GD4\AppData\L
cal\.TI\213602635\0\0\BrdDat\ccBoard0.dat
An invalid processor ID has been found.
(program_evm.js#269)
        at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1705)
        at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:157)
        at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:201)
        at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:74)
        at org.mozilla.javascript.gen.c1._c0(program_evm.js:269)
        at org.mozilla.javascript.gen.c1.call(program_evm.js)
        at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:337)
        at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2755)
        at org.mozilla.javascript.gen.c1.call(program_evm.js)
        at org.mozilla.javascript.gen.c1.exec(program_evm.js)
        at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:500)
        at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:422)
        at org.mozilla.javascript.tools.shell.Main.processFile(Main.java:388)
        at org.mozilla.javascript.tools.shell.Main.processSource(Main.java:379)
        at org.mozilla.javascript.tools.shell.Main.processFiles(Main.java:176)
        at org.mozilla.javascript.tools.shell.Main$IProxy.run(Main.java:97)
        at org.mozilla.javascript.Context.call(Context.java:540)
        at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:447)
        at org.mozilla.javascript.tools.shell.Main.exec(Main.java:159)
        at org.mozilla.javascript.tools.shell.Main.main(Main.java:137)
Caused by: com.ti.ccstudio.scripting.environment.ScriptingException: Could not start server: DebugS
rver.1: Can't generate board data file C:\Users\GD4\AppData\Local\.TI\213602635\0\0\BrdDat\ccBoard0
dat
An invalid processor ID has been found.

        at com.ti.debug.engine.scripting.DebugServer$SessionFactory.<init>(DebugServer.java:155)
        at com.ti.debug.engine.scripting.DebugServer.openSession(DebugServer.java:1314)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:142)
        ... 18 more

over 13 years ago

0 ArunMani over 13 years ago

TI__Genius 9915 points

Gordon, First of all please don't use the XDS100 in a LE board. it will not work if you have the mezzanine board and we highly discourage the users to remove it. Having said that the documentation that comes with this doesn't seems to have LE specific instructions. that might be the reason you faced this issue. Thanks for pointing this. I will take a look and correct the documentation accordingly.

Thanks,

Arun.

0 Gordon Deane over 13 years ago in reply to ArunMani

Expert 1255 points

Arun,

Thanks for replying so quickly. It's useful to know that the XDS100 doesn't work with the mezzanine board on.

You say that "we highly discourage the users to remove it". Is that just because the resulting board is slower and debugging is less capable? I had assumed that a TMDXEVM6678LE without the mezzanine card was just the same as a -L and therefore the XDS100 should work OK. The mezzanine card physically overshadows the EMIF-16 header, and our sparkies have designed an EMIF-16 connector to our FPGA board that is physically incompatible with the mezzanine card, so as soon as I get the associated FPGA board tomorrow I will need to take the mezzanine board off or go and dig out an EVM-L from the lab.

To your other point, "...the documentation that comes with this doesn't seems to have LE specific instructions. that might be the reason you faced this issue." I think you've misunderstood me, it certainly does have LE specific instructions. The program_evm_userguide.pdf I'm reading clearly says (p4, my emphasis):

7.2.1 Windows
1. Set the DSS_SCRIPT_DIR environment variable (Mandatory) to your Code Composer Studio scripting bin directory.
Example:
set DSS_SCRIPT_DIR="C:\Program Files\Texas Instruments\ccsv5\ccs_base_5.0.3.00022\scripting\bin"
2. Set the PROGRAM_EVM_TARGET_CONFIG_FILE environment variable (Optional)
Example:
set PROGRAM_EVM_TARGET_CONFIG_FILE="C:\Documents and Settings\a0756924\user\CCSTargetConfigurations\myC667xl.ccxml"
This step is required only if you are using an emulator other than the one that came with your board. If you wish to use such an external emulator you will need to set PROGRAM_EVM_TARGET_CONFIG_FILE. If this environment variable is not set, the DSS script will use the default ccxml files that support the following emulators:
1. xds100 inbuilt (evm667xl.ccxml)
2. xds560 mezzanine card (evm667xle.ccxml)
Please note that depending on the emulator selected the restore image time may vary. For example, if xds100 inbuilt emulator is selected, the entire process may take over 60 minutes. If xds560 mezzanine card emulator is selected, the process may take about 10 minutes.

You might want to update the documentation to match.

The default CCXML for the xds560 that is actually present seems to be for an STM trace module, not a mezzanine card, I don't know if that's relevant.

0 tscheck over 13 years ago in reply to Gordon Deane

TI__Mastermind 23525 points

Gordon,

A couple comments. First, regarding the mezzanine removal on the TMDXEVM6678LE. It is true that the mezzanine can be removed, the EVM then reverts back to the TMDXEVM6678L using the on-board XDS100. However, as Arun mentioned, we discourage this because we have seen damaged mezzanine cards when repeatedly uninstalling/re-installing the mezzanine. The mezzanine connectors are simply not built to handle this. We have seen damaged flash components on the mezzanine from this. Sounds like you are simply removing it one time so you can plug in your FPGA board, which shouldn't be a problem.

Regarding the default .ccxml files used by the Program_evm script, these seem to work fine for me. I only tested the 560v2 mezzanine configuration, by setting the DSS_SCRIPT_DIR variable, I did not even set the PROGRAM_EVM_TARGET_CONFIG_FILE variable. I used CCS5.0.3 (sounds like you have CCS5.1.x) with the following command:

%DSS_SCRIPT_DIR%\dss.bat program_evm.js TMDXEVM6678le-le

If using the on-board XDS100, it would be:

%DSS_SCRIPT_DIR%\dss.bat program_evm.js TMDXEVM6678l-le

Hope that helps,

Travis

0 Gordon Deane over 13 years ago in reply to tscheck

Expert 1255 points

OK, thanks, that's helpful. It sounds like it might be a CCS incompatibility. Anyway, the problem is sorted for now.

Processors

Processors forum

program_evm ccxml does not work "out of the box" with TMDXEVM6678