exxos's Atari, Amiga & retro forum

can anyone compile Troed's wait state detect program for me ?


https://github.com/troed/WSDETECT


I also wonder if someone could tweak that to actually output the values it read rather than the expected values so I can see how far things are actually out on the suska core.


EDIT:

Finally found the PRG.. still would be useful for a "debug" version of it though...

Haven't tried yet, but looks like being compilable by devpac, maybe pasm with a few tweaks.

If anyone could add a colour background change that would be useful as I cannot see the text output to the screen most of the time because of bit-plane shifts :roll: Red of WS ? or green for a valid wait state would help no end.

I understand assembler, but i don't pretend to understand what this special kind of program is trying to achieve ;)

thorsten.otto wrote: 21 Feb 2020 02:13 I understand assembler, but i don't pretend to understand what this special kind of program is trying to achieve ;)

It outputs the wakeup state of the machine. Demo coders build fullscreen stabilisers based on its value. I don't really understand it myself. http://www.atari-wiki.com/index.php/ST_STE_Scanlines

In very high-level terms, I explained what it does in this other thread: https://www.exxosforum.co.uk/forum/viewt ... =10#p33642

Here is a quick and dirty version that displays the counter in hex. I will publish the source code later (I've never used github before :D )
It seems to work as expected on Steem SSE 4 (I only have STEs)

Thanks, seems to work. I assume in the image below WS2 means it counted 36 bytes :shrug:


and WS ? gives 0x0000 but its always hard to read which is part of the problem... Not sure is possible to actually output how many bytes accounted regardless of it translating it to the "WS" number ?

The computed value is displayed in any case. I get "WS? (0x00AE)" on STE in Hi for example.
It is the value in d4 as used in the switch case at lines 244-252 converted in ASCII

Wonder why it says 0x0000 on mine then ?