Part Number: TMS320F280025
Tool/software: TI C/C++ Compiler
Dear Champs,
I am asking this for our customer.
They are migrating codes from F28062 onto F280025.
When they use F280025 in EABI format, everything looks good. Also, RAM is initialized by the compiler as desired.
Because they want to main the same code base between F28062 and F280025, they want to use legacy COFF on F280025.
By COFF codes, they were writing own codes to initialize RAM, and they found the result were as desired by using SCI to dump out the RAM contents when it is on standalone mode.
However, when they use CCS to emulate and debug the same COFF codes, they found the RAM content were not correct. It seemed the RAM initialization code were run, but the content were not updated.
They used reset CPU->Script emu flash boot->Go Main->Run
They use legacy RTS library rather than the new EABI-based RTS.
CCS 10.1 is used here.
Questions:
1. Do we still support COFF on F28002x? Or is it because that we don't support COFF on F28002x so that the RAM initialization codes were not correctly run on CCS 10.1?
2. If we still support COFF on F28002x, do you have any comment why the result by standalone flash running and by CCS 10.1 were different.
If needed, I can send you the .cmd they use for COFF.
Wayne Huang
