CCS/AWR1642BOOST: Debug error in CCS while connecting to target (using CCXML file)

pritam kumar1

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: AWR1642,

Tool/software: Code Composer Studio

Have created a .ccxml file for debugging using CCS 7.4. After launching the target when i try to connect the cores to the target by right clicking and "Connect Target " it shows error as no source available for 0x58d8. Also, attaching the snapshot of the error. Please provide help to resolve this.

over 5 years ago

0 Kyle Cousino over 5 years ago

TI__Mastermind 24955 points

Pritam,

It looks like you are able to successfully connect to the MSS core of the AWR1642. After you complete the "Connect to Target" step, you then need to load the code onto the MSS core. You are missing an extra step before you can execute the target application.

Please refer to the SDK User's Guide documentation for more detailed instructions. You can search for the "CCS development mode" section of the User Guide.

Regards,
Kyle

0 db_woodall over 5 years ago

TI__Mastermind 21025 points

When I connect to an R4F I also see the current address at 0x58d8, but don't see the error window. I don't think this is a problem since you haven't actually loaded any code yet. Perhaps it's because you don't have any other source window open. If you can't load code and then start it running, then something weird is going on. In that case you might try restarting CCS, or even downloading a more recent version of CCS. I think this is more likely to happen as well if you are not currently working in a CCS project (meaning, you started the debugger and are going to load and run code built outside of CCS).

Also, here is the content of a valid awr1642.ccxml file for your reference:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds510debugssm.xml" id="drivers" xml="tixds510debugssm.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510icepick_m.xml" id="drivers" xml="tixds510icepick_m.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510c674x.xml" id="drivers" xml="tixds510c674x.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cortexR.xml" id="drivers" xml="tixds510cortexR.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510etbcs.xml" id="drivers" xml="tixds510etbcs.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="AWR1642_0" href="devices/awr1642.xml" id="AWR1642_0" xml="awr1642.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

0 pritam kumar1 over 5 years ago in reply to Kyle Cousino

Prodigy 240 points

Hey Kyle,

After connecting the cores i am loading the DSS and MSS images provided in the path C:\ti\mmwave_sdk_03_02_00_04\packages\ti\demo\xwr16xx\mmw . Then i run the cores by going to Run->Free Run. The following snapshot shows the result. How can I proceed from here to see the debug results for. eg. register values, outputs of the variables etc.

0 Kyle Cousino over 5 years ago in reply to pritam kumar1

TI__Mastermind 24955 points

Pritam,

You will need to set a breakpoint somewhere in your code so you can pause the MSS and DSS cores and look at the registers you are interested in.

Also, since you are using the Out-of-Box Demo, you will need to send the CLI commands to the AWR1642BOOST using a program like Tera Term.

You can find the CLI commands at this file location:

C:\ti\mmwave_sdk_03_02_00_04\packages\ti\demo\xwr16xx\mmw\profiles

Feel free to use any of the configuration files there. You can open them using Notepad.

Regards,
Kyle

0 pritam kumar1 over 5 years ago in reply to Kyle Cousino

Prodigy 240 points

Hi Kyle,

After running the OOB demo in debug mode, and running the cores, following messages are displayed on the console. Also, have connected COM5 (which is the CLI port of my system) in tera term but am not able to send the .config commands to the CLI. Tried suspending the cores in CCS and then send the CLI commands but still it doesn't work. A snapshot of the same is attached below.

0 db_woodall over 5 years ago in reply to pritam kumar1

TI__Mastermind 21025 points

Hi,

The MSS core must be running in order for the CLI port to be functional. And it looks like you stopped it before it finished initializing. The typical output looks like the following (it varies a little from release to release):

[Cortex_R4_0] **********************************************
Debug: Launching the Millimeter Wave Demo
**********************************************
Debug: MMWDemoMSS Launched the Initialization Task
Debug: MMWDemoMSS mmWave Control Initialization was successful
Debug: CLI is operational
[C674X_0] Debug: MMWDemoDSS Data Path init succeeded
Debug: MMWDemoDSS initTask exit

You will see the demo's CLI prompt appear in the TeraTerm window.

-dave

Sensors

Sensors forum

CCS/AWR1642BOOST: Debug error in CCS while connecting to target (using CCXML file)