CodeWarrior Development ToolsのトピックRe: Assembler not legal in CodeWarrior

Assembler not legal in CodeWarrior

sijiahao — Mon, 29 Aug 2016 10:39:50 GMT

Hello,

I have a problem when compiling assembler files using mwasmeppc.exe, this is the error message:

* Compiling s -> o
*
### mwasmeppc.exe Assembler:
#    File: ..\output\obj\cstartup.s
# ---------------------------------
#      88:   e_and2i. r3,0xFFF@l
#   Error:   ^^^^^^^^
#   Instruction not legal for current target processor(s)
### mwasmeppc.exe Assembler:
#      99:   sub r4,r3
#   Error:       ^^^^^
#   Not enough arguments for simplified mnemonic sub
### mwasmeppc.exe Assembler:
#     114:   e_or2i r31,0x4002
#   Error:   ^^^^^^
#   Instruction not legal for current target processor(s)

Some commands( e_and2i. sub e_or2i) can not be recognized, but this file cstartup.s works with other compiler(Greenhills, Windriver, etc)

CodeWarrior version: for MPC55xxMPC56xx v2.10.

MCU: XPC560XB

the cpu type is -proc Zen

I don't know if I miss some compiler options, or I need to include some compiler files?

Best regards,

Sijia

Re: Assembler not legal in CodeWarrior

martin_kovar — Tue, 30 Aug 2016 10:41:54 GMT

Hi Sijia,

I see a few discrepancies which probably are in the code you want to compile:

1) instructions e_and2i and e_or2i are VLE while sub is BookE. It is not possible to compile both types of instructions in one file while you use mwasmeppc.exe.

2) instruction sub has to have three parameters.

There are a few solutions:

1) Best way is to replace sub instruction with se_sub which is VLE and which takes 2 parameters. Do not forget to compile the file with -vle option.

2) You can replace the VLE instructions with BookE instructions and add the third parameter to sub instruction.

Look at the attachment, I am sending you BookE and VLE reference manuals which detail describe all instructions.

If you have any other question, please feel free to write me back.

Regards,

Martin

Re: Assembler not legal in CodeWarrior

sijiahao — Wed, 31 Aug 2016 11:08:29 GMT

Hi,

Thanks for your resolution, now I have another problem about the start code:

The CodeWarrior has its own start file __start.c and __ppc_eabi_init.c,

can I use my own startup code instead of these two files?

CodeWarrior version: for MPC55xxMPC56xx v2.10.

MCU: XPC560XB

Best Regards,

Sijia

Re: Assembler not legal in CodeWarrior

martin_kovar — Wed, 31 Aug 2016 12:32:24 GMT

Hi Sijia,

yes, you can definitely use your own startup instead of CodeWarrior startup files.

Regards,

Martin

Re: Assembler not legal in CodeWarrior

sijiahao — Wed, 31 Aug 2016 12:40:18 GMT

Hi,

OK, but now I can’t generate the right .Map file, do I need to add some link option? Or the .o file is not good?

This is part of the generated map file:

Link map of __entry

Code folded in file: C:\HaoSijia\Projects\498_XPC560XD_XB\test_base\Conformance\IN\Platforms_ConTest_RamNoInit\output\obj\Platforms_ConTest_RamNoInit.o

Code folded in file: C:\HaoSijia\Projects\498_XPC560XD_XB\test_base\Conformance\IN\Platforms_ConTest_RamNoInit\output\obj\main.o

Code folded in file: C:\HaoSijia\Projects\498_XPC560XD_XB\test_base\Conformance\IN\Platforms_ConTest_RamNoInit\output\obj\board.o

…

Best Regards,

Sijia

Re: Assembler not legal in CodeWarrior

sijiahao — Wed, 31 Aug 2016 12:42:05 GMT

Hi,

These are the link options I use:

LINK_OPT += -proc=Zen #mcu type; generic

LINK_OPT += -char=unsigned #set sign of 'char';must match with compiler.Set to unsigned

LINK_OPT += -srec #generate an S-record file with extension .mot

LINK_OPT += -map #generate map file

LINK_OPT += -code_merging=all,aggressive #code merging optimization

LINK_OPT += -far_near_addressing #enable far to near addressing optimization

LINK_OPT += -vle_enhance_merging #enable VLE enhance code merging optimization

LINK_OPT += -vle_bl_opt

LINK_OPT += -abi eabi

LINK_OPT += -gdwarf-2

LINK_OPT += -nostdlib

LINK_OPT += -m __entry

Best Regards,

Sijia

Re: Assembler not legal in CodeWarrior

martin_kovar — Wed, 31 Aug 2016 12:47:45 GMT

Hi Sijia,

do you use CodeWarrior IDE or mwldeppc command line tool for linking?

Reagrds,

Martin

Re: Assembler not legal in CodeWarrior

sijiahao — Thu, 01 Sep 2016 01:57:43 GMT

