68060 on ACA500 Amiga 500
- Thread starter mjnurney
- Start date
- Replies 110
- Views 27139
)
Not really, sorryI ran my Blizzard1260 on the ACA more than a month ago, but not being able to use kickstart 3.1 is a problem.
BTW: running a BlizzardPPC won't work, so running AmigaOS4.1 in the Amiga 500 is a no go for now... (that would have been a first!)
---------- Post added at 09:40 ---------- Previous post was at 09:40 ----------
Mmmmmm....BlizzardPPC / 060 / BlizzardVision anyone?
Doesn't work, sorry
For now
Until EVERYTHING has been tried (initial thoughts of custom firmware, various settings, modified kickstarts, hacks etc) I don't think that "it doesn't work" is a result to accept 
This IS Amiga, and there is some VERY talented people in the scene...so let's just see...
I have one on the way also, when it's here I will do some tests.
The thing is, if you have an ACA 1220 or 1232 on their, it's more than enough.
Let's face it, what is the point of having 060 or PPC in any Amiga ?
OS4.1 and few PPC games and demo's is the only thing, with the new Cyrus coming, I think that would be a better choice if you really want to get into that.
And for demos, most 060 demos are AGA, so you'll lack the most important thing.
Zeus68k will be a lot better if it really has AGA.
The thing is, if you have an ACA 1220 or 1232 on their, it's more than enough.
Let's face it, what is the point of having 060 or PPC in any Amiga ?
OS4.1 and few PPC games and demo's is the only thing, with the new Cyrus coming, I think that would be a better choice if you really want to get into that.
And for demos, most 060 demos are AGA, so you'll lack the most important thing.
Zeus68k will be a lot better if it really has AGA.
from jens on 1K.org
.. and the statement brings us to a really simple solution, which is unfortunately not occurred to me: you can turn off the CPU in "transparent translation registers" of both data and instruction caches as well as the 060 CPU. The TTR eke the Amiga a nearly unnoticed existence, because they always relate to a 16 MB block.
For the ACA500 but this is ideal because the * entire * lower 16MB block (just the entire A500) is from the perspective of the 68060 non-cacheable, ergo it does not hurt to disable the caches on the way depend on your location. Fastmem is outside, so grab because the caches again, and the B1260 * might * work. Subjunctive, because a matching 68040 library is missing, also retains this setting.
Groundwork for this is already done, coming in the next version of Flash.
Jens
http://www.a1k.org/forum/showthread.php?t=41442&page=3
Here is a beta version for Blizzard owners . The 68040/68060-Karten work, but the library must not be used under any circumstances , otherwise again , the caches are turned on in the lower 16M , and that pops immediately.
You can display the processor to the CPU command , normally turn the caches (which are active only on the local Fastmem the B1260 ), but the Blizzard SCSI module will NOT work , because running out of DMA controller of a fully functioning MMU - and is not there without a 68060.library replacement.
In the ACA500 menu a little more info text is now added to come - but with F10 in the expert menu , or use the TAB key call up the info screen : It is now also checked whether the $ f8 - range over which the ACA500 usually their Residents fades , is covered by the 1200 Turbo card (" shadowed "). In that case , this means that the function of Maprom Blizzard is active, and menu options can not be changed until the next power cycle . We have not yet succeeded in a " Maprom " which is turned on in the Blizzard once off again (hints welcome).
Other changes:
- ICache is now turned on the ROM Unzip , so the unpacking with 32- bit Turbo card is noticeably faster
- If B1260 is found, the unpack routine is placed in the Fastmem this card , which makes the unpacking process rapidly
- Maprom function of ACA12xx card is automatically used so that ACAtune is not needed (which anyway does not work with the ACA500 )
- $ C0 memory is automatically switched on at ACA1230 , so that Execbase is in any case as soon as possible Fastmem - again, no more need for ACAtune
This is an interim release . Tests should be done only if you have created a rescue disk. It might have crept in new errors that make it necessary to go back to an older version back !
The resident- command " acamaprom " also gets another update, so the Maprom function of the Blizzard can be activated ( ie you can load kickstart files) .
.. and the statement brings us to a really simple solution, which is unfortunately not occurred to me: you can turn off the CPU in "transparent translation registers" of both data and instruction caches as well as the 060 CPU. The TTR eke the Amiga a nearly unnoticed existence, because they always relate to a 16 MB block.
For the ACA500 but this is ideal because the * entire * lower 16MB block (just the entire A500) is from the perspective of the 68060 non-cacheable, ergo it does not hurt to disable the caches on the way depend on your location. Fastmem is outside, so grab because the caches again, and the B1260 * might * work. Subjunctive, because a matching 68040 library is missing, also retains this setting.
Groundwork for this is already done, coming in the next version of Flash.
Jens
http://www.a1k.org/forum/showthread.php?t=41442&page=3
Here is a beta version for Blizzard owners . The 68040/68060-Karten work, but the library must not be used under any circumstances , otherwise again , the caches are turned on in the lower 16M , and that pops immediately.
You can display the processor to the CPU command , normally turn the caches (which are active only on the local Fastmem the B1260 ), but the Blizzard SCSI module will NOT work , because running out of DMA controller of a fully functioning MMU - and is not there without a 68060.library replacement.
In the ACA500 menu a little more info text is now added to come - but with F10 in the expert menu , or use the TAB key call up the info screen : It is now also checked whether the $ f8 - range over which the ACA500 usually their Residents fades , is covered by the 1200 Turbo card (" shadowed "). In that case , this means that the function of Maprom Blizzard is active, and menu options can not be changed until the next power cycle . We have not yet succeeded in a " Maprom " which is turned on in the Blizzard once off again (hints welcome).
Other changes:
- ICache is now turned on the ROM Unzip , so the unpacking with 32- bit Turbo card is noticeably faster
- If B1260 is found, the unpack routine is placed in the Fastmem this card , which makes the unpacking process rapidly
- Maprom function of ACA12xx card is automatically used so that ACAtune is not needed (which anyway does not work with the ACA500 )
- $ C0 memory is automatically switched on at ACA1230 , so that Execbase is in any case as soon as possible Fastmem - again, no more need for ACAtune
This is an interim release . Tests should be done only if you have created a rescue disk. It might have crept in new errors that make it necessary to go back to an older version back !
The resident- command " acamaprom " also gets another update, so the Maprom function of the Blizzard can be activated ( ie you can load kickstart files) .
Last edited:
I've already tested the new firmware - the 1260 works now, but a new 060library is needed.
thanks Mike.
me too , just done it. Does the Blizzard 060 libs work?
---------- Post added at 17:46 ---------- Previous post was at 17:44 ----------
Flash update: files on next post
me too , just done it. Does the Blizzard 060 libs work?
---------- Post added at 17:46 ---------- Previous post was at 17:44 ----------
Flash update: files on next post
Last edited:
flash pics and file.
Copy unzipped file to your CF card and run the flash up date tool from the advanced menu.
( create a flash recovery disk first)
Copy unzipped file to your CF card and run the flash up date tool from the advanced menu.
( create a flash recovery disk first)
Attachments
Last edited:
Okay
So the new firmware allows booting into 3.1 Workbench but it then reboots as though the 060 libs are wrong or something else is.. if i boot with no startup sequence then i can get into workbench but obviously SYSinfo crashes the system ...
on a clean CF WB install , it loads up okay and runs very quick. however sys info or sys speed still crashes it.
mike
So the new firmware allows booting into 3.1 Workbench but it then reboots as though the 060 libs are wrong or something else is.. if i boot with no startup sequence then i can get into workbench but obviously SYSinfo crashes the system ...
on a clean CF WB install , it loads up okay and runs very quick. however sys info or sys speed still crashes it.
mike
Last edited:
at the moment any Blizzard tool crashes the system. anything that seems not too taxing is working okay.
a vanilla 3.1 install is the only to get my one working , so no WHDload or demos at the mo...
i'll continue playing
a vanilla 3.1 install is the only to get my one working , so no WHDload or demos at the mo...
i'll continue playing
Toni.Wilen
Member
It runs fine as long as you don't run any programs that touch MMU or TTRs (transparent translation registers) or it will immediately hang the system because they restore original and incompatible cache settings for lowest 16M of address space. Also FPU is disabled and can't be used.
68040/060 library update or patch is needed that keeps lowest 16M totally uncacheable (for both data and instruction caches).
btw, "C:CPU cache" can be used to enable data caches (noticeable speed increase) but it will break SCSI expansion because it is DMA and DMA controllers require proper MMU tables with 68040 or 68060 CPUs.
68040/060 library update or patch is needed that keeps lowest 16M totally uncacheable (for both data and instruction caches).
btw, "C:CPU cache" can be used to enable data caches (noticeable speed increase) but it will break SCSI expansion because it is DMA and DMA controllers require proper MMU tables with 68040 or 68060 CPUs.
Last edited:
