TM4C129ENCZAD: Arm-based microcontrollers forum

yousuke nasu

Part Number: TM4C129ENCZAD

When the USB is connected to the board on which TM4C129ENCZAD is mounted, the PC will look like the image below.

Just to confirm, when I asked the question last time, it was TM4C129ENCZAD
bootloader and firmware using JTAG
There was a flash.
Is there any problem with writing to TM4C129ENCZAD with this image?

Is there a way to confirm that the XDS110 debug probe and TM4C129ENCZAD are connected via JTAG?
I read the user guide, but I didn't understand it well, so I would like to know if there is a way.

over 2 years ago

0 Charles Tsai over 2 years ago

TI__Guru**** 182636 points

Hi,

yousuke nasu said:
When the USB is connected to the board on which TM4C129ENCZAD is mounted, the PC will look like the image below.

When you use TM4C129ENCZAD the first time, the flash is empty. However, there is a USB bootloader stored in the ROM memory. The ROM-based USB bootloader will enumerate as a Stellaris DFU device. I can confirm that on my own LaunchPad setup. When the flash is fully erased, I will see the Stellaris DFU device on Device Manager.

yousuke nasu said:
Just to confirm, when I asked the question last time, it was TM4C129ENCZAD
bootloader and firmware using JTAG
There was a flash.
Is there any problem with writing to TM4C129ENCZAD with this image?

The boot_loader.bin file is a flash-based USB bootloader that can be loaded via JTAG. The firmware_3.0.0.15.bin is the XDS110 firmware that needs to be loaded through the USB device port.

I'm not an expert on XDS110 and I have forwarded your other thread below to our XDS experts.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1185252/tm4c129enczad-what-to-do-when-the-device-is-not-found