MCUXpresso SDK

Overview

Overview

MCUXpresso SDK is a comprehensive software enablement package designed to simplify and accelerate application development with Arm® Cortex®-M-based devices from NXP, including its general purpose, crossover and Bluetooth™-enabled MCUs.

Previously user should get MCUXpresso SDK via mcuxpresso.nxp.com or MCUXpresso IDE. Now NXP MCUXpresso SDK project provides a new way for user to achieve this. You could find all NXP hot parts in this project and get below features:

  • Arm® CMSIS-CORE startup and device header files and CMSIS-DSP standard libraries
  • Open-source peripheral drivers that provide stateless, high-performance, easy-to-use APIs
  • Drivers for communication peripherals also include high-level transactional APIs for high-performance data transfers
  • High-quality software: all drivers and startup code are MISRA-C: 2012 compliant and checked with Coverity® static analysis tools
  • Software examples demonstrating the usage of peripheral drivers

Other features like RTOS support and middleware stacks currently are not demonstrated in this project. If you are interest in these features please go mcuxpresso.nxp.com to find full SDK support.

Releases

There are two types of release in the project. The MCUXpresso SDK release and GitHub Main SDK release. Below description uses MCUX release short for MCUXpresso SDK release, use Main release short for GitHub Main SDK release.

MCUX Release

The MCUX release launches once a new release is available on SDK Builder. Users previously using SDK Builder could easily find the exact same code base MCUX release with same 2.x.y version of SDK archive package, software examples build/run quality are guaranteed in the release. MCUX releases will be prefixed with 'MCUX_', and every release will be merged into main branch to ensure main branch has all released boards/socs support.

The "MCUX_" releases are categorized into mainline releases and NPI release.

  • For mainline releases, usually it's planned twice a year to do a global feature update for NXP hot parts. The x in 2.x.y version increments each time a mainline release goes out.
  • For NPI release, it aims to support a new soc product recently launched in the market. It is built with verified features in previous mainline release. The release name is suffixed with NPI name to identify it's an NPI release.

Each MCUX release is made on previous mainline release tag/NPI release tag, thus user could easily check the difference between two releases using git diff command.

Main Release

The Main release is a regular release made in main branch. It releases the latest code base and feature set on main branch, which is expected to include all the previous 'MCUX_' release content and new enablement on main branch for NXP hot parts. Main releases will be prefixed with 'MAIN_'.

Below figure takes 2.9.0 and 2.10.0 release as an example to show the relationship between MCUX release and Main release. Release Introduction

Supported development tools and systems

  • Tools

    • MCUXpresso IDE
    • GCC ARM Embedded

    For version of the tool used, please check the release notes in each release.

  • Systems

    See Supported development systems for the list of boards/socs currently support in this project.

Getting Started

See Getting Start Guide to start explore the project.

License

All SDK drivers, components, device support files, board support files and driver examples in this project are under BSD-3-Clause license, license copy please check COPYING_BSD-3. The ARM CMSIS component is under Apache License 2.0, license copy check Apache License 2.0. License information for all components could be found in SW-Content-Register.txt

Contribution

Contributions are greatly welcomed! For detail guideline of contribution please check Contribution Guide.

