MCUXpresso Community Articles

cancel
Showing results for 
Search instead for 
Did you mean: 

MCUXpresso Community Articles

NXP Employee
NXP Employee

On November 2nd, 2020 we introduced our latest debug tool - the new MCU-Link debug probe, initially supporting our general purpose Arm(R) Cortex(R)-M based MCUs, priced at just $10.99 from the nxp.com website.

Read more...

More
1 0 77
NXP Employee
NXP Employee

Ázure RTOS ThreadX and other middleware components have now been released for i.MX RT1050/1060/1064 families. This highly optimized, safety-certified software can now be use for free in your projects.

Read more...

More
1 0 127
NXP Employee
NXP Employee

MCUXpresso Config Tools v8.1 release announcement.

Read more...

More
0 0 30
NXP Employee
NXP Employee

We are pleased to announce that MCUXpresso Secure Provisioning Tool v2 is now available.

MCUXpresso Secure Provisioning Tool is a graphical user interface (GUI) tool covering the secure boot
process, aimed primarily at microcontroller customers. It provides unified GUI front-end over existing
command-line tools - FlashLoader, elftosb, blhost, cst.

Read more...

More
0 0 93
NXP Employee
NXP Employee

Interested in a basic overview of the MCUXpresso Secure Provisioning Tool and seeing a live demonstration of the tool?

A new training module for the MCUXpresso Secure Provisioning Tool is posted at the https://nxp.com/training site.

Getting Started with MCUXpresso Secure Provisioning Tool

More
0 0 81
NXP Employee
NXP Employee

There is a wiki page describing the way hot create the SCR entry for the SDK component here.

It is referenced from the MCUX SDK wiki space.

Feel free to put your comments and questions directly on the wiki page. 

SCR wiki.PNG

More
0 0 50
NXP Employee
NXP Employee

NXP has released the newest versions of MCUXpresso SDK, IDE, Configuration Tools, and Secure Provisioning Tool. In addition to new product support, you will find these updates and enhanced features in the new releases:

MCUXpresso SDK v2.8 (Update release)

  • Device support
    • Kinetis/LPC/i.MX/RT boards, devices support
    • Demo applications and examples
  • Middleware
    • USB Stack, TCP/IP stack, NXP WiFi drivers, Cypress Wiced SDK, FatFS, RTOS, CMSIS, emWin, eIQ, MCUBoot, etc. --- Select the middlewares you need when build the MCUXpresso SDK.
  • Development Tools
    • IAR Embedded Workbench for Arm version 8.50.5
    • MDK-Arm Microcontroller Development Kit (Keil)® 5.31
    • Makefiles support with GCC revision 9-2019-q4-major GCC9 from Arm Embedded
    • MCUXpresso IDE v11.2.0
  • Documentation
    • MCUXpresso SDK Release Notes
    • Getting Started with MCUXpresso SDK
    • MCUXpresso SDK API Reference Manual
    • Kinds of user guides and readme


MCUXpresso IDE v11.2.0 (Update release)

  • Upgraded: Eclipse version to 2019.12 (Eclipse Platform 4.14.0 / CDT9.10.0)
  • Upgraded: GNU ARM Embedded Toolchain to GCC9-2019-q4-major
  • Upgraded: GNU make 4.2.1 is now integrated on IDE on all OS-es
  • Upgraded: Version v8 of MCUXpresso Config Tools
  • Upgraded: FreeRTOS TAD synchronization with FreeRTOS 202002.00
  • Upgraded: newer SEGGER J-Link software (v6.80d)
  • Upgraded: newer PEmicro plugin (v4.6.9)
  • Added RT500 B0 support
  • Added flash programming support for QN9090/JN5189
  • Added KW37/KW38/K39 B0 support
  • Improvement: [RT500/RT600] Extended flash drivers to support boards potentially wired in a different way from the EVKs with regards to the reset pin used for the external flash device
  • Improvement: [RT500/RT600] Flash erase performance of RT600 rev B0 flash driver (~30% speed increase)
  • Improvement: 'Delete' option added for plugin SDKs. Now the removal option should be similar with the file system SDKs
  • Improvement: added new control to manage the maximum number of child expressions that are evaluated in advance by the Live Variables service. This improves the Global Variables window responsiveness for instance when large structures are displayed. New control available on Eclipse Preferences -> MCUXpresso IDE -> Debug Options -> "Number of subexpressions proactively evaluated by Live Variables service". Default is 2 set as depth.
  • Improvement: expressions added in Global Variables are now persistent between debug sessions.

    For a comprehensive list of additional fixes, please follow this link.


MCUXpresso Config Tools v8.0 (Update release)

  • Pins tool:
    • Added Expansion headers support
    • Added muxing alt function details in HTML report
  • TEE tool:
    • Added MPU (Memory Protection Unit) support
    • Validations of peripherals security configuration vs interrupts security configuration
    • Validations of linker map file vs TEE configuration
    • Added ability to generate ROM preset data instead of C code
  • Peripherals tool:
    • Register initialization introduced
    • Quick fix button added next to the problematic part of component when fix is available
  • Device Configuration tool:
    • Added support for Cut, Copy and Paste of DCD commands
    • Improved editing with 'Write - clear and set bits' dialog
  • Memory Validation Tool
    • (MCUXpresso IDE only): Added FCB Validation tool, with RT support (untested support for RT600)
  • Project Cloner in New Configuration Wizard
    • Added support for CodeWarrior examples from DSC SDK

MCUXpresso Secure Provisioning Tool v2 (Update release)

  • Enhanced alignment with MCUXpresso Config Tools
    • Utilization of Device Configuration (DCD) and TrustZone configurations
  • Support for LPC55S6x/2x/1x devices
    • Signed / Authenticated images
    • Generation of chained certificates
    • PRINCE encryption is not yet supported
  • Support for i.MX RT1020/1050/1060/1064
    • Bus Encryption Engine (BEE) support

Collateral

More
0 0 109
NXP Employee
NXP Employee

We are pleased to announce that MCUXpresso Config Tools v8 are now available.

 

MCUXpresso Configuration Tools is a product with set of tools that help users of all levels with a Cortex-M-based MCU solution.

