No problem, we can gladly look into this. Do you mind sharing a screenshot of the entire Visual Studio window demonstrating the issue? The screenshot should also show the Solution Explorer and at least one source file (it’s important for checking for common module loading issues).
Thanks for your help downloaded the update, it now has the new .dll but uses has the old msp430-gdbproxy.exe. I had to copy the new msp430-gdbproxy.exe in to get “start without debugging”(Ctrl F5) to work.
I would have thought you would have the new msp430-gdbproxy.exe in the new package?
No worries. The MSP430 toolchain has a relatively low priority, so we would normally only update the gdbproxy when releasing a new major update to minimize the risk of breaking backward compatibility.
That said, if you have been successfully using the new gdbproxy with the new msp430.dll for a while, the chance of unexpected issues is very low. We have updated the toolchain package again with the latest gdbproxy.