David Schmidt <
[email protected]> writes:
On 2/6/22 10:10 PM, Nick Westgate wrote:
Hi guys.
Obviously this can't be done in earlier Apple II computers.
But someone commented on my answers here:
https://retrocomputing.stackexchange.com/questions/23854/can-you-read-the-character-definitions-font-in-an-apple-ii-using-peek-in-apple/
"Actually, on the Apple IIgs, there was a way to read the character ROM - it wasn't
directly in the memory map, this was done in some backdoor way through other >> video-related registers. It's been far too long, I don't remember the details, or any
explanation as to why Apple bothered implementing this."
I've searched comp.sys.apple2 but came up empty handed.
Does anyone have the details of how to do this?
They _might_ have been thinking about the Apple ///, which you do need to go through some
register and interrupt chicanery to load chargen data.
Well, there are some vague clues:
1. Apple IIgs Firmware Reference, page 281, last line:
C02C:00 246 CHARROM DFB 0 ; Addr for tst mode read of character ROM
page 290 has one line each for three more "test mode" registers:
C06D:00 584 TESTREG DFB 0 ;Test mode bit register
C06E:00 585 CLRTM DFB 0 ;Clear test mode
C06F:00 586 ENTM DFB 0 ;Enable test mode
2. The Cortland Custom ICs document:
http://www.brutaldeluxe.fr/documentation/cortland/v5/Cortland%20Custom%20ICs%20-%20Wayne%20Lowry%20-%20Preliminary%20notes%20-%2019860214.pdf
Page 46 has a _VGC Test Modes_ section, and it says:
VGC Test Modes
The VGC can be put into the test mode by pulling the TEXT input pin to a logic 0 level.
When this pin is low, an internal dot-clock signal is multiplexed out onto the 3.5DISK
output pin. This signal is used inside the chip to clock out video data; it can be
used for signature analysis testing of the video outputs.
When the VGC is in the test mode, writing a 1 in bit 0 of the Disk register "breaks up"
the internal video counters and address counters and causes them to count in a
different sequence. This is done to speed chip testing. When the counters have been
broken, only a power-on clear can restore them to their normal operating condition.
I might pull out my IIgs and fiddle around, but it's going to be a lot
of shooting in the dark.
I've looked around for diagnostic code, but haven't found anything relevant.
There are interesting files here:
https://tek4um.com/Apple Cork Cupertino Arhive/
with some relationship to diagnostic tests, but nothing mentions the
above I/O locations.
The Brutal Deluxe corland documentation also seems like a likely place
to find such information, but so far I haven't found anything else.
Perhaps some other eyeballs on it might uncover something interesting?
--
Jerry awanderin at gmail dot com
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)