MCUXpresso SDK Documentation
Open on Repo Open an Issue
Source (.md/.rst) Page PDF (.pdf)

MCUXpresso SDK Release Notes

MCUXpresso SDK Release Notes#

Development tools#

The MCUXpresso SDK was tested with following development tools. Same versions or above are recommended.

  • CodeWarrior Development Studio v11.2 with CodeWarrior for DSC v11.2 SP1 (Service Pack 1)

Supported development systems#

This release supports board and devices listed in following table. The board and devices in bold were tested in this release.

Development boards

MCU devices

TWR-MC56F8400

MC56F84441VLF, MC56F84442VLH, MC56F84451VLF,
MC56F84452VLH, MC56F84462VLH, MC56F84540VLF,
MC56F84543VLH, MC56F84550VLF, MC56F84553VLH,
MC56F84565VLK, MC56F84567VLL, MC56F84587VLL,
MC56F84763VLH, MC56F84766VLK, MC56F84769VLL,
MC56F84786VLK, MC56F84789VLL

Release contents#

Table 1 provides an overview of the MCUXpresso DSC SDK release package contents and locations.

Deliverable

Location

Boards

<install_dir>/boards

Demo applications

<install_dir>/boards/<board_name>/demo_apps

Driver examples

<install_dir>/boards/<board_name>/driver_examples

Documentation

<install_dir>/docs

Driver, SoC header files, extension header files and feature header files

<install_dir>/devices/<device_name>

Peripheral Drivers

<install_dir>/devices/<device_name>/drivers

Utilities such as debug console

<install_dir>/devices/<device_name>/utilities

Middleware

<install_dir>/middleware

MCUXpresso SDK release package#

The MCUXpresso SDK release package content is aligned with the silicon subfamily it supports. This includes the boards, CMSIS, devices, middleware, and RTOS support.

Device support#

The device folder contains the whole software enablement available for the specific System-on-Chip (SoC) subfamily. This folder includes clock-specific implementation, device register header files, device register feature header files, and the system configuration source files. Included with the standard SoC support are folders containing peripheral drivers, toolchain support, and a standard debug console. The device-specific header files provide a direct access to the microcontroller peripheral registers. The device header file provides an overall SoC memory mapped register definition. The folder also includes the feature header file for each peripheral on the microcontroller. The toolchain folder contains the startup code and linker files for each supported toolchain. The startup code efficiently transfers the code execution to the main() function.

Board support#

The boards folder provides the board-specific demo applications, driver examples, and middleware examples.

Demo application and other examples#

The demo applications demonstrate the usage of the peripheral drivers to achieve a system level solution. Each demo application contains a readme file that describes the operation of the demo and required setup steps. The driver examples demonstrate the capabilities of the peripheral drivers. Each example implements a common use case to help demonstrate the driver functionality.

Middleware#

Motor Control Software (ACIM, BLDC, PMSM)#

Motor control examples.

FreeMASTER#

FreeMASTER communication driver for 32-bit platforms.

Known issues#

This section lists the known issues, limitations, and/or workarounds.

PRINTF issue for program address space#

When project is compiled with SDM, print the address in program address space malfunction.

  • Failed example when SDM

    • PRINTF("%p", main); Root cause: in SDM, %p is treated as 16-bit value, however main in program address space is still considered as 32-bit.

  • Workaround(compliant with SDM and LDM)

    • PRINTF("0x%lx", (uint32_t)main);

Contents