飞思卡尔杯线扫描相机 - 第一部分 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 回顾 TFC-KIT 附带的飞思卡尔线扫描相机的设计和操作。将向观众展示传感器 IC 接口的高级概述。 查看视频链接：1471和视频链接：1472 （在 “我的视频” 中查看）

Device Tree Standalone Compile under Windows Sometime need standalone compile device tree. Only Linux headers and device tree directory are needed.  i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano i.MX6DL i.MX6Dual i.MX6DualPlus | 6QuadPlus i.MX6Quad i.MX6S i.MX6SL i.MX6SoloX i.MX6UL i.MX7Dual i.MX7Solo i.MX7ULP i.MX8ULP Linux Windows

How to load MDK RAM app to the RT1170 external flash How to load MDK RAM app to the RT1170 external flash 1. Abstract This guide is requested by our end customer, he wants to realize the MDK project RAM code download to the MIMXRT1170 external QSPI flash. So, based on the NXP RT1170 SDK, and the MIMXRT1170-EVK board, generate the MDK project, reallocate the app image, generate the image, and use the tool to download the code to the external flash. 2. App image prepare 2.1 Generate one SDK MDK standalone project Open the SDK_2_15_000_MIMXRT1170-EVK webpage: https://mcuxpresso.nxp.com/en/builder?hw=MIMXRT1170-EVK Download the SDK, and generate one MDK standalone project: Fig 1 Fig 2 After downloading, we will get the MIMXRT1170-EVK-iled_blinky_cm7.zip, which is the MDK project. 2.2 MDK project image reallocation As the RAM image is the none-xip image, normally to the IDE, can’t download to the flash directly, as the debug is in the RAM. If want to download to the flash, we can generate the app image, then use the tool to program it to the external flash. Normally, none-xip image, the IVT offset is 0X400, so we need to reallocate the image start address, here, we can use 0X2000 as the app entry address. Fig 3 ITCM default size is 256K=0X4000, so modify the linker file-> scf file like this: Fig 4 Now, to generate the hex and bin image file, which is used for the tool downloading. Fig 5 To build the bin file command: $K\ARM\ARMCC\bin\fromelf.exe --bin --output=debug\@L.bin !L Fig 6   Building, you can find the file in the folder: MIMXRT1170-EVK-iled_blinky_cm7\iled_blinky_cm7\debug Fig 7 2.3 MDK project debug after reallocation After the image reallocation, some customer may still need the MDK RAM project can do the debugging, here, also need to modify the debug .ini file. The Setup also need to change the SP, PC and Vector table offset register address. Fig 8 Then build and debug the code, we can find it can enter the ram image debug mode: Fig 9 3. App image download We can use the MCUBootUtility Tool to download the code: https://github.com/JayHeng/NXP-MCUBootUtility/releases/tag/v6.1.0 the related user manual is: https://github.com/JayHeng/NXP-MCUBootUtility Download the tool. MIMXRT1170-EVK enter the serial download mode by changing SW1: 1-OFF,2-OFF,3-OFF,4-ON Power off and power on the board again, find another USB cable to connect the J20 USB1 interface. Then, use the MCUBootutility to connect the board: Fig 10 After connection, select the MDK project generated .hex file: Fig 11 Press the All-in-One-Action button, to download the code, this is the downloaded result: Fig 12 Press the “Reset device” button to exit the tool. Then MIMXRT1170-EVK board change SW1: 1-OFF, 2-OFF, 3-ON,4-OFF Press the EVK on board reset button, SW4, you will find the LED is blinking, it means the MDK RAM project already download to the external QSPI flash, and boot OK.

直流电机控制简介 - 第二部分 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在本视频中，我们将研究现成的商业 (COTS) H 桥 IC。还将检查 FRDM-TFC 的示例代码。 （在 “我的视频” 中查看）

ラインスキャンカメラデータ処理 - パートII <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ラインスキャンカメラデータ処理 - パートII (マイビデオで視聴)

i.MX v16.0 の設定ツールの提供開始 この度、Config Tools for i.MX v16.0 がリリースされました。 ダウンロード & リンク すべてのプラットフォーム用インストーラーをダウンロードするには、次の方法でダウンロードサイトにログインしてください。 https://www.nxp.com/design/designs/config-tools-for-i-mx-applications-processors:CONFIG-TOOLS-IMX インストールガイドとクイックスタートガイドについては  ドキュメントを参照してください。 DDRの設定と検証の詳細については、この  ブログ記事をご覧ください。 リリース・ノート リリースの詳細 (機能、既知の問題...) この製品は Eclipse 2023-12 に基づいています フレームワーク –ConfigToolsforforの周辺機器ツールを有効にします i.MX –ConfigToolsforforのClocksツール i.MX 有効にします –新しいコマンドライン引数(-UpdateCode)が追加されました。更新と同じアクションを実行します ユーザーインターフェースのコードボタン。-HeadlessToolと一緒に使用する必要があります。 DDRツール – mScaleプロセッサのCAバスドライバの強度とODT構成が追加されました。 – [MX 93 / MX 91]UIからのUART構成が追加されました。 –構成ツールのMX91DDRツールの更新 – MX 93 PF 09 DDR ツールのサポートが追加されました。 SerDes ツール – MX 95 SerDes ツールのサポートが有効になっています。 ピンツール –同時ルーティング検出(1つの信号をルーティングすると、複数の信号がベースでルーティングされる場合があります 同じレジスタ設定)が追加されます。その場合、そのようなシグナルは 構成。 –パッケージにない内部ピンのサポートが追加されました。

HC08 Library of Bootloader application.pdf How to allocate HC08 library of boot loader application . How to allocate HC08 library of boot loader application . General

FS26xx OTP指令 请参阅附件中的 FS26XX OTP 指令文档。 谢谢！

