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.
I am running CCSV4.2.1 with EKS-LM3S3748 evaluation kit.
I am trying to check out some I2C circuits. Occasionally when I try to set a break point, instead of placing the break point on the line where I want it, the break point gets set at the return line at the end of the function.
Example if try to set break point on I2CSlaveInit(I2C1_SLAVE_BASE, slave_address); it gets set on return(0);
slave_address = 0x08;
slave_data = 0xAA;
I2CSlaveInit(I2C1_SLAVE_BASE, slave_address);
i2c_send();
//
// Return success.
//
return(0);
}
Is there some reason I can't set the break point where I want to?
vern hardingham said:I am trying to check out some I2C circuits. Occasionally when I try to set a break point, instead of placing the break point on the line where I want it, the break point gets set at the return line at the end of the function.
Sounds like you have compiler optimization enabled in your build options. This would impact your ability to set source line level breakpoints.
See: http://processors.wiki.ti.com/index.php/Debug_versus_Optimization_Tradeoff
Thanks
ki
With optimisation, you might have more success setting the breakpoint close to where you want in the assembler window rather than in the C source. Stop execution somewhere before you want the breakpoint, then view the disassembly window.
Regards, Tony.
Thanks,
I didn't realize the default optimize settings had this effect. Under Properties I set optimize to blank. Now I can place the breakpoint where I want it.