Re: option ROM into a 3032

From: Francesco Messineo <francesco.messineo_at_gmail.com>
Date: Thu, 28 Sep 2017 19:14:02 +0200
Message-ID: <CAESs-_xum4JY9M-dNYiUC720o5_sYOGmaKkbYnBn232WkfU6KQ@mail.gmail.com>
On Thu, Sep 28, 2017 at 12:48 PM, Francesco Messineo
<francesco.messineo@gmail.com> wrote:

>
> it's every 8 chars. Now I first have to replace the UD9 socket (I
> hope). After swapping the EPROMs a few times, the PET no longer
> execute anything, so I guess it's that crappy socket.
> I'll have a look at that counter after I fix the ROM problem (unless
> something else died).
>>

turns out the "every 8 chars" flickering was a bad UF8 (MOS 2114 variant).
UF7 (the twin MOS 2114) had also a few bad cells (3 that I could
observe using pettester.bin image).
Now for the real "funny" part: pettester.bin shows no error both on
VRAM and on the system RAM, but using the original kernel EPROM on UD9
gives a garbage screen.
I've tried to swap the 16K banks but no change.
Looks like there're still problems.
Does anyone feel like coding a much more useful test image for 2001N? :D
Debugging a PET without a logic analyzer can require a "funny" amount of time.
I think a good test program that can be put in the kernel socket would
speed up the process.

Frank IZ8DWF

       Message was sent through the cbm-hackers mailing list
Received on 2017-09-28 18:00:07

Archive generated by hypermail 2.2.0.