|
|
Post by oziphantom on May 19, 2019 8:22:15 GMT
In the new version of csdb.dk/release/?id=178008 you can now view VDC Bitmap, both from VDC RAM, RAM0 or RAM1. Supports custom stride, and double wide mode. |
|
|
|
Post by hydrophilic on Jun 13, 2019 7:42:26 GMT
This sounds like an interesting project, but your description is very brief. I followed the CSDB link and that had NO description, although it did feature a generic "screen shot". The CSDB page had a link to github/ACME which had a (sub)folder for VICEPDBMonitor. That subfolder didn't have a ReadMe file (or similar)... although I did find Done.txt and TODO.txt files.
The 'done' file reads like a history of accomplishments, but it realy doesn't describe csdb.dk/release/?id=178008 "VICEPDBMonitor". The 'TODO' file seems ambitious, but the context is not clear...
Can you tell us (more specifically) what VICE PDB Monitor does, and how it would be useful to the C128 community? Do you have any example programs / disks / blogs that would clarify your work?
|
|
|
|
Post by cbmguy on Jun 13, 2019 12:42:19 GMT
It's a remote Graphics viewer and monitor for VICE by the looks of it. Run this application on your windows box, run VICE, select 'enable external monitor" from teh machine settings and you're golden. From there, you can select a page for the VIC to view or VDC now and some source code which you can debug in real time. I loaded up turrican II and selected VIC bitmap then selected $E000 for the page. The app showed the VIC screen remotely, for example. I tried to load up Wheels128 to see the boot loader source and the VDC bitmap display, but it would never connect and kept crashing. Even with just the normal bootup screen it would simply crash  I've only been able to connect once, however. Pretty slick if it was more stable or perhaps I was starting them up wrong ... or something... ?? |
|
|
|
Post by oziphantom on Jun 15, 2019 11:37:12 GMT
the zip has docs in it. Basically PDB is the Visual Studio Intellisense file. So this is a source code level "remote monitor" for VICE.  It has break point control, it also has Asserts that can be injected from your source code. It has a script function which lets you perform both vice and shell commands at once. So you can m some area of memory to a file then run a python script over the data to verify it etc. It has a very fancy cpuhistory view ( but 64 only, as 128 doesn't support chis), and it lets you view bitmap,char,sprites,vdc,screen data. Handy calculator to work out addresses, and there is a tweak panel with gives "ic=u64" like tweaking. Stepping is on the F keys at you would expect from VS. you can use DUMP to see the contents of variables in the code, it will even look up ZP vectors for you and get data from the pointer.
|
|
|
|
Post by oziphantom on Jun 15, 2019 11:40:35 GMT
typically you run VICEPDB then you launch vice as
x64/x128 -remotemonitor -remotemonitoraddress 127.0.0.1:6510
you generally want to quit VICE first, or expect lots of pain, (if such a case happens use ALT+Tab and Alt+F4 ) or you can use 'quit' in VicePDB.
|
|
