Cannot build bsp_twrk70f120m. I get error "mingw32-make: *** [Sources/Events_c.obj] Error 1 "

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

Cannot build bsp_twrk70f120m. I get error "mingw32-make: *** [Sources/Events_c.obj] Error 1 "

Jump to solution
1,344 Views
boci
Contributor II

Hello

I have CodeWarrior 10.4.

I downloaded and installed MQX 4.0.2 (latest version today)


I imported board support package for Kinetis K70 from the MQX folder.


When I try to build the  bsp_twrk70f120m, I get  this error  "mingw32-make: *** [Sources/Events_c.obj] Error 1 ".


Can anyone help out and let me know why I cannot build this package??

Thanks.


Boci.

Labels (1)
0 Kudos
1 Solution
700 Views
boci
Contributor II

I found the issue.

Somehow,  (I do not have an explanation how) the Processor Expert created files "Events.c" and "Events.h" under /Sources folder within the bsp_twrk70f120m project.

The strange thing is I do not use the Processor Expert. I must have somehow clicked somewhere.

I removed the files and now I can build successfully. 

I do not get why it was giving me the error above.

I think the error is saying it does not see Events_c. obj file.

However, it does not report any compilation errors on Events.c and Events.h, which I would think would mean that files are ok to compile and thus it would (should have) create an associated object file.

Mark and David, thanks for the help guys.

Boci.

View solution in original post

0 Kudos
5 Replies
700 Views
DavidS
NXP Employee
NXP Employee

Hi Boci,

Close your projects.

Using Windows Explorer goto:

C:\Freescale\Freescale_MQX_4_0_2_GA\config\twrk70f120m\cw10gcc

Drag-n-drop following file into your Project Pane of CW10.5:

twrk70f120m.wsd

This will open the entire RTOS.

<Ctrl>B will build the entire RTOS (or goto the Project pull-down and select "Build All".

Hopefully your error will go away.

If not, please try doing a "clean" of the BSP project and re-try compiling.

Regards,

David

0 Kudos
700 Views
boci
Contributor II

Hello David,

I closed all bsp projects and re-imported them by doing drag and drop as you explained and problem is still there.

I did this several times.

I even reinstalled MQX package completely (did repair).  Still the same issue.

I cleaned and try to rebuild them several times no help.

Any other ideas?

Thank for the help.

Boci

0 Kudos
700 Views
DavidS
NXP Employee
NXP Employee

What are the install paths of MQX and CW10.5?

Hopefully not in Program Folders but in c:\Freescale.

Sent from my iPhone

0 Kudos
700 Views
mjbcswitzerland
Specialist V

Boci

The error that you are seeing is a general make file error. If you open the "console" windows you "may" see why this error occurred, or at least get a little more information.

I also had problems when upgrading form CW10.2 to CW10.5 (possibly the same with CW10.4, but I jumped that) and it was due to a linker script path not being found. The message was however not clear that it was this file but it was at least indicating a problem with not being able to find something.

After some trial and error it was in fact a difficulty with a path that was no longer compatible - origially a path symbol was specified in "" due to the fact that its path had a directory with a space in its name - DOS needs the "" around the path otherwise it stops its search at the space and fails. This solution was OK for CW10.2 but there must be some internal difference in newer versions because it then stopped working and the "" had to be removed.

Maybe you can find something similar?

regards

Mark

0 Kudos
701 Views
boci
Contributor II

I found the issue.

Somehow,  (I do not have an explanation how) the Processor Expert created files "Events.c" and "Events.h" under /Sources folder within the bsp_twrk70f120m project.

The strange thing is I do not use the Processor Expert. I must have somehow clicked somewhere.

I removed the files and now I can build successfully. 

I do not get why it was giving me the error above.

I think the error is saying it does not see Events_c. obj file.

However, it does not report any compilation errors on Events.c and Events.h, which I would think would mean that files are ok to compile and thus it would (should have) create an associated object file.

Mark and David, thanks for the help guys.

Boci.

0 Kudos