Daruma is a design pattern for multi-channel redundant automated driving systems. The video demonstration of the Daruma’s proof of concept shows improvements of automated vehicle’s safety and availability in the CARLA simulator.

Whether you are participating at the NXP Cup competition or simply passionate about self-driving cars, try using MBDT to program a microcontroller to drive your car on a track. In this article you will find a model you can use as a starting point for your application.

This document shows how to debug i.MX8MP uboot with TRACE32 debugger.
For Linux debug, please check https://community.nxp.com/t5/Blogs/Debug-i-MX8MP-Linux-with-TRACE32/ba-p/1582382

1. Build uboot

Follow IMX_LINUX_USERS_GUIDE.pdf to build uboot and generate flash.bin.
We will boot i.MX8MP from eMMC/SD, attach TRACE32 and load uboot symbol.
The uboot image and symbol should come from the same build.

2. Run uboot and get relocate offset

Program flash.bin to eMMC or SD card, boot uboot and "Hit any key to stop autoboot". Run command bdinfo to get uboot reloc off value.

3. TRACE32 script

Attached imx8mp-uboot-attach.cmm is TRACE32 script. You need to modify Data.LOAD.Elf and SYMbol.reloc according to your environment.

3.1 Data.LOAD.Elf

The full command in this example is

Data.LOAD.Elf C:\Debugging\Linux\Sources\uboot-imx\u-boot /NoCODE /STRIPPART "uboot-imx" /SOURCEPATH C:\Debugging\Linux\Sources\uboot-imx

The first parameter C:\Debugging\Linux\Sources\uboot-imx\u-boot tells debugger where to download ELF file. Please note you should not use u-boot.bin.

/NoCODE: The option /NOCODE should be used to only load the symbols without uboot code.

/STRIPPART: With the option /STRIPPART you can remove parts of the path stored in the object file.

/SOURCEPATH: With the option /SourcePATH you can specify a basis directory for the source files.
For example, if you have compiled your uboot on a Linux machine in the directory /home/user/linux/uboot-imx, and you are running TRACE32 on a Windows machine where you have the uboot source files tree under C:\Debugging\Linux\Sources\uboot-imx, set /STRIPPART to “uboot-imx”, and set /SOURCEPATH to C:\Debugging\Linux\Sources.

With above setting, to look for the source file board/freescale/imx8mp_evk/imx8mp_evk.c, the debugger will here use the path
C:\Debugging\Linux\Sources\uboot-imx + /home/user/linux/uboot-imx/board/freescale/imx8mp_evk/imx8mp_evk.c
thus
C:\Debugging\Linux\Sources\uboot-imx/board/freescale/imx8mp_evk/imx8mp_evk.c

3.2 relocate offset

We have got relocate offset in step 2, replace the value in SYMbol.reloc command.

4. Attach i.MX8MP board to TRACE32 debugger

Connect TRACE32 to JTAG port, open TRACE32 ICE Arm USB, then from “File->Run Script...”, run imx8mp-uboot-attach.cmm, you will see below window, TRACE32 is attached to i.MX8MP uboot.

If you want to debug some function, such as boot_jump_linux, you can set break point with command
break.set boot_jump_linux
Then press Go button in TRACE32 PowerView, and run boot command in uboot, uboot will continue to run and stop at boot_jump_linux, as shown in below figure.

This article shows how to attachTRACE32 to i.MX8MP Linux and how to debug Linux module and app.

When running firmware v3.xxx onwards, MCU-Link uses WinUSB, so make sure your firmware matches a compatible MCUXpresso IDE version.

With the introduction of the new GreenBox 3 real-time development platform, NXP offers a game-changing platform that promotes ECU consolidation for enabling the future of automotive electrification. In this post, we will explore a consolidated ECU demo created around the GreenBox 3 and explain what advantages the GreenBox 3 offers for each of these use cases and why you may want to consider an ECU consolidated design.

Introduction

We already have application note AN13336 about running TFLM micro_speech example on Tensilica HiFi4 DSP on i.MX 8M Plus EVK.
In this document, TFLM micro_speech example will be upgraded to support i.MX DSP remote processors driver in newer Linux kernel, patch to support i.MX8QXP/i.MX8QM MEK will be provided, steps about how to download and install toolchain, how to build and run the example will be listed.

Hardware: i.MX8MP EVK, i.MX8QXP MEK, i.MX8QM MEK.
Software: Linux 5.15.52, TensorFlow Lite Micro

