Shop OBEX P1 Docs P2 Docs Learn Events
P2 Challenge - CLDebug — Parallax Forums

P2 Challenge - CLDebug

ctwardellctwardell Posts: 1,716
edited 2012-12-18 14:05 in Propeller 1
The challenge is to create a small interactive debugger for the P2 that mainly resides in the CLUT using CLMM and leaves as much COG space as possible so that the rest of the COG can run the code being debugged.

Ideally this would work with a serial terminal only, but given the small space available we may need a host side interface to do bin/dec/hex conversion, formatted display etc.

With a host side application the debugger could dynamically swap code in/out depending on the specific functionality needed at the time.

C.W.

Comments

  • Cluso99Cluso99 Posts: 18,069
    edited 2012-12-18 13:15
    The basis of this could be my zero footprint debugger (se the obex) - it is an LMM execution unit that lives in the shaddow ram of the P1. Jazzed also did a debugger that could also form the basis. Or a combo of both.
  • ctwardellctwardell Posts: 1,716
    edited 2012-12-18 13:16
    Cluso, I'll look that up. Thanks.

    C.W.
  • ctwardellctwardell Posts: 1,716
    edited 2012-12-18 14:05
    Cluso,

    That is very cool stuff, I don't get along well with SPIN, so it may take a while to fully digest.

    This give me the idea that we could do an SMM, the Serial Memory Model, that gets it's code from the serial port running on another thread on the P2 or via task switching on a P1.
    There could be a version that resides mostly in the CLUT or one that uses regular COG memory when the CLUT is needed by the application.

    It would obviously be very slow but might have some novel uses as the data stream could be dynamically created by the controlling application based on feedback being transmitted back.

    C.W.
Sign In or Register to comment.