[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dead //c?
On Jul 11, 10:45 pm, "RedskullDC" <r...@oz.org> wrote:
> Hi Phil,
>
> "phil" <pjwy...@gmail.com> wrote in message
>
> ace9e1a4-caf8-435a-920b-b0d23eb05e34@v6g2000prd.googlegroups.com">news:ace9e1a4-caf8-435a-920b-b0d23eb05e34@v6g2000prd.googlegroups.com...
>
> > Well, I was just guessing about the RAM. Do you think it might be the
> > CPU?
> > With modern machines bad CPU usually means no display, but Apple broke
> > all the rules with the Apple // I guess.
> > Thanks for pointing me to futurlec for RAM...
>
> The pattern you described ( @'s and solid blocks) is not unusual to
> see briefly before the machine resets and clears the screen memory.
>
> If you can see some activity on the 65C02's clock input, then
> check to see if :
>
> 1. The *RESET line is low/high. Stuck low will keep the machine in a
> perpetual reset cycle.
> 2. Look for pulse activity on the CPU data lines, followed by Address lines.
>
> Where are you by the way?
>
> Cheers,
> Red
Sydney. I'll have to ask a mate about checking a signal on an IC.which
pins of which
IC's do you mean, please, thanks in advance.?