TMS570 MCU Development Kit Debug Problem

Martin,

You are using a very old version of Code Composer Studio. (4.2.3)

I will highly recommend to install the latest version (V5.5) from the following download page:

http://processors.wiki.ti.com/index.php/Download_CCS

Them let me know the result.

Thank you for quickly reply. 

I installed the newest version of CCS and now I get this error:

Error connecting to the target:
(Error -151 @ 0x0)
One of the FTDI driver functions used during
the connect returned bad status or an error.
The cause may one or more of: invalid emulator serial number,
blank emulator EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the emulator can be located.
(Emulation package 5.1.232.0)

Do you have another idea what is wrong with my board?

Gratefulness

Martin

Martin,

Can you check the following:

Power off your board and disconnect the usb cable from your PC.
Switch on the board and then connect the USB cable between the board and the PC.
Open the Control Panel\All Control Panel Items\System\Device Manager and check  underneath Universal Serial Bus controllers for the 2 following entries:

TI XDS100 Channel A
TI XDS100 Channel B

Here is a screen shot:

Please let me know the result.

I have done that.

But when i connect the USB cable to my PC, this appeared.

USB Serial Converter A

USB Serial Converter B

My Screenshot:

Could there anything be wrong with the drivers or on the board? On the pc I had reinstalled all driver. 

Thank you for your support.

Greets 

Martin,

Can you tell me the kind of board you are using. (a picture will be best)

Apparently, the PC does not recognize the board correctly. This could be a board problem.

I've attached an application that can read the way the board is configured.
Can you install and try this application. (Application from FTDI)

Just execute FTPROG with your board connected to your PC.
Click on Device->Scan and Parse.
This will read the content of a EEPROM on the board.

What is the Vendor ID:

What is the Product ID:

1207.FT_Prog_v2.8.2.0.zip

The Vendor ID: 0x0403

The Product ID: 0x6010

It looks like there is an problem on the board, right?T

If you want a picture of the board. Or what did you mean with "kind of board"?

Thanks for your time

Greets

Martin,

Thank you for these information.

The EEPROM is blank and this is the reason of your problem.
This explains why the board is recognized as 2 Serial port. This is the default for the FTDI chip when the EEPROM is blank.
In an earlier post, you said that the board was working, and at one point stops working.
Do you remember anything you tried on this board that could have caused the EEPROM to be erased?
Have you tried the Safety Demo Software?

I'm right now working on the same board and I will send you the configuration file to be used to re-program the EEPROM. You will have to use the FTPROG software to do so.

Hey,

at the time the board was working, i configured a few timer. It was able to use the debug mode witthour problems. I have no idea what I have done that the EEPROM doesn't work. 

Trying the Safety Demo Software is without success.

I'm glad to hear that maybe you have the answer for my question.

The Safety Demo Software is checking the board ID to figure out which options are available.
If the board ID is not recognized, the application will ask you to select from list the board you are using.
This board ID is stored in the FTDI EEPROM. So to program the new board ID, the EEPROM has first to be erased and than re-programmed. If this process fails, it could result in a blank EEPROM.

Do you remember the Safety Demo Software asking for a new board ID?

Hey,

the device manager has now the right identifier. 

TI XDS100 Channel A

TI XDS200 Channel B

But now there is an other error when I debug my project:

Error connecting to the target:
(Error -1204 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.1.232.0)

When I run the Safety Demo I get this error:

nowFlash has encountered an error while erasing the device. Please ensure that the device is properly connected and then try running the demo again.
nowFlash Error #: 199
Please see nowFlash user guide for more information.

Martin,

The Safety Demo is not suppose to run on this board.

Are you trying to connect with CCS5.5?
If this is the case, I will guide you to create a new Target Configuration for your board.