Hi Martin,

I use the mwldeppc.

Best Regards,

Sijia

Re: Assembler not legal in CodeWarrior

martin_kovar — Thu, 01 Sep 2016 11:17:52 GMT

Hi Sijia,

could you please share the map file which you generated? Why do you think your map file is not correct?

Is it possible for you to share the object files your are trying to link?

Regards,

Martin

Re: Assembler not legal in CodeWarrior

sijiahao — Thu, 01 Sep 2016 12:13:56 GMT

Hi Martin,

These are part of .o file and map file.

Best Regards,

Sijia

Re: Assembler not legal in CodeWarrior

martin_kovar — Fri, 02 Sep 2016 11:24:15 GMT

Hi Sijia,

the MAP file looks incomplete. Do you have any errors while linking the project? Are you able to get .elf file after linking? You shared only one object file, so I am not able to try the linking.

So could you please write me back and eventually could you please share all object files you want to link together?

Regards,

Martin

Re: Assembler not legal in CodeWarrior

sijiahao — Mon, 05 Sep 2016 11:13:40 GMT

Hi Martin,

I modified the lcf file, the project can generate map and elf now.

Now the lcf file still has some errors, when I debug the code using Trace32, it can’t find the startup code, how can I define the srart code(__entry) to the address 0x0?

Another issue is that I can only see assembler in Trace32, do you know how can I see the c files in Trace32?

Best Regards,

Sijia

Re: Assembler not legal in CodeWarrior

martin_kovar — Tue, 06 Sep 2016 10:14:51 GMT

Hi Sijia,

please look at the attachment, I am sending you default linker file from some of my project generated using CW 2.10. You can use it as a guide for your linker file.

About debug information, here is part of documentation, which describes, how to add debug information to your .elf file. I hope this will help. If not, please let me know and i will try different solution.

-------------------------------------------------------------------------------
Debugging Control Options
-------------------------------------------------------------------------------
-g[dwarf]                  # global; cased; generate DWARF 1.x debugging
                             #   information; same as '-sym dwarf-1,full'
-gdwarf-2                  # global; cased; generate DWARF 2.x debugging
                             #   information; same as '-sym dwarf-2,full'
-sym keyword[,...]         # global; specify debugging options
     off                     #    do not generate debugging information;
                             #      default
     on|dwarf-1              #    turn on DWARF 1.x debugging information
     dwarf-2                 #    turn on DWARF 2.x debugging information
   -----------------------------------------------------------------------------------------------------

Regards,

Martin

Re: Assembler not legal in CodeWarrior

sijiahao — Tue, 06 Sep 2016 13:17:55 GMT

Hi Martin,

Thanks a lot.

I have another question about assembler code here https://community.nxp.com/thread/434043 , can you have a look?

Best Regards,

Sijia

Re: Assembler not legal in CodeWarrior

martin_kovar — Tue, 06 Sep 2016 13:50:43 GMT

Hi Sijia,

I posted the "answer" to your other thread. Please check.

Regards,

Martin

Re: Assembler not legal in CodeWarrior

lunaarose65 — Sun, 19 Oct 2025 12:19:42 GMT

It can be tricky when certain tools or functions, like the assembler, aren’t supported in CodeWarrior. For additional guidance or verification on related rules and compliance, resources such as Criminal court data can sometimes provide useful reference points. Exploring alternative approaches or supported modules ensures smoother development. Staying informed about constraints helps prevent unexpected errors and streamlines coding projects.

Re: Assembler not legal in CodeWarrior

FriedrichDibbert — Mon, 20 Oct 2025 10:37:33 GMT

That’s an interesting issue! It might be related to how CodeWarrior handles older assembly instructions or project settings. You can try reviewing compiler configurations and checking whether all assembler paths are properly set. For a clearer understanding of such procedural or legal documentation details, you can visit Miami Dade online cases for reference-style insights on structured processes and case handling. Sometimes, revisiting documentation standards can help pinpoint missing configurations effectively.

Re: Assembler not legal in CodeWarrior

Aria_Skye — Tue, 25 Nov 2025 05:31:40 GMT

It can be frustrating when CodeWarrior throws assembler errors, especially when everything in the syntax seems correct. Sometimes the issue comes down to configuration or missing directives, so double-checking project settings can help. I recently came across Richmond Legal Services while researching documentation accuracy, and it reminded me how important reliable references are in troubleshooting. Hopefully sharing experiences like this helps others get unstuck faster.

Re: Assembler not legal in CodeWarrior

Andrew_Foster — Tue, 02 Dec 2025 11:44:31 GMT

I ran into the same issue trying to use assembler in CodeWarrior and found it quite frustrating. For anyone needing reliable court information, the Will public records can be a helpful resource to check filings and case details. It made navigating certain legal queries much easier without relying on scattered sources. Definitely worth exploring if you want quick access to official records.