i.MX RT Developer's Page

The µTasker project celebrated its 15th birthday this year and during the course of the years the project has continuously developed. This development, as of mid-February 2020, is nearing completion of NXP i.MX RT support and this is where you can find latest information about this work as well as getting involved with trying out latest pre-release/development code.


ALL main i.MX RT targets are now supported (boot loader concept and application):

Binary files for the serial loader and reference applications with USB, SD card (and Ethernet) can be found on these, which are suitable for following the i.MX RT Tutorial.

Please send an email to the i.MX RT address at the bottom of the start side in case you would like to be involved with evaluating/testing the present state of support.


Watch the µTasker i.MX RT Video Playlist on Youtube!


Provisional Developer's Guides

During the roll-out phase not all IDE documents may be completed and here are some provisional guides that may help out during the transition period. If you have a requirement due to some missing details please request so that the missing details can be quickly made available [Important note - as from 30.4.2020 the boot loader concept has been upgraded and these document respect the newer version].

- MCUXpresso importing and building the reference project (10.09.2020) - and Video Guide

- IAR building and debugging (28.08.2020) - and Video Guide

- GCC building and debugging (28.08.2020) - and Video Guide

- FlexSPI (SPI Flash) configuration

- µTasker Loader Concept Flow Diagram (28.08.2020)

- Guide to taking the µTasker Loader for a test-drive


Topics

Why Would Anyone want to use the µTasker Project?

The natural first reaction is to use NXP's KDS and possibly some of NXP MCUXpresso's code generation tools, and this is probably what the majority of typical developers will also do. However the µTasker project monitors the 'traditional' approach and then works on delivering an alternative solution that offers product developers various IMPORTANT advantages over the typical approach to ensure they have an overall improved tool kit that gives real competitive advantages over their competitors. These include:

  • Low footprint (avoiding the need for external memory, their cost and power consumption)
  • Simple configuration based on optimised, managed and documented solutions rather than on less transparent generated code that may change at each new generation/release
  • Code that is shared by all processors and projects rather than being different for each part used (improved maintenance and proven solid code base)
  • Generic code that allows applications to be developed on one processor and simply moved to others (also between i.MX RT and Kinetis parts) to ensure flexibility and proven code reuse in future projects, even when a different processor proves to be more suitable
  • Silicon manufacturer independent solution to avoid 'lock-in' due to manufacturer dependancy (eg. projects can also be moved between i.MX RT and the popular STM32 family if they prove to have advantages or, of course, in the other direction too)

  • Specific technical advantages include:

  • Complete boot and OTA (over-the-air) concept integrated into the project
  • Run time optimisation of FlexRAM partitioning to achieve most efficient program and data access
  • Ease of achieving optimal speed/power consumption for each application in hand
  • Dual µTasker and FreeRTOS operation configuration option integrated for each i.MX RT target
  • Compatible µTasker serial loader methods (Ethernet, USB, UART, etc.) as known from the Kinetis project
  • Accurate VisualStudio based i.MX RT simulation to dramatically increase development, testing and debugging efficiency
  • Optimised and continuously verified/further developed HW drivers
  • Integrated µTasker middle-ware such as TCP/IP and USB stacks, utFAT, Modbus, etc.

  • And possibly the most important for commercial developments:

  • Full-time, dedicated support in case of problems, need for technical information/support, training or even user defined custom developments

  • Generally it is true to say that, contrary to typical silicon manufacturer's libraries, the µTasker project is not a collection of examples for use as a starting point but is instead an industrialised solution for helping complete product developments.
    The µTasker tames this complicated part so that you can use its power to quickly get your work done instead of losing time fighting with its intricacies!


    i.MX RT 1021 Guide - the µTasker way

    The µTasker strategy is to enable developer's to quickly achieve reliable product development and this document gives developer's a quick and clear description of the important things to understand to use the i.MX RT 1021 efficiently without needing to read all of its 3'000 page user's manual. With a few configuration definitions a custom setup is possible which not only gives efficient code but also ensures lowest power consumption by automatically powering down internal modules that are not used.

    Follow the development of the i.MX RT 1021 document - V0.13 01.9.2020 / i.MX RT 1064 document - V0.00 23.6.2020


    i.MX RT GPIO and Port Multiplexing

    The GPIO concept used in the i.MX RT is a little different to that used by Kinetis and various other such processors. This video discusses it and how the µTasker solution achieves compatibility with Kinetis to make is simple for Kinetis users to move projects to the i.MX RT part.

    See the video "Getting your Head around i.MX RT 1020 GPIO and Port Multiplexing" here: 9.2.2019



    i.MX RT XBAR and AOI

    The XBAR allows pins and peripheral module outputs to be multiplexed to other pins or peripheral inputs. With the AOI (AND-OR-Invert) module complicated logical connections are also possible. This video discusses the modules and shows how it is used to achieved a DMA pin triggering interface that is highly compatible with Kinetis DMA pin triggering.

    See the video "i.MX RT XBAR and AOI (On-Chip Cross Trigger Network)" here: 2.9.2020



    Development Code Archive

    The i.MX RT project is integrated in the Kinetis project in order to allow product development code to be easily moved between Kinetis and i.MX RT parts. Since the i.MX RT parts share a number of peripherals from Kinetis parts the project code shares the peripheral drivers where possible in order to benefit from proven Kinetis code operation and also to simplify maintenance - for example if a new feature is added, or an improvement made to such a Kinetis peripheral it is immediately inherited by the i.MX RT project.

    Presently it is available to registered commerical users but not yet as open source.






    Return to the i.MX RT landing page



    µTasker Kinetis Development. Copyright (c) 2004..2020 M.J.Butcher Consulting