Features

  • Available as Web, Desktop application and MCUXpresso IDE plug-ins
  • MCUXpresso SDK v2 support
  • Multicore support
  • GUI localized for English and Simplified Chinese
  • On-Demand device data download for latest features and support
  • Integrated directly within MCUXpresso IDE, standalone version supports other compilers and IDEs
  • Currently there are the following tools available

    MCUXConfigTools_BD.jpg
  • Downloads

     

     

    Revision History

    8.0

    • Pins tool:

      • Added Expansion headers support.

      • Added muxing alt function details in HTML report.

    • TEE tool:

      • Added MPU (Memory Protection Unit) support.

      • Validations of peripherals security configuration vs interrupts security configuration.

      • Validations of linker map file vs TEE configuration

      • Added ability to generate ROM preset data instead of C code

    • Peripherals tool:

      • Register initialization introduced

      • Quick fix button added next to the problematic part of component when fix is available

    • Device Configuration tool:

      • Added support for Cut, Copy and Paste of DCD commands

      • Improved editing with 'Write - clear and set bits' dialog

    • Memory Validation Tool

      • (MCUXpresso IDE only): Added FCB Validation tool, with RT support (untested support for RT600)

    • Project Cloner in New Configuration Wizard

      • Added support for CodeWarrior examples from DSC SDK

  • Community

    MCUXpresso Config Tools

     

    MCUXpresso Config Tools Data

    The Data for MCUXpresso Config Tools v8 was successfully deployed on the production system.

     

    What’s new in data

    • 338 Kinetis, LPC, QN and i.MX processors and 229 boards supported in total
    • Updated code generated by Pins, Clocks and Peripherals tool to support SDK v2.8 API
    • Pins tool
      • Support for expansion headers (e.g. Arduino) for selected boards
    • Peripherals tool
      • Support for FreeMASTER, FatFS, littleFS and debug console components
      • Support for FlexSPI Configuration Block (FCB) component, improved Smart External Memory Controller (SEMC) component
      • Support for RT1010 processors in USB component
      • Added example code of interrupt service routine (reading and clearing of interrupt flags) in interrupt handler reference code (for selected components)
      • Support for user symbols and includes generated in peripherals.h
    • TEE tool
      • Added support of MPU
    • Various other small improvements and bug fixes of Pins, Clocks and Peripherals tool

     

    Supported processors, boards, kits and Peripherals tool components

     

    Components:

     

    Components

    acmp

    adc_12b1msps

    adc_etc

    adc12

    adc16

    aoi

    cadc

    capt

    cau3

    cmp_1

    cmp

    cmt

    cop

    crc

    csi

    ctimer

    dac_1

    dac

    dcp

    debug_console

    dma

    dmic

    dspi

    edma

    eeprom

    elcdif

    enc

    ewm

    fatfs

    fcb

    flexbus

    flexcan

    flexcomm_i2c

    flexcomm_i2s

    flexcomm_spi

    flexcomm_usart

    flexio_i2c

    flexio_i2s

    flexio_mculcd

    flexio_spi

    flexio_uart

    flexspi

    freemaster

    ftm

    generic_can

    generic_uart

    gint

    gpio

    gpt

    hashcrypt

    hsadc

    i2c

    i3c

    igpio

    kpp

    lcdif

    littlefs

    llwu

    lpadc

    lpc_acomp

    lpc_adc

    lpc_crc

    lpc_dac

    lpc_dma

    lpc_gpio

    lpc_i2c

    lpc_lcdc

    lpc_minispi

    lpc_miniusart

    lpc_rtc

    lpc_spi

    lpcmp

    lpi2c

    lpit

    lpsci

    lpspi

    lptmr

    lpuart

    mcan

    mipi_dsi

    mrt

    msg

    mu

    nfc

    ostimer

    otfad

    pdb

    pint

    pit

    plu

    pwm

    qtmr_2

    qtmr

    rit

    rnga

    rtc

    rtwdog

    sai

    sctimer

    semc

    sha

    slcd

    snvs_hp

    snvs_lp

    spdif

    spi

    spm

    system

    tempmon

    tpm

    trng

    tsens

    uart

    usb

    utick

    vref

    vspi

    vusart

    wdog

    wdog01

    wdog32

    wdt

    wkt

    wwdt

     

    Processors:

     

    i.MX

    Kinetis

    LPC

    K32W/JN/QN

    MCIMX7U3xxxxx

    MCIMX7U5xxxxx

    MIMX8DX1xxxFZ

    MIMX8DX2xxxFZ

    MIMX8DX3xxxFZ

    MIMX8DX4xxxFZ

    MIMX8DX5xxxDZ

    MIMX8DX5xxxFZ

    MIMX8DX6xxxDZ

    MIMX8DX6xxxFZ

    MIMX8MD6xxxHZ

    MIMX8MD6xxxJZ

    MIMX8MD7xxxHZ

    MIMX8MD7xxxJZ

    MIMX8MM1xxxKZ

    MIMX8MM1xxxLZ

    MIMX8MM2xxxKZ

    MIMX8MM2xxxLZ

    MIMX8MM3xxxKZ

    MIMX8MM3xxxLZ

    MIMX8MM4xxxKZ

    MIMX8MM4xxxLZ

    MIMX8MM5xxxKZ

    MIMX8MM5xxxLZ

    MIMX8MM6xxxKZ

    MIMX8MM6xxxLZ

    MIMX8MN1xxxJZ

    MIMX8MN2xxxJZ

    MIMX8MN3xxxJZ

    MIMX8MN4xxxJZ

    MIMX8MN5xxxJZ

    MIMX8MN6xxxJZ

    MIMX8MN1xxxIZ

    MIMX8MN2xxxIZ

    MIMX8MN3xxxIZ

    MIMX8MN4xxxIZ

    MIMX8MN5xxxIZ

    MIMX8MN6xxxIZ

    MIMX8MQ5xxxHZ

    MIMX8MQ5xxxJZ

    MIMX8MQ6xxxHZ

    MIMX8MQ6xxxJZ

    MIMX8MQ7xxxHZ

    MIMX8MQ7xxxJZ

    MIMX8QM6xxxFF

    MIMX8QX1xxxFZ

    MIMX8QX2xxxFZ

    MIMX8QX3xxxFZ

    MIMX8QX4xxxFZ

    MIMX8QX5xxxDZ

    MIMX8QX5xxxFZ

    MIMX8QX6xxxDZ

    MIMX8QX6xxxFZ

    MIMX8UX5xxxDZ

    MIMX8UX5xxxFZ

    MIMX8UX6xxxDZ

    MIMX8UX6xxxFZ

    MIMXRT1011xxxxx

    MIMXRT1015xxxxx

    MIMXRT1021xxxxx

    MIMXRT1051xxxxB

    MIMXRT1052xxxxB

    MIMXRT1061xxxxA

    MIMXRT1062xxxxA

    MIMXRT1064xxxxA

    MIMXRT633S

    MIMXRT685S

    K32L2A31xxxxA

    K32L2A41xxxxA

    K32L2B11xxxxA

    K32L2B21xxxxA

    K32L2B31xxxxA

    K32L3A60xxx

    MK02FN128xxx10

    MK02FN64xxx10

    MK10DN512xxx10

    MK10DX128xxx10

    MK10DX256xxx10

    MK11DN512Axxx5

    MK11DN512xxx5

    MK11DX128Axxx5

    MK11DX128xxx5

    MK11DX256Axxx5

    MK11DX256xxx5

    MK12DN512xxx5

    MK12DX128xxx5

    MK12DX256xxx5

    MK20DN512xxx10

    MK20DX128xxx10

    MK20DX256xxx10

    MK21DN512Axxx5

    MK21DN512xxx5

    MK21DX128Axxx5

    MK21DX128xxx5

    MK21DX256Axxx5

    MK21DX256xxx5

    MK21FN1M0Axxx12

    MK21FN1M0xxx12

    MK21FX512Axxx12

    MK21FX512xxx12

    MK22DN512xxx5

    MK22DX128xxx5

    MK22DX256xxx5

    MK22FN128xxx10

    MK22FN128xxx12

    MK22FN1M0Axxx12

    MK22FN1M0xxx12

    MK22FN256xxx12

    MK22FN512xxx12

    MK22FX512Axxx12

    MK22FX512xxx12

    MK24FN1M0xxx12

    MK24FN256xxx12

    MK26FN2M0xxx18

    MK27FN2M0Axxx15

    MK27FN2M0xxx15

    MK28FN2M0Axxx15

    MK28FN2M0xxx15

    MK30DN512xxx10

    MK30DX128xxx10

    MK30DX256xxx10

    MK40DN512xxx10

    MK40DX128xxx10

    MK40DX256xxx10

    MK50DN512xxx10

    MK50DX256xxx10

    MK51DN256xxx10

    MK51DN512xxx10

    MK51DX256xxx10

    MK52DN512xxx10

    MK53DN512xxx10

    MK53DX256xxx10

    MK60DN256xxx10

    MK60DN512xxx10

    MK60DX256xxx10

    MK63FN1M0xxx12

    MK64FN1M0xxx12

    MK64FX512xxx12

    MK65FN2M0xxx18

    MK65FX1M0xxx18

    MK66FN2M0xxx18

    MK66FX1M0xxx18

    MK80FN256xxx15

    MK82FN256xxx15

    MKE02Z16xxx4

    MKE02Z32xxx4

    MKE02Z64xxx4

    MKE04Z128xxx4

    MKE04Z64xxx4

    MKE04Z8xxx4

    MKE06Z128xxx4

    MKE06Z64xxx4

    MKE14F256xxx16

    MKE14F512xxx16

    MKE14Z128xxx7

    MKE14Z256xxx7

    MKE14Z32xxx4

    MKE14Z64xxx4

    MKE15Z128xxx7

    MKE15Z256xxx7

    MKE15Z32xxx4

    MKE15Z64xxx4

    MKE16F256xxx16
    MKE16F512xxx16

    MKE16Z32xxx4

    MKE16Z64xxx4

    MKE18F256xxx16

    MKE18F512xxx16

    MKL02Z16xxx4

    MKL02Z32xxx4

    MKL02Z8xxx4

    MKL03Z16xxx4

    MKL03Z32xxx4

    MKL03Z8xxx4

    MKL13Z32xxx4

    MKL13Z64xxx4

    MKL14Z32xxx4

    MKL14Z64xxx4

    MKL15Z128xxx4

    MKL15Z32xxx4

    MKL15Z64xxx4

    MKL16Z128xxx4

    MKL16Z256xxx4

    MKL16Z32xxx4

    MKL16Z64xxx4

    MKL17Z128xxx4

    MKL17Z256xxx4

    MKL17Z32xxx4

    MKL17Z64xxx4

    MKL24Z32xxx4

    MKL24Z64xxx4

    MKL25Z128xxx4

    MKL25Z32xxx4

    MKL25Z64xxx4

    MKL26Z128xxx4

    MKL26Z256xxx4

    MKL26Z32xxx4

    MKL26Z64xxx4

    MKL27Z128xxx4

    MKL27Z256xxx4

    MKL27Z32xxx4

    MKL27Z64xxx4

    MKL28Z512xxx7

    MKL33Z128xxx4

    MKL33Z256xxx4

    MKL33Z32xxx4

    MKL33Z64xxx4

    MKL34Z64xxx4

    MKL36Z128xxx4

    MKL36Z256xxx4

    MKL36Z64xxx4

    MKL43Z128xxx4

    MKL43Z256xxx4

    MKL46Z128xxx4

    MKL46Z256xxx4

    MKL82Z128xxx7

    MKM34Z256xxx7

    MKM35Z256xxx7

    MKM35Z512xxx7

    MKS20FN128xxx12

    MKS20FN256xxx12

    MKS22FN128xxx12

    MKS22FN256xxx12

    MKV10Z128xxx7

    MKV10Z16xxx7

    MKV10Z32xxx7

    MKV10Z64xxx7

    MKV11Z128xxx7

    MKV11Z64xxx7

    MKV30F128xxx10

    MKV30F64xxx10

    MKV31F128xxx10

    MKV31F256xxx12

    MKV31F512xxx12

    MKV42F128xxx16

    MKV42F256xxx16

    MKV42F64xxx16

    MKV44F128xxx16

    MKV44F256xxx16

    MKV44F64xxx16

    MKV46F128xxx16

    MKV46F256xxx16

    MKV56F1M0xxx24

    MKV56F512xxx24

    MKV58F1M0xxx24

    MKV58F512xxx24

    MKW21D256xxx5

    MKW21D512xxx5

    MKW21Z256xxx4

    MKW21Z512xxx4

    MKW22D512xxx5

    MKW24D512xxx5

    MKW31Z256xxx4

    MKW31Z512xxx4

    MKW35A512xxx4

    MKW35Z512xxx4

    MKW36A512xxx4

    MKW36Z512xxx4

    MKW41Z256xxx4

    MKW41Z512xxx4

    LPC51U68

    LPC54005

    LPC54016

    LPC54018

    LPC54018M

    LPC54101J256

    LPC54101J512

    LPC54102J256

    LPC54102J512

    LPC54113J128

    LPC54113J256

    LPC54114J256

    LPC54605J256

    LPC54605J512

    LPC54606J256

    LPC54606J512

    LPC54607J256

    LPC54607J512

    LPC54608J512

    LPC54616J256

    LPC54616J512

    LPC54618J512

    LPC54628J512

    LPC54S005

    LPC54S016

    LPC54S018

    LPC54S018M

    LPC5512

    LPC5514

    LPC5516

    LPC5526

    LPC5528

    LPC55S14

    LPC55S16

    LPC55S26

    LPC55S28

    LPC55S66

    LPC55S69

    LPC802

    LPC804

    LPC810

    LPC811

    LPC812

    LPC822

    LPC824

    LPC832

    LPC834

    LPC844

    LPC845

    LPC8N04

    JN5189

    K32W061

    QN908XC

    QN9090

     

    Boards:

     

    i.MX

    Kinetis

    LPC

    K32W/JN/QN

    IMXRT1050-EVKB

    MCIMX7ULP-EVK-REV-B

    MIMX8M-EVK-REV-B

    MIMX8MM-EVK-REV-C

    MIMX8MN-EVK-REV-A

    MIMX8QM-MEK-REV-B

    MIMX8QX-MEK-REV-B

    MIMXRT1010-EVK

    MIMXRT1015-EVK

    MIMXRT1020-EVK

    MIMXRT1060-EVK

    MIMXRT1064-EVK

    MIMXRT685-EVK

    FRDM-K22F

    FRDM-K28F

    FRDM-K28FA

    FRDM-K32L2A4S

    FRDM-K32L2B

    FRDM-K32L3A6

    FRDM-K64F

    FRDM-K66F

    FRDM-K82F

    FRDM-KE02Z40M

    FRDM-KE04Z

    FRDM-KE06Z

    FRDM-KE15Z

    FRDM-KE16Z

    FRDM-KL02Z

    FRDM-KL03Z

    FRDM-KL25Z

    FRDM-KL26Z

    FRDM-KL27Z

    FRDM-KL28Z

    FRDM-KL43Z

    FRDM-KL46Z

    FRDM-KL82Z

    FRDM-KV10Z

    FRDM-KV11Z

    FRDM-KV31F

    FRDM-KW24

    FRDM-KW36

    FRDM-KW41Z

    HEXIWEAR

    HVP-KE18F

    HVP-KV11Z75M

    HVP-KV31F120M

    HVP-KV46F150M

    HVP-KV58F

    MAPS-KS22

    TWR-K21D50M

    TWR-K21F120M

    TWR-K22F120M

    TWR-K24F120M

    TWR-K60D100M

    TWR-K64F120M

    TWR-K65F180M

    TWR-K80F150M

    TWR-KE18F

    TWR-KL28Z72M

    TWR-KL43Z48M

    TWR-KL82Z72M

    TWR-KM34Z75M

    TWR-KM35Z75M

    TWR-KV10Z32

    TWR-KV11Z75M

    TWR-KV31F120M

    TWR-KV46F150M

    TWR-KV58F220M

    TWR-KW24D512

    USB-KW24D512

    USB-KW41Z

    LPC54018-IoT-Module

    LPC54S018-IoT-Module

    LPC845BREAKOUT

    LPC8N04DevBoard

    LPCXpresso51U68

    LPCXpresso54018

    LPCXpresso54018M

    LPCXpresso54102

    LPCXpresso54114

    LPCXpresso54608

    LPCXpresso54618

    LPCXpresso54628

    LPCXpresso54S018

    LPCXpresso54S018M

    LPCXpresso55S16

    LPCXpresso55S28

    LPCXpresso55S69

    LPCXpresso802

    LPCXpresso804

    LPCXpresso812

    LPCXpresso824

    LPCXpresso845

    JN5189DK6

    K32W061DK6

    QN908XCDK

    QN9090DK6

     

    Kits:

     

    Kinetis

    FRDM-K22F-AGM01

    FRDM-K22F-SA9500

    FRDM-K64F-AGM01

    FRDM-K64F-MULT2B

    FRDMKL25-A8471

    FRDMKL25-A8491

    FRDMKL25-P3115

