Tool/software: Code Composer Studio
Hello,
I have a situation where GP4[0] is being set high, but not understood why. So I need to setup a complex hardware watchpoint, with condition of that bit being written, but with other discrimination logic (since it is not any write, but under certain conditions where it is set high unexpectedly). So I've used this Response Condition in the hardware watchpoint:
( ( ( *(unsigned int *)0x1e26064 & 0x1 ) == 0x1 ) && ( g_mb_debug == 1 ) )
where the 0x1e26064 is the location of BANK45, and the first bit is GP4[0]. g_mb_debug is a local variable to my application which is set high during the period when GP4[0] is being set high unexpectedly. But when running with this logic, the processor application kind of goes nuts ... leds that shouldn't be active start blinking at a high rate of speed, etc.
Can anyone review my logic above, to see if there is something I've overlooked/doing wrong, that might be causing this issue. Or maybe it is an issue with the OS/gpio bank support. I've attached a picture below, showing the exact hardware watchdog setup.
Regards,
Robert
