Other Parts Discussed in Thread: LAUNCHXL-F28379D, C2000WARE
Tool/software:
Hello,
I'm looking for a solution to my problem.
I am developing embedded software using CCS12.6 with LAUNCHXL-F28379D hardware.
The sample code I used is "gpio_ex2_toggle" and the CPU selection is CPU1 only.
To match the hardware configuration of the LAUNCHXL-F28379D, change the package and part options in the Sysconfig->Basic option of the project properties to "F2837xD_337ZWT" and the Predefined symbol in C2000_Compiler Predefined symbol "_LAUNCHXL-F28379D" is added in C2000_Compiler.
In the early stages of software development, we were able to activate the CPU1_FLASH configuration and verify that we could write code to the internal FLASH ROM, that we could execute the expected operation, and that the software would work again even after the hardware reset button was pressed.
We have since switched the configuration to CPU1_RAM and added software functions. When the configuration is CPU1_RAM, the software runs as per the functions incorporated. However, when the configuration is switched to CPU1_FLASH, the software does not work.
In the software under development, the LED is turned on during the initialization of the peripheral in the main() routine.
After executing the build with the CPU1_FLASH configuration and writing to FLASH_ROM, when the hardware reset button is pressed, the LED lights up, so I assume that the software is able to execute until the middle of the main() routine.
After that, the software stops at the breakpoint shown in the figure below, and disassembling the software shows that it stops at ESTOP0.
Are there any possible causes or countermeasures?