TM4C1294KCPDT: Debugging daisy chained dual Tiva C

Oleg Kobrin

Part Number: TM4C1294KCPDT
Other Parts Discussed in Thread: UNIFLASH

Hello!

In my project I have 2 TM4C129 MCUs and daisy chained JTAG connection.

So I am trying just to create a project with empty main() functions and debug it. When I am trying to debug second MCU, I got errors:

CORTEX_M4_0: GEL Output: 
Memory Map Initialization Complete
CORTEX_M4_1: GEL Output: 
Memory Map Initialization Complete
CORTEX_M4_1: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x244: (Error -1066 @ 0x244) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.3.0.00042) 
CORTEX_M4_1: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x248: (Error -1066 @ 0x248) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.3.0.00042) 
CORTEX_M4_1: Trouble Removing Breakpoint with the Action "Finish Auto Run" at 0x248: (Error -2044 @ 0x248) Internal error: Requested breakpoint does not exist. Restart the application. If error persists, please report the error. (Emulation package 9.3.0.00042)

No such errors for first MCU. Code seems to be loaded to second MCU OK, and if I debug it with F5 key I am able to get to main(), but F6 key produses an error. My target configuration is:

And its source:

<?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 XDS100v2 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds100v2cs_dap.xml" id="drivers" xml="tixds100v2cs_dap.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100v2cortexM.xml" id="drivers" xml="tixds100v2cortexM.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="Tiva TM4C1294KCPDT_0" href="devices/tm4c1294kcpdt.xml" id="Tiva TM4C1294KCPDT_0" xml="tm4c1294kcpdt.xml" xmlpath="devices"/>
            <instance XML_version="1.2" desc="Tiva TM4C1294KCPDT_1" href="devices/tm4c1294kcpdt.xml" id="Tiva TM4C1294KCPDT_1" xml="tm4c1294kcpdt.xml" xmlpath="devices"/>
                <device HW_revision="1" XML_version="1.2" description="" id="Tiva TM4C1294KCPDT_1" partnum="TM4C1294KCPDT" simulation="no">
                    <router HW_revision="1.0" XML_version="1.2" desc="CS_DAP_1" description="CS_DAP Router" id="CS_DAP_0" isa="CS_DAP">
                        <subpath desc="subpath_1" id="subpath_0">
                            <cpu HW_revision="1.0" XML_version="1.2" desc="CORTEX_M4_1" description="Cortex M4 CPU" deviceSim="false" id="CORTEX_M4_0" isa="CORTEX_M4">
                                <property Type="numericfield" Value="0x0" id="TraceDeviceId"/>
                            </cpu>
                        </subpath>
                    <property Type="numericfield" Value="0x0" id="DAP TAP ID"/>
                    </router>
                </device>
            </platform>
        </connection>
    </configuration>
</configurations>

Any suggestions?

over 4 years ago

0 Oleg Kobrin over 4 years ago

Expert 1890 points

Update: setting first MCU to bypass mode does not help.

Also I successfully programmed bot MCUs with MAC-address using UniFlash classic.

0 Bob Crosby over 4 years ago

TI__Guru 72500 points

I don't have hardware with two TM4C129 devices on a single JTAG chain, but when I build the configuration file for an XDS200 I get this:

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/908/XDS200DualTM4C129.ccxml

0 Oleg Kobrin over 4 years ago in reply to Bob Crosby

Expert 1890 points

Mine is the same, as you see.

But second core shows errors.

Anyway, it is very easy to reproduce the configuration using 2 launchpads, like it is done here: https://e2e.ti.com/support/microcontrollers/other-microcontrollers-group/other/f/other-microcontrollers-forum/620529/ccs-tm4c123gh6pm-jtag-daisy-chain-debugging-using-ek-tm4c123gxl-icdi-interface

0 Bob Crosby over 4 years ago in reply to Oleg Kobrin

TI__Guru 72500 points

I am transferring your thread to the tools group.

0 Ki over 4 years ago in reply to Oleg Kobrin

TI__Guru**** 464431 points

Hi Oleg,

I'll need to try to replicate your environment and see if I can get it to work. It may take a day or two as I need to go into the office look for the necessary hardware.

Two questions:

1. What CCS version are you using?

2. What host OS are you using?

Thanks

0 Oleg Kobrin over 4 years ago in reply to Ki

Expert 1890 points

Hello!

Thank you for your answer.

1. Tryed with CCS 9.3 and 10.2, XDS100v2 and XDS100v3, same result.

2. Windows 10

Also, searching for the error message I found very similar cases, unfortunately without any solution suggested: case 1 and case 2, it may help. As they said, issue can be reproduced with xds100 or xds200 and ccs v6 to v10, both cases along with mine are with TM4C129x parts.

0 Ki over 4 years ago in reply to Oleg Kobrin

TI__Guru**** 464431 points

Thanks. I will try to set up a similar environment. I am unable to access the office today but I plan on going in tomorrow.

0 Ki over 4 years ago in reply to Ki

TI__Guru**** 464431 points

