Hands-on training utilizing NVIDIA's TAO toolkit and FRDM-IMX93

Customer may want to deploy Android 14 on FRDM-iMX8MP. This doc gives an introduction about how to deploy Android OS14 on FRDM-iMX8MP   Hardware: FRDM-iMX8MP, Power supply cable, usb cable x2,  Ubuntu PC Outline: Follow the below steps: Setup the Android 14 source environment based on LF6.6.36. Apply FRDM-iMX8MP patches in kernel, uboot, mkimage, and device directory. Build the image for FRDM-iMX8MP Flash the image   1. Setup the environment On the Linux PC, set up the Android Source environment according to Section 2- Section 3 from the Android User’s Guide Rev. android-14.0.0_2.1.0 and do not build the image yet. $ cd ~ (or any other directory you like) $ tar xzvf imx-android-14.0.0_2.1.0.tar.gz To generate the i.MX Android release source code build environment, execute the following commands: $ source ~/imx-android-14.0.0_2.1.0/imx_android_setup.sh Prepare the build environment for U-Boot and Linux kernel. This step is mandatory because there is no GCC cross-compile tool chain in the one in AOSP codebase. An approach is provided to use the self-installed GCC cross-compile tool chain for both AArch32 and AArch64. Change to the top-level build directory and set up the environment for building. This only configures the current terminal $ cd ${MY_ANDROID} $ source build/envsetup.sh 2. Apply FRDM-iMX8MP patches into AOSP   Apply the patch in device/nxp, copy all the patches into android_build/device/nxp, and then running the command: $ git apply --check 0001-device-nxp-add-FRDM-i.MX8MP-Android14-basic-support.patch $ git apply 0001-device-nxp-add-FRDM-i.MX8MP-Android14-basic-support.patch Apply the patches in uboot, copy all the patches into android_build/vendor/nxp-opensource/uboot-imx, and then running the command: $ git am *.patch Apply the patches in kernel, copy all the patches into android_build/vendor/nxp-opensource/kernel-imx, and then running the command: $ git am *.patch Apply the patch in mkimage, copy all the patches into android_build/vendor/nxp-opensource/ imx-mkimage, and then running the command: $ git am *.patch     3. Build the image for FRDM-iMX8MP Execute the Android lunch command: $ lunch frdm_8mp-trunk_staging-userdebug Execute the imx-make.sh script to generate the image. $ ./imx-make.sh -j4 2>&1 | tee build-log.txt NOTE: The following outputs are generated by default in ${MY_ANDROID}/out/target/product/frdm_8mp:   4. Flash the image The board image files can be flashed into the target board using Universal Update Utility (UUU). For the UUU binary file, download it from GitHub: uuu release page on GitHub.  To achieve more flexibility, two script files are provided to invoke UUU to automatically flash all Android images. uuu_imx_android_flash.sh for Linux OS uuu_imx_android_flash.bat for Windows OS For this release, these two scripts are validated on UUU 1.5.179 version. Download the corresponding version from GitHub: For Linux OS, download the file named uuu. For Windows OS, download the file named uuu.exe. Perform the following steps to download the board images: Download the UUU binary file from GitHub as described before. Install UUU into a directory contained by the system environment variable of "PATH". Make the board enter serial download mode. Change the board's SW5 (boot mode) to 0001 (from 1-4 bit) to enter serial download mode. Power on the board. Use the USB cable to connect the USB 3.0 dual-role port (with silkprint "PORT1") on the board to your host PC. On the Linux system, open the shell terminal. For example, you can execute a command as follows: $ sudo ./uuu_imx_android_flash.sh -f imx8mp -p frdm -a -e On the Windows system, open the command-line interface in administrator mode. The corresponding command is as follows: $ uuu_imx_android_flash.bat -f imx8mp -p frdm -a -e NOTE: If you want to change the dtb, you can add -d dtb_feature. Also, you can check all the info by using the command: uuu_imx_android_flash.bat Power off the board and Change the board's SW5 (boot mode) to 0010 (from 1-4 bit) to enter emmc boot mode

