I tried a quick sanity check using Blizkick to run the OS3.2 ROM image in a A3000D with CSmk2 060, it works fine. Can't see any reason why the physical ROMs wouldn't work unless there was a problem with how they were written, or the two ROMs are exchanged. The word-swapped EPROM binaries on the OS3.2 CD appear to be slightly mis-named, but the contents is correct otherwise. i.e. if you recombine them and swap words, the resulting binary is the same as the A3000 ROM.
There's no harm in exchanging U180/U181 as there's a reasonable chance your physical ROMs have been mis-labeled. So do give that a try, take care that pin 1 of the ROM matches that of the socket.
Shouldn't make any difference if the EPROMs are in a A3000T or A3000D. The same ROMs should work in the A3000D, but you'll have to install them into the tower (adapter) PCB.
Unfortunately there's no easy way to tell if the ROMs have been written incorrectly without access to an EPROM programmer to check the contents of them.
A quick sanity check you can do is repeatedly press the caps lock key. If the LED sticks (usually on) after 10 or so presses, it means the system isn't running at all; i.e. it's not reading in the keyboard serial data. If the LED does turn on and off reliably, then the system is running (ROMs are working); though it's potentially waiting forever for scsi.device for some reason, or something else.
If you get stuck caps lock LED with the OS3.2 ROMs installed as you'd expect, or with U180/U181 positions exchanged, then there's most likely an issue with the data programmed into the EPROMs, in which case you'll need to return them.
In case you get stuck with the ROMs, send me a private message and I can put you in contact with someone local to you who can check the EPROM contents.
