• Please review our updated Terms and Rules here

Pettester

J

Jannie

Experienced Member
Joined
Feb 5, 2017
Messages
273
Location
Cape Town
Question for all, but clearly daver2 is the man that will know since this is his baby. :)

I downloaded PETTESTER V04 from this post .

Trying it in a 8032 (50Hz, Business keyboard), gives me intermittent, and non-repeatable, results. I've seen it load and run on a 50Hz system, more often that not, it ran at 60Hz, causing V-sync issues and - often - I just get a blank screen.

My Googling skills are failing me and I cannot find a site where the PETTESTER is hosted. :(

Basically looking for the latest and greatest version that will run on a 50Hz, Business 8032.

Thanks!
 
That post is where it is hosted.

V04 is the latest.

The source code is on my google drive and the instructions for changing the CRTC initialisation should be in the PDF documentation. The source code is assembled by an online assembler (again, described in the documentation).

You would definitely have to change the CRTC initialisation code with a 40 column beast (only if it has a CRTC though). An 80 column 8032 should be fine as it is...

Dave
 
Thanks Dave,

I definitely get inconsistent results when using V04 in a 8032.

I wrote it to a 28C16 though, do you think that could be an issue?
 
The checksum on your EEPROM programmer should end in 'DD' if it programmed correctly.

Double check that you are installing in the UD7 EDIT socket and not the kernal socket (UD6).
 
It's a Catalyst (CSI) CAT28C16AP - 20, so, at 200ns, should be plenty fast enough, right.

Looking at the PETTESTER image on the 2816, with my EPROM programmer, I could see Dave's name at the end, so the chip looked OK. But when I verified it against the stored image, a few bytes were different! WTH....:shocked:

It definitely worked and then stopped, so all I can think is that the board managed to write to the chip.

Ah, just realised what happened :) ; At one point I pulled /NOROM low to see if it had any effect on the testing I was doing. BUT....on a 2816, pin-21 is /WE, not CS as on the 2316 so I, inadvertently, put the 2816 into programming mode and the 8032 obliged by rewriting some bytes for me. :)

I reflashed the 2816 with the V04 PETTESTER image and it's now running in an 8032 but at 60Hz, causing sync issues on my monitor.

60Hz-1.jpg

60Hz-2.jpg

I looked a bit at the info Dave posted but, to be honest, it's currently above my paygrade to quickly make a 50Hz version.

If anyone could point me to a byte or two that must change in the image to set the CRTC to 50Hz, I'd be grateful. It's a cool tool to add to the arsenal. Probably in EPROM format :)

/Added: What is the preferred EPROM to use in place of a 2316?
 
Last edited:
Got it working! :D

Dave's excellent documentation made it possible to find the CRTC init parameters in the binary file and also what the various settings should be.

I changed these 3 bytes:

60Hz-50Hz.jpg

And now get a nice, clean, 50Hz display :)

50Hz-1.jpg
 
>>> I looked a bit at the info Dave posted but, to be honest, it's currently above my paygrade to quickly make a 50Hz version.

Have you seen the spreadsheet at http://www.6502.org/users/andre/petindex/crtc.html (bottom of page)?

Basically, you identify your desired EDIT ROM and the various numbers in the columns are the values to be stored into the register initialisation for the CRTC. Can you let me know what EDIT ROM you are running and I will send you the patches.

EDIT: No sooner had I posted then you have fixed it :)! See, it wan't above your pay grade after all! It always pays to write good documentation for people.

Dave
 
daver2 said:
EDIT: No sooner had I posted then you have fixed it :)! See, it wan't above your pay grade after all! It always pays to write good documentation for people.
Dave
Click to expand...

^^ this. A thousand times over. :)

Good documentation is often worth more than the actual code, event, item, etc. being documented. It allows people to learn and ensures knowledge is not lost over time. Few things as frustrating as having to figure something out that's previously been done but not documented.

PS: The 'paygrade' thing refers to having to compile a new ROM from the .asm :) Editing the binary file was easy as it was a byte for byte replacement of a few variables.
 
I find asm80.com a nice and simple online editor/assembler to use. Despite its name, it can be used for a lot of 8-bit microprocessors - not just an 8080...

Dave
 
You must log in or register to reply here.
Back
Top