More
1 0 427
NXP Employee
NXP Employee

We are pleased to announce that MCUXpresso IDE v11.2.0 (build 4120) is now available. This is a major new version of the IDE, and contains new features, enhancements and bug fixes over the previous versions, including latest announced MCUXpresso IDE v11.1.1 .

 

Installer Downloads

To download the installers for all platforms, please login to our download site via: 

 

Documentation

Additional information can be found in the updated User Guide and other documentation, which can be accessed from the built in help system available via IDE's Help menu and in PDF form from within the installation directory or downloaded from:

 

Notification of future releases

To receive notifications about future releases, please follow : MCUXpresso IDE - Release History 

 

Summary of Changes - version 11.2.0 - July 2020

  • Upgraded: Eclipse version to 2019.12 (Eclipse Platform 4.14.0 / CDT9.10.0).
  • Upgraded: GNU ARM Embedded Toolchain to GCC9-2019-q4-major.
  • Upgraded: GNU make 4.2.1 is now integrated on IDE on all OS-es.
  • Upgraded: Version v8 of MCUXpresso Config Tools.
  • Upgraded: FreeRTOS TAD synchronization with FreeRTOS 202002.00.
  • Upgraded: newer SEGGER J-Link software (v6.80d).
  • Upgraded: newer PEmicro plugin (v4.6.9).
  • Added RT500 B0 support.
  • Added flash programming support for QN9090/JN5189.
  • Added KW37/KW38/K39 B0 support.
  • Improvement: [RT500/RT600] Extended flash drivers to support boards potentially wired in a different way from the EVKs with regards to the reset pin used for the external flash device.
  • Improvement: [RT500/RT600] Flash erase performance of RT600 rev B0 flash driver (~30% speed increase).
  • Improvement: 'Delete' option added for plugin SDKs. Now the removal option should be similar with the file system SDKs.
  • Improvement: Added Help -> "MCUXpresso IDE Save Info For Support" option intended to gather enough information to help reporting an issue:
    • MCU IDE installation details
    • Files from workspace
    • Information about Installed SDK
    • Workspace log file
    • Content of the Console View

        User is encouraged to use this option when reporting an issue and to also attach the generated zip file to help         development team to easier trace the reported problem.

  • Improvement: added new control to manage the maximum number of child expressions that are evaluated in advance by the Live Variables service. This improves the Global Variables window responsiveness for instance when large structures are displayed. New control available on Eclipse Preferences -> MCUXpresso IDE -> Debug Options -> "Number of subexpressions proactively evaluated by Live Variables service". Default is 2 set as depth.
  • Improvement: expressions added in Global Variables are now persistent between debug sessions.
  • Fixed: Error reported while importing SDK example and changing to Newlib (semihost).
  • Fixed: LinkerScript awareness reports fails on /DISCARD/ sections.
  • Fixed: IDE freeze and high CPU power consumption while debugging with Segger debug probe and disconnecting the USB cable.
  • Fixed: SDK import project example copies wrong header file in the case of multiple files with the same name.
  • Fixed: Unticking the "Redirect SDK PRINTF to C library printf" does not reset the ticking settings.
  • Fixed: [LPC11U68] A modified register in peripherals view alters other registers.
  • Fixed: [RT600] Debug error using LinkerServer if RT685 previously went to deep sleep state.
  • Fixed: [RT600] Unable to use "Restart" for debug session on RT600.
  • Fixed: [LPC43xx] "Wrong field format" displayed for SPI peripheral registers on LPC43xx.
  • Fixed: [RT1170] breakpoint support for CM4.
  • Fixed: "Hide Installed" within SDK installer view should be unchecked by default.
  • Fixed: Include directory path for the proper newlib.h is missing when newlib-nano spec is used.
  • Fixed: Global Variables showing negative timestamps after "Clear Data" is used.
  • Fixed: Exception thrown after trying to delete a closed project.
  • Fixed: SDK plugins generated with the IDE contains keywords of examples that are missing in the SDK package.
  • Fixed: ELF parsing issue which in some particular circumstances could cause incomplete flashing of programs generated using user-defined linker scripts (for example tfm SDK examples).
  • Fixed: Linker script error related to "OVERLAY" keyword.
  • Fixed: Internal error displayed when creating a new ldt file in MCUX.
  • Fixed: Empty tooltip for "Global Variables" View when adding variables.
  • Fixed: Linker script parsing error reported as: "missing ';' at '}' ".
  • Fixed: Exception shown when renaming a project after a debug session ended.
  • Fixed: Missing board picture when a SDK is selected within "SDK installer" on Ubuntu.
  • Fixed: Removed board related memories on "New Project Wizard" when "Empty board files" option is selected.
  • Fixed: issue when Global Variables list is empty when going into debug mode.
  • Fixed: xpsr registers for which the values cannot be changed for Cortex M0 boards.
  • Fixed: null pointer exception shown when displaying Globals Variable view in NonStopMode.
  • Fixed: freeze reported when hovering over a large size symbol.
  • Fixed: empty tooltip for Global Variables View when adding variables.
  • Fixed: various UI widgets to correctly display the dark theme.
  • Fixed: the issue when removed variables were continuing to plot data.
  • Fixed: "Remove Selected Variables" always removes all added global variables. This was happening when global variables were added in Global Variables view using "Add new expression".
  • Fixed: Japanese/Chinese font issues on MCUXpressoIDE - this was fixed by the updated eclipse version.
  • Fixed: issue (hang) when display large structures while debugging.

More
0 0 1,021
NXP Employee
NXP Employee

Thanks to all of you that joined the MCUXpresso training we've been providing over the last few weeks and months via our webinars. We've also been adding more training videos covering some of the items from the webinars but also some more in-depth tips and tricks - check them out, and let us know what other videos you'd like to see!

We have another live webinar on May 19th, registration now open: How to leverage the MCUXpresso Config Tools in your application development ... join live to have the chance to ask one of our experts, Clark Jarvis, questions on using these great tools! The recording of the webinar will be available a few days after the event.

 

Advanced Debugging with MCUXpresso IDE - Part 1: Building Debugging and Direct Flashing

https://www.nxp.com/pages/advanced-debugging-with-mcuxpresso-ide-part-1-building-debugging-and-direc...

Advanced Debugging with MCUXpresso IDE - Part 2: Accessing Data and Peripherals

https://www.nxp.com/pages/advanced-debugging-with-mcuxpresso-ide-part-2-accessing-data-and-periphera...

Advanced Debugging with MCUXpresso IDE - Part 3: Code & Data Breakpoints

https://www.nxp.com/pages/advanced-debugging-with-mcuxpresso-ide-part-3-code-data-breakpoints:TIP-AD...

Advanced Debugging with MCUXpresso IDE - Part 4: Instruction Trace

https://www.nxp.com/pages/advanced-debugging-with-mcuxpresso-ide-part-4-instruction-trace:TIP-ADVANC...

Advanced Debugging with MCUXpresso IDE - Part 5: FreeRTOS Task Aware Debug

https://www.nxp.com/pages/advanced-debugging-with-mcuxpresso-ide-part-5-freertos-task-aware-debug:TI...

Advanced Debugging with MCUXpresso IDE - Part 6: SWO trace

https://www.nxp.com/pages/advanced-debugging-with-mcuxpresso-ide-part-6-swo-trace:TIP-ADVANCED-DEBUG...

3-Part Series: Basic Application Development Using MCUXpresso IDE and MCUXpresso Config Tools

https://www.nxp.com/design/training/basic-application-development-using-mcuxpresso-ide-and-mcuxpress...

Creating a Custom Board SDK and Migrating Code Between Boards

Creating a Custom Board SDK and Migrating Code Between Boards | NXP 

More
0 0 251
NXP Employee
NXP Employee

Share your FreeMASTER dashboard designs, get a board!

 

Calling all FreeMASTER fans!

 

Are you an experienced FreeMASTER user who has already created custom dashboards, or are you an HTML/Javascript coder who is new to this great tool and keen to share your creative ideas? With all the possibilities that resources such as jqWidgets, Google, PrimeUI, Plotly.js combined with FreeMASTER offer for creating engaging dashboards to control and/or demo your application, we'd love you to share your creations with the NXP Community. We are giving away* 50 NXP evaluation boards (20 each of the i.MX RT1020 and LPC55S28 EVKs, and 10 of the S32K144EVB) as a thank you to those of you who are willing to share your dashboards with our community.

 

If you aren’t familiar with FreeMASTER dashboard coding yet don’t despair! Our upcoming, 4-part series on FreeMASTER should tell you what you need to know. The webinar series starts with introductory sessions then moves into what you need to know for dashboard coding (assuming you have some familiarity with HTML and Javascript): Click here to register for your session of interest.

 

How to participate?

  1. Submit your idea to the NXP FreeMASTER community using #freemasterdash in the title by June 19, 2020.
    NOW EXTENDED UNTIL TO JULY 31ST!
  2. Link to your idea post in the comments section below within this blog and include your board preference (choose from the MX RT1020 EVK, LPC55S28 development board and S32K144EVB). Boards will be provided on a first come, first served basis until quantities are depleted. Please note: Your final code submission is not limited to the above boards, but can use any Kinetis, LPC, i.MX RT, S32K, S12Z or other supported 32-bit MCUs.
  3. Once you’ve created your code example, post a brief description and a screenshot of your dashboard along with a ZIPped code to this blog comment thread below. Be sure to:
  1. Keep each dashboard code as simple as possible so it serves as a good reference design.
  2. Please only post code that you are ok with others using. Be sure to acknowledge all sources and include licenses as needed! We'd prefer you to avoid code under GNU licenses and this may limit what community members can do with it. All official ‘terms of use’ apply.

What we'd like to see in your design:

  • Define an HTML page which runs in a standalone Chrome browser or embedded in FreeMASTER view switched to Chromium mode. This is a requirement!
  • Make use of JSON-RPC wrapper component as demonstrated in FreeMASTER Lite or described in FreeMASTER 3.0 User Guide section 6.8.2
  • Demonstrate use of graphical HTML5 widgets from vendors including (but not limited to) jqWidgets, Google, PrimeUI, Plotly.js. You can also write your own, but please only use these if you are prepared to share.
  • Create one or more demonstration dashboards (one dashboard = one HTML page), showing use of at least one widget (see some widget ideas below)

 

Additional suggestions (not required!):

  • Use the out-of-box FreeMASTER example application and its "var16", "var32" and other variables running on any Kinetis, LPC, i.MX RT, S32K, S12Z or other supported 32-bit MCU.
  • Angular or linear gauge (different to the one we already provide in the NXP examples) to visualize variable values
  • Sliders, knobs or other controls for variable value modification
  • Interactive graph components showing variable values in time
  • Push buttons, input fields, table grids for variable value control

We look forward to hearing your creative ideas!

 

*Development boards are available on a first come, first served basis until quantities are depleted. The board itself is free, however recipients will be responsible for shipping charges; shipping charges may vary by country. 

More
2 13 2,678
NXP Employee
NXP Employee

Hi,

The sdk data schema and validation has been merged to SDK dev branch and sync to SDK mainline.

The schemas are located in bin\generator\sdk_generator\data\sdk_data_schema.

 

Now the data validation will be the first and mandatory steps for most generator cmds run. For the time being, data record which violates the schemas will be reported as “warning”, because there are many warnings, generator won’t log them into screen but recorded in stage1 yml log. Please open the stage1 yml log fix the warnings.

 

For ymls under main repo, we have already used scripts to remove all deprecated and obvious mistakes. For missing attributes, they are mainly about “description”, “full_name”, “manifest_name”, we will also use scripts to add them with comment. Please update them if needed.

 

For standalone middlewares, please do the correction by yours. Please firstly run check_yaml_data.rb under yml_v1, it will check and pre update most errors, then you need to check the correction. After that, please generate your middleware examples to see if there is any more data errors and fix them.

Some preconditions

  1.      About json schema, you can quickly learn from Getting started step by step
  2.      Please run “gem install json-schema” to install the necessary gems.

 

Here is the link for all materials of the presentation about SDK yml data schema introduction.

Here is the ppt inside.

Here is the video inside(500M+).

Best Regards

SDK core/SDK generator

More
1 0 41
NXP Employee
NXP Employee

New features update:

  •  SDKGEN-1390The SDK yml data schema and validation task[In Progress]

The aim of this task is to provide a solution(schema + validation) for SDK data annotation and validation. It is an integral part of SDK generator solution.

We expect that with this all developers should be able to

  • Figure out how to config yml data by referring schemas with some typical examples
  • Read out the error log for wrong data record and fix them accordingly(Easily check and find out typos in data record).
  • With correct data, there won’t be any “no xxx for nil class” related run abort.

After some research and experiment, we will use json schema. Here is https://json-schema.org/.

The json schema draft 07 version is used to do the work.

The SDK yml data schemas(70% completed) are here.

  • component_schema.yml                the component section schemas
  • component_support_schema.yml        the component support section schemas
  • configuration_schema.yml              the configuration section schemas
  • project_schema.yml                   the application section schemas
  • definitions_schema.yml                the definitions of sub properties(attributes) 

The validation codes are enabled in feature/SDKGEN-1390-sdk-yml-data-schema-and-validation-implementation-integratoin

Now the data validation will be the first and mandatory steps for any generator cmds run. Data record which violates the schemas will be reported as “errors”.

Generator also supports direct “data_validate” cmd that just validating the data.

For example, if you run ruby sdk_frdmk64.rb -c data_validation(Please comment the -c project in that rb), you will get error logs like

component.rtc:

               ERROR:

               - The property '#/component_info/common' did not contain a required property of 'full_name' in schema     D:/git_sdk2.x_featuretry/mcu-sdk-2.0/bin/generator/sdk_generator/data/sdk_data_schema/definitions_schema.yml#

               - The property '#/component_info/common' did not contain a required property of 'description' in schema D:/git_sdk2.x_featuretry/mcu-sdk-2.0/bin/generator/sdk_generator/data/sdk_data_schema/definitions_schema.yml#

 

The left work about the schemas:

  • Need “example” and “description” for all properties in the schemas to illustrate how to write ymls
  • Missing some properties
  • Update current SDK data to fix all the errors. 

When the schemas are 100 percent,detailed training and introduction to all SDK developers.

Some preconditions

  • About json schema, you can quickly learn from Getting started step by step, won’t consume you too much time. It is a mainstream and popular solution for json/yml data annotation and validation.
  • Please run “gem install json-schema” before you run. You can try “ruby sdk_frdmk64.rb -p hello_world” in the 1390 integration branch.

Generator has supported project generation for CodeWarrior Development Studio. This feature is mainly for Nevis3 SDK development and integration.
The yml prototype has been prepared in release/2.7.0_nevis3_ear branch, the generator branch is develop/mcu_sdk_generator.
Here is an validation demo hello_world. You can run batch command after putting source code into repo.
Here is an example:1.png

After project generated, you can import the project into your workspace, just a kinder reminder, do not select "Copy projects into workspace" option.

1.png

After building successfully please select correct debug configuration to debug your project.

1.png

  •  SDKGEN-1465 Support preinclude header file for mucx linked and project

When import a project into mcux, there are two kinds of preojects depends on whether "Copy Sources"  checkbox being cheked:

  • Linked project(no check)
  • Copied project(checked)

Preinclude files worked only with copied project in the past. Now both types can be supported at the same time.

The default setting is copy sources type. You can add an additional attribute "linked_support: true" for the file to enable the feature.

For example:

1.png

  •  SDKGEN-1485 FAQ about how to remove/replace single flag.

Sometimes you just want to remove single flag, "__remove__" tag can be used.
For example:

1.png

Further more, if single flag needs to be replaced, you can firstly use "__remove__" to remove them and then add a new one. Thus other flags will not be affected comparing with "__replace__".
For example:

1.png

Note: You must add flag node as "__remove__" 's sub-node first, then add the flag to be removed under the flag node. Don't try to remove an item as this way:

1.png

More
1 0 41
NXP Employee
NXP Employee

Please find attached a document detailing how to debug the Kinetis KE0x range of MCUs via LinkServer (CMSIS-DAP) debug connections using MCUXpresso IDE version 11.1.1 (or later).

This document and updates within the version 11.1.1 release of MCUXpresso IDE address an issue seen if attempting to debug these parts in earlier versions of MCUXpresso IDE.

Note: it is expected that the issues described in the attached document will be addressed in updated SDK releases for this range of MCUs for use with MCUXpresso IDE version 11.1.1 or later.

Yours,

MCUXpresso IDE Support

More
0 0 225
NXP Employee
NXP Employee

We are pleased to announce that MCUXpresso IDE v11.1.1 (build 3241) is now available.

 

This is a maintenance release that builds upon the previous MCUXpresso IDE v11.1.0, and we recommend that all existing users download and install this new version. It also incorporates a minor update to the integrated MCUXpresso Config Tools.

 

To download the installers for all platforms, please login to our download site via:

Notification of future releases

To receive notifications about future releases, please follow : MCUXpresso IDE - Release History 

Summary of Changes - version 11.1.1 - March 2020

  • Fixed issue with file path handling when importing examples or creating new projects with certain SDKs (previously made available as a hotfix to IDE v11.1.0 via Eclipse update system)
  • Fixed issue that prevented text zooming in Editor View
  • Fixed issue that caused deletion of most compiler defines if the MCU package for a project were changed
  • Updates to linker script file awareness, including
    • Fixed issue handling situation where symbols are quoted
    • Removed requirement for MEMORY command to provide access attributes
  • Updates to map file awareness, including
    • Fixed issue with handling of ld's PROVIDE keyword
  • Fixed issue with linker script generation related to placement of symbols for .ARM.exidx section (which could trigger issue with C++ exceptions)
  • Restructured way eGIT plugin integrated into IDE (to allow updating by the user). Supplied version also updated to v5.6.0
  • Updates to allow LinkServer debug connections (ie CMSIS-DAP) to i.MX RT6xx "rev B" silicon. Note that these changes mean that earlier i.MX RT6xx silicon can no longer be supported
  • Updates to LinkServer debug to provide support for debugging Kinetis KE0x. Note that manual changes to SDK 2.7.0 or earlier are required for this to be enabled
  • Preliminary LinkServer support for i.MX RT1170 devices
  • Fixed sector size issue with LinkServer flash driver for Kinetis KM3x devices
  • Fixed issue that prevented launch configuration creation (and hence debug) for multicore projects for preinstalled parts (LPC43xx and LPC54xxx)
  • Fixed issue with Peripheral View incorrectly handling 32-bit bitfields within peripheral registers
  • Fixed issue with Registers View such that modifying fields in xpsr could incorrectly modify other fields
  • Added mechanism to Preferences to allow default reset settings used when creating SEGGER launch configurations to be overridden for specific devices
  • Updated integrated version of MCUXpresso Config Tools to v7.0.1
    • TEE tool: Displays correctly inaccessible regions in "Memory attribution map" view
  • Upgraded to a later version of the P&E Micro plugin (v4.5.3)
  • Upgraded to a later version of the SEGGER J-Link software (v6.62d)

More
0 0 1,316
NXP Employee
NXP Employee

New features update:

  •  SDKGEN-1389Support Periodic Window Update feature for Keil

        Variables will update periodically if View – Periodic Window Update is selected when debugging. To enable or disable this option, a tag named "periodic_update" should be set in yml. Besides, a .uvoptx template file must be set, or this setting can not take effect.
For example:

1.png

  •  SDKGEN-1430Support to set Heap and Stack placement for Mcuxpresso

         There are two kinds of heap and stack placement styles can be set in Mcuxpresso:

         i. MCUXpresso Style

         ii. LPCXpresso Style

         To set this option, a tag named heap_stack_placement should be added in yml. "MCUXpresso Style" is set by default, therefore the yml setting can be omitted for this style.
         For example:
1.png

       Now release owners/middleware developers can directly generate webdata.xml to check whether its content especially the dependency between middlewares is correct or not.
       There are 2 ways:
        i. From batch, using command line argument "-c webdata"
        ii. From release config yml, add output type webdata.
       This feature can speed up webdata.xml generation by skip examples, manifest and superset generation.
       Here is an example by running batch command: ruby sdk_frdmk64f.yml -c webdata
       1.png

More
1 0 40
NXP Employee
NXP Employee

LPCScrypt v2.1.1 | NXP  is now available. This release incorporates the latest versions of LPC-Link2 firmware for both CMSIS-DAP and also SEGGER J-Link.

LPCScrypt is a command-line based, fast flash (internal and QSPI), EEPROM, OTP and security programming tool for LPC1800 and LPC4300 series microcontrollers. It is also the primary delivery mechanism for supplying and programming CMSIS-DAP firmware images for LPC-Link2 and LPCXpresso Boards.

 

Yours,

 

MCUXpresso IDE Support

More
0 0 278
NXP Employee
NXP Employee

davidjurajda‌:

Yes, it is mandatory. Because the internal SDK repository structure is not same as public package structure you have to support -r.  “-r” is basically transformation between internal repository and external package (file merging, changing folder structure). If you would like to produce public package you have to support also –production, which introduce strict testing.

 

For development purposes I am not recommending to use -r directly (it will mess up whole repository):

mcu-sdk-2.0\bin\generator\batch_v1>ruby all_frdmk64f.rb -p hello_world -r

 

but generate package into external location (this perform -r on background):

mcu-sdk-2.0\bin\generator\batch_v1>ruby all_frdmk64f.rb -c package_raw -o D:\package

or

mcu-sdk-2.0\bin\generator\batch_v1>ruby all_frdmk64f.rb -c package_zip -o D:\package

 

For strict package verification use roznovbuildtest system or Jenkins (there are predefined release configurations):

http://10.171.89.106/

for more information about testing contact @Ivo Solansky

 

Take a look here (just mirror of generator documentation):

http://10.193.108.154:4000/mcu-sdk-generator/doc/Getting%20Started%20With%20SDK%20Generator.html#usa...

Related SDK Generator documentation section:

https://bitbucket.sw.nxp.com/projects/MCUCORE/repos/mcu-sdk-generator/browse/doc/Release%20Actions%2...

More
1 0 50
NXP Employee
NXP Employee

An issue has been identified in MCUXpresso IDE v11.1.0 with SDK 2.7 that in certain circumstances can cause the IDE to issue one or more erroneous duplicate file error popups when importing SDK examples or creating new SDK-based projects. This in particular may occur when targeting i.MX RT10xx devices, with the error referring to the XIP component, for example :

The file 'xip/evkmimxrt1060_flexspi_nor_config.c' already exists in your project but is different from the SDK component file.

pastedImage_1.png

We have now issued a "hotfix" for MCUXpresso IDE v11.1.0 to resolve this issue.

Installation Instructions

From within MCUXpresso IDE v11.1.0, select  "Help -> Check for Updates" from the main menu bar.

This should find the updated version of the "MCUXpresso IDE SDK handling" feature (11.1.0.202001201653):
pastedImage_1.png

Select this, then click through the update wizard to install this. As a final step, you will then need to restart the IDE to complete installation.

Note: You may also find that other updates are available to install, in particular for the "PEMicro Interface Debugging Support" (used for debugging via P&E Micro debug probes). You can also choose to install such updates at the same time as the "MCUXpresso IDE SDK handling" update if you wish.

More
0 0 329
NXP Employee
NXP Employee

Our MCUXpresso SDK is expanding to include more and more graphics examples, including LittleVGL and emWIN support for SPI-based LCDs. The examples we provide can be ported to different controllers, but are based/tested on a shield from Adafruit (product ID:1947) with an ILI9341 TFT controller and FT6206 cap touch controller. Adafruit have released different versions of this shield; early ones (marked as v2.3) work out of the box with NXP's boards, but later versions (that don't have a version number!) need a couple of simple modifications.

Older boards dont have solder pads to select IOREF as 3.3V or 5V, and have the SCK, MISO and MOSI connections defaulting to the standard Arduino pins:

pastedImage_1.png

pastedImage_2.png

On the newer boards you will see the IOREF pads (you need to solder the center pin to the 3.3V pad - be careful not to short all the pads together). On this version the SPI signals default to the ICSP connector instead (for Arduino Leo/Mega), so you will need to cut these and solder bridge the adjacent pads (SCK to 13, SO to 12 and SI to 11):

pastedImage_3.jpg

Now the SDK examples should work without any software changes needed.

More
1 0 486
NXP Employee
NXP Employee

NXP provides MCUXpresso SDKs that are configured for use with our standard evaluation boards. These can be used when carrying out your initial evaluation of our MCUs and early development work. However, in most cases you will reach the point of having your own development or production board. This will mean modifying the pins, clocks and other configuration settings from the evaluation board originally used, generally using the MCUXpresso Config Tools, to match your own board. This will initially be done on a per-project basis.

The Board SDK Creator functionality inside MCUXpresso IDE v11.1.0 and later provides a means of generating a secondary SDK to contain these configuration settings for your board, that can be used in conjunction with the original SDK. This can then be used in assisting with the creation of new projects directly for your board and also be easily shared with other members of your team or customers.

Using Board SDK Creator

Starting from another SDK, you must first create a new project and adapt it for your own board (with updated pins/clock settings), making any board related changes by adding/modifying files in the project’s board folder. Once the changes are completed, in order to create a board SDK, select File -> New Project… from MCUXpresso IDE’s menu bar and select Board SDK Wizard under MCUXpresso IDE Addons category.

pastedImage_3.png

The wizard is also available in the right-click menu in the project explorer.

pastedImage_1.png

Once started the following dialog will be shown.

pastedImage_3.png

The base project will be automatically set if it was already selected in the Project Explorer view. The user interface allows you to define a few basic characteristics of the new SDK being created, such as the name of the custom board, an image of the board, and both brief and more detailed descriptions.

pastedImage_5.png

If the code requires new C/C++ preprocessor definitions, you can add them using the Defines section

Once everything is completed you can choose one of two options under the Wizard target section. The first option asks for a name and location for the SDK zip file.  The second option will open the newly created SDK as a project into the current workspace in MCUXpresso IDE, allowing for more advanced customizations of the SDK.

Using the board SDK

 After selecting first option and pressing “Finish” button, the SDK will be automatically imported into the IDE and a zip file for it will be generated. In order to install it on other computers, simply drag & drop the newly created SDK over the “Installed SDKs” view. Note: original SDK (the one used to create the custom SDK) must have been installed first (the image below shows this, with a custom SDK built from the Kinetis K64F Tower Board SDK.)

pastedImage_8.png

Once installed you can create a new project using the new SDK. The new SDK will appear in the SDK Wizard dialog, as seen for standard SDKs from NXP (see example below).

pastedImage_1.png

From the SDK Wizard select the new board, making sure to select the new SDK in the “SDKs for Selected MCU” section (bottom right corner of the window). Choose “Next” and “Finish” to close the wizard and close the project. The project will contain all the changes you have made in order to support your custom board.

Happy customizing!

More
1 0 512
NXP Employee
NXP Employee

This document introduces the double data rate (DDR) RAM configuration and validation tool, which is an embedded component of Config tools for i.MX.

The DDR tool has two components: DDR configuration tool and DDR validation tool. The DDR configuration tool allows you to create a configuration for the DDR component and the DDR validation tool allows you to validate the DDR configuration using various validation scenarios.

Limitation

- Supports only MIMX8MM family

- Supports only LPDDR4

- Supports only one frequency setpoint

- Validation is not working on MacOS

Prerequisite

- Configure the i.MX target board to boot in Serial Download Mode

- Connect UART cable from PC to board's debug UART port

- Connect USB cable from PC to board's USB OTG port 

- Generate the DDR configuration from Register Programming Aid tool (RPA)

DDR configuration

 

DDR configuration tool provides a user-friendly graphical interface to configure the DDR controller and the DDR PHY. It can be used for tweaking some of the configuration parameters when you want to use different DDR devices from different vendors or when you want to optimize the DDR configuration.  

 

To use the DDR configuration tool, you first need to create a new project for processor with DDR tool support.

 

Before starting with the DDR tool, make sure you have RPA tool for your processor and generate the output.

To create a project for DDR tool, follow these steps:

1. Once you start the Config tools for i.MX, you can create a new configuration from the welcoming window

pastedImage_6.png2. In the next step select the processor with DDR tool support

pastedImage_7.png

3. From the Config Tools Overview select the DDR

4. In DDR configuration view expand the DDRC component to view the configuration

5. Importing output from RPA tool is mandatory in this release of DDR tool. To do this, click on Import DDR Configuration button, browse for the .ds file and click OK

pastedImage_8.png

6. In Input data section imported DDR PHY parameters are displayed

7. In Registers View imported DDR controller registers are displayed

pastedImage_9.png

8. Once the output of RPA tool has been imported, you will see the PHY configuration in DDRC component under Phy Configuration. If configuration needs to be changed, you can do it from the UI

pastedImage_10.png

DDR validation

The DDR validation tool can be used to validate a DDR configuration using predefined scenarios. To start DDR validation tool, open Validation View (go to Views and click on Validation if the view is not open already).

1. There are several predefined scenarios used in validation process

Firmware Init will perform PHY initialization based on the parameters from the Phy Configuration.

Operational is a suite of tests for quick verification of DDR configuration using several tests as Write-Read-Compare, Walking Ones, Walking Zeros.

Stress Tests is a suite of tests meant to verify the performance and stability of the memory in a non-OS environment (beta version in this release).

pastedImage_1.png

2. For each test, except the Firmware Init, you can choose test parameters from Choose Tests tab

pastedImage_2.png

3. To start validation, you must select the correct COM port. Searching for available COM ports is available by click on Scan for available COM ports button

pastedImage_3.png

4. Select the Scenario and tests you want to run and click on Start Validation for running the tests on target board

pastedImage_4.png

5. Tests results are available in Results tab

pastedImage_5.png

6. To switch between simple and detailed log select the Real time option

pastedImage_6.png

7. To run vTSA tests go to Diags tab. Tx Eye (Diag Write Margin) and Rx Eye (Diag Read Margin) tests are available. You can select on which lanes to execute the test from Choose Tests parameters

   The TxEye test collects the transmit eye associated with a specifc byte and bit. The eye is measured by running traffic
   while varying the DRAM VREF and Phy’s TxDq delay settings. The test records how many errors occur at each delay and
   voltage setting and returns a matrix of encoded error counts.

   The RxEye test collects the receive eye associated with a specifc byte and bit. The eye is measured by running traffic
   while varying the Phy’s VREF and RxClkDly delay settings. The test records how many errors occur at each delay and
   voltage setting and returns a matrix of encoded error counts.

8. After the vTSA tests are done the Data Eyes will be displayed in Results

pastedImage_8.png

9. Test results can be saved as JPG by using Generate DDRV Report

pastedImage_5.png

More
0 0 913
NXP Employee
NXP Employee

We are pleased to announce that MCUXpresso Secure Provisioning Tool v1 is now available.

MCUXpresso Secure Provisioning Tools is a graphical user interface (GUI) tool covering the secure boot
process, aimed primarily at microcontroller customers. It provides unified GUI front-end over existing
command-line tools - FlashLoader, elftosb, blhost, cst.

Features

  • Support for i.MX RT1050 and i.MX RT1060
  • Unsigned, HAB signed and HAB encrypted Secure Boot modes
  • Conversion of ELF executables, SREC and raw binaries into bootable images files
  • Generation and management of keys, signatures and certificates associated with the image
  • Connectivity to the target via UART, USB-HID.
  • Writing FlexSPI NOR or SD card boot device including configuration of the boot device parameters
  • Use of DCD configuration enabling booting into SDRAM images
  • Programming eFuses per image and use case requirements
  • Optional generation of batch scripts usable later without the GUI
  • Streamlined operation for general users

SPT_v1.png

Downloads

Known Issues and Limitations

  • On Windows platform make sure the windows FIND utility is found first on the PATH (GNU findutils could break the functionality)
  • On Linux platform the USB and/or Serial device files has to be readable and writable by current user.
        See resources/udev/99-secure-provisioning.rules installed into /etc/udev/rules.d/99-secure-provisioning.rules that solves this issue.
        On user's machine can be conflicting rule with higher priority. In case of conflict,
        update the conflicting rule or make this rule file with higher priority by renaming the file with lower number at beginning.
  • Application has to be installed into location where the user has write access.


Revision History

  • 1.0.1
    • Added support for Mac OS X Catalina (10.15) + Ubuntu 18.04
    • Fixed termination of sub-processes of long-running tasks.
  • 1.0
    • Initial version


More
1 0 265
NXP Employee
NXP Employee

NXP's MCUXpresso Software and Tools has expanded to include a new Secure Provisioning Tool, support for integrated third software solutions and has major improvements in the user experience for software selection. This newly updated suite further augments the easy-to-use SDK, IDE and Configuration Tools for streamlined development with Arm® Cortex®-M cores, including NXP’s LPC and Kinetis MCUs and the  i.MX RT Crossover Processors. A (comprehensive) list of supported devices can be found in the MCUXpresso community here: https://community.nxp.com/docs/DOC-333073

