Re: PET 3032 issue

From: Gerrit Heitsch <*gerrit_at_laosinh.s.bawue.de*> Date: Sat, 4 Feb 2017 20:21:43 +0100 Message-ID: <57b3b752-c67e-93fd-ccab-3524524db31c@laosinh.s.bawue.de> · gerrit_at_laosinh.s.bawue.de

On 02/04/2017 07:00 PM, Francesco Messineo wrote:
> Ok some progress.
> It turns out that the petester.bin image only tests one 16K bank, not
> both (on my board, only the innermost bank).
> Swapping the CAS lines (R41, R42) did show some errors and I
> substituted one 4116, I thought I was lucky since the petester didn't
> show any error anymore, so I put back the original kernel ROM and it
> did indeed boot fine.
> I swapped back in their original places R41's and R42's ends and...
> black screen again.
> I socketed and substituted another 3x4116 but that didn't revive the
> PET. So I swapped again the CAS lines and I'm going to write some test
> programs to understand what are the bits that don't work as expected.

Doesn't the 3032 have TIM? You should be able to find the broken RAMs 
from within the Monitor.

  Gerrit

       Message was sent through the cbm-hackers mailing list