Part Number:TMS320F28377D
Tool/software: Code Composer Studio
Hello.
I build the project in CCS 7.1.0 and generate a HEX-file using standart C2000 utility.
Here are first two lines of HEX-file:
%1263980008000048E6
%4E68C800082000C6080C0814081C083A0858087808A808B408D308E708F708070817083B084C08
Then I go to debug mode, load the same project to flash and look at Memory browser. I expect to see the same bytes which I see in HEX, but what I see is (16-bit HEX TI style):
0x00080000 0048 B1E6 FFFF FFFF FFFF FFFF FFFF FFFF
...
0x00082000 77C6 0008 780C 0008 7814 0008 781C 0008
0x00082008 783A 0008 7858 0008 7878 0008 78A8 0008
0x00082010 78B4 0008 78D3 0008 78E7 0008 78F7 0008
0x00082018 7907 0008 7917 0008 793B 0008 794C 0008
It looks like the data bytes from the HEX-file (48 E6 C6 08 0C 08...) are interleaved with 00 B1 77 00 78 00...
What is the origin of these unexpected bytes? How to consider them when doing Flash API programming/verifying?