MCUXpresso software and tools bring together the best of NXP’s software enablement (core technologies) and integrated solutions from select partners (enabling technologies) into one enablement ecosystem for a shared software experience across a broad set of Arm® Cortex®-M MCUs.

291598-CS_MCUXpresso_EcoGraphic-01.png

The MCUXpresso software and tools core technologies include the MCUXpresso SDK, MCUXpresso IDE , MCUXpresso Config Tools and the MCUXpresso Secure Provisioning Tool.

Integrated middleware in the MCUXpresso SDK brings full application examples to life for connectivity, cloud, storage, security, ML/AI, graphics and HMI, and motor control applications. New Enabling Software Technology examples from strategic graphics and connectivity partners make it easy to transition to licensed products without needing development environment changes. A new front-end to MCUXpresso IDE now enables selection of SDK packages directly from within the tool, and SDK Builder has been updated to make middleware selection easier than ever before.

NXP continues to work with leading development tool technology partners, including Arm Keil and IAR Systems, P&E Micro, and SEGGER to ensure options for leading partner IDE and debug tool support options are available. NXP’s industry leading FreeMASTER advanced data visualization tool is also now available across most of our General Purpose MCUs, enabling runtime configuration and tuning of embedded software applications. Collectively, these enabling tool technologies make it easy for customers to work efficiently from evaluation, through application development, into design.

Learn more at https://www.nxp.com/mcuxpresso and visit the MCUXpresso Community to learn more about specific updates and features https://community.nxp.com/community/mcuxpresso

 

Look out for new MCUXpresso presentations, updated videos and more training resources coming from January and throughout Q1 2020!

More
0 0 324
NXP Employee
NXP Employee

New versions of MCUXpresso SDK, IDE, and Configuration Tools are now available, along with a new Secure Provisioning Tool. Please see below to learn more about these updates updates and enhanced features in the new releases:

MCUXpresso Secure Provisioning Tool v1  (NEW Release)

  • New MCUXpresso Tool designed for certificate and key management, secure image preparation, and device provisioning and programming.
  • Secure provisioning via unified graphical UI and command-line interface
  • Support included for i.MX RT1050 and i.MX RT1060 device, supporting HAB4 secure boot flow including signed and encrypted images. Support for LPC devices and features is planned in afuture release, elftosb_gui is currently available as an alternative solution within the MCUXpresso SDK (included with MCU Boot).
  • Uses several existing utilities (unifying them with a common GUI / CLI):
    • elftosb
    • blhost/Flashloader
    • CST/srktool
    • sdphost
  • Supports generation and management of keys, signatures, and certificates associated with encrypting and signing an application.
  • Provides a unified command-line interface to allow for automated scripting of device provisioning and programming.

 

MCUXpresso SDK v2.7 (Update release)

  • Updated peripheral drivers to v2.7.0 SDK code base for all included boards and devices
  • New integrated enabling software technologies (stacks and middleware) –
    • CANopen stacks from EmSA
    • Embedded Wizard by TARA
    • Google Cloud IoT Core
    • LittlevGL
    • Storyboard by Crank Software
  • Updated included middleware –
    • Amazon FreeRTOS Kernel 201908.00
    • Cypress Wi-Fi v6.4.0
    • FatFs v0.13c
    • lwIP v2.1.2+
    • Mbed TLS v2.16.2
    • Microsoft Azure Cloud Connectivity SDK v1.3.4
    • SEGGER emWin v5.50g
  • Updated GNU Arm Embedded Toolchain to GCC8 (2019-q3-update)

 

 

MCUXpresso IDE v11.1 (Update release)

  • New welcome system with built-in SDK selection
  • New SDK plug-in system to simplify SDK installation and management
  • Improved support for Middleware components in New project wizard
  • Improved multi-core, secure/non-secure debug support
  • Flash driver performance improvements
  • Multiple improvements to Image Info view
  • Updated SDK Creator, including photo and metatag customization
  • Added MCUXpresso Dark Theme color options
  • Reduced code size of debug builds by optimization of assert() functions
  • Updated underlying Eclipse and GCC components:
    • Eclipse 4.12.0.v201906 / CDT9.8.1
    • GCC8-2019q3-update

 

MCUXpresso Config Tools v7.0 (Update release)

  • Updated to Trusted Execution Environment tool to allow for easier navigation, visualization of memory regions, and improved alignment with MCUXpresso IDE MCU memory settings.
  • Improved support for FlexSPI configuration within the Peripheral Tool
  • Support for new devices and middleware configuration
  • Improved handling of peripheral structure names
  • Support for external memory validation (SEMC/SDRAM and FlexSPI/NOR) UI support for Dark Theme

More
0 0 283
NXP Employee
NXP Employee

We are pleased to announce that MCUXpresso Config Tools v7 are now available.

 

MCUXpresso Configuration Tools is a product with set of tools that help users of all levels with a Cortex-M-based MCU solution.

Features

  • Available as Web, Desktop application and MCUXpresso IDE plug-ins
  • MCUXpresso SDK v2 support
  • Multicore support
  • GUI localized for English and Simplified Chinese
  • On-Demand device data download for latest features and support
  • Integrated directly within MCUXpresso IDE, standalone version supports other compilers and IDEs
  • Currently there are the following tools available: 

MCUXConfigTools_BD.jpg

Downloads

 

Revision History

7.0.1

  • Mac OS X 10.15 operating system support added.

  • TEE tool: Displays correctly inaccessible regions in "Memory attribution map" view.7.0

7.0

  • Added "Help | Kit/Board Information" option that displays information about currently used kit or board.
  • Clickable Part number, Board and Kit name supported. It displays information about currently used processor, board and kit.
  • Data Manager - supports clearing locally cached processors, boards, kit and components content.
  • Configuration Preferences - supports custom copyright in generated sources
  • TEE tool: Memory map is now interactive, cell double click opens its configuration.
  • TEE tool: Memory map now displays peripherals space details.
  • TEE tool: Added possibility to import memory configuration from MCUXpresso IDE project(s).
  • TEE tool: Memory regions in Access overview are now grouped by memory type; all memory region aliases are displayed in a single row.
  • TEE tool: Pins table now contains pin labels from the Pins tool.
  • TEE tool: Additional validations and security setting recommendations.
  • Peripherals tool: Tool can now generate binary output files.
  • Peripherals tool: Component name is derived from the selected peripheral by default. It can be overwritten by a user.
  • Peripherals tool: Documentation view improvements related to navigation added two new features - header with links in documentation content and selection box in header of view.
  • Peripherals tool: Deprecated components have "(deprecated)" suffix in the add component dialog if there are still other instances of this type in configuration.
  • Pins tool: Added automatic routing feature which can be used for conflict resolution in the current functional group.
  • (MCUXpresso Config Tools only): Preferences - Added Dark theme support
  • (MCUXpresso IDE only): Added SEMC/SDRAM stress tests, with RT support.
  • (MCUXpresso IDE only): Added FlexSPI/NOR Validation tool, with RT support.


Community

MCUXpresso Config Tools

 

 

MCUXpresso Config Tools Data

The Data for MCUXpresso Config Tools v7 was successfully deployed on the production system.

 

What’s new in data

The Data for MCUXpresso Config Tools v7 release provides following updates:

  • 330 Kinetis, LPC and i.MX processors and 229 boards supported in total.
  • Updated code generated by Pins, Clocks and Peripherals tool to support SDK v2.7 API.
  • Peripherals tool support added for LPC8N04, KV11/4x/5x, KExx, KV3x and K22 (FN1M0 and FX512 memory variants only) processors. 200 processors supported by Peripherals tool in total - all processors in SDK v2.7 are supported by Peripherals tool now.
  • Added 21 new Peripherals tool components for various Kinetis, LPC and i.MX RT processors. 103 components are available now in total.
  • Improved DMA support in Peripherals tool - edma and lpc_dma components updated to support transactional and non-transactional modes, improved support of DMA request settings in other Peripherals tool components.
  • Improved interrupt settings in Peripherals tool components, added default interrupt subroutine snippets.
  • Added new Audio 1.0 and Device Firmware Update classes to USB Peripherals tool component, supported suspend/resume/remote wake-up feature, improved PHDC class support and USB endpoint settings.
  • Added support of Memory validation for i.MX8MM processors, maintenance update of Memory validation/DDR tool supporting RT1020, RT1050, RT1060, RT1064 and i.MX8MM processors.
  • Updated TEE tool for LPC55S6x processors.
  • Various other small improvements and bug fixes of Pins, Clocks and Peripherals tool. 

Supported processors, boards, kits and components

 

i.MX

Kinetis

LPC

QN

imx7ulp-14x14-arm2

imx7ulp-evk

imx7ulp-evk-emmc

imx7ulp-evk-emmc-qspi

imx7ulp-evk-ft5416

imx7ulp-evk-lpuart

imx7ulp-evk-mipi

imx7ulp-evk-qspi

imx7ulp-evk-sd1

imx7ulp-evk-sensors-to-i2c5

imx7ulp-evk-wm8960

IMXRT1050-EVKB

MCIMX7ULP-EVK-REV-B

MIMX8M-EVK-REV-B

MIMX8MM-EVK-REV-C

MIMX8MN-EVK-REV-A

MIMX8QM-MEK-REV-B

MIMX8QX-MEK-REV-B

MIMXRT1010-EVK

MIMXRT1015-EVK

MIMXRT1020-EVK

MIMXRT1060-EVK

MIMXRT1064-EVK

FRDM-K32L3A6

FRDM-K32L2B

FRDM-K22F

FRDM-K28F

FRDM-K28FA

FRDM-K64F

FRDM-K66F

FRDM-K82F

FRDM-KE02Z40M

FRDM-KE04Z

FRDM-KE06Z

FRDM-KE15Z

FRDM-KE16Z

FRDM-KL02Z

FRDM-KL03Z

FRDM-KL25Z

FRDM-KL26Z

FRDM-KL27Z

FRDM-KL28Z

FRDM-KL43Z

FRDM-KL46Z

FRDM-KL82Z

FRDM-KV10Z

TWR-KV58F220M

TWR-KW24D512

USB-KW24D512

USB-KW41Z

FRDM-KV11Z

FRDM-KV31F

FRDM-KW24

FRDM-KW36

FRDM-KW41Z

HEXIWEAR

HVP-KE18F

HVP-KV11Z75M

HVP-KV31F120M

HVP-KV46F150M

HVP-KV58F

MAPS-KS22

TWR-K21D50M

TWR-K21F120M

TWR-K22F120M

TWR-K24F120M

TWR-K60D100M

TWR-K64F120M

TWR-K65F180M

TWR-K80F150M

TWR-KE18F

TWR-KL28Z72M

TWR-KL43Z48M

TWR-KL82Z72M

TWR-KM34Z75M

TWR-KV10Z32

TWR-KV11Z75M

TWR-KV31F120M

TWR-KV46F150M

LPC54018-IoT-Module

LPC54S018-IoT-Module

LPC8N04DevBoard

LPCXpresso51U68

LPCXpresso54018

LPCXpresso54018M

LPCXpresso54102

LPCXpresso54114

LPCXpresso54608

LPCXpresso54618

LPCXpresso54628

LPCXpresso54S018

LPCXpresso54S018M

LPCXpresso802

