Variables for Vampire not working on V2-1200

larsonmars / sysvars

Setup environment variables that hold system Information to be used for a multi-system startup-sequence

MIT License

10 stars 0 forks source link

Variables for Vampire not working on V2-1200 #10

Closed djbase78 closed 5 days ago

djbase78 commented 1 week ago

Seems I have some problems getting these

-$VampireType:      The type of vampire installed, for example "V2_600", or "V4_Standalone"
- $VampireCoreRev:   The core revision of the currently flashed firmware .jic file; "N/A", if not available (e.g., some beta cores)
- $VampireClockMult: The vampire clock multiplier

to work on my Vampire 1200 (Core 2.17) as they do not report anything. They are working fine on V4_Standalone.

larsonmars commented 1 week ago

Thank you for reporting!

You say they do not report anything, so I take it you mean they are not set. Could you verify that your $CPU variable is "68080" and $Chipset is "SAGA"? Because detecting the 68080 and SAGA is a precondition for sysvars in its current version to even consider querying the mentioned variables.

djbase78 commented 1 week ago

68080 is detected but no SAGA ($Chipset here is AGA). V2 only have RTG but not full SAGA like on V4.

larsonmars commented 1 week ago

Well then this is the culprit... I thought it always has 68080 and SAGA. Then I'm gonna stick with 68080 as a base for Vampire detection... I will prepare a new release.