MCUXpresso Config Tool generates peripherals.c with conflicting UART structures

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

MCUXpresso Config Tool generates peripherals.c with conflicting UART structures

Jump to solution
1,374 Views
bgraham
Contributor IV

SDK_2.x_MKL16Z256xxx4

MCUXpresso IDE v10.2.1 [Build 795] [2018-07-25]

In the IDE I used the Config Tool to generate my peripherals.c and peripherals.h files.

When the project is compiled, the structures UART_1_config, UART_2_config, and LPSCI_1_config have compile errors:

../board/peripherals.c:66:4: error: 'uart_config_t {aka const struct _uart_config}' has no member named 'idleType'

../board/peripherals.c:144:4: error: 'lpsci_config_t {aka const struct _lpsci_config}' has no member named 'idleLineType'

I am guessing that the Config Tool is generating code for a version of the SDK that does not match my installed SDK.

How do I sort this out?

Thanks,

Bruce

1 Solution
1,127 Views
bgraham
Contributor IV

I got the latest MKL16Z4 MCUXpresso SDK from the web site. It is shows the

version as 2.2.0. See below

Are you suggesting that I download the SDK for the wrong MCU?

What good will that do me?

Thanks,

Bruce

Hardware Details

Included Part Numbers

MKL16Z256VLH4, MKL16Z256VMP4

Board(s)

FRDM-KL46Z

Device

MKL16Z4

Core Type / Max Freq

Cortex-M0P / 48MHz

Device Memory Size

256 KB Flash

32 KB RAM

SDK Details

SDK Version:

2.2.0 (released 2017-03-21)

Host OS:

Windows

Toolchain:

MCUXpresso IDE

Middleware:

CMSIS DSP Library FatFS USB stack FreeRTOS

View solution in original post

0 Kudos
4 Replies
1,127 Views
bgraham
Contributor IV

My ADC does not appear to work on my MKL16Z with the project setup as a MKL26Z.

I attempted to switch the project back to a MKL16Z by editing the MCU, but that left old MKL26Z files in the project, and did not add MKL16Z files.

How do I switch back to the MKL16Z and an SDK that works with the MKL16Z?

Thanks,

Bruce

0 Kudos
1,127 Views
Robin_Shen
NXP TechSupport
NXP TechSupport

Sorry for my late reply!

It was caused by the version of SDK_2.x_MKL16Z256xxx4 is too old.
The newer SDK of KL26 will not get this error.

idleType SDK KL16 KL26.png

Best Regards,

Robin

 

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

1,127 Views
bgraham
Contributor IV

I switched the project from the MKL16Z to the MKL26Z (MKL16Z is the actual

MCU), and replacing the SDK 2.2.0 with SDK 2.4.1.

This required a lot of changes to the project, but it builds without errors

or warnings.

Thanks for the suggestion.

Bruce

On Tue, Jan 15, 2019 at 8:57 AM Bruce Graham <bgraham@technosofteng.com>

0 Kudos
1,128 Views
bgraham
Contributor IV

I got the latest MKL16Z4 MCUXpresso SDK from the web site. It is shows the

version as 2.2.0. See below

Are you suggesting that I download the SDK for the wrong MCU?

What good will that do me?

Thanks,

Bruce

Hardware Details

Included Part Numbers

MKL16Z256VLH4, MKL16Z256VMP4

Board(s)

FRDM-KL46Z

Device

MKL16Z4

Core Type / Max Freq

Cortex-M0P / 48MHz

Device Memory Size

256 KB Flash

32 KB RAM

SDK Details

SDK Version:

2.2.0 (released 2017-03-21)

Host OS:

Windows

Toolchain:

MCUXpresso IDE

Middleware:

CMSIS DSP Library FatFS USB stack FreeRTOS

0 Kudos