LPCXpresso804

LPCXpresso812

LPCXpresso824

LPCXpresso845

LPC845BREAKOUT

LPCXpresso55S28

LPCXpresso55S69

QN908XCDK

Processors:

i.MX

Kinetis

LPC

MCIMX7U3xxxxx

MCIMX7U5xxxxx

MIMX8MD6xxxHZ

MIMX8MD6xxxJZ

MIMX8MD7xxxHZ

MIMX8MD7xxxJZ

MIMX8MM1xxxKZ

MIMX8MM1xxxLZ

MIMX8MM2xxxKZ

MIMX8MM2xxxLZ

MIMX8MM3xxxKZ

MIMX8MM3xxxLZ

MIMX8MM4xxxKZ

MIMX8MM4xxxLZ

MIMX8MM5xxxKZ

MIMX8MM5xxxLZ

MIMX8MM6xxxKZ

MIMX8MM6xxxLZ

MIMX8MN1xxxIZ

MIMX8MN1xxxJZ

MIMX8MN2xxxIZ

MIMX8MN2xxxJZ

MIMX8MN3xxxIZ

MIMX8MN3xxxJZ

MIMX8MN4xxxIZ

MIMX8MN4xxxJZ

MIMX8MN5xxxIZ

MIMX8MN5xxxJZ

MIMX8MN6xxxIZ

MIMX8MN6xxxJZ

MIMX8MQ5xxxHZ

MIMX8MQ5xxxJZ

MIMX8MQ6xxxHZ

MIMX8MQ6xxxJZ

MIMX8MQ7xxxHZ

MIMX8MQ7xxxJZ

MIMX8QM6xxxFF

MIMX8QX2xxxFZ

MIMX8QX6xxxFZ

MIMXRT1011xxxxx

MIMXRT1015xxxxx

MIMXRT1021xxxxx

MIMXRT1051xxxxB

MIMXRT1052xxxxB

MIMXRT1061xxxxA

MIMXRT1062xxxxA

MIMXRT1064xxxxA

 

K32L3A60xxx

K32L2B11xxxxA

K32L2B21xxxxA

K32L2B31xxxxA

MK02FN128xxx10

MK02FN64xxx10

MK10DN512xxx10

MK10DX128xxx10

MK10DX256xxx10

MK11DN512Axxx5

MK11DN512xxx5

MK11DX128Axxx5

MK11DX128xxx5

MK11DX256Axxx5

MK11DX256xxx5

MK12DN512xxx5

MK12DX128xxx5

MK12DX256xxx5

MK20DN512xxx10

MK20DX128xxx10

MK20DX256xxx10

MK21DN512Axxx5

MK21DN512xxx5

MK21DX128Axxx5

MK21DX128xxx5

MK21DX256Axxx5

MK21DX256xxx5

MK21FN1M0Axxx12

MK21FN1M0xxx12

MK21FX512Axxx12

MK21FX512xxx12

MK22DN512xxx5

MK22DX128xxx5

MK22DX256xxx5

MK22FN128xxx10

MK22FN128xxx12

MK22FN1M0Axxx12

MK22FN1M0xxx12

MK22FN256xxx12

MK22FN512xxx12

MK22FX512Axxx12

MK22FX512xxx12

MK24FN1M0xxx12

MK24FN256xxx12

MK26FN2M0xxx18

MK27FN2M0Axxx15

MK27FN2M0xxx15

MK28FN2M0Axxx15

MK28FN2M0xxx15

MK30DN512xxx10

MK30DX128xxx10

MK30DX256xxx10

MK40DN512xxx10

MK40DX128xxx10

MK40DX256xxx10

MK50DN512xxx10

MK50DX256xxx10

MK51DN256xxx10

MK51DN512xxx10

MK51DX256xxx10

MK52DN512xxx10

MK53DN512xxx10

MK53DX256xxx10

MK60DN256xxx10

MK60DN512xxx10

MK60DX256xxx10

MK63FN1M0xxx12

MK64FN1M0xxx12

MK64FX512xxx12

MK65FN2M0xxx18

MK65FX1M0xxx18

MK66FN2M0xxx18

MK66FX1M0xxx18

MK80FN256xxx15

MK82FN256xxx15

MKE02Z16xxx4

MKE02Z32xxx4

MKE02Z64xxx4

MKE04Z128xxx4

MKE04Z64xxx4

MKE04Z8xxx4

MKE06Z128xxx4

MKE06Z64xxx4

MKE14F256xxx16

MKE14F512xxx16

MKE14Z128xxx7

MKE14Z256xxx7

MKE14Z32xxx4

MKE14Z64xxx4

MKE15Z128xxx7

MKE15Z256xxx7

MKE15Z32xxx4

MKE15Z64xxx4

MKE16F256xxx16

MKE16F512xxx16

MKE16Z32xxx4

MKE16Z64xxx4

MKE18F256xxx16

MKE18F512xxx16

MKL02Z16xxx4

MKL02Z32xxx4

MKL02Z8xxx4

MKL03Z16xxx4

MKL03Z32xxx4

MKL03Z8xxx4

MKL13Z32xxx4

MKL13Z64xxx4

MKL14Z32xxx4

MKL14Z64xxx4

MKL15Z128xxx4

MKL15Z32xxx4

MKL15Z64xxx4

MKL16Z128xxx4

MKL16Z256xxx4

MKL16Z32xxx4

MKL16Z64xxx4

MKL17Z128xxx4

MKL17Z256xxx4

MKL17Z32xxx4

MKL17Z64xxx4

MKL24Z32xxx4

MKL24Z64xxx4

MKL25Z128xxx4

MKL25Z32xxx4

MKL25Z64xxx4

MKL26Z128xxx4

MKL26Z256xxx4

MKL26Z32xxx4

MKL26Z64xxx4

MKL27Z128xxx4

MKL27Z256xxx4

MKL27Z32xxx4

MKL27Z64xxx4

MKL28Z512xxx7

MKL33Z128xxx4

MKL33Z256xxx4

MKL33Z32xxx4

MKL33Z64xxx4

MKL34Z64xxx4

MKL36Z128xxx4

MKL36Z256xxx4

MKL36Z64xxx4

MKL43Z128xxx4

MKL43Z256xxx4

MKL46Z128xxx4

MKL46Z256xxx4

MKL82Z128xxx7

MKM34Z256xxx7

MKS20FN128xxx12

MKS20FN256xxx12

MKS22FN128xxx12

MKS22FN256xxx12

MKV10Z128xxx7

MKV10Z16xxx7

MKV10Z32xxx7

MKV10Z64xxx7

MKV11Z128xxx7

MKV11Z64xxx7

MKV30F128xxx10

MKV30F64xxx10

MKV31F128xxx10

MKV31F256xxx12

MKV31F512xxx12

MKV42F128xxx16

MKV42F256xxx16

MKV42F64xxx16

MKV44F128xxx16

MKV44F256xxx16

MKV44F64xxx16

MKV46F128xxx16

MKV46F256xxx16

MKV56F1M0xxx24

MKV56F512xxx24

MKV58F1M0xxx24

MKV58F512xxx24

MKW21D256xxx5

MKW21D512xxx5

MKW21Z256xxx4

MKW21Z512xxx4

MKW22D512xxx5

MKW24D512xxx5

MKW31Z256xxx4

MKW31Z512xxx4

MKW35A512xxx4

MKW35Z512xxx4

MKW36A512xxx4

MKW36Z512xxx4

MKW41Z256xxx4

MKW41Z512xxx4

LPC51U68

LPC54005

LPC54016

LPC54018

LPC54101J256

LPC54101J512

LPC54102J256

LPC54102J512

LPC54113J128

LPC54113J256

LPC54114J256

LPC54605J256

LPC54605J512

LPC54606J256

LPC54606J512

LPC54607J256

LPC54607J512

LPC54608J512

LPC54616J256

LPC54616J512

LPC54618J512

LPC54628J512

LPC54S005

LPC54S016

LPC54S018

LPC54018M

LPC54S018M

LPC802

LPC804

LPC810

LPC811

LPC812

LPC822

LPC824

LPC832

LPC834

LPC844

LPC845

LPC8N04

LPC5526

LPC5528

LPC55S26

LPC55S28

LPC55S66

LPC55S69

QN

QN908XC

Components:

Components

acmp

adc12

adc16

adc_12b1msps_sar

adc_etc

aoi

capt

cmp_1

cmp

cmt

cop

crc

csi

ctimer

dac

dcp

dma

dmic

dspi

edma

eeprom

elcdif

enc

ewm

flexbus

flexcan

flexcomm_i2c

flexcomm_i2s

flexcomm_spi

flexcomm_usart

flexio_i2c_master

flexio_i2s

flexio_spi

flexio_uart

flexspi

ftm

gint

gpio

gpt

hashcrypt

i2c

igpio

kpp

llwu

lpadc

lpc_acomp

lpc_adc

lpc_crc

lpc_dac

lpc_dma

lpc_gpio_1

lpc_gpio

lpc_i2c_1

lpc_i2c

lpc_lcdc

lpc_minispi

lpc_miniusart

lpc_rtc_1

lpc_rtc

lpc_spi_ssp

lpi2c

lpit

lpsci

lpspi

lptmr

lpuart

mcan

mrt

msg

nfc

ostimer

pdb

pint

pit

plu

pwm

qtmr

rit

rnga

rtc

rtwdog

sai

sctimer

semc

sha

snvs_hp

snvs_lp

spdif

spi

system

tempmon

tpm

trng

tsens

uart

usb

utick

vref

vspi

vusart

wdog01

wdog32

wdog

wdt

wkt

wwdt

More
0 0 683
NXP Employee
NXP Employee

We are pleased to announce that MCUXpresso IDE v11.1.0 (build 3209) is now available. This is a major new version of the IDE, and contains many new features and enhancements over the previous MCUXpresso IDE v11.0.1 and earlier releases.

Overview Presentation

The attached presentation, recommended viewing for all users (new or experienced), provides an overview of many of the major changes, as well as things to be aware of when upgrading from an earlier release:

This complements the information provided in the IDE's release notes (also included at the end of this post).

Installer Downloads

To download the installers for all platforms, please login to our download site via: 

 

Documentation

Additional information can be found in the updated User Guide and other documentation, which can be accessed from the built in help system available via IDE's Help menu and in PDF form from within the installation directory or downloaded from:

 

Notification of future releases

To receive notifications about future releases, please follow : MCUXpresso IDE - Release History 