任务＃1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Yocto 项目版本和名称 准备主机环境 对于虚拟机（VirtualBox）： 从 NXP Code Aurora 下载源代码 Yocto 项目版本和名称 请参阅此处所有 yocto 版本名称的列表：发布 - Yocto 项目 当前稳定版本是Zeus 准备主机环境 对于虚拟机（VirtualBox）： 请将内存大小最小设置为 1GB，磁盘大小设置为 32GB。（2014 年 2 月 24 日 Ubuntu 12.04LTS）   首先，确保您的主机 PC 具有运行 Yocto 所需的软件包 以下命令显示了受支持的 Ubuntu 发行版所需的基本软件包： $ sudo apt-get build-dep qemu $ sudo apt-get remove oss4-dev $ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \   build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \   xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \   xterm‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ 对于其他 Linux 发行版或较新的 Yocto 项目版本，请参阅此处的更新列表。 从社区下载源代码 安装 repo $ sudo apt-get install repo‍‍‍‍ 下载BSP源代码： $ mkdir fsl-community-bsp $ cd fsl-community-bsp $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b zeus $ repo sync‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ 从 NXP Code Aurora 下载源代码 请参阅此处 NXP 所有 BSP 版本的列表： imx-manifest - i.MX 发布清单 目前，最新的 NXP 版本操作方法如下： README - imx-manifest - i.MX Release Manifest 要了解 2 个源代码（社区 X NXP BSP）之间的区别，请参见此处 前往https://community.nxp.com/docs/DOC-94849 转到任务 #2 Yocto Project 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我尝试以 root 用户身份进行操作。当我初始化 repo 时我仍然得到这个。 因此，当我尝试repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dora 时出现以下错误 curl：（22）请求的URL返回错误：404 服务器不提供 clone.bundle；忽略。 但我继续了，我认为没有问题。 正如您所描述的，我下载了大约 238MB。后来我改变了 fsl-community-bsp 目录的所有权。 感谢您的支持。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 是的，您已完成，可以开始任务 2 有时，尝试再次下载 repo，并尝试了解为什么会遇到这些错误。由于 repo 用于 android，因此有多个论坛存在多个 repo 错误。慢慢地修复你的环境。 从 yocto 的角度来看，您不需要 repo 来完成工作。当不使用 fsl 社区 bsp 时，会有细微的差别，它是设置环境脚本（您应该使用 poky 中的那个，它是 oe-init-build-env （ http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/oe-init-build-env ） 并且您必须在 build/conf/bblayers.conf 中包含所有层。请查看此处https://community.freescale.com/docs/DOC-94614 你的 bblayers 应该是什么样子。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> git 克隆 git://git.yoctoproject.org/poky 克隆成‘poky’…… 远程：计数对象：226330，完成。 远程：压缩对象：100％（57269/57269），完成。 远程：总计 226330（增量 164862），重用 225517（增量 164064） 接收对象：100％（226330/226330），100.81 MiB | 193 KiB/s，完成。 解决增量：100％（164862/164862），完成。 jigar@ubuntu:~/fsl-community-bsp$ git clone git://git.yoctoproject.org/meta-fsl-arm 克隆到‘meta-fsl-arm’... 远程：计数对象：6917，完成。 远程：压缩对象：100% (2582/2582)，完成。 远程：总计 6917（增量 4165），重用 6788（增量 4037） 接收对象：100％（6917/6917），37.29 MiB | 206 KiB/s，完成。 解决增量：100％（4165/4165），完成。 我尝试了meta-openembedded、 fsl-community-bsp-base、meta-fsl-arm-extra、meta-fsl-demos…… 现在我有 6 个如上所述的目录。 现在我下一步该做什么？或者它已经完成了，我可以开始任务 2 了吗？:smileyconfused: 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 是的，当然安装了 git。 我有最新版本的 git.. apt-get 安装 git 正在读取软件包列表...完成 构建依赖树 正在读取状态信息...完成 git已经是最新版本了。 升级了 0 个，新安装了 0 个，删除了 0 个，未升级 5 个。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 和我一模一样。 哦......你安装了 git 吗???????????? （只是为了确保） （我的 python 是 2.7.5+，我的 git 是 1.8.3.2，我的 gcc 是 4.8.1） 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 不，我还没有尝试过 git clone，而且我不知道如何使用 git clone。:smileysilly: 我用的是这个版本 repo 版本 v1.12.13 （来自https://gerrit.googlesource.com/git-repo ） repo 启动器版本 1.21 git 版本 1.7.9.5 Python 2.7.3（默认，2014 年 2 月 27 日，19:58:35） [GCC 4.6.3] 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您正在使用更新的 repo 文件吗？ 您是否尝试过每个元层的“git clone”？（如果您知道如何做，请告诉我：smileywink：） 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我想要它来交叉编译 qt5 HMI 应用程序。 我有一块 imx6qsabreauto 板。 我想刷新这个板子。 我想用它来做信息娱乐。 我尝试了 http 和 https，但仍然不起作用。:笑脸悲伤: 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我的本地配置中出现了几个有关 http 和 https 的错误。 在 repo 内部您可能会看到一个 URL，您可以将 http 更改为 https（或反之亦然）并尝试与默认值不同的 URL。 或者，您可以使用 git clone 逐个下载每个元层，而不是使用 repo。 清单： https://github.com/Freescale/fsl-community-bsp-platform/blob/dora/default.xml 向您展示要下载什么以及要使用哪个分支。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 好的。这意味着我的代理有问题。 您能建议我采取哪些步骤才能成功下载它吗？ 我尝试了您给出的链接，但是在 repo sync -init 步骤中出现了 curl:(22) 错误。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 让我在这里试试 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 实际上，我在家里的个人笔记本电脑上尝试过这个，但也出现了错误。 curl：（22）请求的URL返回错误：404 服务器不提供clone.bundle；忽略。 在办公室，我在代理下工作，并根据需要设置代理。我的端口也开放了。 并且我也拥有外部网络的访问权限。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 请确保您拥有正确的外部网络访问权限。您有代理人吗？你的 http/https 端口开放了吗？ 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 它仅下载新内容。除非您删除下载目录。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 更改 repo 提供商 URL 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这个问题的解决方案是什么？我看到了同样的问题。 谢谢！ 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 它对我有用。一分钟前刚刚测试过。 你遇到了什么错误？ 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> dora 是最新稳定分支，刚刚正式发布！ 谢谢florianl 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好！ 您在教程中写道： $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform-b 迪伦 还建议使用“dylan”吗？我听说“dora”将会是一个更新的版本，可以更好地支持主板？（例如这里：http: //boundarydevices.com/yocto-dora-release-mx6/ ） 如果 dora 更好的话，我们应该在上面的 DOC 中更新此部分 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 非常感谢， petersuciu ！ 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 黛安娜， 请更新说明，并提供最新的 curl URL，为人们节省几个小时的时间并保护他们头上的头发。 谢谢！ 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您有代理人吗？ 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢 Ajay，我要修复我的文档。 我只使用 Ubuntu，所以请继续执行任务并继续报告您遇到的任何问题！它将帮助很多将来可能会关注它的人 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我会写： 首先，确保您的主机 PC 具有运行 Yocto 所需的软件包。 回复：任务 #1 - 下载源代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 非常感谢

