Printable View
my 2B 'loses' the apollo from time to time but mostly doesn't boot at all with the apollo in it , then again it doesn't boot withe Apollo not plugged in either :-)
with card set to 040 it usually finds it. with the card set to 060, it rarely finds it or crashes when it does. occasionally it will boot to WB.
my 2B is the newest mobo I've ever used and I'm not impressed , i used to have a 1b i think and had no issues other that libs being a pain..
Quote:
Originally Posted by mjnurney
i had one 2B once,and ive got to say this i would never ever have one again.
there just terrible theres parts missing all over it the floppy dident work properly,pure crap tbh,only good for parts to keep the earlier ones alive;)
once my (new to me) 1D1 arrives i will dispose of this by machine gun and fire oh damn i can't I've already sold it oh well..
i'll have to sort out a capacitor pack and replace them on the board, i'll have look what i need.
mike.
To bring this thread up to date a little..
The Apollo has been a constant royal pain in the ass but light is at the end of the tunnel.
It seems I have been supplied with a 68060 rom which is for
A full fpu/mmu spec card and as I am running an ec @ 75mhz im having a few problems. The Libs and code is incorrect ( I'm told. ) so dear reader tomorrow's project is to dump the firmware on the boot rom and burn a spanky new rom and everything will be wonderful.
Well that's the plan.
Mike.
erm.... mike.... there is only one Apollo 060 ROM... its MMU / FPU agnostic
you might have a corrupt ROM or ROM file however.
the biggest issue at the moment is getting a propper working board, as each apollo has .... shall we ecentricies to work with.
remember...
1. Change the CLKEN jumper (this reduces the hard clock via the F74 to the RAM)
2. Use good 60ns or 50ns FPM RAM if you can find it.
3. Change the Jumper to 040 even when you have the 060 (again this is the memory timing nothing to do with the CPU)
4. Ensure you have a GOOD power supply
but this will be for nought my friend on an unreliable board.
just seems strange that one Apollo board works just fine (50 MHz) and my Apollo doesn't and mine has a EPROM boot rom.
The CPU when in the good Apollo works just fine but in mine it's no go - freezing and total fail at wb screen. Either way a fresh rom code won't hurt. I have no idea what version it is and your right I can see no mention of different rom code for ec / mc / lc or any other.
It's just what the rom supplier said. It will not work on ec CPUs ..
I'll burn a new rom tomorrow :-)
---------- Post added at 01:00 ---------- Previous post was at 00:58 ----------
Psu is 500 watt , clkgen moved as requested. Ram works fine in the other card and as a 68040 setup too.
The only discrepancy I can see is the rom from one card to another
@mike
Ensure that the ROM you are programming is 120ns or faster.
arguably it could be a blerged / garbled rom with dead or defunct cells.
I think I have a fast spare I can program for you (yours for gratis) hit me up on PM
I'll reuse the one that's In. Not sure until I peel the sticker off tho
---------- Post added at 01:22 ---------- Previous post was at 01:01 ----------
From the rom seller:
Please note, the firmware rom is a copy from a 1260 card with a 68060RC50 cpu that has both FPU and MMU. It will not work with EC cpu:s and propably not cpu:s w/o MMU either! (The 75 Mhz EC version of the Apollo 1260 has different libs and firmware) It should however work with a 040 cpu also.
*
Regards,
Per-Gunnar
Well this is fascinating
Now I know Per-Gunnar is pretty much up on his Apollo's.... infact the guy is a bit of a legend around them to be honest...
but this is the first I have ever heard of an EC vairient of the ROM code... as far as I know there is no known difference in ROM.
One could ask Jens at Individual if this is the case, since he owns the rights to the Apollo brand of adapters from ACT.
I suppose the quickest way is just to swap the rom , I'll dump the rom contents and see what version it is...