Overview Features Coding ApolloOS Performance Forum Downloads Products Order Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.
Please visit our Apollo-Discord Server for support.



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Documentation about the Vampire hardware

FastRam Broken On My Vampire 600 V2

Bart Mikulski

Posts 101
31 May 2018 09:25


So, finally I found what is broken in my Vampire.
 
  The first picture shows an error from MBRTest-2. This is strange, because the error appears only when I do the test launching MBRTest-2 with 128MB Icon. With the main icon, all the tests went OK for many cycles.
 
  The second picture shows what happens when I want to fill up RAM completely. It always stops at the same point with the same error.
 
  EXTERNAL LINK 
 
  What causes this? Bad RAM chips?


Martin Soerensen

Posts 232
31 May 2018 09:49


Are you running MBRTest-2 from a clean boot? It could well be caused by some bad software, but if you get the same errors from a clean boot disk only containing MBRTest-2, then it looks to me like either your Vampire is faulty due to hardware error or a bad FPGA flash. It could probably also be related to the power supply if that is bad somehow.


Bart Mikulski

Posts 101
31 May 2018 09:52


Martin Soerensen wrote:

  Are you running MBRTest-2 from a clean boot? It could well be caused by some bad software, but if you get the same errors from a clean boot disk only containing MBRTest-2, then it looks to me like either your Vampire is faulty due to hardware error or a bad FPGA flash. It could probably also be related to the power supply if that is bad somehow.
 

 
  I launch MBRTest-2 as the first program after boot. I don't suppose the PSU is an issue, I tried 3 of them, the same RAM-wise behaviour.


Gunnar von Boehn
(Apollo Team Member)
Posts 6207
31 May 2018 10:51


You have _no_ hardware error.
 
Your VAMP has a total of 128 MB memory.
Of this some memory is reserved / in use and protected by the Kickstart after Power-On.
 
This means the memory region $0FEx.xxxx is NOT available for the OS.
If your MBTEST does include this in the test - then this is an SW or user error.
 
 


Bart Mikulski

Posts 101
31 May 2018 11:03


Gunnar von Boehn wrote:

  You have _no_ hardware error.
   
    Your VAMP has a total of 128 MB memory.
    Of this some memory is reserved / in use and protected by the Kickstart after Power-On.
   
    This means the memory region $0FEx.xxxx is NOT available for the OS.
    If your MBTEST does include this in the test - then this is an SW or user error.
   
   
 

 
  Wouldn't that be related to the 194X Deluxe glitches you were helping me solve?
 
  EXTERNAL LINK 
 
  And also to the ShapeShifter issue:
 
  1) ShapeShifter finally runs, but there is this bizarre issue. Depending on how much RAM I set for it to use, it will run or not.
 
  10 meg - 60 meg RAM - it runs,
  60 meg - 80 meg RAM - doesn't run, freezes at splash screen
  81 meg ram - max meg RAM - it runs.
 

posts 5