newRPL: [UPDATED April 27-2017] Firmware for testing available for download

[Claudio L.]

(01-24-2017 05:09 PM)The Shadow Wrote:  Further questions:

Is it one breakpoint at a time globally, one breakpoint per program, or what?

If I forget to CLRBKPOINT, that breakpoint will remain on the program indefinitely?

I forgot to clarify this: I designed it with 3 breakpoints (because they take permanent space, so we can't have that many). Of those 3, one is used for stepping between code (SST) which leaves 2 breakpoints for the user to manage. For now I included commands to set one of those SETBKPOINT/CLRBKPOINT. If in my daily use I find this feature useful, I'll add commands to set a second one, otherwise I'll cut the number to 2 and save some RAM. If you ever feel you *need* to have 2 let me know and I'll just add the commands SETBKPOINT2/CLRBKPOINT2.

Also, enabling a breakpoint slows down execution so we don't want to have many breakpoints unless absolutely needed.