Hi Erich,
Thanks for the reply. I went to the link\article and tried it. Unfortunately, it does not work on the DSC debugger in CW 10.7, like a lot of other standard debugging features. The issue here is that the DSC implementation on Eclipse has too much Metroworks DNA in it.
The old Metroworks tools (6.x for s08 & 4.x & 8.x for DSC) are terrible tools, missing features like adding symbols, post build steps, requiring the user to choose flash download scheme BEFORE debugging, can't build while debugging because the ELF file is locked, windows popping up on every search, no window docking, a windowing nightmare. Compared to TI's Code Composer 2.2 & 3.3 which are also XP tools of the same vintage, the Metrowerks tools look like a high school project.
Fast-forward to Eclipse, the DSC tool chain is just lipstick-on-a-pig. Pretty sure that it is the Eclipse GUI with the old MW code behind it. It's still feature limited, and buggy. Often, I get errors just adding a global variable to the Expression list, something like "Can't find child." Additionally, the debugger will not stop at breakpoints after a build unless a Clean was done first, a complete rebuild. So, that is just a flavor of why a standard Eclipse feature does not work. No tool improvements or fixes BUT, still $5000 !!!
