Page 2 of 2

Re: Robson's H5 x 2

Posted: 22 Jan 2021 14:32
by Robson
It's jumpered to 1Mb at the moment. (I'm 1 jumper short but memory size doesn't make any difference)

Re: Robson's H5 x 2

Posted: 22 Jan 2021 14:37
by Robson
exxos wrote: 22 Jan 2021 12:45 Nothing should be accessing it, so have you done verify ROM ? Looks like you have PP's modified TOS104 so you really need to try a generic 104 so the diag cart can do a proper checksum on it.
It's the same TOS I use with H4 build. There were no issues with it.

Re: Robson's H5 x 2

Posted: 22 Jan 2021 14:39
by exxos
Robson wrote: 22 Jan 2021 14:37
exxos wrote: 22 Jan 2021 12:45 Nothing should be accessing it, so have you done verify ROM ? Looks like you have PP's modified TOS104 so you really need to try a generic 104 so the diag cart can do a proper checksum on it.
It's the same TOS I use with H4 build. There were no issues with it.
Its not what I mean, I mean checksum will verify all the ROM address / data lines are connected correctly etc..

Re: Robson's H5 x 2

Posted: 22 Jan 2021 15:22
by Robson
A10 and A13 shorted together. These are the 2 measuring lower, 2.4k (common imp) to gnd as well.
I'm hoping if that's fixed it will be back.

Re: Robson's H5 x 2

Posted: 22 Jan 2021 16:26
by Robson
@exxos Can you help me with these 2 lines (A10, A13). When is it when they're running close together? To MMU?
thanks

Re: Robson's H5 x 2

Posted: 22 Jan 2021 16:30
by exxos
Robson wrote: 22 Jan 2021 16:26 @exxos Can you help me with these 2 lines (A10, A13). When is it when they're running close together? To MMU?
thanks
They run all over the place, it could be anywhere...

1.PNG
2.PNG
3.PNG
4.PNG

Re: Robson's H5 x 2

Posted: 22 Jan 2021 17:01
by Robson
Thanks...I thought this will be the case.