TM4C1294NCPDT: connection fail with XDS110 FW

Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: AWR2243

Tool/software:

Dear Champs,

My customer is working on TIDA-0200047 Ref. B/D and faced an issue while trying to download XDS110 FW on TM4C as below.

Could you please check why 'initializing flash programming' error occurred in below?

After this, they faced another error in below when they tried to load 'boot_loader.axf' file.

Could you please let me know what is the issue?

Let me explain more details why they faced this errors in TM4C used as XDS110 debugger integrated in TIDA-0200047 Ref. B/D.

At the first time, they found 'Stellaris Device Firmware Upgrade' in the PC device manger window as below when they connected TIDA-0200047 Ref. B/D.

So, they tried to update FW of TM4C using below tool, but they have not seen even above 'Stellaris Device Firmware Upgrade' in their PC device mananger after pressing 'update' in below 'LM Flash Programmer' tool.

So, there is no way to update XDS110 FW through USB, they tried to connect CCS but failed as above.

Could you please check above errors and how they can update XDS110 FW on XDS110 TM4C?

Thanks and Best Regards,

SI.

  • Hello,

    My customer is working on TIDA-0200047 Ref. B/D

    I assume they have a custom board based on the AWR2243 with an onboard XDS110 designed in based off the TM4C1294NCPDT. Is that correct? If so, can they provide some schematic for the onboard XDS110 on the board?

    Thanks

    ki

  • Hi Ki,

    Yes. you are correct. you can find the schematic in below. It seems JTAG pins are not connected to TM4C and would like to check if there is any other way to flash XDS110 FW on TM4C.

    https://www.ti.com/lit/df/tidmb63/tidmb63.pdf?ts=1729559494799

    https://www.ti.com/tool/TIDA-020047?keyMatch=TIDA-0200047&tisearch=universal_search

    Thanks and Best Regards,

    SI.

  • Yes. you are correct. you can find the schematic in below. It seems JTAG pins are not connected to TM4C and would like to check if there is any other way to flash XDS110 FW on TM4C.

    Based on the screenshots on your original post, it looks like the customer was able to connect to the TM4C using code composer studio but just ran into some flashing issue with trying to flash the XDS110 firmware and bootloader. So I assume they have JTAG access to the TM4C. Can you explain what you mean by JTAG pins are not connected?

  • Hi Ki,

    The JTAG pins are connected to PA0 ~ PA5 of TM4C, but I think the JTAG pins of TM4C are PC0 ~ PC3 in below. (but, I'm not familar with TM4C.. ^^)

    Anyway, if TM4C was connected to CCS but ran into some flashing issue, is there any way to fix it or initialize it?

    When they tried to load FW as below, they failed to load it on TM4C.

    Thanks and Best Regards,

    SI.

  • Anyway, if TM4C was connected to CCS but ran into some flashing issue, is there any way to fix it or initialize it?

    The flash programmer was unable to access the required flash address. I don't know what the root cause of it is.

    The JTAG pins are connected to PA0 ~ PA5 of TM4C, but I think the JTAG pins of TM4C are PC0 ~ PC3 in below. (but, I'm not familar with TM4C.. ^^)

    This is a bit beyond my area of expertise. Hardware support of onboard XDS110 design is provided by the device experts for the device on the board. I will bring it to their attention.

  • Hi Sung,

    Can you check the "Flashing the bootloader" section of the following URL? 

    XDS110 Debug Probe

    Especially the "Option 1: Flash the bootloader from the command-line using the XDSDFU utility".

    Best regards,

    Ming

  • Hi Ming,

    Yes. it was already checked, but connection failed even when they tried to connect GND as below.

    Is there any other method to flash FW?

    Thanks and Best Regards,

    SI.

  • Hi Sung-IL,

    Unfortunately, I do not know any other ways to solve this issue. I will assign this thread to SDTO for further help.

    Best regards,

    Ming 

  • Sung-IL

    I would like to confirm the current situation.

    It looked like in the past the customer was able to detect the XDS110 and start CCS and connect to the Tiva device and the issue was with some programming and verification errors when trying to flash the firmware and bootloader.

    But then after trying to use the LM FLash programmer and use the update feature (which they should not have done since it is for updating ICDI firmware and NOT XDS110 firmware), the XDS110 is no longer detected at all so they can no longer even connect CCS to the Tiva device.

    Is this correct? This is what I need confirmation for.

    If so, I think that by trying to flash the ICDI software, it corrupted the XDS110 software on the device. Looks like the customer tried forcing the device into DFU mode by grounding pin 97 of the Tiva device then connecting the USB cable to the Tiva then disconnecting pin 97 a few seconds afterwards. This is the correct procedure but it looks like in the customer case it did not work. 

  • Hi Ki,

    All your understanding is right.

    Thanks and Best Regards,

    SI.

  • Please see the below screenshot you posted earlier:

    This looks like the customer has JTAG access to the onboard XDS110 Tiva chip using an external XDS110 JTAG probe. This is a direct JTAG access (JTAG header on the board or otherwise) and not using the USB port connect that xdsdfu uses. This would allow you to connect the CCS debugger to it. This step no longer works after the failed ICDI firmware update? What happens when they try to connect the CCS debugger like they did in the screenshot above?