[quote]
The immediate value is embedded inside the opcode. In our driver we are testing breakpoint instructions to be BKPT with 0 as immediate value. We should instead mask the bits in the opcode that bear the immediate value and then test for BKPT instruction for embedded breakpoints.
[/quote]
This seems to be the important bit - if I swap to using
BKPT 0
then it can be stepped over in CCS 5.5.0.00077 like my feature request asked, so it sounds like this should be logged as a fault instead since the debugger should mask out the immediate value when considering what to do.
I often use non zero immediate values so I can leave several BKPTs in different code paths and know which one is which when they hit.
[quote] Is updating to CCSv6 an option for you? [/quote]
I can do, though it doesn't sound from what you say that this will help with non zero immediate values which appears to be the trouble. I don't have a problem with '#' or no '#' (but agree that both should generate the same code and behave the same).