Teensy 4.1

This board (including integrated USB loader, but not debugger, and available for around $27) is based on the MIMXRT1062DVL6A, which is the consumer version [0..95°C] of the 600MHz Cortex-M7 base part with double-precision VFPv5 FPU in MAPBGA196. It has 1M of internal RAM, dual-10/100M Ethernet, Dual-high speed USB (with integrated PHY), 8 low power UARTs, 4 I2C controllers, 3 synchronous audio interfaces, 2 SD card interfaces, 2 CAN interfaces, 2 FlexSPI interface (connected to 8MByte QSPI flash), 2 ADC, LCD and touch controller, a True Random Number Generator, plus various other features.

The processor's budget price for 10'000 pieces is $3.48 (low quantity distributor price for 100 pieces under $9), potentially making it very attractive for low cost products requiring connectivity, HDI, high processing performance and audio.

A 24MHz crystal on the board allows for accurate generation of up to 600MHz processor, 100MHz Ethernet and 480MHz USB clocks.

The µTasker target for the Teensy 4.1 allows immediate use of the board for various functions with simple control of performance/consumption as well as the ability to switch operation between this and other i.MX board/processors and Kinetis parts. Accurate simulation of the device in VisualStudio combined with integrated µTasker application functionality ensures reliable, low footprint product development solutions with minimum effort, risk and investment.

The Teensy 4.1 adds Ethernet (requires an external Ethernet socket,for about $4, an SD card socket and options for extended QSPI flash to the smaller Teensy 4.0



Teensy 4.1 Binaries

Here are some binary files that can be loaded to the Teensy 4.1. These were built using the µTasker applications (serial loader and V1.4 application) and can be simply generated using the supported compilers/IDEs [these were built using GCC], built using different configuration options, or modified to suit specific requirements or hardware derived from this board :
  • uTaskerV1.4_TEENSY_4_1_Ethernet.hex [605k iHEX]

    Complete image containing the µTasker secure loader for the Teensy 4.1 and a reference application supporting Ethernet (requires the Ethernet Kit to use the Ethernet but still runs without it). Its command line interface can be accessed via USB-CDC (virual COM) or via Telnet on IPv4 address 192.168.1.3 (IP configuration can be configured via the command line interface), or on LPUART3 (115200Baud on pins 16/A2 and 17/A3).

    The Ethernet interface allows pinging the board or pinging other devices on the network from the board, IGMP, FTP, Telnet, HTTP - load a set of web pages via FTP to QSPI flash where they will be served from (see below).

    Supports OTA firmware uploading via Ethernet and USB-MSD serial loading - to enter the serial loader command "boot" in the Administrator menu on the command line interface, or command "fboot" in the same menu to move to the "Fall-back loader, which allows loading a new serial loader version.

    The application and serial loaders are AES256 encrypted and run at full 600MHz with zero waits-states in internal closely coupled RAM.

    The serial loader supports loading either encrypted or plain code applications to operate either in internal RAM or QSPI (XiP), whereby on-the-fly decryption is performed automatically if needed.

    The complete image (hex file) can be loaded to the Teensy 4.1 using the Teensy Loader.

    For more details of the µTasker loader concept, and preparing an application to work with it, see the documents and videos at the i.MX RT Developer's page

    A set of web pages can be loaded to the board by using the bat file found in the web page package, or with your favorite FTP client. These show dynamically generated content and allow setting parameters and controlling GPIOs etc., as well as posting new images to the web server.
    The default IP address of the board is 192.168.0.3 - its IP configuration can be changed and saved in the "LAN" menu on the command line interface.

    These binary files and web pages are suitable for use with the i.MX RT tutorial.

  • uTaskerV1.4_TEENSY_4_1_AES256_Ethernet.bin [87.1k]

    This is the AES256 encrypted application that is integrated in the complete image, which can be loaded again using the serial loader.

  • uTaskerV1.4_TEENSY_4_1_AES256_Ethernet_MAC.bin [91.9k]

    This is a newer AES256 encrypted application with about the same features as in the original complete image but which takes the Ethernet interface's MAC address from the eFUSEs and thus doesn't need the MAC address configured as a parameter. The manufacturer of the Teensy 4.1 supplies the chip with a dedicated MAC address pre-programmed from their OUI block 04-e9-e5-xx-xx-xx. Use the LAN menu command "show_config" to see the value programmed in the chip on your board.

  • uTaskerSerialLoaderUpload_TEENSY_4_1.bin [29.9k]

    This is the AES256 encrypted serial loader that is integrated in the complete image, which can be loaded again using the fall-back serial loader.

    Note that this is a demonstration version which uses a fixed AES256 key and doesn't program any eFUSEs - it limits operation of uploaded code running in XiP - plain code or on-the-fly decrypted - to 128k and limits code running in internal RAM to 96k. µTasker project users can build the code without limitations and with automated production eFUSE and productive key programming to simply ensure full clone and IP protection of a product.


    • Teensy 4.1 Loader supporting USB-MSD, Web server and FTP server loading

    uTaskerSerialLoader_TEENSY_4_1_WebServer_FTPServer.hex [314k iHEX]

    This serial loader version requires the Ethernet Kit in order to use web server and FTP loading, and also supports USB-MSD loading if the kit is not connected. When the serial loader runs the board can be pinged on the address 192.168.1.125 and connected to via Web Browser or FTP client as described in the appropriate chapters of µTasker Serial Loader - the applications above can be loaded. [note that the application needs to be saved as "z.bin" when loading via FTP]

    Note that this is a demonstration version which uses a fixed AES256 key and doesn't program any eFUSEs - it limits operation of uploaded code running in XiP - plain code or on-the-fly decrypted - to 128k and limits code running in internal RAM to 96k. µTasker project users can build the code without limitations and with automated production eFUSE and productive key programming to simply ensure full clone and IP protection of a product.


    Teensy 4.1 Loader supporting USB-MSD, Web server and FTP server loading - with RNDIS application

    uTaskerCompleteImage_TEENSY_4_1_WebServer_FTP_RNDIS_App.hex [636k iHEX]

    This complete image - containing primary loader, fall-back loader, serial loader and application - shows the same Web and FTP loader capability as the previous reference but doesn't require an application to be loaded seperately. Other applications can subsequently be loaded from the serial loader mode, which can be commanded via the command line interface in the "administrator" menu using "boot".

    The application adds RNDIS device support [see the RNDIS Device User's Guide, especially if the RNDIS driver needs installation help] so that the Teensy 4.1 appears as a remote network adapter to the host PC on its own network. The PC host's adapter network is supplied automatically with an IP configuration via DHCP and can then access the same services such as Telnet, FTP and Web server on this network. The network configuration of the Teensy used by its Ethernet connection (when present) is shown using the "show_config" command in the "Network" menu. "net 1" switches the menu to the RNDIS network configuration and "show_config" then displays its setup.

    uTaskerV1.4_AES256_TEENSY_4_1_Eth_RNDIS.bin [98k] is the AES256 encrypted application that can be loaded via the serial loader method, as well as on the "Administrator" web page when the reference web pages have been loaded. Both the web server and FTP operate on both Ethernet and RNDIS.


    Note that this is a demonstration version which uses a fixed AES256 key and doesn't program any eFUSEs - it limits operation of uploaded code running in XiP - plain code or on-the-fly decrypted - to 128k and limits code running in internal RAM to 110k. µTasker project users can build the code without limitations and with automated production eFUSE and productive key programming to simply ensure full clone and IP protection of a product.






Return to the i.MX RT landing page


µTasker Teensy 4.1 support. Copyright (c) 2004..2021 M.J.Butcher Consulting