NXP Semiconductors MKW36Z512xxx4 Series User manual

© 2018-2019
Migration Guide from MKW36Z512xxx4 to
MKW35Z512xxx4
1.Introduction
This document describes how to migrate from Kinetis
MKW36Z512xxx4 to MKW35Z512xxx4
microcontrollers emphasizing in connectivity software. In
this document MKW36Z512xxx4 and MKW35Z512xxx4
are referred as MKW36 and MKW35 respectively. The
document is intended for software engineers, software
testers, software integrators, and customers designing
their own hardware.
NXP Semiconductor.
Document Number: AN12252
User's Guide
Rev. 1
,
06/2019
Contents
1. Introduction........................................................................1
2. Hardware Considerations...................................................2
2.1. Peripherals Instantiation..........................................2
2.2. MCU On-chip Memory...........................................3
3. Software Development Kit Download and Install..............5
4. Software Migration in IAR Embedded Workbench...........8
4.1. Changes Required in Project Options and Settings.8
5. Software Migration in MCUXpresso IDE........................16
5.1. Changes Required in Project Properties................16
6. Build and Run Bluetooth LE Connectivity Stack Examples
.........................................................................................26

Hardware Considerations
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
2 NXP Semiconductor
2.Hardware Considerations
The MKW35 wireless MCU is pin to pin compatible with MKW36, and almost all peripherals are in
accord in both devices. The main difference between MKW36 and MKW35 microcontrollers is related
to the size and addressing of the On-chip Flash Memory. The Table 1 shows the differences:
Differences between MKW36 and MKW35
Device
512 KB P-Flash
256 KB P-Flash +
256 KB FlexNVM
Capable to
emulate 8 KB
EEPROM
2nd instance of
LPUART
FlexCAN
module
MKW36
X
X
X
X
MKW35
X
2.1. Peripherals Instantiation
KW36/35 devices are pin to pin compatible for both available packages (40-pin QFN and 48-pin
LQFN). MKW35 does not support LPUART1 and FlexCAN, therefore, the signals of the last instances
are not available for multiplexing in this device. Bold alternatives are only included for MKW36
microcontroller.
MKW35/36 instance comparative
Pin Name
ALT0
ALT1
ALT2
ALT3
ALT4
ALT5
ALT6
ALT7
ALT8
ALT9
PTA16
PTA16/
LLWU_P4
SPI1_SOUT
LPUART1_
RTS_b
TPM0_CH0
PTA17
PTA17/
LLWU_P5/
RF_RESET
SPI1_SIN
LPUART1_
RX
CAN0_TX
TPM_
CLKIN1
PTA18
PTA18/
LLWU_P6
SPI1_SCK
LPUART1_
TX
CAN0_RX
TPM2_CH0
PTA19
ADC0_SE5
PTA19/
LLWU_P7
SPI1_PCS0
LPUART1_
CTS_b
TPM2_CH1
PTB0
PTB0/
LLWU_P8/
RF_
RFOSC_
EN/
RF_RESET
I2C0_SCL
CMP0_OUT
TPM0_CH1
CLKOUT
CAN0_TX
PTB1
ADC0_SE1/
CMP0_IN5
PTB1/
RF_
PRIORITY
DTM_RX
I2C0_SDA
LPTMR0_
ALT1
TPM0_CH2
CMT_IRO
CAN0_RX

Hardware Considerations
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
NXP Semiconductor 3
PTB3
ADC0_SE2/
CMP0_IN4
PTB3
LPUART1_
RTS_b
CLKOUT
TPM1_CH1
RTC_
CLKOUT
PTB16
EXTAL32K
PTB16
LPUART1_
RX
I2C1_SCL
TPM2_CH0
PTB17
XTAL32K
PTB17
LPUART1_
TX
I2C1_SDA
TPM2_CH1
BSM_CLK
PTB18
ADC0_SE4/
CMP0_IN2
PTB18
LPUART1_
CTS_b
I2C1_SCL
TPM_
CLKIN0
TPM0_CH0
NMI_b
PTC3
PTC3/
LLWU_P11
RX_
SWITCH
I2C1_SDA
LPUART0_
TX
TPM0_CH1
DTM_TX
SPI1_SIN
CAN0_TX
PTC4
PTC4/
LLWU_P12/
BLE_RF_
ACTIVE
EXTRG_IN
LPUART0_
CTS_b
TPM1_CH0
BSM_DATA
SPI1_PCS0
CAN0_RX
PTC16
PTC16/
LLWU_P0/
RF_
STATUS
SPI0_SCK
I2C0_SDA
LPUART0_
RTS_b
TPM0_CH3
LPUART1_
RTS_b
PTC17
PTC17/
LLWU_P1/
RF_EXT_
OSC_EN
SPI0_SOUT
I2C1_SCL
LPUART0_
RX
BSM_
FRAME
DTM_RX
LPUART1_
RX
PTC18
PTC18/
LLWU_P2
SPI0_SIN
I2C1_SDA
LPUART0_
TX
BSM_DATA
DTM_TX
LPUART1_
TX
PTC19
PTC19/
LLWU_P3/
RF_
EARLY_
WARNING
SPI0_PCS0
I2C0_SCL
LPUART0_
CTS_b
BSM_CLK
LPUART1_
CTS_b
Table 2 is not a full description of the MKW35/36 pinout.
NOTE
There is a change in the number of available digital pins between 40-pin
and 48-pin packages due to different number of pins. For example, in the
48-pin package, there is a total of 25 digital pins while in the 40-pin
package, 18 digital pins are available.
2.2. MCU On-chip Memory
2.2.1 MKW36 Flash Memory

