Quote:
Originally Posted by aros-sg
Maybe this copper/blitter bug. From quick search in forums: "If the copper is WAITing and the blitter is running and the CPU touches COPJMP to strobe the address of a new copper list into the copper's instruction pointer, a blitter channel pointer can be updated instead.". So try blit wait, before starting copper list.
|
Quote:
Originally Posted by ross
Are you forcing the copper list to restart by writing in COPJMP (see previous message from aros-sg)?
It is not recommended for several reasons, unless you know what you are doing.
|
Just to add my 2 cents on this one: aros-sg & ross speak volumes of wisdom here!
I recently had a sporadic bug on real hardware that did not occur on emulation and it was exactly this. I was well aware of the COPJMP strobe bug, but even so I managed to forgot that the Blitter could still be running at the time in my code where I wrote to COPJMP with the CPU.
It's best to make 100% sure that any CPU write to COPJMP is done in such a way the Blitter can't be running. Or bad things might happen.