68000 & 68020 comparaison ? (for GhostsNGhosts temporary freeze)

[CFou!]

Hi guys,

I am working on Ghosts N Goblins whdload's patch.

It seems a problem appears on 68020 running the game on real amiga.

On winuae problem can be reproduct just switching CPU between 68000 and 68020 during execution of game.

I think it's caused by some differences between both CPU and perhaps:
- some 68000 instructions missing on 68020 and >
- some code without effect on 68000 but cause new instructions on 68020
- cpu interuption managment a bit different...

So have you a documentation or table to compare instruction and/or interupt management between 68000 and 68020?

regards,
Bertrand/CFou!

[hooverphonique]

did you check if it's an instruction cache issue?

otherwise, some instructions allowed in user mode on the 000 are only allowed in supervisor mode on 010+

[CFou!]

Originally Posted by hooverphonique

did you check if it's an instruction cache issue?

Originally Posted by hooverphonique

otherwise, some instructions allowed in user mode on the 000 are only allowed in supervisor mode on 010+

I don't think it's my problem.

I thought at self-modifying code in music player code but problem are same if instruction cache are disabled...

The problem is either a sync or freezes on a wait loop interuption because it seems the music player code does not start or started too late the interuption.

I think it may be in music player that 68000 CPU instructions are not understood by the 68020 ... I am looking for ..

For information:
code freezes sometimes on loop:

INTREQR (dff01e) is readed and compared to $200 (bits 9):
->audio channel 2 finished

if equal game continue to run

So code of 68000 music player seems corrupt on 68020+... perhaps by SMC or instruction 68000 badly executed on 68020....

It's for this reason i need instructions & interuptions docs which compare 68000& 68020

[hooverphonique]

what if more int requests happen at the "same time" ? you should "and" the value of intreqr with $200 and check for non-zero instead, otherwise you may loop forever under certain circumstances.. don't know if that's the problem, however..

loop:
move.w $dff01e,d0
and.w #$200,d0
beq loop

also remember to clear the request afterwards..

[CFou!]

Originally Posted by hooverphonique

what if more int requests happen at the "same time" ? you should "and" the value of intreqr with $200 and check for non-zero instead, otherwise you may loop forever under certain circumstances.. don't know if that's the problem, however..

loop:
move.w $dff01e,d0
and.w #$200,d0
beq loop

also remember to clear the request afterwards..

yes it seems problem, it's loop forever but only on 68020 if on winuae i set 68000 cpu indead of 68020 temporary freezes disappear...

but exact code is:
l:
Move.w $1e(a2),d1 ; rem: a2= $dff000
and.w D4,d1 ;rem: D4=$200 in general during freeze..
beq l

[Leffmann]

Sounds like you're looking for the 68000 Family Programmer's Reference Manual, and the 68000 and 68020 User Manuals. You can find them on freescale.com.

[CFou!]

Originally Posted by Leffmann

Sounds like you're looking for the 68000 Family Programmer's Reference Manual, and the 68000 and 68020 User Manuals. You can find them on freescale.com.

thanx

[CFou!]

I think I found the solution but it is a little obscure

apparently three times the query was requested audio interuption (whereas no interest) to the CPU via DMA register INTREQ before going on the waiting loop interuption (to indicate that the wave to be completed play)

suddenly without me really understand yet why, the interupt was not activated when the sound stop and so game freezed on loop waiting interuption...

The CPU seemed disturbed by unnecessary two interupt requests ....

The most amazing is that I have already seen this type of code useless without freeze ...

But it is true that it is Gng is particularly well coded and fully works in 'multitask' with the interuptions (one could even say that it is improper is multitasking)

user mode it nothing happens.

just

t:
bra t:

everything else is multitasking and awaits an interrupt

the main code is in the interuption to address $ 60

in D0 is the value of the function is executed

I hope I was clear ...

what is your opinion about it?