James Michael Newton wrote:
>
> Tony, could you amplify a bit on that "Active break points" thing?
> If I didn't already have a SXKey and an ICD, I'd be emailing away....
> congratulations on a very nice product and, I hope, on a stable marriage.

Hi James,

If you look at the ROMzap web page, you can see a highlighted break
point. This happens when that line of code is executed.

http://www.picnpoke.com/demo/ROMzap.html

Because ROMzap does not use internal debug (yet??), break points are
much like interrupts. Any registers that are used in the boot code must
be saved and restored on exit. This turned out to be quite a reasonably
involved procedure and a BreakCode MACRO is expanded each time break
points are included in the user code. (256 maximum)

Depending if the user code has interrupts enabled , the MACRO expands
into 7 or 10 instructions.

This is the syntax.

        BreakCode 0x44

0x44 is the unique identifier for this particular break point. This 8
bit value is passed to the boot code and back to the PC. ROMzap then
looks through the T*.asm file and highlights this code line. Now RAM can
be accessed and altered. (Soon EEPROM and ROM as well.)



--
Best regards

Tony

http://www.picnpoke.com
mailto:sales@picnpoke.com