Running TFLM micro_speech demo on i.MX8MP EVK

1 Download Xtensa toolchain

1.1 Download license key  

Login https://tensilicatools.com/download/i-mx-8-hifi-4-sdk/, download GETTING STARTED GUIDE, then follow the GUIDE to get a license key for i.MX8MP SDK.

1.2 Download CONFIGURATION file for Linux

There are two configuration packages:
    DSP_configuration_for_Linux_(NEWLIB)_i.MX8MP_RI_2020_4.zip
    hifi4_mscale_mpxclib_prod_linux.tgz
The target binary built with xclib is smaller than the one built with newlib.
In this example, we will use NEWLIB package DSP_configuration_for_Linux_(NEWLIB)_i.MX8MP_RI_2020_4.zip

1.3 Follow the GETTING STARTED GUIDE to download and install XTENSA XPLORER IDE FOR LINUX V8.0.13

After installed, Xtensa tool package can be found at installation folder:
    xtensa/XtDevTools/downloads/RI-2020.4/tools/XtensaTools_RI_2020_4_linux.tgz

2. Install Xtensa development toolchain on Linux OS

2.1 Create imx-audio-toolchain folder

    mkdir -p ./imx-audio-toolchain/Xtensa_Tool/tools
    mkdir -p ./imx-audio-toolchain/Xtensa_Tool/builds

2.2 Set up the configuration-independent Xtensa Tool

    cd imx-audio-toolchain/Xtensa_Tool
    tar zxf XtensaTools_RI_2020_4_linux.tgz -C tools/

2.3 Set up the configuration-specific core files and the Xtensa Tool

Unzip DSP_configuration_for_Linux_(NEWLIB)_i.MX8MP_RI_2020_4.zip, you will get hifi4_mscale_v1_0_2_prod_linux.tgz
    cd imx-audio-toolchain/Xtensa_Tool/
    tar zxf hifi4_mscale_v1_0_2_prod_linux.tgz -C builds/

2.4 Install the Xtensa development toolchain

    cd imx-audio-toolchain/Xtensa_Tool
    ./builds/RI-2020.4-linux/hifi4_mscale_v1_0_2_prod/install --xtensa-tools ./tools/RI-2020.4-linux/XtensaTools --registry ./tools/RI-2020.4-linux/XtensaTools/config

2.5 Set the LM_LICENSE_FILE environment variable

Create ~/.flexlmrc, in the file, set LM_LICENSE_FILE environment variable to the absolute path of your license key folder.
    LM_LICENSE_FILE=<absolute path of your license key folder>

2.6 In imx-audio-toolchain, create environment variables script setup_env.sh for building

#!/bin/bash
export TOOLCHAIN_FOLDER=RI-2020.4-linux
export TOOLCHAIN_PATH=$PWD
export PATH=$TOOLCHAIN_PATH/Xtensa_Tool/tools/$TOOLCHAIN_FOLDER/XtensaTools/bin:$PATH
export XTENSA_CORE=hifi4_mscale_v1_0_2_prod
export XTENSA_BASE=$PWD/Xtensa_Tool/
export XTENSA_TOOLS_VERSION=RI-2020.4-linux
export XTENSA_SYSTEM=$PWD/Xtensa_Tool/tools/RI-2020.4-linux/XtensaTools/config
export PLATF=imx8m

3. Build TFLM micor speech for HiFi4

3.1 Clone the specific TensorFlow repository and check out the proper branch

    git clone https://github.com/pnikam-cad/tensorflow.git
    cd tensorflow
    git checkout hifi5_hifi4_nnlib_new_versions

3.2 Apply patch

    0001-i.MX-8M-Plus-HiFi4-TFLM-Enablement-changes-required-.patch
    0002-resolve-download-error-and-upgrade-toolchain-to-2022.patch
    0003-upgrade-to-support-remoteproc-in-linux-5.10.72.patch

3.3 Compile Micro Speech example

In imx-audio-toolchain, run setup script setup_env.sh
In tensorflow folder, build micro_speech_mock demo with command
    make -f tensorflow/lite/micro/tools/make/Makefile TARGET=xtensa_hifi TARGET_ARCH=hifi4 XTENSA_USE_LIBC=true micro_speech_mock
The compiled binary is tensorflow/lite/micro/tools/make/gen/xtensa_hifi_hifi4/bin/micro_speech_mock

