CW Development Studio for Freescale MPC55xx version 2.1 - problems compiling sample code

[armadillo]

Hi,

I have some error free demo projects targeting MPC55xx CPU's.
When I click on "make" after starting a project-file, there were reported over 50 errors like the following:

Error   : Use of '*' in statement level assembler is not allowed
Please use a label
(assembler source) line 1     b *+0

Error   : '}' expected
handlers.c line 684   {(asm macro expansion):1}    asm void external_input_int_handler(void) { nofralloc

Error   : undefined identifier 'stwu'
handlers.c line 700      stwu r1,-80(r1) ASM_END_OF_LINE stw r0,8(r1) ASM_END_OF_LINE mfsrr0 r0 ; 

Error   : declaration syntax error
handlers.c line 702        wrteei 1 ASM_END_OF_LINE; 

Error   : undefined identifier 'mfctr'
handlers.c line 704      mfctr r0 ASM_END_OF_LINE stw r0,12(r1) ASM_END_OF_LINE mfxer r0 ASM_END_; 

Error   : identifier 'intc_dispatcher(unsigned long)' redeclared as 'int'
handlers.c line 705      lis r4,intc_dispatcher@ha ASM_END_OF_LINE addi r4,r4,intc_dispatcher@l ASM_END_OF_LINE ; 

Error   : identifier 'intc_dispatcher(unsigned long)' was originally declared as 'void (unsigned long)'
handlers.c line 341   { 

Error   : identifier 'intc_dispatcher(unsigned long)' redeclared as 'int'
handlers.c line 705     _LINE addi r4,r4,intc_dispatcher@l ASM_END_OF_LINE mtlr r4 ASM_END_OF_LINE blrl ASM_END_OF_LINE; 

I use CodeWarrior Development Studio for Freescale MPC55xx version 2.1, build 70520 (Version 2.0 produces the same errors), IDE version 5.7.0, build 2009, main target CPU is MPC5567.


Should something be changed in the compiler settings?
Is it a problem with the linker targets?
Are there some header files missing?

Does anyone have an idea how to resolve this problem?


Thanks,
armadillo


--
Alban Edit: changed text colour so can be read.


Message Edited by Alban on 2007-06-07 09:10 PM

[Voxan]

Hi Armadillo,

looks like inline asm issue...

Please be aware that the Freescale compilers based on the 4.x front end are now using the GCC-style inline ASM syntaxe.

If your exemples were written with CW 55xx v1.5, it is most likely the case that you will have to modify the inline asm to match GCC-style syntaxe.

Hope this helps...

[Voxan]

You can find more information about GCC-Style syntax at http://gcc.gnu.org/onlinedocs/gcc-3.4.0/gcc/Extended-Asm.html#Extended%20Asm

Hope this helps...