This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
As the thread title suggests, I'm using Code Composer and setting a breakpoint at a certain line where I'm performing a GPIO Pin Read during the rising edge of a clock that is generated by a Timer. I'm using the MSP432 to communicate with an eMMC Flash storage device that is able to read/write data from a sensor attached to a GPIO Pin and use the eMMC for data logging. I'm essentially saving either a '1' or a '0' into an unsigned char array that is 4096 bytes long (which is something I plan on optimizing to be more efficient with memory storage), in order to translate a data block the eMMC is sending back to the MSP432. When I set a breakpoint at the line where the GPIO Pin Read is performed, I am able to step through the pin read actions or cancel the breakpoint and allow my program to continue reading at the clock frequency I have set. However, if there is no breakpoint on this line, the program freezes and I can only suspend or execute the program in Debug mode (suspending and then resuming my program still leaves the program frozen and unchanged). I assume there is some unexpected interrupt happening that is keeping my program stuck in this state when there is no breakpoint on this line. So I was wondering if anyone had any insight on what the breakpoint might be resolving that's allowing my program to resume or step through my program and why having no breakpoint might be causing me this issue? Also, any ideas on why my program might be freezing without the breakpoint would be super helpful as well! Thanks
TM
After further examination, I noticed my program enters an infinite while loop inside the Default_Handler(), does anyone know what that could convey about where/why an unexpected interrupt could be occurring in my program?
See the [FAQ] How to debug a program going into FaultISR which is linked from [FAQ] FAQs for TM4C Arm Cortex-M4F Microcontrollers.
The 1st FAQ links to http://www.ti.com/lit/spma043 which describes how to find out why Default_Handler() got called.
While the FAQ was written for TM4C devices, it should be relevant to a MSP432E which shares the same Cortex-M4F CPU and peripherals as the TM4C129 devices.