TM4C1230C3PM: Flash a .hex file to TM4C1230C3PM

mauro guiotto

Part Number: TM4C1230C3PM
Other Parts Discussed in Thread: UNIFLASH, EK-TM4C1294XL, EK-TM4C123GXL

Tool/software:

Hello,

I just need to flash a .hex file.

I'm trying to flash the TM4C1230C3PMI microcontroller using

code composer studio v10.4 and xds200 debug probe.

In target configuration I manage to select the correct debug probe

 and microcontroller but when I do the connection test I get the following error:

I checked the connections between micro and programmer and they all

seem correct. As an interface I use JTAG and as an adapter to the programmer I use the

20eCTI-20tARM. However, using the oscilloscope I don't see any activity on the signals coming out of the programmer. I therefore have the doubt that there are some particular parameters or settings to make.

Alternatively, is there any other software or method to use with the XDS200 probe to flash a .hex file in TM4C1230C3PMI ?

3 months ago

0 Charles Tsai 3 months ago

TI__Guru**** 184346 points

Hi,

I want to know if your problem is related to XDS200 or the .hex file. Can do you the below experiments:

- Load your .hex using Unilfash, not CCS along with XDS200. Refer to this post answered by John. You should use CCS to load a .out file, not .hex file. To load a .hex, use Uniflash.

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/619006/ccs-tms320f28069m-how-to-upload-a-hex-file-to-the-mcu

- Load your .out file in CCS with XDS200. This will confirm if the problem is with the XDS200 or not. If you can load a simple .out file like a blinky.out then your XDS200 is fine.

- If you are having problem to even load a .out file then it is possible a problem with your PCB. If you have a EK-TM4C1294XL LaunchPad, it has a JTAG connector for external debug probe. The LaunchPad only has a 10-pin JTAG Arm header, not 20 pin. You can try to load the blinky.out with the XDS200 on the LaunchPad. If it is successful, it further confirms that the problem is related to your board, not XDS200. In CCS, you can do a scan-chain test. See below. First run on the EK-TM4C1294XL LaunchPad with the XDS200 attached to get a reference to compare with. Next, run on your custom board. If the scan-chain is broken, it traces to your board.

- Refer to Using TM4C12x Devices Over JTAG Interface app note for details on the difference between the various JTAG header pin out.

- Also go to section 6 for Debugging JTAG Connection Failure.

0 mauro guiotto 3 months ago in reply to Charles Tsai

Prodigy 10 points

Hi,

I installed Uniflash, xds200 is recognized by uniflash, I correctly selected the TM4C1230C3PMI micro.

I checked the pin connection I used ARM 20Pin, but got the following response ERROR -183

I tried the same procedure using EK-TM4C123GXL and got the same result.

Now I'll try to load a .out with ccs but these results dishearten me.

0 Charles Tsai 3 months ago in reply to mauro guiotto

TI__Guru**** 184346 points

mauro guiotto said:
I installed Uniflash, xds200 is recognized by uniflash, I correctly selected the TM4C1230C3PMI micro. I checked the pin connection I used ARM 20Pin, but got the following response ERROR -183

When you purchase the XDS200, doesn't come with Arm 10 pin adapter? Can you try the 10pin adapter?

mauro guiotto said:
I tried the same procedure using EK-TM4C123GXL and got the same result.

Please clarify. The EK-TM4C123GXL does not have a external JTAG header. How do you connect the XDS200 to the LaunchPad?

mauro guiotto said:
Now I'll try to load a .out with ccs but these results dishearten me.

Are you saying you can use XDS200 to load a .out file in CCS but not Uniflash?

You didn't answer me my earlier question. Let me repeat here again.

- Load your .out file in CCS with XDS200. This will confirm if the problem is with the XDS200 or not. If you can load a simple .out file like a blinky.out then your XDS200 is fine.

0 mauro guiotto 3 months ago in reply to Charles Tsai

Prodigy 10 points

Charles Tsai said:
When you purchase the XDS200, doesn't come with Arm 10 pin adapter? Can you try the 10pin adapter?

Yes I found the 10 pin adapter. I'll give this a try

Charles Tsai said:
Please clarify. The EK-TM4C123GXL does not have a external JTAG header. How do you connect the XDS200 to the LaunchPad?

page 14 of the link you suggested there is the pinout of the jtag connection. I used LaunchPad to try to program my device

Charles Tsai said:
Using TM4C12x Devices Over JTAG Interface

Charles Tsai said:
Are you saying you can use XDS200 to load a .out file in CCS but not Uniflash?

no, even with ccs I can't program any .out files

I also tried with the 10 pin adapter but the result is the same.
I'm using uniflash 9.0.0.5086 and XDS200 from blackhawk. 
Is there any advice on the drivers to follow? 
Are the drivers integrated with uniflash? 
I select "Texas Instruments XDS2xx USB Debug probe" from the connection list. Is this correct?

0 Charles Tsai 2 months ago in reply to Charles Tsai

TI__Guru**** 184346 points

HI,

I also tried with the 10 pin adapter but the result is the same.

Do you have any other TI boards with a 10pin JTAG header on it? It does not have to be EK-TM4C123GXL. I just wanted to know if your problem 
is related to the debug probe you have. 

I'm using uniflash 9.0.0.5086 and XDS200 from blackhawk. 

That should be fine. 

Is there any advice on the drivers to follow? 
Are the drivers integrated with uniflash? 

Follow this webpage if you need to update the driver and see if that resolves the problem. https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds200.html


I select "Texas Instruments XDS2xx USB Debug probe" from the connection list. Is this correct?

Correct.

Arm-based microcontrollers

Arm-based microcontrollers forum

TM4C1230C3PM: Flash a .hex file to TM4C1230C3PM