One more thing with tilib: <snip> hardy:~/workspace.37/mspdebug> ./mspdebug tilib -d COM12 MSPDebug version 0.20 - debugging tool for MSP430 MCUs : (mspdebug) setbreak 0xa800 Set breakpoint 0 (mspdebug) delbreak Clearing all breakpoints... (mspdebug) run tilib: MSP430_EEM_SetBreakpoint: Invalid parameter(s) (error = 3) run: failed to start CPU (mspdebug) run tilib: MSP430_EEM_SetBreakpoint: Invalid parameter(s) (error = 3) run: failed to start CPU (mspdebug) <snap>
This is because setbreak/delbreak are actually not updating the target, while run does. So run tries to clear a breakpoint which is already cleared which leads to the message. Hardy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
