ACA1233n with ACA500plus possible boot bug ?

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.

Don't Panic. Please wash hands.
  • Jens,


    Before plugging on of my ACA1233n (26 and 40MHz versions), I was running stable 28MHz on my ACA500plus, everything working just fine.

    When plugging in the ACA1233n and using it inside the ACA500plus boot menu, everything works fine as well (26Mhz or 40MHz depending on the card I have.


    The issue arises when I chose to disable the ACA1233n in the boot menu, returning the Amiga to the host 68000 processor. The machine does not boot in 28MHz at all (it gives a 'D9' error on the DiSMo). When I use 21MHz, it boots just fine, and when inside workbench, I can press the DiSMo button to increase the speed back to 28MHz and everything works ok.


    I have tried this in both my ACA1233n cards and also on different A500 machines and all reproduce the same problem.


    Any ideas?

  • Any ideas?

    Sounds like a power issue; the ACA1233n still consumes some power even if switched off, and if you have a power supply without cable drop compensation (AFAIK only the original Commodore PSUs have that), you may have a slightly lower voltage at the chips and overclocking is therefore not possible any more.



    When I use 21MHz, it boots just fine, and when inside workbench, I can press the DiSMo button to increase the speed back to 28MHz and everything works ok.

    The good nes is that it does what it was originally advertised to do: Run stable at 21 MHz. I take it that under heavy load or when the floppy drive starts working (i.e. when power consumption rises), the system will become unstable again.

  • The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.