3.4 Run Micro Speech example

Boot i.MX8MP with imx8mp-evk-dsp.dtb, copy micro_speech_mock to /lib/firmware/imx/dsp/, rename it to hifi4.bin, then load and run the example with command
    echo start >/sys/class/remoteproc/remoteproc0/state 
    On UART4 output(the fourth terminal in J23 DEBUG port), you can get such log

3.5 Sample data

If you want to use new sample data, please refer to AN13336 about how to generate and convert.

Running TFLM micro_speech example on i.MX8QXP MEK

4 Download Xtensa toolchain

4.1 Download license key

Login https://tensilicatools.com/download/i-mx8-quadxplus-hifi-4-sdk/, download GETTING STARTED GUIDE, then follow the GUIDE to get a license key for i.MX8QXP SDK.

4.2 Download CONFIGURATION file for Linux

There are two configuration packages:
        hifi4_nxp_v4_3_1_prod_linux.tgz
        hifi4_nxp_v4_3_1_prod_XC_linux_redist.tgz
In this example, we will use XCLIB package: hifi4_nxp_v4_3_1_prod_XC_linux_redist.tgz

4.3 Follow the GETTING STARTED GUIDE to download and install XTENSA XPLORER IDE FOR LINUX V8.0.13

After installed, Xtensa tool package can be found at installation folder:
    xtensa/XtDevTools/downloads/RI-2020.4/tools/XtensaTools_RI_2020_4_linux.tgz

5. Install Xtensa development toolchain on Linux OS

5.1 Create imx-audio-toolchain folder

    mkdir -p ./imx-audio-toolchain/Xtensa_Tool/tools
    mkdir -p ./imx-audio-toolchain/Xtensa_Tool/builds

5.2 Set up the configuration-independent Xtensa Tool 

    cd imx-audio-toolchain/Xtensa_Tool
    tar zxf XtensaTools_RI_2020_4_linux.tgz -C tools/

5.3 Set up the configuration-specific core files and the Xtensa Tool

    cd imx-audio-toolchain/Xtensa_Tool/
    tar zxf hifi4_nxp_v4_3_1_prod_XC_linux_redist.tgz -C builds/

5.4 Install the Xtensa development toolchain

    cd imx-audio-toolchain/Xtensa_Tool
    ./builds/RI-2020.4-linux/hifi4_nxp_v4_3_1_prod_XC/install --xtensa-tools ./tools/RI-2020.4-linux/XtensaTools --registry ./tools/RI-2020.4-linux/XtensaTools/config

5.5 Set the LM_LICENSE_FILE environment variable

Create ~/.flexlmrc, in the file, set LM_LICENSE_FILE environment variable to the absolute path of your license key folder.
    LM_LICENSE_FILE=<absolute path of your license key folder>

5.6 In imx-audio-toolchain, create environment variables script setup_env.sh for building

#!/bin/bash
export TOOLCHAIN_FOLDER=RI-2020.4-linux
export TOOLCHAIN_PATH=$PWD
export PATH=$TOOLCHAIN_PATH/Xtensa_Tool/tools/$TOOLCHAIN_FOLDER/XtensaTools/bin:$PATH
export XTENSA_CORE=hifi4_nxp_v4_3_1_prod_XC
export XTENSA_BASE=$PWD/Xtensa_Tool/
export XTENSA_TOOLS_VERSION=RI-2020.4-linux
export XTENSA_SYSTEM=$PWD/Xtensa_Tool/tools/RI-2020.4-linux/XtensaTools/config
export PLATF=imx8

6. Build TFLM micor speech for HiFi4

6.1 Clone the specific TensorFlow repository and check out the proper branch

    git clone https://github.com/pnikam-cad/tensorflow.git
    cd tensorflow
    git checkout hifi5_hifi4_nnlib_new_versions

6.2 Apply patch

    0001-i.MX-8M-Plus-HiFi4-TFLM-Enablement-changes-required-.patch
    0002-resolve-download-error-and-upgrade-toolchain-to-2022.patch
    0003-upgrade-to-support-remoteproc-in-linux-5.10.72.patch

6.3 Compile Micro Speech example

In imx-audio-toolchain, run setup script setup_env.sh
In tensorflow folder, build micro_speech_mock demo with command
    make -f tensorflow/lite/micro/tools/make/Makefile TARGET=xtensa_hifi TARGET_ARCH=hifi4 micro_speech_mock
The compiled binary is tensorflow/lite/micro/tools/make/gen/xtensa_hifi_hifi4/bin/micro_speech_mock

6.4 Apply Linux Kernel patch to enable UART2 for HiFi4

    0001-linux-enable-uart2-for-8qxp-hifi4.patch

6.5 Run Micro Speech example

Boot i.MX8QXP MEK board, copy micro_speech_mock to /lib/firmware/imx/dsp/, rename it to hifi4.bin, then load and run the example with command
    echo start >/sys/class/remoteproc/remoteproc1/state 
On base board RS232 port J37, you can get such log

Running TFLM micro_speech example on i.MX8QM MEK

7. Install toolchain and Build TFLM micor speech for HiFi4

Follow above step 4 ~ step 6.3 to download and setup toolchain, apply TFLM patch and compile Micro Speech example.

8. Linux kernel patch and image

In above i.MX8QXP example, micro speech example print log through UART2.

In i.MX8QM MEK Linux demo image imx-image-full-imx8qmmek.wic, M4 is enabled and UART2 is occupied by M4.

To resolve this conflict, we will not enable M4. The steps to run Linux image without M4 are shown below.

1. Apply patch 0001-linux-enable-uart2-for-8qm-hifi4.patch to enable UART2 for HiFi4
2. Build Linux dtb, we will boot i.MX8QM MEK board with imx8qm-mek.dtb.
3. Assume you boot 8QM from SD card, program uboot image without M4 to SD card
    sudo dd if=imx-boot-imx8qmmek-sd.bin-flash of=/dev/sdX

9. Run Micro Speech example

Boot i.MX8QM MEK board with your new imx8qm-mek.dtb, copy micro_speech_mock to /lib/firmware/imx/dsp/, rename it to hifi4.bin, then load and run the example with command
    echo start >/sys/class/remoteproc/remoteproc2/state 
On base board RS232 port J37, you can get such log

10. Troubleshooting

10.1 No remoteproc device in /sys/class/remoteproc/

Run lsmod, check if imx_dsp_rproc module is loaded. If not, rebuild Linux kernel and modular and update to your board.

10.2 No output on HiFi4 UART

• In 8MP, check if you bootup the board with imx8mp-evk-dsp.dtb
• There may be several remoteproc devices in /sys/class/remoteproc, check which one is imx-dsp-rproc by below command, then "echo start" to that device.
      cat /sys/class/remoteproc/remoteproc1/name 

10.3 In 8QXP MEK, Get "remoteproc remoteproc1: can't start rproc imx-dsp-rproc: -110" error when run the "echo start" command

Check if you have applied Linux patch to enable UART2 for HiFi4, and bootup your board with the dtb file.

11 Reference

https://www.nxp.com/webapp/Download?colCode=AN13336

XPLOR8QM8QP-UG_Rev0.pdf in https://tensilicatools.com/download/i-mx8-quadxplus-hifi-4-sdk/

step by step: load fusion fw to 8ulp flash

In this article, I'd like to share the steps to run fusion dsp fw in 8ulp, including all the issues I have encountered.

Pre-steps

To follow the steps, you will need:

• An 8ULP A1 EVK board
• 8ULP L5.15.52 image https://www.nxp.com/webapp/Download?colCode=L5.15.52_2.1.0_MX8ULP-BETA4&appType=license
• uboot and imx-mkimage
• SDK_2_12_1_EVK-MIMX8ULP_PRC4 - https://mcuxpresso.nxp.com/download/3b8a2df3ddcfce9bbe402722d28c85d9
• IAR IDE 9.30.1 - https://www.iar.com/
• Jlink V7.50 - https://www.segger.com/downloads/jlink/
• Access to Tensilica Tools - https://tensilicatools.com/download/i-mx-8ulp-fusion-dsp-sdk

You'll need to register to this site.

• GETTING STARTED GUIDE FOR I.MX 8ULP: very useful, I mainly refer to this document. I suggest to read this article throughout to get a whole picture before getting started.
• XTENSA XPLORER IDE FOR WINDOWS V8.0.15
• DSP CONFIGURATION FOR WINDOWS(NEWLIB) V8.0.15
• DSP CONFIGURATION FOR WINDOWS(XCLIB) V8.0.15

Notes:

1. About the IAR IDE
1. For internal use, you can download it from internal server. http://10.193.108.11/_IDEs/IAR/9.30.1 (user: ubuntu11, pwd: Test@2021)
2. Click EWARM-9301-50054.exe to install
3. Update license serve. In help -> License Manager