割り込みの背景 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> マイクロコントローラの割り込みを一般的な観点から見てみましょう。これは、ARM コアの割り込みに関連する他のビデオをコンテキストに配置するために使用されます。 (マイビデオで視聴) Re:割り込みの背景 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ビデオ チュートリアルの完全なセットについては、「The Book of Eli - Microcontrollers, robotics and warp drives」をご覧ください。

DCモータ制御の概要 - パートII <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この動画では、シェルフ(COTS)のH-Bridge ICのCMについて解説します。FRDM-TFCのサンプルコードについても検討します。 (マイビデオで視聴)

GoPoint Demo On FRDM-IMX93 GoPoint GoPoint is a user-friendly application that allows the user to launch preselected demonstrations included in the NXP provided BSP and follows the quarterly release roadmap for BSP How to launch GoPoint   GoPoint Demo On FRDM-IMX93 Board Since FRDM-IMX93 board’s BSP is based on standard BSP release, GoPoint is included in FRDM-IMX93 Yocto build by default. List of 9 demos available on FRDM-IMX93 Board: Image Classification Object Detection Selfie Segmenter i.MX Smart Fitness DMS (Driver Monitor System) ML Benchmark Video Test i.MX Smart Kitchen i.MX E-Bike VIT Image Classification Demo Image classification is a ML task that attempts to comprehend an entire image as a whole. The goal is to classify the image by assigning it to a specific label. Typically, it refers to images in which only one object appears and is analyzed. This example is using NNStreamer.      Object Detection Demo Object detection is the ML task that detects instances of objects of a certain class within an image. A bounding box and a class label are found for each detected object. This example is using NNStreamer.    Selfie Segmenter Demo Selfie Segmenter showcases the ML capabilities of i.MX 93 by using the NPU to accelerate an instance segmentation model. This model lets you segment the portrait of a person and can be used to replace or modify the background of an image. This example is using NNStreamer.     i.MX Smart Fitness Demo i.MX Smart Fitness showcases the i.MX' Machine Learning capabilities by using an NPU to accelerate two Deep Learning vision-based models. Together, these models detect a person present in the scene and predict 33 3D-keypoints to generate a complete body landmark, known as pose estimation. From the pose estimation, the application tracks the 'squats' fitness exercise.      DMS (Driver Monitor System) Demo This application showcases the capability of implementing DMS on i.MX 93 platform, and the performance boost brought by Neural Processing Unit (NPU). DMS uses four ML models in total to achieve face detection, capturing face landmark and iris landmark, smoking detection and calling detection.     ML Benchmark Demo This example is based on benchmark_model tool in Tensorflow Lite framework, which allows to easily compare the performance of TensorFlow Lite models running on CPU (Cortex-A) and NPU. Video Test Demo This is a simple demo that allows users to play back video captured on a camera or a test source. It’s based on gstreamer pipeline.      i.MX Smart Kitchen Demo i.MX Smart Kitchen showcases the Multimedia capabilities of i.MX to emulate an interactive kitchen through a GUI controlled by voice commands. The GUI is based on LVGL (Little Versatile Graphic Library) and NXP's Voice Intelligent Technology (VIT) supports the voice commands. Usage: Keyword + command     i.MX E-Bike VIT Demo i.MX E-Bike VIT showcases the Multimedia capabilities of i.MX to emulate an interactive ebike through a GUI controlled by voice commands. The GUI is based on LVGL (Little Versatile Graphic Library) and NXP's Voice Intelligent Technology (VIT) supports the voice commands. Usage: Keyword + command     Useful Link GoPoint User Guide: https://www.nxp.com/webapp/Download?colCode=GPNTUG GoPoint repo: https://github.com/nxp-imx-support/nxp-demo-experience-demos-list/tree/lf-6.6.36_2.1.0 (Including source code of demo: Selfie Segmenter, DMS, ML benchmark, Video test) Image Classification/Object Detection: https://github.com/nxp-imx/eiq-example/tree/lf-6.6.36_2.1.0 i.MX Smart Fitness: https://github.com/nxp-imx-support/imx-smart-fitness i.MX Smart Kitchen: https://github.com/nxp-imx-support/smart-kitchen i.MX E-Bike VIT: https://github.com/nxp-imx-support/imx-ebike-vit FRDM-IMX93 FRDM-Training i.MX Application Processors MCU Wireless

MCUXpresso 安装程序错误：手动安装工具 MCUXpresso 安装程序是一种工具，用于为 VS Code 的 MCUXpresso 扩展或使用 Zephyr 进行开发安装其他软件、工具和依赖项。它将这些安装程序下载到缓存文件夹中，然后执行安装程序。如果在安装这些组件时出现错误，安装程序日志将显示哪个工具安装失败。如果失败的原因不清楚，您可以手动运行该工具的安装程序。这可能会解决问题，或者可能会提供安装程序失败的更多详细信息。 MCUXpresso 安装程序日志将提供工具安装程序所在的缓存文件夹的路径。通常在 Windows 中，此路径位于： C:\Users\ \AppData\Local\Programs\MCUXpressoInstaller\.cache 使用管理员权限安装也可能有助于解决该问题。

i.MX6 D/Q and i.MX6 DL/S Android JB4.2.2_1.0.0-GA release Hi All, The new Android JB4.2.2_1.0.0-GA release is now available on www.freescale.com ·         Files available Name Description IMX6_JB422_100_ANDROID_DOCS i.MX 6Quad, i.MX 6Dual, and   i.MX 6DualLite Android jb4.2.2_1.0.0 BSP Documentation. Includes Release   Notes, User's Guide, QSG and FAQ Sheet. IMX6_JB422_100_ANDROID_SOURCE i.MX 6Quad, i.MX 6Dual, and   i.MX 6DualLite Android jb4.2.2_1.0.0 BSP, Documentation and Source Code for   BSP and Codecs. IMX6_JB422_100_ANDROID_DEMO i.MX 6Quad, i.MX 6Dual, and   i.MX 6DualLite Android jb4.2.2_1.0.0 BSP Binary Demo Files ·         Target HW boards o   i.MX6DL  SABRE SD board o   i.MX6Q  SABRE SD board o   i.MX6DQ SABRE AI board o   i.MX6DL SABRE AI board ·         Release Description i.MX Android jb4.2.2_1.0.0-ga is GA release for Android 4.2.2 Jelly Bean(JB) on i.MX6Q SABRE SD, i.MX6DL SABRE SD and i.MX6Q/DL SABRE AI platform with key features integrated. i.MX Android jb4.2.2_1.0.0-ga release includes all necessary codes, documents and tools to assist users in building and running Android 4.2.2 on i.MX6Q and i.MX6DL hardware board from the scratch. The prebuilt images are also included for a quick trial on Freescale i.MX6Q, i.MX6DL SABRE SD and i.MX6Q/DL SABRE AI boards. Most of deliveries in this release are provided in source code with the exception of some proprietary modules/libraries from third parties. ·         Features Feature i.MX6Q   SABRE SD i.MX6DL   SABRE SD i.MX6   SABRE AI Comments Linux 3.0.35  kernel Y Y Y Based on Linux BSP   L3.0.35_4.0.0 GA release Google JellyBean   4.2.2 release Y Y Y Based on   android-4.2.2_r1 release Bootup with Android Y Y Y Boot source eMMC& External SD eMMC& External SD SD&Nand Default Nand chip   been support is Micron MT29F8G08ABABAWP Splash Screen for   LVDS Y Y N UI (input) Multi-touch on LVDS   panel Multi-touch on LVDS panel Multi-touch on LVDS   panel UI (display) LVDS panel, HDMI   display LVDS panel, HDMI   display LVDS panel, HDMI   display UI (dual display,   LVDS+HDMI, UI mirror displayed on second device) Y Y Y UI (brightness   control) Y Y Y UI (LiveWallpaper) Y Y Y Storage - External   Media Y Y Y SD, External SD and   UDisk Storage - MTP   (Media Transfer Protocol) Y Y Y Connectivity -   Ethernet Y Y Y Connectivity - BT     Y Y     N Hardware: ·           Atheros AR3001 ·           Atheros AR3002 Profiles: ·           A2DP ·           HID ·           OPP ·           PBAP Connectivity - WiFi Y Y     Y Hardware: ·           Atheros AR6103 SDIO card Features: ·           AP mode ·           Wake on Wireless Connectivity -   3G Y Y   N Hardware: ·           HUAWEI EM770W modem ·           Infinion Amazon 1 modem ·           ZTE FM210 modem Connectivity -   GPS Y Y N Connectivity - USB Tethering Y Y Y Support WIFI and   Ethernet as upstream Internet - SIP   voice call N N N Internet - VPN Y Y Y Power - Battery   status report Y Y N/A Known limitations   about the accuracy in some use cases Power - CPU Freq Y Y Y Power - Bus Freq Y Y Y Media - Music Play Y Y Y Media - Sound Record Y Y Y Media - Video Play Y Y Y Media - Camera Y Y N Media - TVIN N/A N/A Y PAL/NTSC Media - Dual Camera Y Y Y Hardware for SABRE SD: ·           Front Camera: OV5642 CSI camera ·           Rear Camera: OV5640 MIPI camera Hardware   for SABRE AI: ·           Front Camera: UVC camera ·           Rear Camera: TV IN Media - Camcorder Y Y N Media - USB Camera Y Y Y Logitech: ·           C250 ·           E3500 Media - USB Micro Y Y Y Media - Movie   Studio Y Y Y Media - HDMI audio output Y Y Y Graphic - HW 3D   acceleration Y Y Y OpenGLES 1.1/2.0   via GC2000 or GC800 3D core Graphic - HW   accelerated UI surface composition Y Y Y Misc - ADB over USB Y Y Y Misc - Fastboot   utility Y Y Y Misc - SW update   and factory reset Y Y Y Sensor - Magmatic Y Y N Sensor -   Accelerometer Y Y N Sensor - Light Y Y N NTFS-3G File System Y Y Y For external   Storage NAND N N Y Tested NAND chip: - Micro 29F8G08ABABA ·         Change List The below section lists the big changes in JellyBean which need the user’s attention when comparing to Freescale ICS version: o   Default Android multiple display implementation in JellyBean o   Display resolution change in Setting is not been supported o   New camera hal implementation based on JellyBean libcamera2 o   Add NTFS file system support for external storage ·         Known issues For known issues and limitations please consult the release notes Android i.MX6DL i.MX6Dual i.MX6Quad i.MX6S

FRDM-RW612 Getting Started. Wi-Fi CLI on VS Code 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: (view in My Videos) FRDM-RW612 FRDM-Training Hands-On Training MCU Wireless

Waking up iMX93EVK from Deep Sleep via GPIO -- DTS for gpio wakeup // SPDX-License-Identifier: (GPL-2.0+ OR MIT) /*  * Copyright 2022 NXP  */ #include "imx93-11x11-evk.dts" / {         gpio-keys {                 compatible = "gpio-keys";                 pinctrl-names = "default";                 pinctrl-0 = <&pinctrl_gpio_keys>;                 power {                   label = "GPIO Key Power";                   linux,code = ;                   gpios = <&gpio2 7 GPIO_ACTIVE_LOW>;                   wakeup-source;                   debounce-interval = <20>;                   interrupt-parent = <&gpio2>;                   interrupts = <7 IRQ_TYPE_LEVEL_LOW>;                 };         }; }; &iomuxc {         pinctrl_gpio_keys: gpio_keys_grp {                 fsl,pins = <                         MX93_PAD_GPIO_IO07__GPIO2_IO07  0x31e                 >;         }; }; -- testing the switch GPIO  First check if your gpio dts configuration to make it act as a switch works or not After executing the command - 'evtest /dev/input/event1' Trigger an interrupt by connecting GPIO2 7 to GND, as soon as you do that, you will receive Event logs such as below:- This shows that your dts configuration for GPIO works.   -- Verify the interrupt       -- Go to sleep and then connect the GPIO to GND to trigger a wakeup, in the logs we see that kernel exits the suspend mode   i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Linux Yocto Project

Updating Firmware via USB DFU Based on RT1170 Updating Firmware via USB DFU Based on RT1170 Updating Firmware via USB DFU Based on RT1170         Development Environment         Preparing dfu-util                  Steps to Prepare dfu-util         Running the Demo                  Using Prebuilt Firmware from SDK                  Using Custom Firmware Performing microcontroller (MCU) firmware upgrades in the field without the aid of external programming tools is a necessary feature. For MCUs that support USB device controllers, the USB Device Firmware Update (DFU) class offers a solution. the USB_DFU bootloader requires only a PC and a USB cable. The RT series also provides this feature. In the case of the RT1170, for example, a DFU project is provided in the SDK under the USB class. The project is based on the MCUXpresso IDE. by running the dev_dfu_freertos_cm7 project in the SDK, the RT1170 will be enumerated as a dfu device, and after connecting it to the Host PC via another USB cable, the user can use the “dfu-util” utility to download a firmware to this device. Development Environment Software Environment: SDK Version: 2.15.000 IDE: MCUXpresso IDE Demo Project: dev_dfu_freertos_cm7 Host Software: dfu-util Download link: dfu-util For Windows 64-bit: Download dfu-util-0.9-win64.zip   Hardware Environment: Board: RT1170-EVKB   Preparing dfu-util dfu-util is used to download Firmware to a DFU device, but it does not add CRC32 to the Firmware. Since the DFU demo in the SDK verifies the CRC32 to ensure the Firmware written to Flash is free from bit errors, modifications to the dfu-util source code are necessary. Steps to Prepare dfu-util Install Dependencies sudo apt-get build-dep libusb-1.0-0 dfu-util sudo apt-get install gcc-mingw-w64-x86-64 Download dfu-util and libusb Source Code git clone https://git.code.sf.net/p/dfu-util/dfu-util git clone https://github.com/libusb/libusb.git Modify CRC Code in Source Modify the dfu_store_file function in dfu_file.c to add CRC32 to the Firmware suffix. /* write suffix, if any */ if (write_suffix) {     uint8_t dfusuffix[DFU_SUFFIX_LENGTH];     dfusuffix[0] = file->bcdDevice & 0xff;     dfusuffix[1] = file->bcdDevice >> 8;     dfusuffix[2] = file->idProduct & 0xff;     dfusuffix[3] = file->idProduct >> 8;     dfusuffix[4] = file->idVendor & 0xff;     dfusuffix[5] = file->idVendor >> 8;     dfusuffix[6] = file->bcdDFU & 0xff;     dfusuffix[7] = file->bcdDFU >> 8;     dfusuffix[8] = 'U';     dfusuffix[9] = 'F';     dfusuffix[10] = 'D';     dfusuffix[11] = DFU_SUFFIX_LENGTH;     /*crc = dfu_file_write_crc(f, crc, dfusuffix,     DFU_SUFFIX_LENGTH - 4);*/     dfusuffix[12] = crc;     dfusuffix[13] = crc >> 8;     dfusuffix[14] = crc >> 16;     dfusuffix[15] = crc >> 24;     crc = dfu_file_write_crc(f, crc, dfusuffix +     12, 4); }   Build libusb mkdir -p build cd libusb-1.0.24 ./autogen.sh PKG_CONFIG_PATH=$PWD/../build/lib/pkgconfig ./configure --host=x86_64-w64-mingw32 --prefix=$PWD/../build make make install cd .. Build dfu-util cd dfu-util-0.11 ./autogen.sh PKG_CONFIG_PATH=$PWD/../build/lib/pkgconfig ./configure --host=x86_64-w64-mingw32 --prefix=$PWD/../build make make install cd .. After these steps, the newly built tool will be located in the /build/bin folder. Open cmd for Windows. Run the following command with the new dfu-suffix.exe and CRC32 will be added to the Firmware. dfu-suffix.1 exe -a your_Firmware Running the Demo Using Prebuilt Firmware from SDK The SDK provides a prebuilt Firmware binary (dev_hid_mouse_bm.bin) that already includes CRC32. Follow these steps: Use MCUXpresso IDE to flash the dev_dfu_freertos_cm7 demo to the EVKB board.   Connect the board to the Host PC via USB. In the USB Device Descriptor, we find the Vendor ID and Product ID:   Run the following command to download the Firmware: dfu-util.exe -d <your_vid:pid> -D <your_Firmware> After downloading, the DFU demo will verify the CRC32 and execute the new Firmware in RAM. The device will be enumerated as a USB mouse, moving in a rectangular pattern on the screen. Using Custom Firmware When using custom Firmware, ensure that the image is loaded at the correct address (e.g., 0x10000). If the offset is incorrect, the DFU demo will fail to load the Firmware, even if the CRC check passes. To build and load custom Firmware: Import the hello_world_cm7 project into MCUXpresso IDE. In the Managed Linker Script settings, enable "Link application to RAM". Adjust memory settings to match the DFU project requirements, ensuring ITCM is the first RAM region. Build the project and generate a binary file. Use the modified dfu-util tool to append CRC32 to the binary and download it to the board. Verify that the custom Firmware executes correctly. CRC Added: New Firmware loaded successfully: For Chinese version and demo, please check this link:  https://www.nxpic.org.cn/module/forum/forum.php?mod=viewthread&tid=803149&fromuid=3253523 Hands-On Training

Adding a new Flash Device to Codewarrior 10.x Codewarior 10.x includes a pretty flexible flash programmer. Included with the standard install of the tool is a long list of common flash devices. However, if you're creating a new custom board, with a very new technology flash device it may be necessary to add a new device to the Codewarrior flash programmer. Documentation on exactly how to do this exists in the CW install at:         ..\CW PA v10.x\PA\PA_Tools\FlashToolKit\Documentation I've attached it for your convenience. Adding a flash device involves modifying a few XML configuration files within the CW install tree. There are really only a few different algorithms used for flash, so as long as the new device uses one of the existing ones (i.e. Intel or AMD) it's very straightforward, and the new XML file will be used just to describe the Manufacturer ID code and sector map. Flash configuration files are located in:      ..\CW PA v10.x\PA\bin\plugins\support\Products\ProductData\FPDevices.mwpdb\FP In this directory we see a list of currently supported flash devices (one XML file per device) In order to add a new device we need the following information from the device datasheet: Device Name Manufacturer ID code Device ID code Number of sectors Starting and ending address for each sector If the chip can be erased Options for data width Number of flash devices Algorithm (need to pick from one of the existing algorithms) As an example, I am going to show how to add a Micron / Numonyx PC28F00AP30BF flash device. According to the datasheet:     Manufacturer ID = 0x89      Sector Map shows 4 sectors of 16K words followed by 1023 sectors of 64K-words         ChipErase = yes      Algorithm looks like an intel based algorithm, which we can tell from table 7 of the Flash datasheet (I compare the method needed to program or erase a sector to one of the flash parts with an existing XML file) I create a new file named:       ..\CW PA v10.x\PA\bin\plugins\support\Products\ProductData\FPDevices.mwpdb\FP\PC28F00AP30BF.xml   0.1    PC28F00AP30BF    0x89    TRUE    4    0x8000    1023    0x20000 </SPAN></P><P style="padding-left: 90px;"><SPAN style="color: #0000ff;">#######################################################################</SPAN></P><P style="padding-left: 90px;"><SPAN style="color: #0000ff;">         64Mx16x1         0x8963         intel16x1j3.elf         FlashUtility.elf I then need to tell CW about the new file, so I modify the product manifest:      ..\CW PA v10.x\PA\bin\plugins\support\Products\ProductData\FPDevices.mwpdb\product-manifest.xml And add the following section at the end:                             PC28F00AP30BF                   0.1              FP/PC28F00AP30BF.xml            After saving the files, I open Codewarrior and within the flash programmer, I can now see that my new flash has been added. Qonverge

Android HW-Assisted Address Sanitizer for Memory Overflow checking Android HW-assisted Address Sanitizer for Memory Overflow checking     Hardware-assisted AddressSanitizer (HWASan) is a memory error detection tool.     HWASan is based on the memory tagging approach, where a small random tag value is associated both with pointers and with ranges of memory addresses. For a memory access to be valid, the pointer and memory tags have to match.     HWASan uses a lot less RAM compared to ASan, which makes it suitable for whole system sanitization. Here show an example: Use HWAsan for WiFi-HAL Memory Overflow issue hunting in Android-13.0.0_2.3.0_auto BSP.     Test environment:         SW:   Android-13.0.0_2.3.0_auto_car2, pre-built image.         HW:  88W9098 WiFi/BT EVK (PCIe) + i.MX8QXP EVK.     Run 88W9098 WiFi/BT on i.MX8QXP EVK, after ~2 hours, got memory leakage.     To locate root cause, enabled HWASan, re-build Android-13.0.0_2.3.0_auto BSP, run again, Got HWAddressSanitizer report: “heap-buffer-overflow”.          --Reason>  "Empty or null ScanResult list"  ->           --Then>      "Attempt to retrieve OsuProviders with invalid scanResult List" ->          --Result>    "heap-buffer-overflow"       HWASan help to locate root cause of Memory Overflow issue, on WiFi AP Scan code.       Attach file:            "Android_HW-assisted-Address-Sanitizer_for_memory-overflow_checking.pdf"

CodeWarrior 项目从零开始 - 第一部分 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何在 Codewarrior 中从头开始为 Freedom 板创建一个基本项目。 观看视频链接：1459 （在 “我的视频” 中查看） 回复：从零开始的 CodeWarrior 项目 - 第一部分 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 完整的视频教程可在以下网址找到： 《艾利之书 - 微控制器、机器人技术和曲速引擎》 。