Re: option ROM into a 3032

From: Francesco Messineo <francesco.messineo_at_gmail.com>
Date: Wed, 4 Oct 2017 12:43:15 +0200
Message-ID: <CAESs-_yJ7jtzb+W9axpT-1Bx0-ahCR6j0PAqXeJx4b1ujXM3+Q@mail.gmail.com>
On Tue, Oct 3, 2017 at 7:00 PM, Francesco Messineo
<francesco.messineo@gmail.com> wrote:
> On Mon, Oct 2, 2017 at 9:41 AM, Francesco Messineo
> <francesco.messineo@gmail.com> wrote:
>> On Fri, Sep 29, 2017 at 10:20 AM, Francesco Messineo
>> <francesco.messineo@gmail.com> wrote:
>>> On Fri, Sep 29, 2017 at 7:55 AM, Francesco Messineo
>>> <francesco.messineo@gmail.com> wrote:
>>>> On Fri, Sep 29, 2017 at 7:05 AM, William Levak <wlevak@sdf.org> wrote:
>>>>> On Thu, 28 Sep 2017, Francesco Messineo wrote:
>>>>>
>>>>>> On Thu, Sep 28, 2017 at 12:48 PM, Francesco Messineo
>>>>>> <francesco.messineo@gmail.com> wrote:
>>>>>>
>>>>>>>
>>>>
>>>>>>
>>
>>> update: changing the UD8 socket, did bring the system to the basic
>>> prompt, with correct bytes free count.
>>> I then restored the two CAS resistors (I had lifted them to swap RAM
>>> banks) and now I have a completely black screen, not even the garbage
>>> screen if I remove the UD9 ROM :(
>>> Looks like I now have to debug the video signal path. This PET hates me I guess.

Success, so far :)
Look like it was quite a broad fault (probably originated from a
single shorted input):

UG3 bad
UF4 bad
UF5 bad
UH5 bad (shorted input on pin4) <-- this was probably the start of the
multiple fault

In the process I have suspected also UF2 (socketed, but good).
All in all, I'm happy I didn't socket too many good ICs.

Frank IZ8DWF

       Message was sent through the cbm-hackers mailing list
Received on 2017-10-04 11:00:02

Archive generated by hypermail 2.2.0.