Part Number: TMS320F28388D
Other Parts Discussed in Thread: UNIFLASH, C2000WARE
Tool/software:
Hi everyone,
I'm working on a project using the TMS320F28388D, and I'm currently debugging an issue when programming CPU2.
When I flash the application to CPU2 from Code Composer Studio (v12.8.0) and run it, the code immediately ends up in the illegal_isr. Looking at the disassembly, execution seems to hit an ITRAP0 opcode, which leads directly to the illegal ISR.
However, when I take the exact same .out file and program it using UniFlash (v8.7.0.4818), the application runs correctly and behaves as expected.
Some additional info:
-
CPU1 handles the boot process.
-
I'm using a custom linker command file (.cmd) for CPU2.
-
I'm using C2000Ware version 5.04.00.00.
-
CPU2 is loaded and started via CCS after CPU1 is already running.
I'm wondering:
-
Could the custom
.cmdfile for CPU2 be causing improper placement of code or vectors, leading to theITRAP0on boot? -
Is there something different in how CCS vs UniFlash performs memory initialization or sets up the entry point?
Any suggestions or similar experiences would be appreciated!
Thanks in advance,