Summary of Changes - version 11.1.0 - December 2019

  • Upgraded underlying Eclipse Framework to 4.12.0.v201906 / CDT9.8.1
  • Upgraded supplied GNU ARM Embedded Toolchain to GCC8-2019q3-update
  • Added support for MCUXpresso SDK v2.7
  • Upgraded integrated version of MCUXpresso Config Tools to v7
  • New Welcome View, providing an improved out-of-box experience for new users. The IDE now also opens for the first time at a larger default window size, improving usability without the need for resizing
  • New "plugin SDK" system provides an easy-to-use mechanism for simplified installation and management of MCUXpresso SDKs
  • Reduced code size of debug builds of SDK projects by decreasing the overhead of the assert() function, which is commonly called by SDK functions. This has been done by the addition of "-fmerge-constants" and "-fmacro-prefix-map" compiler options to project compiler optimization settings
  • Added support for more complex specification of dependencies between SDK components. This allows some components (in particular, middleware ones) that previously could only be accessed through SDK examples, to now be added to projects and configured, either as they are created by the new project wizard, or for existing projects via "Manage SDK Components". Note that this functionality requires SDK 2.7
  • Various enhancements to "Installed SDKs" View, including:
    • New tabs provide easy access to the list of boards and devices that are installed into IDE, in addition to the actual SDKs.
    • Right click menu on a board or device also allows new project wizard (and, for boards, import example wizard) to be run
    • Detailed information on contents of selected SDK is now displayed in Outline View
    • Improved loading of SDKs, including refreshing, improving performance and fixing memory leaks
    • Copy/paste of SDKs now allowed between View and OS filer, as well as between different IDE instances
  • Fixed an issue with sorting of boards in SDK wizards
  • Fixed an issue with handling of combined secure / non-secure with multicore projects
  • Fixed issue with "Manage SDK Components" removing &quot from C++ Symbols in .cproject file
  • Various fixes and enhancements to SDK Editor / Creator, to support "user board SDKs" to act as an extension to a standard MCUXpresso SDK
  • Various fixes and enhancements to Image Info View. In particular:
    • Further improvements to load times
    • Added ability to double-click on memory region in Memory Usage tab and jump to that region in the Memory Contents tab
    • "Load" from project button now provides a drop-down to allow direct loading of info from multiple build configurations into multiple Image Info Views
    • Regular expressions now supported in "Search..." box
    • "Open 'main' symbol" button implemented on toolbar
    • Improved support for projects outside the workspace
  • Various improvements and fixes to map file awareness, including:
    • Improved handling of C++ projects
    • Fixed an issue with handling expressions containing parentheses
  • Various improvements and fixes to linker script file awareness, including improved handling of libraries specified in script
  • Various improvements to the managed linker script system:
    • Standardized set of symbols now generated for sections
    • Fixed an issue with LMA being incorrectly set in some circumstances for sections that do not have a real load address (e.g. .bss). Although this did not prevent the generated image from working, it could cause, for example, erroneous information in Image Info View
    • Plain load image functionality now supported for RT6xx devices
    • LinkServer FreeRTOS debug config rodata now placed by script, when appropriate
  • Increased default java memory settings (-Xms, -Xmx) in mcuxpressoide.ini file. This means the IDE may now use up to 2GB by default
  • Windows build tools now provide 'mv' command
  • Added MCUXpresso Dark Theme, providing better support for IDE's tailored set of Views being used in dark mode
  • * Improved organization of MCUXpresso IDE preferences, in
    particular Debug related ones
  • Project decorators implemented in Project Explorer View to indicate Master/Slave and Secure/Non-secure projects
  • Standardized graphing technology used by SWO Interrupt trace and by Global Variables View
  • Improvements to LinkServer flash driver performance for many devices. In particular, most flash drivers now implement a
    "verify-same" hashing mechanism to remove the need to erase/reprogram when the memory being programmed already has the required content. This can provide a noticeable improvement in debug startup time, particularly when repeatably debugging large, non-changing images
  • Required debug probe can now be selected by double-clicking on it in the "Probes discovered" dialog
  • Global Variables View now uses a check-box system to select variables to be displayed in graphs within the details pane
  • Improved handling of certain variable types, along with signed versus unsigned variables, within the Global Variables View
  • Fixed an issue with display of large arrays in Global Variables View with SEGGER and P&E Micro debug connections, when Live variables are enabled
  • Various fixes and enhancements to the Peripherals View, in particularly some registers being marked as inaccessible when single stepping
  • Fixed an issue with Disassembly View going blank after Restart, with LinkServer debug connections
  • Fixed an issue with flash programming with P&E Micro probes when filename or path contains a space
  • Fixed various memory leaks triggered during debugging
  • Fixed an issue with decoding correct stack pointer to be used in Faults View
  • When debugging secure / non-secure projects, you can now set breakpoints in CMSE functions and view source when breakpoints hit
  • Reduced the RAM footprint of the FTFA_1K.cfx LinkServer flash driver, to prevent issues on some smaller RAM devices that make use of this driver (e.g. MKE14Z32)
  • Additional and improved Linkserver connect scripts for RT10xx devices, which in particular reset the FlexRAM sizes to default. Note that for some devices, these will only be picked up by default if you are using an appropriate SDK 2.7
  • Fixed an issue that could prevent LinkServer SWO trace and power measurement from working on Linux platforms in some circumstances
  • Fixed an issue with setting wirespeed in LinkServer launch configurations
  • Cleaned up various layout issues with launch configuration editor
  • Updates to product and installer to allow better compatibility with newer versions of Ubuntu. Note that our supported Linux platforms remain Ubuntu 16.04 LTS and 18.04 LTS
  • Updates to support new devices, including LPC551x, K32L2A and K32L2B families
  • NXP LPC-LINK2 CMSIS-DAP firmware soft-loaded by IDE updated to v5.361
  • Upgraded to a later version of the P&E Micro plugin (v4.4.1)
  • Upgraded to a later version of the SEGGER J-Link software (v6.54c)

More
2 0 1,466
NXP Employee
NXP Employee

Memory validation extends Peripherals tool with the capability to validate different types of memories. For now, it supports RT10xx CPUs family with SEMC/SDRAM and FlexSPI/NOR (starting with MCUXpresso v11.1.0/Config tools v7) devices. 

The SEMC is a multi-standard memory controller optimized for both high-performance and low pin-count. It can support multiple external memories in the same application with shared address and data pins. The interface supported includes SDRAM.

 

FlexSPI is a flexible SPI (Serial Peripheral Interface) host controller which supports two SPI channels and up to 4 external devices. Each channel supports Single/Dual/Quad/ Octal mode data transfer (1/2/4/8 bidirectional data lines).

 

For developing hardware with SDRAM memory connected to SEMC controller or with NOR memory connected to FlexSPI controller, the validation of memories settings can be done with the new introduced validation tool. The tool is available for SEMC and FLEXSPI peripherals and can be used after selecting the SEMC or FLEXSPI peripheral from the list in the Peripherals view.

Note:

  • This document assumes the use of MCUXpresso IDE v11.0.0 (or later).
  • An MCUXpresso SDK for RT10xx CPUs family will also be required
  • This must be “SDK Version: 2.5.0 (released 2019-02-25)” or later – which can be obtained from https://mcuxpresso.nxp.com
  • Installation of Python 2.7 is required (Install the latest of Python 2.7 version available on  https://www.python.org/downloads). If you see connection errors, make sure arm-none-eabi-gdb-py (can be found in \MCUXpressoIDE_11.1.0\ide\plugins\com.nxp.mcuxpresso.tools.win32\tools\bin\) is starting without error. Also, on Windows it is possible that python27.dll to be required and must be placed in Python27 installation folder. 
  • Once the SDK is imported into MCUXpresso IDE and a project including SEMC or FlexSPI driver is created, the settings can be tuned and validated following the next steps

Example below is for SEMC with SDRAM:

  1. Select the project and open the Peripherals tool pastedImage_13.png
  2. Select the SEMC componentpastedImage_14.png
  3. Configure the SDRAM parameters using the UI
  4. Click on Validation View icon to open SEMC Validation tool viewpastedImage_35.png
  5. From Validation view can be selected validation scenarios and tests. Available tests are DMA,
    Write-Read-Compare, Walking Ones, Walking Zeros. Also Stress test scenario (starting with MCUXpresso v11.1.0/Config tools v7) is available for SDRAM.
    DMA test will transfer data from a source address to a destination address in SDRAM. The size of the data transferred is configurable. The source region is filled with a repeating pattern. After DMA finished the transfer, the test is reading back the data from the destination and compares it with the source data. The test fails at the first mismatch found.
    Write-Read-Compare test checks SDRAM reads versus writes. Sequentially writes into a SDRAM area a pattern, until area is fully covered. Then reads back from the same SDRAM area and compare with what has been written. User can set the start and size of SDRAM area and pattern to be used. The test fails after the first identified memory mismatch.
    Walking Ones test writes a bit pattern that gradually sets [to 1] bits from LSB to MSB. Each byte is written multiple times depending on the selected access size, until each of the contained bits gets set, while the other ones are cleared. For each bit pattern, a write/read/compare sequence is performed. The test is repeated for each of the access size selected using the corresponding access size.
    Walking Zeros test writes a bit pattern that gradually clears [to 0] bits from LSB to MSB. Each byte is written multiple times depending on the selected access size, until each of the contained bits gets set, while the other ones are cleared. For each bit pattern, a write/read/compare sequence is performed. The test is repeated for each of the access size selected using the corresponding access size.
    Stress test is a suite of tests meant to verify the performance and stability of the memory in a non-OS environment.pastedImage_4.png
  6. To set the test parameters and the number of repetitions go to Choose Tests tabpastedImage_8.png
  7. Once the test parameters are set and the scenario is selected, validation can be started by clicking on Start Validation buttonpastedImage_31.png
  8. Status of the test will be displayed in Test Results viewpastedImage_32.png
  9. In Logs view Simple or Real time log can be displayed for each test pastedImage_36.pngpastedImage_37.png
  10. For SDRAM once the validation tests succeeded, there are two options to set the target with the new SDRAM settings
    1. C code generation. Necessary C code for setting the SDRAM is generated in peripherals.c/.h files and will be deployed into the project by pressing Update Code button. Also, a preview of the code is available in Code Preview tabpastedImage_39.png
    2. Create a DCD C array or binary with the SDRAM settings by using the Apply to DCD option.
      First is necessary that the SEMC component mode to the switched to DCD. This way only DCD component will be updated with the SEMC settings and not the peripherals.c/.h files.pastedImage_40.png 
      1. After pressing Apply to DCD button, open DCD tool to view the SDRAM initialization pastedImage_16.png
      2. SDRAM configuration generated into DCD is supposed to be used to update the existing configuration. We are not expected the board to boot with this configuration alone.
  11. Once the validation process is done and the SDRAM settings were applied using one of the above options, project can be rebuilt with the validated SDRAM settings

More
1 0 427
NXP Employee
NXP Employee

MCUXpresso IDE is currently supported on macOS 10.12 to 10.14.

In macOS 10.15 (Catalina), Apple have introduced a new additional "signing" mechanism for software that is download outside of the Apple App Store, know as "Notarization". Currently MCUXpresso IDE for macOS is signed using NXP's Apple Developer ID, but has not yet gone through Apple's notarization process. This means that by default you will not be able to install if you are running macOS 10.15.

Therefore we currently do not claim to officially support MCUXpresso IDE on macOS 10.15. We expect to make a version of MCUXpresso IDE that has been notarized during 2q2020. However in the meantime, you may be still be able to install and use current IDE releases using the following instructions.

When you first try to install MCUXpresso IDE on macOS 10.15, you will see a error dialog :pastedImage_3.jpg

which is because the IDE installer is not notarized. Now open up "System Preferences" and select the "Security and Privacy" option:

pastedImage_4.jpg

and select the "Open Anyway" option for the MCUXpresso IDE installation pkg file.

If you now try to run the installer again, you will again receive a dialog warning that it is not notarized, but this time you can now select the "Open" option:
pastedImage_5.jpg
The IDE installer will now be run and install the tools, in the same way as on earlier versions of macOS.


For more information...

More
0 0 508
Labels