42bs Posted June 10, 2022 Share Posted June 10, 2022 (edited) Ok, run into a strange problem, and really out of ideas: I tried "re-compile" JagTris source and it seems there are no more GPU interrupts?! I only activate the Timer Interrupt, and as soon as it fires, the GPU seems to stop. The code seems to be correct as in VirtualJaguar it is running, so there must be something which is different from the real HW. The 68k keeps running and I can dump some value via Skunk and see that the return address is pushed on the stack. Sometimes the interrupt code runs a one or two instructions than it goes off the rails. org $f03020 timer:: .l store r1,(r2) storew r1,(r0) jr .l addq #1,r1 This is the timer code, r0,r1,r2 are preset by the foreground code. R0 = $f00058, r2 is in DRAM. Any idea what could make the GPU turn weird? I first thought it is related to some stuff JagGD is doing, but same behavior with JagGD and Skunk. Edited June 10, 2022 by 42bs Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.