1. In add a server -> add, copy wsv11103.swis.cn-sha01.nxp.com into it

1. About the 8ULP patch for IAR

iar_segger_support_patch_imx8ulp.zip https://www.nxp.com/security/login?TARGET=https%3A%2F%2Fwww.nxp.com%2Fwebapp%2Fsecure%2Flogin.SAMLSe...

Follow the readme in download zip.

1. About the Jlink version

The version after V7.50 will not support 8ULP.

One problem is the integrated Jlink in IAR is V7.66, so we need to downgrade it to V7.50.

In Jlink installed path, SEGGER\JLink\JLinkDLLUpdater.exe. After running the exe, Jlink in IAR will be changed to V7.50.

Steps:

1. Compile the m33 bin file.

You can either compile with ARMGCC or with IAR.

With ARMGCC, just use the script build_flash_debug.sh.

With IAR, something to pay attention to:

1. Select the device as NXP MIMX8UD7_M33

1. The DSP_IMAGE_COPY_TO_RAM in Defined symbols.

If set to 1, DSP application will launch from Arm core; if set to 0, it will not launch from Arm core, and can be loaded from Xtensa Xplorer.

You can also find explanation in GETTING STARTED GUIDE FOR I.MX 8ULP.

1. Build flash.bin

I assume you to be familiar with this step. If not, you need to read section "4.5.13 How to build imx-boot image by using imx-mkimage" in IMX_LINUX_USERS_GUIDE.

But still I'd like to take some notes here, as building 8ULP uboot has some tricks.

To build 8ULP uboot, we need extra images like mx8ulpa1-ahab-container.img and upower.bin, they can be downloaded from internally:

http://shlinux22.ap.freescale.net/internal-only/Linux_IMX_5.15.52_2.1.0/L5.15.52-2.1.0-rc2(36)/commo...

Also, the DSP examples only supports flash target in dual boot mode, which means we need to flash m33 into nor flash. Here are the steps to achieve this.

1. A uuu script to flash dualboot image uuu_8ulp_dual.auto, can be found in http://shlinux22.ap.freescale.net/internal-only/Linux_IMX_5.15.52_2.1.0/latest/common_bsp/imx_mfgtoo...

In this script, it needs three different flash.bins: _flash_singleboot_m33.bin, _flash_dualboot_m33.bin, _flash_dualboot.bin.

They need to be built with the following commands respectively:

1. You will also need a _rootfs.sdcard, which corresponds to the  imx-image-multimedia-imx8ulpevk.wic image.
2. Then you need to switch board to serial download mode, and can use the command uuu.exe uuu_8ulp_dual.auto to flash all image. This only needs to be done once.

1. Load the m33 bin file to nor flash

In the above step, there is already m33 bin in nor flash. This step explains how to load m33 bin alone when you only have change in m33.

1. Switch board to serial download mode
2. use Jlink commander V7.50 to connect to it.
3. Then use the command to load bin file: loadbin _flash_dualboot_m33.bin 0x4000000

1. System bootup

Switch the 8ULP dip to 1000_0010 A35-eMMC/ M33-Nor

If you set DSP_IMAGE_COPY_TO_RAM=1 in step #1, during boot up, you will see both prints in M33 and in DSP.

Otherwise you will only see prints in M33.

1. Debug the fusion DSP.

The steps are very detailed in "chapter 4 Run and debug DSP demo using Xplorer IDE".

One note to take here:

Windows platform, there is bug in Xtensa Xplorer license manager. You need to clear the existing license path if you want to change license. Otherwise the license may not correctly as expected.

Clean existing license by searching key `XTENSAD_LICENSE_FILE` in windows registry.

In my case, I had an 8MP license installed before, so when I try to debug the 8ULP, I keep to have the following error:

I need to clear previous license and install the one for 8ULP.

The race is on

The automotive industry is being revolutionized by innovations in efficient energy management, new vehicle architectures and software-defined vehicles (SDVs).  Automakers are racing to develop new solutions, taking advantage of these paradigm shifts in the market to establish themselves as innovators and to secure competitive positioning for their products.   

