Other Parts Discussed in Thread: TMS320VC5509A
I am using TMS320VC5509A in my application and have recently moved from v4.3.6 to v4.3.7 of CGT. The code needs to flashed to the target system so am using hex55.exe to created boot table. Since migrating to v4.3.7 the target will no longer boot successfully as it had been doing with v4.3.6. Made .out file using the v4.3.7 compiler as part of debug process, then used v4.3.6 and v4.3.7 of hex55. Result was that using v4.3.7 of hex55 is creating the problem.
I created -ascil version of boot table so I could compare v4.3.6 and v4.3.7 outputs of hex55. The .cmd file for hex55 is configuring registers prior to loading code/data. The v4.3.7 boot table is missing most of the register configuration statements. I am attaching .out, .map, .cmd for hex55, ascii versions of boot table for both v4.3.6 and 4.3.7 and an excel spreadsheet that analyzes the contents of the boot tables to show the missing register configuration statements.
The .cmd for hex55 has multiple -delay statements which seem to causing problems for the v4.3.7 hex55. Has there been a change in method of defining register configurations and delay counts?
Regards.