Can all registered uses please login, even just for a few minutes..
It helps build a picture where our "good traffic" is coming from..
Thanks :)
It helps build a picture where our "good traffic" is coming from..
Thanks :)
Problem with H4 not booting (zChris's board)
Re: Problem with H4 not booting (zChris's board)
Not sure i did it correctly, i think so. I hade one probe on AS and one probe on a address line. Then i had a trigger on AS and recorded 0.001s after it triggered. Went back to the beginning and took a screenshot.
So i hold reset, started recording, released the reset and waited for triggering. Here is the results.
Channel 0 at the top is Adressline, Channel 1 is AS and Channel 0 at the bottom is analogue adressline.
A1 to A13
So i hold reset, started recording, released the reset and waited for triggering. Here is the results.
Channel 0 at the top is Adressline, Channel 1 is AS and Channel 0 at the bottom is analogue adressline.
A1 to A13
Re: Problem with H4 not booting (zChris's board)
It seems to be stuck in a loop accessing address zero. If you have your scope on AS and ROM_CE...
CE is the bottom right pin of U2, and goes to pin 22 of the ROM on the highlighted track..
So first check you have continuity between those two points,And when you know which pin on the ROM IC it is, use your scope on that pin along with AS. You should see both pulse low at the same time after reset / power up.
CE is the bottom right pin of U2, and goes to pin 22 of the ROM on the highlighted track..
So first check you have continuity between those two points,And when you know which pin on the ROM IC it is, use your scope on that pin along with AS. You should see both pulse low at the same time after reset / power up.
Re: Problem with H4 not booting (zChris's board)
I measured the pin on the rom and the bottom right pin on that chip and there was connection. Then i did a measure with the probe when i released reset.
Here is the results:
Here is the results:
Re: Problem with H4 not booting (zChris's board)
Thanks. So the CPU is trying to access ROM, just it's not getting anywhere at all.
Have you checked there is activity on the databus after reset ? ( no need to post images of it all)
I also suggest you continuity check the address and databus from the CPU to the ROM IC. (note the ROM only goes up to A16) .
Also check for shorts on the CPU. Meter out pins next to each other all the way around the CPU and make sure no pins next to each other or shorting out.
GLUE must be working as it's decoding address zero and issuing DTACK etc When the ROM puts data on the bus the CPU should jump to a new address, but it's not doing that.
Just to be sure, you did not change anything on the board (like the ROM) at all before it suddenly stopped working ?
Also (without power on) check resistance from all the address and databus pins to 5V and make sure they are something like 2.2K or 4.7K etc.
Have you checked there is activity on the databus after reset ? ( no need to post images of it all)
I also suggest you continuity check the address and databus from the CPU to the ROM IC. (note the ROM only goes up to A16) .
Also check for shorts on the CPU. Meter out pins next to each other all the way around the CPU and make sure no pins next to each other or shorting out.
GLUE must be working as it's decoding address zero and issuing DTACK etc When the ROM puts data on the bus the CPU should jump to a new address, but it's not doing that.
Just to be sure, you did not change anything on the board (like the ROM) at all before it suddenly stopped working ?
Also (without power on) check resistance from all the address and databus pins to 5V and make sure they are something like 2.2K or 4.7K etc.
Re: Problem with H4 not booting (zChris's board)
I found that there was no connection between the ROM and CPU on address line 12, other lines had connection.exxos wrote: Fri Aug 20, 2021 10:27 pm Thanks. So the CPU is trying to access ROM, just its not getting anywhere at all.
Have you checked there is activity on the databus after reset ? ( no need to post images of it all)
I also suggest you continuity checked the address and databus from the CPU to the ROM IC. (note the ROM only goes up to A16) .
Also check for shorts on the CPU. Meter out pins next to each other all the way around the CPU and make sure no pins next to each other or shorting out.
GLUE must be working as its decoding address zero and issuing DTACK etc When the ROM puts data on the bus the CPU should jump to a new address, but its not doing that.
Just to be sure, you did not change anything on the board (like the ROM) at all before it suddenly stopped working ?
Also (without power on) check resistance from all the address and databus pins to 5V and make sure they are something like 2.2K or 4.7K etc.
The resistance was good and varied between 1 - 2.2 but there was one pin (pin 20) that had a resistance of 5K ohm.
I did not remember doing much with the board while waiting for TF536 to arrive. Sadly though a pin broke loose yesterday on the chip that has 2.06 and 1.04 when i tried to straighten them. But i have two other roms with 2.06 and EmuTOS. I just don't know which bank they are in so i just test both banks on both roms.
/zChris
Re: Problem with H4 not booting (zChris's board)
Is this the pin that should be connected to A12 ?
Re: Problem with H4 not booting (zChris's board)
I have tried to highlight A12 for you..
Re: Problem with H4 not booting (zChris's board)
By the way, the left leg of C21 doesn't look very well soldered. Can see straight through the hole.

