I understand your problem now. With that debugger you have a program which supports multiple CPUs and therefore also has parts with opcodes for them.
Difficult, because IRA currently has no means to assign a cpu-setting to specific program regions. It's always for the whole program. I agree that would be a useful addition, though.
A hack to the IRA source you can try:
Code:
--- init.c 26 Apr 2017 20:03:22 -0000 1.9
+++ init.c 6 Oct 2021 15:11:40 -0000
@@ -309,6 +309,8 @@
else
if (!strcmp(&odata[2], "060"))
ira->params.cpuType |= M68060;
+ else if (!strcmp(&odata[2], "0x0"))
+ ira->params.cpuType |= M680x0;
else
ExitPrg("Unknown processor Motorola %c%s", option, odata);
else
Then reassemble with -m680x0. But IRA won't emit the matching MC680.. directives when a cpu-specific opcode was found. It just emits "MC68060" on top, which is wrong. So even in the best case you have to check the reassembled source.
And turn on -a, so you know if a PFLUSHA mnemonic was meant for 68030 or 68060.