CCS4 +BlackHawkUSB2.0 +TMS320C6713

Kamil,

The memory address the message refers to is internal, therefore neither the linker command file nor the loader should have problems in loading it.

The only thing I can think of is that this issue may be a consequence of improper initialization performed by the GEL file (included by default with the selected DSK6713 configuration). Just as a test can you open the Advanced tab of the target configuration file you created and remove the reference to the GEL file?

Unfortunately I don't have a board with me right now, but I can do a test on Monday.

Cheers,

Rafael

Rafael,

This was one of the first modifications I tried. Unfortunately removing path to the gel file does not give expected results. Have a nice weekend.

Best,

Kamil

Kamil,

I was able to connect to my C6713B DSK board, however I only have a BH-USB-560m emulator and it uses a different driver than yours. 

I've seen in the past some cases where the emulator connected successfully to the target but its operation was flaky (program loads failed, breakpoints were not correctly set, execution lost track after running for a few cycles). This was usually caused by connection speed too high or noise in the JTAG wiring. Just FYI, I managed to connect and run programs even with the JTAG speed fixed in 35MHz (the highest for the emulator/device).

In addition to that, I would test a few other things:

- Although this emulator does not allow reducing the JTAG speed (BlackHawk has an entry about this on their FAQ), I would try to use the most conservative option possible. In the target editor screen, click on tab Advanced and enable the Thorough Poll Mode.

- You can try to create a target configuration using the core only. In the target configuration editor, select the tab Advanced and remove the DSK6713_0 from the configuration. Click on Add, select the tab CPUs and select C671x. This is the most basic target configuration as it only has the core device configurations (this also worked for my board).

Apart from that I can only suggest the page below that has additional details on how to debug the JTAG connection using the command-line utilites supplied with CCSv4.

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

Hope this helps,

Rafael

Rafael, Kamil,

The message that you are seeing comes when you try to load the program, correct?  If this is the case, I don't think this has anything to do with the emulator.  When we load an application with data verification on, we simply write the data out to memory, and then read the memory to ensure that all of the correct values are written.

You might try doing a memory fill on this section and then verifying that all of the values in that section get updated to the value you wrote.  CCS is basically saying that the value that it read back is not the same as what it tried to write.

Regards,

Dan

Dan, Rafael,

The message comes when I try to load the program, that's correct. I also checked emulator with tools provided in ccs and emulator is ok. Furtheremore I have tested it on the same board with c6455 dsp's, and everything is fine.

According to the Dan's suggestion:

1. I can fill memory by some template value. Values are stored in the cpu correctly. After I read it to a file data contained in it are also correct.

2. After loading some .bin file (with random data) to the cpu's memory values are not correct (a lot of differences). Doesn't matter if data are assumed to be 8-bit or 32-bit organized. Similarly CCS cannot load file to the cpu's memory correctly. I tried the same with c6455 (on the same custom board) and everything is done perfectly (random bin files are loaded to and from memory, and files are compared 1:1 without any errors). Thus I don't expect the emulator is defective.

3. I can load the cpu's mem via HPI. Values that are read through the emulator afterthat are correct.

4. I can use the emulator without any problems with DSK6713.

According to the Rafael's suggestion:

1. I modified target configuration file by removing the path to gel file and removing DSK6713_0 branch as well. In all cases I obtain similar results, as described above.

Any further suggestions ?

Best, Kamil

Today I updated CCS (automatic updates), but I still have same problems. Do You have any suggestion to solve described problem?