MK40DX256 & MK60DN512 SDK versions

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

MK40DX256 & MK60DN512 SDK versions

1,311 Views
partis
Contributor III

Hi all

When using the SDKs for the MK40DX256 and MK60DN512 devices, I get the following warning/error (and build fails due to differing structures etc):

Unsupported version of the I2C Driver in the toolchain/IDE project. Required: 2.0.5, actual: 2.0.3.

Unsupported version of the UART Driver in the toolchain/IDE project. Required: 2.1.5, actual: 2.1.4.

Unsupported version of the FLEXCAN Driver in the toolchain/IDE project. Required: 2.2.3, actual: 2.2.0.

The SDKs are the latest available v2.2.0, and the MCUXpresso IDE is v11.6.0.

Is there later SDKs hidden away (I cant find any), or a different version of IDE that needs to be used, or a magic setting which needs enabled...?

Thanks in advance

Gary

 

Gary Partis
0 Kudos
Reply
5 Replies

1,299 Views
DanielRuvalcaba
NXP TechSupport
NXP TechSupport

Hi,

Could you please tell me how are you making your project? Are you trying to make some kind of port from another platform or device? Can you please tell me how are you importing the drivers?

A screen capture of the error might be useful.

Best regards, Daniel.

0 Kudos
Reply

1,286 Views
partis
Contributor III

Hi Daniel

Firstly the MEX files are created using MCUXpresso Config Tools version 12.0.

A project is then created in MCUXpresso IDE version 11.6.0, with the MEX file dropped into this.

I have attached the MEX file to this message - it does not contain commercially sensitive information.

Within the MCUXpresso IDE, in I get:

partis_0-1661158751488.png

During compilation, also within MCUXpresso IDE, I get:

partis_1-1661159180874.png

Also, the IDE keeps changing the runtime library to RedLib from NewLib, which also breaks the build as RedLib does not support complex numbers which we require.

Is there a recommended workflow to avoid such problems, or a tweak to a .cproject or .mex file, etc?

Kind regards

 

Gary Partis
0 Kudos
Reply

1,270 Views
DanielRuvalcaba
NXP TechSupport
NXP TechSupport

Hi,

You can use Config Tools directly in MCUXpresso as it follows:

DanielRuvalcaba_0-1661278475411.png

I did the configuration myself with the same pins, peripherals and clocks as in the mex file you attached and I didn’t get any errors.

Could you please try to make the configuration using Config Tools directly in MCUXpresso to see if the errors still appear?

I hope this helps, Daniel.

0 Kudos
Reply

1,243 Views
partis
Contributor III

Hi Daniel

I tried to recreate everything from within IDE only (skipping the Xpresso Tools), but to no avail. Then I came across this:

Latest UART Driver for Kinetis K60 - NXP Community

...which described the same problem but only for UART. I tried this (selecting "add component instance" instead of just clicking on item); and I get the option of which UART version to add. This works.

However, the CAN and I2C drivers dont give this option.

I then reverted to Xpresso IDE 10.0.0 and used Tools v12.0 for MEX editing and also got I2C to work; but still lacks CAN (still complains about versions).

This is obviously a mismatch between design tools and SDK versions, and as the K40 & K60 are older devices, may never be resolved in any new version of the tools.

I'll persist on different tool version permutations until I find something which "ticks all boxes".

Kind regards

Gary Partis
0 Kudos
Reply

1,224 Views
DanielRuvalcaba
NXP TechSupport
NXP TechSupport

Hi,

I tried to replicate your problem without success. I am creating the project from the scratch and using Config Tools from MCUXpresso.

Could you please verify that there are not other SDK versions or projects causing problems in your workspace?

Best regards, Daniel.

0 Kudos
Reply