请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。
器件型号：MCU-PLUS-SDK-AM243X 主题中讨论的其他器件：CCStudio、 AM2434、 AM2432
我尝试使用 DSS 脚本 loadit.sh、它在 main.js 行239 (debugSession.memory.loadProgram (OUTFILE))挂起。
我不熟悉 DSS、因此请不要以为我知道太多。
我在 Linux 系统上运行、能够通过 CCS GUI 加载和执行该操作、但我必须能够通过命令行对器件进行编程和刷写、以实现自动化。 我无法通过 Rhino 进一步进入。
如何进一步调试？
控制台：
~/ti/ccs1210/ccs/ccs_base/scripting/examples/loadti $ dss.sh -dss.debug main.js -v -s=~/stdout.log -c ~/ti/CCSTargetConfigurations/am243x-gp-evm-XDS200.ccxml /home/markwar/workspaces/ti-rot4.1-fvt/rot4.1-fvt/fvt_jtag_flash/Debug/fvt_jtag_flash.out SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See www.slf4j.org/codes.html for further details.
Rhino 内部的 JavaScript 控制台：
***** DSS Generic Loader ***** START: 09:40:31 GMT-0600 (CST) Configuring Debug Server for specified target... getServer: ENTRY sServerName: DebugServer.1 getServer: Getting definition for: DebugServer.1 getServer: Constructing server getServer: RETURN com.ti.debug.engine.scripting.DebugServer@45909523 setConfig: ENTRY sConfigurationFile: /home/markwar/ti/CCSTargetConfigurations/am243x-gp-evm-XDS200.ccxml setConfig: RETURN Done debuggerOpen: ENTRY sBoardName: * sCPUName: * start: ENTRY start: Firing: onServerStarting() start: Connecting to XPCOM DebugServer start: Initializing DebugServer using specified configuration: "/home/markwar/ti/CCSTargetConfigurations/am243x-gp-evm-XDS200.ccxml" waitUntil: ENTRY com.ti.ccstudio.scripting.environment.ScriptingEnvironment@4759f349 timeout: infinite <init>: CPU Name: MAIN_Cortex_R5_0_0 <init>: PartNum: AM2434_ALV <init>: Family: 470 <init>: SubFamily/MajorISA: d <init>: Revision/MinorISA: 0 <init>: Platform: EMULATOR <init>: Processor ID: 1971336192 <init>: DBName: ArmAdvancedFeatures <init>: CPU Name: CS_DAP_0 <init>: PartNum: AM2434_ALV <init>: Family: 224 <init>: SubFamily/MajorISA: 1 <init>: Revision/MinorISA: 0 <init>: Platform: NONE <init>: Processor ID: 939525125 waitUntil: RETURN com.ti.ccstudio.scripting.environment.ScriptingEnvironment@4759f349 start: Firing: onServerStarted() start: Searching for devices listDevices: ENTRY listDevices: Found debuggable device: Texas Instruments XDS2xx USB Debug Probe_0/MAIN_Cortex_R5_0_0 listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Debug Probe_0/CS_DAP_0 listDevices: RETURN start: RETURN debuggerOpen: RETURN Texas Instruments XDS2xx USB Debug Probe_0/MAIN_Cortex_R5_0_0 setString: ENTRY ID: FileIODefaultDirectory Value: undefined setString: RETURN TARGET: Texas Instruments XDS2xx USB Debug Probe_0 Connecting to target... connect: ENTRY isConnected: ENTRY isConnected: Target is not connected isConnected: RETURN false connect: Requesting target connect waitUntil: ENTRY timeout: infinite log: Target is now connected waitUntil: RETURN isConnected: ENTRY isConnected: Target is connected isConnected: RETURN true connect: RETURN testEnv.outFiles: /home/markwar/workspaces/ti-rot4.1-fvt/rot4.1-fvt/fvt_jtag_flash/Debug/fvt_jtag_flash.out Loading /home/markwar/workspaces/ti-rot4.1-fvt/rot4.1-fvt/fvt_jtag_flash/Debug/fvt_jtag_flash.out loadProgram: ENTRY sFileName: /home/markwar/workspaces/ti-rot4.1-fvt/rot4.1-fvt/fvt_jtag_flash/Debug/fvt_jtag_flash.out load: Requesting program load waitUntil: ENTRY timeout: infinite waitUntil: RETURN load: Program load successful getBoolean: ENTRY ID: AutoRunToLabelOnRestart getBoolean: RETURN true waitForHaltIfPropertySet: Waiting for halt waitUntil: ENTRY timeout: infinite
