Boot Diagnostics (Amiga 1200)

below are some steps you can use to try and diagnose no boot or issues during boot minimum boot start off removing all expansion ports, hard drives, floppy and so on, to use just the bare board apply a known working good power supply and check all power rails are stable we will test boot with two main states with diagrom installed in the kickstart with no kickstart installed + pistorm in expansion slot fully configured to boot the goal here is to get to the diagrom boot screen at least, to allow further diagnostics diagrom removable chips to get the diagrom to boot we can remove the following as they are not needed to get to a boot screen all ram (u16/17/18/19) pistorm removable chips to get the pistorm to boot we can remove all of the chips above from the diagrom boot, plus kickstart roms (u6a / u6b) gal16v8 (xu1) the pistorm emulates the following components on the board and effectively bypasses them cpu (u1) although this is still needed to initially run the pistorm it still requires the following to be fully functional ram (u16/17/18/19) adv/vp101 (u30) for video output cias (u3/u8) to interface with externals when you have the pistorm installed, you will get the normal diagrom activity for a few seconds, then the pistorm will restart the amiga and run its own action this means when reading the with pistorm statements below, the with diagrom statements would also run first for a few seconds for example, no ram would be flashing red/green screen for a few seconds (as the diagrom is running) and then solid green once pistorm kicks in if you can boot into pistorm diagrom without real roms installed on the motherboard, but installing roms on the real motherboard then stops the pistorm booting, this is typically the gal16v8 (xu1) with a bad xu1 you can remove the xu1 and the u6a/b roms and use a pistorm to still boot you must have u6a/b empty though otherwise it won't boot, as you will get bus contention between the rom and other ics critical chips as there are many general components that are responsible for boot, such as resistors, capacitors, good traces, crystals, clocks, av connectors, power rails and many things, it is best to focus on the most common and critical chips first when diagnosing below are the components that are absolutely needed to get boot cpu (u1) even if using pistorm, as cpu needs to read from expansion slot adv/vp101 (u30) needed to see anything on screen gal16v8 (ux1) otherwise flickering or no sync general procedure what i typically do to help diagnose issues with not even getting to diagrom boot screen are the following initially, clean the board fully, change the kickstart rom sockets for new turned pin headers to make sure they have good contact as that is a common issue use a known working power supply and av cable remove pistorm and roms from u6a/b so there is nothing in the slots turn on if i see 50/60hz on screen regardless of what's on the screen it that helps to prove in general the power supply, adv/vp101, av cable, receiver tv/monitor are all generally good if this fails and you have no sync on screen at all, then i would check power rails, clocks, crystals, shorts (anything getting hot or rails loading down) and make sure all the board is free from fluff, rot or trace damage firstly after this (getting a signal on screen), i would keep the rom slots empty and add the pistorm to the expansion slot, loaded with the diagrom as the kick rom file https //archbee doc uploads s3 amazonaws com/j28kvka0c jxcfzcoqq29 dqliurnsx780xddgqrazw 20241106 113219 zip if this boots, then run the following tests to confirm functionality of the following chips memory tests dedicated chip mem (checks u16/17/18/19) cia tests test cias (checks u3/u8) this way you know all those chips are good, and the cpu (as it has to work to run the expansion port, although it doesn't need to fully work to run the entire system so it could be partially working) we know also the entire video output circuit then works too in order for it to boot that far, so the adv/vp101 is good too if removing the pistorm and using real diagrom in the kickstart does not work, the likely suspects are the components or traces to them that the pistorm is bypassing rom sockets (u6a/b) or roms themselves, traces to cpu and other chips cpu (u1) traces more likely than actual bad cpu, reflow cpu gayle, alice, budgie, lisa ? (unconfirmed if these are bypassed by pistorm) troubleshooting with the system in the state mentioned above, resort to the table below for hints with diagrom with pistorm possible cause flashing red/green solid green no ram / faulty ram (u16/17/18/19) all black screen (no border) all black screen (no border) bad cpu / kickstart freezes after doing rom checksumtest green lines boots fine ??? black screen then no screen without roms installed, boots, otherwise colored screens gal16v8 (xu1)