Issues
  • Support for multichannel SAI EDMA transfers

    Support for multichannel SAI EDMA transfers

    Prerequisites

    • [x] I have checked latest main branch and the issue still exists.
    • [x] I did not see it is stated as known-issue in release notes.
    • [x] No similar GitHub issue is related to this change.
    • [x] My code follows the commit guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.

    Describe the pull request

    Currently API for SAI EDMA transfers assumes that audio data can only be interleaved (e.g. sent via a single wire I2S0_TXD0) but for example K66/K26 MCUs support output of non-interlieved audio using 2 wires via the I2S0_TXD0 and I2S0_TXD1 pins.

    The proposed change allows to send non-interlieved data using SAI EDMA mechanism. In our case this method works successfully for transmitting native DSD non-interlieved data to ESS Technology audio DACs (ES9218P, ES9038Q2M).

    Type of change (please delete options that are not relevant):

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Tests

    • Test configuration (please complete the following information):
      • Hardware setting: K66/K26, ES9218P or ES9038Q2M
      • Toolchain:
      • Test Tool preparation:
      • Any other dependencies:
    • Test executed Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
      • [ ] Build Test
      • [x] Run Test: connect I2S0_TXD0 and I2S0_TXD1 pins of MCU to the receiver (audio DAC) that accepts non-interlieved input.
    opened by dmitrykos 16
  • zephyr: Fill the device and driver support gap in mcux-sdk

    zephyr: Fill the device and driver support gap in mcux-sdk

    • Add missing device support for K8x, KE18F, KL25Z, KW2x, KW3x and KW4x. Reuse files in hal_nxp.
    • Add lpsci driver which is needed for KL25Z.

    Signed-off-by: Susan Su [email protected]

    Prerequisites

    • [x] I have checked latest main branch and the issue still exists.
    • [x ] I did not see it is stated as known-issue in release notes.
    • [x] No similar GitHub issue is related to this change.
    • [x] My code follows the commit guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.

    Describe the pull request

    A clear and concise description for the change in this Pull Request and which issue is fixed.

    Fixes # (issue)

    Type of change (please delete options that are not relevant):

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [x] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Tests

    • Test configuration (please complete the following information):
      • Hardware setting:
      • Toolchain:
      • Test Tool preparation:
      • Any other dependencies:
    • Test executed Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
      • [x] Build Test
      • [ ] Run Test
    opened by mcuxsusan 14
  • fsl_i2c.c: Clearing the NAK flag prevents scan.

    fsl_i2c.c: Clearing the NAK flag prevents scan.

    The following code lines (1068ff) clear the NAK flag on the last byte before checking.

        /* For the last byte, nack flag is expected.
           Do not check and clear kLPI2C_MasterNackDetectFlag for the last byte,
           in case FIFO is emptied when stop command has not been sent. */
        if (handle->remainingBytes == 0U)
        {
            status &= ~(uint32_t)kLPI2C_MasterNackDetectFlag;
        }
    

    That interferes with an attempt to scan the I2C bus for addresses, when just a single byte is sent and the NAK flag returns essential information. This part of the code sneaking in between 2019 and 2020. It works wirth the 2019 code and if I simply drop this check. So what was the reason to introduce it, and for that case, is is feasible to do that check only for messages of length > 1?

    bug 
    opened by robert-hh 12
  • [BUG] Using the MCUX SDK as a library seems to not add boot header

    [BUG] Using the MCUX SDK as a library seems to not add boot header

    Describe the bug I had added a PR a while back which makes the include headers public so that the mcux sdk components could be used as a library instead of "decorating" an executable. This allows for multiple binaries to have the library linked in the same CMake file. When we do that, it seems that the boot header isn't properly inserted and the image won't flash.

    To Reproduce

    • Environment (please complete the following information):
      • Tag/Commit hash: latest
      • Toolchain: gcc-arm-none-eabi-10-2020-q4-major
      • Board/SoC: mimxrt1060
      • Example: own
    • Steps to reproduce the behavior:

    Example CMake here with the issue. You can maybe try doing what is here with samples in your sample repo and just build the mcux as a library. Then link it to two samples.

    # Copyright (c) Microsoft Corporation. All rights reserved.
    # SPDX-License-Identifier: MIT
    
    # set parent scope path
    set(BOARD_DEMO_CONFIG_PATH ${CMAKE_CURRENT_SOURCE_DIR}/config CACHE INTERNAL "Config path")
    set(BOARD_DEMO_FREERTOS_PORT_PATH ${FreeRTOS_ARM_CM4F_PATH} CACHE INTERNAL "FreeRTOS Port used ")
    
    # Define
    add_definitions(-DFSL_FEATURE_PHYKSZ8081_USE_RMII50M_MODE=1 -DSDK_DEBUGCONSOLE=1 -DSDK_DEBUGCONSOLE_UART -DLWIP_DHCP=1 -DLWIP_DNS=1 -DUSE_RTOS=1 -DFSL_RTOS_FREE_RTOS -DLWIP_TIMEVAL_PRIVATE=0 -D__STARTUP_CLEAR_BSS -D__STARTUP_INITIALIZE_NONCACHEDATA)
    
    include(${CMAKE_CURRENT_SOURCE_DIR}/gcc_flags.cmake)
    
    set(MCUX_SDK_PROJECT_NAME mcux-sdk-lib)
    
    add_library(${MCUX_SDK_PROJECT_NAME})
    target_include_directories(${MCUX_SDK_PROJECT_NAME}
      PUBLIC
        ${BOARD_DEMO_FREERTOS_PORT_PATH}
    )
    target_link_libraries(${MCUX_SDK_PROJECT_NAME}
      PUBLIC
        FreeRTOS
    )
    
    nxp_mcux_sdk_fetch()
    lwip_fetch()
    
    list(APPEND CMAKE_MODULE_PATH ${NXP_MCUX_SDK_PATH})
    
    find_package(LWIP)
    
    include_directories(${BOARD_DEMO_CONFIG_PATH})
    include_directories(nxp_code)
    include_directories(nxp_code/lwip)
    
    file(GLOB NXPCODE_SOURCES nxp_code/*.c nxp_code/lwip/*.c)
    set(PROJECT_SOURCES ${NXPCODE_SOURCES} main.c)
    
    # configure modules
    set(CONFIG_USE_driver_lpuart true)
    set(MCUX_DEVICE "MIMXRT1062")
    
    # Include sdk
    include(all_devices)
    
    include(driver_mdio-enet)
    
    include(driver_phy-device-ksz8081)
    
    # include modules
    include(driver_igpio)
    
    include(driver_clock)
    
    include(driver_common)
    
    include(device_CMSIS)
    
    include(utility_debug_console)
    
    include(component_lpuart_adapter)
    
    include(component_serial_manager)
    
    include(component_lists)
    
    include(component_serial_manager_uart)
    
    include(driver_lpuart)
    
    include(device_startup)
    
    include(driver_iomuxc)
    
    include(utility_assert)
    
    include(driver_xip_device)
    
    include(driver_xip_board)
    
    include(CMSIS_Include_core_cm7)
    
    include(driver_mdio-common)
    
    include(CMSIS_Include_common)
    
    include(CMSIS_Include_dsp)
    
    include(utilities_misc_utilities)
    
    include(device_system)
    
    include(driver_enet)
    
    include(driver_trng)
    
    include(driver_phy-common)
    
    include(driver_dcp)
    
    add_executable(${PROJECT_NAME} ${PROJECT_SOURCES})
    target_link_libraries(${PROJECT_NAME} PRIVATE
        FreeRTOS::Timers
        FreeRTOS::Heap::5
        FreeRTOS::ARM_CM4F
        FreeRTOS::EventGroups
        FreeRTOSPlus::Utilities::backoff_algorithm
        FreeRTOSPlus::Utilities::logging
        FreeRTOSPlus::ThirdParty::mbedtls
        az::iot_middleware::freertos
        LWIP
        SAMPLE::SOCKET::LWIP
        SAMPLE::AZUREIOT
        SAMPLE::TRANSPORT::MBEDTLS
        ${MCUX_SDK_PROJECT_NAME}
        )
    
    add_custom_command(TARGET ${PROJECT_NAME}
        # Run after all other rules within the target have been executed
        POST_BUILD
        COMMAND ${CMAKE_OBJCOPY} -Obinary $<TARGET_FILE:${PROJECT_NAME}> ${PROJECT_NAME}.bin
        COMMENT "Generate Bin file"
        VERBATIM)
    
    add_executable(${PROJECT_NAME}-pnp ${PROJECT_SOURCES})
    target_link_libraries(${PROJECT_NAME}-pnp PRIVATE
        FreeRTOS::Timers
        FreeRTOS::Heap::5
        FreeRTOS::ARM_CM4F
        FreeRTOS::EventGroups
        FreeRTOSPlus::Utilities::backoff_algorithm
        FreeRTOSPlus::Utilities::logging
        FreeRTOSPlus::ThirdParty::mbedtls
        az::iot_middleware::freertos
        LWIP
        SAMPLE::SOCKET::LWIP
        SAMPLE::AZUREIOTPNP
        SAMPLE::TRANSPORT::MBEDTLS
        ${MCUX_SDK_PROJECT_NAME}
        )
    
    add_custom_command(TARGET ${PROJECT_NAME}-pnp
        # Run after all other rules within the target have been executed
        POST_BUILD
        COMMAND ${CMAKE_OBJCOPY} -Obinary $<TARGET_FILE:${PROJECT_NAME}-pnp> ${PROJECT_NAME}-pnp.bin
        COMMENT "Generate Bin file"
        VERBATIM)
    

    Expected behavior I would expect that the map files would be equivalent for the boot section.

    Screenshots and console output Working: image

    Not working: image

    Additional context Add any other context about the problem here.

    bug 
    opened by danewalton 10
  • [BUG] Application freeze in DbgConsole_Flush when many bigger messages are sent

    [BUG] Application freeze in DbgConsole_Flush when many bigger messages are sent

    Describe the bug Here is modified example for imx7ulp erpc_matrix_multiply_rpmsg_rtos_imxcm4.zip. Changes are in source/main_core1.c and cmake related files (flags for release target -DDEBUG_CONSOLE_TRANSFER_NON_BLOCKING
    -DPRINTF_ADVANCED_ENABLE=1
    -D__FILENAME__='"$(notdir $(abspath $<))"' ) Zip file contains also release dir with built binaries. If few printf are removed from modification, program is working. But with all modification program will freeze.

    To Reproduce image described above

    Expected behavior To not freeze at printf function.

    Screenshots and console output image

    bug 
    opened by Hadatko 9
  • Feature/enable zephyr integration

    Feature/enable zephyr integration

    Prerequisites

    • [ ] I have checked latest main branch and the issue still exists.
    • [ ] I did not see it is stated as known-issue in release notes.
    • [ ] No similar GitHub issue is related to this change.
    • [ ] My code follows the commit guidelines of this project.
    • [X] I have performed a self-review of my own code.
    • [ ] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.

    Describe the pull request

    This pull request aims to enable zephyr hal nxp support using current mcux-sdk. Below integration has been done:

    • Cmake build system integration: reference existing CMakeLists.txt of hal-nxp, include driver component according to the Kconfig setting in zephyr.
    • Kconfig integration: For menuconfig item Modules->hal_nxp, menu MCUX SDK is listed when select to Use MCUX SDK, all available configuration for soc/drivers/components/middleware/utility are listed. simple build test of hello_world has been executed for all RT1xxx boards, RT6xx boards, lpcxpresso54114 and lpcxpresso55s69, shows now build issue.

    Fixes # (issue)

    Type of change (please delete options that are not relevant):

    • [ ] Bug fix (non-breaking change which fixes an issue)
    • [*] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
    • [ ] This change requires a documentation update

    Tests

    • Test configuration (please complete the following information):
      • Hardware setting:
      • Toolchain:
      • Test Tool preparation:
      • Any other dependencies:
    • Test executed Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
      • [*] Build Test
      • [ ] Run Test
    opened by mcuxsusan 8
  • fsl_wm8960.c: Wrong argument order,

    fsl_wm8960.c: Wrong argument order,

    https://github.com/NXPmicro/mcux-sdk/blob/7b545788e3f6e0c1a8decae21e428ed8d5b5a8e7/components/codec/wm8960/fsl_wm8960.c#L201

    The argument order or the call is wrong. It must me:

            WM8960_CHECK_RET(WM8960_SetInternalPllConfig(handle, config->masterClock.sysclkFreq, sysclk,
                                                         config->format.sampleRate, config->format.bitWidth),
    
    opened by robert-hh 7
  • [BUG] GCC assembler flags produce warnings when cmake is used.

    [BUG] GCC assembler flags produce warnings when cmake is used.

    Describe the bug Does assembler compiler needs so many flags you are providing in CmakeList.txt? Screenshot_20210816_114641

    I was searching trought internet and it looks like these compiler flags are more or less C specific flags and not assembler. Actually i am not sure if any of mentioned above is usefull maybe only DNDEBUG or DDEBUG. This is related to all examples of all projects. I guess assembler should contains only application specific macros as there is none compiler specific (if i am wrong, correct me)

    Why is this issue to me? For example combination of ENABLE_LANGUAGE(ASM) and -std=gnu99: https://github.com/microsoft/vscode-cmake-tools/issues/2044#issuecomment-896991481 It would be better to get rid of useless compiler macros for assembler. So many not used flags for assembler target has also another side-effect data "noise" in file (file with flags can be smaller and more transparent)

    To Reproduce Look into assembler flags for armgcc

    Expected behavior Smaller file with flags for compiler. More transparent

    bug 
    opened by Hadatko 7
  • video/camera/receiver/isi/fsl_isi_camera_adapter component should support output frame with raw8/raw10 format.

    video/camera/receiver/isi/fsl_isi_camera_adapter component should support output frame with raw8/raw10 format.

    Is your enhancement proposal related to a problem? Please describe. There are some camera only support raw8/raw10 format. So it is batter that video/camera/receiver/isi/fsl_isi_camera_adapter component should support output frame with raw8/raw10 format.

    Describe the solution you'd like video/camera/receiver/isi/fsl_isi_camera_adapter component can output the raw8/raw10 format.

    opened by SimonFu0506 6
  • FLEXCAN workaround for chip errata 6032 may cause intermittent RX FIFO overflows in an RTOS multithreaded environment.

    FLEXCAN workaround for chip errata 6032 may cause intermittent RX FIFO overflows in an RTOS multithreaded environment.

    Is your enhancement proposal related to a problem? Please describe. We were updating our project from SDK version 2.4.2 to 2.10.0 when we observed intermittent RX FIFO overflows on FLEXCAN. After much debugging, we were able to narrow it down to the chip errata 6032 workaround function causing this issue. We run a multithreaded RTOS, and whenever a thread wanted to send a frame on CAN, it could disable all FLEXCAN interrupts, then context switch to another task leaving FLEXCAN interrupts disabled, eventually causing the 6 frame RX FIFO to overflow.

    Describe the solution you'd like Either an option added to disable the 6032 errata workaround, or to have it implemented in such a way that interrupts cannot be disabled long enough to overflow the RX FIFO. I am willing to contribute a pull request for one of these options if you can provide some guidance on which approach is preferred.

    Describe alternatives you've considered We have locally modified the SDK to disable the workaround and confirmed we no longer get intermittent RX FIFO overflows.

    Additional context Similar data loss issues also appear to be present in the implementation of LPUART. Whenever transmit/receive functions are called from an RTOS task, LPUART interrupts are disabled/enabled and if a task switch occurs or some higher priority task is running, received data on the LPUART can be lost.

    opened by abascom 6
  • Patch RT1166 fsl_clock.h to fix PLL POST_DIV_SEL Constants

    Patch RT1166 fsl_clock.h to fix PLL POST_DIV_SEL Constants

    Prerequisites

    • [x] I have checked latest main branch and the issue still exists.
    • [x] I did not see it is stated as known-issue in release notes.
    • [x] No similar GitHub issue is related to this change.
    • [x] My code follows the commit guidelines of this project.
    • [x] I have performed a self-review of my own code.
    • [x] My changes generate no new warnings.
    • [ ] I have added tests that prove my fix is effective or that my feature works.

    Describe the pull request

    Constants for field POST_DIV_SEL in ARM_PLL_CTRL_REGISTER were incorrect, fix them.

    Type of change:

    • [x] Bug fix (non-breaking change which fixes an issue)
    opened by danieldegrasse 6
  • [BUG] MIMXRT1176 CLOCK_GetRootClockFreq returns wrong frequency when post divider is 1

    [BUG] MIMXRT1176 CLOCK_GetRootClockFreq returns wrong frequency when post divider is 1

    Describe the bug CLOCK_GetRootClockFreq returns wrong frequency when post divider is set to divide by 1 (0b11)

    To Reproduce

    • Environment (please complete the following information):
      • Tag/Commit hash: [MCUX_2.11.0]
      • Toolchain: [ARMGCC 10.3-2021.07]
      • Board/SoC: [MIMXRT1176 on MIMXrt1170-EVK]
      • Example [iled_blinky_cm7]
    • Steps to reproduce the behavior:
      1. In MCUXpresso use the excample MIMXRT1176 iled_blinky_cm7
      2. Configure CortexM7 core root clock to ARM_PLL_CLK and the Divider to 3
      3. Configure ArmPLL to 1875 and the Post Divider to 1
      4. Update Code
      5. Set a breakpoint board/clock_config.c on the line with "SystemCoreClock = CLOCK_GetRootClockFreq(kCLOCK_Root_M7);"
      6. Read out SystemCoreClock. On My system says its 37500000.

    Expected behavior SystemCoreClock should be 600000000

    Screenshots and console output image

    Additional context CLOCK_GetPllFreq(kCLOCK_PllArm) does not calculate the post divider correctly. if post divider is 1, the register holds 0x3. fsl_clock.c line 1442 shifts postDiv to 0x10, But the divider for the calculation should be 1.

    bug 
    opened by ChristianMosbach 0
  • Better VSCode+CMake Tools experience

    Better VSCode+CMake Tools experience

    Based on this project, I tried to create a VSCode + CMake + GNU Arm Embedded Toolchain development environment (mcuxsdk-vscode), including:

    • Build executable
    • Flash the executable to the device
    • Debug executable

    Currently this works fine.

    In the process of developing mcuxsdk-vscode, I found some points that can be improved in this project:

    • The build output of the example project uses ${PROJECT_BINARY_DIR}/${CMAKE_BUILD_TYPE} to be more flexible than ${ProjDirPath}/${CMAKE_BUILD_TYPE}.
    • The example project should have its build output ignored from git.
    • The example project should generate a hex file after building to facilitate user flashing to the device.
    • Move the CMakeLists.txt of the example project to the example root directory to make it more suitable for VSCode Multi-root Workspaces.
    • Add the appropriate CMakePresets.json to the example project to make the CMake Tools plugin work better.
    • The Zephyr west tool is a good tool, but when I make changes to the repositories it manages, I don't know how to commit and track.

    If you are interested in my idea, you can try mcuxsdk-vscode. You can use VSCode to open mcuxsdk-vscode's vscode-ws/examples-evkbmimxrt1060.code-workspace and vscode-ws/examples-ok1061s.code-workspace and compare their led_blinky.

    Thanks

    opened by dsyx 1
  • Enhancement: Multi target CMake project support

    Enhancement: Multi target CMake project support

    Currently, MCUXpresso SDK only supports single target in top level CMakeLists.txt, since the components and drivers uses the following method adding source files to the build:

    target_sources(${MCUX_SDK_PROJECT_NAME} PRIVATE
        #...something belongs to the component...
    )
    
    target_include_directories(${MCUX_SDK_PROJECT_NAME} PUBLIC
       #...some directories needs to be searched...
    )
    

    This method requires there could only be one single target (namely ${MCUX_SDK_PROJECT_NAME}), adding another target to the same project (with use cases below) will not work without touching the SDK content or adding them manually.

    Typical use cases:

    • Linking to somewhere else by changing linker script: SRAM, FlexSPI, SDRAM..etc, you name it.
    • Different build configurations, compiler definitions

    Possible solution: It would be nice if components are re-organized as static library targets, and built as dependencies of the main executable target... maybe not the best solution, and may requires a lot of effort...

    opened by imi415 1
  • Any specific reason why rtos lpuart send function data buffer variable is not const?

    Any specific reason why rtos lpuart send function data buffer variable is not const?

    https://github.com/NXPmicro/mcux-sdk/blob/81a42c9e5875b70f0acdf10c23aa977ce1135100/drivers/lpuart/fsl_lpuart_freertos.h#L132

    In Send function the data shouldn't be changed and it looks like they are not. Isn't better to use const variable type? (i have data type conflict because it is not using const keyword)

    opened by Hadatko 0
  • Aligning lpuart config member and rtos lpuart config member names.

    Aligning lpuart config member and rtos lpuart config member names.

    Is your enhancement proposal related to a problem? Please describe.

    Hello, is there reason why lpuart_config and lpuart_rtos_config have different names for theirs members which has same functionality? It looks a bit messy to me. Maybe both configuration may have common structure which they may use inside.

    https://github.com/NXPmicro/mcux-sdk/blob/81a42c9e5875b70f0acdf10c23aa977ce1135100/drivers/lpuart/fsl_lpuart.h#L240 https://github.com/NXPmicro/mcux-sdk/blob/81a42c9e5875b70f0acdf10c23aa977ce1135100/drivers/lpuart/fsl_lpuart_freertos.h#L32

    Describe the solution you'd like Align members names or create new common structure.

    Describe alternatives you've considered Do nothing

    Additional context

    opened by Hadatko 3
  • Certain devices folder are missing .cmake files

    Certain devices folder are missing .cmake files

    Is your enhancement proposal related to a problem? Please describe. Below list of device are missing .cmake files. This will cause build issues. This was highlighted by a Zephyr customer who was trying to use RT1051 which is missing the .cmake files. I compiled a complete list of devices that are missing these .cmake files.

    K32L2A31A/
    K32L2B11A/
    K32L2B21A/
    LPC54005/
    LPC54016/
    LPC54018/
    LPC54018M/
    LPC54113/
    LPC54605/
    LPC54606/
    LPC54607/
    LPC54608/
    LPC54616/
    LPC54618/
    LPC54S005/
    LPC54S016/
    LPC5502/
    LPC5502CPXXXX/
    LPC5504/
    LPC5504CPXXXX/
    LPC5512/
    LPC5514/
    LPC5516/
    LPC5526/
    LPC5528/
    LPC55S04/
    LPC55S14/
    LPC55S26/
    LPC55S66/
    LPC810/
    LPC811/
    LPC822/
    LPC832/
    LPC834/
    LPC844/
    MCIMX7U3/
    MCIMX7U5/
    MIMX8DX1/
    MIMX8DX2/
    MIMX8DX3/
    MIMX8DX4/
    MIMX8DX5/
    MIMX8DX6/
    MIMX8MD6/
    MIMX8MD7/
    MIMX8ML3/
    MIMX8ML4/
    MIMX8ML6/
    MIMX8MM1/
    MIMX8MM2/
    MIMX8MM3/
    MIMX8MM4/
    MIMX8MM5/
    MIMX8MN1/
    MIMX8MN2/
    MIMX8MN3/
    MIMX8MN4/
    MIMX8MN5/
    MIMX8MQ5/
    MIMX8MQ7/
    MIMX8QX1/
    MIMX8QX2/
    MIMX8QX3/
    MIMX8QX4/
    MIMX8QX5/
    MIMX8UX5/
    MIMX8UX6/
    MIMXRT1051/
    MIMXRT1061/
    MIMXRT1165/
    MIMXRT1171/
    MIMXRT1172/
    MIMXRT1173/
    MIMXRT1175/
    MIMXRT633S/
    MK02F12810/
    MK22F12810/
    MK22F25612/
    MK24F12/
    MK26F18/
    MK27FA15/
    MK63F12/
    MK65F18/
    MK80F25615/
    MK82F25615/
    MKE04Z1284/
    MKE14F16/
    MKE14Z4/
    MKE14Z7/
    MKE15Z4/
    MKE16F16/
    MKL17Z644/
    MKL25Z4/
    MKM14ZA5/
    MKM33ZA5/
    MKV10Z1287/
    MKV10Z7/
    MKV30F12810/
    MKV31F12810/
    MKV31F25612/
    MKV56F24/
    MKW20Z4/
    MKW21Z4/
    MKW22D5/
    MKW24D5/
    MKW30Z4/
    MKW31Z4/
    MKW40Z4/
    MKW41Z4/
    

    Describe the solution you'd like Please add .cmake files similar to other platforms

    opened by mmahadevan108 2
Releases(MCUX_2.10.0_LPC55S36)
  • MCUX_2.10.0_LPC55S36(Apr 6, 2022)

    Development Tool Version

    • MCUXpresso IDE, version is 11.4.1
    • GCC ARM Embedded, version is 10-2020-q4-major

    Development Systems

    Development boards/socs verified in this release are listed as below.

    | Development boards | MCU devices | | :----------------: | :----------------------------------------------------------: | | LPCXpresso55S36 | LPC55S36JBD100, LPC5536JBD100, LPC5536JBD64, LPC5536JHI48, LPC5534JBD100, LPC5534JBD64, LPC5534JHI48, LPC55S36JHI48 |

    Source code(tar.gz)
    Source code(zip)
  • MCUX_2.11.0(Mar 9, 2022)

    Updates in This Release

    • Source code update applied from MCUXpresso SDK 2.11.0 release, build and run quality for examples in below board list are verified with specified toolchain version.
    • New middleware repositories added and will be checked out when you use west tool to pull this repository:
      • https://github.com/NXPmicro/mcux-sdk-middleware-usb
      • https://github.com/NXPmicro/mcux-sdk-middleware-edgefast-bluetooth
      • https://github.com/NXPmicro/mcux-sdk-middleware-ethermind
      • https://github.com/NXP/azure-rtos
      • https://github.com/NXP/threadx
      • https://github.com/NXP/filex
      • https://github.com/NXP/levelx
      • https://github.com/NXP/netxduo
      • https://github.com/NXP/usbx
      • https://github.com/NXP/guix

    Development Tool Version

    • MCUXpresso IDE, version is 11.5.0
    • GCC ARM Embedded, version is 10-2021.07

    Development Systems

    Development boards/socs verified in this release are listed as below.

    | Development boards | MCU devices | | :----------------: | :----------------------------------------------------------: | | EVK-MCIMX7ULP | MCIMX7U5DVP07 , MCIMX7U5DVP07, MCIMX7U5DVK07, MCIMX7U5CVP06, MCIMX7U3DVK07, MCIMX7U3CVP06 | | EVK-MIMX8MM | MIMX8MM6DVTLZ , MIMX8MM6DVTLZ, MIMX8MM2DVTLZ, MIMX8MM1DVTLZ, MIMX8MM6CVTKZ, MIMX8MM2CVTKZ, MIMX8MM5CVTKZ, MIMX8MM5DVTLZ, MIMX8MM1CVTKZ, MIMX8MM4CVTKZ, MIMX8MM3CVTKZ, MIMX8MM4DVTLZ, MIMX8MM3DVTLZ | | EVK-MIMX8MN | MIMX8MN6DVTJZ , MIMX8MN2DVTJZ, MIMX8MN4CVTIZ, MIMX8MN3DVTJZ, MIMX8MN4DVTJZ, MIMX8MN5CVTIZ, MIMX8MN6CVTIZ, MIMX8MN5DVTJZ, MIMX8MN6DVTJZ, MIMX8MN1DVTJZ, MIMX8MN2CVTIZ, MIMX8MN1CVTIZ, MIMX8MN3CVTIZ | | EVK-MIMX8MNDDR3L | MIMX8MN6DVTJZ , MIMX8MN2DVTJZ, MIMX8MN4CVTIZ, MIMX8MN3DVTJZ, MIMX8MN4DVTJZ, MIMX8MN5CVTIZ, MIMX8MN6CVTIZ, MIMX8MN5DVTJZ, MIMX8MN6DVTJZ, MIMX8MN1DVTJZ, MIMX8MN2CVTIZ, MIMX8MN1CVTIZ, MIMX8MN3CVTIZ | | EVK-MIMX8MQ | MIMX8MQ6DVAJZ , MIMX8MQ6CVAHZ, MIMX8MQ5CVAHZ, MIMX8MD6DVAJZ, MIMX8MQ7DVAJZ, MIMX8MD7CVAHZ, MIMX8MD7DVAJZ, MIMX8MQ7CVAHZ, MIMX8MQ5DVAJZ, MIMX8MQ6DVAJZ, MIMX8MD6CVAHZ | | EVK-MIMX8MP | MIMX8ML8DVNLZ, MIMX8ML6CVNKZ, MIMX8ML8CVNKZ, MIMX8ML4DVNLZ, MIMX8ML4CVNKZ, MIMX8ML6DVNLZ, MIMX8ML3CVNKZ, MIMX8ML3DVNLZ | | EVK-MIMXRT1010 | MIMXRT1011DAE5A , MIMXRT1011DAE5A, MIMXRT1011CAE4A | | EVK-MIMXRT1015 | MIMXRT1015DAF5A , MIMXRT1015CAF4A, MIMXRT1015DAF5A | | EVK-MIMXRT1020 | MIMXRT1021DAG5A , MIMXRT1021DAF5A, MIMXRT1021DAG5A, MIMXRT1021CAG4A, MIMXRT1021CAF4A | | EVK-MIMXRT1060 | MIMXRT1062DVL6A , MIMXRT1061CVL5A, MIMXRT1061DVJ6A, MIMXRT1062CVL5A, MIMXRT1062DVL6A, MIMXRT1062DVJ6A, MIMXRT1062CVJ5A, MIMXRT1061CVJ5A, MIMXRT1061DVL6A | | EVK-MIMXRT1064 | MIMXRT1064DVL6A , MIMXRT1064CVJ5A, MIMXRT1064CVL5A, MIMXRT1064DVL6A, MIMXRT1064DVJ6A | | EVK-MIMXRT595 | MIMXRT595SFFOC, MIMXRT595SFAWC | | EVK-MIMXRT685 | MIMXRT685SFVKB , MIMXRT633SFAWBR, MIMXRT685SFFOB, MIMXRT633SFFOB, MIMXRT685SFAWBR, MIMXRT685SFVKB, MIMXRT633SFVKB | | EVKB-IMXRT1050 | MIMXRT1052DVL6B , MIMXRT1052DVL6B, MIMXRT1052CVJ5B, MIMXRT1051DVJ6B, MIMXRT1051CVL5B, MIMXRT1052DVJ6B, MIMXRT1051DVL6B, MIMXRT1052CVL5B, MIMXRT1051CVJ5B | | FRDM-K22F | MK22FN512VLH12 , MK22FN128VDC10, MK22FN512VMP12, MK22FN128VLH10, MK02FN64VFM10, MK22FN512VDC12, MK22FN256CAH12, MK22FN512CAP12, MK02FN128VLH10, MK22FN128VLL10, MK22FN128CAH12, MK22FN256VDC12, MK22FN512VFX12, MK22FN512VLL12, MK02FN128VLF10, MK22FN256VLL12, MK22FN256VMP12, MK02FN64VLF10, MK22FN256VLH12, MK02FN128VFM10, MK02FN64VLH10, MK22FN128VMP10, MK22FN512VLH12 | | FRDM-K32L2A4S | K32L2A41VLL1A , K32L2A31VLL1A, K32L2A41VLH1A, K32L2A31VLH1A, K32L2A41VLL1A | | FRDM-K32L2B | K32L2B31VLH0A , K32L2B21VLH0A, K32L2B11VLH0A, K32L2B31VMP0A, K32L2B11VMP0A, K32L2B31VFT0A, K32L2B31VFM0A, K32L2B11VFM0A, K32L2B21VFM0A, K32L2B11VFT0A, K32L2B21VFT0A, K32L2B21VMP0A, K32L2B31VLH0A | | FRDM-K32L3A6 | K32L3A60VPJ1A , K32L3A60VPJ1A | | FRDM-K64F | MK64FN1M0VLL12 , MK64FN1M0VLQ12, MK24FN1M0CAJ12, MK64FX512VMD12, MK63FN1M0VMD12, MK24FN1M0VDC12, MK63FN1M0VLQ12, MK64FN1M0CAJ12, MK64FN1M0VDC12, MK64FN1M0VLL12, MK24FN1M0VLQ12, MK64FX512VLL12, MK64FX512VDC12, MK64FX512VLQ12, MK24FN1M0VLL12, MK64FN1M0VMD12 | | FRDM-K66F | MK66FN2M0VMD18 , MK65FX1M0CAC18, MK65FN2M0VMI18, MK66FX1M0VLQ18, MK66FN2M0VLQ18, MK26FN2M0VLQ18, MK26FN2M0VMI18, MK26FN2M0VMD18, MK65FX1M0VMI18, MK66FN2M0VMD18, MK66FX1M0VMD18, MK65FN2M0CAC18, MK26FN2M0CAC18 | | FRDM-KE02Z40M | MKE02Z64VQH4 , MKE02Z16VLC4, MKE02Z32VLH4, MKE02Z64VLH4, MKE02Z16VLD4, MKE02Z32VLC4, MKE02Z64VFM4, MKE02Z32VQH4, MKE02Z32VLD4, MKE02Z64VLD4, MKE02Z16VFM4, MKE02Z64VLC4, MKE02Z32VFM4, MKE02Z64VQH4 | | FRDM-KE04Z | MKE04Z8VFK4 , MKE04Z8VWJ4, MKE04Z8VFK4, MKE04Z8VTG4 | | FRDM-KE06Z | MKE06Z128VLK4 , MKE04Z128VQH4, MKE04Z64VLK4, MKE04Z128VLH4, MKE06Z64VLH4, MKE06Z128VQH4, MKE04Z64VLD4, MKE04Z128VLD4, MKE04Z128VLK4, MKE04Z64VLH4, MKE04Z64VQH4, MKE06Z64VQH4, MKE06Z64VLD4, MKE06Z128VLK4, MKE06Z128VLD4, MKE06Z64VLK4, MKE06Z128VLH4 | | FRDM-KE15Z | MKE15Z256VLL7 , MKE15Z128VLH7, MKE14Z128VLL7, MKE15Z256VLH7, MKE14Z256VLL7, MKE15Z256VLL7, MKE14Z256VLH7, MKE14Z128VLH7, MKE15Z128VLL7 | | FRDM-KE16Z | MKE16Z64VLF4 , MKE15Z32VLF4, MKE16Z32VLF4, MKE14Z32VLF4, MKE15Z32VLD4, MKE15Z64VLD4, MKE16Z32VLD4, MKE14Z32VFP4, MKE16Z64VLF4, MKE15Z64VFP4, MKE14Z64VFP4, MKE16Z64VLD4, MKE15Z32VFP4, MKE14Z32VLD4, MKE14Z64VLD4, MKE15Z64VLF4, MKE14Z64VLF4 | | FRDM-KV11Z | MKV11Z128VLH7 , MKV10Z64VFM7, MKV10Z64VLH7, MKV10Z128VFM7, MKV11Z128VLC7, MKV10Z128VLC7, MKV10Z16VLF7, MKV10Z32VLF7, MKV11Z64VLC7, MKV11Z128VLH7, MKV10Z32VFM7, MKV11Z128VLF7, MKV11Z128VFM7, MKV10Z16VLC7, MKV10Z128VLF7, MKV11Z64VLH7, MKV11Z64VFM7, MKV10Z32VLC7, MKV11Z64VLF7, MKV10Z64VLC7, MKV10Z128VLH7, MKV10Z64VLF7, MKV10Z16VFM7 | | FRDM-KV31F | MKV31F512VLL12 , MKV31F512VLH12, MKV30F128VLF10, MKV31F512VLL12, MKV30F64VFM10, MKV30F128VFM10, MKV31F256VLL12, MKV30F64VLF10, MKV31F128VLH10, MKV30F64VLH10, MKV31F256VLH12, MKV30F128VLH10, MKV31F128VLL10 | | HVP-KV11Z75M | MKV11Z128VLF7 , MKV10Z64VFM7, MKV10Z64VLH7, MKV10Z128VFM7, MKV11Z128VLC7, MKV10Z128VLC7, MKV10Z16VLF7, MKV10Z32VLF7, MKV11Z64VLC7, MKV11Z128VLH7, MKV10Z32VFM7, MKV11Z128VLF7, MKV11Z128VFM7, MKV10Z16VLC7, MKV10Z128VLF7, MKV11Z64VLH7, MKV11Z64VFM7, MKV10Z32VLC7, MKV11Z64VLF7, MKV10Z64VLC7, MKV10Z128VLH7, MKV10Z64VLF7, MKV10Z16VFM7 | | HVP-KV31F120M | MKV31F512VLL12 , MKV31F512VLH12, MKV30F128VLF10, MKV31F512VLL12, MKV30F64VFM10, MKV30F128VFM10, MKV31F256VLL12, MKV30F64VLF10, MKV31F128VLH10, MKV30F64VLH10, MKV31F256VLH12, MKV30F128VLH10, MKV31F128VLL10 | | LPC845BREAKOUT | LPC845M301JBD48 , LPC845M301JHI33, LPC844M201JHI48, LPC845M301JHI48, LPC845M301JBD48, LPC844M201JBD48, LPC844M201JBD64, LPC844M201JHI33, LPC845M301JBD64 | | LPCXpresso51U68 | LPC51U68JBD64 , LPC51U68JBD48, LPC51U68JBD64 | | LPCXpresso54628 | LPC54628J512ET180 , LPC54605J512ET100, LPC54608J512BD208, LPC54606J512ET100, LPC54605J512BD100, LPC54605J256ET180, LPC54607J512ET180, LPC54605J512ET180, LPC54607J256BD208, LPC54618J512BD208, LPC54606J256ET100, LPC54605J256BD100, LPC54606J256BD100, LPC54616J256ET180, LPC54607J256ET180, LPC54606J256ET180, LPC54606J512BD208, LPC54616J512BD208, LPC54606J512BD100, LPC54618J512ET180, LPC54608J512ET180, LPC54628J512ET180, LPC54605J256ET100, LPC54616J512BD100, LPC54616J512ET100 | | LPCXpresso54S018 | LPC54S018JET180 , LPC54S016JBD208, LPC54005JBD100, LPC54S018JET180, LPC54016JBD100, LPC54S018JBD208, LPC54016JBD208, LPC54005JET100, LPC54S016JET180, LPC54S016JBD100, LPC54018JET180, LPC54016JET180, LPC54S005JET100, LPC54018JBD208, LPC54S005JBD100 | | LPCXpresso54S018M | LPC54S018J4MET180 , LPC54018J2MET180, LPC54018J4MET180, LPC54S018J2MET180, LPC54S018J4MET180 | | LPCXpresso55S06 | LPC55S06JBD64, LPC55S06JHI48, LPC55S04JBD64 , LPC55S04JHI48, LPC5502JBD64, LPC5502JHI48, LPC5506JBD64 , LPC5506JHI48, LPC5504JBD64, LPC5504JHI48 | | LPCXpresso55S06CP | LPC5506JHI48CPXXXX, LPC5504JHI48CPXXXX, LPC5502JHI48CPXXXX | | LPCXpresso55S16 | LPC55S16JBD100 , LPC5514JBD64, LPC55S16JBD100, LPC5516JEV98, LPC5516JBD100, LPC5514JBD100, LPC55S14JBD64, LPC55S14JBD100, LPC55S16JEV98, LPC5512JBD100, LPC5516JBD64, LPC55S16JBD64, LPC5512JBD64 | | LPCXpresso55S28 | LPC55S28JBD100 , LPC5526JBD64, LPC5526JEV98, LPC5528JBD100, LPC5528JEV98, LPC55S26JBD64, LPC55S26JBD100, LPC55S28JBD64, LPC55S28JEV98, LPC5526JBD100, LPC5528JBD64, LPC55S26JEV98, LPC55S28JBD100 | | LPCXpresso55S69 | LPC55S69JBD100 , LPC55S66JBD64, LPC55S69JBD100, LPC55S66JEV98, LPC55S69JBD64, LPC55S66JBD100, LPC55S69JEV98 | | LPCXpresso802 | LPC802M001JDH20 , LPC802M001JDH20, LPC802M011JDH20, LPC802UK, LPC802M001JDH16, LPC802M001JHI33 | | LPCXpresso804 | LPC804M101JDH24 , LPC804M101JHI33, LPC804M101JDH20, LPC804M111JDH24, LPC804M101JDH24, LPC804UK | | LPCXpresso824MAX | LPC824M201JHI33 , LPC822M101JDH20, LPC824M201JHI33, LPC834M101FHI33, LPC832M101FDH20, LPC824M201JDH20, LPC822M101JHI33 | | LPCXpresso845MAX | LPC845M301JBD64 , LPC845M301JHI33, LPC844M201JHI48, LPC845M301JHI48, LPC845M301JBD48, LPC844M201JBD48, LPC844M201JBD64, LPC844M201JHI33, LPC845M301JBD64 | | MIMXRT1024-EVK | MIMXRT1024DAG5A , MIMXRT1024DAG5A, MIMXRT1024CAG4A | | MIMXRT1060-EVKB | MIMXRT1062DVL6A , MIMXRT1061CVL5A, MIMXRT1061DVJ6A, MIMXRT1062CVL5A, MIMXRT1062DVL6A, MIMXRT1062DVJ6A, MIMXRT1062CVJ5A, MIMXRT1061CVJ5A, MIMXRT1061DVL6A | | MIMXRT1160-EVK | MIMXRT1166DVM6A, MIMXRT1166CVM5A, MIMXRT1166XVM5A, MIMXRT1165DVM6A,MIMXRT1165CVM5A, MIMXRT1165XVM5A | | MIMXRT1170-EVK | MIMXRT1176AVM8A, MIMXRT1176CVM8A, MIMXRT1176DVMAA, MIMXRT1171DVMAA , MIMXRT1171AVM8A, MIMXRT1171CVM8A, MIMXRT1173CVM8A , MIMXRT1175DVMAA, MIMXRT1175AVM8A, MIMXRT1175CVM8A , MIMXRT1172DVMAA, MIMXRT1172AVM8A, MIMXRT1172CVM8A | | TWR-KM35Z75M | MKM35Z512VLQ7 , MKM35Z256VLL7, MKM35Z256VLL7R, MKM35Z512VLL7, MKM35Z256VLQ7R, MKM35Z512VLQ7R, MKM35Z512VLQ7, MKM35Z256VLQ7, MKM35Z512VLL7R | | TWR-KM34Z50MV3 | MKM34Z128ACLL5, MKM33Z128ACLH5, MKM33Z128ACLL5 , MKM33Z64ACLH5, MKM33Z64ACLL5, MKM14Z64ACHH5, MKM14Z128ACHH5 | | TWR-KM34Z75M | MKM34Z256VLQ7, MKM34Z256VLL7 | | FRDM-KE17Z | MKE17Z256VLL7, MKE17Z256VLH7, MKE17Z128VLL7, MKE17Z128VLH7,MKE13Z256VLL7, MKE13Z256VLH7, MKE13Z128VLL7, MKE13Z128VLH7, MKE12Z256VLL7, MKE12Z256VLH7, MKE12Z128VLL7, MKE12Z128VLH7 | | MIMXRT685-AUD-EVK | MIMXRT685SFVKB , MIMXRT633SFAWBR, MIMXRT685SFFOB, MIMXRT633SFFOB, MIMXRT685SFAWBR, MIMXRT685SFVKB, MIMXRT633SFVKB |

    Source code(tar.gz)
    Source code(zip)
  • MCUX_2.10.0(Jul 27, 2021)

    Development Tool Version

    • MCUXpresso IDE, version is 11.4.0
    • GCC ARM Embedded, version is 10-2020-q4-major

    Development Systems

    Development boards/socs verified in this release are listed as below.

    | Development boards | MCU devices | | :----------------: | :----------------------------------------------------------: | | EVK-MCIMX7ULP | MCIMX7U5DVP07 , MCIMX7U5DVP07, MCIMX7U5DVK07, MCIMX7U5CVP06, MCIMX7U3DVK07, MCIMX7U3CVP06 | | EVK-MIMX8MM | MIMX8MM6DVTLZ , MIMX8MM6DVTLZ, MIMX8MM2DVTLZ, MIMX8MM1DVTLZ, MIMX8MM6CVTKZ, MIMX8MM2CVTKZ, MIMX8MM5CVTKZ, MIMX8MM5DVTLZ, MIMX8MM1CVTKZ, MIMX8MM4CVTKZ, MIMX8MM3CVTKZ, MIMX8MM4DVTLZ, MIMX8MM3DVTLZ | | EVK-MIMX8MN | MIMX8MN6DVTJZ , MIMX8MN2DVTJZ, MIMX8MN4CVTIZ, MIMX8MN3DVTJZ, MIMX8MN4DVTJZ, MIMX8MN5CVTIZ, MIMX8MN6CVTIZ, MIMX8MN5DVTJZ, MIMX8MN6DVTJZ, MIMX8MN1DVTJZ, MIMX8MN2CVTIZ, MIMX8MN1CVTIZ, MIMX8MN3CVTIZ | | EVK-MIMX8MNDDR3L | MIMX8MN6DVTJZ , MIMX8MN2DVTJZ, MIMX8MN4CVTIZ, MIMX8MN3DVTJZ, MIMX8MN4DVTJZ, MIMX8MN5CVTIZ, MIMX8MN6CVTIZ, MIMX8MN5DVTJZ, MIMX8MN6DVTJZ, MIMX8MN1DVTJZ, MIMX8MN2CVTIZ, MIMX8MN1CVTIZ, MIMX8MN3CVTIZ | | EVK-MIMX8MQ | MIMX8MQ6DVAJZ , MIMX8MQ6CVAHZ, MIMX8MQ5CVAHZ, MIMX8MD6DVAJZ, MIMX8MQ7DVAJZ, MIMX8MD7CVAHZ, MIMX8MD7DVAJZ, MIMX8MQ7CVAHZ, MIMX8MQ5DVAJZ, MIMX8MQ6DVAJZ, MIMX8MD6CVAHZ | | EVK-MIMX8MP | MIMX8ML8DVNLZ, MIMX8ML6CVNKZ, MIMX8ML8CVNKZ, MIMX8ML4DVNLZ, MIMX8ML4CVNKZ, MIMX8ML6DVNLZ, MIMX8ML3CVNKZ, MIMX8ML3DVNLZ | | EVK-MIMXRT1010 | MIMXRT1011DAE5A , MIMXRT1011DAE5A, MIMXRT1011CAE4A | | EVK-MIMXRT1015 | MIMXRT1015DAF5A , MIMXRT1015CAF4A, MIMXRT1015DAF5A | | EVK-MIMXRT1020 | MIMXRT1021DAG5A , MIMXRT1021DAF5A, MIMXRT1021DAG5A, MIMXRT1021CAG4A, MIMXRT1021CAF4A | | EVK-MIMXRT1060 | MIMXRT1062DVL6A , MIMXRT1061CVL5A, MIMXRT1061DVJ6A, MIMXRT1062CVL5A, MIMXRT1062DVL6A, MIMXRT1062DVJ6A, MIMXRT1062CVJ5A, MIMXRT1061CVJ5A, MIMXRT1061DVL6A | | EVK-MIMXRT1064 | MIMXRT1064DVL6A , MIMXRT1064CVJ5A, MIMXRT1064CVL5A, MIMXRT1064DVL6A, MIMXRT1064DVJ6A | | EVK-MIMXRT595 | MIMXRT595SFFOC, MIMXRT595SFAWC | | EVK-MIMXRT685 | MIMXRT685SFVKB , MIMXRT633SFAWBR, MIMXRT685SFFOB, MIMXRT633SFFOB, MIMXRT685SFAWBR, MIMXRT685SFVKB, MIMXRT633SFVKB | | EVKB-IMXRT1050 | MIMXRT1052DVL6B , MIMXRT1052DVL6B, MIMXRT1052CVJ5B, MIMXRT1051DVJ6B, MIMXRT1051CVL5B, MIMXRT1052DVJ6B, MIMXRT1051DVL6B, MIMXRT1052CVL5B, MIMXRT1051CVJ5B | | FRDM-K22F | MK22FN512VLH12 , MK22FN128VDC10, MK22FN512VMP12, MK22FN128VLH10, MK02FN64VFM10, MK22FN512VDC12, MK22FN256CAH12, MK22FN512CAP12, MK02FN128VLH10, MK22FN128VLL10, MK22FN128CAH12, MK22FN256VDC12, MK22FN512VFX12, MK22FN512VLL12, MK02FN128VLF10, MK22FN256VLL12, MK22FN256VMP12, MK02FN64VLF10, MK22FN256VLH12, MK02FN128VFM10, MK02FN64VLH10, MK22FN128VMP10, MK22FN512VLH12 | | FRDM-K32L2A4S | K32L2A41VLL1A , K32L2A31VLL1A, K32L2A41VLH1A, K32L2A31VLH1A, K32L2A41VLL1A | | FRDM-K32L2B | K32L2B31VLH0A , K32L2B21VLH0A, K32L2B11VLH0A, K32L2B31VMP0A, K32L2B11VMP0A, K32L2B31VFT0A, K32L2B31VFM0A, K32L2B11VFM0A, K32L2B21VFM0A, K32L2B11VFT0A, K32L2B21VFT0A, K32L2B21VMP0A, K32L2B31VLH0A | | FRDM-K32L3A6 | K32L3A60VPJ1A , K32L3A60VPJ1A | | FRDM-K64F | MK64FN1M0VLL12 , MK64FN1M0VLQ12, MK24FN1M0CAJ12, MK64FX512VMD12, MK63FN1M0VMD12, MK24FN1M0VDC12, MK63FN1M0VLQ12, MK64FN1M0CAJ12, MK64FN1M0VDC12, MK64FN1M0VLL12, MK24FN1M0VLQ12, MK64FX512VLL12, MK64FX512VDC12, MK64FX512VLQ12, MK24FN1M0VLL12, MK64FN1M0VMD12 | | FRDM-K66F | MK66FN2M0VMD18 , MK65FX1M0CAC18, MK65FN2M0VMI18, MK66FX1M0VLQ18, MK66FN2M0VLQ18, MK26FN2M0VLQ18, MK26FN2M0VMI18, MK26FN2M0VMD18, MK65FX1M0VMI18, MK66FN2M0VMD18, MK66FX1M0VMD18, MK65FN2M0CAC18, MK26FN2M0CAC18 | | FRDM-KE02Z40M | MKE02Z64VQH4 , MKE02Z16VLC4, MKE02Z32VLH4, MKE02Z64VLH4, MKE02Z16VLD4, MKE02Z32VLC4, MKE02Z64VFM4, MKE02Z32VQH4, MKE02Z32VLD4, MKE02Z64VLD4, MKE02Z16VFM4, MKE02Z64VLC4, MKE02Z32VFM4, MKE02Z64VQH4 | | FRDM-KE04Z | MKE04Z8VFK4 , MKE04Z8VWJ4, MKE04Z8VFK4, MKE04Z8VTG4 | | FRDM-KE06Z | MKE06Z128VLK4 , MKE04Z128VQH4, MKE04Z64VLK4, MKE04Z128VLH4, MKE06Z64VLH4, MKE06Z128VQH4, MKE04Z64VLD4, MKE04Z128VLD4, MKE04Z128VLK4, MKE04Z64VLH4, MKE04Z64VQH4, MKE06Z64VQH4, MKE06Z64VLD4, MKE06Z128VLK4, MKE06Z128VLD4, MKE06Z64VLK4, MKE06Z128VLH4 | | FRDM-KE15Z | MKE15Z256VLL7 , MKE15Z128VLH7, MKE14Z128VLL7, MKE15Z256VLH7, MKE14Z256VLL7, MKE15Z256VLL7, MKE14Z256VLH7, MKE14Z128VLH7, MKE15Z128VLL7 | | FRDM-KE16Z | MKE16Z64VLF4 , MKE15Z32VLF4, MKE16Z32VLF4, MKE14Z32VLF4, MKE15Z32VLD4, MKE15Z64VLD4, MKE16Z32VLD4, MKE14Z32VFP4, MKE16Z64VLF4, MKE15Z64VFP4, MKE14Z64VFP4, MKE16Z64VLD4, MKE15Z32VFP4, MKE14Z32VLD4, MKE14Z64VLD4, MKE15Z64VLF4, MKE14Z64VLF4 | | FRDM-KV11Z | MKV11Z128VLH7 , MKV10Z64VFM7, MKV10Z64VLH7, MKV10Z128VFM7, MKV11Z128VLC7, MKV10Z128VLC7, MKV10Z16VLF7, MKV10Z32VLF7, MKV11Z64VLC7, MKV11Z128VLH7, MKV10Z32VFM7, MKV11Z128VLF7, MKV11Z128VFM7, MKV10Z16VLC7, MKV10Z128VLF7, MKV11Z64VLH7, MKV11Z64VFM7, MKV10Z32VLC7, MKV11Z64VLF7, MKV10Z64VLC7, MKV10Z128VLH7, MKV10Z64VLF7, MKV10Z16VFM7 | | FRDM-KV31F | MKV31F512VLL12 , MKV31F512VLH12, MKV30F128VLF10, MKV31F512VLL12, MKV30F64VFM10, MKV30F128VFM10, MKV31F256VLL12, MKV30F64VLF10, MKV31F128VLH10, MKV30F64VLH10, MKV31F256VLH12, MKV30F128VLH10, MKV31F128VLL10 | | HVP-KV11Z75M | MKV11Z128VLF7 , MKV10Z64VFM7, MKV10Z64VLH7, MKV10Z128VFM7, MKV11Z128VLC7, MKV10Z128VLC7, MKV10Z16VLF7, MKV10Z32VLF7, MKV11Z64VLC7, MKV11Z128VLH7, MKV10Z32VFM7, MKV11Z128VLF7, MKV11Z128VFM7, MKV10Z16VLC7, MKV10Z128VLF7, MKV11Z64VLH7, MKV11Z64VFM7, MKV10Z32VLC7, MKV11Z64VLF7, MKV10Z64VLC7, MKV10Z128VLH7, MKV10Z64VLF7, MKV10Z16VFM7 | | HVP-KV31F120M | MKV31F512VLL12 , MKV31F512VLH12, MKV30F128VLF10, MKV31F512VLL12, MKV30F64VFM10, MKV30F128VFM10, MKV31F256VLL12, MKV30F64VLF10, MKV31F128VLH10, MKV30F64VLH10, MKV31F256VLH12, MKV30F128VLH10, MKV31F128VLL10 | | LPC845BREAKOUT | LPC845M301JBD48 , LPC845M301JHI33, LPC844M201JHI48, LPC845M301JHI48, LPC845M301JBD48, LPC844M201JBD48, LPC844M201JBD64, LPC844M201JHI33, LPC845M301JBD64 | | LPCXpresso51U68 | LPC51U68JBD64 , LPC51U68JBD48, LPC51U68JBD64 | | LPCXpresso54628 | LPC54628J512ET180 , LPC54605J512ET100, LPC54608J512BD208, LPC54606J512ET100, LPC54605J512BD100, LPC54605J256ET180, LPC54607J512ET180, LPC54605J512ET180, LPC54607J256BD208, LPC54618J512BD208, LPC54606J256ET100, LPC54605J256BD100, LPC54606J256BD100, LPC54616J256ET180, LPC54607J256ET180, LPC54606J256ET180, LPC54606J512BD208, LPC54616J512BD208, LPC54606J512BD100, LPC54618J512ET180, LPC54608J512ET180, LPC54628J512ET180, LPC54605J256ET100, LPC54616J512BD100, LPC54616J512ET100 | | LPCXpresso54S018 | LPC54S018JET180 , LPC54S016JBD208, LPC54005JBD100, LPC54S018JET180, LPC54016JBD100, LPC54S018JBD208, LPC54016JBD208, LPC54005JET100, LPC54S016JET180, LPC54S016JBD100, LPC54018JET180, LPC54016JET180, LPC54S005JET100, LPC54018JBD208, LPC54S005JBD100 | | LPCXpresso54S018M | LPC54S018J4MET180 , LPC54018J2MET180, LPC54018J4MET180, LPC54S018J2MET180, LPC54S018J4MET180 | | LPCXpresso55S06 | LPC55S06JBD64, LPC55S06JHI48, LPC55S04JBD64 , LPC55S04JHI48, LPC5502JBD64, LPC5502JHI48, LPC5506JBD64 , LPC5506JHI48, LPC5504JBD64, LPC5504JHI48 | | LPCXpresso55S06CP | LPC5506JHI48CPXXXX, LPC5504JHI48CPXXXX, LPC5502JHI48CPXXXX | | LPCXpresso55S16 | LPC55S16JBD100 , LPC5514JBD64, LPC55S16JBD100, LPC5516JEV98, LPC5516JBD100, LPC5514JBD100, LPC55S14JBD64, LPC55S14JBD100, LPC55S16JEV98, LPC5512JBD100, LPC5516JBD64, LPC55S16JBD64, LPC5512JBD64 | | LPCXpresso55S28 | LPC55S28JBD100 , LPC5526JBD64, LPC5526JEV98, LPC5528JBD100, LPC5528JEV98, LPC55S26JBD64, LPC55S26JBD100, LPC55S28JBD64, LPC55S28JEV98, LPC5526JBD100, LPC5528JBD64, LPC55S26JEV98, LPC55S28JBD100 | | LPCXpresso55S69 | LPC55S69JBD100 , LPC55S66JBD64, LPC55S69JBD100, LPC55S66JEV98, LPC55S69JBD64, LPC55S66JBD100, LPC55S69JEV98 | | LPCXpresso802 | LPC802M001JDH20 , LPC802M001JDH20, LPC802M011JDH20, LPC802UK, LPC802M001JDH16, LPC802M001JHI33 | | LPCXpresso804 | LPC804M101JDH24 , LPC804M101JHI33, LPC804M101JDH20, LPC804M111JDH24, LPC804M101JDH24, LPC804UK | | LPCXpresso824MAX | LPC824M201JHI33 , LPC822M101JDH20, LPC824M201JHI33, LPC834M101FHI33, LPC832M101FDH20, LPC824M201JDH20, LPC822M101JHI33 | | LPCXpresso845MAX | LPC845M301JBD64 , LPC845M301JHI33, LPC844M201JHI48, LPC845M301JHI48, LPC845M301JBD48, LPC844M201JBD48, LPC844M201JBD64, LPC844M201JHI33, LPC845M301JBD64 | | MIMXRT1024-EVK | MIMXRT1024DAG5A , MIMXRT1024DAG5A, MIMXRT1024CAG4A | | MIMXRT1060-EVKB | MIMXRT1062DVL6A , MIMXRT1061CVL5A, MIMXRT1061DVJ6A, MIMXRT1062CVL5A, MIMXRT1062DVL6A, MIMXRT1062DVJ6A, MIMXRT1062CVJ5A, MIMXRT1061CVJ5A, MIMXRT1061DVL6A | | MIMXRT1160-EVK | MIMXRT1166DVM6A, MIMXRT1166CVM5A, MIMXRT1166XVM5A, MIMXRT1165DVM6A,MIMXRT1165CVM5A, MIMXRT1165XVM5A | | MIMXRT1170-EVK | MIMXRT1176AVM8A, MIMXRT1176CVM8A, MIMXRT1176DVMAA, MIMXRT1171DVMAA , MIMXRT1171AVM8A, MIMXRT1171CVM8A, MIMXRT1173CVM8A , MIMXRT1175DVMAA, MIMXRT1175AVM8A, MIMXRT1175CVM8A , MIMXRT1172DVMAA, MIMXRT1172AVM8A, MIMXRT1172CVM8A | | TWR-KM35Z75M | MKM35Z512VLQ7 , MKM35Z256VLL7, MKM35Z256VLL7R, MKM35Z512VLL7, MKM35Z256VLQ7R, MKM35Z512VLQ7R, MKM35Z512VLQ7, MKM35Z256VLQ7, MKM35Z512VLL7R | | TWR-KM34Z50MV3 | MKM34Z128ACLL5, MKM33Z128ACLH5, MKM33Z128ACLL5 , MKM33Z64ACLH5, MKM33Z64ACLL5, MKM14Z64ACHH5, MKM14Z128ACHH5 | | TWR-KM34Z75M | MKM34Z256VLQ7, MKM34Z256VLL7 |

    Source code(tar.gz)
    Source code(zip)
  • MCUX_2.9.0(Jan 18, 2021)

    Development Tool Version

    • MCUXpresso IDE, version is 11.3.0
    • GCC ARM Embedded, version is 9-2020-q2-update

    Development Systems

    Development boards/socs verified in this release are listed as below.

    | Development boards | MCU devices | |:----------------:|:----------------------------------------------------------:| | EVK-MCIMX7ULP | MCIMX7U5DVP07 , MCIMX7U5DVP07, MCIMX7U5DVK07, MCIMX7U5CVP06, MCIMX7U3DVK07, MCIMX7U3CVP06 | | EVK-MIMX8MM | MIMX8MM6DVTLZ , MIMX8MM6DVTLZ, MIMX8MM2DVTLZ, MIMX8MM1DVTLZ, MIMX8MM6CVTKZ, MIMX8MM2CVTKZ, MIMX8MM5CVTKZ, MIMX8MM5DVTLZ, MIMX8MM1CVTKZ, MIMX8MM4CVTKZ, MIMX8MM3CVTKZ, MIMX8MM4DVTLZ, MIMX8MM3DVTLZ | | EVK-MIMX8MN | MIMX8MN6DVTJZ , MIMX8MN2DVTJZ, MIMX8MN4CVTIZ, MIMX8MN3DVTJZ, MIMX8MN4DVTJZ, MIMX8MN5CVTIZ, MIMX8MN6CVTIZ, MIMX8MN5DVTJZ, MIMX8MN6DVTJZ, MIMX8MN1DVTJZ, MIMX8MN2CVTIZ, MIMX8MN1CVTIZ, MIMX8MN3CVTIZ | | EVK-MIMX8MQ | MIMX8MQ6DVAJZ , MIMX8MQ6CVAHZ, MIMX8MQ5CVAHZ, MIMX8MD6DVAJZ, MIMX8MQ7DVAJZ, MIMX8MD7CVAHZ, MIMX8MD7DVAJZ, MIMX8MQ7CVAHZ, MIMX8MQ5DVAJZ, MIMX8MQ6DVAJZ, MIMX8MD6CVAHZ | | EVK-MIMXRT1010 | MIMXRT1011DAE5A , MIMXRT1011DAE5A, MIMXRT1011CAE4A | | EVK-MIMXRT1015 | MIMXRT1015DAF5A , MIMXRT1015CAF4A, MIMXRT1015DAF5A | | EVK-MIMXRT1020 | MIMXRT1021DAG5A , MIMXRT1021DAF5A, MIMXRT1021DAG5A, MIMXRT1021CAG4A, MIMXRT1021CAF4A | | EVK-MIMXRT1060 | MIMXRT1062DVL6A , MIMXRT1061CVL5A, MIMXRT1061DVJ6A, MIMXRT1062CVL5A, MIMXRT1062DVL6A, MIMXRT1062DVJ6A, MIMXRT1062CVJ5A, MIMXRT1061CVJ5A, MIMXRT1061DVL6A | | EVK-MIMXRT1064 | MIMXRT1064DVL6A , MIMXRT1064CVJ5A, MIMXRT1064CVL5A, MIMXRT1064DVL6A, MIMXRT1064DVJ6A | | EVK-MIMXRT685 | MIMXRT685SFVKB , MIMXRT633SFAWBR, MIMXRT685SFFOB, MIMXRT633SFFOB, MIMXRT685SFAWBR, MIMXRT685SFVKB, MIMXRT633SFVKB | | EVKB-IMXRT1050 | MIMXRT1052DVL6B , MIMXRT1052DVL6B, MIMXRT1052CVJ5B, MIMXRT1051DVJ6B, MIMXRT1051CVL5B, MIMXRT1052DVJ6B, MIMXRT1051DVL6B, MIMXRT1052CVL5B, MIMXRT1051CVJ5B | | FRDM-K22F | MK22FN512VLH12 , MK22FN128VDC10, MK22FN512VMP12, MK22FN128VLH10, MK02FN64VFM10, MK22FN512VDC12, MK22FN256CAH12, MK22FN512CAP12, MK02FN128VLH10, MK22FN128VLL10, MK22FN128CAH12, MK22FN256VDC12, MK22FN512VFX12, MK22FN512VLL12, MK02FN128VLF10, MK22FN256VLL12, MK22FN256VMP12, MK02FN64VLF10, MK22FN256VLH12, MK02FN128VFM10, MK02FN64VLH10, MK22FN128VMP10, MK22FN512VLH12 | | FRDM-K28FA | MK28FN2M0AVMI15 , MK28FN2M0AVMI15, MK28FN2M0ACAU15R, MK27FN2M0AVMI15 | | FRDM-K32L2A4S | K32L2A41VLL1A , K32L2A31VLL1A, K32L2A41VLH1A, K32L2A31VLH1A, K32L2A41VLL1A | | FRDM-K32L2B | K32L2B31VLH0A , K32L2B21VLH0A, K32L2B11VLH0A, K32L2B31VMP0A, K32L2B11VMP0A, K32L2B31VFT0A, K32L2B31VFM0A, K32L2B11VFM0A, K32L2B21VFM0A, K32L2B11VFT0A, K32L2B21VFT0A, K32L2B21VMP0A, K32L2B31VLH0A | | FRDM-K32L3A6 | K32L3A60VPJ1A , K32L3A60VPJ1A | | FRDM-K64F | MK64FN1M0VLL12 , MK64FN1M0VLQ12, MK24FN1M0CAJ12, MK64FX512VMD12, MK63FN1M0VMD12, MK24FN1M0VDC12, MK63FN1M0VLQ12, MK64FN1M0CAJ12, MK64FN1M0VDC12, MK64FN1M0VLL12, MK24FN1M0VLQ12, MK64FX512VLL12, MK64FX512VDC12, MK64FX512VLQ12, MK24FN1M0VLL12, MK64FN1M0VMD12 | | FRDM-K66F | MK66FN2M0VMD18 , MK65FX1M0CAC18, MK65FN2M0VMI18, MK66FX1M0VLQ18, MK66FN2M0VLQ18, MK26FN2M0VLQ18, MK26FN2M0VMI18, MK26FN2M0VMD18, MK65FX1M0VMI18, MK66FN2M0VMD18, MK66FX1M0VMD18, MK65FN2M0CAC18, MK26FN2M0CAC18 | | FRDM-KE02Z40M | MKE02Z64VQH4 , MKE02Z16VLC4, MKE02Z32VLH4, MKE02Z64VLH4, MKE02Z16VLD4, MKE02Z32VLC4, MKE02Z64VFM4, MKE02Z32VQH4, MKE02Z32VLD4, MKE02Z64VLD4, MKE02Z16VFM4, MKE02Z64VLC4, MKE02Z32VFM4, MKE02Z64VQH4 | | FRDM-KE04Z | MKE04Z8VFK4 , MKE04Z8VWJ4, MKE04Z8VFK4, MKE04Z8VTG4 | | FRDM-KE06Z | MKE06Z128VLK4 , MKE04Z128VQH4, MKE04Z64VLK4, MKE04Z128VLH4, MKE06Z64VLH4, MKE06Z128VQH4, MKE04Z64VLD4, MKE04Z128VLD4, MKE04Z128VLK4, MKE04Z64VLH4, MKE04Z64VQH4, MKE06Z64VQH4, MKE06Z64VLD4, MKE06Z128VLK4, MKE06Z128VLD4, MKE06Z64VLK4, MKE06Z128VLH4 | | FRDM-KE15Z | MKE15Z256VLL7 , MKE15Z128VLH7, MKE14Z128VLL7, MKE15Z256VLH7, MKE14Z256VLL7, MKE15Z256VLL7, MKE14Z256VLH7, MKE14Z128VLH7, MKE15Z128VLL7 | | FRDM-KE16Z | MKE16Z64VLF4 , MKE15Z32VLF4, MKE16Z32VLF4, MKE14Z32VLF4, MKE15Z32VLD4, MKE15Z64VLD4, MKE16Z32VLD4, MKE14Z32VFP4, MKE16Z64VLF4, MKE15Z64VFP4, MKE14Z64VFP4, MKE16Z64VLD4, MKE15Z32VFP4, MKE14Z32VLD4, MKE14Z64VLD4, MKE15Z64VLF4, MKE14Z64VLF4 | | FRDM-KL27Z | MKL27Z64VLH4 , MKL27Z64VMP4, MKL27Z64VLH4, MKL17Z32VMP4, MKL17Z32VLH4, MKL17Z32VFT4, MKL17Z64VFM4, MKL27Z32VLH4, MKL27Z32VMP4, MKL17Z64VLH4, MKL27Z32VDA4, MKL17Z64VDA4, MKL17Z32VFM4, MKL27Z64VFM4, MKL27Z32VFM4, MKL17Z64VFT4, MKL27Z32VFT4, MKL27Z64VFT4, MKL17Z32VDA4, MKL27Z64VDA4, MKL17Z64VMP4 | | FRDM-KV11Z | MKV11Z128VLH7 , MKV10Z64VFM7, MKV10Z64VLH7, MKV10Z128VFM7, MKV11Z128VLC7, MKV10Z128VLC7, MKV10Z16VLF7, MKV10Z32VLF7, MKV11Z64VLC7, MKV11Z128VLH7, MKV10Z32VFM7, MKV11Z128VLF7, MKV11Z128VFM7, MKV10Z16VLC7, MKV10Z128VLF7, MKV11Z64VLH7, MKV11Z64VFM7, MKV10Z32VLC7, MKV11Z64VLF7, MKV10Z64VLC7, MKV10Z128VLH7, MKV10Z64VLF7, MKV10Z16VFM7 | | FRDM-KV31F | MKV31F512VLL12 , MKV31F512VLH12, MKV30F128VLF10, MKV31F512VLL12, MKV30F64VFM10, MKV30F128VFM10, MKV31F256VLL12, MKV30F64VLF10, MKV31F128VLH10, MKV30F64VLH10, MKV31F256VLH12, MKV30F128VLH10, MKV31F128VLL10 | | HVP-KV11Z75M | MKV11Z128VLF7 , MKV10Z64VFM7, MKV10Z64VLH7, MKV10Z128VFM7, MKV11Z128VLC7, MKV10Z128VLC7, MKV10Z16VLF7, MKV10Z32VLF7, MKV11Z64VLC7, MKV11Z128VLH7, MKV10Z32VFM7, MKV11Z128VLF7, MKV11Z128VFM7, MKV10Z16VLC7, MKV10Z128VLF7, MKV11Z64VLH7, MKV11Z64VFM7, MKV10Z32VLC7, MKV11Z64VLF7, MKV10Z64VLC7, MKV10Z128VLH7, MKV10Z64VLF7, MKV10Z16VFM7 | | HVP-KV31F120M | MKV31F512VLL12 , MKV31F512VLH12, MKV30F128VLF10, MKV31F512VLL12, MKV30F64VFM10, MKV30F128VFM10, MKV31F256VLL12, MKV30F64VLF10, MKV31F128VLH10, MKV30F64VLH10, MKV31F256VLH12, MKV30F128VLH10, MKV31F128VLL10 | | LPC845BREAKOUT | LPC845M301JBD48 , LPC845M301JHI33, LPC844M201JHI48, LPC845M301JHI48, LPC845M301JBD48, LPC844M201JBD48, LPC844M201JBD64, LPC844M201JHI33, LPC845M301JBD64 | | LPCXpresso51U68 | LPC51U68JBD64 , LPC51U68JBD48, LPC51U68JBD64 | | LPCXpresso54114 | LPC54114J256BD64 , LPC54113J256BD64, LPC54113J128BD64, LPC54114J256BD64, LPC54113J256UK49, LPC54114J256UK49 | | LPCXpresso54628 | LPC54628J512ET180 , LPC54605J512ET100, LPC54608J512BD208, LPC54606J512ET100, LPC54605J512BD100, LPC54605J256ET180, LPC54607J512ET180, LPC54605J512ET180, LPC54607J256BD208, LPC54618J512BD208, LPC54606J256ET100, LPC54605J256BD100, LPC54606J256BD100, LPC54616J256ET180, LPC54607J256ET180, LPC54606J256ET180, LPC54606J512BD208, LPC54616J512BD208, LPC54606J512BD100, LPC54618J512ET180, LPC54608J512ET180, LPC54628J512ET180, LPC54605J256ET100, LPC54616J512BD100, LPC54616J512ET100 | | LPCXpresso54S018 | LPC54S018JET180 , LPC54S016JBD208, LPC54005JBD100, LPC54S018JET180, LPC54016JBD100, LPC54S018JBD208, LPC54016JBD208, LPC54005JET100, LPC54S016JET180, LPC54S016JBD100, LPC54018JET180, LPC54016JET180, LPC54S005JET100, LPC54018JBD208, LPC54S005JBD100 | | LPCXpresso54S018M | LPC54S018J4MET180 , LPC54018J2MET180, LPC54018J4MET180, LPC54S018J2MET180, LPC54S018J4MET180 | | LPCXpresso55S16 | LPC55S16JBD100 , LPC5514JBD64, LPC55S16JBD100, LPC5516JEV98, LPC5516JBD100, LPC5514JBD100, LPC55S14JBD64, LPC55S14JBD100, LPC55S16JEV98, LPC5512JBD100, LPC5516JBD64, LPC55S16JBD64, LPC5512JBD64 | | LPCXpresso55S28 | LPC55S28JBD100 , LPC5526JBD64, LPC5526JEV98, LPC5528JBD100, LPC5528JEV98, LPC55S26JBD64, LPC55S26JBD100, LPC55S28JBD64, LPC55S28JEV98, LPC5526JBD100, LPC5528JBD64, LPC55S26JEV98, LPC55S28JBD100 | | LPCXpresso55S69 | LPC55S69JBD100 , LPC55S66JBD64, LPC55S69JBD100, LPC55S66JEV98, LPC55S69JBD64, LPC55S66JBD100, LPC55S69JEV98 | | LPCXpresso802 | LPC802M001JDH20 , LPC802M001JDH20, LPC802M011JDH20, LPC802UK, LPC802M001JDH16, LPC802M001JHI33 | | LPCXpresso804 | LPC804M101JDH24 , LPC804M101JHI33, LPC804M101JDH20, LPC804M111JDH24, LPC804M101JDH24, LPC804UK | | LPCXpresso812MAX | LPC812M101JDH20 , LPC812M101JDH20, LPC810M021FN8, LPC812M101JDH16, LPC812M101JD20, LPC811M001JDH16, LPC812M101JTB16 | | LPCXpresso824MAX | LPC824M201JHI33 , LPC822M101JDH20, LPC824M201JHI33, LPC834M101FHI33, LPC832M101FDH20, LPC824M201JDH20, LPC822M101JHI33 | | LPCXpresso845MAX | LPC845M301JBD64 , LPC845M301JHI33, LPC844M201JHI48, LPC845M301JHI48, LPC845M301JBD48, LPC844M201JBD48, LPC844M201JBD64, LPC844M201JHI33, LPC845M301JBD64 | | MEK-MIMX8QM | MIMX8QM6AVUFF , MIMX8QM6AVUFF | | MEK-MIMX8QX | MIMX8QX6AVLFZ , MIMX8UX5AVOFZ, MIMX8QX6AVLFZ, MIMX8DX3AVLFZ, MIMX8DX5CVLDZ, MIMX8QX2AVOFZ, MIMX8QX2AVLFZ, MIMX8QX5CVLDZ, MIMX8DX4AVLFZ, MIMX8QX3AVLFZ, MIMX8DX6CVLDZ, MIMX8DX1AVOFZ, MIMX8QX5AVLFZ, MIMX8QX4AVLFZ, MIMX8DX5AVLFZ, MIMX8DX1AVLFZ, MIMX8DX2AVOFZ, MIMX8UX5CVLDZ, MIMX8QX1AVLFZ, MIMX8UX6CVLDZ, MIMX8QX6CVLDZ, MIMX8UX6AVOFZ, MIMX8UX6AVLFZ, MIMX8UX5AVLFZ, MIMX8DX6AVLFZ, MIMX8QX1AVOFZ, MIMX8DX2AVLFZ | | MIMXRT1024-EVK | MIMXRT1024DAG5A , MIMXRT1024DAG5A, MIMXRT1024CAG4A | | TWR-KM35Z75M | MKM35Z512VLQ7 , MKM35Z256VLL7, MKM35Z256VLL7R, MKM35Z512VLL7, MKM35Z256VLQ7R, MKM35Z512VLQ7R, MKM35Z512VLQ7, MKM35Z256VLQ7, MKM35Z512VLL7R |

    MISRA Compliance

    Drivers in this release are checked with MISRA-C 2012 with below exceptions:

    | Exception rules | Description | | --------------- | ------------------------------------------------------------ | | Directive 4.4 | Sections of code should not be commented out. | | Directive 4.5 | Identifiers in the same name space with overlapping visibility should be typographically unambiguous. | | Directive 4.6 | Typedefs that indicate size and signedness should be used in place of the basic numerical types. | | Directive 4.8 | If a pointer to a structure or union is never dereferenced within a translation unit, then the implementation of the object should be hidden. | | Directive 4.9 | A function should be used in preference to a function-like macro where they are interchangeable. | | Directive 4.13 | Functions which are designed to provide operations on a resource should be called in an appropriate sequence. | | Rule 1.2 | Language extensions should not be used. | | Rule 2.3 | A project should not contain unused type declarations. | | Rule 2.4 | A project should not contain unused tag declarations. | | Rule 2.5 | A project should not contain unused macro declarations. | | Rule 2.6 | A function should not contain unused label declarations. | | Rule 2.7 | There should be no unused parameters in functions. | | Rule 4.2 | Trigraphs should not be used. | | Rule 5.1 | External identifiers shall be distinct. | | Rule 5.4 | Macro identifiers shall be distinct. | | Rule 5.9 | Identifiers that define objects or functions with internal linkage should be unique. | | Rule 8.7 | Functions and objects should not be defined with external linkage if they are referenced in only one translation unit. | | Rule 8.9 | An object should be defined at block scope if its identifier only appears in a single function. | | Rule 8.11 | When an array with external linkage is declared, its size should be explicitly specified. | | Rule 8.13 | A pointer should point to a const-qualified type whenever possible. | | Rule 10.5 | The value of an expression should not be cast to an inappropriate essential type. | | Rule 11.4 | A conversion should not be performed between a pointer to object and an integer type. | | Rule 11.5 | A conversion should not be performed from pointer to void into pointer to object. | | Rule 12.1 | The precedence of operators within expressions should be made explicit. | | Rule 12.3 | The comma operator should not be used. | | Rule 12.4 | Evaluation of constant expressions should not lead to unsigned integer wrap-around. | | Rule 13.3 | A full expression containing an increment (++) or decrement (--) operator should have no other potential side effects other than that caused by the increment or decrement operator. | | Rule 15.4 | There should be no more than one break or go to statement used to terminate any iteration statement. | | Rule 17.5 | The function argument corresponding to a parameter declared to have an array type shall have an appropriate number of elements. | | Rule 17.8 | A function parameter should not be modified. | | Rule 19.2 | The union keyword should not be used. | | Rule 20.1 | #include directives should only be preceded by preprocessor directives or comments. | | Rule 20.10 | The # and ## preprocessor operators should not be used. | | Rule 21.1 | #define and #undef shall not be used on a reserved identifier or reserved macro name. | | Rule 21.2 | A reserved identifier or macro name shall not be declared. | | Rule 21.12 | The exception handling features of <fenv.h> should not be used. |

    Known Issues

    1. Maximum file path length in Windows 7 operating system

      The Windows 7 operating system imposes a 260-character maximum length for file paths. When clone the project or unzip the release archive, place it in a directory close to the root to prevent file paths from exceeding the maximum character length specified by the Windows operating system. The recommended location is the C:<folder>.

    Source code(tar.gz)
    Source code(zip)
Owner
NXP Micro
NXP Micro
Enabling services on your device 66 Jun 23, 2022
The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design. This project aims to help C++ developers connect to and interact with services.

Welcome! The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design

Microsoft 6.9k Jun 22, 2022
A modding SDK that allows you to interact with a modified version of Cocos 2DX v2.2.3 utilized by Geometry Dash

What is CappuccinoSDK CappucinoSDK is a modding utility that allows you to interact with a modified version of the game engine Cocos-2DX v2.2.3, which

null 16 Mar 27, 2022
Good Game, Peace Out Rollback Network SDK

(日本語ドキュメントはこちら) What's GGPO? Traditional techniques account for network transmission time by adding delay to a players input, resulting in a sluggish,

Tony Cannon 2.5k Jun 24, 2022
grey sdk

grey是龙游天下公司的产品"汉末霸业"的一个附属产品。开始是为了解决产品的扩展性,自由度,热更新,视频流播放,用户DIY,3d扩展,人工智能等功能而开发。后来把这些功能集成整理后,从而形成了一个完整的应用级解决方案。 grey是一套应用开发解决方案,使用类似c++的语言(cplus)进行开发。 让

grey-platform 51 Jun 18, 2022
A modding SDK for Hitman 3

ZHM Mod SDK A modding SDK and mod loader for HITMAN 3. Description This is a community-made modding SDK and mod loader for HITMAN 3. Its purpose is to

Orfeas Zafeiris 35 Jun 6, 2022
Tuya IoTOS Embeded SDK WiFi & BLE for BK7231T

Tuya IoTOS Embedded Wi-Fi and BLE SDK for BK7231T 中文版 | English Overview Developed independently by Tuya Smart, Tuya IoTOS is the world's only IoT ope

Tuya 31 Jun 19, 2022
C++ Kite Connect API library / SDK

Kite Connect API C++ client Overview Dependencies Getting dependencies Linux Others & uWS v0.14 Building & installation Examples REST API Ticker Docum

Zerodha Technology 23 Jun 2, 2022
Android and iOS SDK to display maps and geodata of swisstopo. Owner: simonroesch, Deputy: gjn

Open Swiss Maps SDK Android and iOS SDK to display maps and geodata of swisstopo Free map layers and geo data by swisstopo in your app Offer your mobi

geo.admin.ch 21 May 20, 2022
Firmware and SDK for the ER-301

ER-301 Sound Computer Table of Contents Introduction Emulator Compiling the emulator Running the emulator Configuring the emulator Installing packages

Orthogonal Devices 100 May 21, 2022
Tuya MCU SDK Arduino Library is developed based on the Tuya Wi-Fi general integration solution

Tuya MCU SDK Arduino Library is developed based on the Tuya Wi-Fi general integration solution. The device's MCU is connected to a Wi-Fi module through a serial port to implement a network connection. The development is based on general firmware, which supports the adaptative 9600 and115200 baud rate

Tuya 74 May 16, 2022
Teamspeak FriendSystem Plugin written in C/C++ (Teamspeak SDK)

Teamspeak-FriendSystem Teamspeak FriendSystem Plugin written in C/C++ (Teamspeak SDK) Install it into AppData / Roaming / Ts3Client / plugins Its only

null 2 Sep 24, 2021
Minecraft Windows 10 Bedrock SDK (1.17.30)

MCBE SDK Minecraft Windows 10 Bedrock SDK (1.17.30) Simple usage: cmake_minimum_required(VERSION 3.20) project(DummieProj VERSION 0.1.0) SET(CMAKE_CX

null 20 Jun 8, 2022
A cross-platform SDK enabling developers to integrate real-time chat technology into their projects

4Players ODIN SDK ODIN is a cross-platform software development kit (SDK) that enables developers to integrate real-time chat technology into multipla

4Players 4 Feb 20, 2022
macOS 12.0 Monterey SDK for Mach engine

macOS 12.0 Monterey SDK for Mach Engine This repository contains native system binary files required to build Mach Engine for macOS, from any host OS.

Hexops 5 Jun 23, 2022
This repository provides a C++ client SDK for Unleash that meets the Unleash Client Specifications.

Unleash Client SDK for C++ This repository provides a C++ client SDK for Unleash that meets the Unleash Client Specifications. Features The below tabl

Antonio Ruiz 4 Jan 30, 2022
MIRACL Cryptographic SDK: Multiprecision Integer and Rational Arithmetic Cryptographic Library is a C software library that is widely regarded by developers as the gold standard open source SDK for elliptic curve cryptography (ECC).

MIRACL What is MIRACL? Multiprecision Integer and Rational Arithmetic Cryptographic Library – the MIRACL Crypto SDK – is a C software library that is

MIRACL 482 Jun 24, 2022
MIRACL Cryptographic SDK: Multiprecision Integer and Rational Arithmetic Cryptographic Library is a C software library that is widely regarded by developers as the gold standard open source SDK for elliptic curve cryptography (ECC).

MIRACL What is MIRACL? Multiprecision Integer and Rational Arithmetic Cryptographic Library – the MIRACL Crypto SDK – is a C software library that is

MIRACL 483 Jun 27, 2022
This repo contains Direct3D 9, Direct3D 10, a few Direct3D 11, and DirectSound C++ samples from the legacy DirectX SDK updated to build using the Windows 10 SDK and the Microsoft.DXSDK.D3DX NuGet package

DirectX SDK Legacy Samples This repo contains Direct3D 9, Direct3D 10, a few Direct3D 11, and DirectSound samples that originally shipped in the legac

Chuck Walbourn 33 Jun 21, 2022
Enabling services on your device 66 Jun 23, 2022
The Raspberry Pi Pico SDK (henceforth the SDK) provides the headers, libraries and build system necessary

The Raspberry Pi Pico SDK (henceforth the SDK) provides the headers, libraries and build system necessary to write programs for the RP2040-based devices such as the Raspberry Pi Pico in C, C++ or assembly language.

Raspberry Pi 1.5k Jul 2, 2022
The Gecko SDK (GSDK) combines all Silicon Labs 32-bit IoT product software development kits (SDKs) based on Gecko Platform into a single, integrated SDK.

Silicon Labs Gecko SDK (GSDK) The Gecko SDK (GSDK) combines Silicon Labs wireless software development kits (SDKs) and Gecko Platform into a single, i

Silicon Labs 91 Jun 16, 2022
The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design. This project aims to help C++ developers connect to and interact with services.

Welcome! The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design

Microsoft 6.9k Jun 22, 2022
Bullet Physics SDK: real-time collision detection and multi-physics simulation for VR, games, visual effects, robotics, machine learning etc.

Bullet Physics SDK This is the official C++ source code repository of the Bullet Physics SDK: real-time collision detection and multi-physics simulati

Bullet Physics SDK 9.4k Jun 30, 2022
NVIDIA PhysX SDK 3.4

NVIDIA PhysX SDK 3.4 Copyright (c) 2018 NVIDIA Corporation. All rights reserved. Redistribution and use in source and binary forms, with or without mo

NVIDIA GameWorks 2.3k Jun 25, 2022
The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design. This project aims to help C++ developers connect to and interact with services.

Welcome! The C++ REST SDK is a Microsoft project for cloud-based client-server communication in native code using a modern asynchronous C++ API design

Microsoft 6.9k Jun 25, 2022
A modding SDK that allows you to interact with a modified version of Cocos 2DX v2.2.3 utilized by Geometry Dash

What is CappuccinoSDK CappucinoSDK is a modding utility that allows you to interact with a modified version of the game engine Cocos-2DX v2.2.3, which

null 16 Mar 27, 2022
The lightweight and modern Map SDK for Android and iOS

Open Mobile Maps The lightweight and modern Map SDK for Android (6.0+) and iOS (10+) openmobilemaps.io Getting started Readme Android Readme iOS Featu

Open Mobile Maps 90 Jun 13, 2022
Good Game, Peace Out Rollback Network SDK

(日本語ドキュメントはこちら) What's GGPO? Traditional techniques account for network transmission time by adding delay to a players input, resulting in a sluggish,

Tony Cannon 2.5k Jun 24, 2022