Another PASD Feature Request

pjv

Hello Ariba / Andy;

I'm using your PASD debugger quite a bit, and find it very useful, especially with the changes you have implemented. I wonder though if it would be possible to add the following features;

When stopping a debug session (F6), it appears that all COGRam variables get cleared - or at least the viewer is not updated. Could that be changed to automatically show the latest contents on stopping?

Secondly, would it be possible to have a "poll" mode where, on encountering a certain breakpoint, the COGRam variables are again updated on the display, and then automatically continue debugging? This may be much more difficult, in which case only the first request would already be of significant advantage.

Many thanks for listening,

Cheers,

Peter (pjv)

Ariba

Hello Peter

I wish your first request would be possible. But the lack of any kind of interrupt on the propeller prevent this feature.
You can stop a cog, but not restart it without reloading the whole cog memory. And then all the previous content is lost.
I hope Prop II will have a new Hub Instruction which restarts a cog without reloading!

Your second request is rather possible, but needs some significant changes in the PC Application.
Would it be helpful to have only a "Auto continue" mode which updates the viewer contents and the continue to run on
every breakpoint?
Have you noticed that the Pin-Viewer is continuously updated? So it may be a solution to write some bits of a variable to
Port-Pins in your code, then you can watch theme while running.

Andy

pjv

Hi Andy;

Thanks for that information.

Now I understand why the memory contents cannot be seen after stopping.

As to the second request, yes enabling an Autocontinue feature with a button would do very nicely. Nicer yet, if the update could be on a specially enabled breakpoint(s). And a selectable delay to view the data before continuing. Alternately a display of the data every Nth time through a breakpoint.

Wonderful if this could happen.

As to using the I/O pins, effectively I'm already doing that with 32 LEDS and multiple scope probes attached.

Many thanks,

Cheers,

Peter (pjv)