There are some usability issues with hardware breakpoints in the Disassembly view

1) When hardware breakpoint resources run out, a greyed out icon appears when attempting to set a hardware breakpoint on a new line. This is expected. When a previously set hardware breakpoint is removed, one of the greyed out icon will turn red as expected, indicating that the hardware breakpoint resource was freed up and used for a line that previously had a greyed out icon. While this breakpoint appears valid (program will halt on this line), the icon is missing the "H" indicator for a hardware breakpoint. Also, when checking the breakpoint in the Breakpoints view, it is not possible to get the properties of the breakpoint.

2) For both greyed out breakpoints and breakpoints missing the "H" icon, it is not possible to click on it again in the Disassembly view to remove the breakpoint. When clicking on a greyed out icon, it simply sets an addition greyed out breakpoint on the same line. For a breakpoint missing the "H", it will set an additional proper hardware breakpoint (with the "H") on the same line. This "proper" breakpoint then can be removed by clicking on it again while the "invalid" one continues to remain.

Note that #2 was not an issue with CCS 20.3.1