linker exit code -1073741819

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

linker exit code -1073741819

1,241 Views
daniel_ebel
Contributor I

Hello,

 

I'm writing a linker script for the MPC5634M. When compiling these scipt I get the following exit code:

### mwcceppc.exe Driver Error:
#   linker
#   'C:\Programme\Freescale\CW_for_MPC55xx_and_MPC56xx_2.7\PowerPC_EABI_Tools\C
#   ommand_Line_Tools\mwldeppc.exe' returned with exit code -1073741819

 

Does everyone knows what this code means???

 

Thank you for your help

Labels (1)
0 Kudos
4 Replies

466 Views
J2MEJediMaster
Specialist I

It looks like the linker is picking garbage up from somewhere and trying to present that as an error code. Did the scripts work before you modified them? If so, what did you change?

 

---Tom

0 Kudos

466 Views
daniel_ebel
Contributor I

I solved the problem with the help of the freescale support (thanks a lot). They showed me an other approach for my solution and now it works. I still don't know what the problem was but that's okay. As lonag as my application is working now :smileyhappy:

 

daniel_ebel

0 Kudos

466 Views
FridgeFreezer
Senior Contributor I

So what was the solution?

0 Kudos

466 Views
jimtrudeau
Senior Contributor I

The suggestion was to refer to the default startup file for guidance to see how it sets up the platform. In this case it was

 

CW_for_MPC55xx_and_MPC56xx_2.7\PowerPC_EABI_Support\Runtime\Src\ __start.c

 

This file allows for user-level initialization before main().  It defines a function called __init_user(). If the program is in C++, __init_user needs to initialize exceptions and static constructors.

So the default startup file will call __init_user().
The user can complete action of startup.

This function is in the __ppc_eabi_init.c file. Placing an  __init_user() function in the __ppc_eabi_init.c file to do specific initialization resolved the problem.

 

There was probably some problem among the startup code used, the lcf file, and the application. By reverting to the "known good" default startup code and initialization, the problem went away.

0 Kudos