Market adoption of electrified vehicles is ramping quickly, propelled by government legislation for improved efficiency and reduced carbon emissions.  Vehicle networks have become increasingly complex, and manufacturers are recognizing significant opportunities to reduce cost, vehicle weight and development cycle times by moving to domain and zonal architectures that consolidate functions into fewer electronic control units with increased processing power.  Software-defined vehicles, which take full advantage of these new vehicle architectures, will provide life-long upgrade possibilities, resulting in vehicles that improve in performance over their lifetime and enable new revenue streams for vehicle manufacturers. 

The RT685-AUD-EVK allowed me to validate my custom frontend circuitry and get started on other critical DSP software development.  I was able to connect the piezoelectric saddle pickups on my engineering guitar into the test bed via the custom daughtercard. From here I can focus on firmware in the MCU and DSP cores in the RT685. 

Please find document which is missing in the latest SDK bundle location for RT devices \docs\wireless\Release Notes.

The new S32Z and S32E automotive real-time processor families supercharge real-time vehicle compute and control applications. This article highlights how the complementary S32G vehicle network processor for service-oriented gateways, combined with the S32Z and S32E real-time processor can enable new automotive applications. Combining real-time compute with secure cloud connectivity supports advanced sensing, processing and control applications that can adapt with the life of your vehicle.

Vehicle electrical architectures are going through a transformation to achieve the consumers demand for driver assistance, electrification and service functions.  To support modern software-defined vehicles and reduce the cost of the vehicle network, and the associated wiring harness, it is being transitioned to a domain and zonal architectures (or a combination of them). While this evolution helps address the software and cost challenges, it brings other challenges, such as how to partition safety critical real time control operations, like vehicle propulsion.  

As automotive manufacturers are modernizing their vehicle networks, they are increasingly integrating related functions into a single ECU. Choosing a processor for these new ECUs is a critical task, which NXP makes easier with the new S32Z/E Real-Time Processor families

A beginner-level model example that can be implemented using NXP's Model-Based Design Toolbox. Learn how to design, build and deploy an embedded program that can run on any MCU.

The disruptive technologies of multi-gigabit Automotive Ethernet, IEEE time-sensitive networking (TSN) protocols and automotive cloud-native DevOps are coming together to enable the Software-Defined Vehicle (SDV). NXP is at the leading edge of these technology trends and recently announced the S32Z and S32E real-time processors families. 

This article lays out some of the progress on the disruptive technology front and explains how NXP plays a critical role with the launch of the S32 real-time processors by enabling the integration of vehicle-wide, real-time functions and supporting new vehicle architectures involving central compute, domain control and the zonal edge.  

This launch introduces our Smart Card Trust Provisioning Solution, bringing customers a major new capability in protecting their Software Intellectual Property (IP) and guarding against over-production and cloning.

A singular article is simply not enough to do this component justice, so I wanted to follow up and highlight some other features that make the LPC5536 unique.

The latest release of NXP's free UI design tool for LVGL is out now - GUI Guider 1.3.1 features major improvements in usability and optimization. 

Hooking up to the external world usually means that our MCUs must learn to  “speak” analog.   A high-performance analog system was added to the LPC553x family to enable more integrated, lower external component count designs.

NXP's free UI design tool for the open source LVGL graphics library continues to add great new features and capabilities. GUI Guider 1.3.0 was released on January 24th 2022 and includes exciting new widgets, more host platform support, Keil project output and Micropython.

We are pleased to announce that Config Tools for i.MX Application Processors v11 are now available.

DDR tool supports i.MX8M family and LX2160A. DDR tool is part of Config tools for i.MX offering configuration, inspection, optimization, vTSA, stressing and code generation. It can be downloaded from 

https://www.nxp.com/design/designs/config-tools-for-i-mx-applications-processors:CONFIG-TOOLS-IMX

After setting my new 16” M1Max Macbook Pro, I found some surprising results for the kernel compile time. The Ubuntu Virtual Machine on my M1 MBP compiled the i.MX Linux kernel faster than an Intel i9 3650 Dell Precision workstation running native Ubuntu. Since the comparison is a bit like apple to oranges, I tried to minimize the variables, and, I also compared an older i7 Dell Precision M4700 and a Xeon.

The SuperMonkey is here!  Come see the bring-up of an i.MX RT685 based design that uses QSPI flash connected to FlexSPI Port A.

NXP has now introduced MCU-Link Pro - the second incarnation of the MCU-Link debug probe architecture, adding several powerful capabilities and features to build on the entry level MCU-Link standalone model. This includes power/energy measurement, USB bridging and a J-Link firmware option.