Memory access problems using XDS100v2

Jonathan,

For CCSv4:
When you create your target configuration file,
1. select the Texas Instruments XDS100v1 USB Emulator connection, and then select the TMS3206748 for Device.
(OR)
2. select the Texas Instruments XDS100v2 USB Emulator Connection for XDS100 version 2, and then select TMS320C6748 for Device.
If you use DBGJTAG to test the JTAG scan path, it will look like the below, with a zero-bit scan path on both IR and DR.
C:\ccsv4\ccsv4\common\uscif>dbgjtag

For CCSv5:

Ffollow the above same method to create a target configuration file.
Here you can find a useful "Test Connection" button at the target configuration editor.
Click on the Test Connection, this executes various low-level JTAG tests on the configured connection.

Please see this wiki articles will help you better to undersatnd the target connection and also debug the connection,

http://processors.wiki.ti.com/index.php/BIOS_C6SDK_2.0_Getting_Started_Guide
http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

Hey Pubesh,

For your info - I'm using the most recent version of CCS. 

Unfortunately I've already tried all of these measures... and likely read 30 or more forums on this website looking for a solution. When I try to go the Test Connection like you mention above after making a custom configuration file I receive an error saying "Device Disconnected: Error Unknown"

I honestly feel that there is some mundane step or setting I'm missing and I just have had no success as of yet. 

Please let me know if there is anything else I can do in your opinion. 

Thanks again for all your help. 

Which boot mode are you using? Emulation boot is suggested for JTAG debugging. Other boot modes may result in code execution that "locks" out the JTAG. I have no idea exactly the processor is doing but it stops responding to the JTAG. Emulation boot is supposed to execute JTAG friendly infinite loop code.

Jonathan - Sounds like the application is jumping to a program address which is probably reserved or doesn't exist for your target. Check the address range used by your program. Make sure you used a correct linker command file and the debugger memory map is set up properly. Also check Norman's suggestion about the boot mode.

Thanks

ki

Hey Ki,

Thanks for your response... I believe you're correct. In my project I'm using the C6748.cmd file which is part of CCSv5.5 and I wasn't using that before, unfortunately I get the same result. 

I have also imported .gel files associated with my TMS320C6748 board, and ran those memory map scripts to either set-up the memory map or clear the memory. 

I do not know anything about boot modes or how to change them, maybe you can enlighten me on this?

After all of this I'm still having problems though. Anymore help would be greatly appreciated. 

Thanks 

Where did you get the board from? Is it the kit from LogicPD?

Ki, 

I got the board along with the JTAG emulator which is a TI branded XDS100v2 directly from Texas Instruments. 

There are several flavors of the C6748 board available. Could you provide a web link which has some info on the board?

Thanks

Hey Ki, 

http://processors.wiki.ti.com/index.php/L138/C6748_Development_Kit_(LCDK)

and

http://www.ti.com/lit/ds/symlink/tms320c6748.pdf

Thanks

If you haven't figured it out already, the boot mode on the LCDK board is controlled by SW1 DIP switch. The switch bits SW1[4:1] are inverted levels of BOOT[4:1]. Physically, the switch is oriented from left to right as LSb to MSb to make it more confusing.
SW1[0:7] SW1[7:0] BOOT[7:0]
01010000 00001010 00010100 UART
01110000 00001110 00010000 NAND
00000000 00000000 00011110 Emulation Debug
The UART and NAND settings are in the LCDK board doc. The other modes you have to string together from info in the schematic and the processor manual.

EDIT:
Oops. Misread my notes. The board is wired to swap ends. Not the switch SW1[1]=BOOT[4], SW1[2]=BOOT[3], SW1[3]=BOOT[2], SW1[4]=BOOT[3].
SW1[8:1] BOOT[7:0]
00000101 00010100 UART
00000111 00010000 NAND
00000000 00011110 Emulation Debug

Anyhow, set SW1 to all 0 for emulation debug. Just remember what it was before you changed it.

EDIT:
Oops again. One last try.
SW1[8:1] BOOT[7:0]
00001010 00010100 UART
00001110 00010000 NAND
00000000 00011110 Emulation Debug