On Wed, Sep 7, 2016 at 1:46 PM, Noel Chiappa wrote:
> > From: Paul Koning
>
> > A possible reason would be that the address drivers for that bit, or
> > the address decoders in that chip, are busted. The result would be that
> > reads and writes always touch the same address in the
> From: Paul Koning
> Semiconductor memory, right?
Yup.
> A possible reason would be that the address drivers for that bit, or
> the address decoders in that chip, are busted. The result would be that
> reads and writes always touch the same address in the chip.
Oooh, good p
Is there a hint as far as the affected hardware in that the ODT is
working, but the ram is not? The rom that is running ODT is also being
accessed for read correctly. Perhaps the problem is migrating since the
system halts however. A wild jump and a fault if the rom path is
affected might ex
> On Sep 7, 2016, at 11:44 AM, Noel Chiappa wrote:
>
>> From: Ethan Dicks
>
> Let's look at this one first, this is probably the easier to solve.
>
2) Setting D10 in location 00 results in D10 set in all the
locations
>
>>> Sorry, didn't follow that? Did you mean that if you sto
> From: Ethan Dicks
Let's look at this one first, this is probably the easier to solve.
>>> 2) Setting D10 in location 00 results in D10 set in all the
>>> locations
>> Sorry, didn't follow that? Did you mean that if you store 02000 in
>> location 0, all other locations n
On Wed, Sep 7, 2016 at 8:35 AM, Noel Chiappa wrote:
> > From: Ethan Dicks
>
> > What's happening now . is when I change one location .. it
> > echoes across multiple locations...
> > ...
> > 1) Depositing any value is echoed 20 later.
> > ...
> > Does this sound li
> From: Ethan Dicks
> What's happening now . is when I change one location .. it
> echoes across multiple locations...
> ...
> 1) Depositing any value is echoed 20 later.
> ...
> Does this sound like a dodgy CPU, dodgy RAM or both?
It could be either. One possible
