i.MX31 PDK NAND Flashing RedBoot Flashing Kernel and Root File System using RedBoot Creating an image A kernel image and a root file system can be created using All Boards LTIB or compiling the kernel and setting the correct set of files. Create a root file system image from a set of files converting the files to a jffs2 file system. For this, install the package mtd-tools. In Ubuntu type apt-get install mtd-tools For making an root file system for flash, use the jffs2 file system like: mkfs.jffs2 -r rootfs/ -e 0x20000 -n -p -o rootfs.jffs2 Where rootfs/ is the original set of file for the file system and rootfs.jffs2 is the output image file. Flashing Some connections errors can be avoided by All Boards Configuring RedBoot. The process below uses TFTP to copy the files between host and target. See All Boards TFTP for detail in configurations. Copy the kernel image and the root file system image to the TFTP dir. For example, in  LTIB dir, type sudo cp ./rootfs/boot/zImage /tftpboot sudo cp rootfs.jffs2 /tftpboot/ Where /tftpboot is the dir configured for TFTP The next steps are performed in a Minicom session, and happens on the board. Formatting the flash: fis init Flashing kernel Load kernel image (zImage) using the command below. Remember to modify the host IP address: load -r -b 0x100000 /tftpboot/zImage -h 10.29.244.99 The address 0x100000 is used as a temporary location Create the kernel at the right address (0x200000, for IMX31PDK) fis create -f 0x200000 kernel Flashing root file system Load root file system image (rootfs.jffs2) to the temporary address. Remember to modify the host IP address: load -r -b 0x100000 /tftpboot/rootfs.jffs2 -h 10.29.244.99 Create the root file system in the right address (0x600000, for IMX31PDK. fis create -f 0x600000 root Testing You can now load your kernel in the flash by typing: fis load kernel To know if the root file system written in the flash was correctly saved, execute the NFS file system and mount the flash. For load the the root file system by NFS, type: exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/nfs nfsroot=10.29.244.99:/tftpboot/rootfs init=/linuxrc ip=10.29.241.6:10.29.244.99" Wait the system go up, then mount the flash at /mnt. Reminde that the flash has a jffs2 file system. mount -t jffs2 /dev/mtdblock2 /mnt ls /mnt List the /mnt contents. The output must be the right file system. Modifying the initial script Reset the board and press CTRL-C. Type fc to modify the configurations and insert the initialization script. RedBoot> fc Run script at boot: true Boot script: Enter script, terminate with empty line >> fis load kernel >> exec -c "noinitrd console=ttymxc0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2 ip=none" >> Boot script timeout (1000ms resolution): 1 Use BOOTP for network configuration: false Gateway IP address: 10.29.241.254 Local IP address: 10.29.241.6 Local IP address mask: 255.255.254.0 Default server IP address: 10.29.244.99 Board specifics: 0 Console baud rate: 115200 Set eth0 network hardware address [MAC]: false GDB connection port: 9000 Force console for special debug messages: false Network debug at boot time: false Update RedBoot non-volatile configuration - continue (y/n)? y ... Read from 0x07ee0000-0x07eff000 at 0x00080000: . ... Erase from 0x00080000-0x000a0000: . ... Program from 0x07ee0000-0x07f00000 at 0x00080000: . RedBoot> Remember to save the configuration in the flash by typing y Reset the system. To certify that the board is loading the system from flash, remove the ethernet cable.

NXP Tech Session - i.MX RT10xxを使用したリアルタイム産業用HMIシステムへのグラフィックスの実装 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ウェビナーの録画を見る <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ウェビナーの録画を見る i.MXRT 106倍

Right the First Time! EMC Compliance is Not Rocket Science, Thank You Ralph Morrison! As IC geometries continue to shrink and switching speeds increase, designing electromagnetic systems and printed circuit boards to meet the required signal integrity and EMC specifications has become even more challenging. A new design methodology is required. Specifically, the utilization of an electromagnetic physics-based design methodology to control the field energy in your design will be discussed. This training module will walk through the development process and provide you with guidelines for building successful, cost effective printed circuit boards. As IC geometries continue to shrink and switching speeds increase, designing electromagnetic systems and printed circuit boards to meet the required signal integrity and EMC specifications has become even more challenging. A new design methodology is required. Specifically, the utilization of an electromagnetic physics-based design methodology to control the field energy in your design will be discussed. This training module will walk through the development process and provide you with guidelines for building successful, cost effective printed circuit boards. Software & Tools Re: Right the First Time! EMC Compliance is Not Rocket Science, Thank You Ralph Morrison! Best app

车辆动力学与安全：汽车照明系统的功能安全及其对集成电路开发的影响 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 随着 LED 不断取代传统照明解决方案，渗透到汽车外部照明应用中，对更安全、高效、灵活和可扩展的电子设备和驱动器 IC 的需求也日益增长，以便在这些安全关键型应用中充分发挥 LED 的优势。本次会议将概述先进汽车照明系统对 ADAS 系统安全性的要求。这些系统要求还对 IC 规格产生影响，包括全系统诊断、跛行回家模式、热和 EMC 考虑。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 随着 LED 不断取代传统照明解决方案，渗透到汽车外部照明应用中，对更安全、高效、灵活和可扩展的电子设备和驱动器 IC 的需求也日益增长，以便在这些安全关键型应用中充分发挥 LED 的优势。本次会议将概述先进汽车照明系统对 ADAS 系统安全性的要求。这些系统要求还对 IC 规格产生影响，包括全系统诊断、跛行回家模式、热和 EMC 考虑。

Implement Your AI/ML Application at the Edge with NXP eIQ™ Machine Learning Software Development Environment The NXP® eIQ™ machine learning software development environment enables the use of ML algorithms on NXP microcontrollers and microprocessors. eIQ software includes inference engines, neural network compilers and optimized libraries. This software not only leverages open-source technologies, it is fully integrated into our MCUXpresso SDK and Yocto development environments, allowing you to develop complete system-level applications with ease. The NXP® eIQ™ machine learning software development environment enables the use of ML algorithms on NXP microcontrollers and microprocessors. eIQ software includes inference engines, neural network compilers and optimized libraries. This software not only leverages open-source technologies, it is fully integrated into our MCUXpresso SDK and Yocto development environments, allowing you to develop complete system-level applications with ease. Kinetis Cortex®-M Microcontrollers

动力总成和电气化：恩智浦GD3100先进隔离式高压栅极驱动器，助力电动动力总成 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> GD3100 是一款可编程高压栅极驱动器，具有先进的功能安全 (FuSa)、控制和保护功能，专为汽车和电动汽车应用而开发。本演讲将简要回顾 Si IGBT 和 WBG MOSFET 等高压功率器件。然后，演讲将重点介绍 GD3100 的关键特性，这些特性对于使用 Si IGBT 或 SiC MOSFET 实现高牵引逆变器、DC/DC 转换器或车载充电器 (OBC) 非常重要。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> GD3100 是一款可编程高压栅极驱动器，具有先进的功能安全 (FuSa)、控制和保护功能，专为汽车和电动汽车应用而开发。本演讲将简要回顾 Si IGBT 和 WBG MOSFET 等高压功率器件。然后，演讲将重点介绍 GD3100 的关键特性，这些特性对于使用 Si IGBT 或 SiC MOSFET 实现高牵引逆变器、DC/DC 转换器或车载充电器 (OBC) 非常重要。 电源管理

Vehicle Service-Oriented Gateway Opportunities and Enablement This session will introduce you to a new type of vehicle gateway called a Service-oriented Gateway that can support broad deployment of services to transform the automotive industry with new opportunities, and provide insights on how NXP can help you develop one. This session will introduce you to a new type of vehicle gateway called a Service-oriented Gateway that can support broad deployment of services to transform the automotive industry with new opportunities, and provide insights on how NXP can help you develop one. Interface & Connectivity

S12Z machine exception caused by ECC issue – address detection The S12Z devices contain unmaskable machine exception interrupt for severe system problems. The Memory Map Control module (MMC) generates this exception in the case of illegal memory access and uncorrectable ECC errors. The MMCECn register is set to a non-zero value if an S12ZCPU access violation or an uncorrectable ECC error has occurred. At the same time when this register is set to a non-zero value, access information is captured in the MMCPCn (program counter) and MMCCCRn (CCR U, X and I bits) registers. The MMCECn registers are cleared by writing the value 0xFFFF. Unfortunately, the exact address with corrupted data isn’t stored in any user-accessible register and this makes the debugging more difficult. In the case of reading memory with an uncorrectable ECC error, the MMC causes jump to the address in the Machine Exception vector as soon as the current instruction finishes execution. This may be used in workaround code for detection of the exact address with corrupted data. See attached example code. Note: The code detects only the first address of the phrase with uncorrectable corrupted data. The solution for detecting multiple ECC issues isn't included.   The execution of a machine exception code isn’t straightforward in this case. Please read the simplified procedure: The reading of uncorrectable corrupted data (double bit ECC error) will invoke machine exception. The ma_counter variable is incremented to 1. The MMCEC register is checked for detection of machine exception source. If ECC at EEPROM or P-Flash is detected as a machine exception source, the sequential reading of appropriate memory starts. Note: Since the P-FLASH is protected by 39-Bit ECC Scheme, we should read at leats single word(byte) from every aligned 32bit phrases. The global variable add contains a current reading address. When CPU read the uncorrectable corrupted data again, the MMC causes jump to the address in the Machine Exception vector again. The ma_counter variable is incremented to 2. When ma_counter is 2, we may store add variable address with corrupted data, clear ma_counter and clear pending flags in MMCEC register. Application project-specific user code for machine exception case may be applied (signalization, repair,…) Please be aware that no information is stored on the stack during entering machine exception handler (missing return address). So, default RTI instruction on end of routine cannot be used for returning to the application code. We must end the machine exception routine by MCU reset or jump to some known code entry point or by an endless loop.  This code is only a simple example code and does not cover all conditions. More details regarding simulating ECC issue at EEPROM and P-Flash: S12Z - Simulating ECC errors at EEPROM by cumulative write  https://community.nxp.com/docs/DOC-334327 

ARM用S32DS - サンプル一覧 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32 Design Studio の例のリストはここに移動されました。 https://community.nxp.com/docs/DOC-341380  S32K144 例: S32K_printf_implementation - S32DS  例: S32k144 FreeRTOS での UART printf/scanf - S32DS  例: S32K SDK - LPIT タイマーを使用して構成可能期間の関数呼び出し。  例:FlexNVMをコード/データフラッシュとして使用  例: EEEPROM の使用S32K144  例: EEEPROM の使用S32K144 - SDK なし  例: S32K144 .noinit セクションの使用  その他の例とハウツーについては、以下を参照してください。 S32K1xx ドキュメント &サンプルリスト

イネーブリング・テクノロジー: DDRの基礎 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、DDRデバイスの基本操作と内部メカニズムについて説明します。このクラスでは、DDRサブシステムの立ち上げと検証を可能にし、簡素化するためのツールについても説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、DDRデバイスの基本操作と内部メカニズムについて説明します。このクラスでは、DDRサブシステムの立ち上げと検証を可能にし、簡素化するためのツールについても説明します。

Tools & Enablement: BlueBox v2.0 のソフトウェアイネーブルメント: ADAS Enablement <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、BlueBox v2.0、別名「BlueBox Mini」または「BLBX2」に関するソフトウェアの有効化について詳しく説明します。レベル2/3の自動運転に適しています。エンジニアリングの観点からは、トピックには次のものが含まれます:1。BlueBox v2.0 ハードウェア レイアウト。2.ミドルウェアを使用したBSPコンテンツ。Linux configおよびUbuntu rootfs;それらの間のLinuxオプションとそれらの間の相互通信。ミドルウェアオプション (ROS バージョンなどを含む) についてのディスカッション。3. ADASのサポート方法4. AutonomouStuffでレベル2/3のADASを達成するために組み合わせます。5. Apolloバージョンの移植と計画モジュールのベンチマーク。6. ハードウェアサポートとシステムレベルの安全性とオーケストレーションを備えた将来の製品。7. このイネーブルメントの内部を説明する技術講義。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、BlueBox v2.0、別名「BlueBox Mini」または「BLBX2」に関するソフトウェアの有効化について詳しく説明します。レベル2/3の自動運転に適しています。エンジニアリングの観点からは、トピックには次のものが含まれます:1。BlueBox v2.0 ハードウェア レイアウト。2.ミドルウェアを使用したBSPコンテンツ。Linux configおよびUbuntu rootfs;それらの間のLinuxオプションとそれらの間の相互通信。ミドルウェアオプション (ROS バージョンなどを含む) についてのディスカッション。3. ADASのサポート方法4. AutonomouStuffでレベル2/3のADASを達成するために組み合わせます。5. Apolloバージョンの移植と計画モジュールのベンチマーク。6. ハードウェアサポートとシステムレベルの安全性とオーケストレーションを備えた将来の製品。7. このイネーブルメントの内部を説明する技術講義。

QN9080 PCB RF検証とMT8872を使用した非シグナリングテスト <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> お客様から、QN9080 を MT887x でテストできるかどうか尋ねられます。台湾アンリツと協力して、QN9080とMT887xを統合し、1M bps、2M bps、およびフレームエラーレートテストを実行します。このドキュメントでは、QN9080 のセットアップと MT887x c接続のセットアップについて説明します。1M bps、2M bps、およびフレームエラーレートの結果を示します。 アンリツの機器はMT8870に適用され、MT8872のモデル名です。 同じテスト環境を実行する場合。アンリツに問い合わせて、アンリツがリリースした最新の「オートテストツール」を入手し、SOPドキュメントに従って「オートテストツール」をPCにインストールして、このRF検証テストを実行することができます。 BLEソフトウェア QNの 日時:MT8872を使用した非シグナリングテストによるQN9080PCB RF検証 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> また、国際的な先進生産設備と良好な協力メーカーがあり、会社は片面myprepaidcenterの活性化を生産できます

Tools & Enablement: The Software Enablement of BlueBox v2.0: ADAS Enablement This session will go into the detail of the software enablement around the BlueBox v2.0, aka “BlueBox Mini” or “BLBX2”. Suited for level 2/3 autonomous drive. From an engineering perspective topics will include: 1. The BlueBox v2.0 hardware layout. 2. BSP content with middleware; Linux config and Ubuntu rootfs; Linux options between and inter-communication between them; Discussion of middleware options (including ROS versions, and others). 3. How ADAS is supported. 4. Combined to achieve level 2/3 ADAS with AutonomouStuff. 5. Apollo versions ported and benchmarking of the planning module. 6. Future offerings with hardware support and systems-level safety and orchestration. 7. Technical lecture explaining the internals of this enablement. This session will go into the detail of the software enablement around the BlueBox v2.0, aka “BlueBox Mini” or “BLBX2”. Suited for level 2/3 autonomous drive. From an engineering perspective topics will include: 1. The BlueBox v2.0 hardware layout. 2. BSP content with middleware; Linux config and Ubuntu rootfs; Linux options between and inter-communication between them; Discussion of middleware options (including ROS versions, and others). 3. How ADAS is supported. 4. Combined to achieve level 2/3 ADAS with AutonomouStuff. 5. Apollo versions ported and benchmarking of the planning module. 6. Future offerings with hardware support and systems-level safety and orchestration. 7. Technical lecture explaining the internals of this enablement.

车身电子：使用 S32K 的边缘节点 OTA 解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 加入此会议，了解边缘节点中的 AB 交换固件更新解决方案的概述，特别关注我们的 S32K1xx 微控制器系列。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 加入此会议，了解边缘节点中的 AB 交换固件更新解决方案的概述，特别关注我们的 S32K1xx 微控制器系列。 回复：车身电子：使用S32K的边缘节点OTA解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您能发布其中的演示代码吗？

EdgeLock ™ SE050：恩智浦新一代即插即用解决方案，确保物联网边缘安全 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 没有其他公司拥有如此广泛和多样化的嵌入式解决方案来应对物联网安全挑战。从安全元件 IC 到先进的多媒体和网络微处理器，恩智浦提供了保护终端或边缘节点整个生命周期所需的技术。此外，借助 Edgescale 云服务软件，可以从部署到退役对设备进行维护。加入此课程以了解 NXP 安全解决方案的概述。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 没有其他公司拥有如此广泛和多样化的嵌入式解决方案来应对物联网安全挑战。从安全元件 IC 到先进的多媒体和网络微处理器，恩智浦提供了保护终端或边缘节点整个生命周期所需的技术。此外，借助 Edgescale 云服务软件，可以从部署到退役对设备进行维护。加入此课程以了解 NXP 安全解决方案的概述。 软件和工具

セキュア・カー・アクセス:ハンズオン・ワークショップ:新しいNXP RFレシーバー(Lizard)とトランシーバー(MantraCS/F)とカー・アクセス・システム用のすぐに使えるファームウェア・スタック <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 当社のRF製品(Lizard、MantraCS、MantraF)のRCI(Remote Control Interface)についてご紹介します。システムの統合と開発は、RCIファームウェアとConfiguration Development Kit(CDK)を併用することで簡単に行えます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 当社のRF製品(Lizard、MantraCS、MantraF)のRCI(Remote Control Interface)についてご紹介します。システムの統合と開発は、RCIファームウェアとConfiguration Development Kit(CDK)を併用することで簡単に行えます。

Body Electronics: An OTA Solution for Edge Nodes Using S32K Join this session for an overview of the A-B swap firmware update solutions in edge nodes, specially focusing on our S32K1xx microcontroller family. Join this session for an overview of the A-B swap firmware update solutions in edge nodes, specially focusing on our S32K1xx microcontroller family. Re: Body Electronics: An OTA Solution for Edge Nodes Using S32K Could you please release the demo code in it?

安全汽车访问：实践研讨会：S32K 烹饪手册 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 与会者将获得有关 S32K Cookbook 应用说明示例的知识和经验，从而实现成功的客户设计。所有示例都会有一个概述，并且会进行一些练习。与会者必须携带笔记本电脑并预装 S32 Design Studio for Arm。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 与会者将获得有关 S32K Cookbook 应用说明示例的知识和经验，从而实现成功的客户设计。所有示例都会有一个概述，并且会进行一些练习。与会者必须携带笔记本电脑并预装 S32 Design Studio for Arm。

Secure Car Access: Hands-On Workshop: New NXP RF Receiver (Lizard) and Transceiver (MantraCS/F) with Ready to Use Firmware Stack for Car Access Systems Introduction on RCI (Remote Control Interface) for our RF products (Lizard, MantraCS, MantraF). System integration and development made easy using the RCI firmware together with the Configuration Development Kit (CDK). Introduction on RCI (Remote Control Interface) for our RF products (Lizard, MantraCS, MantraF). System integration and development made easy using the RCI firmware together with the Configuration Development Kit (CDK).

车载无线充电解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 由于无线充电的便利性、耐用性和汽车安装性，消费者对无线充电的接受度正在呈指数级增长。本次会议将提供车载无线充电设计的深入技术细节和指导。还回顾了涵盖低功率和中功率应用的 NFC/RFID 卡保护。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 由于无线充电的便利性、耐用性和汽车安装性，消费者对无线充电的接受度正在呈指数级增长。本次会议将提供车载无线充电设计的深入技术细节和指导。还回顾了涵盖低功率和中功率应用的 NFC/RFID 卡保护。