68332 to CodeFire code migration issue in assembly language

cancel
Showing results for 
Search instead for 
Did you mean: 

68332 to CodeFire code migration issue in assembly language

809 Views
peimeng
Contributor I

I am using CodeWarrior for MCF5234 uP and migrating the 68332’s code to CodeFire. [Question] What is the comment practice/guideline for 68K to coldFire migration? Use both of the PortASM-68K converter and CF68KLibin? If so, then I have a big problem now. After the PortASM-68K conversion, there are some more assembly errors such as

"Error : undefined identifier 'a6' " for asm("movea.l (s,a6),a1"); Perhaps, CF68KLibin may be able to solve this but I can't use the CF68KLibin since it only applicable for ColdFire V3 & V4 whereas my processor is MCF5234 V2… What should I do? Can anyone advice on this?:smileymad: Thanks in advance...

Labels (1)
0 Kudos
1 Reply

94 Views
admin
Specialist II

 pei meng,

Which address mode of the source do you mean by using term "s" in the "movea.l (s,a6),a1" instruction?

Possibly, the error message is caused by the forbidden address mode, or your compiler don't familiar with the given pseudo instruction.

 

Possibly, you mention one of the following address mode of the source, which are permitted in movea instruction of Coldfire V2 (ISA_A):

 

Addressing mode: (d16,Ay)

Mode: 101

Register: Ay

 

Addressing mode: (d8,Ay,Xi)

Mode: 110

Register: Ay

 

Addressing mode: (d16,PC)

Mode: 111

Register: 010

 

Addressing mode: (d8,PC,Xi)

Mode: 111

Register: 011

 

For example, the instruction movea.l (5,%a6),%a1 is compiled successfully with GNU compiler.

 

0 Kudos