CCSTUDIO: [v20.2.0/AWR2E44P] Unable to check real-time variables during debugging.

Part Number: CCSTUDIO

Tool/software:

Hello team,

When customer used CCS v20.2.0 with AWR2E44P. He cannot check real-time variables during debugging.

While debugging, when selecting a core in the RUNNING state, if the variable shown in the WATCH window belongs to that core, in CCS v12.x.x the variable’s value was updated in real time (especially for the DSP, the variable values were periodically refreshed).

However, in CCS v20.2.0, the variables are not updated and instead appear as unrecognized errors.

If I pause and then resume the selected core, the variable values are refreshed. Could you let me know whether this issue is a bug, or if there is a separate setting that needs to be enabled?

• Picture 1: When selecting the DSP core in RUNNING state, the variable is not recognized.

• Picture 2: After pausing, the variables are refreshed. (However, if I then switch from R5_0 core back to the DSP core, the variables again stop updating.)

 

Regards,

Lina

  • Hi Lina,

    I see differences in the device xml files between CCS 12 and CCS 20. The one for CCS 12 explicitly enables real-time mode support so this could be the issue. I will need to investigate further.

    Thanks

    ki

  • Can you provide the ccxml file you are using?

  • Hello Ki,

    This issue was raised by me. As per your request, I’m sharing the contents of the ccxml file related to this issue.

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
        <configuration XML_version="1.2" id="configuration_0">
            <instance XML_version="1.2" desc="Blackhawk XDS560v2-USB System Trace Emulator" href="connections/BH-XDS560v2-USB_Connection.xml" id="Blackhawk XDS560v2-USB System Trace Emulator" xml="BH-XDS560v2-USB_Connection.xml" xmlpath="connections"/>
            <connection XML_version="1.2" id="Blackhawk XDS560v2-USB System Trace Emulator">
                <instance XML_version="1.2" href="drivers/tixds560debugssm.xml" id="drivers" xml="tixds560debugssm.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds560cs_dap.xml" id="drivers" xml="tixds560cs_dap.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds560cortexR.xml" id="drivers" xml="tixds560cortexR.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds560cortexM.xml" id="drivers" xml="tixds560cortexM.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds560etbcs.xml" id="drivers" xml="tixds560etbcs.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds560icepick_m.xml" id="drivers" xml="tixds560icepick_m.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds560c66xx.xml" id="drivers" xml="tixds560c66xx.xml" xmlpath="drivers"/>
                <platform XML_version="1.2" id="platform_0">
                    <instance XML_version="1.2" desc="AWR2X44P" href="devices/awr2x44p.xml" id="AWR2X44P" xml="awr2x44p.xml" xmlpath="devices"/>
                </platform>
            </connection>
        </configuration>
    </configurations>

    Best Regards,
    Seung.

  • Thank you. I see you are using AWR2X44P.

    However:

    While debugging, when selecting a core in the RUNNING state, if the variable shown in the WATCH window belongs to that core, in CCS v12.x.x the variable’s value was updated in real time (especially for the DSP, the variable values were periodically refreshed).

    It was mentioned that CCS 12.x did not have any issue. However, AWR2X44P was not a supported device in CCS 12.x.x. Was the target configuration you provided above used with CCS 12.x or did you use a different one with a different device specified?

  • It was mentioned that CCS 12.x did not have any issue. However, AWR2X44P was not a supported device in CCS 12.x.x. Was the target configuration you provided above used with CCS 12.x or did you use a different one with a different device specified?

    Or perhaps you installed some additional device support package over CCS 12.x?

  • Hello Ki,

    Yes, that's correct. I'm using the device support package included in the mmWave SDK v4.7.0.1.

    Regards,
    Seung.

  • I see. I ended up following the steps in this post:

     RE: AWR2944P: supported CCS example project 

    I didn't see the CSP in 4.7.1.0 but I did see it in 4.7.0.1.

    The awr2x44p.xml file in the CSP seems nearly identical as the one in CCS 20.2.0.

    However CCS 12.x real-time memory access worked but 20.2.0 did not. 

    Can you share the awr2x44p.xml file you are using with CCS 12 where it is working? The location is:

    <CCS 12 INSTALL DIR>\ccs\ccs_base\common\targetdb\devices