This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
this is my first post, so i hope i'm doing it all right. I kept reading the forum, but no one seems to have the exact same problem.
I use the Delfino F28377D with the Sauris JTAG Programmer (SAU510-USB, IsoPlus2) and it is no problem to load a program into the RAM. When I change the .cmd file to Flash, it won't work anymore and it says the following error:
C28xx_CPU1: File Loader: Verification failed: Values at address 0x0000000000082000 do not match Please verify target memory and memory map.
We have a development kit, which I tried as well to program with the extern JTAG programmer, and there is no problem with the same selections. We also have another custom board and it works out fine. So we found out (at least we think) the problem is with the TMS and the TMX... the TMX works (which is btw on the development board and on one of our custom boards) and the two TMS don't work.
I didn't even know about the TMX320 and it even seems to be the "not so perfect, pre-version", so I don't really understand what's wrong.
What I tried so far:
-Change the JTAG Settings (clock speed)
-Checked and rechecked the Linkerfiles (Tried the TMS320F28377D and the F28377D)
-Looked at the Memory Browser (it says all 0xFFFF in the flash section)
-Tried to erase the Flash manually but it says: "Target is not connected or does not support current Flash operation".
-I have a "Hello World" program, so it can't be this one either
-I checked the Flash sections of the hardware in the Datasheet and it is the same one as the one declared in the linkerfile.
-I tried the Uniflash for "external flashing" but it doesn't have a Sauris support. Also I think this is no solution, since I have a full license CCS version.
There was one person who had a similar problem, but he had some hardware problems with the reset pin and he never wrote back, so I couldn't check on his solution.
I hope I provided all the information needed, thanks for your help in advance!
My CodeComposer Version: 6.1.0.00104
Please see this related thread that I believe explains the behavior you are seeing with CCS 6.1.0. The specific posts of interest within the thread are this and this.
To solve the issue, you can either upgrade to the latest version of CCS v6.2 (http://processors.wiki.ti.com/index.php/Download_CCS) or update the C2000 device support package in your existing installation, as mentioned in the above post. I would recommend updating CCS itself so you can avail of all the other bug fixes and enhancements in the newer version. You can even have your current version and the latest version of CCS installed on the same machine as long as they are in two different directories.