Re: option ROM into a 3032

From: William Levak <wlevak_at_SDF.ORG>
Date: Fri, 29 Sep 2017 05:05:13 +0000 (UTC)
Message-ID: <Pine.NEB.4.64.1709290443070.12710@sdf.lonestar.org>
On Thu, 28 Sep 2017, Francesco Messineo wrote:

> 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
>

If you have an older PET (without CRTC) that has been upgraded to Basic 
4.0, the jumpers may not have been set correctly.  There are jumpers that
control addressing of the ROMs. If they are not set correctly you will 
have addressing problems. Check the schematics for correct jumper settings.



wlevak@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

       Message was sent through the cbm-hackers mailing list
Received on 2017-09-29 06:00:03

Archive generated by hypermail 2.2.0.