web_hvac_twrk70f120m no compile with parallel build

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

web_hvac_twrk70f120m no compile with parallel build

Jump to solution
677 Views
Microfelix
Contributor IV

hi

 

until now I have been working with CodeWarrior 10.6.

I made a big project with the K70 and MQX 4.0.2.

 

 

Today I would like to update the MQX 4.2 and CodeWarrior upgrade to KDS.

I managed to make it work.

But MEETING OF problems. When it is compiling, times are slow.

Reading forums, I activated "parallel build" but I can not fill. I can not generate the file ".elf". As if it disables the "parallel build" okay.

 

 

There are settings to do?

 

 

Maurizio

Labels (1)
0 Kudos
1 Solution
568 Views
DavidS
NXP Employee
NXP Employee

Hi Maurizio,

The parallel builds for MQX4.2 with KDS is a known issue.  Sorry.

Workaround is to not use parallel builds.

Regards,

David

View solution in original post

0 Kudos
3 Replies
569 Views
DavidS
NXP Employee
NXP Employee

Hi Maurizio,

The parallel builds for MQX4.2 with KDS is a known issue.  Sorry.

Workaround is to not use parallel builds.

Regards,

David

0 Kudos
568 Views
Microfelix
Contributor IV

Thanks David for your quick response.

So I do not waste time.

Question. It 'expected shortly upgrade the KDS?

Advise me to start a new project with KDS or remain for a while 'to Codewarrior?

Thank you

Maurizio

0 Kudos
568 Views
DavidS
NXP Employee
NXP Employee

Hi Maurizio,

Complex answer as MQX4.2 is last Classic version (i.e. standalone) and will only have maintenance updates for bug fixes and not be adding in new features and/or new devices.  It will remain supported for 1 years+.

KDS_3.0/KSDK_1.3 is pretty good and has options for using MQX that is in the KSDK distribution.  This MQX uses the KSDK peripheral drivers and not the same MQX drivers that are in MQX4.2 so a port is an effort.

KSDK_2.0 will be a big change early next year and will not have MQX in it.  Freescale is migrating RTOS efforts to FreeRTOS.

Assuming your device remains K70 then remaining with your current tool environment is best as K70 is not supported in the KSDK as it is a legacy Kinetis device.

Hope this helps.

Regards,

David

0 Kudos