+Andrew Davie Posted January 26 Share Posted January 26 2 minutes ago, Thomas Jentzsch said: Got you. I figure if the ARM code should take longer than 4096*2 6502 cycles (~450,000 ARM cycles), one could split this execution into multiple slices, right? Yes, this is what I do. I use the ARM timer to figure out how many cycles of ARM have been used, and abort back to servicing the BUS if the VB or OS time are close to expiring. It's not as nice as having a separate CPU to do ARM stuff, but it's functional enough if you structure your systems to work in discrete chunks like we did in BD. 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.