Build Error for MC9S12ZVML128_LIN_BLDC_Sensorless using CodeWarrior

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

Build Error for MC9S12ZVML128_LIN_BLDC_Sensorless using CodeWarrior

Jump to solution
1,009 Views
itsnewforme
Contributor IV

I'm trying to build the code MC9S12ZVML128_LIN_BLDC_Sensorless using CodeWarrior IDE. It is giving me the following errors. How to resolve them ?

Description Resource Path Location Type
mingw32-make: *** [src/S12ZVM_system/vector_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/coreapi/lin_common_proto_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/S12ZVM_system/startup_CW/startup_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/S12ZVM_system/startup_CW/mc9s12zvml128_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/lowlevel/lin_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/coreapi/lin_common_api_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/transport/lin_commontl_proto_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/coreapi/lin_j2602_api_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
Invalid project path: Include path not found (C:\Freescale\CW MCU v10.7\MCU\S12lisa_Support\s12lisac\src). MC9S12ZVML128_LIN_BLDC_Sensorless pathentry Path Entry Problem
Invalid project path: Include path not found (C:\Freescale\CW MCU v10.7\MCU\S12lisa_Support\s12lisac\lib_small). MC9S12ZVML128_LIN_BLDC_Sensorless pathentry Path Entry Problem
Invalid project path: Include path not found (C:\Freescale\AMMCLIB\MC9S12ZVM_AMMCLIB_v1.0.2\include). MC9S12ZVML128_LIN_BLDC_Sensorless pathentry Path Entry Problem
Invalid project path: Include path not found (C:\Freescale\CW MCU v10.7\MCU\S12lisa_Support\s12lisac\include). MC9S12ZVML128_LIN_BLDC_Sensorless pathentry Path Entry Problem
mingw32-make: *** [MC9S12ZVML128_BLDC_Sensorless_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** Waiting for unfinished jobs.... MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/diagnostic/lin_diagnostic_service_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/transport/lin_j2602tl_api_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/transport/lin_lin21tl_api_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/coreapi/lin_j2602_proto_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/coreapi/lin_lin21_api_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/coreapi/lin_lin21_proto_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem
mingw32-make: *** [src/LIN/LIN_driver/transport/lin_commontl_api_c.obj] Error 1 MC9S12ZVML128_LIN_BLDC_Sensorless C/C++ Problem

0 Kudos
1 Solution
998 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @itsnewforme,

Which version of the demo SW do you use?

You should find release notes in the installation directory, it specifies compatible CW revisions.

Also, when you download the latest version of the SW, you should use it with the latest Automotive Math and Motor Control Library (AMMCLIB).

 

Regards,

Daniel

View solution in original post

0 Kudos
2 Replies
999 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hello @itsnewforme,

Which version of the demo SW do you use?

You should find release notes in the installation directory, it specifies compatible CW revisions.

Also, when you download the latest version of the SW, you should use it with the latest Automotive Math and Motor Control Library (AMMCLIB).

 

Regards,

Daniel

0 Kudos
992 Views
itsnewforme
Contributor IV

Yes, It was a library issue. Thanks for helping :))

0 Kudos