AdamK wrote:IIRC, CT60 does not use ROM on motherboard (in 060 mode, for sure)
exxos wrote:As you are getting the logo TOS has to be running so that is a good thing..
You really need to know what comes next after the logo in TOS. I would assume TOS will try and access the floppy drive before it counts ST ram and other things.
exxos wrote:Have you looked at the Atari service manual ? Be it probably for ST range, but it would show the boot sequence of TOS ? Probably its waiting for a ack line from something and never getting it, so it gets stuck..
exxos wrote:I doubt wire resistance would cause that much of a problem. It it was, im sure you would get all sorts of corruption on the screen. I never worked on fixing Falcon hardware before (other than my own ) but have you tried removing the WD1772 and see what happens. Normally if that is missing it will bomb out. At least you can see if it gets stuck before or after floppy access. I don't know what comes before that, probably keyboard ? Unplugging it should give you the repeated click sounds if it gets that far. Not sure what else happens during boot up.
exxos wrote:I did not realise it was working with CT60. Doesn't the CT60 use the 030 CPU for some things anyway ? That would pretty much rule out a lot of things. A ST ram test would verify good 030 operation if that can be done with CT60 installed.
It would seem to be some odd problem with TOS then I would assume. Is the 030 bus still active after the logo comes up ? normally any errors give the bombs, but never known TOS just to sit there like that, unless your TOS is just simply bad, or pure fluke it boots and there is a dataline missing preventing it from accessing higher up TOS locations. Could be a fluke that TOS is wanting to run the next routine, but a failed address line is causing it to bounce back a few instructions to display the logo again, and its stuck in a loop displaying the logo. Could be highly unlikely, but worth checking out all the TOS address lines are active.
Dal wrote:You have got the keyboard plugged in, right?
paul92706 wrote:could the trace resistance be a factor to this?? as i used standard copper wire to do all my trace rework, which were a tad bit under sized to the original traces.
Dal wrote:OK - we as long as you've tried with another keyboard just to be doubly sure (I've seen similar behaviour). It's going to be something really daft given it got as far as showing the Atari Logo
You may also try resetting the NVRAM (left ALT + CONTROL + right SHIFT + UNDO on boot).
Hippy Dave wrote:I don't think it is crosstalk or the wiring. I would double check the eprom code, and give the board another visual inspection, check for missing capacitors, broken resistors (can be broken in two and not visible -- use dental pick).
exxos wrote:You will read a short because of the caps on the supply rail. Just discharge any old cap, but meter across it, meter will beep until the cap charges enough for the meter to stop beeping. It also can matter which way around your probes go if the caps already have a charge. Try on voltage setting instead
exxos wrote:ST's are more my thing
Though not sure if you said, but you have got a ST-RAM card plugged into your falcon haven't you ? TOS may well bring up the logo without RAM, though it wouldn't be able to do anything much I would imagine.
Also, when the CT60 is unplugged there is a small jumper link you have to put on the connector somewhere (not sure what it does but must be there for a reason lol )
Users browsing this forum: No registered users and 5 guests