• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 796 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MCU-PLUS-SDK-AM243X: AM243x

Mark Ward
Prodigy 111 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: CCSTUDIO, AM2434, AM2432

I am trying to use the DSS script loadit.sh and it hangs at main.js line 239 (debugSession.memory.loadProgram(outFile)).

I am new to DSS, so please don't assume I know much.

I am running on a Linux system and able to load and execute this via CCS GUI, but I must be able to program and flash my device via command line for automation.  I cannot step in any further via Rhino.

How do I debug this further?

Console:

✔ ~/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 http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

JavaScript Console from within Rhino:

***** 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

  • 0
    Prodigy 111 points

    The SLF4J warnings don’t bother me, they are a known problem that I can ignore.

    I can get some images to load.  We have some simpler, smaller builds that load and run (223K), but when I try and load a larger (1.2M) - which loads and runs via CCS GUI without issues - it hangs.

     

    I have been looking at the difference in the logs, and I have tried to single step the script in Rhino, but I haven’t gotten any further in discovering the nature of the hang other than it is waiting for a halt.

    Output from kitchen_sink_am243_gpio_fvt_1.out (223k) Output from kitchen_sink_am243.out (1.2M)

    $ loadti.sh -v -c ~/ti/CCSTargetConfigurations/am243-gp-evm-fresh-xds200.ccxml ~/Downloads/kitchen_sink_am243_gpio_fvt_1.out

    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

    SLF4J: Defaulting to no-operation (NOP) logger implementation

    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

     

    ***** DSS Generic Loader *****

     

    START: 16:18:29 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@e688bb6

    setConfig: ENTRY sConfigurationFile: /home/markwar/ti/CCSTargetConfigurations/am243-gp-evm-fresh-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/am243-gp-evm-fresh-xds200.ccxml"

    waitUntil: ENTRY com.ti.ccstudio.scripting.environment.ScriptingEnvironment@850908btimeout: 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: MAIN_Cortex_R5_0_1

    <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: MAIN_Cortex_R5_1_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: MAIN_Cortex_R5_1_1

    <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: DMSC_Cortex_M3_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: e

    <init>: Revision/MinorISA: 0

    <init>: Platform: EMULATOR

    <init>: Processor ID: 1971337216

    <init>: DBName: ArmAdvancedFeatures

    <init>: CPU Name: ICSS_G0_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_RTU_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_TX_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_RTU_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_TX_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_RTU_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_TX_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_RTU_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_TX_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: BLAZAR_Cortex_M4F_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: e

    <init>: Revision/MinorISA: 0

    <init>: Platform: EMULATOR

    <init>: Processor ID: 1971337216

    <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

    <init>: CPU Name: CSSTM_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: 26

    <init>: Revision/MinorISA: 0

    <init>: Platform: NONE

    <init>: Processor ID: 1971361796

    <init>: CPU Name: CTSET2

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: 27

    <init>: Revision/MinorISA: 0

    <init>: Platform: NONE

    <init>: Processor ID: 1971362820

    <init>: CPU Name: DebugCell_TBR_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: 25

    <init>: Revision/MinorISA: 0

    <init>: Platform: NONE

    <init>: Processor ID: 1971360772

    waitUntil: RETURN com.ti.ccstudio.scripting.environment.ScriptingEnvironment@850908b

    start: Firing: onServerStarted()

    start: Searching for devices

    listDevices: ENTRY

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_0_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_0_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_1_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_1_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/DMSC_Cortex_M3_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_RTU_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_TX_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_RTU_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_TX_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_RTU_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_TX_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_RTU_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_TX_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/BLAZAR_Cortex_M4F_0

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/CS_DAP_0

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/CSSTM_0

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/CTSET2

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/DebugCell_TBR_0

    listDevices: RETURN

    start: RETURN

    debuggerOpen: RETURN Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_0_0

    setString: ENTRY ID: FileIODefaultDirectory Value: undefined

    setString: RETURN

    TARGET: Texas Instruments XDS2xx USB Onboard 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/Downloads/kitchen_sink_am243_gpio_fvt_1.out

    Loading /home/markwar/Downloads/kitchen_sink_am243_gpio_fvt_1.out

    loadProgram: ENTRY sFileName: /home/markwar/Downloads/kitchen_sink_am243_gpio_fvt_1.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

    log: Target has halted at 0x70094B10

    waitUntil: RETURN

    loadProgram: RETURN

    Done

    Target running...

    setScriptTimeout: ENTRY nTimeout: -1

    setScriptTimeout: Timeout is infinite

    setScriptTimeout: RETURN

    exists: ENTRY sSymbol: C$$EXIT

    exists: Getting symbol package

    exists: Looking-up symbol

    exists: Symbol "C$$EXIT" exists

    exists: RETURN true

    evaluate: ENTRY sExpression: PC == C$$EXIT

    eval: Requesting evaluation of expression: "PC == C$$EXIT"

    isConnected: ENTRY

    isConnected: Target is connected

    isConnected: RETURN true

    isHalted: ENTRY

    isHalted: Target is halted

    isHalted: RETURN true

    waitUntil: ENTRY com.ti.ccstudio.scripting.environment.ScriptingEnvironment@850908btimeout: infinite

    waitUntil: RETURN com.ti.ccstudio.scripting.environment.ScriptingEnvironment@850908b

    waitUntil: ENTRY timeout: infinite

    onEvent: Evaluated expression: PC == C$$EXIT

    waitUntil: RETURN

    evaluate: RETURN 0x0

    exists: ENTRY sSymbol: C$$EXITE

    exists: Getting symbol package

    exists: Looking-up symbol

    exists: RETURN false

    exists: ENTRY sSymbol: abort

    exists: Getting symbol package

    exists: Looking-up symbol

    exists: Symbol "abort" exists

    exists: RETURN true

    evaluate: ENTRY sExpression: PC == abort

    eval: Requesting evaluation of expression: "PC == abort"

    isConnected: ENTRY

    isConnected: Target is connected

    isConnected: RETURN true

    isHalted: ENTRY

    isHalted: Target is halted

    isHalted: RETURN true

    waitUntil: ENTRY com.ti.ccstudio.scripting.environment.ScriptingEnvironment@850908btimeout: infinite

    waitUntil: RETURN com.ti.ccstudio.scripting.environment.ScriptingEnvironment@850908b

    waitUntil: ENTRY timeout: infinite

    onEvent: Evaluated expression: PC == abort

    waitUntil: RETURN

    evaluate: RETURN 0x0

    Interrupt to abort . . .

    runBenchmark: ENTRY

    runBenchmark: ENTRY nEventID: 0

    runBenchmark: Setting Profile Clock count event

    setCurrentEvent: ENTRY nEventID: 0

    setCurrentEvent: Profile Clock is already configured to profile: Clock Cycles

    setCurrentEvent: RETURN

    runBenchmark: Enabling Profile Clock event counting

    enable: ENTRY

    enable: RETURN

    runBenchmark: Resetting the profile clock register

    reset: ENTRY

    reset: RETURN

    runBenchmark: Running target

    run: ENTRY

    go: Requesting target execution

    waitUntil: ENTRY timeout: infinite

    GPIO FVT Test Started ...

    0(0) 1(0) 2(0) 3(1) 4(1) 5(0) 6(0) 7(0) 8(1) 9(0) 10(0) 11(0) 12(0) 13(0) 14(0) 15(1) 46(1) 47(1) 48(1) tick_ms=9

    0(0) 1(0) 2(0) 3(1) 4(1) 5(0) 6(0) 7(0) 8(1) 9(0) 10(0) 11(1) 12(1) 13(1) 14(1) 15(0) 46(1) 47(1) 48(1) tick_ms=5017

    0(0) 1(0) 2(0) 3(1) 4(1) 5(0) 6(0) 7(0) 8(1) 9(0) 10(0) 11(1) 12(1) 13(1) 14(1) 15(1) 46(1) 47(1) 48(1) tick_ms=10025

    $ loadti.sh -v -c ~/ti/CCSTargetConfigurations/am243-gp-evm-fresh-xds200.ccxml ~/Downloads/kitchen_sink_am243.out

    SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

    SLF4J: Defaulting to no-operation (NOP) logger implementation

    SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

     

    ***** DSS Generic Loader *****

     

    START: 16:20:05 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@250febf1

    setConfig: ENTRY sConfigurationFile: /home/markwar/ti/CCSTargetConfigurations/am243-gp-evm-fresh-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/am243-gp-evm-fresh-xds200.ccxml"

    waitUntil: ENTRY com.ti.ccstudio.scripting.environment.ScriptingEnvironment@a80860btimeout: 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: MAIN_Cortex_R5_0_1

    <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: MAIN_Cortex_R5_1_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: MAIN_Cortex_R5_1_1

    <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: DMSC_Cortex_M3_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: e

    <init>: Revision/MinorISA: 0

    <init>: Platform: EMULATOR

    <init>: Processor ID: 1971337216

    <init>: DBName: ArmAdvancedFeatures

    <init>: CPU Name: ICSS_G0_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_RTU_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_TX_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_RTU_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G0_TX_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_RTU_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_TX_PRU_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_RTU_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: ICSS_G1_TX_PRU_1

    <init>: PartNum: AM2434_ALV

    <init>: Family: 192

    <init>: SubFamily/MajorISA: 20

    <init>: Revision/MinorISA: 26

    <init>: Platform: EMULATOR

    <init>: Processor ID: 805339344

    <init>: CPU Name: BLAZAR_Cortex_M4F_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: e

    <init>: Revision/MinorISA: 0

    <init>: Platform: EMULATOR

    <init>: Processor ID: 1971337216

    <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

    <init>: CPU Name: CSSTM_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: 26

    <init>: Revision/MinorISA: 0

    <init>: Platform: NONE

    <init>: Processor ID: 1971361796

    <init>: CPU Name: CTSET2

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: 27

    <init>: Revision/MinorISA: 0

    <init>: Platform: NONE

    <init>: Processor ID: 1971362820

    <init>: CPU Name: DebugCell_TBR_0

    <init>: PartNum: AM2434_ALV

    <init>: Family: 470

    <init>: SubFamily/MajorISA: 25

    <init>: Revision/MinorISA: 0

    <init>: Platform: NONE

    <init>: Processor ID: 1971360772

    waitUntil: RETURN com.ti.ccstudio.scripting.environment.ScriptingEnvironment@a80860b

    start: Firing: onServerStarted()

    start: Searching for devices

    listDevices: ENTRY

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_0_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_0_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_1_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_1_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/DMSC_Cortex_M3_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_RTU_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_TX_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_RTU_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G0_TX_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_RTU_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_TX_PRU_0

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_RTU_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/ICSS_G1_TX_PRU_1

    listDevices: Found debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/BLAZAR_Cortex_M4F_0

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/CS_DAP_0

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/CSSTM_0

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/CTSET2

    listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Onboard Debug Probe_0/DebugCell_TBR_0

    listDevices: RETURN

    start: RETURN

    debuggerOpen: RETURN Texas Instruments XDS2xx USB Onboard Debug Probe_0/MAIN_Cortex_R5_0_0

    setString: ENTRY ID: FileIODefaultDirectory Value: undefined

    setString: RETURN

    TARGET: Texas Instruments XDS2xx USB Onboard 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/Downloads/kitchen_sink_am243.out

    Loading /home/markwar/Downloads/kitchen_sink_am243.out

    loadProgram: ENTRY sFileName: /home/markwar/Downloads/kitchen_sink_am243.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

    ^C

    Both outputs say “load: Program load successful“, but the larger image seems to hang waiting for a halt.

     

    I know that the .out file loads and runs without problem via CCS GUI, but not via command line and I don’t seem to have a means of knowing more about why it would get stuck waiting for the halt.  Can you tell me more about that and what I might do to move forward?

  • 0 in reply to Mark Ward
    TI__Guru**** 463941 points

    Hello Mark,

    By default, loadti will run the program and then wait for the program to terminate. If the program does not terminate (runs in a loop, etc) then loadti will just wait indefinitely until loadti is forcibly terminated (CTRL+C, etc). If you run the program and then have loadti exit immediately, you can run with the "-a" option. Another option is to set a timeout (using"-t") so that loadti will wait for a specified amount of time before exiting. 

    See the sections: "Known Limitations" and "Using loadti with MSP430" in the link below for more details:

    https://software-dl.ti.com/ccs/esd/documents/sdto_dss_loadti.html

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 111 points

    That would be okay but I expect to see my device use a UART port for its console.

    When kitchen_sink_am243_gpio_fvt_1.out loaded it periodically spits out a series of strings to the UART and console that indicate the state of a bunch of gpio pins.  It does not exit it just keeps printing a line every 10 seconds with the state of the selected gpio pins.

    kitchen_sink_am243.out uses the same UART to log its boot sequence and then after fully initialized that UART function as a console for the device, but not a single character is output to the UART.

  • 0 in reply to Mark Ward
    TI__Guru**** 463941 points
    Mark Ward said:
    kitchen_sink_am243.out uses the same UART to log its boot sequence and then after fully initialized that UART function as a console for the device, but not a single character is output to the UART.

    When you load and run this program via CCS, you see all the expected output coming from the UART but when using loadti (with just -v, -s, and -c), you are not seeing any UART output while the program is running?

  • 0 in reply to Ki
    Prodigy 111 points

    Correct.  UART output when running from CCS but not when running via loadti.

  • 0 in reply to Mark Ward
    TI__Guru**** 463941 points
    Mark Ward said:
    UART output when running from CCS but not when running via loadti.

    loadti should not be interfering with this. It should be the similar as running the program from CCS.

    Any chance you could share your program? Are you running on a custom AM243x target or some TI EVM or LaunchPad?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 111 points

    We had a breakthrough today and were able to run the kitchen_sink_am243.out file via loadti.sh on our OL8 systems.  Seems the problem is that the embedded target device used to build the one of the projects was AM2434_AVL and the other used AM243x_GP_EVM. Using the same config as the out was built for got it running.  It worries me a bit that we don’t have a config choice for AM2432_AVL which matches the processor on our boards, in absence of that is AM2434_AVL correct target for us to select?

    To make things work smoother I went into the advanced settings and “bypassed” all but the MAIN_Cortex_R5_0_0 processor.

    What I was not able to get running was the Rhino debugger past or into line 87 of main.js in the loadti foldler.  Rhino would start with no problems, but if I let it run it would exit.  If I single stepped it into getArgs() it exits without every showing me the first line of the function.  I would like to get this functionality working as it could be very helpful when we write our one script to load and flash to the am2432.

    Do you know why I can’t get Rhino to step into or over getArgs()?

    This is the command line I am using:

    ~/ti/ccs1210/ccs/ccs_base/scripting/examples/loadti $ dss.sh -dss.debug main.js -c -v ~/ti/CCSTargetConfigurations/am243-gp-evm-fresh-xds200.ccxml ~/Downloads/kitchen_sink_am243_gpio_fvt_1.out

    My guess is that running loadit.sh under dss might cause problems for loadti argument parsing, but that shouldn’t stop me from single stepping.

    Best regards,

    Mark

  • 0 in reply to Mark Ward
    TI__Guru**** 463941 points
    Mark Ward said:
    It worries me a bit that we don’t have a config choice for AM2432_AVL which matches the processor on our boards, in absence of that is AM2434_AVL correct target for us to select?

    I can't comment on this as I don't know what the main differences are between the two. It is likely very similar but I will defer to a device expert (perhaps create a new thread on this)

    Mark Ward said:

    What I was not able to get running was the Rhino debugger past or into line 87 of main.js in the loadti foldler.  Rhino would start with no problems, but if I let it run it would exit.  If I single stepped it into getArgs() it exits without every showing me the first line of the function.  I would like to get this functionality working as it could be very helpful when we write our one script to load and flash to the am2432.

    Do you know why I can’t get Rhino to step into or over getArgs()?

    This is odd. This works for me. If you set a breakpoint at line 87, what shows up as the arguments value?

    Step Into

    How are you running Rhino debugger for loadti? Did you modify the loadti.bat script to use the debugger over the shell as so?

  • 0 in reply to Ki
    Prodigy 111 points

    This is odd. This works for me. If you set a breakpoint at line 87, what shows up as the arguments value?

    -c -v ~/ti/CCSTargetConfigurations/am243-gp-evm-fresh-xds200.ccxml ~/Downloads/kitchen_sink_am243_gpio_fvt_1.out

    Step Into

    The step into fails I do not get taken the the getArgs.js file or getArgs() function, it just exists

    How are you running Rhino debugger for loadti? Did you modify the loadti.bat script to use the debugger over the shell as so?

    Rhino cannot take a batch file or shell script at an input.  I passed the main.js as the starting point ($ dss.sh -dss.debug main.js -c -v ~/ti/CCSTargetConfigurations/am243-gp-evm-fresh-xds200.ccxml ~/Downloads/kitchen_sink_am243_gpio_fvt_1.out), so I did not modify the batch or script file as they are not used.

    The loadti.sh file is much simpler than the loadti.bat file:

    #! /bin/sh
    # This script executes LoadTI for DSS Linux

    export LOADTI_PATH=$(dirname $(which $0))
    $LOADTI_PATH/../../bin/dss.sh $LOADTI_PATH/main.js $@

    So I did the export before calling dss.

    I am able to see the other source files and single step through the first part of main.js, but everything quits when I set into or over getArgs().

  • 0 in reply to Mark Ward
    TI__Guru**** 463941 points
    Mark Ward said:
    -c -v ~/ti/CCSTargetConfigurations/am243-gp-evm-fresh-xds200.ccxml ~/Downloads/kitchen_sink_am243_gpio_fvt_1.out

    This is incorrect. You need to specify the ccxml file after the -c argument. You have a -v right after the -c argument. That will cause an exception to occur.

    Mark Ward said:
    The loadti.sh file is much simpler than the loadti.bat file:

    Sorry, I had forgotten that you are on linux. I will try in that environment.

  • 0 in reply to Ki
    TI__Guru**** 463941 points
    Ki said:
    Sorry, I had forgotten that you are on linux. I will try in that environment.

    Can you use an absolute path to the loadti directory when exporting LOADTI_PATH? I needed to do that instead to get things to work

  • 0 in reply to Ki
    Prodigy 111 points

    I was running loadit out of the ~/ti/ccs1220/ccs/ccs_base/scripting/examples/loadti folder.  dss.sh is available because the ~/ti/ccs1220/ccs/ccs_base/scripting/bin file is in my $PATH.

  • 0 in reply to Mark Ward
    TI__Guru**** 463941 points

    Did you try the absolute path? Did it work?

  • 0 in reply to Ki
    Prodigy 111 points

    No change.  I ran this from my home folder.

    $ dss.sh -dss.debug ~/ti/ccs1210/ccs/ccs_base/scripting/examples/loadti/main.js -c -v ~/ti/CCSTargetConfigurations/am243-gp-evm-fresh-xds200.ccxml ~/Downloads/kitchen_sink_am243_gpio_fvt_1.out
  • 0 in reply to Mark Ward
    TI__Guru**** 463941 points

    This is what I meant:

    Double click on the image to expand.

    See how in the console, the first command I export LOADTI_PATH to the location of the loadti script using an ABSOLUTE PATH. No "~" used.

    Then I run the main.js script in the Rhino debugger.

    I am able to now step through getArgs.js. Note that I hit line 140 because I passed in the arguments incorrectly:

    -c -v <ccxml> <out file>

    That is incorrect. It should be:

    -c <ccxml> -v <out file>

    I expect you to run into the same error also since you are also doing: -c -v <ccxml> <out file>

    Thanks

    ki 

  • 0 in reply to Ki
    Prodigy 111 points

    That worked, thanks!

  • +1 in reply to Mark Ward
    TI__Guru**** 463941 points

    Great!