I was able to secure two 1294 launchpads and in the process of setting things up. I'll keep you posted of my progress. Thanks for your patience.

0 Oleg Kobrin over 4 years ago in reply to Ki

Expert 1890 points

Good morning! Any news?

0 Ki over 4 years ago in reply to Oleg Kobrin

TI__Guru**** 464431 points

Not yet. Sorry for the delay. I will try to get something set up this weekend

0 Ki over 4 years ago in reply to Ki

TI__Guru**** 464431 points

I have two TM4C1294XL LaunchPads and tried daisy chaining them but was unsuccessful. I've never tried with these launchpads so I may be missing something here. I will need to pull in some help from the device experts...

0 Oleg Kobrin over 4 years ago in reply to Ki

Expert 1890 points

As I check TM4C1294 lanuchpad documentation, I see there is ICDI interface with TM4C123 MCU. So you need depopulate jumpers connecting ICDI to JTAG of TM4C1294 and populate the connector for external JTAG.

0 Ki over 4 years ago in reply to Oleg Kobrin

TI__Guru**** 464431 points

This issue is being discussed via private e2e discussion

0 Ki over 4 years ago in reply to Ki

TI__Guru**** 464431 points

For other following this thread, please see the below post for further details:

https://e2e.ti.com/support/microcontrollers/other-microcontrollers-group/other/f/other-microcontrollers-forum/1003595/tm4c1294kcpdt-debugging-daisy-chained-dual-tm4c1294---emulation-pack-bug/3716203#3716203

0 Genatco over 4 years ago in reply to Oleg Kobrin

Guru 55913 points

Hi Oleg,

Windows can launch multiple sessions of CCS debug, each one in protected memory space. Why not launch two CCS debugs to watch both MCU side by side?

0 Ki over 4 years ago in reply to Genatco

TI__Guru**** 464431 points

Hi Oleg,

Genatco said:
Windows can launch multiple sessions of CCS debug, each one in protected memory space. Why not launch two CCS debugs to watch both MCU side by side?

You mentioned that you daisy chained two TM4C129 MCUs. Is this a custom board with both MCUs on the same board on the same scan chain or did you daisy chain two TM4C1294 launchpads?

If the latter, then the workaround suggested by GI seems like a viable workaround.

Thanks

0 Oleg Kobrin over 4 years ago in reply to Ki

Expert 1890 points

This is a custom board with both MCUs on same board on tha same scan chain. This is done to simplify later production of the board, as at production facility they should use only one connector to flash both MCUs. Of course for development, I can make another board with 2 JTAG connectors, but it is additional expenses and time.

0 Ki over 4 years ago in reply to Oleg Kobrin

TI__Guru**** 464431 points

Oleg, thanks for confirming. I suspected as much. I will make sure the priority of this bug is made known to the engineers.

0 Genatco over 4 years ago in reply to Oleg Kobrin

Guru 55913 points

Oleg Kobrin said:
Of course for development, I can make another board with 2 JTAG connectors, but it is additional expenses and time.

Perhaps for simplicity sake and if both firmware are different it might be worth the expense to place JTAG header pads on both MCU. Then there is DAP unlocking to consider, will it also have same difficulty?

+1 Ki over 4 years ago in reply to Oleg Kobrin

TI__Guru**** 464431 points

Oleg,

One update: The issue seems to be related to the ctools components in the debugger. You can try disabling it. To do so, go to <CCS INSTALL DIR>\ccs\ccs_base\emulation\analysis\bin and rename ctools.dll. This will disable ctools.

When I do the above, I can set hardware breakpoints for the second CPU also. However, it seems to cause the below error to constantly appear every time a breakpoint is hit or for each single step:

CORTEX_M4_1: Trouble Reading Register SP: (Error -2030 @ 0xF) Attempted to access an unknown or invalid register. Confirm the register is valid and accessible, and retry the operation. (Emulation package 9.3.0.00058)

This will happen for both cores. Not sure why there is an issue reading SP as I can access it just fine via Registers view. In any case it doesn't seem to impact the debugging functionality (though the constant message can get annoying).

You can use the above as workaround until we properly fix the ctools issue.

Thanks

0 Genatco over 4 years ago in reply to Ki

Guru 55913 points

Ki you always amaze me with your intuitive approach to such issues. Keep up the great work with CCS we all appreciate your efforts

0 Oleg Kobrin over 4 years ago in reply to Ki

Expert 1890 points

One more note: just tryed with linux-based CCS, same issue.

0 Oleg Kobrin over 4 years ago in reply to Oleg Kobrin

Expert 1890 points

This workaround works, but CIO does not. Not the big problem.

0 Ki over 4 years ago in reply to Oleg Kobrin

TI__Guru**** 464431 points

Oleg Kobrin said:
This workaround works, but CIO does not. Not the big problem.

Yes that looks to be another limitation with this workaround.

Arm-based microcontrollers

Arm-based microcontrollers forum

TM4C1294KCPDT: Debugging daisy chained dual Tiva C