Debug with it's own cog?

Comments

• JonnyMac Posts: 9,567

  2026-01-02 21:14

  I used to do that, too, and still do when I want nice formatting on the output terminal (e.g., PST). If your background cog is simply displaying global variables being used by your main cog, then it shouldn't have any impact on the speed of your main cog.
• Wuerfel_21 Posts: 5,758

  2026-01-02 21:34

  Generally whatever is happening in one cog does not slow down or speed up another. The Propeller is specifically designed to avoid this sort of "scary action at a distance".

  The only exception is when using locks or other forms of explicit synchronization, which relates back to debugging: The debugger uses a lock bit to arbitrate access to the serial port. If one cog is hogging this debugger lock (by constantly printing debug messages) then other cogs will wait on that lock whenever they want to print a message.
• Rayman Posts: 15,934

  2026-01-03 01:24

  This is one reason the debug terminal mode is nice. If there is a concern one can use fullduplex serial instead of debug and be sure…