Careful with Spin2 debug
Rayman
Posts: 14,744
in Propeller 2
Guess I'm off today, just spent several minutes racking my brain to figure out why I was suddenly getting this "Debug Communications Lost" message after adding a new debug line...
Figured out it was because did:
debug(otype)
instead of:
debug(udec(otype))
I'm not sure what that first one does, but it's nothing good...
Comments
I have noticed that, too -- odd errors if there is type definition typo.
IIRC the first one sends a raw byte over the serial link. May mess up the step debugger stuff.
Right, if it gets a 0..7 byte, it thinks a breakpoint has occured.
This gets me, sometimes, too.