FRDM Training Hub

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

FRDM Training Hub

FRDM Training and resources
Refer to here to explore available training materials and resources for FRDM development boards for microcontrollers and i.MX Application Processors to help you identify available content for you.

Discussions

Sort by:
Hands-on training utilizing NVIDIA's TAO toolkit and FRDM-IMX93
View full article
FRDM Training and Resources This article provide a guide of available resources for FRDM Development boards to help you to find and use available resources (Boards, Guides, Hands-On Trainings and more)
View full article
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>  
View full article
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 
View full article
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 
View full article
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 
View full article
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  Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here 
View full article
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 
View full article
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 
View full article
FRDM-IMX91 Hardware Introduction The FRDM i.MX 91 development board is a low-cost and compact development board with NXP i.MX91 applications processor. On-board NXP IW610 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 91 development board is ideal for developing modern Industrial and IoT applications. Get to know FRDM-IMX 91 Development Board   Specifications: 1x Arm® Cortex®-A55​ MAYA-W476-00B, Wi-Fi + BLE 5.4 + 802.15.4​​ Module on-board, IW610 2x GbE Ethernet (1xETER, 1xTSN) M.2 Key-E for Wi-Fi/BLE/802.15.4​ LPDDR4 16-bit 1GB eMMC 5.1, 8GB MicroSD 3.0 card slot 3x USB 2.0 Type-C connector (1-Debug, 1-PD, 1-USB2.0) + One USB 2.0 Type-A​ 40 pin (2x20) Expansion I/O One 2x5 Pin NXP interface (1- CAN, Two channels for ADC, I2C/I3C expansion)   Features FRDM-IMX91 eMMC 8GB DRAM NANYA 1GB PMIC PCA9451 WiFi Module u-blox MAYA-W476-00B on-board USB TYPE Type-C+Type-A ENET 2xGbE M.2 (Key E) SDIO Wi-Fi / BLE Y (rework needed) HDMI N Display (Parallel RGB LCD) 2x20 EXPI Camera (Parallel Camera) 2x20 EXPI 2x20 Expansion Interface Y CAN BUS Y MicroSD Y UART Y Audio  MQS Remote Debug N Power Connector Type-C PCB layers 10 Base Board DIM 6.5x10.5cm     NXP Devices On-board   PMIC PCA9451AHNY Real time clock/calendar PCF2131 WIFI/BLE/802.15.4 Tri-Radio IW610 in u-blox module CAN Transceiver TJA1051T/3 USB Type-C CC and SBU Protection IC NX20P0407  High-Voltage USB PD Power Switch NX20P5090UK USB PD and Type-C High-Voltage Sink/Source Combo Switch with Protection NX20P3483UK IIC Extends GPIO PCAL6524/ PCAL6408A Expansion Boards TM050RDH03-41: LCD display module 5” TFT 800X480, RGB, 120.7 mm x75.8 mm7inch MX93AUD-HAT: Audio expansion board with multiple features ​8MIC-RPI-MX8: 8-microphone array proto board for voice enablement Trainings   FRDM-IMX91 SW Release Package    Documentation  −FRDM-IMX91 Quick Start Guide −FRDM-IMX91 Board User Manual -FRDM-IMX91 Software User Guide   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
View full article
i.MX FRDM Development (FRDM) software release contains prebuilt images, documentation, and i.MX FRDM Yocto layer for FRDM-IMX boards. It also includes support for Matter and Debian release. This article will give a brief introduction of FRDM-IMX91 software release. For more details, please check i.MX FRDM Software User Guide. FRDM-IMX91 Yocto BSP Release Based on i.MX SW 2024 Q3 BSP release Linux kernel: 6.6.36_2.1.0 u-boot: 2024.04 i.MX FRDM Yocto layer source: https://github.com/nxp-imx-support/meta-imx-frdm FRDM-IMX91 BSP changes: U-boot: Add basic support for FRDM-IMX91 Kernel: Add basic support for FRDM-IMX91 and add support for kinds of accessories FRDM-IMX91 Yocto layer: Add Yocto layer for FRDM-IMX91 and integrate u-boot/kernel patches FRDM-IMX91 accessories and corresponding dtb: 5 inch Tianma LCD: imx91-11x11-frdm-tianma-wvga-panel.dtb RPI-CAM-INTB: imx91-11x11-frdm-mt9m114.dtb MX91AUD-HAT or MX91AUD-HAT + 8MIC-RPI-MX8: imx91-11x11-frdm-aud-hat.dtb 8MIC-RPI-MX8: imx91-11x11-frdm-8mic.dtb 2LL M.2 Module: imx91-11x11-frdm.dtb Build FRDM-IMX91 Yocto Image: Download i.MX SW 2024 Q3 Release: $ repo init -uhttps://github.com/nxp-imx/imx-manifest-b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml $ repo sync Integrate meta-imx-frdm layer into Yocto code base: $ cd ${MY_YOCTO}/sources $ git clone https://github.com/nxp-imx-support/meta-imx-frdm.git Yocto Project Setup: $ cd ${MY_YOCTO} $ MACHINE=imx91frdm DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-setup.sh -b frdm-imx91 Build images: $ bitbake imx-image-full Flashing SD card image using dd: $ zstdcat imx-image-full-imx91frdm.rootfs.wic.zst | sudo dd of=/dev/sdx bs=1M && sync Or using uuu to burn image to SD card: $ uuu -b sd_all imx-image-full-imx91frdm.rootfs.wic.zst FRDM-IMX91 Matter Support Based on i.MX Matter 2024 Q3 To include Matter support, please follow below steps to include Matter layer into Yocto build. Download i.MX SW 2024 Q3 BSP Release: $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml $ repo sync Download i.MX Matter Yocto layer: $ cd ${MY_YOCTO}/sources/meta-nxp-connectivity $ git remote update $ git checkout imx_matter_2024_q3 Integrate meta-imx-frdm layer into Yocto code base: $ cd ${MY_YOCTO}/sources $ git clone https://github.com/nxp-imx-support/meta-imx-frdm.git Yocto Project Setup: $ cd ${MY_YOCTO} $ MACHINE=imx91frdm-iwxxx-matter DISTRO=fsl-imx-xwayland source sources/meta-imx-frdm/tools/imx-frdm-matter-setup.sh bld-xwayland-imx91 Build images: $ bitbake imx-image-multimedia FRDM-IMX91 Debian Release FRDM-IMX91 has support for Debian 12 OS. i.MX Debian Linux SDK distribution is a combination of NXP-provided kernel and boot loaders with a Debian distro user-space image, which includes: Debian-based rootfs Debian Base (basic packages) Debian Server (more packages without GUI Desktop) Debian Desktop (with GNOME GUI Desktop) Linux kernel BSP components various applications (graphics, multimedia, networking, connectivity, security, and AI/ML) For more details of NXP Debian Linux SDK Distribution, please check NXP Debian Linux SDK Distribution for i.MX and Layerscape. Quick Start with Debian: To create an SD card with Debian for FRDM-IMX91, please follow below steps. Download flex-installer on the Linux host $ wget http://www.nxp.com/lgfiles/sdk/lsdk2412/flex-installer $ chmod +x flex-installer $ sudo mv flex-installer /usr/bin Plug the SD card into the Linux host and install the images as below # format SD card $ flex-installer -i pf -d /dev/sdb # automatically download and install images into SD card $ flex-installer -i auto -d /dev/mmcblk1 -m imx91frdm Plug the SD card into the FRDM-IMX91 board and install the extra packages as below         1. Setup Ethernet network interface by DHCP or setting it manually $ dhclient -i end0         2. Set correct system time, for example $ date -s "22 Nov 2024 09:00:00"         3. Install extra packages for GNOME GUI Desktop version $ debian-post-install-pkg desktop         4. Or install extra packages for Server version without GUI Desktop $ debian-post-install-pkg server         5. After finishing the installation, run the reboot command to boot up the Debian Desktop/Server system  Building Debian Images with Flexbuild: To build Debian image with Flexbuild for FRDM-IMX91, please follow below steps. Set up the build environment $ git clone https://github.com/nxp/flexbuild $ cd flexbuild && source setup.env #Continue to run commands below in case you need to build in Docker due to lack of Ubuntu 22.04 or Debian 12 host $ bld docker $ source setup.env Build image with Flexbuild $ bld -m imx91frdm Flexbuild usage: To build individual part of the image, please check below command list for Flexbuild usage $ bld uboot -m imx91frdm (compile u-boot image for imx91frdm) $ bld linux (compile linux kernel for all arm64 i.MX machines) $ bld bsp -m imx91frdm (generate BSP firmware) $ bld boot (generate boot partition tarball including kernel, dtb, modules, distro bootscript for iMX machines) $ bld multimedia (build multimedia components for i.MX platforms) $ bld rfs -r debian:server (generate Debian server rootfs) $ bld apps -r debian:server (compile apps against runtime dependencies of Debian server RootFS) $ bld merge-apps -r debian:server (merge iMX-specific apps into target Debian server RootFS) $ bld packrfs -r debian:server (pack and compress target debian server rootfs) Related Documentation FRDM-IMX91 Documents: FRDM-IMX91 Quick Start Guide FRDM-IMX91 Board User Manual i.MX FRDM Software User Guide More information about i.MX productions can be found at(http://www.nxp.com/imxlinux) i.MX Yocto Project User’s Guide​ i.MX Linux User’s Guide​ i.MX Linux Reference Manual​ i.MX Porting Guide Debian documents at http://www.nxp.com/nxpdebian i.MX Debian Linux SDK User Guide
View full article
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   
View full article
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 
View full article
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 
View full article
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 
View full article
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 
View full article
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 
View full article
  The RW61x is a highly integrated, low-power tri-radio wireless MCU with an integrated MCU and Wi-Fi ®  6 + Bluetooth ®  Low Energy (LE) 5.4 / 802.15.4 radios designed for a broad array of applications, including connected smart home devices, enterprise and industrial automation, smart accessories and smart energy. The RW612 MCU subsystem includes a 260 MHz Arm ®  Cortex ® -M33 core with Trustzone ™ -M, 1.2 MB on-chip SRAM and a high-bandwidth Quad SPI interface with an on-the-fly decryption engine for securely accessing off-chip XIP flash. The RW612 includes a full-featured 1x1 dual-band (2.4 GHz/5 GHz) 20 MHz Wi-Fi 6 (802.11ax) subsystem bringing higher throughput, better network efficiency, lower latency and improved range over previous generation Wi-Fi standards. The Bluetooth LE radio supports 2 Mbit/s high-speed data rate, long range and extended advertising. The on-chip 802.15.4 radio can support the latest Thread mesh networking protocol. In addition, the RW612 can support Matter over Wi-Fi or Matter over Thread offering a common, interoperable application layer across ecosystems and products. Hands-On Trainings Introduction to RW61x and FRDM-RW612 Quick introduction to RW61x family, module offering and FRDM-RW612 evaluation board FRDM-RW612 Out of the Box Experience Wi-Fi CLI (Command Line Interface) demo provides the user with a menu with different commands to explore the Wi-Fi capabilities of the FRDM RW612 board. When the board is powered on for the first time, the green RGB LED should be blinking indicating that the demo is loaded into the board. FRDM-RW612 Getting Started. Wi-Fi CLI on VS Code This lab guides you step by step on how to get started with FRD-RW612 board using Visual Studio Code  FRDM-RW612 BLE Sensors over Zephyr This demo shows the temperature from the i2c temperature sensor integrated in the board. This demo is based on Zephyr RTOS. The information can be monitored in the UART terminal or in the IoT Toolbox app. FRDM-RW612 Kitchen Timer using Low-cost LCD This lab shows how to modify a Kitchen Timer graphical application using LCD-PAR-S035 display Changing the date and button colors. The timer can also be viewed on a serial terminal.   Community Support If you have questions regarding this training or RW61x series, please leave your comments in our Wireless MCU Community! here 
View full article
    Step by Step video:
View full article
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:
View full article

The following has evaluated to null or missing: ==> defaults.manyEnable [in template "Language_CP_BulkTranslation_Angular" at line 168, column 56] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign displayConn = defaults.manyEn... [in template "Language_CP_BulkTranslation_Angular" at line 168, column 33] ----