Hardware Considerations
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
4 NXP Semiconductor
MKW36 Flash is partitioned into:
•One 256 KB Program Flash (P-Flash) array divided into 2 KB sectors. Flash address range from
0x0000_0000 to 0x0003_FFFF.
•One 256 KB FlexNVM array divided in 2 KB sectors, flash address range from 0x1000_0000 to
0x1003_FFFF with an Alias memory with address range 0x0004_0000 to 0x0007_FFFF.
FlexNVM memory can be used as Program Flash (P-Flash), Data Flash (D-Flash) and EEPROM
Flash.
Figure 1. KW36 Flash Memory Map
2.2.2 MKW35 Flash Memory
MKW35 Flash does not support FlexNVM nor Alias memory, therefore, Program Flash array increase
to:
•2x256 KB Program Flash (P-Flash) array starting from 0x0000_0000 to 0x0007 FFFF address
divided into 2 KB sectors.

Software Development Kit Download and Install
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
NXP Semiconductor 5
Figure 2. KW35 Flash Memory Map
3.Software Development Kit Download and Install
This chapter provides all the steps needed to download the SDK (Software Development Kit) for
MKW35Z512xxx4 due it is used as starting point to migrate a MKW36 code to MKW35 MCU. Below
are the steps to download the SDK package:
1. Go to MCUXpresso web page (mcuxpresso.nxp.com).
2. Log in with your registered account.
3. Search for “KW35Z” device. Then click on the suggested processor and click on “Build
MCUXpresso SDK”.

Software Development Kit Download and Install
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
6 NXP Semiconductor
Figure 3. Building MKW35 SDK package
4. The next page is displayed. Select “All toolchains” in the “Toolchain / IDE” box and provide
name to identify the package.
Figure 4. Selecting version of SDK
5. Click on the “Request Build” button. This will start the building process of the desired SDK. It
will take few minutes until the system get the package into your profile in MCUXpresso web
page.
6. Once the SDK is ready to download, it is displayed in the MCUXpresso Dashboard as shown in
Figure 5

Software Development Kit Download and Install
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
NXP Semiconductor 7
Figure 5. MKW35 SDK displayed in Dashboard
7. Click on download icon as shown in Figure 5 A new window appears to download the package.
Figure 6. MKW35 SDK displayed in Dashboard
8. Accept the license agreement and save the SDK in your desired location.
9. If MCUXpresso IDE is used, drag and drop the MKW35 SDK zip folder in “Installed SDK’s”
perspective to install the package.
At this point, you have downloaded and installed the SDK package for MKW35Z device.

Software Migration in IAR Embedded Workbench
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
8 NXP Semiconductor
4.Software Migration in IAR Embedded Workbench
This chapter provides all the steps needed to migrate a MKW36 example code to MKW35 MCU in IAR
Embedded Workbench IDE. The Heart Rate Sensor project is used as base in this document because it
has easy to understand example and involves the Bluetooth LE connectivity software stack (included in
SDK).
4.1. Changes Required in Project Options and Settings
In this section “bare metal” version of the project was used, however, the
same steps apply for “freertos” projects. Some paths related to “bm”
projects may differ if “freertos” versions were used.
1. Open the heart rate sensor project located at the following path:
<SDK_root>/boards/frdmkw36/wireless_examples/bluetooth/hrs/bm/iar/hrs_bm.eww
2. Select the project in the workspace and press Alt + F7 to open project options.
Figure 7. Project options window
3. In the General Options/Target window click the icon next to the device name and select the
appropriate device NXP/KinetisKW/KW3x/NXP MKW35Z512xxx4, then click the OK button.

Software Migration in IAR Embedded Workbench
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
NXP Semiconductor 9
Figure 8. Selecting MKW35 device
4. Create a new folder with the name MKW35Z at following paths:
<SDK_root>/middleware/wireless/framework_5.4.2/DCDC/Interface
<SDK_root>/middleware/wireless/framework_5.4.2/DCDC/Source
<SDK_root>/middleware/wireless/framework_5.4.2/LowPower/Interface
<SDK_root>/middleware/wireless/framework_5.4.2/LowPower/Source
<SDK_root>/middleware/wireless/framework_5.4.2/XCVR
Figure 9. Creating MKW35Z folders
5. Copy all files inside MKW36Z folders located at the above mentioned paths and paste in
MKW35Z folders.
Figure 10. Creating the MKW35 files

Software Migration in IAR Embedded Workbench
Migration Guide from MKW36Z512xxx4 to MKW35Z512xxx4, User's Guide, Rev. 1, 06/2019
10 NXP Semiconductor
6. Select the heart rate sensor in the workspace and press Alt+F7 to open project options window.
In C/C++ Compiler/Preprocessor window, rename the paths related to MKW36Z folders to
MKW35Z folders modifying a 5 number instead of 6 in the additional include directories text
box. The results must look similar as shown below:
$PROJ_DIR$/middleware/wireless/framework_5.4.2/LowPower/Interface/MKW35Z
$PROJ_DIR$/../../../../../../../devices/MKW35Z4/drivers
$PROJ_DIR$/../../../../../../../middleware/wireless/framework_5.4.2/DCDC/Interface/MKW35Z
$PROJ_DIR$/../../../../../../../middleware/wireless/framework_5.4.2/XCVR/MKW35Z4
$PROJ_DIR$/../../../../../../../devices/MKW35Z4
$PROJ_DIR$/../../../../../../../devices/MKW35Z4/utilities
Figure 11. Updating the MKW35 files
7. Rename the CPU_MKW36Z512VHT4 macro as CPU_MKW35Z512VHT4 and delete
FRDM_KW36 and FREEDOM macros in defined symbols text box. Click the OK button.