| |
Trap
Registered: Jul 2010
Posts: 222 |
Best practice IRQ recovery
Hi,
Here's a little newbie question. Sorry, I'm still learning this shit and it's really complicated :(
I have kernel off ($01=$35) and I am running IRQ's using the normal $fffe/$ffff vectors.
I want to exit from this and call a prepacked piece of code (in this case something packed with TinyCrunch).
I tried restoring the IRQ vectors and jump to the packer. However, it just hangs. I tried some other things but all gave the same result. The only thing that worked was when I did this:
sei
lda #$36
sta $01
jsr $ff81
jmp unpacker
The problem of course is that it resets the VIC which isn't really great for my situation.
So, my question:
What is the correct/proper way to exit from a part and go to the next? preferably not using kernal routines :|
Thank you.
Trap |
|
... 78 posts hidden. Click here to view all posts....
|
| |
Trap
Registered: Jul 2010
Posts: 222 |
It crashes before it gets to the unpacking |
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Set a breakpoint at unpacker and then step through the code and see where it crashes? There's no one answer here, it makes some assumption about things and you'll have to figure out what it is. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11089 |
the first thing that comes to mind is... don't use SEI. disable the irq sources instead. then set the pointers to their defaults. |
| |
Krill
Registered: Apr 2002
Posts: 2821 |
Without further information, my bet is on pending interrupts that wreak havoc as soon as the I flag is cleared. =)
Then wrong vectors/memory configuration usually cause crashes, or with the ROM interrupt handler restored, an infinite IRQ-handling loop (as the ROM interrupt handler only acknowledges CIA1 interrupts, but not VIC interrupts).
Bottom line being that properly disabling any interrupt sources (not just executing SEI) is good practice for cleanly exiting a demo part (in a classical spacemo, that is).
Edit: Oh yeah, what Groepaz said. :D |
| |
Trap
Registered: Jul 2010
Posts: 222 |
Well, I'm just learning stuff right now :)
ok, I will re-visit setting the IRQ vectors back. What would be the perfect sequence for this?
Should I just modify the running IRQ code to go to the default IRQ handler and then wait a few frames for it to catch it? |
| |
Krill
Registered: Apr 2002
Posts: 2821 |
It's common practice to check for space during an interrupt handler that's executed once a video frame. The I flag is usually still set (because you're in an interrupt) and the interrupt itself was triggered by VIC.
When detecting the keypress, just write 0 to $d01a to disable any VIC interrupts, then write $ff to $d019 to acknowledge any pending VIC interrupts. Resetting any interrupt vectors should not be required. Directly exit to whatever code to unpack and run the next part. |
| |
Trap
Registered: Jul 2010
Posts: 222 |
So
set IRQ vector to default handler
$d01a=0
$d019=$ff
wait a frame or two
go to unpacker
Is that what you meant? |
| |
Krill
Registered: Apr 2002
Posts: 2821 |
Resetting IRQ vectors or waiting shouldn't be required, but should be no harm. It's just unnecessary. :) |
| |
Oswald
Registered: Apr 2002
Posts: 5017 |
my guess is that depacker overwrites your irq code, and on the next irq request cpu tries to jump into that. simply set irq vector to a new piece of irq handler which surely is undisturbed. |
| |
Flavioweb
Registered: Nov 2011
Posts: 442 |
I guess something overwrite $0314/5 before setting $01 to $36.
Force it back to $EA31 (or $EA81) (and may be better to restore other vectors too) insted of call $FF81.
Clear VIC IRQs enable flags too. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 - Next |
