Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
amigaos314 [2019/08/21 10:09]
bax [MapROM on Apollo-Core FPGA Cards]
amigaos314 [2019/11/13 09:00] (current)
bax
Line 10: Line 10:
   * Minimum Gold 2.10   * Minimum Gold 2.10
   * AmigaOS 3.1.4 ROM image purchased from Hyperion or a reseller   * AmigaOS 3.1.4 ROM image purchased from Hyperion or a reseller
-  * VampireMAP314 and VampireFlash314 copied to C: ([[http://​www.apollo-accelerators.com/​files/​AOS314VampireTools.lha|download]])+  * VampireMAP314 and VampireFlash314 copied to C: ([[http://​www.apollo-accelerators.com/​files/​AOS314VampireTools.lha|v1.2 download]], or v1.4 Beta update {{ ::​vampireflashmapv14.zip |}})
  
-Suitable ROM images are the A1200, A500 or A600 releases. Other variants have not been tested by the team.+Suitable ROM images are the A1200, A500 or A600 releases. Other variants have not been tested by the team. Please note that Core flashing is not yet enabled/​supported on Vampire V4 standalone (as of version 1.4). Use the MapROM variant in the meantime.
  
 ===== MapROM on Apollo-Core FPGA Cards ===== ===== MapROM on Apollo-Core FPGA Cards =====
Line 33: Line 33:
   C:​VampireFlash314 Devs:​Kickstarts/​kick.a1200   C:​VampireFlash314 Devs:​Kickstarts/​kick.a1200
  
-Please replace the example path of the Kickstart image by the actual location on your harddrive. The tool will need about 5 minutes to compress the Kickstart image after a quick verification of Flash chip type and Kickstart location within it. The flashing may commence after the compression was finished. Please confirm the flashing procedure with YES (as shown, in caps), followed by Return.+Please replace the example path of the Kickstart image by the actual location on your harddrive. The tool will need about 5 minutes to compress the Kickstart image after a quick verification of Flash chip type and Kickstart location within it. The flashing may commence after the compression was finished. Please confirm the flashing procedure with YES (as shown, in caps), followed by <key>Return</​key>​.
  
 You need to power-cycle your Amiga after flashing. You need to power-cycle your Amiga after flashing.
Line 60: Line 60:
  
 The same procedure applies if you have an A500/​600/​2000 image. The only difference is that you have to load the appropriate preset in that case. The same procedure applies if you have an A500/​600/​2000 image. The only difference is that you have to load the appropriate preset in that case.
 +
 +==== Kickstart 1.3 with SCSI.device ====
 +
 +While the tool is named "​VampireMap314",​ it's actually not limited to the specific AmigaOS ROM release that it's file name would probably ​ imply. The Kickstart modules for the extended features of the Vampire have also been successfully tested with ROM images of Kickstarts 1.3, 2.0, 3.0, 3.1, 3.9 and various releases of Cloanto'​s 3.X.
 +
 +The Kickstart 1.3 ROM does not contain a scsi.device driver. There is, however a patch available on [[http://​aminet.net/​package/​util/​boot/​kick13scsipatch|Aminet]] that will either build a special scsi.device enabled 1.3 ROM image or a 1.3-sepecific scsi.device for use with Remus. It's assumed further on that the latter variant was chosen (i.e. a patched scsi.device was built).
 +
 +Start Remus and enter the Settings tab. Specify a $F80000 ROM type but set the size to 256k, Image type "​normal"​.
 +{{::​remus_basicsettings.png?​direct|}}
 +
 +In the next step, put a "ROM header"​ first into the ROM contents list. You'll find a suitable ROM header in the Remus distribution,​ as well as the Kick13ScsiPatch archive. ​ The second module you need to add is the scsi.device itself. Save your project, compile a ROM image and that's it.
 +{{::​remus_extrom.png?​direct|}}
 +
 +(Note: please don't mind the FC file name suffix to RomHeader in the example picture. VampireMap314 will take care of the correct values in the ROM header. It just has to be present.)
 +
 +Next, call VampireMap314 with the Kickstart file, followed by the "​extrom13"​ option whose argument is the name of the newly built Kick1.3 extension ROM. Make sure you have a drive connected that'​ll actually be 1.3 compatible. In the example below, the WB1.3 was booted from the default Kick for the mapping procedure.
 +{{::​kick13_maprom.jpg?​direct&​600|}}
 +
 +Kickstart 1.3 after booting from CF-Card
 +{{::​kick13_booted.jpg?​direct&​600|}}
 +
Last modified: le 2019/08/21 10:09