Overview Features Instructions Performance Forum Downloads Products OrderV4 Reseller Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Documentation about the Vampire hardware

V1200 ROM Weirdness

Manfred Bergmann

Posts 182
18 May 2020 19:03


Hi.

I have self burned ROMs with 3.1.4 on them.
After booting, even without startup-sequence, the Shell reports with some Vampire ROM strings.
When I try to maprom via Vampire314 it reports a checksum error.

All this results in an empty Workbench screen.

This same procedure works on my V600.
Am I doing something wrong here?
AFAIKT I'm using the latest SAGA drivers.

Manfred


Manfred Bergmann

Posts 182
19 May 2020 07:52


Looking in the latest SAGA package under C folder I think I should be using VampireMap I guess.
I'll give that a try.


Manfred Bergmann

Posts 182
19 May 2020 16:15


So, the latest VampireMap (from SAGA 2.0.1) does report invalid checksum for 3.1.4 ROMs.
How do I map 3.1.4 ROMs.
Or actually, how do I make the V1200 use the installed ROMs?


Gunnar von Boehn
(Apollo Team Member)
Posts 4788
19 May 2020 16:34


Manfred Bergmann wrote:

So, the latest VampireMap (from SAGA 2.0.1) does report invalid checksum for 3.1.4 ROMs.
  How do I map 3.1.4 ROMs.
  Or actually, how do I make the V1200 use the installed ROMs?

Why is there a checksum change?
Did you change the Roms?


Manfred Bergmann

Posts 182
19 May 2020 16:47


Gunnar von Boehn wrote:

Manfred Bergmann wrote:

  So, the latest VampireMap (from SAGA 2.0.1) does report invalid checksum for 3.1.4 ROMs.
  How do I map 3.1.4 ROMs.
  Or actually, how do I make the V1200 use the installed ROMs?
 

  Why is there a checksum change?
  Did you change the Roms?

I'm not sure what you mean.
Does it compare something?


Gunnar von Boehn
(Apollo Team Member)
Posts 4788
19 May 2020 16:51


Manfred Bergmann wrote:

Does it compare something?

You said "checksum does not match" is the error?
So what rom file do you use exactly?
Did you change the ROM?
Or did you not correctly burn them?


Manfred Bergmann

Posts 182
19 May 2020 17:03


Gunnar von Boehn wrote:

Manfred Bergmann wrote:

  Does it compare something?
 

  You said "checksum does not match" is the error?
  So what rom file do you use exactly?
  Did you change the ROM?
  Or did you not correctly burn them?

I'm not sure what the error message suggests.
'Match' what? What does it compare.
Why does it compare something at all?
I use VampireMap to 'maprom' a 3.1.4 ROM by specifying a ROM file.
I've tried the original and a self modified one (intuition-45).

How is the operation of VampireMap related to the inserted ROMs?
However, those are the same that I want to 'maprom'. They do work without the Vampire attached.

Manfred


Gunnar von Boehn
(Apollo Team Member)
Posts 4788
19 May 2020 17:11


Manfred Bergmann wrote:

    Why does it compare something at all?
 

Manfred i would love to help you but  I don't know.
I did not write the tool and not use it.
Maybe Hyperion asked for this?

Maybe you can ask in IRC or slack user channels and find people helping you.
 


Manfred Bergmann

Posts 182
19 May 2020 17:55


No worries Gunnar.
Just trying to understand how this all works.

Is 'VampireMap' not a tool build by the Vampire team?



Henryk Richter
(Apollo Team Member)
Posts 119
19 May 2020 18:42


Manfred Bergmann wrote:

So, the latest VampireMap (from SAGA 2.0.1) does report invalid checksum for 3.1.4 ROMs.
  How do I map 3.1.4 ROMs.
  Or actually, how do I make the V1200 use the installed ROMs?

The Vampire cards load the Kickstart ROM from Flash. Physical ROM chips on the Mainboard are not usable.

Changing the active ROM on Vampire cards requires to either replace the ROM image in the special protected RAM space or to replace it directly in Flash.

When VampireMap (formerly VampireMap314) says "invalid checksum" on the file you've supplied to map, then the file you've tried to load has an invalid checksum because it became corrupt on it's way to your Amiga. Nothing more, nothing less.

Vampiremap (and Vampireflash which shares it's codebase) will accept any valid AmigaOS Kickstart from 1.3 (maybe even 1.2) up to 3.1.4, 3.X or later. Incidentally, every Amiga Kickstart has the same type of checksum: a simple sum over all longwords that needs to end up at $ffffffff when computed over the kickstart content.

Please be aware that I could not include V4 support to these tools because I was never provided with the hardware interface specifications I repeatedly asked for.

And no, I did not write that tool on behalf of anyone. I contributed stuff in my unpaid spare time. Getting dragged into weird conspiracy theories for stuff I did voluntarily is the perfect way of making sure it won't happen again.


Manfred Bergmann

Posts 182
19 May 2020 19:05


Thanks Henryk.

I am just looking for this information. Nothing more, nothing less. :)
Grateful that this tool exists.

This would mean though that my floppy disk is somehow copying not properly.
I need to check on that.


Henryk Richter
(Apollo Team Member)
Posts 119
19 May 2020 19:13


Manfred Bergmann wrote:

  I am just looking for this information. Nothing more, nothing less. :)
  Grateful that this tool exists.

No worries. The last paragraph of my text was not related to your questions.
 

This would mean though that my floppy disk is somehow copying not properly.

I'd advise to pack the files for the transfer (ZIP, LHA etc.) The unpackers do perform checksumming on their own while decompressing. And you save some time copying from/to floppy.

Also, FFS was faster because if left the block checksums out which the old OFS had.


Simo Koivukoski
(Apollo Team Member)
Posts 558
19 May 2020 20:43


Manfred Bergmann wrote:
This would mean though that my floppy disk is somehow copying not properly. I need to check on that.

If you are copying kickrom file into HDD, make sure that you have set MaxTransfer value to 0x1fe00 in HDToolBox. Otherwise all your files in HDD which are bigger than 127.5K will be corrupted.


Sean Sk

Posts 364
20 May 2020 01:27


I also wanted to chime in and say thanks to Henryk for these tools. Since I have been using AOS 3.1.4 these tools have been invaluable to me, so thanks again for maintaining them. Awesome work!


Renaud Schweingruber
(Apollo Team Member)
Posts 330
20 May 2020 08:02


That checksum error happened to me also quite some times and indeed it was because of file corruption. Best way to solve it and make sure file is correctly copied is by packing it with LHA/LZX before copying it and unpacking it on your Amiga.


Manfred Bergmann

Posts 182
20 May 2020 12:50


Is there a tool I can check the calculated checksum with?
I've tried 'SumKick'. But it doesn't calculate $ffffffff, but something else depending on the ROM.



Manfred Bergmann

Posts 182
20 May 2020 16:23


OK, found the problem.

It was indeed the max-transfer value. Changing it to 0x1fe00 and re-transfer the rom image did work then.

Thanks for all the pointers.

posts 17