1] In CCS select View->Target Configuration
2] Right click in Target Configuration windows and select "New Target Configuration"
3] Assign a name to this new target configuration (ex: MCBTMS570_xds100.ccxml)
4] Select the connection as: Texas Instruments XDS100v2 USB Enulator.
5] Select the Board or Device as: TMS570LS20216ZWT.
6] Save the configuration.
7] Click on Test Connection. I've attached the log file on my board. 2543.Test Connection.txt
8] If there is no error than continue to 9.
9] In Target Configuration, right click on your new configuration and select :Launch Selected Configuration.
10] CCS will switch to :CCS Debug and a window named Debug should be visible.
11] Right click on Texas Instruments XDS100v2USB Emulator_0 and select: Show all Core.
12] Expand the Non Debuggable Devices.
13] Right click on Texas Instruments XDS100v2USB Emulator_0/Icepick (Disconnected) and select "Connect Target"
14] Icepick should be connected now.
15] Do the same with Texas Instruments XDS100v2USB Emulator_0/Dap (Disconnected)
16] Dap should be connected now.
17] Do the same with Texas Instruments XDS100v2USB Emulator_0/CortexR4(Disconnected)
18] CortexR4 should be connected now. You are ready to debug.

Please have a try with this procedure and let me know if something is not going as supposed.

Hey,

Texas Instruments XDS100v2USB Emulator_0/Icepick (Connected)

 Texas Instruments XDS100v2USB Emulator_0/Dap (Connected)

Texas Instruments XDS100v2USB Emulator_0/CortexR4 i get a new error:

CortexR4: Error connecting to the target: (Error -1141 @ 0x0) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.232.0)

When I reset the device, I get this error:

Error connecting to the target:
(Error -1265 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.
(Emulation package 5.1.232.0)

This is the Test Connection file:

6406.Connection Test.txt

Ok,

We are getting close.

Go back in the Target Configuration window and double click your target configuration name.
Select Advance Setup and click on "Target Configuration"
You should see a tree view of your target configuration.
Right Click on CortexR4 and check in Cpu Properties the value of: Address. It should be 0x80001000
If it is not the case, change the value and save your target.
You can now try to connect again.

Please if the value is not 0x80001000 let me know the value.

This log file is perfect.
The hardware connection to the board is working fine (JTAG)

The value is the same

Martin,

There is one last thing we can do.
1] After connecting the DAP, select "Texas Instruments XDS100v2 USB Emulator_0/Dap.
2] Select View->Memory Browser to open a memory window.
3] In the memory window enter 0x0000 and Go.
4] You should see the content of the Flash. Is it erased? (0xffff_ffff every where)
5] Enter a new base address as 0xFFFFFF00 (System Register)
6] Are you able to read something?
7] At address 0xFFFFFFE0 you should read 0x00004000
8] Write 0x0 at this location.
9] Try to connect the CortexR4.

If this is not working, I can set up a Webex session so I can have a look to your setup.
Is it something possible?

I don't have 0xffff_ffff in the memory Browser. I have 0xBAD0BAD0 everywhere

Also at address 0xFFFFFFE0 I have 0xBAD0BAD0

When you power cycle the board, can you see any display on the LCD?

I will be available for a webex session at 10:00am US central time.
If you are ok I can send you a link to join a remote session so I can have a look.
Please let me know if you want me to do so.
I'm also sending you a "friend request" so we can exchange privately phone numbers.

Hi Jean,

I have a very similar issue with the DRV8301-LS12-KIT. Receiving the following errors when I try to debug:

CortexR4: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.507.2)
CortexR4: Unable to determine target status after 20 attempts
CortexR4: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
Texas Instruments XDS100v2 USB Emulator_0/CortexR4 : Target must be connected before loading program.

I am using the latest CCSv6, Motorware, etc. Basically, I cannot erase the flash. Thank you very much.

Dear Mr. Jean, 

I have gone through the procedure step by step as u suggested above still I am not able to find the error. Could you please suggest me ?? 

Regards,

Aniketh chepuri.

Aniketh,

Can you create a new post and link this long thread to it?

This actual thread is really long and closed.