Customer may want to debug FRDM-IMX93 with the SWD interface of Jtag. This doc give an introduction about how to do that. Hardware: FRDM-IMX93,J-link. 1.Rework FRDM-IMX93 board and get the VREF(1.8V) from TP707 for SWD, show as the following picture.     2. Remove the  R3017 and R3018 in the following picture.     3.Connect FRDM-IMX93 and PC through J-link as the following pictures.     4.Switch the sw1 to 1001 to the serial download of the M33, then run the J-link commander.   The command is as following: J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect   The full log is as following: SEGGER J-Link Commander V8.10 (Compiled Sep 26 2024 08:38:41) DLL version V8.10, compiled Sep 26 2024 08:37:48 Connecting to J-Link via USB...O.K. Firmware: J-Link V10 compiled Jan 30 2023 11:28:07 Hardware version: V10.10 J-Link uptime (since boot): N/A (Not supported by this model) S/N: 600109556 License(s): RDI, FlashBP, FlashDL, JFlash, GDB VTref=1.800V Type "connect" to establish a target connection, '?' for help J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect Device "MIMX9352_M33" selected. Connecting to target via SWD ConfigTargetSettings() start ConfigTargetSettings() end - Took 12us InitTarget() start InitTarget() end - Took 2.53ms Found SW-DP with ID 0x5BA02477 DPIDR: 0x5BA02477 CoreSight SoC-400 or earlier AP map detection skipped. Manually configured AP map found. AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[1]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: Core found AP[3]: AHB-AP ROM base: 0xE00FF000 CPUID register: 0x411FD210. Implementer code: 0x41 (ARM) Feature set: Mainline Cache: No cache Found Cortex-M33 r1p0, Little endian. Cortex-M (ARMv8-M and later): The connected J-Link (S/N 600109556) uses an old firmware module that does not handle I/D-cache correctly. Proper debugging functionality cannot be guaranteed if cache is enabled FPUnit: 8 code (BP) slots and 0 literal slots Security extension: implemented Secure debug: enabled CoreSight components: ROMTbl[0] @ E00FF000 [0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33 [0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT [0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB [0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM [0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM [0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI Memory zones: Zone: "Default" Description: Default access mode Cortex-M33 identified. J-Link>   5.You can also switch the sw1 to 0011 boot the A55 and stop at U-boot, then run the J-link commander The following is the command: J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect   The following is the full log: SEGGER J-Link Commander V8.10 (Compiled Sep 26 2024 08:38:41) DLL version V8.10, compiled Sep 26 2024 08:37:48 Connecting to J-Link via USB...O.K. Firmware: J-Link V10 compiled Jan 30 2023 11:28:07 Hardware version: V10.10 J-Link uptime (since boot): N/A (Not supported by this model) S/N: 600109556 License(s): RDI, FlashBP, FlashDL, JFlash, GDB VTref=1.806V Type "connect" to establish a target connection, '?' for help J-Link>device MIMX9352_M33 J-Link>speed 4000 Selecting 4000 kHz as target interface speed J-Link>si swd Selecting SWD as current target interface. J-Link>power on J-Link>connect Device "MIMX9352_M33" selected. Connecting to target via SWD ConfigTargetSettings() start ConfigTargetSettings() end - Took 27us InitTarget() start InitTarget() end - Took 3.89ms Found SW-DP with ID 0x5BA02477 DPIDR: 0x5BA02477 CoreSight SoC-400 or earlier AP map detection skipped. Manually configured AP map found. AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[1]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: Core found AP[3]: AHB-AP ROM base: 0xE00FF000 CPUID register: 0x411FD210. Implementer code: 0x41 (ARM) Feature set: Mainline Cache: No cache Found Cortex-M33 r1p0, Little endian. Cortex-M (ARMv8-M and later): The connected J-Link (S/N 600109556) uses an old firmware module that does not handle I/D-cache correctly. Proper debugging functionality cannot be guaranteed if cache is enabled FPUnit: 8 code (BP) slots and 0 literal slots Security extension: implemented Secure debug: enabled CoreSight components: ROMTbl[0] @ E00FF000 [0][0]: E000E000 CID B105900D PID 000BBD21 DEVARCH 47702A04 DEVTYPE 00 Cortex-M33 [0][1]: E0001000 CID B105900D PID 000BBD21 DEVARCH 47701A02 DEVTYPE 00 DWT [0][2]: E0002000 CID B105900D PID 000BBD21 DEVARCH 47701A03 DEVTYPE 00 FPB [0][3]: E0000000 CID B105900D PID 000BBD21 DEVARCH 47701A01 DEVTYPE 43 ITM [0][5]: E0041000 CID B105900D PID 002BBD21 DEVARCH 47724A13 DEVTYPE 13 ETM [0][6]: E0042000 CID B105900D PID 000BBD21 DEVARCH 47701A14 DEVTYPE 14 CSS600-CTI Memory zones: Zone: "Default" Description: Default access mode Cortex-M33 identified. J-Link>device MIMX9352_A55_0 Disconnecting from J-Link...O.K. Device "MIMX9352_A55_0" selected. Connecting to target via SWD ConfigTargetSettings() start ConfigTargetSettings() end - Took 19us Found SW-DP with ID 0x5BA02477 DPIDR: 0x5BA02477 CoreSight SoC-400 or earlier AP map detection skipped. Manually configured AP map found. AP[0]: AHB-AP (IDR: Not set, ADDR: 0x00000000) AP[1]: APB-AP (IDR: Not set, ADDR: 0x00000000) AP[2]: MEM-AP (IDR: Not set, ADDR: 0x00000000) AP[3]: AHB-AP (IDR: Not set, ADDR: 0x00000000) Using preconfigured AP[1] as APB-AP AP[1]: APB-AP found DebugRegs + CTI manually specified. ROM table scan skipped. Cortex-A55 @ 0x80810000 (configured) CoreCTI @ 0x80820000 (configured) Debug architecture: ARMv8.2 6 code breakpoints, 4 data breakpoints Processor features: EL0 support: AArch64 + AArch32 EL1 support: AArch64 + AArch32 EL2 support: AArch64 + AArch32 EL3 support: AArch64 + AArch32 FPU support: Single + Double + Conversion + single arithmetic ARMv8-A/R: The connected J-Link (S/N 600109556) uses an old firmware module V0 with known problems / limitations. Add. info (CPU temp. halted) Current exception level: EL2 Exception level AArch usage: EL0: AArch32 EL1: AArch32 EL2: AArch64 EL3: AArch64 Non-secure status: Non-secure Cache info: Inner cache boundary: none LoU Uniprocessor: 0 LoC: 0 LoU Inner Shareable: 0 VMSAv8-64: Supports 48-bit VAs Memory zones: Zone: "Default" Description: Default access mode Zone: "AP0" Description: MEM-AP (AHB-AP) Zone: "AP1" Description: MEM-AP (APB-AP) Zone: "AP3" Description: MEM-AP (AHB-AP) Cortex-A55 identified. Memory zones: Zone: "Default" Description: Default access mode Zone: "AP0" Description: MEM-AP (AHB-AP) Zone: "AP1" Description: MEM-AP (APB-AP) Zone: "AP3" Description: MEM-AP (AHB-AP) J-Link>  

  The FRDM i.MX 8M Plus development board is a low-cost and compact development board with NXP i.MX 8M Plus applications processor. On-board NXP IW612 Tri-Radio module supports Wi-Fi 6 + Bluetooth Low Energy 5.4 + 802.15.4. NXP releases Debian every six months and releases Yocto every year for this board. The FRDM i.MX 8M Plus development board is ideal for developing modern Industrial and IoT applications.   Get to know FRDM-IMX8MPLUS Development Boaard     Specifications 4× Arm® Cortex®A53 + 1× Arm Cortex-M7 LPDDR4 32-bit 4GB eMMC 5.1, 32GB QSPI NOR flash, 32 MB Power Management IC (PMIC) MicroSD 3.0 card slot One USB 3.0 Type-C connector One USB 2.0 Type-C for debug One USB 3.0 Type-A connector One USB Type-C PD only Onboard Wi-Fi® 6 + Bluetooth® LE 5.4/802.15.4 module Optional M.2 Key-E for Wi-Fi/ BT/802.15.4 M.2 Key-M for SSD Multiple display interface:     MIPI-DSI connector 2x4 data lane LVDS w/ Backlight HDMI connector Two MIPI-CSI connectors One 2x5 Pin NXP custom interface with: One CAN port I2C expansion Two 1 Gbps Ethernet Port0 supports POE Port1 supports TSN External RTC with coin cell connector 40 pin (2 x 20) expansion I/O     Feature FRDM-IMX8MPLUS eMMC 32GB DRAM Micron 4GB PMIC PCA9450C WiFi Module u-blox MAYA-W276 on-board USB Type-C+Type-A ENET 2xGbE M.2 (Key E) SDIO WiFi / BT Y (rework needed) M.2 (Key M) PCIE Y HDMI Y MIPI DSI Panel 22 Pins FPC HDR LVDS Panel 40 Pins 2mm HDR MIPI CSI camera 22 Pins FPC HDR 2x20 Expansion Interface Y CAN BUS Y MicroSD Y UART Y Audio WM8962B Remote Debug N NXP Connector (CAN, I2C) Y Power Connector Type-C PCB layers 6 Board DIM 12x13cm       NXP Devices On-Board PMIC PCA9450C USB PD TCPC PHY IC PTN5110 High-Voltage USB PD Power Switch NX20P5090UK I2C  Extends  GPIO PCAL6416A USB3.0 Switch CBTL02043A I2C Repeater PCA9509PDP Bi-directional Level Shifter NTS0104 CAN Transceiver TJA1051T/3 USB Sink & Source combo power switch NX20P3483UK USB Type-C CC and SBU Protection IC NX20P0407 Real-time clock/calendar PCF2131 Wi-Fi, BT, 802.15.4 Tri-Radio IW612 (in u-blox Module)     Expansion Boards RPI-CAM-MIPI: IAS camera to 22 Pins FPC camera adapter Waveshare 7'' DSI LCD: 7inch Capacitive Touch, 1024×600 DY1212W-4856 TFT LCD panel with LVDS interface: 12.1" (WXGA) TFT LCD panel with LVDS interface ​8MIC-RPI-MX8: 8-microphone array proto board for voice enablement   Trainings   Generic FRDM-IMX8MPLUS Software Release Deploy Android14 on FRDM-iMX8MP Lf6.6.36   Useful Links −i.MX Yocto Project User’s Guide​ −i.MX Linux User’s Guide ​−i.MX Linux Reference Manual​ −i.MX Porting Guide -i.MX Debian Linux SDK User Guide

Bring up Wi-Fi and Bluetooth interface. Configure and bring up Bluetooth A2DP sink profile. Configure and bring up Wi-Fi STA mode and perform throughput test. Bluetooth A2DP Sink profile configurations STA mode creation Connection of STA device to Ext AP Execution of udhcp client to receive the dynamic IP address from Ext AP iPerf server execution on Ubuntu/Windows machine iPerf client execution on FRDM i.MX 93 board 802.15.4 configuration on FRDM i.MX 93 board Wi-Fi Bluetooth LE and OT COEX Hands-on Demo Guide  Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

In this lab, you will learn how to: Load wireless module into board Bring-up Bluetooth + 802.15.4 firmware Initialize the 802.15.4 interface on the FRDM-i.MX93 board. Configure and bring up the 802.15.4 interface. Create a thread network. Add nodes to the thread network. Verify thread network connectivity. Exchange data between thread nodes.   OpenTread Hands-on Demo Guide  Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

Load drivers of wireless module into board Bring-up Bluetooth Scan/pair/connect Bluetooth with smartphone Hands-on Bluetooth A2DP sink/source profile demo play audio on remote Bluetooth headset or speaker using Bluetooth A2DP source profile play audio on FRDM i.MX 93 board from smart phone using Bluetooth A2DP sink profile Bluetooth A2DP Source and Sink Profile Demo    Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

This document assumes FRDM-iMX91 board is flashed with a Linux image. For flashing instructions, refer to FRDM-MX93_Board_Flashing guide. Then, follow this document to download software applications to test Wi-Fi, Bluetooth, and 802.15.4 performance. Hardware Prerequisites Windows or Linux PC with 64-bit OS 2 spare USB ports on PC FRDM-iMX91 Development Board Bluetooth LE device: Mobile phone which can configured as central or peripheral Wi-Fi Access Point: Standalone or mobile hotspot Wi-Fi Station: Mobile phone used as a station OPENTHREAD: 1 Another OT enabled board   Required PC Software Serial Terminal program Setting for terminal: Baud rate:115200, Parity: none, Data bits: 8, Stop bits: 1 Windows:   PUTTY or teraterm  and USB Device driver  Linux:           Minicom (Command to download the tool : sudo apt-get install minicom)   Iperf Windows:    Download Iperf version 3.0.11 from here. Linux:            Download Debian package of IPerf 3.0.11 for Ubuntu 16.04 from here. $ wget https://iperf.fr/download/ubuntu/iperf3_3.0.11-1_amd64.deb   Install the package using the command below. $ sudo dpkg -i /path/to/package/iperf3_3.0.11-1_amd64.deb   Required Mobile Software Iperf Application (iperf 3) Android:                  HE.NET Network Tools on Google Play iOS:                HE.NET Network Tools on AppStore   nRF Connect Application Android:                   nRF Connect on Google Play iOS:               nRF Connect on App Store   Required EVK Software Linux BSP Image  Version: L6.6.52_2.2.0 Link: https://www.nxp.com/webapp/sps/download/license.jsp?colCode=L6.6.52_2.2.0_MX91&appType=file1&DOWNLOA...   To download the pre-built image, please refer to https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/embedded-linux-for...   hands-on Labs Lab1 - WIFI Basic Hands-on Lab2 - Bluetooth A2DP Source and Sink Profile Demo Lab3 - OpenThread  Hands-on Lab4- WiFi Bluetooth and OT COEX Demo   Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

The FRDM-i.MX93 development board is designed to support advanced applications such as Industrial and Consumer HMI, Edge AI, Interconnected Devices, and High-Performance IoT Solutions. Built with NXP's i.MX 93 applications processor, it offers robust features like efficient machine learning acceleration, enhanced multimedia capabilities, and advanced connectivity options. This document provides a detailed guide on setting up the FRDM-i.MX93 development board. It includes hardware connections, flashing the Linux image, and accessing the debug console for seamless development and prototyping. FRDM-IMX93 Board Flashing Guide  Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

In this lab, you will learn how to: Bring up Wi-Fi interfaces. Run basic Wi-Fi scan Configure and bring up Wi-Fi STA mode using WPA_SUPPLICANT. Configure and bring up UDHCP server for dynamic IP assignment for associated client devices. Run UDHCP client to get dynamic IP address. Configure and bring up Wi-Fi AP mode using hostapd. Connect STA to external AP Connect AP to external STA Start ping  Wi-Fi Basic Hands on Demo Guide Video   Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

The FRDM-i.MX 91 development board enables Advance HMI Solutions supporting Industrial and consumer HMI, Enriched user experience, Immersive Audio Processing, Voice Solutions, and Interconnected Devices (smarter edge devices) among other applications. This document explains how to set up FRDM-i.MX 91 development board. This includes the hardware connections, flashing the Linux image, and accessing the debug console.   FRDM-IMX91 Board Flashing Guide Video   Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

In this lab, you will learn how to: Bring up Wi-Fi and Bluetooth interface. Configure and bring up Bluetooth A2DP sink profile. Configure and bring up Wi-Fi STA mode and perform throughput test. Bluetooth LE GATT profile configurations STA mode creation Connection of STA device to Ext AP Execution of udhcp client to receive the dynamic IP address from Ext AP iPerf server execution on Ubuntu/Windows machine iPerf client execution on FRDM i.MX 91 board OT child configuration on FRDM i.MX 91 board Wi-Fi Bluetooth LE and OT COEX Hands-on Demo Guide Video   Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

In this lab, you will learn how to: Load wireless module into board Bring-up Bluetooth The bring-up of 802.15.4 Initialize the 802.15.4 interface on the FRDM-i.MX91 board. Configure and bring up the 802.15.4 interface. Create a thread network. Add nodes to the thread network. Verify thread network connectivity. Exchange data between thread nodes.   OpenTread Hands-on Demo Guide Video   Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

In this lab, you will learn how to:   Bring-up Bluetooth interface. The LE GATT profile defines the way that two Bluetooth LE devices transfer the data using concept of Services and Characteristics. Configure and bring up Bluetooth LE GATT server profile using NXP-based IW610 module. Configure and bring up Bluetooth LE GATT client profile using NXP-based IW610 module. nRF connect smartphone application is used to run the LE GATT server with the help of predefined Heart Rate Service.   Bluetooth LE GATT Profile Demo Guide Lab Video   Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 

This document assumes FRDM-iMX91 board is flashed with a Linux image. For flashing instructions, refer to FRDM-iMX91_Board_Flashing guide. Then, follow this document to download software applications to test Wi-Fi, Bluetooth, and 802.15.4 performance. Hardware Prerequisites Windows or Linux PC with 64-bit OS 2 spare USB ports on PC FRDM-iMX91 Development Board Bluetooth LE device: Mobile phone which can configured as central or peripheral Wi-Fi Access Point: Standalone or mobile hotspot Wi-Fi Station: Mobile phone used as a station OPENTHREAD: 1 Another OT enabled board   Required PC Software   Serial Terminal program Setting for terminal: Baud rate:115200, Parity: none, Data bits: 8, Stop bits: 1 Windows:   PUTTY or teraterm  and USB Device driver  Linux:           Minicom (Command to download the tool : sudo apt-get install minicom)   Iperf Windows:    Download Iperf version 3.0.11 from here. Linux:            Download Debian package of IPerf 3.0.11 for Ubuntu 16.04 from here. $ wget https://iperf.fr/download/ubuntu/iperf3_3.0.11-1_amd64.deb   Install the package using the command below. $ sudo dpkg -i /path/to/package/iperf3_3.0.11-1_amd64.deb   Required Mobile Software   Iperf Application (iperf 3) Android:  HE.NET Network Tools on Google Play iOS:   HE.NET Network Tools on AppStore   nRF Connect Application Android:   nRF Connect on Google Play iOS:    nRF Connect on App Store   Required EVK Software Linux BSP Image  Version: L6.6.52_2.2.0 Link: https://www.nxp.com/webapp/sps/download/license.jsp?colCode=L6.6.52_2.2.0_MX91&appType=file1&DOWNLOAD_ID=null   To download the pre-built image, please refer to https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applications-processors:IMXLINUX   hands-on Labs   Lab1 - WIFI Hands-on Lab2 - Bluetooth LE GATT Profile  Lab3 - OpenThread  Lab4-WIFI_Bluetooth-LE_OpenThread   Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here   

Prerequisites  Hardware  FRDM-RW612 evaluation board  USB-C Cable Software Visual Studio Code VS Code Serial Terminal Software: Tera Term You can use any serial terminal you have, but we are using Tera Term for the training slides LCD-PAR-S035 display  Step by Step instructions document is here  Step by Step video:

Prerequisites  Hardware  FRDM-RW612 evaluation board  USB-C Cable Mobile phone (Android or IOS) Software Visual Studio Code VS Code Serial Terminal Software: Tera Term You can use any serial terminal you have, but we are using Tera Term for the training slides IoT Toolboox App Available for Android and iPhone app stores. Step by Step instructions document is here Step by Step video:

Prerequisites  Hardware  FRDM-RW612 evaluation board  USB-C cable Software Visual Studio Code VS Code FRDM-RW612 SDK Serial Terminal Software: Tera Term You can use any serial terminal you have, but we are using Tera Term for the training slides Step by Step instructions document is here Step by Step video:

Prerequisites  Hardware  FRDM-RW612 evaluation board  USB-C Cable Software Visual Studio Code VS Code Serial Terminal Software: Tera Term You can use any serial terminal you have, but we are using Tera Term for the training slides Step by Step instructions document is here Step by Step video:    

    Step by Step video: