CCS/TMS320F28069M: How to upload a HEX file to the MCU?

John,

I get this error when I try to verify the image:

But I can successfully load the image and it works!

Hi John,

I am able to use UniFlash easily to flash the hex file but my customer is getting the below error on our custom board:

John,

Here is what I got:

It is reporting errors on all the the microsoft runtime DLLs.  The capture should look something like this.

Instead for all of the API-MS-WIN-CORE dlls they have an error loading them.  Are they running Windows 8 or WIndows 10?  I did some searches and it looks like Dependency Walker is not able to figure out some indirection on loading these dlls with Windows 8/10.  Works fine for me on Windows 7.

We may have to try using Process Monitor.

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

Click on the filter button and add this filter.  Operation in the drop down, then is in the second and load image as the text.  Click on the Add button then click ok

Then try running UniFlash and lets see if there are any failures.

John

John,

I guess they fixed the driver issue but now they're getting this error:

We followed this schematic for JTAG connector:

John,
That's exactly what i'm going to do. since they are not here in the U.S., it takes a little time for me to troubleshoot.
I sent them LUANCHXL-F28069 so they can verify if the software/machine works fine. Then I'm going to send them a simple CCS project to test their programmer (XDS100V2). I guess with these two methods I will be able to find where the problem is.

The problem is I've never used CCS so I have to learn how to make a simple project for F28069 (let's say blink the LEDs) then send it over so they can use it.

John,

The customer used a LAUNCHXL-F28069 and tested the UniFlash and it worked fine which means the emulator and/or the JTAG connection on our custom board doesn't function properly.

This is the schematic we're using for JTAG in which we connect 13,14 and 5 to board VCC (3.3V). 

I know that TDIS pin at the emulator side should be grounded at the target side so the emulator can use this pin to detect when the target is disconnected but I guess the problem is that the emulator can't see it is connected because the board's ground is different from emulator's ground since the emulator is connected to the computer through the USB cable. Here is the error we get:

Ki,

Sure, I'll ask them to run the JTAG test. But before that, this is what they get while trying to program: