S32K358 SEMA42 demo 你好！我要使用 SEMA42 模块中的 Gate 寄存器，去写其 GTFSM 字段。需要在 mcal 中去进行使能 SEMA42 操作，目的为在使用的过程中保证对 GTFSM 字段可以正常写入与读取。请帮忙提供一份使用SEMA42的核间通信的demo给我，谢谢！

Battery Management System - SW & HW Environment Battery Management System Software and Hardware Environment 0 Table of Contents •Introduction •Software •Hardware •References •Conclusion 1 Introduction This article presents a comprehensive overview of the hardware and software components required to design and implement a high-voltage Battery Management System (BMS). It focuses on solutions based on NXP hardware platforms, combined with the integrated development ecosystems provided by NXP and MathWorks. The objective is to highlight how these technologies work together to streamline system development, deployment, and validation. 2 Software The software environment provides the modeling, simulation, communication, code generation, and deployment capabilities required by the Battery Management System. 2.1 Deep Learning Toolbox Deep Learning Toolbox brings artificial intelligence into the model-based workflow. It provides MATLAB functions, apps, and Simulink blocks for designing, training, simulating, and analyzing deep neural networks. This makes AI-based behavior easier to develop, understand, and validate before deployment. In the Battery Management System, deep learning can support battery state estimation, fault detection, and operating-condition classification. The toolbox can create and evaluate neural networks, import pretrained models from PyTorch, TensorFlow, and ONNX, and integrate trained networks into Simulink for system-level simulation. Artificial intelligence is not treated as a separate development activity. Neural network behavior can be simulated and verified together with the battery control model. Networks can also be optimized through quantization, projection, or pruning, and prepared for embedded deployment through automatic code generation. This reduces integration risk and makes AI-based BMS functions easier to validate within the complete system. For more information, see the Deep Learning Toolbox documentation in the References chapter. 2.2 Vehicle Network Toolbox Vehicle Network Toolbox brings CAN communication into the model-based workflow. It provides MATLAB functions and Simulink blocks for sending, receiving, encoding, and decoding CAN messages, making network behavior visible and testable before deployment. In the Battery Management System, commands, feedback, and status information are exchanged over CAN, linking the ECU with the surrounding vehicle architecture. The toolbox helps define signal interfaces, pack and unpack CAN messages, simulate bus traffic, and validate communication before target execution. Communication is not treated as a late integration step. CAN interaction can be simulated and verified together with the control model. This reduces integration risk and makes ECU behavior easier to validate end to end. For more information, see the Vehicle Network Toolbox documentation in the References chapter. 2.3 NXP Model-Based Design Toolbox for BMS The NXP Model-Based Design Toolbox for BMS extends the NXP Model-Based Design Toolbox for S32K3 with BMS support. It enables configuration and integration of the MC33775A, MC33774A, MC33772C, MC33665A, and MC33664. The S32K3 toolbox includes peripheral blocks that provide access to key microcontroller resources such as ADC, PWM, CAN, SPI, UART, timers, and interrupts. These interfaces facilitate communication between the S32K3 microcontroller and the supported BMS integrated circuits. Together, the toolboxes support the development and deployment of BMS applications on the S32K3 platform, leveraging the underlying S32K3 and BMS software stack. The workflow also integrates with NXP configuration tools and supports real-time monitoring and visualization through FreeMASTER, simplifying application development, validation, and debugging. 3 Hardware The central hardware platform is the 800 V Battery Management System Reference Design using ETPL. The kit contains: RD-K358BMU - Battery Management Unit RD33774CNTEVB - Cell Monitoring Unit RD772BJBTPL8EVB - Battery Junction Box BATT-18EMULATOR - 18-cell battery pack emulator 3.1 RD-K358BMU The RD-K358BMU is an NXP reference Battery Management Unit (BMU) designed for evaluation, development, and rapid prototyping of 800 V high-voltage Battery Management System (HVBMS) hardware and software. It provides a representative automotive-grade BMU platform built around the S32K358 microcontroller, enabling developers to evaluate battery-management architectures, safety concepts, communication interfaces, diagnostics, and control strategies in a realistic system environment. The board integrates several NXP components, including the S32K358, FS26, MC33665A, HB2000, TJA1145A, PCA2131, NBP8 and MC12XS6. Together, these components provide the processing, power management, communication, sensing, actuation, diagnostics, and safety capabilities required in a high-voltage BMS application. 3.2 Cell Monitoring Unit: MC33774A The RD33774CNT3EVB is a centralized Cell Monitoring Unit (CMU) reference design intended for the development and evaluation of 800 V high-voltage Battery Management System (HVBMS) applications. It uses Electrical Transport Protocol Link (ETPL) communication to connect with the broader BMS architecture and support reliable data exchange within the battery system. The board includes three MC33774 Analog Front End (AFE) devices arranged in a daisy-chain configuration. These AFEs are responsible for measuring and monitoring battery cell parameters, helping developers evaluate cell supervision, diagnostics, and communication strategies in a centralized BMS topology.   3.3 Battery Junction Box: MC33772C The RD772BJBTPL8EVB is a Battery Junction Box (BJB) reference design developed for 800 V high-voltage Battery Management System (HVBMS) applications. It leverages Electrical Transport Protocol Link (ETPL) communication to ensure robust and isolated data exchange within the battery system. The board features two MC33772C battery sensor ICs configured to deliver redundant measurements of voltage and current, improving diagnostic coverage and supporting functional safety requirements. It also performs isolation measurements, which are essential for monitoring insulation integrity and detecting potential fault conditions in high-voltage environments. 3.4 18-Cell Battery Pack Emulator The BATT-18EMULATOR board is designed to emulate a multi-cell battery pack and is easily interfaced with MC33774 battery cell controller evaluation boards. It enables quick evaluation of NXP Battery Cell Controller (BCC) ICs and supports software development by providing a controlled and flexible test environment. The board allows users to intuitively adjust the voltage of each of the 18 emulated cells, as well as the voltage levels on selected analog inputs typically used for temperature sensing. This capability makes it particularly useful for validating measurement accuracy, system behavior, and control algorithms without requiring a physical battery pack. Additionally, the BATT-18EMULATOR provides three independent outputs, allowing up to three BCC ICs to be connected simultaneously to a single emulator board. 4 References Deep Learning Toolbox Documentation Vehicle Network Toolbox Documentation NXP Model-Based Design Toolbox 800 V Battery Management System Reference Designs Using ETPL 5 Conclusion This article described the software and hardware environment required for the Battery Management System. The software combines MathWorks model-based design capabilities with NXP BMS and S32K3 platform support. The hardware integrates the S32K3 with NXP battery-cell controllers, communication interfaces, and associated BMS devices. Together, these elements provide the foundation for battery monitoring, communication, algorithm development, code generation, deployment, and validation. Next article: BMS architecture and model description, including the main software components, communication interfaces, data flow, and overall application structure.

First Steps with the Automotive MCU S32K – Development Environment Setup Guide: How to Install S32DS and RTD (Japanese Blog) What is this article about? NXP provides the S32 Design Studio ( S32DS) software development IDE environment for S32 microcontrollers and processors , as well as the Real-time Driver (RTD) software required to operate the MCU, free of charge. This article explains how to install the S32DS development environment and the RTD. * What is a Real-Time Driver ? This is NXP's proprietary driver set that integrates an " AUTOSAR- compliant MCAL(Microcontroller Abstraction Layer)" and a " non-AUTOSAR-compliant conventional SDK(Software Development Kit)" into a single unit. This time, we'll use the S32K3 , an automotive MCU that is versatile and has a wide range of options, as an example. S32DS is an environment that can be used with other NXP automotive MCUs as well. Overview of the S32K3 microcontroller's software First, let's get a rough understanding of the S32K3's software configuration . You don't need to understand the details at this point. This article will only cover a portion of the following: S32 Design Studio (S32DS) Real-Time Driver (RTD) What should I install? (Checklist) S32 Design Studio (※A common development environment for the S32 series) S32K3 Real-Time Drivers (RTD for S32K3) 1. Install S32 Design Studio S32 Design Studio is a free integrated development environment (IDE) that supports Power Architecture ® ( e200 core) and Arm ® -based automotive high-reliability microcontrollers /processors. S32DS IDE is a simple development tool with no code size limitations, based on open-source software such as Eclipse IDE , the GNU Compiler Collection (GCC) , and the GNU Debugger (GDB), and can be used for editing, compiling, and debugging designs. Download and install Download the IDE installer from the download site for S32 Design Studio for S32 Platform: ide/s32-design-studio-for-s32-platform:S32DS-S32PLATFORM" target="_blank" rel="noopener"> nxp.com Go to the S32DS download site and click the " Download " button. The page will scroll down, so please click " Download " below. Click on S32 Design Studio IDE. Click on the latest version, and if there are no issues, agree to the terms of service. There are versions for Linux and Windows, so please click the one that matches your operating system. Once the download is complete, launch the installer and follow the on-screen instructions to complete the installation. The process isn't particularly difficult, but if you're unsure, the following video provides detailed instructions, so please watch it while you proceed with the installation. Recommended ▶ gallerypage/video-id/6366101833112" target="_blank" rel="noopener">Video S32DS3.6_install_activation_use.mp4 - NXP Community 2. Install the S32K3 Real-Time Driver. Real-Time Drivers (RTDs) are a set of software components developed by NXP to accelerate the development of embedded applications running on S32 automotive MCUs . They provide a standardized, high-performance interface to hardware peripherals, enabling developers to create reliable and scalable automotive software systems.   Download and install Go to the download site for RTD xp.jp/design/design-center/software/automotive-software-and-tools/real-time-drivers-rtd:AUTOMOTIVE-RTD" target="_blank" rel="noopener"> and click the " Download " button. The page will scroll down, so please click the " Download " button for the S32K3 Standard Software below. Please note that this Standard Software is free software and tools available for use. This time, we'll select an RTD for the S32K3. Click on the one that says“ Qualified as RFP Release” (RFP = Release For Production). I agree to the terms of service and will proceed. Next, click on the Updatesite for S32 Design Studio and download it . spoiler (Highlight for reading) * What is Updatesite? Simply downloading the RTD file doesn't mean you can use it with S32DS; you only have the "zip package" on hand. Only by installing the downloaded Update Site ( ..._DesignStudio_updatesite.zip ) into S32DS will the RTD be registered in the IDE. This allows you to select the RTD in the new project wizard and automatically generate the RTD code using "Update Code" based on the settings configured in the S32 Configuration Tool . *If you do not add this, RTD will not appear as an option when creating a new project. *Note that if the RTD is already bundled with the S32DS version, this procedure is unnecessary and you can use it as is. *What is Updatesite? Even after downloading RTD, you only have the "zip package" on hand and cannot use it with S32DS. Only by installing the downloaded Update Site (..._DesignStudio_updatesite.zip) into S32DS will RTD be registered in the IDE, allowing you to select RTD in the new project wizard and automatically generate RTD code using "Update Code" based on settings configured in the S32 Configuration Tool. *Without this, RTD will not appear as an option when creating a new project. *Note that this step is unnecessary for versions of S32DS that already bundle RTD and can be used immediately.   Open the Real-Time Driver on the S32DS and install RTD. Now let's actually open S32DS. Once you open S32DS, click on " S32DS Extension and Updates ". Verify that the S32K3 Development Package is installed. Click " Add Updates Site " in the bottom right corner and add the Real-time Driver you downloaded earlier. Once the addition is complete, the Real-Time Driver will appear on the left side. This time, click on "S32K3XX Real-Time Driver…" to start the installation. If you look at the bottom right, you can confirm that the installation has started. As the installation progresses, you will be prompted to restart the S32DS, so follow the instructions. After restarting, the RTD installation is complete! If you open " S32DS Project From Example " in the lower left, you can see the S32K3XX Real-Time Driver that you just installed . The following video also provides detailed instructions, so please try installing while watching the video. Recommended ▶ S32 Design Studio 3.6: How to Download RTD | NXP Semiconductors At this point, the installation of the S32 Design Studio IDE and the S32K3 Real-Time Driver is complete. Great job! In the next article, we will actually run the drivers and sample applications included in the RTD. =========================​ We are currently unable to respond to comments left in the " Comment " section of this post . We apologize for the inconvenience, but when making an inquiry, please refer to " 8 %E3% 81 %AE% E6 %8A% 80 %E8% A1 %93% E8 %B3% AA %E5% 95 %8F-% E5 %95% 8F %E3% 81 %84% E5 %90% 88 %E3% 82 %8F% E3 %81% 9B %E6% %B9% %B3% E6 %E6% 97 %A5% E6 %9C% AC %E8% AA %9E% E3 %83% 96 %E3% 83 %AD% E3 %82% B0/ba-p/2153299" target="_blank" rel="noopener" data-hyperlinktype="0" > How to ask technical questions to NXP ( Japanese blog ) " . (If you are already an NXP distributor or have a relationship with NXP , you may ask your representative directly. ) This article provides a detailed explanation of how to install the S32 Design Studio (S32DS) development environment and the Real-Time Driver for NXP automotive MCUs, in a level of detail that even those new to S32K can easily follow. This example uses the S32K3 automotive MCU, but the same procedure can be used to set up the environment for other automotive MCUs. (Working time: 20 minutes) General Purpose Microcontrollers S32 Design Studio S32K SW | Downloads Japanese Blog

让我们使用 S32K – RTD（首款车规级 MCU）运行一个 LED 闪烁应用程序（日本博客） 这篇文章是关于什么的？ 在上一篇文章中，我们安装了S32 设计工作室（以下简称S32DS ）和实时驱动程序（以下简称RTD），以执行使用 S32 MCU 进行评估和开发所需的必要准备步骤。 汽车级MCU S32K入门指南——开发环境搭建指南：安装S32DS和RTD（日语博客） 这一次，我们将迈出下一步，实际打开一个 RTD 示例项目，并通过生成代码、构建和调试来体验 S32K3 开发的“第一步” 。 本文目标：调试 S32K3 FRDM 板上的 RTD 示例 ， 并使 LED 闪烁（预计时间：15 分钟） 准备 硬件： FRDM-A-S32K344 USB Type-C 数据线（※FRDM-A-S32K344 随附） 在本文中， 我们将使用 FRDM Automotive 的 新型 开发板 FRDM-A-S32K344 ，该开发板采用 S32K3 微控制器。S32K344 是 一款 1x LockStep Arm Cortex-M7 微控制器， 广泛应用于 电机控制 和车身控制 等领域。 软件： S32DS（IDE 开发环境） RTD（S32K3软件） 请事先确保已安装上一篇文章中介绍的 S32DS和RTD 。 步骤 1：打开 RTD 样品 启动 S32DS 并创建一个新项目。然后，按照以下步骤打开 RTD 示例。 打开左下角的“ S32DS 项目示例”，然后点击“ S32K3XX 实时驱动程序… ”查看ADC 、 CAN 、 GPT 、 I2C 、 PWM 等示例。 这次，我们以“ Dio 示例”为例。 点击“Dio 示例”，然后 选择“ Dio_Example_S32K344 ”。 示例的详细信息会显示在右侧，请检查内容并 点击“完成”。 在左侧的“项目资源管理器”中导航到 main.c ，然后单击打开源代码。 您会在右下角和代码中看到几个“警告”，但这些警告并不表示源代码本身存在错误，而是表示S32DS没有正确找到与 RTD 相关的头文件。 步骤 2：解决警告 要解决此警告，请先单击屏幕左侧项目资源管理器中的“example_Dio.mex” 。 “example_Dio.mex”是一个存储MCU设置（例如，DIO = 数字I/O）、引脚/时钟/外设设置和代码生成设置的文件。 配置工具界面将会出现。点击顶部中央的“更新代码”按钮，即可更新代码并解决错误。更新完成后，右下角“问题”部分中的警告信息将会消失。   步骤 3：构建 点击下方按钮返回上一屏幕。 在项目资源管理器的“生成”部分，您可以查看每个软件及其各自的标题。 最后，点击屏幕左上角的构建按钮。屏幕右下角应该会显示“构建完成”的消息，确认没有错误后，就表示之前提到的警告问题已经解决。 到目前为止，我们已经确认可以打开 RTD 示例项目，从 .mex 文件生成代码，并成功完成构建。 第四步：调试 使用随附的USB Type-C 数据线将 FRDM-A-S32K344 连接到您的电脑。连接成功后，板上的 LED 指示灯将亮起。   返回 S32DS 屏幕，点击屏幕顶部中央的调试图标（虫子图标）开始调试。点击后，屏幕上会显示一条消息，提示您启动 PE Micro 调试器，请允许其启动，并按照屏幕上的说明进行调试。 PE Micro是一款用于调试的调试驱动程序（工具）。S32DS使用名为 PE Micro的调试器将开发板连接到PC。 在当前环境下， S32DS （ IDE ）➡ PE Micro（调试工具） ➡ FRDM-A-S32K344 这是我们沟通的渠道。 调试后，如果控制台中出现“目标已复位”和“ DAP 已成功上电”等日志，并且调试视图中显示线程信息（线程 #1），则表示与目标板的连接和程序传输已成功完成。   步骤五：点亮LED灯 现在，让我们在 FRDM-A-S32K344 板上实际检查一下。 点击屏幕中央工具栏中的播放图标 ▶ “恢复/运行” 以开始执行程序。 请注意，每个示例程序都在 main() 函数的开头设置了一个断点，以便于调试。 如果您能确认 LED 灯 亮起 几秒钟 （下图黄色圆圈中的 LED 灯），则此调试成功。 在这个示例代码中， 我们被指示“ while (count++ < 10) ”。 初始计数为0 每次循环迭代，计数都会增加count++。 仅当计数小于 10 时才有效 换句话说，LED 最多亮 10次才能完成操作，所以LED 只亮几秒钟然后停止是正常的。 到目前为止，我们已经体验了从构建和调试 RTD 示例项目到验证其在实际电路板上的运行（打开和关闭 LED）的整个过程。 最后 这一系列步骤代表了使用 S32K3 的基本开发步骤。 代码生成 → 构建 → 调试 → 测试功能 通过在电路板上实际观察其运行情况，你就能更直观地了解软件如何控制硬件。 根据这些基本步骤，尝试开发你自己的应用程序。 =========================​ 我们目前无法 回复 此帖子“ 评论”部分留下的评论。 对于由此造成的不便，我们深表歉意，但 在进行咨询时， 请 参考“ NXP 技术问题 - 如何联系我们 （ 日语博客 ） ” 。 （如果您已经是 恩智浦的 分销商或 与 恩智浦 有合作关系 ，您可以直接咨询您的代表。） 在本文中，我们将使用 S32K3 实时驱动程序中的一个 LED 闪烁示例项目，通过生成、构建和调试代码来体验 S32K3 开发的“第一步”。 本文目标：调试S32K3 FRDM 板上的RTD示例并使其 LED闪烁。 （预计时间：15分钟） 通用微控制器 S32设计工作室 S32K SW | 下载 日本博客

Let's run an LED blinking application using the S32K – RTD, the first automotive-grade MCU (Japanese blog) What is this article about? In the previous article, we installed S32 Design Studio (hereinafter S32DS ) and Real-Time Driver (hereinafter RTD) to perform the necessary preliminary steps for evaluating and developing with the S32 MCU. First Steps with the Automotive MCU S32K – Development Environment Setup Guide: Installing S32DS and RTD (Japanese Blog) This time, as the next step, we will actually open an RTD sample project and experience the " first step " of S32K3 development by generating code, building, and debugging . Goal of this article: Debug a sample from RTD on an S32K3 FRDM board and make an LED blink (estimated time: 15 minutes) Preparation Hardware: FRDM-A-S32K344 USB Type-C cable (※Included with FRDM-A-S32K344) In this article, we will be using the new FRDM Automotive board, the FRDM-A-S32K344 , which uses the S32K3. The S32K344 is a 1x LockStep Arm Cortex-M7 microcontroller and is used in a wide range of applications, including motor control and body control . software: S32DS (IDE development environment) RTD (Software for S32K3) Beforehand, please make sure that S32DS and RTD, which were introduced in the previous article , are installed. Step 1: Open the RTD sample Launch S32DS and create a new project. Then, follow these steps to open the RTD sample. Open " S32DS Project from Example " in the lower left corner, and click " S32K3XX Real-Time Drivers… " to see examples of ADC , CAN , GPT , I2C , PWM, etc. This time, let's use " Dio Example " as an example. Click on "Dio Example," and then select " Dio_Example_S32K344 " from there. The details of the example are displayed on the right, so check the contents and click "Finish." Navigate to main.c in the "Project Explorer" on the left and click to open the source code. You will see several "Warnings" in the bottom right and on the code, but these warnings do not indicate errors in the source code itself, but rather that S32DS is not correctly finding where to look for RTD-related header files. Step 2: Resolving the Warning To resolve the warning, first click on "example_Dio.mex" in the Project Explorer on the left side of the screen. "example_Dio.mex" is a file that stores MCU settings (e.g., DIO = Digital I/O), Pins/Clock/Peripheral settings, and code generation settings. The Configuration Tool screen will appear. Click "Update Code" at the top center to update the code and resolve the error. Once the update is complete, the warning message will disappear from the "Problem" section at the bottom right.   Step 3: Build Click the button below to return to the previous screen. In the " generate " section of Project Explorer, you can view each software and its respective headers. Finally, click the build button in the upper left corner of the screen. You should also see a "Build Finished" message in the lower right corner of the screen, and confirm that there are no errors, which means the warning mentioned earlier has been resolved. Up to this point, we have confirmed that we can open the RTD sample project, generate code from the .mex file, and complete the build successfully. Step 4: Debugging Connect the FRDM-A-S32K344 to your PC using the included USB Type-C cable . The LED on the board will light up when the connection is successful.   Return to the S32DS screen and click the debug icon (bug logo) at the top center of the screen to start debugging. After clicking, a message will appear asking you to launch the PE Micro debugger, so allow it to launch and follow the on-screen instructions to proceed with debugging. PE Micro is a debug driver (tool) used by the S32DS to connect the board to the PC. In the current environment, S32DS ( IDE ) ➡ PE Micro ( Debugging Tool ) ➡ FRDM-A-S32K344 This is the route through which we are communicating. After debugging, if logs such as " Target has been RESET " and " DAP successfully powered up " appear in the Console, and thread information ( Thread #1 ) is displayed in the Debug view, then the connection to the target board and program transfer have been completed successfully.   Step 5: Light up the LED Now, let's actually check it on the FRDM-A-S32K344 board. Click the play icon ▶ “Resume/Run” in the toolbar in the center of the screen to start the program execution. Please note that each sample program has a breakpoint placed at the beginning of the main() function to facilitate debugging. If you can confirm that the LED lights up for a few seconds (the LED circled in yellow in the diagram below), then this debugging was successful. In this example code, we are instructed to " while (count++ < 10) ". Start with count = 0 The count increases by count++ with each loop iteration. It only works while count < 10 In other words, the LED lights up a maximum of 10 times to complete the operation, so it's normal for the LED to light up for only a few seconds and then stop . Up to this point, we have been able to experience the entire process from building and debugging the RTD sample project to verifying its operation on the actual board ( turning the LEDs on and off). Finally This series of steps represents the basic development steps using the S32K3. Code generation → Build → Debug → Test functionality By actually seeing it in action on the board, you were able to gain a more intuitive understanding of how software controls hardware. Based on these basic steps, try developing your own application. =========================​ We are currently unable to respond to comments left in the " Comment " section of this post . We apologize for the inconvenience, but please refer to " Technical Questions to NXP - How to Contact Us( Japanese Blog) " when making inquiries.(If you are already an NXP distributor or have a relationship with NXP, you may ask your representative directly.) In this article, we will use a sample LED blinking project within the S32K3 Real-Time Driver to experience the " first steps " of S32K3 development by generating, building, and debugging code. Goal of this article: Debug a sample in RTD on an S32K3 FRDM board and blink an LED. (Estimated time: 15 minutes) General Purpose Microcontrollers S32 Design Studio S32K SW | Downloads Japanese Blog

初めての車載向けMCU S32K – RTDを使用してLED点滅のアプリケーションを動かしてみよう (日本語ブログ) この記事は？ 前回の記事では、S32 Design Studio（以下S32DS）とReal-Time Driver（以下RTD）のインストールを行い、S32 MCUの評価、開発に必要な下準備を行いました。 初めての車載向けMCU S32K – 開発環境構築ガイド：S32DSとRTDのインストール（日本語ブログ） 今回はその次のステップとして、実際にRTDのサンプルプロジェクトを開き、コード生成、ビルド、デバッグを行うことで、S32K3開発の「最初の一歩」を体験してみます。 この記事のゴール：S32K3 FRDMボード上でRTD内のサンプルをデバッグし、LEDを点滅させる （所要時間：15分） 事前準備 ハードウェア： FRDM-A-S32K344 USB Type-Cケーブル (※FRDM-A-S32K344に付属しています。) 今回の記事では、S32K3の新しいFRDM Automotiveボード、FRDM-A-S32K344を使います。S32K344は、１ｘLockStep Arm Cortex-M7 マイクロコントローラで、モーター制御、ボディ制御等、幅広いアプリケーションで採用されています。 ソフトウェア： S32DS (IDE開発環境) RTD (S32K3用ソフトウェア) 事前に、前回の記事、で紹介したS32DSとRTDがインストールされていることを確認してください。 ステップ１：RTDサンプルを開く S32DSを起動し、新しいプロジェクトを作成しましょう。その後、以下の手順に沿って、RTDサンプルを開きます。 左下の「S32DS Project from Example」を開き、「S32K3XX Real-Time Drivers…」をクリックすると、ADC、CAN、GPT、I2C、PWM…etc.等のサンプルが確認できます。 今回は、例として「Dio Example」を使ってみましょう。「Dio Example」をクリックし、その中からさらに「Dio_Example_S32K344」を選択。右側に、Exampleの詳細が記載されているため、中身を確認し、「Finish」をクリック。 左の「Project Explorer」でmain.cへと移動し、クリックすると、ソースコードを開くことができる。 右下およびコード上にいくつかの「Warning」が表示されますが、この警告は、ソースコードそのもののミスではなく、S32DSがRTD関連のヘッダファイルを探す場所を正しく見つけられていない場合に表示されます。 ステップ２：Warningの解消 Warningを解消するために、まずは画面左のProject Explorerから、「example_Dio.mex」をクリックします。「example_Dio.mex」は、MCUの設定（例：DIO = Digital I/O）、Pins / Clock / Peripheral設定、コード生成設定情報を保存しているファイルです。 Configuration Toolの画面が表示されるので、中央上の「Update Code」をクリックし、エラーを解消するためにコードを更新します。アップデートが完了すると、右下の「Problem」セクションからWarningメッセージが消えます。   ステップ３：ビルド 以下のボタンをクリックし、元の画面に戻ります。 Project Explorerの「generate」のセクションで、各ソフトウェアとそれぞれのヘッダーを確認することができます。 最後に、画面左上のビルドボタンをクリックします。画面右下に「Build Finished」のコメントともにエラーが無いことも確認できるので、先ほどのWarningも解消されたことが確認できます。 ここまでで、RTDサンプルプロジェクトを開き、.mexファイルからコードを生成し、ビルドが正常に完了するところまで確認できました。 ステップ４：デバッグ FRDM-A-S32K344を付属のUSB Type-Cケーブルを使って、お使いのPCにつないでください。正常につながると、ボード上のLEDが光った状態になります。   S32DSの画面に戻り、画面中央上のデバッグアイコン（虫のロゴ）をクリックし、デバッグを開始しましょう。クリックすると、デバッガのPE Microを起動させるメッセージが出てくるので、起動を許可し、画面の指示に沿ってデバッグを進めてください。 PE Micro は、デバッグ用の接続ドライバ（ツール）で、S32DSがPCとボードをつなぐために、PE Microというデバッガを使っています。 現在の環境では、 S32DS（IDE）➡ PE Micro(デバッグツール) ➡ FRDM-A-S32K344 という経路で通信しています。 そして、デバッグ実行後、Consoleに「Target has been RESET」「DAP successfully powered up」などのログが表示され、さらにDebugビューにスレッド情報（Thread #1）が表示されていれば、ターゲットボードへの接続およびプログラム転送は正常に完了しています。   ステップ５：LEDを光らせる では、実際にFRDM-A-S32K344ボード上で確認しましょう。 画面中央のツールバーにある再生マーク ▶ “Resume/Run”をクリックすると、プログラム実行がスタートします。 尚、各サンプルプログラムはデバッグを行いやすいように、main()の先頭にブレイクポイントを貼っています。 「数秒だけLEDが光る」（下図の黄色で囲ったLED）動作が確認できれば、今回のデバッグは成功です。 今回のDim Exampleのコードでは、“while (count++ < 10)”と指示されており、 count = 0 でスタート ループ1回ごとに count++ で増える count < 10 の間だけ動く つまり、最大10回LEDが光って動作が完了する、という中身になっているため、LEDが数秒だけ動作して止まるのが正常な挙動です。 ここまでで、RTDサンプルプロジェクトのビルドからデバッグ、そして実機ボード上での動作確認（LEDの点灯・消灯）までを一通り体験することができました。 さいごに 今回の一連の流れは、S32K3を用いた開発の基本ステップとなります。 コード生成 → ビルド → デバッグ → 動作確認 実際にボード上で動作を確認することで、ソフトウェアがハードウェアを制御していることをより直感的に理解できたのではないでしょうか。 この基本ステップをベースに、ご自身のアプリケーション開発へと発展させてみてください。 =========================​ 本投稿の「Comment」欄にコメントをいただいても、現在返信に対応しておりません。​ お手数をおかけしますが、お問い合わせの際には「NXPへの技術質問 - 問い合わせ方法 (日本語ブログ)」をご参照ください。​ （既に弊社NXP代理店、もしくはNXPとお付き合いのある方は、直接担当者へご質問いただいてもかまいません。） 今回の記事では、S32K3 Real-Time Driver内のLED点滅のサンプルプロジェクトを用いて、コード生成、ビルド、デバッグを行うことで、S32K3開発の「最初の一歩」を体験します。 この記事のゴール：S32K3 FRDMボード上でRTD内のサンプルをデバッグし、LEDを点滅させる （所要時間：15分） General Purpose Microcontrollers S32 Design Studio S32K SW | Downloads 日本語ブログ

汽车级MCU S32K入门指南——开发环境搭建指南：如何安装S32DS和RTD（日语博客） 这篇文章是关于什么的？ 恩智浦 半导体 (NXP) 为 S32 微控制器和 处理器 免费 提供 S32 设计 工作室 ( S32DS) 软件开发集成开发环境 (IDE)，以及 运行 MCU 所需的 实时驱动程序 (RTD) 软件。本文将介绍如何安装 S32DS 开发环境和 RTD。 什么是 实时驱动程序 ？ 这是 NXP 的 专有驱动程序集 ，它将“ 符合 AUTOSAR 标准的 MCAL （微控制器抽象层）”和“ 不符合 AUTOSAR 标准的常规 SDK （软件开发工具包）” 集成到一个单元中 。 这次，我们将以功能全面、选项丰富的 汽车级 MCU S32K3 为例进行说明。S32DS 环境也可以与 NXP的其他汽车级 MCU配合使用。 S32K3微控制器软件概述 首先，让我们大致了解一下S32K3的软件配置。 你现在不需要了解细节。 本文仅涵盖以下内容的一部分： S32 设计工作室 (S32DS) 实时驾驶员 (RTD) 我应该安装哪些软件？（清单） S32 设计工作室（※S32 系列的通用开发环境） S32K3 实时驱动程序（S32K3 的 RTD） 1.安装S32 设计工作室 S32 Design Studio是一个免费的集成开发环境 (IDE)，支持基于 Power Architecture ® ( e200内核) 和Arm ®的汽车高可靠性微控制器/处理器。 S32DS IDE 是一款简单的开发工具，没有代码大小限制，它基于 Eclipse IDE 、 GNU编译器集合(GCC)和GNU调试器(GDB) 等开源软件，可用于编辑、编译和调试设计。 下载并安装 从下载站点下载适用于 S32 平台的 S32 Design Studio IDE安装程序：ide/s32-design-studio-for-s32-platform:S32DS-S32PLATFORM" target="_blank" rel="noopener"> nxp.com 前往 S32DS 下载网站，然后点击“下载”按钮。 页面会向下滚动，请点击下面的“下载”按钮。 点击 S32 设计工作室 IDE。 点击最新版本，如果没有问题，请同意服务条款。 有Linux 和Windows 版本，请点击与您的操作系统匹配的版本。 下载完成后，启动安装程序，并按照屏幕上的说明完成安装。 这个过程并不特别难，但如果您不确定，以下视频提供了详细的说明，请在安装过程中观看。 推荐▶ gallerypage/video-id/6366101833112" target="_blank" rel="noopener">视频 S32DS3.6_install_activation_use.mp4 - NXP 社区 2.安装S32K3 实时驱动程序。 实时驱动程序 (RTD) 是恩智浦半导体开发的一组软件组件，旨在加速在 S32 汽车 MCU 上运行的嵌入式应用程序的开发。它们为硬件外设提供标准化的高性能接口，使开发人员能够创建可靠且可扩展的汽车软件系统。   下载并安装 前往RTD的下载站点xp.jp/design/design-center/software/automotive-software-and-tools/real-time-drivers-rtd:AUTOMOTIVE-RTD" target="_blank" rel="noopener"> 并点击“下载”按钮。 页面将向下滚动，请点击下方“ 下载”按钮 下载 S32K3 标准软件。 请注意，此标准软件为免费软件和工具。 这次，我们将为 S32K3 选择 RTD。 点击标有“符合 RFP 发布条件”的选项（RFP =发布用于生产）。 我同意服务条款，并将继续操作。 接下来，点击 S32 Design Studio的更新站点并下载。 剧透 （高亮显示以便阅读） Updatesite是什么？ 仅仅下载 RTD 文件并不意味着您可以将其与 S32DS 一起使用；您手中只有“zip 压缩包”。只有将下载的更新站点 ( ..._DesignStudio_updatesite.zip ) 安装到 S32DS 中，RTD 才能在 IDE 中注册。这样，您就可以在新建项目向导中选择 RTD ，并根据 S32 配置工具中配置的设置，使用“更新代码”自动生成 RTD 代码。 *如果不添加此项，创建新项目时 RTD 将不会显示为选项。 *请注意，如果 RTD 已与 S32DS 版本捆绑在一起，则此步骤是不必要的，您可以直接使用它。 Updatesite是什么？ 即使下载了 RTD，您也只能获得“zip 压缩包”，而无法将其与 S32DS 一起使用。只有将下载的更新站点 (..._DesignStudio_updatesite.zip) 安装到 S32DS 中，RTD 才能在 IDE 中注册，从而允许您在新建项目向导中选择 RTD，并根据 S32 配置工具中配置的设置，使用“更新代码”自动生成 RTD 代码。*否则，创建新项目时将不会显示 RTD 选项。*请注意，对于已捆绑 RTD 并可直接使用的 S32DS 版本，此步骤是不必要的。   在 S32DS上打开实时驱动程序并安装 RTD。 现在让我们打开 S32DS。 打开 S32DS 后 ， 点击“ S32DS 扩展和更新”。 确认已安装 S32K3 开发包。 点击右下角的“添加更新站点”，然后添加您之前下载的实时驱动程序。 添加完成后，实时驱动程序将显示在左侧。这次，点击“S32K3XX 实时驱动程序…”开始安装。 查看右下角，即可确认安装已开始。安装过程中，系统会提示您重启 S32DS，请按照提示操作。 重启后，RTD安装完成！ 如果您在左下角打开“ S32DS 项目示例”，您可以看到您刚刚安装的S32K3XX 实时驱动程序。 以下视频也提供了详细的安装说明，请边观看视频边尝试安装。 推荐▶ S32 设计工作室 3.6：如何下载 RTD | 恩智浦半导体 至此，S32 设计工作室 IDE和S32K3实时驱动程序的安装已完成。干得好！ 下一篇文章中，我们将实际运行 RTD 中包含的驱动程序和示例应用程序。 =========================​ 我们目前无法回复此帖子“评论”部分留下的评论。 由此给您带来的不便，我们深表歉意。如有任何疑问，请参考“ 8 %E3% 81 %AE% E6 %8A% 80 %E8% A1 %93% E8 %B3% AA %E5% 95 %8F-% E5 %95% 8F %E3% 81 %84% E5 %90% 88 %E3% 82 %8F% E3 %81% %E6% %B9% %B3% E6 %E6% 97 %A5% E6 %9C% AC %E8% AA %9E% E3 %83% 96 %E3% 83 %AD% E3 %82% B0/ba-p/2153299” target="_blank" rel="noopener" data-hyperlinktype="0" >如何向NXP提出技术问题（日语博客） ” ） “ 。 （如果您已经是恩智浦的分销商或与恩智浦有合作关系，您可以直接咨询您的代表。 ） 本文详细介绍 了如何安装 S32 设计工作室 (S32DS) 开发环境和 NXP 汽车 MCU 的实时驱动程序 ， 即使是 S32K 新手 也能轻松理解。 本示例使用 S32K3 汽车 MCU，但相同的步骤也可用于设置其他汽车 MCU 的环境。 （操作时间：20分钟） 通用微控制器 S32设计工作室 S32K SW | 下载 日本博客

初めての車載向けMCU S32K – 開発環境構築ガイド：S32DSとRTDのインストール方法（日本語ブログ） この記事は？ NXPでは、S32 マイコン・プロセッサ用ソフトウェア開発IDE環境「S32 Design Studio (S32DS)」と、MCUを動かすために必要なソフトウェア*Real-time Driver(RTD)を無料で提供されています。この記事では、開発環境S32DSとRTDのインストール方法について解説します。 *Real-Time Driverとは？ 「AUTOSAR準拠のMCAL（マイコン抽象化レイヤ）」と「AUTOSAR非準拠の従来のSDK（ソフトウェア開発キット）」を1つに統合したNXP独自のドライバセットです。 今回は、汎用的かつラインナップも豊富なS32K3という車載MCUを例にします。S32DSは、他のNXP車載MCUでも使用できる環境です。 S32K3マイコン の Software 全体像 最初に、S32K3 のソフトウェア構成を “ざっくり” 把握しておきましょう。  この時点で細かい理解は必要ありません。 本記事で扱う範囲は、以下の一部だけです。 S32 Design Studio (S32DS) Real-Time Driver (RTD) 何をインストールすればいい？（チェックリスト） S32 Design Studio (※S32シリーズで共通の開発環境) S32K3 Real-Time Drivers (※S32K3向けRTD) １．S32 Design Studioをインストール S32 Design Studioは、Power Architecture®（e200コア）およびArm®ベースの車載向け高信頼性マイクロコントローラ/プロセッサに対応する統合開発環境(IDE)であり、無償で提供されています。 S32DS IDEは、Eclipse IDE、GNUコンパイラ・コレクション (GCC)、GNU デバッガ (GDB) などのオープンソース・ソフトウェアをベースにした、コード・サイズに制限のないシンプルな開発ツールであり、設計の編集、コンパイル、デバッグに利用できます。 ダウンロードとインストール IDEのインストーラをide/s32-design-studio-for-s32-platform:S32DS-S32PLATFORM" target="_blank" rel="noopener">S32 Design Studio for S32 Platformのダウンロードサイトからダウンロードします。このダウンロードにはnxp.com S32DS のダウンロードサイトへ行き、「ダウンロード」ボタンを押します。 ページがスクロールされるので、以下の「ダウンロード」を押します。 S32 Design Studio IDEをクリックします。 最新バージョンをクリックし、問題がなければ利用規約に同意します。 Linux用とWindows用があるので、ご自身のOSに応じてクリックください。 ダウンロードが完了したら、インストーラーを起動し、表示される手順に従ってインストールを完了させます。 そこまで難しい内容はございませんが、もし不安な方は、以下のビデオにて、細かい手順が案内されているので、ビデオを見ながら平行してインストールを進めてみてください。 おすすめ ▶ gallerypage/video-id/6366101833112" target="_blank" rel="noopener">Video S32DS3.6_install_activation_use.mp4 - NXP Community ２．S32K3 Real-Time Driverをインストール リアル・タイム・ドライバ(RTD)は、S32車載MCU上で動作する組込みアプリケーションの開発を加速するためにNXPが開発した一連のソフトウェア・コンポーネントです。ハードウェア・ペリフェラルに対する標準化された高性能インターフェースを提供し、開発者が信頼性と拡張性に優れた車載ソフトウェア・システムを開発できるようにします。   ダウンロードとインストール RTD xp.jp/design/design-center/software/automotive-software-and-tools/real-time-drivers-rtd:AUTOMOTIVE-RTD" target="_blank" rel="noopener">のダウンロードサイトへ行き、「ダウンロード」ボタンを押します。 ページがスクロールされるので、以下のS32K3 Standard Softwareの「ダウンロード」ボタンを押します。尚、このStandard Softwareとは、無償でご利用いただけるソフトウェア、ツールです。 今回はS32K3向けのRTDを選択します。  “Qualified as RFP Release”(RFP＝Release For Production)となっているものをクリック。 利用規約に同意して、進めます。 続いて、S32 Design StudioのUpdatesiteをクリックし、ダウンロードします。 スポイラ （読むためにハイライト） *Updatesiteとは？ RTDをダウンロードした状態は、まだ「zipで配布されたパッケージ」を手元に持っているだけで、S32DSからは使えません。ダウンロードしたUpdate Site（ ..._DesignStudio_updatesite.zip ）をS32DSに追加インストールすることで、はじめてRTDがIDEに登録され、新規プロジェクトウィザードでRTDを選択したり、S32 Configuration Toolで設定した内容を「Update Code」でRTDのコードとして自動生成できるようになります。 ※これを追加しないと、新規プロジェクト作成時にRTDが選択肢に表示されません。 ※なお、RTDがあらかじめS32DSにバンドルされているバージョンでは、この手順は不要でそのまま使えます。 *Updatesiteとは？ RTDをダウンロードした状態は、まだ「zipで配布されたパッケージ」を手元に持っているだけで、S32DSからは使えません。ダウンロードしたUpdate Site（..._DesignStudio_updatesite.zip）をS32DSに追加インストールすることで、はじめてRTDがIDEに登録され、新規プロジェクトウィザードでRTDを選択したり、S32 Configuration Toolで設定した内容を「Update Code」でRTDのコードとして自動生成できるようになります。※これを追加しないと、新規プロジェクト作成時にRTDが選択肢に表示されません。※なお、RTDがあらかじめS32DSにバンドルされているバージョンでは、この手順は不要でそのまま使えます。   S32DSでReal-Time Driverを開き、RTDをインストール では実際にS32DSを開いてみましょう。 S32DSを開いたら「S32DS Extension and Updates」をクリック。 S32K3のDevelopment Packageがインストール済であることを確認。 右下の「Add Updates Site」をクリックし、先ほどダウンロードしたReal-time Driverを追加します。 追加が完了すると、左側にReal-Time Driverが出てくるので、今回は「S32K3XX Real-Time Driver…」をクリックし、インストールを開始する。 右下を見ると、インストールが開始されたことを確認できます。インストールが進むと、S32DSを再起動するよう求められるので、指示に沿って進めます。 再起動を行い、RTDのインストールが完了！ 左下の「S32DS Project From Example」を開くと、先ほどインストールしたS32K3XX Real-Time Driverが確認できます。 以下のビデオにも、細かい手順が案内されているので、ビデオを見ながら平行してインストールを進めてみてください。 おすすめ ▶　S32 Design Studio 3.6: How to Download RTD | NXP Semiconductors ここまでで、S32 Design Studio IDEとS32K3のReal-Time Driverのインストールが完了しました。お疲れ様でした。 次の記事で、実際にRTDに含まれるドライバーとサンプル・アプリケーションを動かしてみます。 =========================​ 本投稿の「Comment」欄にコメントをいただいても、現在返信に対応しておりません。​ お手数をおかけしますが、お問い合わせの際には「8%E3%81%AE%E6%8A%80%E8%A1%93%E8%B3%AA%E5%95%8F-%E5%95%8F%E3%81%84%E5%90%88%E3%82%8F%E3%81%9B%E6%96%B9%E6%B3%95-%E6%97%A5%E6%9C%AC%E8%AA%9E%E3%83%96%E3%83%AD%E3%82%B0/ba-p/2153299" target="_blank" rel="noopener" data-hyperlinktype="0">NXPへの技術質問 - 問い合わせ方法 (日本語ブログ)」をご参照ください。​ （既に弊社NXP代理店、もしくはNXPとお付き合いのある方は、直接担当者へご質問いただいてもかまいません。）​ 本記事では、NXP車載MCU用の開発環境S32 Design Studio (S32DS)、及びReal-Time Driverのインストール方法を、初めて S32K に触る方でも迷わず進められる粒度で丁寧に解説します。 今回はS32K3という車載MCUを例にしますが、他の車載MCUでも同じ手順で環境を構築できます。 （作業時間：20分） General Purpose Microcontrollers S32 Design Studio S32K SW | Downloads 日本語ブログ

S32K312 POR_WDG is what, how to use. Hi HXP, S32K312 POR_WDG is what, how to use. Re: S32K312 POR_WDG is what, how to use. Hi @li3, 1. Please refer to the DCF clients file attached to the reference manual. 2. The Watchdog timer has a configurable threshold, if the chip does not exit the reset sequence within this time, the POR_WDG initiates a power-on-reset. You can monitor the WDG status from the DCMROPPn register.  3. This register only captures the status of the functional reset sequence process when POR_WDG overflows. Since the POR_WDG is part of the DCF client safety function, you can also look into the Safety Manual for S32K3 in "Secure Files" from the S32K3 Auto General-Purpose MCUs, documentation. Best regards, Julián Re: S32K312 POR_WDG is what, how to use. Hi NXP,     Please help me answer the following three questions.     1.I can't find the control register for reset monitor. I don't know how to turn on or off the reset monitoring function of POR_WDG. Please tell me the location of the register.     2. How does the reset monitoring function detect that the system is stuck in the reset sequence? Does it detect registers that have not been successfully reset?     3.The reset monitoring function indicates that after POR_WDG times out, the system deadlock position can be captured in DCM's DCMROPPn register. Can these states only let us know the system deadlock position after POR_WDG times out? Or is it the state of DCM's DCMROPPn register that determines the POR_WDG timeout? Best regards, Li 3. Re: S32K312 POR_WDG is what, how to use. Hi @li3, This is in case of functional reset event: Best regards, Julián Re: S32K312 POR_WDG is what, how to use. Hi NXP, What is the Reset monitoring control register? Is it to monitor whether Reset can succeed? Best regards, Li 3. Re: S32K312 POR_WDG is what, how to use. Hi @li3, The Power-on Reset Watchdog is a module for added monitoring to the chip. If the chip is stuck in reset or standby for a determined time, the watchdog generates a power-on reset to recover it.  Best regards, Julián

i.MX8M Plus HiFi4 DSP (Zephyr): SDMA cyclic TX callback fires once then stops On the i.MX8MP HiFi4 DSP running Zephyr, I'm bringing up a hardware-endpoint playback path using the Zephyr nxp,dai-sai (SAI3) and nxp,sdma (SDMA3) drivers in cyclic mode. On start playback, the SDMA channel completion callback fires exactly once, then no further SDMA interrupts occur. I'd like help identifying why the cyclic SDMA transfer does not keep generating periodic interrupts.   Hardware / boot   - Board: i.MX8MP EVK, DTS: imx8mp-evk-dsp.dts   - DSP core: HiFi4 (Cadence Xtensa), board target imx8mp_evk/mimx8ml8/adsp   - Codec: WM8960   - Peripherals: SAI3, SDMA3   Architecture and Build details:   - Architecture Overview: https://audioreach.github.io/platform/nxp.html#architecture-overview    - Build Details:     - Yocto: https://audioreach.github.io/platform/nxp.html#step-1-create-a-yocto-image       - Linux (control/host): Yocto (scarthgap), linux-imx.       - Repo manifest: imx-6.6.52-2.2.0.xml     - Zephyr DSP Image: https://audioreach.github.io/platform/nxp.html#step-2-create-a-zephyr-image       - Zephyr (v4.2.0), AudioReach Engine signal processing framework running on the HiFi4.   What I'm building   A custom hardware-endpoint (sink) module in the DSP image that:   1. Configures SAI3 via the Zephyr DAI API.   2. Sets up a cyclic SDMA transfer (2 buffer descriptors, MEMORY_TO_PERIPHERAL) from a DRAM ring into the SAI TX FIFO.   3. Uses the SDMA completion callback to signal the Signal Processing Framework to refill the ring.   Audio format   - 48 kHz, 16-bit, mono stream; SAI wire = 16-bit × 2 slots (stereo I2S frame for WM8960), BCLK = 1.536 MHz.   - DMA period = 192 bytes (48 frames × 2 bytes × 2 slots), 2 descriptors, 384-byte ring   Relevant Kconfig (DSP image) enabled   CONFIG_DAI=y   CONFIG_DMA=y   CONFIG_DAI_NXP_SAI=y   CONFIG_DMA_NXP_SDMA=y   CONFIG_SAI_HAS_MCLK_CONFIG_OPTION=y   CONFIG_CLOCK_CONTROL_FIXED_RATE_CLOCK=y   Device tree overlay (DSP app):   Link: app/boards/imx8mp_evk_mimx8ml8_adsp.overlay   mclk1: mclk {     status = "okay";   };   &sdma3 {     status = "okay";   };   &sai3 {     rx-fifo-watermark = <65>;     tx-fifo-watermark = <65>;     fifo-depth = <128>;     rx-sync-mode = <1>;     status = "okay";   };   &micfil {     status = "okay";   };   DAI / DMA config used (DSP)   - dai_config: type=DAI_IMX_SAI, dai_index=3, format= DAI_PROTO_I2S (SAI slave), rate=48000, channels=2, word_size=16.   - SAI bespoke: mclk_rate=12288000, fsync_rate=48000, bclk_rate=1536000, tdm_slots=2, tx_slots=rx_slots=0x3, tdm_slot_width=16.   - DMA (struct dma_config): channel_direction=MEMORY_TO_PERIPHERAL, source_data_size=4, dest_data_size=4, source_burst_length=4, cyclic=1, block_count=2, dma_slot from SAI handshake, dma_callback set. Two dma_block_config BDs point at dma_src_addr[0/192] Source code reference: endpoint/capi/src/capi_nxp_device_utils.c Application Processror:   - DTS: imx8mp-evk-dsp.dts https://github.com/nxp-imx/linux-imx/blob/lf-6.6.y/arch/arm64/boot/dts/freescale/imx8mp-evk-dsp.dts   - Enumerate PCM device with wm8960 codec with dummy dai and dummy platform. Attachments: - DSP logs (sdma, sai) - Modified imx8mp-evk-dsp.dts  Happy to provide any other details. i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Multimedia

How can I download GuierV1.7.2? How can I download GuierV1.7.2? Re: How can I download GuierV1.7.2? Hi @smile168  Thank you for your inquiry. Currently, only GUI Guider v2.0.0 and v1.10.1 are available for download. Unfortunately, v1.7.2 is no longer available through our download channels. Create Modern Embedded GUIs Fasts | NXP Semiconductors BR Harry

SL3S1013FTB0,115 design check request 1) Is the transponder schematic above correct for a 3.6V-powered and RFID-powered configuration?   2) Is the voltage stated correct for a 3.6V-powered and RFID-powered configuration for the RFID transponder?   a) 2.6V - 3.1V (3.6V powered) b) 1 - 1.5V (RFID powered) Re: SL3S1013FTB0,115 design check request Your supply voltage correction has been received. I will make the correction.  Your question: Is this the intended purpose for your application? Answer: We don't have an application for the current product, but we want to understand how this tamper alarm works.  I calculated the Vout for 1.8V and 2.2 V. Is this calculation correct? If yes, the Vout is too low to do anything meaningful. Vout = Ivdd X 1k Ivdd = Iinternal +Iout The typical, permanent current consumption will be ~120 µA for 1.8V and ~340 µA for 2.2V. For VDD = 1.8 V, Idd = 0.00012A For VDD = 2,2 V, Idd = 0.00034A For VDD = 1.8 V, Vout =  0.00012 X 1kohm Vout = 0.12V For VDD = 2.2 V, Vout =  0.00034 X 1kohm Vout = 0.34V Re: SL3S1013FTB0,115 design check request Hello @pragashsangaran When externally supplied, VDD pad requires a voltage between 1.8V and 2.2V; for a higher value, a series resistance would be required. For proper calculation, please refer to AN10940 FAQs on UCODE G2i, Chapter 3/Chapter 4. OUT pad is a digital output that can be used for tamper loop, a small external circuit or as indicator; these configurations require VDD pin to be externally suppled. If you populate R35, it will introduce a connection that could activate the "tamper indicator" bit, as per Tag Tamper Alarm feature (please see AN10940 FAQs on UCODE G2i, Chapter 16). Is this the intended purpose for your application? Expected voltage level on OUT pin is described in AN10940 FAQs on UCODE G2i, Chapter 13. A solution that powers a device connected to OUT pin requires an external supply on VDD pin. I will recommend you taking a look at the AN11237 UCODE G2iM+ demo board documentation, Fig 3 and Fig 5 for some reference connections. Regards, Eduardo. Re: SL3S1013FTB0,115 design check request Hi, In order to use the OUT pin functionalities, such as digital output/switch or powering an external circuit, an external supply is required. Also, as mentioned in AN10940 FAQs on UCODE G2i, Chapter 16 "How is the Tag Tamper Alarm used?" this feature is based on a galvanic connection between VDD and OUT; something important to remark is that the tamper feature and the external supply mode cannot be used at the same time. Regarding the calculations, please consider that the voltage level available on the OUT pin is defined by the voltage level on VDD reduced by the voltage drop on the internal series resistor. You can find a few examples on AN10940 FAQs on UCODE G2i, Chapter 5.3. Regards, Eduardo. Re: SL3S1013FTB0,115 design check request EduardoZamora, thank you so much. After many attempts to ask the same questions again and again, I finally feel like I im getting the correct answers to my questions. I really hope we can resolve my question in this ticket.  I also want to know if it is the Vout of the RFID-powered configuration (without VDD). Can you please let me know as well?  im not using a tamper indicator. I hope we can justify the use of SL3S1013FTB0,115 vs a Schottky diode. If a Schottky diode can provide higher Vout without a supply voltage, I'd rather go for a Schottky diode.  Re: SL3S1013FTB0,115 design check request Hi, Vout depends on the voltage present on VDD pin (after proper dimensioning of the series resistor between VDD and RFN according to AN10940 FAQs on UCODE G2i, Chapter 5), reduced by the voltage drop on the internal series resistor between VDD and OUT (~1kΩ). Some calculation examples can be found in Chapter 5.3. Regarding the state of OUT pin, please refer to Chapter 8 to 10 for more information on how to control this pin. Regards, Eduardo. Re: SL3S1013FTB0,115 design check request Hi  EduardoZamora, We are not going to use Tamper Alarm, so we can ignore this. The R35 is there just in case. For us, Vout is very important because it needs to turn the product ON. You are saying VDD needs to be present in order to get Vout. However, I have two major concerns about using this part. The calculated Vout is too low. For VDD = 1.8 V, Vout = 0.12V For VDD = 2.2 V, Vout = 0.34V. This Vout will not help at all to turn things on . Even if we think about boosting this voltage, there aren't many options available to raise it further. Is my calculation correct? Please see one of my previous replies for full calculations. In the presence of VDD, can Vout be present regardless of the RFID signal? We want Vout to be present only when the antenna receives an RFID signal. Is this true?

GUI Guider 1.10.1 omits background style properties when Background Opacity is 0 Environment GUI Guider: 1.10.1 LVGL: 8.3 Widget: Button Style Part: LV_PART_MAIN Style State: LV_STATE_DEFAULT Problem Description I found a reproducible code-generation issue in GUI Guider 1.10.1. When a button has a configured background color but its Background Opacity is set to 0, GUI Guider does not generate the corresponding background color property. This causes unexpected behavior when the background opacity is changed dynamically at runtime. Reproduction Create a Button and configure: Background Color: #F08300 Background Opacity: 0 Then generate the LVGL 8.3 code. GUI Guider generates: lv_obj_set_style_bg_opa(ui->screen_password_btn_15, 0, LV_PART_MAIN | LV_STATE_DEFAULT); However, the configured background color is not generated: lv_obj_set_style_bg_color(ui->screen_password_btn_15, lv_color_hex(0xF08300), LV_PART_MAIN | LV_STATE_DEFAULT); Test: Change only Background Opacity from 0 to 1 I changed only the Background Opacity from 0 to 1, while keeping the same Background Color #F08300. After regenerating the code, GUI Guider generates: lv_obj_set_style_bg_opa(ui->screen_password_btn_15, 1, LV_PART_MAIN | LV_STATE_DEFAULT); lv_obj_set_style_bg_color(ui->screen_password_btn_15, lv_color_hex(0xF08300), LV_PART_MAIN | LV_STATE_DEFAULT); lv_obj_set_style_bg_grad_dir(ui->screen_password_btn_15, LV_GRAD_DIR_NONE, LV_PART_MAIN | LV_STATE_DEFAULT); Therefore, the generated code differs depending on whether Background Opacity is exactly 0. Background Opacity = 0: bg_opa is generated bg_color is not generated Background Opacity = 1: bg_opa is generated bg_color is generated other background properties are also generated Runtime Impact My application uses the background opacity to indicate the currently selected password digit. The background color is configured in GUI Guider as #F08300, while the application dynamically changes only the background opacity. For example: lv_obj_set_style_bg_opa(btn, LV_OPA_COVER, LV_PART_MAIN | LV_STATE_DEFAULT); For a button whose initial Background Opacity is 0, the generated code does not contain the configured background color. When the application changes the opacity from 0 to LV_OPA_COVER, the button displays the LVGL theme or default background color instead of the #F08300 color configured in GUI Guider. The behavior is: GUI Guider configuration: Background Color = #F08300 Background Opacity = 0 Generated code: bg_opa = 0 bg_color is not generated Runtime: bg_opa is changed to LV_OPA_COVER Result: The default or theme background color is displayed instead of #F08300. Workaround Explicitly setting the background color in application code resolves the issue: lv_obj_set_style_bg_color(btn, lv_color_hex(0xF08300), LV_PART_MAIN | LV_STATE_DEFAULT); lv_obj_set_style_bg_opa(btn, LV_OPA_COVER, LV_PART_MAIN | LV_STATE_DEFAULT); Another possible workaround is setting Background Opacity to 1 in GUI Guider, because this causes GUI Guider to generate the configured background color. However, this changes the initial UI state and is therefore not ideal. Expected Behavior Background Color and Background Opacity are separate LVGL style properties. If the user explicitly configures: Background Color = #F08300 Background Opacity = 0 I would expect GUI Guider to preserve both properties in the generated code: lv_obj_set_style_bg_opa(btn, 0, LV_PART_MAIN | LV_STATE_DEFAULT); lv_obj_set_style_bg_color(btn, lv_color_hex(0xF08300), LV_PART_MAIN | LV_STATE_DEFAULT); Although bg_color has no visible effect while bg_opa is 0, it becomes relevant when the application dynamically changes bg_opa at runtime. The current code-generation behavior loses the background color information configured in GUI Guider. Actual Behavior GUI Guider 1.10.1 appears to omit background style properties when Background Opacity is 0. Changing only the opacity from 0 to 1 causes the background color and other background properties to be generated again. Steps to Reproduce Create a Button in GUI Guider 1.10.1. Set Background Color to #F08300. Set Background Opacity to 0. Generate LVGL 8.3 code. Observe that lv_obj_set_style_bg_opa with value 0 is generated. Observe that lv_obj_set_style_bg_color with #F08300 is not generated. Change only Background Opacity from 0 to 1. Generate the code again. Observe that lv_obj_set_style_bg_color with #F08300 is now generated. At runtime, change the opacity of the original button to LV_OPA_COVER. Observe that the configured background color is not displayed unless bg_color is explicitly set by the application. Question Is this an intentional code-size optimization in GUI Guider 1.10.1, or is it a code-generation issue? If this optimization is intentional, could GUI Guider provide an option to preserve background properties when Background Opacity is 0? Runtime applications commonly change LVGL style properties dynamically, so omitting bg_color based only on its initial opacity can result in runtime behavior that differs from the UI configuration. Re: GUI Guider 1.10.1 omits background style properties when Background Opacity is 0 Hello @zzjgood , Thanks for your post.  I can reproduce the behavior you described. I think this is a code-generation issue. If the user explicitly configures a Background Color, GUI Guider should preserve the corresponding bg_color code even when the initial Background Opacity is 0, or provide an option to preserve background style properties for transparent objects. I will report this to the GUI-Guider team for further fix. In addition, according to our internal escalation process, we would appreciate it if you could provide the following information: - Which NXP product are you using? - What is your end application? The current practical workaround is to explicitly set both the background color and opacity in the application code: Copy lv_obj_set_style_bg_color(btn, lv_color_hex(0xF08300), LV_PART_MAIN | LV_STATE_DEFAULT); lv_obj_set_style_bg_opa(btn, LV_OPA_COVER, LV_PART_MAIN | LV_STATE_DEFAULT); Hop it helps. BR Celeste

PN512 - Does it actually support Type 4 Tag (T4T/HCE) card emulation? Hi all, Working on a custom board (LPC54101 + PN512) that needs to both read NTAG213/216 tags (working fine) and emulate a Type 4 Tag serving a static NDEF (BT-OOB pairing record) so a phone can tap and read it. Using NxpRdLib V2.0.3.0 with phpalI14443p4C_Sw / phceT4T_Sw. Calling phceT4T_Listen() in a loop -> internally phhalHw_Listen() -> Autocoll on the PN512. Consistently get PH_ERR_IO_TIMEOUT (0x0201), unaffected by timeout config, explicit FieldOff before listening, or register-level checks (TxControlReg confirms our own field is off, GsNOffReg at datasheet default, RFCfgReg/RxThresholdReg/DemodReg all normal). No reaction at all from Android or iPhone held directly on the antenna. I found this thread where NXP support says PN512 can't do card emulation per the datasheet, and recommends CLRC663 instead: https://community.nxp.com/t5/Other-NXP-Products/PN512-Emulation-Tag-Write-issue/m-p/2089993 But that seems to contradict the PN512 product page (lists "card emulation functionality" as a feature), and this other thread where someone got Mifare Ultralight tag emulation working fine on PN512: https://community.nxp.com/t5/NFC/Pn512-Tag-Emulation-Callibration/td-p/684135 So: is the difference that PN512 can do simple ISO14443-3 tag emulation (UID/anticollision, like Mifare UL) but NOT full ISO14443-4 Type 4 Tag activation (RATS/ATS, APDU exchange)? Has anyone gotten genuine T4T/HCE working on PN512, or is this chip a dead end for that specific use case? Also separately: our RdLib V2.0.3.0 package's ReleaseNotes.txt states the discovery loop only supports Poll/Pause phases, and the .chm docs have zero mention of phceT4T or phpalI14443p4C - so I'm also unsure whether the card-emulation component we have was ever an officially validated/documented release. Any pointers to a proper matching package appreciated. Thanks! Re: PN512 - Does it actually support Type 4 Tag (T4T/HCE) card emulation? Hello sir, As mentioned in your other case, yes PN512 does support HCE, we even have an example with Raspberry Pi. But please keep in mind that PN512 isn't recommended for new designs. Please explore the possibility of using our NFC Readers that are Full Support NFC mode (PN5190, PN5180, PN7462, PN7642).  All of these readers can be used with our NFC Reader Library. I hope this information may have been useful. Re: PN512 - Does it actually support Type 4 Tag (T4T/HCE) card emulation? Quick update for anyone finding this thread later, since I got two different answers between here and my support ticket: AN11480 (the Raspberry Pi/EXPLORE-NFC guide) only demonstrates Type 2 Tag emulation on PN512 - it says so directly in §7.1 ("the Card Emulation example emulates an NFC Forum Type 2 Tag") and never mentions phceT4T or T4T anywhere. If you were pointed there for T4T/HCE, that's not the right doc. For actual Type 4 Tag (T4T/HCE) emulation on PN512, see AN11308 (PNEV512B/LPC1769 Quick Startup Guide), §6.8 "Example 8 - HCE T4T" and §7.1.6 "HCE Layer". That example is explicitly built on the NFC Forum Type 4 Tag Operation Specification v2.0, using phceT4T_Activate()/phceT4T_AppProcessCmd(), and supports Select/ReadBinary/UpdateBinary. So: yes, PN512 does support genuine T4T emulation, just not via the Raspberry Pi package - via the PNEV512B/LPC1769 (Blueboard) package instead. Following up with support to confirm the exact library version and reconcile the two answers.

LIN communication failure during E-Flash write A LIN communication failure is detected during the write operation of 100 bytes of data to the internal EEPROM. Please suggest an appropriate LIN communication recovery method. Re: LIN communication failure during E-Flash write Hi @SivaB  Could you please let us know which exact S32K device you are using? One possible explanation is that the Emulated EEPROM operation takes a relatively long time, and the resulting delay may prevent the software from servicing LIN interrupts within the required timing constraints. Another possibility is a Read-While-Write conflict. During flash erase/program operations, code or data located in the flash block currently being programmed or erased cannot be fetched/read. If such code or data is required by the application, this could cause the application to crash, which would subsequently result in the observed LIN communication failures. Could you also clarify what happens when the issue occurs? Does the application crash completely, or does it continue running and only the LIN communication stop working? Regards, Lukas

IMX8MP Self Designed Board system crash after booting in the system Hi everyone, We designed a custom board using the i.MX8M Plus (IMX8MP) CPU with 4GB LPDDR4 RAM and 128GB eMMC storage. Below is our boot log. As you can see, after booting into Linux, we can briefly enter commands in the console, but the system freezes almost immediately and becomes completely unresponsive. We suspect this issue might be caused by the EXT4-fs error shown in the log. Has anyone encountered a similar issue, or could you give us some advice on how to troubleshoot this? Any help would be greatly appreciated! Thanks in advance. U-Boot SPL 2020.04 (Aug 10 2026 - 12:59:20 +0800) DDRINFO: start DRAM init DDRINFO: DRAM rate 3200MTS DDRINFO:ddrphy calibration done DDRINFO: ddrmix config done Normal Boot Trying to boot from MMC2 Authentication key not yet programmed keyslot package magic error, do nothing here! NOTICE: BL31: v2.2(release):fc5b00e8fa-dirty NOTICE: BL31: Built : 12:59:31, Aug 10 2026 welcome to lk/MP boot args 0x2000000 0x56000000 0x2000 0x0 initializing trusty (Built: 12:16:06 Nov 19 2020) Initializing Trusted OS SMC handler avb: Initializing AVB App hwcrypto: Initializing hwrng_caam: Init HWRNG service provider hwrng_srv: Start HWRNG service hwcrypto_caam: Init HWCRYPTO service provider hwcrypto_srv: Start HWCRYPTO service hwkey_caam: Init HWKEY service provider hwkey_caam: 183: Invalid magic, unpack key package fail. hwkey_srv: Start HWKEY service hwcrypto: enter main event loop trusty_gatekeeper: Initializing U-Boot 2020.04 (Aug 10 2026 - 12:59:20 +0800) CPU: i.MX8MP Lite[4] rev1.1 1600 MHz (running at 1200 MHz) CPU: Industrial temperature grade (-40C to 105C) at 48C Reset cause: POR Model: NXP i.MX8MPlus abcd LPDDR4 EVK board DRAM: 4 GiB tcpc_init: Can't find device id=0x50 setup_typec: tcpc port2 init failed, err=-19 tcpc_init: Can't find device id=0x50 setup_typec: tcpc port1 init failed, err=-19 MMC: FSL_SDHC: 1, FSL_SDHC: 2 Loading Environment from MMC... *** Warning - bad CRC, using default environment [*]-Video Link 0Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings probe video device failed, ret -19 [0] lcd-controller@32e80000, video [1] mipi_dsi@32e60000, video_bridge [2] adv7535@3d, panel Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings probe video device failed, ret -19 In: serial Out: serial Err: serial BuildInfo: - ATF - U-Boot 2020.04 flash target is MMC:2 Net: Error: ethernet@30bf0000 address not set. Error: ethernet@30bf0000 address not set. No ethernet found. INFO Initializing Trusty device INFO selected trusty api version: 3 (requested 3) ss: get_rpmb_auth_key: failed to get key: -2 ss: proxy_connect: can't get storage auth key: (-2) ss-ipc: 105: do_connect: failure initializing channel state (1001) rpmb_proxy.c:312: ERROR rpmb_storage_proxy_init: unexpected proxy channel close libtipc.c:92: ERROR Initlializing RPMB storage proxy service failed (-8) Authentication key not yet programmed Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_validate_vbmeta_public_key_rpmb: Read public key error avb_slot_verify.c:900: ERROR: vbmeta_a: Public key used to sign data rejected. avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_read_rollback_index_rpmb: read rollback from Trusty error! Authentication key not yet programmed avb_slot_verify.c:482: ERROR: dtbo_a: Hash of data does not match digest in descriptor. avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized Writing A/B metadata to disk. verify FAIL, state: UNLOCK boot 'boot_a' still kernel @ 40480000 (36925952) ramdisk @ 44680000 (7268024) fdt @ 44480000 (65027) avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized Device is unlocked, press power key to skip warning logo... Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings no video device found! can't show unlock warning. avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized ERROR - failed to read public key for keymaster keymaster.c:318: ERROR Keymaster TIPC client not initialized! avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized ipc_dev.c:306: ERROR trusty_ipc_dev_close: secure OS returned (-7) ## Flattened Device Tree blob at 44480000 Booting using the fdt blob at 0x44480000 Using Device Tree in place at 0000000044480000, end 0000000044492e02 Found /vpu_g1@38300000 node Modify /vpu_g1@38300000:status disabled Found /vpu_g2@38310000 node Modify /vpu_g2@38310000:status disabled Found /vpu_vc8000e@38320000 node Modify /vpu_vc8000e@38320000:status disabled Found /vipsi@38500000 node Modify /vipsi@38500000:status disabled Found /soc@0/bus@32c00000/camera/isp@32e10000 node Modify /soc@0/bus@32c00000/camera/isp@32e10000:status disabled Found /soc@0/bus@32c00000/camera/isp@32e20000 node Modify /soc@0/bus@32c00000/camera/isp@32e20000:status disabled Found /dsp@3b6e8000 node Modify /dsp@3b6e8000:status disabled Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings probe video device failed, ret -19 Starting kernel ... unable to select a mode device_remove: Device '[email protected]' failed to remove, but children are gone [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.4.70 (forenex@forenex20) (Android (5271481 based on r349610) clang version 8.0.8 (https://android.googlesource.com/toolchain/clang 4dba9ad555eabb40b39dc53c12d09423e9faea7b) (https://android.googlesource.com/toolchain/llvm ab552995647d484a712bf15f77e6c6f4e8ac532b) (based on LLVM 8.0.8svn), GNU ld (binutils-2.27-44492f8e) 2.27.0.20170315) #96 SMP PREEMPT Mon Aug 10 12:43:56 CST 2026 [ 0.000000] Machine model: NXP i.MX8MPlus EVK board [ 0.000000] earlycon: ec_imx6q0 at MMIO 0x0000000030890000 (options '115200') [ 0.000000] printk: bootconsole [ec_imx6q0] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: UEFI not found. [ 0.000000] OF: reserved mem: failed to allocate memory for node 'linux,cma' [ 0.000000] cma: Reserved 800 MiB at 0x0000000060000000 [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000017fffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x17f7cc500-0x17f7cdfff] [ 0.000000] Zone ranges: [ 0.000000] DMA32 [mem 0x0000000040000000-0x00000000ffffffff] [ 0.000000] Normal [mem 0x0000000100000000-0x000000017fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x00000000557fffff] [ 0.000000] node 0: [mem 0x0000000058000000-0x00000000923fffff] [ 0.000000] node 0: [mem 0x0000000094410000-0x00000000bfffffff] [ 0.000000] node 0: [mem 0x0000000100000000-0x000000017fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000017fffffff] [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.1 [ 0.000000] percpu: Embedded 32 pages/cpu s93400 r8192 d29480 u131072 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] Speculative Store Bypass Disable mitigation not required [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1014032 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: console=ttymxc1,115200 earlycon=ec_imx6q,0x30890000,115200 init=/init androidboot.console=ttymxc1 androidboot.hardware=freescale firmware_class.path=/vendor/firmware loop.max_part=7 transparent_hugepage=never androidboot.lcd_density=240 androidboot.primary_display=imx-drm androidboot.wificountrycode=CN androidboot.selinux=permissive cma=800M@0x400M-0xb80M buildvariant=userdebug androidboot.serialno=0926980055347a54 androidboot.btmacaddr=09:26:98:00:55:34 androidboot.soc_type=imx8mp androidboot.boot_device_root=mmcblk2 androidboot.boottime=1BLL:0,1BLE:4332,KL:0,KD:0,AVB:671,ODT:0,SW:0 androidboot.bootreason=cold,powerkey androidboot.verifiedbootstate=orange androidboot.flash.locked=0 androidboot.slot_suffix=_a androidboot.vbmeta.device=PARTUUID=a670210c-8754-426c-a5b2-440a72068e31 androidboot.vbmeta.avb_version=1.1 androidboot.vbmeta.device_state=unlocked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=3456 androidboot.vbmeta.digest=6f86b17aea6 [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0xbc000000-0xc0000000] (64MB) [ 0.000000] Memory: 3110948K/4120512K available (19388K kernel code, 1884K rwdata, 10296K rodata, 4416K init, 589K bss, 190364K reserved, 819200K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 160 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: no VLPI support, no direct LPI support [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000 [ 0.000000] ITS: No ITS available, not enabling LPIs [ 0.000000] random: get_random_bytes called from start_kernel+0x1e0/0x3a4 with crng_init=0 [ 0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns [ 0.000004] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [ 0.008586] Console: colour dummy device 80x25 [ 0.012580] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [ 0.022843] pid_max: default: 32768 minimum: 301 [ 0.027543] LSM: Security Framework initializing [ 0.032144] SELinux: Initializing. [ 0.035679] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.043064] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.052153] ASID allocator initialised with 32768 entries [ 0.056453] rcu: Hierarchical SRCU implementation. [ 0.062588] EFI services will not be available. [ 0.065940] smp: Bringing up secondary CPUs ... [ 0.070740] Detected VIPT I-cache on CPU1 [ 0.070762] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000 [ 0.070788] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.071277] Detected VIPT I-cache on CPU2 [ 0.071293] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000 [ 0.071308] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.071758] Detected VIPT I-cache on CPU3 [ 0.071772] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000 [ 0.071787] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.071847] smp: Brought up 1 node, 4 CPUs [ 0.126892] SMP: Total of 4 processors activated. [ 0.131607] CPU features: detected: 32-bit EL0 Support [ 0.136784] CPU features: detected: CRC32 instructions [ 0.141964] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching [ 0.150345] CPU: All CPU(s) started at EL2 [ 0.154458] alternatives: patching kernel code [ 0.160090] CPU3: update max cpu_capacity 1024 [ 0.161162] devtmpfs: initialized [ 0.171950] CPU3: update max cpu_capacity 1024 [ 0.177065] Initilizing CustomIPI irq domain [ 0.181854] Registered cp15_barrier emulation handler [ 0.186900] Registered setend emulation handler [ 0.191752] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.201261] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.230348] pinctrl core: initialized pinctrl subsystem [ 0.233519] DMI not present or invalid. [ 0.236972] NET: Registered protocol family 16 [ 0.241723] schedtune: configured to support 5 boost groups [ 0.253931] DMA: preallocated 256 KiB pool for atomic allocations [ 0.257232] audit: initializing netlink subsys (disabled) [ 0.262846] audit: type=2000 audit(0.188:1): state=initialized audit_enabled=0 res=1 [ 0.270434] cpuidle: using governor menu [ 0.275031] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.282334] Serial: AMBA PL011 UART driver [ 0.285353] imx mu driver is registered. [ 0.289231] imx rpmsg driver is registered. [ 0.330534] imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver [ 0.355197] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.359088] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [ 0.365812] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.372548] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 0.380290] cryptd: max_cpu_qlen set to 1000 [ 0.386907] ACPI: Interpreter disabled. [ 0.389749] iommu: Default domain type: Translated [ 0.392979] vgaarb: loaded [ 0.395797] SCSI subsystem initialized [ 0.399630] usbcore: registered new interface driver usbfs [ 0.404821] usbcore: registered new interface driver hub [ 0.410185] usbcore: registered new device driver usb [ 0.416258] mc: Linux media interface: v0.10 [ 0.419511] videodev: Linux video capture interface: v2.00 [ 0.425062] pps_core: LinuxPPS API ver. 1 registered [ 0.429985] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.439183] PTP clock support registered [ 0.443476] trusty trusty: trusty version: Built: 12:16:06 Nov 19 2020 [ 0.449684] trusty trusty: selected api version: 3 (requested 3) [ 0.462140] EDAC MC: Ver: 3.0.0 [ 0.463513] FPGA manager framework [ 0.465936] Advanced Linux Sound Architecture Driver Initialized. [ 0.472339] Bluetooth: Core ver 2.22 [ 0.475559] NET: Registered protocol family 31 [ 0.480018] Bluetooth: HCI device and connection manager initialized [ 0.486408] Bluetooth: HCI socket layer initialized [ 0.491305] Bluetooth: L2CAP socket layer initialized [ 0.496381] Bluetooth: SCO socket layer initialized [ 0.502651] clocksource: Switched to clocksource arch_sys_counter [ 0.581807] VFS: Disk quotas dquot_6.6.0 [ 0.582934] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.589959] pnp: PnP ACPI: disabled [ 0.599613] thermal_sys: Registered thermal governor 'step_wise' [ 0.599616] thermal_sys: Registered thermal governor 'power_allocator' [ 0.603184] NET: Registered protocol family 2 [ 0.614167] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear) [ 0.622368] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.630475] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear) [ 0.638103] TCP: Hash tables configured (established 32768 bind 32768) [ 0.644288] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.650996] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.658273] NET: Registered protocol family 1 [ 0.662906] PCI: CLS 0 bytes, default 64 [ 0.666612] Trying to unpack rootfs image as initramfs... [ 0.969042] Freeing initrd memory: 7096K [ 0.971205] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available [ 0.978368] kvm [1]: IPA Size Limit: 40bits [ 0.982977] kvm [1]: GICv3: no GICV resource entry [ 0.986931] kvm [1]: disabling GICv2 emulation [ 0.991384] kvm [1]: GIC system register CPU interface enabled [ 0.997313] kvm [1]: vgic interrupt IRQ1 [ 1.001294] kvm [1]: Hyp mode initialized successfully [ 1.009715] Initialise system trusted keyrings [ 1.011415] workingset: timestamp_bits=44 max_order=20 bucket_order=0 [ 1.023899] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.027035] Registering sdcardfs 0.1 [ 1.030681] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 1.036976] fuse: init (API version 7.31) [ 1.040947] 9p: Installing v9fs 9p2000 file system support [ 1.061195] Key type asymmetric registered [ 1.062439] Asymmetric key parser 'x509' registered [ 1.067377] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 1.074786] io scheduler mq-deadline registered [ 1.079335] io scheduler kyber registered [ 1.086444] /ubuntu20/imx8_data/imx8_an10/android_build/vendor/nxp-opensource/kernel_imx/drivers/gpio/dido.c dido_get_of_properties() line 65, cannot get device_node [ 1.109693] i.MX8MP clock driver probe done [ 1.115607] imx-sdma 30bd0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 [ 1.120533] mxs-dma 33000000.dma-apbh: initialized [ 1.123274] imx-sdma 30bd0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin [ 1.129738] Bus freq driver module loaded [ 1.145963] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.151900] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 27, base_baud = 5000000) is a IMX [ 1.158772] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 28, base_baud = 5000000) is a IMX [ 1.167481] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 29, base_baud = 1500000) is a IMX [ 1.175960] printk: console [ttymxc1] enabled [ 1.175960] printk: console [ttymxc1] enabled [ 1.184631] printk: bootconsole [ec_imx6q0] disabled [ 1.184631] printk: bootconsole [ec_imx6q0] disabled [ 1.215387] brd: module loaded [ 1.225099] loop: module loaded [ 1.228659] zram: Added device: zram0 [ 1.245575] imx ahci driver is registered. [ 1.253618] spi-nor spi0.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00 [ 1.260560] spi-nor: probe of spi0.0 failed with error -2 [ 1.267745] libphy: Fixed MDIO Bus: probed [ 1.272662] tun: Universal TUN/TAP device driver, 1.6 [ 1.278971] thunder_xcv, ver 1.0 [ 1.282228] thunder_bgx, ver 1.0 [ 1.285499] nicpf, ver 1.0 [ 1.290093] hclge is initializing [ 1.293427] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.300654] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.306006] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 1.313062] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.318842] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 1.324682] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.330695] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k [ 1.337666] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.343278] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k [ 1.351114] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.357260] sky2: driver version 1.30 [ 1.361899] PPP generic driver version 2.4.2 [ 1.366319] PPP BSD Compression module registered [ 1.371035] PPP Deflate Compression module registered [ 1.376113] PPP MPPE Compression module registered [ 1.380912] NET: Registered protocol family 24 [ 1.385361] PPTP driver version 0.8.5 [ 1.389257] usbcore: registered new interface driver r8152 [ 1.394782] usbcore: registered new interface driver asix [ 1.400239] usbcore: registered new interface driver ax88179_178a [ 1.406370] usbcore: registered new interface driver cdc_ether [ 1.412238] usbcore: registered new interface driver net1080 [ 1.417931] usbcore: registered new interface driver cdc_subset [ 1.423885] usbcore: registered new interface driver zaurus [ 1.429508] usbcore: registered new interface driver cdc_ncm [ 1.435352] VFIO - User Level meta-driver version: 0.3 [ 1.445715] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.452309] ehci-pci: EHCI PCI platform driver [ 1.456815] ehci-platform: EHCI generic platform driver [ 1.462338] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.468535] ohci-pci: OHCI PCI platform driver [ 1.473034] ohci-platform: OHCI generic platform driver [ 1.479307] usbcore: registered new interface driver uas [ 1.484672] usbcore: registered new interface driver usb-storage [ 1.490764] usbcore: registered new interface driver usbserial_generic [ 1.497316] usbserial: USB Serial support registered for generic [ 1.503356] usbcore: registered new interface driver ftdi_sio [ 1.509129] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.516472] usbcore: registered new interface driver usb_serial_simple [ 1.523022] usbserial: USB Serial support registered for carelink [ 1.529140] usbserial: USB Serial support registered for zio [ 1.534827] usbserial: USB Serial support registered for funsoft [ 1.540859] usbserial: USB Serial support registered for flashloader [ 1.547233] usbserial: USB Serial support registered for google [ 1.553176] usbserial: USB Serial support registered for libtransistor [ 1.559725] usbserial: USB Serial support registered for vivopay [ 1.565755] usbserial: USB Serial support registered for moto_modem [ 1.572042] usbserial: USB Serial support registered for motorola_tetra [ 1.578677] usbserial: USB Serial support registered for novatel_gps [ 1.585051] usbserial: USB Serial support registered for hp4x [ 1.590818] usbserial: USB Serial support registered for suunto [ 1.596762] usbserial: USB Serial support registered for siemens_mpi [ 1.603158] usbcore: registered new interface driver usb_ehset_test [ 1.612942] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0 [ 1.626318] usbcore: registered new interface driver xpad [ 1.631778] usbcore: registered new interface driver usb_acecad [ 1.637740] usbcore: registered new interface driver aiptek [ 1.643351] usbcore: registered new interface driver gtco [ 1.648784] usbcore: registered new interface driver hanwang [ 1.654478] usbcore: registered new interface driver kbtab [ 1.661884] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0 [ 1.668105] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T00:00:09 UTC (9) [ 1.677317] i2c /dev entries driver [ 1.682145] uvcvideo: Unable to create debugfs directory [ 1.687515] usbcore: registered new interface driver uvcvideo [ 1.693270] USB Video Class driver (1.1.1) [ 1.698293] __power_supply_register: Expected proper parent device for 'battery' [ 1.706033] __power_supply_register: Expected proper parent device for 'usb' [ 1.721398] trusty-virtio trusty:trusty-virtio: initializing [ 1.727285] trusty_ipc virtio0: vring0: va(pa) (____ptrval____)(0) qsz 32 notifyid 1 [ 1.735140] trusty_ipc virtio0: vring1: va(pa) (____ptrval____)(0) qsz 32 notifyid 2 [ 1.743200] trusty-virtio trusty:trusty-virtio: initializing done [ 1.743335] trusty_ipc virtio0: is online [ 1.750259] device-mapper: uevent: version 1.0.3 [ 1.758225] device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: [email protected] [ 1.766887] Bluetooth: HCI UART driver ver 2.3 [ 1.771348] Bluetooth: HCI UART protocol H4 registered [ 1.776497] Bluetooth: HCI UART protocol BCSP registered [ 1.781837] Bluetooth: HCI UART protocol LL registered [ 1.786983] Bluetooth: HCI UART protocol ATH3K registered [ 1.792407] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.798892] Bluetooth: HCI UART protocol Broadcom registered [ 1.804577] Bluetooth: HCI UART protocol QCA registered [ 1.810129] EDAC MC: ECC not enabled [ 1.816509] sdhci: Secure Digital Host Controller Interface driver [ 1.822704] sdhci: Copyright(c) Pierre Ossman [ 1.827336] Synopsys Designware Multimedia Card Interface Driver [ 1.834244] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.840630] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SD1_CLK already requested by 30860000.serial; cannot claim for 30b40000.mmc [ 1.852990] imx8mp-pinctrl 30330000.pinctrl: pin-35 (30b40000.mmc) status -22 [ 1.860139] imx8mp-pinctrl 30330000.pinctrl: could not request pin 35 (MX8MP_IOMUXC_SD1_CLK) from group usdhc1grp on device 30330000.pinctrl [ 1.872837] sdhci-esdhc-imx 30b40000.mmc: Error applying setting, reverse things back [ 1.880695] sdhci-esdhc-imx: probe of 30b40000.mmc failed with error -22 [ 1.920203] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA [ 1.931108] ledtrig-cpu: registered to indicate activity on CPUs [ 1.937923] hidraw: raw HID events driver (C) Jiri Kosina [ 1.945993] usbcore: registered new interface driver usbhid [ 1.951586] usbhid: USB HID core driver [ 1.956991] mxc-isi 32e00000.isi: mxc_isi.0 registered successfully [ 1.964353] mxc-mipi-csi2-sam 32e40000.csi: 32e40000.csi supply mipi-phy not found, using dummy regulator [ 1.974260] mxc-mipi-csi2-sam 32e40000.csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 500000000 [ 1.986232] ashmem: initialized [ 1.993860] optee: probing for conduit method from DT. [ 1.999031] optee: api uid mismatch [ 2.004745] Galcore version 6.4.3.p1.305572 [ 2.051739] mmc2: new HS400 Enhanced strobe MMC card at address 0001 [ 2.059265] mmcblk2: mmc2:0001 AKL11X 115 GiB [ 2.063988] mmcblk2boot0: mmc2:0001 AKL11X partition 1 4.00 MiB [ 2.070180] mmcblk2boot1: mmc2:0001 AKL11X partition 2 4.00 MiB [ 2.077029] mmcblk2rpmb: mmc2:0001 AKL11X partition 3 4.00 MiB, chardev (236:0) [ 2.090822] Alternate GPT is invalid, using primary GPT. [ 2.096206] mmcblk2: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 [ 2.115512] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 0 [ 2.126011] usbcore: registered new interface driver snd-usb-audio [ 2.134183] OF: /sound-bt-sco/simple-audio-card,cpu: could not get #sound-dai-cells for /soc@0/bus@30c00000/spba-bus@30c00000/sai@30c20000 [ 2.146639] asoc-simple-card sound-bt-sco: parse error -22 [ 2.152158] asoc-simple-card: probe of sound-bt-sco failed with error -22 [ 2.164837] imx-micfil sound-micfil: ASoC: failed to init link micfil hifi: -517 [ 2.172301] imx-micfil sound-micfil: snd_soc_register_card failed (-517) [ 2.179588] imx-cdnhdmi sound-hdmi: ASoC: failed to init link imx8 hdmi: -517 [ 2.186746] imx-cdnhdmi sound-hdmi: snd_soc_register_card failed (-517) [ 2.193608] imx-xcvr sound-xcvr: ASoC: failed to init link XCVR PCM: -517 [ 2.200412] imx-xcvr sound-xcvr: snd_soc_register_card failed: -517 [ 2.206794] pktgen: Packet Generator for packet performance testing. Version: 2.75 [ 2.218070] drop_monitor: Initializing network drop monitor service [ 2.224432] NET: Registered protocol family 26 [ 2.228889] netem: version 1.3 [ 2.231955] u32 classifier [ 2.234668] input device check on [ 2.238328] Actions configured [ 2.242384] xt_time: kernel timezone is -0000 [ 2.246881] gre: GRE over IPv4 demultiplexor driver [ 2.251769] IPv4 over IPsec tunneling driver [ 2.256576] Initializing XFRM netlink socket [ 2.260876] IPsec XFRM device driver [ 2.264908] NET: Registered protocol family 10 [ 2.270517] Segment Routing with IPv6 [ 2.274279] mip6: Mobile IPv6 [ 2.278148] NET: Registered protocol family 17 [ 2.282622] NET: Registered protocol family 15 [ 2.288131] Bluetooth: RFCOMM TTY layer initialized [ 2.293026] Bluetooth: RFCOMM socket layer initialized [ 2.298177] Bluetooth: RFCOMM ver 1.11 [ 2.301934] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.307254] Bluetooth: BNEP filters: protocol multicast [ 2.312488] Bluetooth: BNEP socket layer initialized [ 2.317458] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.323406] Bluetooth: HIDP socket layer initialized [ 2.328414] l2tp_core: L2TP core driver, V2.0 [ 2.332789] l2tp_ppp: PPPoL2TP kernel driver, V2.0 [ 2.337591] 8021q: 802.1Q VLAN Support v1.8 [ 2.341797] lib80211: common routines for IEEE802.11 drivers [ 2.347864] 9pnet: Installing 9P2000 support [ 2.352169] tsn generic netlink module v1 init... [ 2.357961] registered taskstats version 1 [ 2.362078] Loading compiled-in X.509 certificates [ 2.367003] Key type ._fscrypt registered [ 2.371023] Key type .fscrypt registered [ 2.374950] Key type fscrypt-provisioning registered [ 2.384645] i2c i2c-0: IMX I2C adapter registered [ 2.390402] adv7511 1-003d: 1-003d supply avdd not found, using dummy regulator [ 2.397803] adv7511 1-003d: 1-003d supply dvdd not found, using dummy regulator [ 2.405134] adv7511 1-003d: 1-003d supply pvdd not found, using dummy regulator [ 2.412464] adv7511 1-003d: 1-003d supply a2vdd not found, using dummy regulator [ 2.419883] adv7511 1-003d: 1-003d supply v3p3 not found, using dummy regulator [ 2.427227] adv7511 1-003d: 1-003d supply v1p2 not found, using dummy regulator [ 2.436243] adv7511 1-003d: Probe failed. Remote port 'mipi_dsi@32e60000' disabled [ 2.444589] i2c i2c-1: IMX I2C adapter registered [ 2.450457] pca953x 2-0020: using no AI [ 2.455251] pca953x 2-0020: failed writing register [ 2.467882] nvmem pcf85063_nvram0: nvmem: invalid reg on /soc@0/bus@30800000/i2c@30a40000/rtc@51/clock [ 2.483902] rtc rtc1: Power loss detected, invalid time [ 2.489497] rtc-pcf85063 2-0051: registered as rtc1 [ 2.494436] i2c i2c-2: IMX I2C adapter registered [ 2.500085] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SD1_CLK already requested by 30860000.serial; cannot claim for 30b40000.mmc [ 2.512449] imx8mp-pinctrl 30330000.pinctrl: pin-35 (30b40000.mmc) status -22 [ 2.519598] imx8mp-pinctrl 30330000.pinctrl: could not request pin 35 (MX8MP_IOMUXC_SD1_CLK) from group usdhc1grp on device 30330000.pinctrl [ 2.532318] sdhci-esdhc-imx 30b40000.mmc: Error applying setting, reverse things back [ 2.540175] sdhci-esdhc-imx: probe of 30b40000.mmc failed with error -22 [ 2.548202] imx-dwmac 30bf0000.ethernet: IRQ eth_lpi not found [ 2.554176] imx-dwmac 30bf0000.ethernet: no reset control found [ 2.560913] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51 [ 2.567720] imx-dwmac 30bf0000.ethernet: DWMAC4/5 [ 2.572522] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported [ 2.579667] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported [ 2.586808] imx-dwmac 30bf0000.ethernet: TX Checksum insertion supported [ 2.593518] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported [ 2.599647] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 2.607321] imx-dwmac 30bf0000.ethernet: device MAC address 7e:46:32:ef:7e:37 [ 2.614471] imx-dwmac 30bf0000.ethernet: Enabled Flow TC (entries=8) [ 2.620843] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max_off=256) [ 2.628566] libphy: stmmac: probed [ 2.632216] mdio_bus stmmac-1: MDIO device at address 1 is missing. [ 2.654401] imx8mq-usb-phy 381f0040.usb-phy: 381f0040.usb-phy supply vbus not found, using dummy regulator [ 2.664384] imx8mq-usb-phy 382f0040.usb-phy: 382f0040.usb-phy supply vbus not found, using dummy regulator [ 2.674860] pwm-backlight lvds_backlight: aaaaaaaaaaaaaaaaaaaaaa [ 2.680888] pwm-backlight lvds_backlight: bbbbbbbbbbbbbbbbbbbbbbb [ 2.686988] pwm-backlight lvds_backlight: cccccccccccccccccccccccc [ 2.693178] pwm-backlight lvds_backlight: dddddddddddddddddddddd [ 2.699211] pwm-backlight lvds_backlight: eeeeeeeeeeeeeeeeeeee [ 2.705061] pwm-backlight lvds_backlight: lvds_backlight supply power not found, using dummy regulator [ 2.714430] pwm-backlight lvds_backlight: gggggggggggggggggggggg [ 2.720500] pwm-backlight lvds_backlight: hhhhhhhhhhhhhhhhhhhhhhh [ 2.726606] pwm-backlight lvds_backlight: iiiiiiiiiiiiiiiiiiiiiii [ 2.732715] pwm-backlight lvds_backlight: jjjjjjjjjjjjjjjjjjjjj [ 2.738674] pwm-backlight lvds_backlight: kkkkkkkkkkkkkkkkkkkkk [ 2.744663] pwm-backlight lvds_backlight: llllllllllllllllll [ 2.756906] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.763562] [drm] No driver support for vblank timestamp query. [ 2.769555] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 2.777523] imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops) [ 2.785486] imx-drm display-subsystem: bound imx-lcdifv3-crtc.2 (ops lcdifv3_crtc_ops) [ 2.793504] imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200 [ 2.800520] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi [ 2.808799] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19 [ 2.816470] imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops) [ 2.828193] panel-lvds lvds0_panel: 11111111111111 width-mm DT property [ 2.834866] panel-lvds lvds0_panel: 22222222222 width-mm DT property [ 2.841242] panel-lvds lvds0_panel: 333333333333 width-mm DT property [ 2.847738] panel-lvds lvds0_panel: 44444444444 width-mm DT property [ 2.854127] panel-lvds lvds0_panel: 55555555555555 width-mm DT property [ 2.860765] panel-lvds lvds0_panel: 6666666666666 width-mm DT property [ 2.867895] OF: graph: no port node found in /usb-phy@381f0040 [ 2.874515] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 2.880033] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1 [ 2.888052] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000002001810010 [ 2.897492] xhci-hcd xhci-hcd.1.auto: irq 69, io mem 0x38200000 [ 2.903561] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.911848] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.919083] usb usb1: Product: xHCI Host Controller [ 2.923969] usb usb1: Manufacturer: Linux 5.4.70 xhci-hcd [ 2.929376] usb usb1: SerialNumber: xhci-hcd.1.auto [ 2.934977] hub 1-0:1.0: USB hub found [ 2.938762] hub 1-0:1.0: 1 port detected [ 2.942938] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 2.948445] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2 [ 2.956134] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed [ 2.962730] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 2.970936] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 [ 2.979208] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.986439] usb usb2: Product: xHCI Host Controller [ 2.991330] usb usb2: Manufacturer: Linux 5.4.70 xhci-hcd [ 2.996735] usb usb2: SerialNumber: xhci-hcd.1.auto [ 3.002458] hub 2-0:1.0: USB hub found [ 3.006247] hub 2-0:1.0: 1 port detected [ 3.010740] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 7 mkt segment 2 supported-hw 0x80 0x4 [ 3.020530] imx-micfil sound-micfil: ASoC: failed to init link micfil hifi: -517 [ 3.027944] imx-micfil sound-micfil: snd_soc_register_card failed (-517) [ 3.035275] imx-cdnhdmi sound-hdmi: ASoC: failed to init link imx8 hdmi: -517 [ 3.042426] imx-cdnhdmi sound-hdmi: snd_soc_register_card failed (-517) [ 3.049774] imx-xcvr sound-xcvr: snd-soc-dummy-dai <-> 30cc0000.xcvr mapping ok [ 3.057106] imx-xcvr sound-xcvr: ASoC: no DMI vendor name! [ 3.067515] spi_imx 30830000.spi: probed [ 3.073457] pca9450 0-0025: Device ID=0x31 [ 3.077570] pca9450 0-0025: gpio_intr = 3 [ 3.081588] pca9450 0-0025: chip_irq=74 [ 3.155658] random: fast init done [ 3.175508] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_GPIO1_IO15 already requested by 30670000.pwm; cannot claim for 1-003c [ 3.187356] imx8mp-pinctrl 30330000.pinctrl: pin-20 (1-003c) status -22 [ 3.193987] imx8mp-pinctrl 30330000.pinctrl: could not request pin 20 (MX8MP_IOMUXC_GPIO1_IO15) from group csi_mclk_grp on device 30330000.pinctrl [ 3.207206] ov5640 1-003c: Error applying setting, reverse things back [ 3.213754] ov5640: probe of 1-003c failed with error -22 [ 3.225436] wm8960 2-0034: Failed to issue reset [ 3.235935] rpmsg-audio-codec-wm8960 2-0034: Failed to issue reset [ 3.243295] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO [ 3.278992] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 3.280297] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA [ 3.298940] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 45 [ 3.304195] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 46 [ 3.309441] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 47 [ 3.314688] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 48 [ 3.323324] imx6q-pcie 33800000.pcie: 33800000.pcie supply epdev_on not found, using dummy regulator [ 3.323334] reg-fixed-voltage regulator-usb4-vbus: nonexclusive access to GPIO for regulator-usb4-vbus [ 3.332729] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!. [ 3.341994] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SAI2_RXD0 already requested by regulator-usb4-vbus; cannot claim for regulator-usb3-vbus [ 3.347966] imx6q-pcie 33800000.pcie: PCIe PHY PLL clock is locked. [ 3.360859] imx8mp-pinctrl 30330000.pinctrl: pin-105 (regulator-usb3-vbus) status -22 [ 3.360865] imx8mp-pinctrl 30330000.pinctrl: could not request pin 105 (MX8MP_IOMUXC_SAI2_RXD0) from group usb1grp on device 30330000.pinctrl [ 3.360870] reg-fixed-voltage regulator-usb3-vbus: Error applying setting, reverse things back [ 3.360884] reg-fixed-voltage: probe of regulator-usb3-vbus failed with error -22 [ 3.404582] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SAI2_RXD0 already requested by regulator-usb4-vbus; cannot claim for regulator-usb2-vbus [ 3.415777] pcie phy pipe clk is not ready [ 3.418075] imx8mp-pinctrl 30330000.pinctrl: pin-105 (regulator-usb2-vbus) status -22 [ 3.422161] phy phy-32f00000.pcie-phy.5: phy init failed --> -110 [ 3.429993] imx8mp-pinctrl 30330000.pinctrl: could not request pin 105 (MX8MP_IOMUXC_SAI2_RXD0) from group usb1grp on device 30330000.pinctrl [ 3.429997] reg-fixed-voltage regulator-usb2-vbus: Error applying setting, reverse things back [ 3.436117] imx6q-pcie 33800000.pcie: Waiting for PHY PLL ready timeout! [ 3.448887] reg-fixed-voltage: probe of regulator-usb2-vbus failed with error -22 [ 3.472322] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SAI2_RXD0 already requested by regulator-usb4-vbus; cannot claim for regulator-usb1-vbus [ 3.478038] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout [ 3.485811] imx8mp-pinctrl 30330000.pinctrl: pin-105 (regulator-usb1-vbus) status -22 [ 3.491464] imx6q-pcie 33800000.pcie: host bridge /pcie@33800000 ranges: [ 3.499220] imx8mp-pinctrl 30330000.pinctrl: could not request pin 105 (MX8MP_IOMUXC_SAI2_RXD0) from group usb1grp on device 30330000.pinctrl [ 3.505958] imx6q-pcie 33800000.pcie: No bus range found for /pcie@33800000, using [bus 00-ff] [ 3.518724] reg-fixed-voltage regulator-usb1-vbus: Error applying setting, reverse things back [ 3.527842] imx6q-pcie 33800000.pcie: IO 0x1ff80000..0x1ff8ffff -> 0x00000000 [ 3.528112] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3 [ 3.528120] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3.536116] reg-fixed-voltage: probe of regulator-usb1-vbus failed with error -22 [ 3.543526] imx6q-pcie 33800000.pcie: MEM 0x18000000..0x1fefffff -> 0x18000000 [ 3.552546] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_ECSPI2_SS0 already requested by 30830000.spi; cannot claim for regulator-rtc-en [ 3.571709] hub 1-1:1.0: USB hub found [ 3.573724] imx8mp-pinctrl 30330000.pinctrl: pin-127 (regulator-rtc-en) status -22 [ 3.587067] hub 1-1:1.0: 4 ports detected [ 3.590172] imx8mp-pinctrl 30330000.pinctrl: could not request pin 127 (MX8MP_IOMUXC_ECSPI2_SS0) from group rtcreggrp on device 30330000.pinctrl [ 3.614781] reg-fixed-voltage regulator-rtc-en: Error applying setting, reverse things back [ 3.623164] reg-fixed-voltage: probe of regulator-rtc-en failed with error -22 [ 3.631132] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_ECSPI2_MISO already requested by 30830000.spi; cannot claim for regulator-sd2-vsel [ 3.644102] imx8mp-pinctrl 30330000.pinctrl: pin-126 (regulator-sd2-vsel) status -22 [ 3.651862] imx8mp-pinctrl 30330000.pinctrl: could not request pin 126 (MX8MP_IOMUXC_ECSPI2_MISO) from group sd2vselgrp on device 30330000.pinctrl [ 3.665086] reg-fixed-voltage regulator-sd2-vsel: Error applying setting, reverse things back [ 3.673626] reg-fixed-voltage: probe of regulator-sd2-vsel failed with error -22 [ 3.683227] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 3.689860] [drm] No driver support for vblank timestamp query. [ 3.695843] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 3.703798] imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops) [ 3.711761] imx-drm display-subsystem: bound imx-lcdifv3-crtc.2 (ops lcdifv3_crtc_ops) [ 3.719811] imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200 [ 3.726396] Hot alarm is canceled. GPU3D clock will return to 64/64 [ 3.726844] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi [ 3.741328] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19 [ 3.749001] imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops) [ 3.756928] imx-drm display-subsystem: bound 32c00000.bus:ldb@32ec005c (ops imx8mp_ldb_ops) [ 3.765498] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2) [ 3.776543] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver [ 3.787290] imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw_hdmi_imx_ops) [ 3.795561] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 3.854942] Console: switching to colour frame buffer device 160x50 [ 3.876866] imx-drm display-subsystem: fb0: imx-drmdrmfb frame buffer device [ 3.894739] imx-micfil sound-micfil: snd-soc-dummy-dai <-> 30ca0000.micfil mapping ok [ 3.902602] imx-micfil sound-micfil: ASoC: no DMI vendor name! [ 3.909889] imx-cdnhdmi sound-hdmi: i2s-hifi <-> 30cb0000.aud2htx mapping ok [ 3.916973] imx-cdnhdmi sound-hdmi: ASoC: no DMI vendor name! [ 3.923539] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card2/input1 [ 3.936137] isi-m2m 32e00000.isi:m2m_device: Register m2m success for ISI.0 [ 3.943234] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 3.956605] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 3.963238] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 3.971866] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 3.988180] mx8-img-md: Registered mxc_isi.0.capture as /dev/video1 [ 3.994611] unregister ISI channel: mxc_isi.0 [ 3.999832] ALSA device list: [ 4.002832] #0: imx-audio-xcvr [ 4.006061] #1: imx-audio-micfil [ 4.009500] #2: audio-hdmi [ 4.559295] imx6q-pcie 33800000.pcie: Phy link never came up [ 4.564996] imx6q-pcie 33800000.pcie: failed to initialize host [ 4.570954] imx6q-pcie 33800000.pcie: unable to add pcie port. [ 4.579502] Freeing unused kernel memory: 4416K [ 4.584124] Run /init as init process [ 4.615576] init: init first stage started! [ 4.620061] init: Switching root to '/first_stage_ramdisk' [ 4.627770] init: Using Android DT directory /proc/device-tree/firmware/android/ [ 4.666891] init: [libfs_mgr]Created logical partition system_a on device /dev/block/dm-0 [ 4.675120] init: [libfs_mgr]Skipping zero-length logical partition: system_b [ 4.684424] init: [libfs_mgr]Created logical partition vendor_a on device /dev/block/dm-1 [ 4.692721] init: [libfs_mgr]Skipping zero-length logical partition: vendor_b [ 4.700948] init: [libfs_mgr]Created logical partition product_a on device /dev/block/dm-2 [ 4.709248] init: [libfs_mgr]Skipping zero-length logical partition: product_b [ 4.719499] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/by-name/metadata [ 4.731226] EXT4-fs (mmcblk2p6): warning: mounting unchecked fs, running e2fsck is recommended [ 4.740441] EXT4-fs (mmcblk2p6): mounted filesystem without journal. Opts: discard [ 4.758741] device-mapper: verity: sha1 using implementation "sha1-ce" [ 4.770638] EXT4-fs (dm-3): mounted filesystem without journal. Opts: errors=panic,barrier=1,inode_readahead_blks=8 [ 4.789439] device-mapper: verity: sha1 using implementation "sha1-ce" [ 4.801749] EXT4-fs (dm-4): mounted filesystem without journal. Opts: errors=panic,barrier=1,inode_readahead_blks=8 [ 4.813824] device-mapper: verity: sha1 using implementation "sha1-ce" [ 4.827263] EXT4-fs (dm-5): mounted filesystem without journal. Opts: errors=panic,barrier=1,inode_readahead_blks=8 [ 4.855174] printk: init: 21 output lines suppressed due to ratelimiting [ 4.873812] random: init: uninitialized urandom read (40 bytes read) [ 5.030090] random: init: uninitialized urandom read (40 bytes read) [ 5.055733] init: Loading SELinux policy [ 5.096641] SELinux: Permission nlmsg_readpriv in class netlink_route_socket not defined in policy. [ 5.106121] SELinux: the above unknown classes and permissions will be denied [ 5.113311] SELinux: policy capability network_peer_controls=1 [ 5.119234] SELinux: policy capability open_perms=1 [ 5.124200] SELinux: policy capability extended_socket_class=1 [ 5.130122] SELinux: policy capability always_check_network=0 [ 5.135956] SELinux: policy capability cgroup_seclabel=0 [ 5.141356] SELinux: policy capability nnp_nosuid_transition=1 [ 5.229817] audit: type=1403 audit(13.056:2): auid=4294967295 ses=4294967295 lsm=selinux res=1 [ 5.229854] selinux: SELinux: Loaded policy from /vendor/etc/selinux/precompiled_sepolicy [ 5.229854] [ 5.257929] selinux: SELinux: Loaded file_contexts [ 5.257929] [ 5.269706] random: init: uninitialized urandom read (40 bytes read) [ 5.309469] init: init second stage started! [ 5.341372] init: Using Android DT directory /proc/device-tree/firmware/android/ [ 5.353855] selinux: SELinux: Loaded file_contexts [ 5.353855] [ 5.360210] init: Running restorecon... [ 5.384418] init: Overriding previous 'ro.' property 'pm.dexopt.boot':'verify' with new value 'quicken' [ 5.396721] init: Couldn't load property file '/product_services/build.prop': open() failed: No such file or directory: No such file or directory [ 5.409834] init: Couldn't load property file '/factory/factory.prop': open() failed: No such file or directory: No such file or directory [ 5.424334] init: Setting product property ro.product.brand to 'Android' (from ro.product.product.brand) [ 5.433862] init: Setting product property ro.product.device to 'evk_8mp' (from ro.product.product.device) [ 5.443560] init: Setting product property ro.product.manufacturer to 'freescale' (from ro.product.product.manufacturer) [ 5.588309] ueventd: ueventd started! [ 5.595405] selinux: SELinux: Loaded file_contexts [ 5.595405] [ 5.601997] ueventd: Parsing file /ueventd.rc... [ 5.607871] ueventd: Parsing file /vendor/ueventd.rc... [ 5.614863] ueventd: Parsing file /odm/ueventd.rc... [ 5.620044] ueventd: Unable to read config file '/odm/ueventd.rc': open() failed: No such file or directory [ 5.620658] apexd: Bootstrap subcommand detected [ 5.629864] ueventd: Parsing file /ueventd.freescale.rc... [ 5.640068] ueventd: Unable to read config file '/ueventd.freescale.rc': open() failed: No such file or directory [ 5.823101] ueventd: firmware: loading 'regulatory.db' for '/devices/platform/regulatory.0/firmware/regulatory.db' [ 5.830381] ueventd: firmware: loading 'imx/sdma/sdma-imx7d.bin' for '/devices/platform/soc@0/30800000.bus/30bd0000.dma-controller/firmware/imx!sdma!sdma-imx7d.bin' [ 5.842111] apexd: wait for '/dev/loop-control' took 170ms [ 5.854176] apexd: Pre-allocated 9 loopback devices [ 5.857406] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5 [ 5.859661] apexd: Scanning /system/apex for embedded keys [ 5.873197] apexd: Scanning /product/apex for embedded keys [ 5.879013] apexd: ... does not exist. Skipping [ 5.883675] apexd: Scanning /system/apex looking for APEX packages. [ 5.890177] apexd: Found /system/apex/com.android.conscrypt.apex [ 5.896773] apexd: Skipped when bootstrapping [ 5.901300] apexd: Found /system/apex/com.android.runtime.debug.apex [ 5.990229] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null) [ 6.065499] EXT4-fs (loop1): mounted filesystem without journal. Opts: (null) [ 6.078921] printk: apexd: 13 output lines suppressed due to ratelimiting [ 6.194159] Registered swp emulation handler [ 6.229608] Console: switching to colour dummy device 80x25 [ 6.245412] watchdogd: watchdogd started (interval 10, margin 20)! [ 6.252055] watchdogd: Failed to open /dev/watchdog: No such file or directory [ 6.292389] logd.auditd: start [ 6.297725] logd.klogd: 6187058250 [ 6.344294] usbcore: registered new interface driver rtk_btusb [ 6.400504] zram0: detected capacity change from 0 to 629145600 [ 6.403018] vvcam_video: loading out-of-tree module taints kernel. [ 6.413714] enter viv_video_init_module [ 6.430540] mkswap: Swapspace size: 614396k, UUID=1839bbda-a0e1-41ad-b8fd-80cf76215e06 [ 6.455206] enter viv_isp_init_module [ 6.458752] Adding 614396k swap on /dev/block/zram0. Priority:-2 extents:1 across:614396k SS [ 6.489640] enter viv_dwe_init_module [ 6.572752] type=1400 audit(14.400:3): avc: denied { search } for comm="android.hardwar" name="/" dev="mmcblk2p6" ino=2 scontext=u:r:hal_bootctl_default:s0 tcontext=u:object_r:metadata_file:s0 tclass=dir permissive=1 [ 6.592182] type=1400 audit(14.400:3): avc: denied { search } for comm="android.hardwar" name="/" dev="mmcblk2p6" ino=2 scontext=u:r:hal_bootctl_default:s0 tcontext=u:object_r:metadata_file:s0 tclass=dir permissive=1 [ 6.611451] type=1400 audit(14.400:4): avc: denied { search } for comm="android.hardwar" name="gsi" dev="mmcblk2p6" ino=16 scontext=u:r:hal_bootctl_default:s0 tcontext=u:object_r:gsi_metadata_file:s0 tclass=dir permissive=1 [ 9.301272] random: crng init done [ 9.304683] random: 7 urandom warning(s) missed due to ratelimiting [ 11.166976] init: Calling: /system/bin/vdc checkpoint needsCheckpoint [ 11.196453] init: /dev/block/by-name/userdata is not dm device: No such file or directory [ 11.205523] type=1400 audit(14.400:4): avc: denied { search } for comm="android.hardwar" name="gsi" dev="mmcblk2p6" ino=16 scontext=u:r:hal_bootctl_default:s0 tcontext=u:object_r:gsi_metadata_file:s0 tclass=dir permissive=1 [ 11.225437] type=1400 audit(19.032:5): avc: denied { create } for comm="kdevtmpfs" name="dm-6" scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 11.241480] type=1400 audit(19.032:5): avc: denied { create } for comm="kdevtmpfs" name="dm-6" scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 11.257240] type=1400 audit(19.032:6): avc: denied { setattr } for comm="kdevtmpfs" name="dm-6" dev="devtmpfs" ino=259 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 11.261452] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/dm-6 [ 11.282321] init: [libfs_mgr]Filesystem on /dev/block/dm-6 was not cleanly shutdown; state flags: 0x1, incompat feature flags: 0x10046 [ 11.295483] EXT4-fs (dm-6): Ignoring removed nomblk_io_submit option [ 11.308061] EXT4-fs (dm-6): recovery complete [ 11.312460] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit [ 11.322803] init: [libfs_mgr]check_fs(): mount(/dev/block/dm-6,/data,ext4)=0: Success [ 11.344142] init: [libfs_mgr]check_fs(): unmount(/data) succeeded [ 11.350511] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/dm-6 [ 12.208005] e2fsck: e2fsck 1.44.4 (18-Aug-2018) [ 12.208005] [ 12.214257] e2fsck: Pass 1: Checking inodes, blocks, and sizes [ 12.214257] [ 12.221593] e2fsck: Pass 2: Checking directory structure [ 12.221593] [ 12.228397] e2fsck: Pass 3: Checking directory connectivity [ 12.228397] [ 12.235483] e2fsck: Pass 4: Checking reference counts [ 12.235483] [ 12.242027] e2fsck: Pass 5: Checking group summary information [ 12.242027] [ 12.249412] e2fsck: /dev/block/dm-6: 11/383520 files (0.0% non-contiguous), 43458/1531904 blocks [ 12.249412] [ 12.262962] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/dm-6 [ 12.270187] init: [libfs_mgr]Reserved blocks 32768 is too large; capping to 30638 [ 12.278488] EXT4-fs (dm-6): Ignoring removed nomblk_io_submit option [ 12.289376] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic [ 12.300575] init: [libfs_mgr]__mount(source=/dev/block/dm-6,target=/data,type=ext4)=0: Success [ 12.326738] watchdogd: watchdogd started (interval 10, margin 20)! [ 12.333094] watchdogd: Failed to open /dev/watchdog: No such file or directory [ 12.351440] device-mapper: bow: Switching to state Checkpoint [ 12.824103] init (pid 1) is setting deprecated v1 encryption policy; recommend upgrading to v2. [ 12.873926] fscrypt: AES-256-CTS-CBC using implementation "cts-cbc-aes-ce" [ 12.952712] fscrypt: AES-256-XTS using implementation "xts-aes-ce" [ 12.965509] apexd: Marking APEXd as starting [ 12.971175] apexd: Scanning /system/apex for embedded keys [ 12.980847] apexd: Scanning /product/apex for embedded keys [ 13.054212] EXT4-fs (loop2): mounted filesystem without journal. Opts: (null) [ 13.121384] EXT4-fs (loop3): mounted filesystem without journal. Opts: (null) [ 13.201140] EXT4-fs (loop4): mounted filesystem without journal. Opts: (null) [ 13.278465] EXT4-fs (loop5): mounted filesystem without journal. Opts: (null) [ 13.369859] EXT4-fs (loop6): mounted filesystem without journal. Opts: (null) [ 13.446070] EXT4-fs (loop7): mounted filesystem without journal. Opts: (null) [ 13.540168] EXT4-fs (loop8): mounted filesystem without journal. Opts: (null) [ 17.487386] init: Command 'load_persist_props' action=load_persist_props_action (/init.rc:306) took 1573ms and succeeded [ 17.498409] init: starting service 'watchdogd'... [ 17.504934] init: Service 'exec 9 (/system/bin/recovery-persist)' (pid 292) exited with status 0 [ 17.514329] init: starting service 'logd-reinit'... [ 17.515365] watchdogd: watchdogd started (interval 10, margin 20)! [ 17.521007] init: processing action (load_persist_props_action) from (/system/etc/init/flags_health_check.rc:1) [ 17.525576] watchdogd: Failed to open /dev/watchdog: No such file or directory [ 17.543363] init: Setting policy on /data/server_configurable_flags [ 17.549900] init: Policy for /data/server_configurable_flags set to 15cd3c2eedde1152 modes 1/4 [ 17.558841] init: Service 'watchdogd' (pid 294) exited with status 1 [ 17.564727] logd.daemon: reinit [ 17.565318] init: Sending signal 9 to service 'watchdogd' (pid 294) process group... [ 17.576279] libprocessgroup: Successfully killed process cgroup uid 0 pid 294 in 0ms [ 17.727752] update_verifier: Started with arg 1: nonencrypted [ 17.737000] update_verifier: Booting slot 0: isSlotMarkedSuccessful=0 [ 17.743599] update_verifier: /data/ota_package/care_map.pb doesn't exist [ 17.750332] update_verifier: Failed to parse the care map file, skipping verification [ 17.759028] update_verifier: Deferred marking slot 0 as booted successfully. [ 17.766136] update_verifier: Leaving update_verifier. [ 17.801249] type=1400 audit(19.032:6): avc: denied { setattr } for comm="kdevtmpfs" name="dm-6" dev="devtmpfs" ino=259 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 17.819167] type=1400 audit(25.628:7): avc: denied { setattr } for comm="init" name="wifi" dev="dm-6" ino=16343 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 17.837972] type=1400 audit(25.628:7): avc: denied { setattr } for comm="init" name="wifi" dev="dm-6" ino=16343 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 17.855959] type=1400 audit(25.628:8): avc: denied { search } for comm="init" name="wifi" dev="dm-6" ino=16343 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 17.873981] type=1400 audit(25.628:8): avc: denied { search } for comm="init" name="wifi" dev="dm-6" ino=16343 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 17.891921] type=1400 audit(25.636:9): avc: denied { setattr } for comm="init" name="dhcp" dev="dm-6" ino=16347 scontext=u:r:vendor_init:s0 tcontext=u:object_r:dhcp_data_file:s0 tclass=dir permissive=1 [ 18.288744] Mass Storage Function, version: 2009/09/11 [ 18.293986] LUN: removable file: (no medium) [ 18.300648] using random self ethernet address [ 18.305189] using random host ethernet address [ 18.312666] file system registered [ 18.785370] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a [ 18.814364] watchdogd: watchdogd started (interval 10, margin 20)! [ 18.833075] watchdogd: Failed to open /dev/watchdog: No such file or directory [ 18.854269] type=1400 audit(25.636:9): avc: denied { setattr } for comm="init" name="dhcp" dev="dm-6" ino=16347 scontext=u:r:vendor_init:s0 tcontext=u:object_r:dhcp_data_file:s0 tclass=dir permissive=1 [ 18.890064] init: Setting policy on /data/eGalax [ 18.901792] init: Policy for /data/eGalax set to 15cd3c2eedde1152 modes 1/4 [ 18.951266] isi-m2m 32e00000.isi:m2m_device: ISI channel[0] is busy [ 18.975692] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a [ 19.012033] isi-m2m 32e00000.isi:m2m_device: ISI channel[0] is busy [ 19.063087] type=1400 audit(26.680:10): avc: denied { setattr } for comm="init" name="bluetooth" dev="dm-6" ino=16327 scontext=u:r:vendor_init:s0 tcontext=u:object_r:bluetooth_data_file:s0 tclass=dir permissive=1 evk_8mp:/ $ [ 19.743098] type=1400 audit(26.680:10): avc: denied { setattr } for comm="init" name="bluetooth" dev="dm-6" ino=16327 scontext=u:r:vendor_init:s0 tcontext=u:object_r:bluetooth_data_file:s0 tclass=dir permissive=1 [ 19.855768] read descriptors [ 19.868579] read strings [ 20.553363] printk: Binder:260_1: 99 output lines suppressed due to ratelimiting [ 20.564030] binder: release 320:320 transaction 809 in, still active [ 20.568042] kvm: exiting hardware virtualization [ 20.570716] binder: send failed reply for transaction 809 to 337:337 [ 20.606405] trusty-virtio trusty:trusty-virtio: removing Android i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: IMX8MP Self Designed Board system crash after booting in the system The log is the first time booting. But when I reboot the system again, it will generate another log as below. U-Boot SPL 2020.04 (Aug 10 2026 - 12:59:20 +0800) DDRINFO: start DRAM init DDRINFO: DRAM rate 3200MTS DDRINFO:ddrphy calibration done DDRINFO: ddrmix config done Normal Boot Trying to boot from MMC2 Authentication key not yet programmed keyslot package magic error, do nothing here! NOTICE: BL31: v2.2(release):fc5b00e8fa-dirty NOTICE: BL31: Built : 12:59:31, Aug 10 2026 welcome to lk/MP boot args 0x2000000 0x56000000 0x2000 0x0 initializing trusty (Built: 12:16:06 Nov 19 2020) Initializing Trusted OS SMC handler avb: Initializing AVB App hwcrypto: Initializing hwrng_caam: Init HWRNG service provider hwrng_srv: Start HWRNG service hwcrypto_caam: Init HWCRYPTO service provider hwcrypto_srv: Start HWCRYPTO service hwkey_caam: Init HWKEY service provider hwkey_caam: 183: Invalid magic, unpack key package fail. hwkey_srv: Start HWKEY service hwcrypto: enter main event loop trusty_gatekeeper: Initializing U-Boot 2020.04 (Aug 10 2026 - 12:59:20 +0800) CPU: i.MX8MP Lite[4] rev1.1 1600 MHz (running at 1200 MHz) CPU: Industrial temperature grade (-40C to 105C) at 48C Reset cause: POR Model: NXP i.MX8MPlus abcd LPDDR4 EVK board DRAM: 4 GiB tcpc_init: Can't find device id=0x50 setup_typec: tcpc port2 init failed, err=-19 tcpc_init: Can't find device id=0x50 setup_typec: tcpc port1 init failed, err=-19 MMC: FSL_SDHC: 1, FSL_SDHC: 2 Loading Environment from MMC... *** Warning - bad CRC, using default environment [*]-Video Link 0Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings probe video device failed, ret -19 [0] lcd-controller@32e80000, video [1] mipi_dsi@32e60000, video_bridge [2] adv7535@3d, panel Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings probe video device failed, ret -19 In: serial Out: serial Err: serial BuildInfo: - ATF - U-Boot 2020.04 flash target is MMC:2 Net: Error: ethernet@30bf0000 address not set. Error: ethernet@30bf0000 address not set. No ethernet found. INFO Initializing Trusty device INFO selected trusty api version: 3 (requested 3) ss: get_rpmb_auth_key: failed to get key: -2 ss: proxy_connect: can't get storage auth key: (-2) ss-ipc: 105: do_connect: failure initializing channel state (1001) rpmb_proxy.c:312: ERROR rpmb_storage_proxy_init: unexpected proxy channel close libtipc.c:92: ERROR Initlializing RPMB storage proxy service failed (-8) Authentication key not yet programmed Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_validate_vbmeta_public_key_rpmb: Read public key error avb_slot_verify.c:900: ERROR: vbmeta_a: Public key used to sign data rejected. avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized fsl_read_rollback_index_rpmb: read rollback from Trusty error! Authentication key not yet programmed avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized Writing A/B metadata to disk. verify FAIL, state: UNLOCK boot 'boot_a' still kernel @ 40480000 (36925952) ramdisk @ 44680000 (7268024) fdt @ 44480000 (65023) avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized Device is unlocked, press power key to skip warning logo... Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings no video device found! can't show unlock warning. avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized ERROR - failed to read public key for keymaster keymaster.c:318: ERROR Keymaster TIPC client not initialized! avb.c:86: ERROR avb_do_tipc: AVB TIPC client not initialized ipc_dev.c:306: ERROR trusty_ipc_dev_close: secure OS returned (-7) ## Flattened Device Tree blob at 44480000 Booting using the fdt blob at 0x44480000 Using Device Tree in place at 0000000044480000, end 0000000044492dfe Found /vpu_g1@38300000 node Modify /vpu_g1@38300000:status disabled Found /vpu_g2@38310000 node Modify /vpu_g2@38310000:status disabled Found /vpu_vc8000e@38320000 node Modify /vpu_vc8000e@38320000:status disabled Found /vipsi@38500000 node Modify /vipsi@38500000:status disabled Found /soc@0/bus@32c00000/camera/isp@32e10000 node Modify /soc@0/bus@32c00000/camera/isp@32e10000:status disabled Found /soc@0/bus@32c00000/camera/isp@32e20000 node Modify /soc@0/bus@32c00000/camera/isp@32e20000:status disabled Found /dsp@3b6e8000 node Modify /dsp@3b6e8000:status disabled Can't find cec device id=0x3c fail to probe panel device adv7535@3d fail to get display timings probe video device failed, ret -19 Starting kernel ... unable to select a mode device_remove: Device '[email protected]' failed to remove, but children are gone [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.4.70 (forenex@forenex20) (Android (5271481 based on r349610) clang version 8.0.8 (https://android.googlesource.com/toolchain/clang 4dba9ad555eabb40b39dc53c12d09423e9faea7b) (https://android.googlesource.com/toolchain/llvm ab552995647d484a712bf15f77e6c6f4e8ac532b) (based on LLVM 8.0.8svn), GNU ld (binutils-2.27-44492f8e) 2.27.0.20170315) #96 SMP PREEMPT Mon Aug 10 12:43:56 CST 2026 [ 0.000000] Machine model: NXP i.MX8MPlus EVK board [ 0.000000] earlycon: ec_imx6q0 at MMIO 0x0000000030890000 (options '115200') [ 0.000000] printk: bootconsole [ec_imx6q0] enabled [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: UEFI not found. [ 0.000000] OF: reserved mem: failed to allocate memory for node 'linux,cma' [ 0.000000] cma: Reserved 800 MiB at 0x0000000060000000 [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000017fffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x17f7cc500-0x17f7cdfff] [ 0.000000] Zone ranges: [ 0.000000] DMA32 [mem 0x0000000040000000-0x00000000ffffffff] [ 0.000000] Normal [mem 0x0000000100000000-0x000000017fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x00000000557fffff] [ 0.000000] node 0: [mem 0x0000000058000000-0x00000000923fffff] [ 0.000000] node 0: [mem 0x0000000094410000-0x00000000bfffffff] [ 0.000000] node 0: [mem 0x0000000100000000-0x000000017fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000017fffffff] [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.1 [ 0.000000] percpu: Embedded 32 pages/cpu s93400 r8192 d29480 u131072 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] Speculative Store Bypass Disable mitigation not required [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1014032 [ 0.000000] Policy zone: Normal [ 0.000000] Kernel command line: console=ttymxc1,115200 earlycon=ec_imx6q,0x30890000,115200 init=/init androidboot.console=ttymxc1 androidboot.hardware=freescale firmware_class.path=/vendor/firmware loop.max_part=7 transparent_hugepage=never androidboot.lcd_density=240 androidboot.primary_display=imx-drm androidboot.wificountrycode=CN androidboot.selinux=permissive cma=800M@0x400M-0xb80M buildvariant=userdebug androidboot.serialno=0926980055347a54 androidboot.btmacaddr=09:26:98:00:55:34 androidboot.soc_type=imx8mp androidboot.boot_device_root=mmcblk2 androidboot.boottime=1BLL:0,1BLE:4324,KL:0,KD:0,AVB:664,ODT:0,SW:0 androidboot.bootreason=cold,powerkey androidboot.verifiedbootstate=orange androidboot.flash.locked=0 androidboot.slot_suffix=_a androidboot.vbmeta.device=PARTUUID=a670210c-8754-426c-a5b2-440a72068e31 androidboot.vbmeta.avb_version=1.1 androidboot.vbmeta.device_state=unlocked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=3456 androidboot.vbmeta.digest=6f86b17aea6 [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0xbc000000-0xc0000000] (64MB) [ 0.000000] Memory: 3110948K/4120512K available (19388K kernel code, 1884K rwdata, 10296K rodata, 4416K init, 589K bss, 190364K reserved, 819200K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 160 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: no VLPI support, no direct LPI support [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000 [ 0.000000] ITS: No ITS available, not enabling LPIs [ 0.000000] random: get_random_bytes called from start_kernel+0x1e0/0x3a4 with crng_init=0 [ 0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns [ 0.000004] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [ 0.008572] Console: colour dummy device 80x25 [ 0.012575] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [ 0.022843] pid_max: default: 32768 minimum: 301 [ 0.027545] LSM: Security Framework initializing [ 0.032145] SELinux: Initializing. [ 0.035678] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.043065] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.052141] ASID allocator initialised with 32768 entries [ 0.056458] rcu: Hierarchical SRCU implementation. [ 0.062537] EFI services will not be available. [ 0.065940] smp: Bringing up secondary CPUs ... [ 0.070748] Detected VIPT I-cache on CPU1 [ 0.070770] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000 [ 0.070796] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.071291] Detected VIPT I-cache on CPU2 [ 0.071306] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000 [ 0.071322] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.071770] Detected VIPT I-cache on CPU3 [ 0.071786] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000 [ 0.071801] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.071861] smp: Brought up 1 node, 4 CPUs [ 0.126891] SMP: Total of 4 processors activated. [ 0.131608] CPU features: detected: 32-bit EL0 Support [ 0.136786] CPU features: detected: CRC32 instructions [ 0.141964] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching [ 0.150343] CPU: All CPU(s) started at EL2 [ 0.154457] alternatives: patching kernel code [ 0.160090] CPU3: update max cpu_capacity 1024 [ 0.161163] devtmpfs: initialized [ 0.171948] CPU2: update max cpu_capacity 1024 [ 0.178462] Initilizing CustomIPI irq domain [ 0.181852] Registered cp15_barrier emulation handler [ 0.186898] Registered setend emulation handler [ 0.191748] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.201257] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.230326] pinctrl core: initialized pinctrl subsystem [ 0.233494] DMI not present or invalid. [ 0.236946] NET: Registered protocol family 16 [ 0.241705] schedtune: configured to support 5 boost groups [ 0.253909] DMA: preallocated 256 KiB pool for atomic allocations [ 0.257210] audit: initializing netlink subsys (disabled) [ 0.262826] audit: type=2000 audit(0.188:1): state=initialized audit_enabled=0 res=1 [ 0.270413] cpuidle: using governor menu [ 0.275007] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.282273] Serial: AMBA PL011 UART driver [ 0.285327] imx mu driver is registered. [ 0.289209] imx rpmsg driver is registered. [ 0.330552] imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver [ 0.354998] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.358882] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [ 0.365610] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.372351] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 0.380069] cryptd: max_cpu_qlen set to 1000 [ 0.386706] ACPI: Interpreter disabled. [ 0.389562] iommu: Default domain type: Translated [ 0.392773] vgaarb: loaded [ 0.395630] SCSI subsystem initialized [ 0.399402] usbcore: registered new interface driver usbfs [ 0.404626] usbcore: registered new interface driver hub [ 0.410157] usbcore: registered new device driver usb [ 0.416056] mc: Linux media interface: v0.10 [ 0.419305] videodev: Linux video capture interface: v2.00 [ 0.424850] pps_core: LinuxPPS API ver. 1 registered [ 0.429781] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 0.438979] PTP clock support registered [ 0.443266] trusty trusty: trusty version: Built: 12:16:06 Nov 19 2020 [ 0.449481] trusty trusty: selected api version: 3 (requested 3) [ 0.461975] EDAC MC: Ver: 3.0.0 [ 0.463348] FPGA manager framework [ 0.465802] Advanced Linux Sound Architecture Driver Initialized. [ 0.472177] Bluetooth: Core ver 2.22 [ 0.475398] NET: Registered protocol family 31 [ 0.479853] Bluetooth: HCI device and connection manager initialized [ 0.486240] Bluetooth: HCI socket layer initialized [ 0.491140] Bluetooth: L2CAP socket layer initialized [ 0.496213] Bluetooth: SCO socket layer initialized [ 0.502473] clocksource: Switched to clocksource arch_sys_counter [ 0.581760] VFS: Disk quotas dquot_6.6.0 [ 0.582890] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.589906] pnp: PnP ACPI: disabled [ 0.599523] thermal_sys: Registered thermal governor 'step_wise' [ 0.599527] thermal_sys: Registered thermal governor 'power_allocator' [ 0.603101] NET: Registered protocol family 2 [ 0.614092] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear) [ 0.622278] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.630391] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear) [ 0.638013] TCP: Hash tables configured (established 32768 bind 32768) [ 0.644197] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.650910] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.658183] NET: Registered protocol family 1 [ 0.662794] PCI: CLS 0 bytes, default 64 [ 0.666544] Trying to unpack rootfs image as initramfs... [ 0.968860] Freeing initrd memory: 7096K [ 0.971029] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available [ 0.978177] kvm [1]: IPA Size Limit: 40bits [ 0.982797] kvm [1]: GICv3: no GICV resource entry [ 0.986748] kvm [1]: disabling GICv2 emulation [ 0.991201] kvm [1]: GIC system register CPU interface enabled [ 0.997133] kvm [1]: vgic interrupt IRQ1 [ 1.001111] kvm [1]: Hyp mode initialized successfully [ 1.009394] Initialise system trusted keyrings [ 1.011102] workingset: timestamp_bits=44 max_order=20 bucket_order=0 [ 1.023604] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.026737] Registering sdcardfs 0.1 [ 1.030372] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 1.036685] fuse: init (API version 7.31) [ 1.040636] 9p: Installing v9fs 9p2000 file system support [ 1.060571] Key type asymmetric registered [ 1.061815] Asymmetric key parser 'x509' registered [ 1.066755] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 1.074159] io scheduler mq-deadline registered [ 1.078713] io scheduler kyber registered [ 1.085722] /ubuntu20/imx8_data/imx8_an10/android_build/vendor/nxp-opensource/kernel_imx/drivers/gpio/dido.c dido_get_of_properties() line 65, cannot get device_node [ 1.108788] i.MX8MP clock driver probe done [ 1.114677] imx-sdma 30bd0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 [ 1.120214] mxs-dma 33000000.dma-apbh: initialized [ 1.122338] imx-sdma 30bd0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin [ 1.128691] Bus freq driver module loaded [ 1.145031] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.150879] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 28, base_baud = 5000000) is a IMX [ 1.157844] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 29, base_baud = 5000000) is a IMX [ 1.166555] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 30, base_baud = 1500000) is a IMX [ 1.175023] printk: console [ttymxc1] enabled [ 1.175023] printk: console [ttymxc1] enabled [ 1.183706] printk: bootconsole [ec_imx6q0] disabled [ 1.183706] printk: bootconsole [ec_imx6q0] disabled [ 1.214047] brd: module loaded [ 1.223859] loop: module loaded [ 1.227381] zram: Added device: zram0 [ 1.244283] imx ahci driver is registered. [ 1.252219] spi-nor spi0.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00 [ 1.259130] spi-nor: probe of spi0.0 failed with error -2 [ 1.266262] libphy: Fixed MDIO Bus: probed [ 1.271224] tun: Universal TUN/TAP device driver, 1.6 [ 1.277448] thunder_xcv, ver 1.0 [ 1.280720] thunder_bgx, ver 1.0 [ 1.283992] nicpf, ver 1.0 [ 1.288493] hclge is initializing [ 1.291822] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version [ 1.299048] hns3: Copyright (c) 2017 Huawei Corporation. [ 1.304400] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [ 1.311457] e1000: Copyright (c) 1999-2006 Intel Corporation. [ 1.317246] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k [ 1.323083] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.329075] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k [ 1.336049] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.341660] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k [ 1.349497] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.355640] sky2: driver version 1.30 [ 1.360226] PPP generic driver version 2.4.2 [ 1.364657] PPP BSD Compression module registered [ 1.369372] PPP Deflate Compression module registered [ 1.374450] PPP MPPE Compression module registered [ 1.379250] NET: Registered protocol family 24 [ 1.383697] PPTP driver version 0.8.5 [ 1.387587] usbcore: registered new interface driver r8152 [ 1.393116] usbcore: registered new interface driver asix [ 1.398569] usbcore: registered new interface driver ax88179_178a [ 1.404697] usbcore: registered new interface driver cdc_ether [ 1.410567] usbcore: registered new interface driver net1080 [ 1.416266] usbcore: registered new interface driver cdc_subset [ 1.422228] usbcore: registered new interface driver zaurus [ 1.427847] usbcore: registered new interface driver cdc_ncm [ 1.433690] VFIO - User Level meta-driver version: 0.3 [ 1.443948] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.450523] ehci-pci: EHCI PCI platform driver [ 1.455026] ehci-platform: EHCI generic platform driver [ 1.460530] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.466725] ohci-pci: OHCI PCI platform driver [ 1.471217] ohci-platform: OHCI generic platform driver [ 1.477425] usbcore: registered new interface driver uas [ 1.482795] usbcore: registered new interface driver usb-storage [ 1.488880] usbcore: registered new interface driver usbserial_generic [ 1.495435] usbserial: USB Serial support registered for generic [ 1.501487] usbcore: registered new interface driver ftdi_sio [ 1.507259] usbserial: USB Serial support registered for FTDI USB Serial Device [ 1.514605] usbcore: registered new interface driver usb_serial_simple [ 1.521158] usbserial: USB Serial support registered for carelink [ 1.527273] usbserial: USB Serial support registered for zio [ 1.532954] usbserial: USB Serial support registered for funsoft [ 1.538985] usbserial: USB Serial support registered for flashloader [ 1.545364] usbserial: USB Serial support registered for google [ 1.551306] usbserial: USB Serial support registered for libtransistor [ 1.557859] usbserial: USB Serial support registered for vivopay [ 1.563890] usbserial: USB Serial support registered for moto_modem [ 1.570178] usbserial: USB Serial support registered for motorola_tetra [ 1.576814] usbserial: USB Serial support registered for novatel_gps [ 1.583185] usbserial: USB Serial support registered for hp4x [ 1.588954] usbserial: USB Serial support registered for suunto [ 1.594898] usbserial: USB Serial support registered for siemens_mpi [ 1.601294] usbcore: registered new interface driver usb_ehset_test [ 1.610921] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0 [ 1.624304] usbcore: registered new interface driver xpad [ 1.629762] usbcore: registered new interface driver usb_acecad [ 1.635721] usbcore: registered new interface driver aiptek [ 1.641330] usbcore: registered new interface driver gtco [ 1.646767] usbcore: registered new interface driver hanwang [ 1.652467] usbcore: registered new interface driver kbtab [ 1.659881] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0 [ 1.666103] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T00:00:09 UTC (9) [ 1.675320] i2c /dev entries driver [ 1.680139] uvcvideo: Unable to create debugfs directory [ 1.685501] usbcore: registered new interface driver uvcvideo [ 1.691258] USB Video Class driver (1.1.1) [ 1.696261] __power_supply_register: Expected proper parent device for 'battery' [ 1.704023] __power_supply_register: Expected proper parent device for 'usb' [ 1.719391] trusty-virtio trusty:trusty-virtio: initializing [ 1.725244] trusty_ipc virtio0: vring0: va(pa) (____ptrval____)(0) qsz 32 notifyid 1 [ 1.733105] trusty_ipc virtio0: vring1: va(pa) (____ptrval____)(0) qsz 32 notifyid 2 [ 1.741162] trusty-virtio trusty:trusty-virtio: initializing done [ 1.741297] trusty_ipc virtio0: is online [ 1.748265] imx2-wdt 30280000.watchdog: timeout 60 sec (nowayout=0) [ 1.758108] device-mapper: uevent: version 1.0.3 [ 1.762979] device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: [email protected] [ 1.771659] Bluetooth: HCI UART driver ver 2.3 [ 1.776122] Bluetooth: HCI UART protocol H4 registered [ 1.781269] Bluetooth: HCI UART protocol BCSP registered [ 1.786614] Bluetooth: HCI UART protocol LL registered [ 1.791760] Bluetooth: HCI UART protocol ATH3K registered [ 1.797185] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 1.803657] Bluetooth: HCI UART protocol Broadcom registered [ 1.809341] Bluetooth: HCI UART protocol QCA registered [ 1.814878] EDAC MC: ECC not enabled [ 1.821131] sdhci: Secure Digital Host Controller Interface driver [ 1.827337] sdhci: Copyright(c) Pierre Ossman [ 1.831984] Synopsys Designware Multimedia Card Interface Driver [ 1.838884] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.845231] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SD1_CLK already requested by 30860000.serial; cannot claim for 30b40000.mmc [ 1.857594] imx8mp-pinctrl 30330000.pinctrl: pin-35 (30b40000.mmc) status -22 [ 1.864741] imx8mp-pinctrl 30330000.pinctrl: could not request pin 35 (MX8MP_IOMUXC_SD1_CLK) from group usdhc1grp on device 30330000.pinctrl [ 1.877442] sdhci-esdhc-imx 30b40000.mmc: Error applying setting, reverse things back [ 1.885297] sdhci-esdhc-imx: probe of 30b40000.mmc failed with error -22 [ 1.924707] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA [ 1.935293] ledtrig-cpu: registered to indicate activity on CPUs [ 1.942052] hidraw: raw HID events driver (C) Jiri Kosina [ 1.950140] usbcore: registered new interface driver usbhid [ 1.955731] usbhid: USB HID core driver [ 1.961117] mxc-isi 32e00000.isi: mxc_isi.0 registered successfully [ 1.968481] mxc-mipi-csi2-sam 32e40000.csi: 32e40000.csi supply mipi-phy not found, using dummy regulator [ 1.978376] mxc-mipi-csi2-sam 32e40000.csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 500000000 [ 1.990351] ashmem: initialized [ 1.997949] optee: probing for conduit method from DT. [ 2.003122] optee: api uid mismatch [ 2.008786] Galcore version 6.4.3.p1.305572 [ 2.055455] mmc2: new HS400 Enhanced strobe MMC card at address 0001 [ 2.062951] mmcblk2: mmc2:0001 AKL11X 115 GiB [ 2.067666] mmcblk2boot0: mmc2:0001 AKL11X partition 1 4.00 MiB [ 2.073836] mmcblk2boot1: mmc2:0001 AKL11X partition 2 4.00 MiB [ 2.080685] mmcblk2rpmb: mmc2:0001 AKL11X partition 3 4.00 MiB, chardev (236:0) [ 2.093403] Alternate GPT is invalid, using primary GPT. [ 2.098799] mmcblk2: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 [ 2.120362] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 0 [ 2.130834] usbcore: registered new interface driver snd-usb-audio [ 2.139047] OF: /sound-bt-sco/simple-audio-card,cpu: could not get #sound-dai-cells for /soc@0/bus@30c00000/spba-bus@30c00000/sai@30c20000 [ 2.151502] asoc-simple-card sound-bt-sco: parse error -22 [ 2.157006] asoc-simple-card: probe of sound-bt-sco failed with error -22 [ 2.169543] imx-micfil sound-micfil: ASoC: failed to init link micfil hifi: -517 [ 2.176958] imx-micfil sound-micfil: snd_soc_register_card failed (-517) [ 2.184216] imx-cdnhdmi sound-hdmi: ASoC: failed to init link imx8 hdmi: -517 [ 2.191366] imx-cdnhdmi sound-hdmi: snd_soc_register_card failed (-517) [ 2.198239] imx-xcvr sound-xcvr: ASoC: failed to init link XCVR PCM: -517 [ 2.205040] imx-xcvr sound-xcvr: snd_soc_register_card failed: -517 [ 2.211425] pktgen: Packet Generator for packet performance testing. Version: 2.75 [ 2.221559] drop_monitor: Initializing network drop monitor service [ 2.227921] NET: Registered protocol family 26 [ 2.232386] netem: version 1.3 [ 2.235459] u32 classifier [ 2.238166] input device check on [ 2.241834] Actions configured [ 2.245894] xt_time: kernel timezone is -0000 [ 2.250369] gre: GRE over IPv4 demultiplexor driver [ 2.255256] IPv4 over IPsec tunneling driver [ 2.260056] Initializing XFRM netlink socket [ 2.264358] IPsec XFRM device driver [ 2.268398] NET: Registered protocol family 10 [ 2.273902] Segment Routing with IPv6 [ 2.277657] mip6: Mobile IPv6 [ 2.281532] NET: Registered protocol family 17 [ 2.286005] NET: Registered protocol family 15 [ 2.290912] Bluetooth: RFCOMM TTY layer initialized [ 2.295807] Bluetooth: RFCOMM socket layer initialized [ 2.300956] Bluetooth: RFCOMM ver 1.11 [ 2.304719] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.310036] Bluetooth: BNEP filters: protocol multicast [ 2.315270] Bluetooth: BNEP socket layer initialized [ 2.320245] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.326191] Bluetooth: HIDP socket layer initialized [ 2.331192] l2tp_core: L2TP core driver, V2.0 [ 2.335565] l2tp_ppp: PPPoL2TP kernel driver, V2.0 [ 2.340362] 8021q: 802.1Q VLAN Support v1.8 [ 2.344574] lib80211: common routines for IEEE802.11 drivers [ 2.350654] 9pnet: Installing 9P2000 support [ 2.354962] tsn generic netlink module v1 init... [ 2.360756] registered taskstats version 1 [ 2.364872] Loading compiled-in X.509 certificates [ 2.369791] Key type ._fscrypt registered [ 2.373811] Key type .fscrypt registered [ 2.377742] Key type fscrypt-provisioning registered [ 2.387356] i2c i2c-0: IMX I2C adapter registered [ 2.393083] adv7511 1-003d: 1-003d supply avdd not found, using dummy regulator [ 2.400481] adv7511 1-003d: 1-003d supply dvdd not found, using dummy regulator [ 2.407832] adv7511 1-003d: 1-003d supply pvdd not found, using dummy regulator [ 2.415162] adv7511 1-003d: 1-003d supply a2vdd not found, using dummy regulator [ 2.422575] adv7511 1-003d: 1-003d supply v3p3 not found, using dummy regulator [ 2.429923] adv7511 1-003d: 1-003d supply v1p2 not found, using dummy regulator [ 2.438658] adv7511 1-003d: Probe failed. Remote port 'mipi_dsi@32e60000' disabled [ 2.446987] i2c i2c-1: IMX I2C adapter registered [ 2.452859] pca953x 2-0020: using no AI [ 2.457041] pca953x 2-0020: failed writing register [ 2.464232] nvmem pcf85063_nvram0: nvmem: invalid reg on /soc@0/bus@30800000/i2c@30a40000/rtc@51/clock [ 2.475722] rtc rtc1: Power loss detected, invalid time [ 2.481668] rtc-pcf85063 2-0051: registered as rtc1 [ 2.486611] i2c i2c-2: IMX I2C adapter registered [ 2.492243] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SD1_CLK already requested by 30860000.serial; cannot claim for 30b40000.mmc [ 2.504608] imx8mp-pinctrl 30330000.pinctrl: pin-35 (30b40000.mmc) status -22 [ 2.511760] imx8mp-pinctrl 30330000.pinctrl: could not request pin 35 (MX8MP_IOMUXC_SD1_CLK) from group usdhc1grp on device 30330000.pinctrl [ 2.524464] sdhci-esdhc-imx 30b40000.mmc: Error applying setting, reverse things back [ 2.532338] sdhci-esdhc-imx: probe of 30b40000.mmc failed with error -22 [ 2.540344] imx-dwmac 30bf0000.ethernet: IRQ eth_lpi not found [ 2.546330] imx-dwmac 30bf0000.ethernet: no reset control found [ 2.552775] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51 [ 2.559581] imx-dwmac 30bf0000.ethernet: DWMAC4/5 [ 2.564388] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported [ 2.571534] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported [ 2.578679] imx-dwmac 30bf0000.ethernet: TX Checksum insertion supported [ 2.585385] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported [ 2.591518] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 2.599191] imx-dwmac 30bf0000.ethernet: device MAC address e6:c8:4a:db:83:6d [ 2.606338] imx-dwmac 30bf0000.ethernet: Enabled Flow TC (entries=8) [ 2.612708] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max_off=256) [ 2.620431] libphy: stmmac: probed [ 2.624079] mdio_bus stmmac-1: MDIO device at address 1 is missing. [ 2.646673] imx8mq-usb-phy 381f0040.usb-phy: 381f0040.usb-phy supply vbus not found, using dummy regulator [ 2.656589] imx8mq-usb-phy 382f0040.usb-phy: 382f0040.usb-phy supply vbus not found, using dummy regulator [ 2.667021] pwm-backlight lvds_backlight: aaaaaaaaaaaaaaaaaaaaaa [ 2.673050] pwm-backlight lvds_backlight: bbbbbbbbbbbbbbbbbbbbbbb [ 2.679156] pwm-backlight lvds_backlight: cccccccccccccccccccccccc [ 2.685345] pwm-backlight lvds_backlight: dddddddddddddddddddddd [ 2.691385] pwm-backlight lvds_backlight: eeeeeeeeeeeeeeeeeeee [ 2.697234] pwm-backlight lvds_backlight: lvds_backlight supply power not found, using dummy regulator [ 2.706611] pwm-backlight lvds_backlight: gggggggggggggggggggggg [ 2.712686] pwm-backlight lvds_backlight: hhhhhhhhhhhhhhhhhhhhhhh [ 2.718791] pwm-backlight lvds_backlight: iiiiiiiiiiiiiiiiiiiiiii [ 2.724894] pwm-backlight lvds_backlight: jjjjjjjjjjjjjjjjjjjjj [ 2.730835] pwm-backlight lvds_backlight: kkkkkkkkkkkkkkkkkkkkk [ 2.736819] pwm-backlight lvds_backlight: llllllllllllllllll [ 2.749185] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.755846] [drm] No driver support for vblank timestamp query. [ 2.761849] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 2.769812] imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops) [ 2.777777] imx-drm display-subsystem: bound imx-lcdifv3-crtc.2 (ops lcdifv3_crtc_ops) [ 2.785795] imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200 [ 2.792804] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi [ 2.801080] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19 [ 2.808753] imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops) [ 2.820444] panel-lvds lvds0_panel: 11111111111111 width-mm DT property [ 2.827103] panel-lvds lvds0_panel: 22222222222 width-mm DT property [ 2.833481] panel-lvds lvds0_panel: 333333333333 width-mm DT property [ 2.839956] panel-lvds lvds0_panel: 44444444444 width-mm DT property [ 2.846331] panel-lvds lvds0_panel: 55555555555555 width-mm DT property [ 2.852978] panel-lvds lvds0_panel: 6666666666666 width-mm DT property [ 2.860119] OF: graph: no port node found in /usb-phy@381f0040 [ 2.866780] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 2.872297] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1 [ 2.880315] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000002001810010 [ 2.889753] xhci-hcd xhci-hcd.1.auto: irq 70, io mem 0x38200000 [ 2.895825] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 2.904100] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.911333] usb usb1: Product: xHCI Host Controller [ 2.916217] usb usb1: Manufacturer: Linux 5.4.70 xhci-hcd [ 2.921624] usb usb1: SerialNumber: xhci-hcd.1.auto [ 2.927206] hub 1-0:1.0: USB hub found [ 2.931002] hub 1-0:1.0: 1 port detected [ 2.935166] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 2.940672] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2 [ 2.948341] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed [ 2.954954] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 2.963154] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 [ 2.971428] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.978660] usb usb2: Product: xHCI Host Controller [ 2.983548] usb usb2: Manufacturer: Linux 5.4.70 xhci-hcd [ 2.988960] usb usb2: SerialNumber: xhci-hcd.1.auto [ 2.994495] hub 2-0:1.0: USB hub found [ 2.998272] hub 2-0:1.0: 1 port detected [ 3.002762] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 7 mkt segment 2 supported-hw 0x80 0x4 [ 3.012521] imx-micfil sound-micfil: ASoC: failed to init link micfil hifi: -517 [ 3.019936] imx-micfil sound-micfil: snd_soc_register_card failed (-517) [ 3.027248] imx-cdnhdmi sound-hdmi: ASoC: failed to init link imx8 hdmi: -517 [ 3.034399] imx-cdnhdmi sound-hdmi: snd_soc_register_card failed (-517) [ 3.041709] imx-xcvr sound-xcvr: snd-soc-dummy-dai <-> 30cc0000.xcvr mapping ok [ 3.049041] imx-xcvr sound-xcvr: ASoC: no DMI vendor name! [ 3.056399] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_ECSPI2_MOSI already requested by 30280000.watchdog; cannot claim for 30830000.spi [ 3.069306] imx8mp-pinctrl 30330000.pinctrl: pin-125 (30830000.spi) status -22 [ 3.076542] imx8mp-pinctrl 30330000.pinctrl: could not request pin 125 (MX8MP_IOMUXC_ECSPI2_MOSI) from group ecspi2grp on device 30330000.pinctrl [ 3.089677] spi_imx 30830000.spi: Error applying setting, reverse things back [ 3.096833] spi_imx: probe of 30830000.spi failed with error -22 [ 3.104008] pca9450 0-0025: Device ID=0x31 [ 3.108122] pca9450 0-0025: gpio_intr = 3 [ 3.112145] pca9450 0-0025: chip_irq=75 [ 3.146015] random: fast init done [ 3.150358] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_GPIO1_IO15 already requested by 30670000.pwm; cannot claim for 1-003c [ 3.162202] imx8mp-pinctrl 30330000.pinctrl: pin-20 (1-003c) status -22 [ 3.168830] imx8mp-pinctrl 30330000.pinctrl: could not request pin 20 (MX8MP_IOMUXC_GPIO1_IO15) from group csi_mclk_grp on device 30330000.pinctrl [ 3.182072] ov5640 1-003c: Error applying setting, reverse things back [ 3.188620] ov5640: probe of 1-003c failed with error -22 [ 3.197068] wm8960 2-0034: Failed to issue reset [ 3.204584] rpmsg-audio-codec-wm8960 2-0034: Failed to issue reset [ 3.211913] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO [ 3.247183] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA [ 3.260582] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 46 [ 3.265841] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 47 [ 3.270802] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 3.271089] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 48 [ 3.282891] fsl-micfil-dai 30ca0000.micfil: GET IRQ: 49 [ 3.291199] imx6q-pcie 33800000.pcie: 33800000.pcie supply epdev_on not found, using dummy regulator [ 3.291234] reg-fixed-voltage regulator-usb4-vbus: nonexclusive access to GPIO for regulator-usb4-vbus [ 3.300617] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!. [ 3.309860] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SAI2_RXD0 already requested by regulator-usb4-vbus; cannot claim for regulator-usb3-vbus [ 3.315838] imx6q-pcie 33800000.pcie: PCIe PHY PLL clock is locked. [ 3.328757] imx8mp-pinctrl 30330000.pinctrl: pin-105 (regulator-usb3-vbus) status -22 [ 3.342858] imx8mp-pinctrl 30330000.pinctrl: could not request pin 105 (MX8MP_IOMUXC_SAI2_RXD0) from group usb1grp on device 30330000.pinctrl [ 3.355642] reg-fixed-voltage regulator-usb3-vbus: Error applying setting, reverse things back [ 3.364271] reg-fixed-voltage: probe of regulator-usb3-vbus failed with error -22 [ 3.372454] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SAI2_RXD0 already requested by regulator-usb4-vbus; cannot claim for regulator-usb2-vbus [ 3.383918] pcie phy pipe clk is not ready [ 3.385952] imx8mp-pinctrl 30330000.pinctrl: pin-105 (regulator-usb2-vbus) status -22 [ 3.390031] phy phy-32f00000.pcie-phy.5: phy init failed --> -110 [ 3.390036] imx6q-pcie 33800000.pcie: Waiting for PHY PLL ready timeout! [ 3.397889] imx8mp-pinctrl 30330000.pinctrl: could not request pin 105 (MX8MP_IOMUXC_SAI2_RXD0) from group usb1grp on device 30330000.pinctrl [ 3.423465] reg-fixed-voltage regulator-usb2-vbus: Error applying setting, reverse things back [ 3.424486] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout [ 3.432107] reg-fixed-voltage: probe of regulator-usb2-vbus failed with error -22 [ 3.437706] imx6q-pcie 33800000.pcie: host bridge /pcie@33800000 ranges: [ 3.445800] imx8mp-pinctrl 30330000.pinctrl: pin MX8MP_IOMUXC_SAI2_RXD0 already requested by regulator-usb4-vbus; cannot claim for regulator-usb1-vbus [ 3.451851] imx6q-pcie 33800000.pcie: No bus range found for /pcie@33800000, using [bus 00-ff] [ 3.451870] imx6q-pcie 33800000.pcie: IO 0x1ff80000..0x1ff8ffff -> 0x00000000 [ 3.465372] imx8mp-pinctrl 30330000.pinctrl: pin-105 (regulator-usb1-vbus) status -22 [ 3.474158] imx6q-pcie 33800000.pcie: MEM 0x18000000..0x1fefffff -> 0x18000000 [ 3.474451] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3 [ 3.474459] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3.481549] imx8mp-pinctrl 30330000.pinctrl: could not request pin 105 (MX8MP_IOMUXC_SAI2_RXD0) from group usb1grp on device 30330000.pinctrl [ 3.524928] reg-fixed-voltage regulator-usb1-vbus: Error applying setting, reverse things back [ 3.533569] reg-fixed-voltage: probe of regulator-usb1-vbus failed with error -22 [ 3.541497] hub 1-1:1.0: USB hub found [ 3.544112] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 3.551912] [drm] No driver support for vblank timestamp query. [ 3.552207] hub 1-1:1.0: 4 ports detected [ 3.557909] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops) [ 3.569820] imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops) [ 3.577801] imx-drm display-subsystem: bound imx-lcdifv3-crtc.2 (ops lcdifv3_crtc_ops) [ 3.585856] imx_sec_dsim_drv 32e60000.mipi_dsi: version number is 0x1060200 [ 3.592859] imx_sec_dsim_drv 32e60000.mipi_dsi: Failed to attach bridge: 32e60000.mipi_dsi [ 3.601147] imx_sec_dsim_drv 32e60000.mipi_dsi: failed to bind sec dsim bridge: -19 [ 3.608838] imx-drm display-subsystem: bound 32e60000.mipi_dsi (ops imx_sec_dsim_ops) [ 3.616772] imx-drm display-subsystem: bound 32c00000.bus:ldb@32ec005c (ops imx8mp_ldb_ops) [ 3.625366] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2) [ 3.636270] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver [ 3.646497] imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw_hdmi_imx_ops) [ 3.654770] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [ 3.714197] Console: switching to colour frame buffer device 160x50 [ 3.726141] Hot alarm is canceled. GPU3D clock will return to 64/64 [ 3.742385] imx-drm display-subsystem: fb0: imx-drmdrmfb frame buffer device [ 3.757814] imx-micfil sound-micfil: snd-soc-dummy-dai <-> 30ca0000.micfil mapping ok [ 3.765684] imx-micfil sound-micfil: ASoC: no DMI vendor name! [ 3.773594] imx-cdnhdmi sound-hdmi: i2s-hifi <-> 30cb0000.aud2htx mapping ok [ 3.780673] imx-cdnhdmi sound-hdmi: ASoC: no DMI vendor name! [ 3.787847] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card2/input1 [ 3.800414] isi-m2m 32e00000.isi:m2m_device: Register m2m success for ISI.0 [ 3.807510] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 3.819216] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 3.825875] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 3.834524] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [ 3.844672] mx8-img-md: Registered mxc_isi.0.capture as /dev/video1 [ 3.851321] unregister ISI channel: mxc_isi.0 [ 3.856848] ALSA device list: [ 3.859839] #0: imx-audio-xcvr [ 3.863093] #1: imx-audio-micfil [ 3.866503] #2: audio-hdmi [ 4.483422] imx6q-pcie 33800000.pcie: Phy link never came up [ 4.489122] imx6q-pcie 33800000.pcie: failed to initialize host [ 4.495078] imx6q-pcie 33800000.pcie: unable to add pcie port. [ 4.503316] Freeing unused kernel memory: 4416K [ 4.507936] Run /init as init process [ 4.539282] init: init first stage started! [ 4.543755] init: Switching root to '/first_stage_ramdisk' [ 4.551461] init: Using Android DT directory /proc/device-tree/firmware/android/ [ 4.590101] init: [libfs_mgr]Created logical partition system_a on device /dev/block/dm-0 [ 4.598440] init: [libfs_mgr]Skipping zero-length logical partition: system_b [ 4.606853] init: [libfs_mgr]Created logical partition vendor_a on device /dev/block/dm-1 [ 4.615122] init: [libfs_mgr]Skipping zero-length logical partition: vendor_b [ 4.623959] init: [libfs_mgr]Created logical partition product_a on device /dev/block/dm-2 [ 4.632256] init: [libfs_mgr]Skipping zero-length logical partition: product_b [ 4.642553] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/by-name/metadata [ 4.653330] EXT4-fs (mmcblk2p6): warning: mounting unchecked fs, running e2fsck is recommended [ 4.662603] EXT4-fs (mmcblk2p6): mounted filesystem without journal. Opts: discard [ 4.670348] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 4.681057] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 4.701152] device-mapper: verity: sha1 using implementation "sha1-ce" [ 4.713628] EXT4-fs (dm-3): mounted filesystem without journal. Opts: errors=panic,barrier=1,inode_readahead_blks=8 [ 4.731825] device-mapper: verity: sha1 using implementation "sha1-ce" [ 4.745097] EXT4-fs (dm-4): mounted filesystem without journal. Opts: errors=panic,barrier=1,inode_readahead_blks=8 [ 4.757210] device-mapper: verity: sha1 using implementation "sha1-ce" [ 4.771831] EXT4-fs (dm-5): mounted filesystem without journal. Opts: errors=panic,barrier=1,inode_readahead_blks=8 [ 4.783872] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 4.796143] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 4.824474] printk: init: 21 output lines suppressed due to ratelimiting [ 4.845592] random: init: uninitialized urandom read (40 bytes read) [ 4.987323] random: init: uninitialized urandom read (40 bytes read) [ 5.010594] init: Loading SELinux policy [ 5.048657] SELinux: Permission nlmsg_readpriv in class netlink_route_socket not defined in policy. [ 5.058130] SELinux: the above unknown classes and permissions will be denied [ 5.065335] SELinux: policy capability network_peer_controls=1 [ 5.071258] SELinux: policy capability open_perms=1 [ 5.076250] SELinux: policy capability extended_socket_class=1 [ 5.082178] SELinux: policy capability always_check_network=0 [ 5.088052] SELinux: policy capability cgroup_seclabel=0 [ 5.093472] SELinux: policy capability nnp_nosuid_transition=1 [ 5.181619] selinux: SELinux: Loaded policy from /vendor/etc/selinux/precompiled_sepolicy [ 5.181619] [ 5.181622] audit: type=1403 audit(13.012:2): auid=4294967295 ses=4294967295 lsm=selinux res=1 [ 5.210320] selinux: SELinux: Loaded file_contexts [ 5.210320] [ 5.222363] random: init: uninitialized urandom read (40 bytes read) [ 5.262211] init: init second stage started! [ 5.294525] init: Using Android DT directory /proc/device-tree/firmware/android/ [ 5.307148] selinux: SELinux: Loaded file_contexts [ 5.307148] [ 5.313510] init: Running restorecon... [ 5.337875] init: Overriding previous 'ro.' property 'pm.dexopt.boot':'verify' with new value 'quicken' [ 5.349533] init: Couldn't load property file '/product_services/build.prop': open() failed: No such file or directory: No such file or directory [ 5.362648] init: Couldn't load property file '/factory/factory.prop': open() failed: No such file or directory: No such file or directory [ 5.377155] init: Setting product property ro.product.brand to 'Android' (from ro.product.product.brand) [ 5.386703] init: Setting product property ro.product.device to 'evk_8mp' (from ro.product.product.device) [ 5.396406] init: Setting product property ro.product.manufacturer to 'freescale' (from ro.product.product.manufacturer) [ 5.470744] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 5.551985] ueventd: ueventd started! [ 5.559108] selinux: SELinux: Loaded file_contexts [ 5.559108] [ 5.565679] ueventd: Parsing file /ueventd.rc... [ 5.571500] apexd: Bootstrap subcommand detected [ 5.572588] ueventd: Parsing file /vendor/ueventd.rc... [ 5.582424] ueventd: Parsing file /odm/ueventd.rc... [ 5.587529] ueventd: Unable to read config file '/odm/ueventd.rc': open() failed: No such file or directory [ 5.597399] ueventd: Parsing file /ueventd.freescale.rc... [ 5.602952] ueventd: Unable to read config file '/ueventd.freescale.rc': open() failed: No such file or directory [ 5.773052] ueventd: firmware: loading 'imx/sdma/sdma-imx7d.bin' for '/devices/platform/soc@0/30800000.bus/30bd0000.dma-controller/firmware/imx!sdma!sdma-imx7d.bin' [ 5.787758] ueventd: firmware: loading 'regulatory.db' for '/devices/platform/regulatory.0/firmware/regulatory.db' [ 5.789442] apexd: wait for '/dev/loop-control' took 191ms [ 5.804387] apexd: Pre-allocated 9 loopback devices [ 5.810451] apexd: Scanning /system/apex for embedded keys [ 5.818133] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5 [ 5.820667] apexd: Scanning /product/apex for embedded keys [ 5.830259] apexd: ... does not exist. Skipping [ 5.834912] apexd: Scanning /system/apex looking for APEX packages. [ 5.841436] apexd: Found /system/apex/com.android.conscrypt.apex [ 5.848043] apexd: Skipped when bootstrapping [ 5.852559] apexd: Found /system/apex/com.android.runtime.debug.apex [ 5.944272] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null) [ 6.033780] EXT4-fs (loop1): mounted filesystem without journal. Opts: (null) [ 6.047251] printk: apexd: 13 output lines suppressed due to ratelimiting [ 6.185804] Registered swp emulation handler [ 6.217701] Console: switching to colour dummy device 80x25 [ 6.236828] watchdogd: watchdogd started (interval 10, margin 20)! [ 6.252843] logd.auditd: start [ 6.259590] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 6.263556] logd.klogd: 6185073500 [ 6.271990] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 6.293012] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 6.306361] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 6.319633] usbcore: registered new interface driver rtk_btusb [ 6.377240] vvcam_video: loading out-of-tree module taints kernel. [ 6.384991] enter viv_video_init_module [ 6.397209] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm vold: deleted inode referenced: 16 [ 6.434220] zram0: detected capacity change from 0 to 629145600 [ 6.434222] enter viv_isp_init_module [ 6.469312] mkswap: Swapspace size: 614396k, UUID=7977a225-d8ae-44c0-856b-35e5f3c7cd0c [ 6.477597] enter viv_dwe_init_module [ 6.502594] Adding 614396k swap on /dev/block/zram0. Priority:-2 extents:1 across:614396k SS [ 6.594117] type=1400 audit(14.424:3): avc: denied { search } for comm="android.hardwar" name="/" dev="mmcblk2p6" ino=2 scontext=u:r:hal_bootctl_default:s0 tcontext=u:object_r:metadata_file:s0 tclass=dir permissive=1 [ 9.333839] random: crng init done [ 9.337248] random: 6 urandom warning(s) missed due to ratelimiting [ 11.052162] init: Calling: /system/bin/vdc checkpoint needsCheckpoint [ 11.082738] init: /dev/block/by-name/userdata is not dm device: No such file or directory [ 11.091763] type=1400 audit(14.424:3): avc: denied { search } for comm="android.hardwar" name="/" dev="mmcblk2p6" ino=2 scontext=u:r:hal_bootctl_default:s0 tcontext=u:object_r:metadata_file:s0 tclass=dir permissive=1 [ 11.111065] type=1400 audit(18.924:4): avc: denied { create } for comm="kdevtmpfs" name="dm-6" scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 11.127099] type=1400 audit(18.924:4): avc: denied { create } for comm="kdevtmpfs" name="dm-6" scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 11.142897] type=1400 audit(18.924:5): avc: denied { setattr } for comm="kdevtmpfs" name="dm-6" dev="devtmpfs" ino=2623 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 11.147871] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/dm-6 [ 11.168067] init: [libfs_mgr]Filesystem on /dev/block/dm-6 was not cleanly shutdown; state flags: 0x1, incompat feature flags: 0x10046 [ 11.181011] EXT4-fs (dm-6): Ignoring removed nomblk_io_submit option [ 11.191665] EXT4-fs (dm-6): recovery complete [ 11.196048] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit [ 11.206324] init: [libfs_mgr]check_fs(): mount(/dev/block/dm-6,/data,ext4)=0: Success [ 11.224886] init: [libfs_mgr]check_fs(): unmount(/data) succeeded [ 11.231260] init: [libfs_mgr]Running /system/bin/e2fsck on /dev/block/dm-6 [ 12.055154] e2fsck: e2fsck 1.44.4 (18-Aug-2018) [ 12.055154] [ 12.061376] e2fsck: Pass 1: Checking inodes, blocks, and sizes [ 12.061376] [ 12.068716] e2fsck: Pass 2: Checking directory structure [ 12.068716] [ 12.075517] e2fsck: Pass 3: Checking directory connectivity [ 12.075517] [ 12.082578] e2fsck: Pass 4: Checking reference counts [ 12.082578] [ 12.089130] e2fsck: Pass 5: Checking group summary information [ 12.089130] [ 12.096455] e2fsck: /dev/block/dm-6: 11/383520 files (0.0% non-contiguous), 43458/1531904 blocks [ 12.096455] [ 12.110022] init: [libfs_mgr]superblock s_max_mnt_count:65535,/dev/block/dm-6 [ 12.117235] init: [libfs_mgr]Reserved blocks 32768 is too large; capping to 30638 [ 12.125742] EXT4-fs (dm-6): Ignoring removed nomblk_io_submit option [ 12.137066] EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic [ 12.148282] init: [libfs_mgr]__mount(source=/dev/block/dm-6,target=/data,type=ext4)=0: Success [ 12.157755] EXT4-fs error: 11 callbacks suppressed [ 12.157762] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm init: deleted inode referenced: 16 [ 12.211235] device-mapper: bow: Switching to state Checkpoint [ 12.687278] init (pid 1) is setting deprecated v1 encryption policy; recommend upgrading to v2. [ 12.736174] fscrypt: AES-256-CTS-CBC using implementation "cts-cbc-aes-ce" [ 12.817697] fscrypt: AES-256-XTS using implementation "xts-aes-ce" [ 12.830521] apexd: Marking APEXd as starting [ 12.836092] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm Binder:215_2: deleted inode referenced: 12 [ 12.847794] apexd: Scanning /system/apex for embedded keys [ 12.857712] apexd: Scanning /product/apex for embedded keys [ 12.944911] EXT4-fs (loop2): mounted filesystem without journal. Opts: (null) [ 13.033454] EXT4-fs (loop3): mounted filesystem without journal. Opts: (null) [ 13.101408] EXT4-fs (loop4): mounted filesystem without journal. Opts: (null) [ 13.193804] EXT4-fs (loop5): mounted filesystem without journal. Opts: (null) [ 13.289426] EXT4-fs (loop6): mounted filesystem without journal. Opts: (null) [ 13.372860] EXT4-fs (loop7): mounted filesystem without journal. Opts: (null) [ 13.454231] EXT4-fs (loop8): mounted filesystem without journal. Opts: (null) [ 17.191207] init: Command 'load_persist_props' action=load_persist_props_action (/init.rc:306) took 1382ms and succeeded [ 17.202241] init: Service 'exec 9 (/system/bin/recovery-persist)' (pid 291) exited with status 0 [ 17.211551] init: starting service 'logd-reinit'... [ 17.218311] init: processing action (load_persist_props_action) from (/system/etc/init/flags_health_check.rc:1) [ 17.231005] init: Setting policy on /data/server_configurable_flags [ 17.237613] init: Policy for /data/server_configurable_flags set to c5db7d5efd01df3f modes 1/4 [ 17.246839] init: starting service 'exec 10 (/system/bin/flags_health_check BOOT_FAILURE)'... [ 17.259332] init: SVC_EXEC service 'exec 10 (/system/bin/flags_health_check BOOT_FAILURE)' pid 293 (uid 1000 gid 1000+0 context default) started; waiting... [ 17.275469] logd.daemon: reinit [ 17.278776] init: Service 'logd-reinit' (pid 292) exited with status 0 [ 17.867637] init: Service 'exec 10 (/system/bin/flags_health_check BOOT_FAILURE)' (pid 293) exited with status 0 waiting took 0.608000 seconds [ 17.915069] update_verifier: Started with arg 1: nonencrypted [ 17.923696] update_verifier: Booting slot 0: isSlotMarkedSuccessful=0 [ 17.930282] update_verifier: /data/ota_package/care_map.pb doesn't exist [ 17.937036] update_verifier: Failed to parse the care map file, skipping verification [ 17.945629] update_verifier: Deferred marking slot 0 as booted successfully. [ 17.952744] update_verifier: Leaving update_verifier. [ 17.997383] type=1400 audit(18.924:5): avc: denied { setattr } for comm="kdevtmpfs" name="dm-6" dev="devtmpfs" ino=2623 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=blk_file permissive=1 [ 18.015458] type=1400 audit(25.828:6): avc: denied { setattr } for comm="init" name="wifi" dev="dm-6" ino=228503 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 18.033953] type=1400 audit(25.828:6): avc: denied { setattr } for comm="init" name="wifi" dev="dm-6" ino=228503 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 18.052070] type=1400 audit(25.828:7): avc: denied { search } for comm="init" name="wifi" dev="dm-6" ino=228503 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 18.070346] type=1400 audit(25.828:7): avc: denied { search } for comm="init" name="wifi" dev="dm-6" ino=228503 scontext=u:r:vendor_init:s0 tcontext=u:object_r:wifi_data_file:s0 tclass=dir permissive=1 [ 18.088377] type=1400 audit(25.832:8): avc: denied { setattr } for comm="init" name="dhcp" dev="dm-6" ino=228507 scontext=u:r:vendor_init:s0 tcontext=u:object_r:dhcp_data_file:s0 tclass=dir permissive=1 [ 18.596543] Mass Storage Function, version: 2009/09/11 [ 18.601843] LUN: removable file: (no medium) [ 18.611636] using random self ethernet address [ 18.616182] using random host ethernet address [ 18.622366] file system registered [ 18.908336] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a [ 19.004762] isi-m2m 32e00000.isi:m2m_device: ISI channel[0] is busy [ 19.085698] isi-m2m 32e00000.isi:m2m_device: ISI channel[0] is busy [ 19.193446] healthd: battery l=85 v=3 t=35.0 h=2 st=2 c=400 fc=4000000 cc=32 chg=a [ 19.254622] type=1400 audit(25.832:8): avc: denied { setattr } for comm="init" name="dhcp" dev="dm-6" ino=228507 scontext=u:r:vendor_init:s0 tcontext=u:object_r:dhcp_data_file:s0 tclass=dir permissive=1 [ 19.283218] init: Setting policy on /data/eGalax [ 19.296075] init: Policy for /data/eGalax set to c5db7d5efd01df3f modes 1/4 [ 19.355259] type=1400 audit(27.084:9): avc: denied { setattr } for comm="init" name="bluetooth" dev="dm-6" ino=228487 scontext=u:r:vendor_init:s0 tcontext=u:object_r:bluetooth_data_file:s0 tclass=dir permissive=1 evk_8mp:/ $ [ 19.512630] type=1400 audit(27.084:9): avc: denied { setattr } for comm="init" name="bluetooth" dev="dm-6" ino=228487 scontext=u:r:vendor_init:s0 tcontext=u:object_r:bluetooth_data_file:s0 tclass=dir permissive=1 [ 19.596086] EXT4-fs error (device mmcblk2p6): ext4_lookup:1789: inode #2: comm gsid: deleted inode referenced: 16 [ 19.840037] isi-m2m 32e00000.isi:m2m_device: ISI channel[0] is busy [ 20.246930] read descriptors [ 20.262966] read strings [ 20.618795] EXT4-fs error (device dm-6): ext4_find_dest_de:2030: inode #228492: block 918033: comm Binder:296_3: bad entry in directory: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, lblk=0, size=4096 fake=1 [ 20.620421] printk: Binder:260_2: 99 output lines suppressed due to ratelimiting [ 20.637013] binder: release 318:352 transaction 680 in, still active [ 20.637019] binder: send failed reply for transaction 680 to 334:334 [ 20.647166] Aborting journal on device dm-6-8. [ 20.678647] Kernel panic - not syncing: EXT4-fs (device dm-6): panic forced after error [ 20.686666] CPU: 2 PID: 296 Comm: Binder:296_3 Tainted: G O 5.4.70 #96 [ 20.694503] Hardware name: NXP i.MX8MPlus EVK board (DT) [ 20.699829] Call trace: [ 20.702291] dump_backtrace+0x0/0x134 [ 20.705955] show_stack+0x14/0x1c [ 20.709271] dump_stack+0xa0/0xd8 [ 20.712587] panic+0x148/0x350 [ 20.715642] __ext4_error_inode+0x0/0x214 [ 20.719652] __ext4_error_inode+0x154/0x214 [ 20.723848] __ext4_check_dir_entry+0x23c/0x284 [ 20.728381] ext4_find_dest_de+0xa8/0x154 [ 20.732390] add_dirent_to_buf+0x9c/0x218 [ 20.736397] ext4_add_entry+0x1fc/0xe60 [ 20.740229] ext4_create+0x104/0x20c [ 20.743804] path_openat+0x9e0/0xe1c [ 20.747376] do_filp_open+0x74/0x11c [ 20.750948] do_sys_open+0x130/0x24c [ 20.754521] __arm64_sys_openat+0x24/0x2c [ 20.758528] el0_svc_common+0x98/0x160 [ 20.762275] el0_svc_handler+0x68/0x80 [ 20.766021] el0_svc+0x8/0xc [ 20.768903] SMP: stopping secondary CPUs [ 21.772823] SMP: failed to stop secondary CPUs 0-2 [ 21.777611] Kernel Offset: disabled [ 21.781096] CPU features: 0x00010002,2000200c [ 21.785449] Memory Limit: none [ 21.788501] trusty-log panic notifier - trusty version Built: 12:16:06 Nov 19 2020 [ 21.788509] Rebooting in 5 seconds.. It will show this log, It seems the emmc problem is here. EXT4-fs error (device dm-6) Re: IMX8MP Self Designed Board system crash after booting in the system Hi @VictorWang129  Based on your logs, it doesn't seem to be an issue with eMMC or DDR.  Please check if your DTS file configuration is correct. What modifications did you make to the code? B.R

S32DS LPSPI SLAVE 配置 S32K344 + 33664需要将LPSPI 配置成slave 模式。 S32DS SPI配置slave后，33664回完数据后， MCU如何取数据呢？ 需要调用哪些API？ Re: S32DS LPSPI SLAVE 配置 已经测试，使用 Lpspi_Ip_AsyncTransmit().可以收到数据.  我是想在 Lpspi_Ip_AsyncTransmit().的回调函数中继续调这个函数来触发接收第二帧33664回复的数据，但是由于MC33664 回复了两帧数据，两次CS之间间隔只有2.6us， Lpspi_Ip_AsyncTransmit().的回调函数来不及处理，导致第二次CS的数据没有收到，这个如何处理呢？ Re: S32DS LPSPI SLAVE 配置 你好@RRR123 建议使用 电池管理系统 SDK 中提供的 PHY_664 驱动程序进行 MC33664 通信。PHY_664 驱动程序专门设计用于管理与 MC33664 收发器的通信。 NXP电池管理软件开发工具包和工具链

imx95 15x15封装 DDR5的问题 Hi NXP     我现在正在调试imx95 15x15封装的DDR5，遇到了问题,DDR5:RS2G32LO5D4FB-31BT     1.我通过Config Tools for i.MX 26.06，校验，使用lpddr5_timing.c编译的.bin文件，烧录时，M33核出现了DDR OEI: done, err = -1     2.我将ddr的速率降到1866MT/s，还是出现-1的错误     3.我看sdk中没有发布官板的imx9596 15x15 ddr5 Re: imx95 15x15封装 DDR5的问题 Hi @yrj  imx95 不支持DDR5。 B.R Re: imx95 15x15封装 DDR5的问题 HI @pengyong_zhang       是lpddr5，支持吗

Example code for K344 & FS26 with MCAL component Sbc_fs26 and OS component freeRTOS Hello, Can you provide a S32K344 & FS26 chips source code example (S32DS project) that integrates the Sbc_fs26 and freeRTOS components? I am aware that there are individual RTD examples: 1)  Sbc_fs26_example_HLD_S32K344  (no freeRTOS) 2) FreeRTOS_Toggle_Led_Example_S32K344 (no Sbc_fs26) and also an example: 3) MR_CANHUBK3_IEEE1722 in which the watchdog is disabled and the Sbc_fs26 component is not used  Essentially I'm looking for a basic source code example for properly setting and refreshing a FS26 chip in a freeRTOS environment. Thank you. Re: Example code for K344 & FS26 with MCAL component Sbc_fs26 and OS component freeRTOS Hello Slavko, At the moment, I am not aware of an example project combining these components.   The examples you mentioned are the relevant reference points: - Sbc_fs26_example_HLD_S32K344 This demonstrates the FS26/SBC integration, but it does not use FreeRTOS. - FreeRTOS_Toggle_Led_Example_S32K344 This demonstrates a basic FreeRTOS setup on S32K344, but it does not include the FS26 SBC component. - MR_CANHUBK3_IEEE1722 This includes a broader system-level implementation, but the FS26 watchdog is disabled and the Sbc_fs26 component is not used. For your use case, the practical approach would be to start from the Sbc_fs26_example_HLD_S32K344 project and then integrate the FreeRTOS configuration from the FreeRTOS example. The FS26 initialization should remain part of the system startup sequence, while the watchdog refresh should be handled periodically from a FreeRTOS task or another deterministic timing mechanism.   BRs, Tomas

FS2400 current consumption after wakeup hello expert: my chip is S32K312 and SBC is FS2400 now i need to wake up the chip and the wakeup source is a GPIO falling edge before make S32K312 going to standby ,i set the FS2400 goto LPON mode  /* register M_WU1_EN : filed CAN_WUEN set to wakeup and interrupt(03) */ Sbc_FS24_Ip_WriteRegister(0, SBC_FS24_IP_M_WU1_EN_ADDR, SBC_FS24_IP_M_CAN_WUEN_MASK); /* register M_IOWU_EN : filed WAKE2,WAKE3,HVIO1 set to no wakeup and interrupt(00) */ Sbc_FS24_Ip_WriteRegister(0, SBC_FS24_IP_M_IOWU_EN_ADDR, 0x00); /* register M_CAN : filed CAN MODE set to Transceiver receive only mode */ Sbc_FS24_Ip_WriteRegister(0, SBC_FS24_IP_M_CAN_ADDR, SBC_FS24_IP_M_CAN_MODE_RX_ONLY); /* go to LPON mode */ Sbc_FS24_Ip_WriteRegister(0, SBC_FS24_IP_M_SYS_CFG_ADDR, SBC_FS24_IP_M_GO2LPON_MASK) after wakeup ,i set the SBC goto normal Lpspi_Ip_Init(&Lpspi_Ip_PhyUnitConfig_SpiPhyUnit_SBC_Instance_0); Sbc_FS24_Ip_InitDriver(&Sbc_FS24_Ip_Config); Sbc_FS24_Ip_InitDevice(SBC_FS24_DEVICE_ID); eReturnValue = Sbc_FS24_Ip_CanTrcvSetState(SBC_FS24_DEVICE_ID, SBC_FS24_CANTRCV_STATE_ACTIVE); Sbc_FS24_Ip_WriteRegister(0, SBC_FS24_IP_M_SYS_CFG_ADDR, SBC_FS24_IP_M_GO2NORMAL_MASK); i found the current consumption is 54mA but the POR current consumption is 72mA if i do nothing about the SBC before goto standby ,after wakeup ,the current consumption is same as POR, so i think the sbc status is something wrong ,can you tell me why? Re: FS2400 current consumption after wakeup Hello PINKMAN Good day! Based on the behavior you described, I do not think the FS2400 is necessarily "stuck", but it is very likely that after waking from LPON the SBC is not returning to exactly the same configuration/state as after a POR The datasheet states that waking from LPON returns the device directly to Normal mode through the wake-up sequence. The device does not re-enter INIT state automatically after an LPON wake-up Also, if the device goes in LPON or LPOFF or Fail-safe mode while in INIT state, the device stays in INIT state, which can lead to misconfiguration of the device. It is recommended to read the INIT_S status bit in M_STATUS register before going to LPON or LPOFF mode, and to go only if the device is no longer in INIT state I would capture and compare the following registers in both cases (POR path and LPON-wakeup path): M_STATUS M_SYS_CFG M_CAN M_SYS1_CFG M_REG_CTRL M_IOWU_EN M_WU1_EN I hope this information has helped you, please let me know if you need help with anything else. Have a great day and best of luck. Re: FS2400 current consumption after wakeup hi : RafaR Based on your suggestion, I compared the FS2400 registers during POR and wake-up. I found that during POR, the value of register M_REG_CTRL is 0x04, while after wake-up, the value of register M_REG_CTRL is 0x1304. Based on this finding, I traced it to the function Sbc_FS24_Ip_InitDevice → Sbc_FS24_Ip_OptionalInitSequence → Sbc_FS24_Ip_InitMain, where there is an operation on M_REG_CTRL. However, this function has a prerequisite that SBC_FS24_NORMAL == ePowState. Therefore, during POR, this function can be executed, but during wake-up, GOTONORMAL is executed after Sbc_FS24_Ip_InitDevice, so this function cannot be executed, resulting in a power consumption difference. So I have two questions: 1. Is Sbc_FS24_Ip_InitDevice mandatory? Because I found that even if I do not call it during initialization, CAN message transmission/reception and power supply still work fine. 2. Where does this power consumption difference mainly come from?