I have worked on this issue with the CCS group, reaching the conclusion that the problem is more likely to be related to the boot firmware in the F28379D.
This is the original post, which demonstrates the steps on how to reproduce the issue. In summary, when the cores are grouped, CCS is unable to resume and suspend execution without generating an error on the first attempt. https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/559771
Here are some of the conclusions and questions directly from the customer, who is well versed in the bootloader process of the C2000 devices:
- Running both cores causes them to stop because of an ESTOP0 in the boot ROM. Why is this in the code? Why stop the code execution when the debugger is connected? We just want the code to read the hardware jumpers at startup to determine the boot mode. This is what the boot ROM source code states:
-
void WaitBoot(void) { // sysctl_wdog_enable(); //- for debug if(((OTP_BOOT_CONFIGURE_WORD & 0xFF000000) >> 24) == 0x5A) //CHECK if key match fails { if(((OTP_BOOT_CONFIGURE_WORD >> 8) & 3) == 0x1) { c1brom_enable_pie_in_boot(1); } } else { sysctl_wdog_enable(); } // If the emulator stops here // a) change EMU_KEY to 0x55AA // b) write the appropriate boot mode to EMU_BMODE // c) perform a debugger reset, and run asm(" ESTOP0"); for(;;) { } }
Thank you!
