Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
Radar - SW & HW Environment 1 Table of Contents • Introduction • Reference Architecture • Hardware Environment • Software Environment • Radar Signal Chain • From Simulation to Target • Installing the NXP Toolchain • Next Article in the Series • References 2 Introduction This article presents the NXP hardware platforms and the MathWorks and NXP software tools used to build an automotive radar application. The development workflow is anchored in the MathWorks example "Radar Signal Simulation and Processing for Automated Driving," which provides a reference architecture spanning driving-scenario simulation, radar modeling, and signal processing. The resulting signal-processing chain is then adapted and deployed onto NXP radar hardware using NXP-specific toolboxes and hardware accelerators. This article is part of the Radar Application Development Series, which describes the complete workflow for developing, deploying, and optimizing automotive radar applications on NXP radar platforms. The purpose of this article is to introduce the overall software and hardware environment and show how the different tools, hardware components, and processing engines fit together within a radar development workflow. The next article in this series, "Radar - Processing Chain," will explore in depth each processing block presented in the Radar Signal Processing section: Range FFT, Doppler FFT, Non-Coherent Combining, CFAR Detection, Clustering, and Direction-of-Arrival (DoA) estimation. 3 Reference Architecture The starting point for the radar application is the MathWorks reference example, which models a complete automotive radar system end to end. The workflow begins by defining a highway driving scenario using the Automated Driving Toolbox ( drivingScenario ), where vehicles and traffic participants are modeled. The ground-truth generated data then feeds the radar model.   Figure 1: MathWorks example bird's-eye plot with Radar detections A 77 GHz FMCW radar is parameterized from high-level system requirements such as: Maximum detection range, typically 250-300 m for long-range radar Range resolution, around 1 m Velocity resolution Maximum relative target velocity, up to around 230 km/h The example then builds a transceiver model with antenna arrays, transmitter/receiver components, and signal-propagation effects, generating synthetic detections that estimate the position and velocity of surrounding vehicles. For the NXP application, the reference architecture is divided into two domains: Environment Simulation Executes entirely within MATLAB, and is responsible for: Driving scenario generation Vehicle motion simulation Target ground-truth generation FMCW signal generation Radar channel and propagation modeling Radar Signal Processing Contains the processing chain deployed on the S32R45 platform: Range FFT processing Doppler FFT processing Non-Coherent Combining CFAR detection Clustering Direction-of-Arrival (DoA) estimation The Radar Signal Processing domain forms the basis of the embedded radar application deployed on the S32R45 Evaluation Board. 4 Hardware Environment 3.1 S32R45 Evaluation Board The primary processing platform is the NXP S32R45 Evaluation Board, a development platform for high-performance 77 GHz radar applications such as adaptive cruise control, autonomous emergency braking, and cascaded imaging radar. It integrates several specialized processing engines optimized for radar workloads. Processing engine Role 4x Arm® Cortex®-A53 cores Application-level processing, radar control, clustering, and object management SPT Accelerator Optimized FFTs and high-throughput radar signal-processing kernels BBE32 DSP Vectorized signal processing, detection algorithms, and custom radar kernels LAX Accelerator Matrix and linear-algebra operations for accelerated angle estimation   Figure 2: S32R45 block diagram 3.2 TEF82xx Customer Application Board The TEF82xx is a fully integrated 76-81 GHz RFCMOS automotive radar transceiver providing the RF front end for signal generation and capture. It integrates 3 transmit channels, 4 receive channels, ADCs, a low-phase-noise VCO, and a phase rotator, and is fully compatible with the S32R45. In the current application, the input signal is sourced from simulation rather than hardware, so the TEF82xx is not actively used. It is included as a placeholder for future hardware-in-the-loop and real-sensor integration. 5 Software Environment The radar application combines MathWorks toolboxes for algorithm development with NXP toolboxes and tools for deployment and accelerator integration. 4.1 MathWorks Tools Tool Role in the workflow Radar Toolbox FMCW waveform generation, propagation modeling, detection, and analysis Automated Driving Toolbox Scenario modeling, road/vehicle simulation, and ground-truth generation 4.2 NXP Tools Tool Version Role in the workflow S32 Design Studio for S32 Platform 3.5 IDE, compiler, debugger, and deployment environment for the S32R45, including its accelerators NXP Model-Based Design Toolbox for SPT 1.9.0 Bit-exact SPT simulator integration and rapid prototyping in MATLAB NXP Model-Based Design Toolbox for RADAR 1.0.0 MATLAB integration for S32R45; SPT/LAX kernel execution, code generation, and PIL workflows NXP Radar SDK (S32R45) 1.2.0 Optimized radar algorithms, accelerator libraries, SPT/LAX kernels, and embedded deployment infrastructure Together, these tools act as the gateway between the MathWorks and NXP ecosystems, enabling algorithm development, simulation, code generation, deployment, and SIL/PIL validation within a common workflow. 6 Radar Signal Chain Once the FMCW echoes are generated or captured, the signal-processing chain transforms the radar cube into a list of detected objects. The application currently implements the following stages. # Stage What it does Runs on 1 ADC Acquisition Digitizes the beat signal into a radar data cube, using samples x chirps x antennas TEF82xx ADCs → S32R45 2 Range FFT Fast-time FFT converts beat frequency into target range SPT accelerator 3 Doppler FFT Slow-time FFT resolves velocity, producing the processed radar cube SPT accelerator 4 Non-Coherent Combining Combines the magnitude of the range/Doppler-processed radar cube across channels, producing the range-Doppler magnitude matrix SPT accelerator 5 CFAR Detection Applies Constant False Alarm Rate thresholding on the range-Doppler magnitude matrix to detect possible targets BBE32 DSP 6 Clustering Groups neighboring detections, for example using DBSCAN, into physical objects Cortex-A53 cores 7 Angle / DoA Estimation Estimates azimuth/elevation across the antenna array, using methods such as beamforming or MUSIC LAX accelerator The output of the chain is a list of detected objects with range, relative velocity, and angle of arrival. Future Improvements The current application focuses on signal processing and object detection. Planned enhancements include: Multi-target tracking, including Kalman filtering and track-to-track association Hardware-in-the-loop testing using the TEF82xx front end 7 From Simulation to Target The MathWorks reference example executes entirely within MATLAB. During deployment, the example is partitioned into the Environment Simulation block and the Radar Signal Processing block, where the computationally intensive signal-processing functions are replaced with NXP-optimized implementations from the Radar SDK. This delivers faster execution, reduced CPU utilization, and accelerator offloading on the S32R45. 8 Installing the NXP Toolchain 7.1 Installation Order The development tools must be installed in the following order to ensure that all external dependencies required by the NXP MBDT for RADAR are available before it is configured: S32 Design Studio for S32 Platform 3.5 S32R45 Radar SDK 1.2.0 NXP Model-Based Design Toolbox for SPT 1.9.0 NXP Model-Based Design Toolbox for RADAR 1.0.0 7.2 Integrating the Development Environment After NXP MBDT for RADAR is installed, the integration of S32 Design Studio and S32R45 Radar SDK is performed using the MATLAB Live Script: mbd_lax_dependencies_path.mlx The script is located at the root of the NXP MBDT for RADAR installation. Running this script configures the required dependency paths and establishes the connection between MATLAB, the NXP Model-Based Design Toolbox for RADAR, S32 Design Studio, and the S32R45 Radar SDK. Once the script is completed successfully, the environment is ready for simulation, code generation, accelerator kernel execution, and Processor-in-the-Loop (PIL) validation. 7.3 Installation Methods The NXP toolboxes ship as MATLAB Toolbox packages (.mltbx) and can be installed in three ways: Manual install (.mltbx) - Double-click the .mltbx file, or right-click and select Install in MATLAB. The Add-On Manager installs and registers the toolbox automatically. Via NXP Support Package - Install NXP_Support_Package_RADAR from MATLAB Add-Ons, then follow the guided steps to download and install MBDT for RADAR and generate/activate the free license. Via the Automotive Software Package Manager - A bundle installer that walks through toolbox installation, dependency configuration, and license activation. 9 Next Article in the Series This article introduced the software environment, hardware environment, deployment workflow, and high-level radar signal-processing architecture. The next article, "Radar - Processing Chain - RSDK," will provide a detailed analysis of each processing block presented in Section 5: Range FFT Doppler FFT Non-Coherent Combining CFAR Detection Clustering Direction-of-Arrival (DoA) Estimation It will also explain how these algorithms are mapped onto the S32R45 processing resources and how the NXP Radar SDK accelerates the execution of each stage. 10 References MathWorks Radar Signal Simulation and Processing for Automated Driving Radar Toolbox Automated Driving Toolbox NXP S32R45 High-Performance Processor for Imaging Radar S32R45 Evaluation Board TEF82xx 77 GHz Radar Transceiver Model-Based Design Toolbox MBDT for RADAR - Knowledge Base NXP Support Package for RADAR How to install .MLTBX
View full article
S32K3 ADC 使用外部通道 你好。恩智浦团队 如何使用S32K3 ADC的外部通道 . Re: S32K3 ADC Use of external channels 嗨@VaneB 我还有后续问题。 如果我的设计没有多路复用器,但我只想使用例如 ADC1_X[0] 连接传感器 1,ADC1_X[1] 连接传感器 2,ADC1_X[2] 连接传感器 3,我可以将 MA 引脚重复使用于其他用途吗,例如用作 GPIO 输出引脚来驱动 LED? 我的设计基于s32k344 Re: S32K3 ADC Use of external channels NPX团队,您好! 关于这个话题,请问是否可以实现如下图所示的SCH? 非常感谢您的支持。 Re: S32K3 ADC Use of external channels @VaneB 非常感谢您的帮助。 Re: S32K3 ADC Use of external channels 嗨@Niuyanlin 每个 ADC 提供 3 个外部解码信号 (MA),用于从外部模拟多路复用器的 8 个通道中选择 1 个通道,最多可以有 4 个这样的多路复用器来连接 32 个外部通道,这意味着这 4 个多路复用器共享相同的 MA 信号。 ADC 根据当前选择的转换通道,自动设置 MA 来控制这些外部模拟多路复用器。根据掩码寄存器位,对相应的“X”引脚进行采样,并将结果存储在“MA”和“X”组合的匹配位置中。 由于我们的开发板上没有设计外部模拟多路复用器,因此没有实现这样的示例。 Re: S32K3 ADC Use of external channels 你好。VaneB 根据您的提示,我找不到在RTD中使用外部通道ADC的例子。如果你有相应的日常安排,希望你能发给我。非常感谢。 Re: S32K3 ADC Use of external channels 嗨@Niuyanlin 您可以在 RTD 中找到一些可能对您有用的 ADC 实现示例。 BR VaneB
View full article
CAN Bus Handling in MBDT I’m using NXP’s MBDT for S32K344 for configuring FlexCAN0. I want to understand what part of CAN message handling is managed by the NXP blocks/toolbox and what needs to be handled by the application. Are arbitration and buffer handling managed by the driver/toolbox? Example: If I send 0x18FEF111 first, then 0x18FEEF00 neither appears on the bus. But if 0x18FEEF00 is sent first, both are transmitted. When triggered together, only one appears. So, do we need to assign dedicated Tx Hardware Objects to each message ID when sending multiple frames simultaneously? Does the MBDT or SDK handle message prioritization and retries automatically if ACK is not received? If a high-priority ID fails (e.g., no ACK), will it block other messages? How do we detect and recover from this? Do we need to manage buffer allocation or transmission timing manually in the model to avoid blocking or message loss? What’s the best way to configure multiple Tx message IDs in MBDT? With dynamic buffers. Please clarify what is handled internally vs. what we must handle in the application. Example Models Re: CAN Bus Handling in MBDT Hello @SorinIBancila , I've run into a scenario where I need to send more frames than the available HTH hardware object count. Since the CanIf transmit buffering implementation cannot be leverage in S32CT, can you recommend simulink-based buffer solution to this problem? Thanks & regards, Sandesh Re: CAN Bus Handling in MBDT Hello, The 32 Can Hw Object Count is not the limit. You can increase the limit even further, depending on what MCU you have. You can modify the number of Can Hw Object Count and if you put a number too large, the S32CT is going to throw an error. Best regards, Sorin Bancila Re: CAN Bus Handling in MBDT Understood! So If I need to transmit more than 32 messages, should I create additional Tx Hardware Objects? Also, what is the maximum number of Hardware Objects that can be configured under a single CAN transceiver or controller in S32K3 using S32CT? Looking to understand the best way to structure HOHs for large message sets while staying within the limits. Re: CAN Bus Handling in MBDT Hello, How many messages do you think you need to transmit at one time? I've tested on a S32K358 HVBMS reference design the following scenario: Use a single TX Hardware Object and set the Can Hw Object Count to 32 (to allow a maximum of 32 messages in the buffer). In Simulink, I populated the message buffer with 32 messages, increasing the priority as it populates the buffer, to prove the arbitration process. The results: As expected, the first messages sent are with low priority, as the message buffer is not completely populated. Around the 6th message, the buffer is populated and we can see that the messages with higher priority are sent first. Since you want to use a single transceiver, it is not really possible to simultaneously send all the messages at the same time. Best regards, Sorin Bancila Re: CAN Bus Handling in MBDT Hi Sorin, Thanks for your input! I wanted to clarify the best way to configure multiple Tx message IDs in MBDT when using dynamic buffers. In my case, the controller is being used for an EV application with a J1939-based CAN setup involving hundreds of cyclic messages. Creating separate hardware objects for each message in S32CT doesn’t seem scalable or practical. I’m looking to use a single Tx Hardware Object to handle multiple messages dynamically and transmit them simultaneously over one CAN interface. Could you please guide on the recommended setup or best practice for this use case? Also please do suggest the documentation I must refer in order to understand the working of config setting and involved Functions used in MBDT. Re: CAN Bus Handling in MBDT Hello, First of all, I want to point out that the MBDT for S32K3xx is build on top of the S32K3 RTD. The configuration of a peripheral is done in the S32 Configuration Tool to allow full flexibility on the settings you need. So basically, to check if a feature is supported by the NXP's MBDT S32K3xx, you can check the source code used by the peripheral (in the S32K3 RTD) and its available settings in the S32 Configuration Tool. In the toolbox, you can find the implementation for the FlexCAN peripheral here: {toolboxRoot}/src/S32K3_RTD/SW32K3_S32M27x_RTD_R21-11_6.0.0/eclipse/plugins/Can_43_FLEXCAN_TS_T40D34M60I0R0/ Note! The name of the S32K3 RTD might differ, depending on which version of the MBDT S32K3 do you use. The answers to your questions are based on my experience and they might not be totally accurate. 1 & 2 & 5: The toolbox does not handle any arbitration, but I am not sure what options are available in the SDK for this matter. In your example, you create another CanHardwareObject and use it to send the second message, but this approach might be difficult to manage. The second solution might be to increate the Can Hw Object Count to allow more messages in the buffer. 3: The MBDT for S32K3 does not handle any message prioritization. As far as I know, that's the job of the FlexCAN controller to retry to send the message until the ACK is received, while blocking the message the buffer. 4. One way to detect if a message is sent or not is to use interrupt CanIf_TxConfirmation in the Hardware Interrupt Callback to mark that a message is sent. If the interrupt is not triggered for the specified PDU, it means that the message is not sent. Moreover, there is another interrupt (CAN_ControllerBusOff) available that triggers when the conditions for CAN Bus Off are met. In the S32 Configuration Tool, there is an option to automatically recover from Bus Off. If you have any questions, do not hesitate to reply. Best regards,  Sorin Bancila Re: CAN Bus Handling in MBDT Hello, Hello, I think one way to bypass the Hw Object Count limit is to configure multiple CAN controllers and to connect them to the same bus. Then, to avoid receiving messages sent from the other CAN Controller, you can take advantage of filter codes and masks to discard the messages right at the controller level. (offloading the MCU). Then, in the Simulink, you can use both CAN Controller to send data to the bus, either by round robin or any method you find suitable. I did not try this method yet, but I will keep you updated to see if it works. Best regards, Sorin Bancila
View full article
How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hello to everyone on the NXP support team. I am currently working on a project using the S32K314, RTD 7.0.0, and FreeRTOS. I am trying to implement the measurement of the voltage of an external device connected to the MCU, the internal temperature (TEMPSENSE) of the MCU, the internal voltage (ANAMUX) of the MCU, and the bandgap voltage using the MCAL's ADC module. Looking at the measurement results, the voltage of the external device and the bandgap voltage seem to be measured correctly, but the values of the internal temperature and internal voltage of the MCU are different from what I expected. Expected value: MCU internal voltage (VDD_HV_A): 8192 (2.5V, 14-bit resolution) Actual measured value: Approximately 6800–7100 (2.07–2.13V, 14-bit resolution) The MCU power supply voltage is 5.0V. The ADC hardware unit is set to ADC0, and the ADC measurement target is configured as follows: Ch8: MCU internal temperature (TEMPSENSE) Ch9: MCU Internal Voltage (ANAMUX) Chapter 10: Band Gap MCU input voltage = 5.0V ADC initialization code: void AdcAdapter_Init ( void ) { Adc_Calibrate ( ADC0 , & calStatus ) ; Adc_SetupResultBuffer ( ADC0 , Group0Result ) ; IP_DCM_GPR -> DCMRWF1 = ( IP_DCM_GPR -> DCMRWF1 | DCM_GPR_DCMRWF1_SUPPLY_MON_EN ( 1 ) | DCM_GPR_DCMRWF1_VDD_HV_A_VLT_DVDR_EN ( 1 ) | DCM_GPR_DCMRWF1_VDD_HV_B_VLT_DVDR_EN ( 1 ) | DCM_GPR_DCMRWF1_VDD_1_5_VLT_DVDR_EN ( 1 ) ) ; IP_DCM_GPR -> DCMRWF1 = ( IP_DCM_GPR -> DCMRWF1 & ~ DCM_GPR_DCMRWF1_SUPPLY_MON_SEL_MASK ) | DCM_GPR_DCMRWF1_SUPPLY_MON_SEL ( 0U ) ; // VDD_HV_A_DIV Adc_StartGroupConversion ( ADC0 ) ; // AdcConversionStart } ADC data acquisition (all periodic tasks) void AdcAdapter_RunCyclic ( void ) { Adc_StatusType ret = ADC_IDLE ; Std_ReturnType adcStatus ; uint16 temperature ; // 変換完了チェック ret = Adc_GetGroupStatus ( ADC0 ) ; if ( ( ret == ADC_COMPLETED ) || ( ret == ADC_STREAM_COMPLETED ) ) { // 結果を取得 Adc_ReadGroup ( ADC0 , Group0Result ) ; // 次の変換を開始 Adc_StartGroupConversion ( ADC0 ) ; } else { // エラーログ } /* Adc_TempSenseGetTemp Singed Q11.4 */ adcStatus = Adc_TempSenseGetTemp ( ADC0 , mcuTemperature ) ; if ( E_OK == adcStatus ) { temperature = Adc_TempSenseCalculateTemp ( ADC0 , mcuTemperature ) ; } else { // エラーログ } } I believe the ADC values for the ADC0 group can be updated using `Adc_ReadGroup`, but I think you need to use `Adc_TempSenseGetTemp` and `Adc_TempSenseCalculateTemp` to check the MCU's internal temperature. Please let me know if I've overlooked any settings. Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi Senlent-san, Thank you for your quick response. I have already reviewed the sample code you provided and believe I have incorporated it into my code. I interpreted the table you provided as a table of register settings for each clock supplied to the ADC block. However, I was unable to determine which of the ADC settings in MCAL they correspond to. Since I am unable to provide the source code, I am attaching an image of the ADC settings. Please let me know which settings I should change. If there are any other settings screens you need, please let me know. AdcHwUnit> Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi@Teruhiko I didn't see the complete ADC configuration in the information you provided, so please double-check that the ADC clock matches the datasheet requirements. If possible, you can share your test project with me, and I'll check it for you. by the way, take a look at the demo in the link below: https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K344-TempSenser-S32DS36-RTD600-500-400-p24/ta-p/2136187 Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi Senlent-san, Thank you for your advice. Following your advice, I changed the settings as shown below to set the TEMPSENSE sampling time to 1.2 usec.  160MHz = 0.00625usec 1.2usec/0.00625usec = 192 I created a task with a 1-second cycle in FreeRTOS and acquired the ADC values for the MCU voltage (VDD_HV_A) and MCU temperature (TEMPSENSE) every second (collecting 30 seconds’ worth of data). For the MCU voltage, I used the bandgap voltage and converted it to mV using the following compensation formula. (The bandgap voltage showed almost no fluctuation, with a value of around 3975 (approximately 1.2 V) obtained.) AdcCorrection = (1200(mV) * Adc_VCC_HV_A) / Adc_bandgap Mcu Voltage = AdcCorrection * 2  (2 is the voltage division ratio of VDD_HV_A) Additionally, the McuTemp data comes from `Adc_TempSenseGetTemp(ADC0, &mcuTemperature)`. Even taking into account the ADC conversion error of +/- 5.0%, I believe the variation is too large. Are there any suggested solutions?   Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi@Teruhiko From the configuration screenshots and code you provided, I don't see any obvious errors. However, it's important to note that the temperature sensor's sampling time must be greater than 1.2µs; otherwise, it will affect the sampling accuracy. Therefore, I suggest you double check the sampling time before testing. Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 The image for ADC_Config>AdcHwUnit was compressed, resulting in a loss of resolution, so I am re-uploading it. <#1> <#2> <#3> Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi Senlent-san, Thank you for attaching the documentation. Since I am currently measuring channels 32–63, I understand that this corresponds to Sampling Duration 1. Thank you for your prompt response. The issue has been resolved.  Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi@Teruhiko You can directly read the raw data from the temperature channel to observe whether there are fluctuations. If the fluctuations are large, you can continue to try increasing the sampling time. Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi Senlent-san, I interpreted the information in Table 317 as follows. When fmc = 160 MHz: ・ Set the prescaler for calibration to 4 ・ Set the prescaler for normal ADC conversion to 2 ・ Set “ADC High Speed” to Disable The data obtained by applying these settings is shown in the table below. Although averaging reduced the variation, I feel that the variation in the MCU’s internal temperature is still quite significant. The table below shows the MCU temperature data converted from ADC values to °C. (To convert the ADC values to °C, I divided the ADC values by 16.) A variation of 2.55 degrees over a 16-point average is extremely large. I understand that the MCU temperature fluctuates depending on the processing load, but is it normal for it to change this much instantaneously? When measuring the internal temperature of the MCU, is averaging the correct approach?  Re: How to Measure the Internal Temperature and Voltage of an MCU Using the ADC0 Hi Senlent-san, Thank you for you reply. As shown in the figure below, the values stabilized after I increased the Sampling Duration 1/Duration 2 values. I thought the default setting was Sampling Duration 0, but how can I switch between Sampling Duration 0, 1, and 2? (Based on the prescale setting, since the ADC clock is 80 MHz, the duration equivalent to 1.2 μs is 96.)
View full article
i.MX 95 NNStreamer C++ 演示 NPU 问题 环境 | 元器件 | 细节 | |-----------|--------| | 主板 | i.MX 95 | | 电路板支持包。 | lf-6.12.49-2.2.0 | | 内核 | Linux ... 6.12.49-lts-next-gbf3cf0324593 #1 SMP PREEMPT 2026年6月16日星期二 03:46:26 UTC aarch64 | | NNStreamer | 2.4.2 | | TensorFlow Lite | 2.19.0 | | Neutron 委托 | libneutron_delegate.so 报告版本为 v1.0.0-f24d08e5,非零cp,构建于 2025 年 11 月 12 日 | | nnstreamer-examples | v1.6 (SRCREV 062ebd1) 和 v1.9 (SRCREV 37d3d86) — 行为相同 | |相机 | OV5640 MIPI 通过 libcamera (imx8-isi),相机 ID:/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c | 从 meta-nxp-demo-experience/配方示例/imx-nnstreamer-examples/imx-nnstreamer-examples.bb 获取二进制文件,安装在 /opt/gopoint-apps/scripts/machine_learning/nnstreamer/。 模型 所有模型均来自 Yocto gopoint-base-apps 配方(downloads.json,lf-6.12.49_2.2.0 分支),托管于: https://github.com/nxp-imx-support/nxp-demo-experience-assets/raw/lf-6.12.49_2.2.0/models/ 目标模型位于 /opt/gopoint-apps/scripts/machine_learning/nnstreamer/downloads/models/: | 任务 | CPU 型号 | NPU 型号 | |------|-----------|-----------| | 人脸检测 | face-detection/ultraface_slim_uint8_float32.tflite | face-detection/ultraface_slim_uint8_float32_neutron.tflite | | 目标检测 | object-detection/ssdlite_mobilenet_v2_coco_quant_uint8_float32_no_postprocess.tflite | object-detection/ssdlite_mobilenet_v2_coco_quant_uint8_float32_no_postprocess_neutron.tflite | | 分类 | classification/mobilenet_v1_1.0_224_quant_uint8_float32.tflite | classification/mobilenet_v1_1.0_224_quant_uint8_float32_neutron.tflite | 来自同一来源的元数据:labels_mobilenet_quant_v1_224.txtcoco_labels_list.txt,box_priors.txt。 必需的环境变量 i.MX 95 上的 OV5640 需要 libcamera ISI: export CAMERA_BACKEND=libcamera export LIBCAMERA_CAM_DEVICE='/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c'--- 问题 1:人脸检测 神经网络处理单元模式 CAMERA_BACKEND=libcamera \ LIBCAMERA_CAM_DEVICE='/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c' \ /opt/gopoint-apps/scripts/machine_learning/nnstreamer/face_detection/example_face_detection_tflite \ --后端 NPU \ --model_path downloads/models/face-detection/ultraface_slim_uint8_float32_neutron.tflite \ --display_perf 时间 管道日志: 信息:启动应用程序... 调试:libcamerasrc name=cam_src camera-name=/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c \ !video/x-raw,width=640,height=480,framerate=30/1,format=YUY2 !队列 !tee name=t \ t.!队列名称=thread-nn 最大缓冲区大小=2 泄漏=2 \ !imxvideoconvert_g2d name=scale_csc_g2d_0 !video/x-raw,width=320,height=240,format=RGB \ !张量转换器!tensor_filter latency=1 framework=tensorflow-lite \ model=downloads/models/face-detection/ultraface_slim_uint8_float32_neutron.tflite \ custom=Delegate:External,ExtDelegateLib:libneutron_delegate.so name=face_filter \ !张量接收器名称=tsink_fd \ t.!队列名称=thread-img 最大缓冲区大小=2 泄漏=2 !cairooverlay 名称=cairooverlay \ !fpsdisplaysink name=img_tensor text-overlay=false video-sink=waylandsink 信息:NeutronDelegate 委托:49 个节点中有 2 个节点被委托,共 2 个分区。 信息:Neutron 委托版本:v1.0.0-f24d08e5,非零cp。 [libcamera v0.0.0+6194-lf-6.12.49-2.2.0] [ov5640 管道:ov5640 -> csidev-4ad30000.csi -> formatter@20 -> crossbar] 相机 camera.cpp:1215配置流:(0)640x480-YUYV/未设置 调试:管道状态从 NULL 变为 READY。 调试:管道状态从就绪变为暂停。 调试:管道状态从暂停变为播放。 结果:边界框错乱。 CPU 模式——相同的流水线,不同的模型和委托 CAMERA_BACKEND=libcamera \ LIBCAMERA_CAM_DEVICE='/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c' \ /opt/gopoint-apps/scripts/machine_learning/nnstreamer/face_detection/example_face_detection_tflite \ --后端 CPU \ --model_path downloads/models/face-detection/ultraface_slim_uint8_float32.tflite \ --display_perf 时间 日志: 信息:启动应用程序... 信息:已为 CPU 创建 TensorFlow Lite XNNPACK 委托。 调试信息:[相同的相机流程,相同的 imxvideoconvert_g2d] ... tensor_converter!tensor_filter latency=1 framework=tensorflow-lite \ model=downloads/models/face-detection/ultraface_slim_uint8_float32.tflite \ custom=Delegate:XNNPACK,NumThreads:6 ... 调试:管道状态已更改……正在播放。 结果: ✅ 边界框准确。 相同的流程,相同的摄像机,相同的 imxvideoconvert_g2d YUY2→RGB 转换。唯一区别:量化的 .tflite+ XNNPACK 与 _neutron.tflite + neutron 委托。 --- 问题 2:目标检测(SSD MobileNetV2) 神经网络处理单元模式 CAMERA_BACKEND=libcamera \ LIBCAMERA_CAM_DEVICE='/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c' \ /opt/gopoint-apps/scripts/machine_learning/nnstreamer/object_detection/example_detection_mobilenet_ssd_v2_tflite \ --后端 NPU \ --model_path downloads/models/object-detection/ssdlite_mobilenet_v2_coco_quant_uint8_float32_no_postprocess_neutron.tflite \ --labels_path downloads/models/object-detection/coco_labels_list.txt \ --boxes_path downloads/models/object-detection/box_priors.txt \ --display_perf 时间 管道日志: 信息:启动应用程序... 调试:libcamerasrc name=cam_src camera-name=/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c \ !video/x-raw,width=640,height=480,framerate=30/1,format=YUY2 !队列 !tee name=t \ t.!队列名称=thread-nn 最大缓冲区大小=2 泄漏=2 \ !imxvideoconvert_g2d name=scale_csc_g2d_0 !video/x-raw,width=300,height=300,format=RGB \ !张量转换器!tensor_filter latency=1 framework=tensorflow-lite \ model=downloads/models/object-detection/ssdlite_mobilenet_v2_coco_quant_uint8_float32_no_postprocess_neutron.tflite \ custom=Delegate:External,ExtDelegateLib:libneutron_delegate.so name=detection_filter \ !tensor_decoder name=tensor_decode_bounding_boxes_1 mode=bounding_boxes option1=mobilenet-ssd \ option2=downloads/models/object-detection/coco_labels_list.txt \ option3=downloads/models/object-detection/box_priors.txt \ 选项4=640:480 选项5=300:300 !imxvideoconvert_g2d!mix.sink_0 \ t.!队列名称=thread-img 最大缓冲区大小=2 泄漏=2 !mix.sink_1 \ imxcompositor_g2d name=mix sink_0::zorder=2 sink_1::zorder=1 latency=20000000 min-upstream-latency=20000000 \ !cairooverlay 名称=perf!fpsdisplaysink name=img_tensor text-overlay=false video-sink=waylandsink 信息:NeutronDelegate 委托:26 个节点中有 1 个节点被委托,共 1 个分区。 信息:Neutron 委托版本:v1.0.0-f24d08e5,非零cp。 相机 camera.cpp:1215配置流:(0)640x480-YUYV/未设置 调试:管道状态已更改……正在播放。 结果:摄像头画面区域完全黑屏。边界框不准确。 CPU 模式——相同的流水线,不同的模型和委托 CAMERA_BACKEND=libcamera \ LIBCAMERA_CAM_DEVICE='/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c' \ /opt/gopoint-apps/scripts/machine_learning/nnstreamer/object_detection/example_detection_mobilenet_ssd_v2_tflite \ --后端 CPU \ --model_path downloads/models/object-detection/ssdlite_mobilenet_v2_coco_quant_uint8_float32_no_postprocess.tflite \ --labels_path downloads/models/object-detection/coco_labels_list.txt \ --boxes_path downloads/models/object-detection/box_priors.txt \ --display_perf 时间 日志: 信息:启动应用程序... 信息:已为 CPU 创建 TensorFlow Lite XNNPACK 委托。 调试:[相同的管道,相同的 imxvideoconvert_g2d,相同的 imxcompositor_g2d,XNNPACK 代理] 调试:管道状态已更改……正在播放。 结果:摄像头画面区域仍然完全是黑色的(与 NPU 相同)。边界框正确。 CPU和NPU均出现黑屏。人脸检测和分类(不使用 imxcompositor_g2d)显示正常的摄像头画面。 --- 问题 3:分类(MobileNetV1) 神经网络处理单元模式 CAMERA_BACKEND=libcamera \ LIBCAMERA_CAM_DEVICE='/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c' \ /opt/gopoint-apps/scripts/machine_learning/nnstreamer/classification/example_classification_mobilenet_v1_tflite \ --后端 NPU \ --model_path downloads/models/classification/mobilenet_v1_1.0_224_quant_uint8_float32_neutron.tflite \ --labels_path downloads/models/classification/labels_mobilenet_quant_v1_224.txt \ --display_perf 时间 管道日志: 信息:启动应用程序... 调试:libcamerasrc name=cam_src camera-name=/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c \ !video/x-raw,width=640,height=480,framerate=30/1,format=YUY2 !队列 !tee name=t \ t.!队列名称=thread-nn 最大缓冲区大小=2 泄漏=2 \ !imxvideoconvert_g2d name=scale_csc_g2d_0 !video/x-raw,width=224,height=224,format=RGB \ !张量转换器!tensor_filter latency=1 framework=tensorflow-lite \ model=downloads/models/classification/mobilenet_v1_1.0_224_quant_uint8_float32_neutron.tflite \ custom=Delegate:External,ExtDelegateLib:libneutron_delegate.so name=classification_filter \ !张量解码器名称=tensor_decode_labeling_1 模式=图像标注 \ option1=downloads/models/classification/labels_mobilenet_quant_v1_224.txt !overlay.text_sink\ t.!队列名称=thread-img 最大缓冲区大小=2 泄漏=2 \ !textoverlay name=overlay font-desc="Sans, 24" valignment=baseline halignment=center \ !imxvideoconvert_g2d!cairooverlay name=perf \ !fpsdisplaysink name=img_tensor text-overlay=false video-sink=waylandsink 信息:NeutronDelegate 委托:4 个节点中有 1 个节点被委托,共 1 个分区。 信息:Neutron 委托版本:v1.0.0-f24d08e5,非零cp。 相机 camera.cpp:1215配置流:(0)640x480-YUYV/未设置 调试:管道状态已更改……正在播放。 结果:摄像头画面正常。标签始终错误。 CPU 模式——相同的流水线,不同的模型和委托 CAMERA_BACKEND=libcamera \ LIBCAMERA_CAM_DEVICE='/base/soc/bus@42000000/i2c@42530000/ov5640_mipi@3c' \ /opt/gopoint-apps/scripts/machine_learning/nnstreamer/classification/example_classification_mobilenet_v1_tflite \ --后端 CPU \ --model_path downloads/models/classification/mobilenet_v1_1.0_224_quant_uint8_float32.tflite \ --labels_path downloads/models/classification/labels_mobilenet_quant_v1_224.txt \ --display_perf 时间 日志: 信息:启动应用程序... 信息:已为 CPU 创建 TensorFlow Lite XNNPACK 委托。 调试信息:[相同的管道,相同的 imxvideoconvert_g2d,XNNPACK 代理] 调试:管道状态已更改……正在播放。 结果: ✅ 摄像头画面正常。标签正确且能根据摄像机画面做出响应。 --- 摘要 在这三个演示中,CPU 和 NPU 都使用相同的相机管线、相同的 imxvideoconvert_g2d YUY2→RGB 转换以及相同的 GStreamer 管线结构。唯一的区别在于: | 变量 | CPU 测试 | NPU 测试 | |----------|----------|----------| | 模型 | *.tflite(量子化) | *_neutron.tflite | | 委托 | XNNPACK (委托:XNNPACK) | neutron (委托:External,ExtDelegateLib:libneutron_delegate.so)| 结果: | 演示 | CPU(量化 .tflite)+ XNNPACK) | NPU (_neutron.tflite + neutron) | |------|:---:|:---:| 人脸检测——边界框 | ✅ 正确 | ❌ 乱码 | | 目标检测 — 边界框 | ✅ 正确 | ❌ 不准确 | | 分类 — 标签 | ✅ 正确 | ❌ 错误 | 目标检测结果显示,CPU 和 NPU 中的摄像头画面均为黑色。此演示使用 imxcompositor_g2d 进行显示;人脸检测和分类使用 cairooverlay/textoverlay 并正常显示。 Re: i.MX 95 NNStreamer C++ Demo NPU Issues 嗨@Chavira : 板级支持包(BSP)版本为6.12.49 。我通过 Yocto 单独构建了nxp-nnstreamer-examples (SRCREV: 062ebd1 ),然后将编译好的 deb 部署到目标板上。我没有通过 GoPoint 应用程序启动演示程序,而是根据随附的downloads.json文件手动下载了模型文件。并使用前面提到的命令运行程序。 Re: i.MX 95 NNStreamer C++ Demo NPU Issues 嗨@BIG_FLY , 感谢您提供的有关 GoPoint 演示的信息。 请问您能否详细说明一下您是如何运行演示的? 您是直接使用 GoPoint 应用程序运行这些程序,还是自己交叉编译的? 您能否一步一步地描述一下您那边是如何进行演示的? 您使用的是 电路板支持包。 版本 6.12.49 吗? 你用的是哪款板? 这些信息将有助于我们更好地了解您的设备配置并发现任何潜在问题。 此致, 查维拉
View full article
请求提供适用于 Linux 内核 6.1.85 的 IW416 Wi-Fi/BT 驱动程序源代码和构建指南 NXP社区的各位朋友,大家好! 我目前正在将NXP IW416(基于 8997) Wi-Fi/蓝牙模块集成到定制的 SBC 中。我的系统运行的是基于 Yocto 的发行版,内核版本为Linux Kernel 6.1.85 。 我想将 Wi-Fi 和蓝牙驱动程序构建为内核外部模块,但我希望确保我使用的是正确且最稳定的源代码。 请问您能否指导我完成以下事项? 驱动程序源代码:对于内核 6.1.85,我应该使用哪个特定的存储库和分支(或提交)? 构建说明:是否有任何官方文档、应用说明或指南,说明如何正确构建和集成这些驱动程序和所需的固件? 任何帮助或相关资源的指引都将不胜感激。 提前谢谢!   Re: Request for IW416 Wi-Fi/BT driver source code and build guide for Linux Kernel 6.1.85 我的环境配置如下: $ ls -al /lib/firmware/nxp/ drwxr-xr-x 2 root root 4096 2月28日 02:44 ./ drwxr-xr-x 3 root root 4096 2024年2月28日 ../ -rw-r--r-- 1 root root 415996 2024年2月28日 sdioiw416_wlan_v0.bin -rw-r--r-- 1 root root 570976 2024年2月28日 sdiouartiw416_combo_v0.bin -rw-r--r-- 1 root root 154920 Feb 28 2024 uartiw416_bt_v0.bin -rw-r--r-- 1 root root 58 2月 28 02:28 wifi_mod_para.conf   $ cat /lib/firmware/nxp/wifi_mod_para.conf fw_name= "nxp/sdiouartiw416_combo_v0.bin" cal_data_cfg=none   $ lsmod 模块尺寸使用 摩尔 745472 0 mlan 585728 1摩尔   我可以提供 dmesg 日志的相关部分。请问我应该搜索哪些具体的关键词或部分?另外,我想知道它在正常运行时的预期结果/输出是什么。   谢谢! + 启动时,mlan 驱动程序会输出如下日志。 [ 1.312336] wlan:正在加载 MWLAN 驱动程序 [ 1.316381] wlan:向总线驱动程序注册... [ 1.321331] wlan:已完成向总线驱动程序注册 [ 1.326355] wlan:驱动程序已成功加载   Re: Request for IW416 Wi-Fi/BT driver source code and build guide for Linux Kernel 6.1.85 你好, @sunam 固件应放置在 /lib/firmware/nxp/ 目录下。 如果您使用的是 Wi-Fi 和蓝牙组合固件,请按如下方式操作: root@imx8mnevk: /lib/firmware/nxp # ls -l sduartiw416_combo.bin -rw-r--r-- 1 root root 406996 2011年4月5日sduartiw416_combo.bin 安装完成后,请检查/lib/firmware/nxp/wifi_mod_para.conf 中的 wifi 驱动程序加载参数,并再次确认固件名称是否匹配。 如果仍然失败,请提供设备启动时的 dmesg 日志。 顺祝商祺! Christine。 Re: Request for IW416 Wi-Fi/BT driver source code and build guide for Linux Kernel 6.1.85 你好, 我目前正在使用IW416芯片。我已经使用 6.1.55-2.2.2 分支成功构建了驱动程序,并确认驱动程序已正确生成。 但是,它似乎无法正常工作,我怀疑是因为缺少最新的固件。请问固件文件应该放在哪个目录下? 谢谢! Re: Request for IW416 Wi-Fi/BT driver source code and build guide for Linux Kernel 6.1.85 你好, @sunam 1. 请再次确认您使用的是IW416 还是 88W8997 ,它们是不同的芯片组。 对于 IW416, 下载我们最新的固件: imx-firmware/FwImage_IW416_SD at lf-6.18.20_2.0.0 · nxp-imx/imx-firmware · GitHub 下载我们最新的驱动程序: GitHub - nxp-imx/mwifiex at lf-6.18.20_2.0.0 · GitHub 驱动程序源代码与运行 Linux 内核版本2.6.32 到 6.19.0 的主机兼容,因此适用于您的 L6.1.85。 2.组装说明: 是否有任何官方文档、应用说明或指南,介绍如何正确构建和集成这些驱动程序和所需的固件? ==> 请参阅: 如何下载和构建 NXP Wi-Fi 驱动程序 我相信以下文档对您也很有用: 在运行 Linux 操作系统的 i.MX 8M Quad EVK 上使用基于 NXP 的无线模块入门指南 如果您还有其他疑问,请告诉我。 如果不行,请将我的回答标记为解决方案,以便我们关闭此问题。 如果您在使用我们产品的过程中遇到任何问题,欢迎创建新案例。 顺祝商祺! Christine。 Re: Request for IW416 Wi-Fi/BT driver source code and build guide for Linux Kernel 6.1.85 你好, @sunam 通常情况下,它应该打印类似如下的 dmesg 日志: ========= root@imx8mnevk:~# dmesg | grep 无线局域网 [ 5.127546] wlan:正在加载 MWLAN 驱动程序 [ 5.141006] wlan:向总线驱动程序注册... [ 5.213728] wlan:启用 TX SG 模式 [ 5.217262] wlan: mpa_tx.buf_size=65280 [ 5.221136] wlan:启用 RX SG 模式 [ 5.224679] wlan: mpa_rx.buf_size=65280 [ 6.505940] wlan:启用 RX SG 模式 [ 6.585864] wlan: 版本 = SD8987----16.92.21.p155.1-MM6X16540.p33-GPL-(FP92)//这是我们的 88W8987 的示例。 [ 6.624373] wlan:已完成向总线驱动程序注册 [ 6.637582] wlan:驱动程序已成功加载 ======== 您可以按如下方式修改 wifi_mod_para.conf 文件: ====== SDIW416 = { fw_name=nxp/sdiouartiw416_combo_v0.bin cal_data_cfg=none cfg80211_wext=0xf max_sta_bss=1 驱动模式=7 } ======= 如果仍然失败,请提供设备启动时的完整 dmesg 日志。 您可以将 dmesg 日志作为附件上传。 顺祝商祺! Christine。
View full article
使用 S32K3X8EVB-Q289 板载调试器对自定义 S32K358 目标进行编程 我目前正在使用 S32K3X8EVB-Q289 评估板,并基于 S32K358 MCU 开发了定制硬件设计。 请问您能否澄清一下: 官方是否支持使用 EVB 板载调试器对外部 S32K358 目标进行编程/调试? 如果支持,EVB 需要进行哪些跳线设置或硬件修改? 为此应该使用哪个调试连接器? 与使用 S32 调试探针相比,有哪些局限性? 是否有相关文档或应用笔记描述此配置? 感谢您的支持。 问候, 亚什·古普塔 Re: Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target 你好@Yash2530 , 1. 是的,支持使用 S32K3X8EVB-Q289 板载调试器对外部 S32K358 目标进行编程/调试。实际上,EVB 板载 OpenSDA 调试器使用的是 P&E Micro 开发的引导加载程序/调试应用程序 - https://community.nxp.com/t5/S32-Design-Studio/Which-debugging-interface-is-better/mp/1715877 2. 对于此使用情况,EVB 上不需要焊接返工或跳线设置。 3. J55 USB 主机连接器。 4. 实际上,对于外部 S32K358 目标的标准烧录和源代码级调试,EVB 的板载调试器应该足够了。由于我不知道您最看重哪些功能,请您自行比较各项功能: https://www.nxp.com/design/design-center/software/automotive-software-and-tools/s32-design-studio-ide/s32-debugger-for-s32-platform:S32DBG-S32PLATFORM https://www.pemicro.com/products/product_viewDetails.cfm?product_id=15320180&productTab=5045 5. 是的, https://www.nxp.com/webapp/Download? colCode=S32K3X8EVB-Q289HWUM 顺祝商祺! 帕维尔 Re: Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target @PavelL , 尝试对外部控制器进行编程时出现此错误。 CMD>VC 正在验证目标文件 CRC-16 校验值是否与设备范围匹配…… 区块 00400000-0042F4B7 ... 计算出的 CRC-16 值与数据块不匹配。(文件 = $A9EE,设备 = $EDEF) 验证设备闪存时出错 Flash编程过程中发生错误。 信息:DAP IDCODE = 0x6BA02477 信息:DAP 已成功启动。DP CTRL/STAT = 0xF0000000 启动 RESET 脚本 (C:\NXP\S32DS.3.6.7\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_6.1.8.202603121731\supportFiles_ARM\NXP\S32K3xx\S32K358.mac)... REM 启用 MC_ME 模块中选定内核的时钟 延迟200毫秒…… 完毕。 REM 初始化 RAM 和 DMA: REM 初始化 DMA TCD: REM 将有效的可执行代码复制到每个要使用的核心的 RAM 中。 REM 启用 MC_ME 中所需的内核: 延迟20毫秒…… 完毕。 延迟20毫秒…… 完毕。 重置脚本 (C:\NXP\S32DS.3.6.7\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_6.1.8.202603121731\supportFiles_ARM\NXP\S32K3xx\S32K358.mac)完全的。 PEmicro GDB 启动失败:闪存编程期间出错。调试会话结束。 PE错误:下载到设备时出错。调试会话结束。 通过 127.0.0.1 与“127.0.0.1”断开连接。通过端口“53100”与6224断开连接 PE-ERROR:错误:尝试发送响应,但连接已关闭。 通过 127.0.0.1 与“127.0.0.1”断开连接。通过端口“53104”与7224断开连接 信息:DAP IDCODE = 0x6BA02477 目标设备已断开连接。 Yash2530_0-1789183717483.jpegYash2530_0-1789183717483.jpegYash2530_0-1789183717483.jpegYash2530_0-1789183717483.jpegYash2530_0-1789183717483.jpegYash2530_0-1789183717483.jpeg 请帮我解决这些问题。 问候, 亚什·古普塔 Re: Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target 你好@Yash2530 , 我使用 S32K3X8EVB-Q289 和通过 J55 连接的板载 PEmicro 调试器进行了参考测试。 在我的测试中,第一次 CRC 验证也报告了不匹配,因为现有的 flash 内容与正在下载的应用程序不同。然而,编程顺序随后继续进行,包括闪存擦除和编程。因此,初始 CRC 不匹配不一定是根本原因,也不能单独确认安全调试已启用。 重要的区别在于,在你提供的日志中,调试会话在第一个 VC 命令之后立即终止。我没有看到后续用于擦除和编程闪存的 EM 和 PM 命令。 请检查 PEmicro 调试启动配置,特别是是否启用了可执行文件下载和闪存编程。请同时提供从会话开始到结束的完整 PEmicro 日志。日志开头应显示 CM 命令和选定的 .arp 文件。闪存算法。 作为参考,我成功的测试使用了以下针对 HSE 禁用设备的算法: PavelL_0-1789370094591.pngPavelL_0-1789370094591.pngPavelL_0-1789370094591.pngPavelL_0-1789370094591.pngPavelL_0-1789370094591.png 请确认您在配置中选择的算法与您的 S32K358 设备的实际状态相符,例如 HSE 已禁用或 HSE 已启用。   顺便说一下,下次请另开新帖——我们只会在最后一条回复发布7天后才开始追踪社区帖子。我只接收更新订阅邮件,偶尔会错过一些。 顺祝商祺! 帕维尔 Re: Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target 你好@PavelL , 我已经对设备进行了编程,问题出在 JTAG 的 RESET 引脚与板载 MCU 和目标板 MCU 的冲突上。所以我将复位引脚与 JTAG RESET 引脚隔离,编程就可以正常工作了。现在唯一的问题是我需要手动重置MCU。 您是否也使用了自定义目标以及 EVK 板 jtag(J50 和 J55(usb))连接器? 此致, 亚什·古普塔 Re: Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target 你好@Yash2530 , 是的,我使用过外部 PEmicro 调试器和 Lauterbach TRACE32。 根据我的笔记,EVB 上的所有跳线都保持在默认位置,只有 J685 和 J23 被设置为位置 2-3。 供您参考,跳线配置如下: J685:2-3 J23:2-3 J25:1-2 J30:1-2 J31:1-2 J691:1-2 J37:2-3 J746:2-3 J13:1-2 J16:1-2 J701:1-2 在这种配置下,我的设备中编程、调试和自动RESET功能都能正常工作。请将这些跳线设置与您当前的EVB配置进行比较。 顺祝商祺! 帕维尔 Re: Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target 你好@Yash2530 , “提供 i2c 和 spi 示例代码”是一个新话题。为了保持讨论主题的清晰性,请创建一个新的专门讨论主题。 感谢您的理解。 顺祝商祺! 帕维尔 Re: Using S32K3X8EVB-Q289 On-Board Debugger to Program a Custom S32K358 Target @PavelL , 感谢您的回复,这真的很有帮助。您能否也分享一下 I2C 和 SPI 的示例代码?因为 RTD 的示例代码包含环回示例。我尝试通过保持外设的主控状态,使用 SPI 和 I2C 初始化外设,但是我在 SPI 和 I2C 上都没有收到时钟信号,MOSI 和 MISO 也没有响应。如果你能分享一个,那就太好了。 谢谢! 亚什·古普塔
View full article
S32K3 recovery issue when install HSE fw via MU We are currently developing secure boot functionality on the S32K344/S32K314 using HSE, based on the `S32K344_Advanced_SecureBoot` demo from the `S32K3_HSE_DemoExamples`. We have completed most of the feature development and can debug through successfully. In our configuration program, we calculate signatures for the BM, FBL, and APP using ED25519, write them to specified addresses in flash, and configure the SMR and CR for these three applications (BM as pre‑boot SMR, FBL and APP as post‑boot SMR). However, we have encountered some unclear issues and would appreciate your help. We are currently using the FULL_MEM form of HSE. Because we use the ED25519 algorithm to compute signatures for all application binaries, the configuration program takes a long time to execute. If a power failure occurs unexpectedly before the program finishes, we find that HSE enters an unrecoverable error state. Neither power‑cycling nor re‑flashing the firmware makes HSE respond to any host requests anymore. By checking the register at `0x4039C028` (HSE_CONFIG_GPR3), we see the value is `0xC0`; bit 0 has become `0`, which indicates that the HSE firmware may have been erased by SBAF. After power‑up, the MU0 FSR register is also `0`. We therefore tried to re‑install the HSE firmware. Since the normal IVT‑based installation method no longer works, we attempted installation via the MU interface. We simulated the steps described in the documentation, but found that after writing the SRAM address of the Pink Image into the MU Tx register (step 5), the value in HSE_CONFIG_GPR3 immediately changes from `0xC2` back to `0xC0` – i.e., bit 1 goes from `1` to `0` – and we never receive the expected success response `0xDACACADA`. We also referred to a similar issue on the forum:S32K3_The MU installation AB_SWAP process of HSE is incorrect. . We tried performing a functional reset immediately after step 5, but after the reset the new HSE firmware still cannot be installed. Could you please advise how to handle and recover from such a corrupted HSE state? Let me know if you need any adjustments. Re: S32K3 recovery issue when install HSE fw via MU Hi @chengjinwang  I’m unable to read the source files in the project you shared because they are encrypted. Please provide a version with plain (unencrypted) files. A few days ago, I created a Trace32 script to recover the HSE AB_SWAP firmware via the MU interface, so I quickly modified it for the FULL_MEM version. It works on my side - I receive the 0xDACACADA response. Do you wait approximately 1.5 seconds after writing the pink image location before performing any further actions? This delay is not explicitly mentioned in the FULL_MEM installation procedure, but it is required for the AB_SWAP version. This could be the issue. If you are using Trace32, let me know and I can share my script. Regards, Lukas Re: S32K3 recovery issue when install HSE fw via MU Here is the recovery program I'm using for HSE FW installation through MU; could you take a look and see what's wrong? Re: S32K3 recovery issue when install HSE fw via MU The attached file is the unencrypted version of the project I am currently using. For my tests, I am using the S32K344 chip, a PE debugger, and the S32DS project in the attachment. I tried waiting a few seconds after writing the Pink image to receive a successful response from SBAF, but that did not work either. Performing a functional reset directly also did not work. Could you please check if there are any issues with my MU installation routine in the attached project? Re: S32K3 recovery issue when install HSE fw via MU I tested the project on my board. First, I had to fix RAM initialization in startup files because I got hardfault when the pink file was copied to RAM. The RAM initialization is not the best one in these HSE demo examples, so I did quick fix like this: Pemicro debugger initializes the RAM automatically and RAM content is retained over functional resets, so you probably did not see this issue. But it would not work after power-on. I used Trace32 for debugging, so I saw it right at the beginning. Then I modified IVT – I removed pointer to the pink file, so it is not installed automatically after first reset and I can confirm installation via MU. And the result – I got 0xDACACADA and the firmware is installed via MU. So, the procedure is obviously correct. The question is why it does not work on your side. What is the SBAF version on your device? Please read double word at 0x4039_C020. Regards, Lukas Re: S32K3 recovery issue when install HSE fw via MU Additionally, we are currently using HSE FW version 0.2.55.0. Re: S32K3 recovery issue when install HSE fw via MU This is the result I read. Re: S32K3 recovery issue when install HSE fw via MU hello, @lukaszadrapa . I haven't resolved this issue yet. If you have any progress on your end, please let me know. Thank you. Re: S32K3 recovery issue when install HSE fw via MU Thank you! I successfully restored the HSE firmware by directly triggering a SWAP request. However, what puzzles me is that I had been using the FULL_MEM firmware all along—so why was the firmware restored via AB_SWAP in the end? Re: S32K3 recovery issue when install HSE fw via MU I’m sorry for delayed response. You have SBAF version 0.15.0 which is fully compatible with HSE firmware 0.2.55.0. There’s no problem with this. For my test, I erased the firmware completely using service HSE_SRV_ID_ERASE_FW, so there’s no valid backup in passive partition. In your case, it looks like the backup is available, so the flow may be different (not sure why this does not work). I can see in your code that swap only is not implemented. Could you try to add it to your code? This could solve the problem. Regards, Lukas Re: S32K3 recovery issue when install HSE fw via MU That’s interesting. Frankly speaking, I made a mistake – I’m jumping between a lot of customers and I was somehow under impression that you use AB_SWAP, not FULL_MEM. Otherwise I would not recommend it. I can see two possible explanations – if there’s still valid backup of the firmware, it is possible that the “swap” command works also for FULL_MEM version even if it is not described in the MU procedure for FULL_MEM. Second option is that functional resets triggered by your recovery application forced SBAF to erase the firmware completely and then the installation was successful. Not really sure, this is quite hard to reproduce and confirm...
View full article
Reference & Guide Docs for i.MX Linux Release Rev.LF5.15.71_2.2.2 Hello, staff. I'm currently working on i.MX yocto project LF5.15.71_2.2.2 with imx8mp MPU.  I need to access the corresponding User Guide, Reference Manual,  etc for this specific version. However, when searching on the NXP design center, I can only find and download the documentation for the latest 6.x kernel versions. Could anyone please point me in the right direction or provide a direct link to the archived documentation for LF5.15.71_2.2.2? Thanks! Evaluation Board
View full article
EasyEVSE signal board compatibility and availability I’m standing up an EasyEVSE development system and I have a few questions.   From the code revision history (and the 6 May 2026  vs. Dec 2025 versions of CCEVCPGSUG.pdf), it looks it looks like in software version 5.1.2  that support for EVSE-SIG-BRD2X has been removed and the expectation is that the EVSE side will use SIGBRD-HPGP instead.  Is this correct? It looks like software v5.1.2 added much of the support for SIGBRD-HPGP, does the previous version (v5.0.8) still support EVSE-SIG-BRD2X? Is the SIGBRD-HPGP available?  I don’t see it at mouser or digikey, or in NXP’s store. I have two of the EVSE-SIG-BRD2Xs and I’d like to move forward as the SIGBRD-HPGP appears to not be an option right now. Any insights would be appreciated Best Regards,               Chris Re: EasyEVSE signal board compatibility and availability Hi @chrisedwards, As you mention, the updated EVSE platform is designed to leverage the SIGBRD-HPGP on the EVSE side. Currently, the EV side still supports EVSE-SIG-BRD2X, although it can also be implemented using SIGBRD-HPGP. However, considering that you already have both EVSE-SIG-BRD2Xs, and that the SIGBRD-HPGP is still under qualification process (and will likely take some more time for it to be available for the public), I recommend you stick to this setup, and consider the use of a previous SW version before this latest modification. You should be able to use v5.0.8 for support with the two EVSE-SIG-BRD2X setup. BR, Edwin. Re: EasyEVSE signal board compatibility and availability Hi Edwin,  Thank you for your response.  I'm back working on this and am having issues getting EVSE code v5.0.8 that i got from Git to work.  It builds fine and displays the GUI, but when I try to use its debug interface and request the version information, I get a correct response for the 1060 code of 5.0.8, but the version of the sigbrd2x shows as hw: v 255, and sw: v255.255.0.  I seem to recall reading a post that said there was some issue with a communications conflict with the LCD display on the 1060 board.  I can program the sigbrd2x and step code, so I'm pretty confident that that side is executing.  I'm using the EVSE-RT106X-CBL rather than the arduino headers.  My primary symptoms are the version reporting above that seems suspect, and I can't get past the "firmware download" status on the EVSE LCD, and the EVSE code on the 1060 won't start if the sigbrd2x is powered up (I'm powering them separately).  It feels like a communications issue.  Is there a patch / workaround for this?  If so, can you point me to documentation on how to resolve it? Best Regards, Chris Edwards
View full article
2026年にAdopt Meのペットを無料で即座に入手するトップ10の方法 Robloxの「Adopt Me」をプレイしたことがある人なら、レア、レジェンダリー、ウルトラレアのペットを集めるのがどれほどエキサイティングなことか、既にご存知でしょう。ドラゴンやユニコーンからユニークなイベントペットまで、強力なペットコレクションを作ることはゲームの最も楽しい部分の一つです。しかし、誰もがRobuxを使ってインベントリを拡張したいわけではない。朗報です。実際のお金を使わずにAdopt Meのペットを無料で入手する合法的な方法がいくつかあります。 ➤➤ ここをクリックして このガイドでは、Adopt Meでペットを無料で入手するためのトップ10の方法を紹介し、安全かつ効率的にコレクションを増やすお手伝いをします。 1. 毎日ログイン報酬を完了する Adopt Meで無料のペットを手に入れる最も簡単な方法の一つは、毎日ゲームにログインすることです。Adopt Meでは、アクティブなプレイヤーに、ゲーム内通貨(Bucks)、アイテム、そして時折卵を入手できる機会などを含むデイリーボーナスが与えられます。 ログイン連続記録を長く維持すればするほど、より多くの報酬を受け取ることができます。継続が鍵であり、これらの報酬は時間をかけて孵化した貴重なペットになる卵の購入に役立ちます。 2. 無料の卵を孵化させる Adopt Meでは、卵がペットを入手する主な手段です。プレイヤーはゲームプレイで得たバックスを使って様々な卵を購入できます。最も人気のある選択肢には、ひび割れた卵、ペットの卵、ロイヤルエッグなどがあります。 日常の活動に参加し、お金を貯めることで、Robuxを使わずに卵を継続的に購入できます。卵を一つ開けるごとに、レアなペットや伝説のペットを無料で孵化させるチャンスが得られます。 3. 季節イベント情報への参加 Adopt Meは祝日や主要な祝日の際にイベント情報を頻繁に開催しています。これらのイベント情報では、Robuxで購入するのではなく、ゲームプレイチャレンジで獲得できる期間限定のペットが登場することが多いです。 ハロウィン、クリスマス、イースター、夏のイベント情報は、無料のAdopt Meペットを求めるプレイヤーの間で特に人気があります。イベント情報タスクをクリアしたり、イベント情報通貨を集めたりすると、イベント情報終了前に限定ペットをアンロックできます。 4. 他のプレイヤーと賢く取引する ペットのコレクションを増やすには、トレードが最も効果的な方法の一つです。伝説のペットがなくても、コモンペットとアンコモンペットを戦略的に取引することでステップアップできます。 重複しているペットを交換してくれるプレイヤーや、あなたが所有している特定のアイテムを必要としているプレイヤーを探しましょう。時間が経つにつれて、賢い取引は普段は手に入れにくいペットを手に入れる手助けをしてくれます。 必ず公式のゲーム内取引システムを利用し、ゲーム外で無料のペットを約束する詐欺には注意してください。 5. タスクを完了してバックスを獲得する Adopt Meでは、プレイヤーにBucks(ゲーム内通貨)が報酬として与えられる様々なアクティビティが用意されています。ペットへのご給餌、学校への通学、キャンプ、シャワー、その他の日常的な作業をこなすことで、卵子の購入に使える収入が生まれます。 活動的であればあるほど、バックスをより早く貯めることができます。多くの熟練プレイヤーは、定期的にタスクを完了するだけで数千ドルのバックスを獲得し、毎週複数の卵を孵化させている。 6. プレゼント企画に参加する 多くのAdopt Meコンテンツクリエイターは、YouTubeやDiscord、ソーシャルメディアなどのプラットフォームでプレゼント企画を開催しています。これらのプレゼント企画では、伝説のペット、珍しい卵、貴重なアイテムなどがよく登場します。 プレゼント企画に参加する前に、主催者が信頼できる人物であることを確認してください。正規のプレゼント企画では、パスワードやアカウント情報の入力は一切求められません。信頼できるプレゼント企画に参加することは、無料の「Adopt Me」ペットを手に入れる素晴らしい方法です。 7. ペットのレベルアップと成長 プレイヤーは、生まれたばかりのペットよりも、成長したペットを高く評価する傾向がある。タスクを通じてペットの年齢を上げることに時間を投資することで、取引価値を大幅に高めることができます。 成体になったペットは、交換条件によっては複数の若いペットに匹敵する価値があるかもしれない。この戦略を使えば、一般的なペットをより良い機会に変え、最終的にはRobuxを使わずに希少なペットを入手できます。 8. アクティブなAdopt Meコミュニティに参加する Adopt Meコミュニティは、無料のペットを求めるプレイヤーにとって貴重なリソースとなり得ます。Robloxグループ、Discordサーバー、ソーシャルメディアコミュニティでは、取引イベント情報やコンテスト、コミュニティのプレゼント企画がよく開催されています。 活発なコミュニティは、マーケットの価値、イベント情報、安全な取引慣行についても有益なアドバイスを提供します。これらのコミュニティに関わることで、普段なら逃すかもしれない機会につながります。 9.新しいアップデートを活用する Adopt Meのメジャーアップデートでは、毎回新しいコンテンツと機会が追加されます。新しい卵、ペット、イベント情報、ゲームプレイ機能などにより、アクティブなプレイヤーが貴重な報酬を獲得しやすくなることが多いです。 更新のお知らせに注意を払い、新しいコンテンツが公開されたらすぐに参加してください。早期に参加することで、ペットが希少で非常に人気が高まる前に手に入れる助けになることがあります。 10. ペットマネジメントの戦略を活用する ペットを効果的に管理することで、時間とともにより良いペットを迎える可能性が高まります。複数のペットを同時に育て、タスクを効率的に完了させ、可能な限りバックスを節約することに集中しましょう。 多くの成功したプレイヤーは、複数のペットを同時に世話したり、ファミリのゲームプレイ要素を組み合わせて収益を最大化するなどの代替戦略を用います。より良い資源マネジメントは、より多くの卵、孵化、そして最終的にはより多くの無料ペットをもたらします。 無料ペット詐欺を回避するためのヒント Adopt Meで無料のペットを探していると、すぐに伝説のペットを提供すると謳うウェブサイト、動画、または個人に出くわす可能性が高いでしょう。注意深く、以下のセーフティ対策を守ってください: Robloxのパスワードは絶対に他人に教えないでください。 無料のペットを入手できると謳うウェブサイトは避けてください。 公式のAdopt Meトレードシステムのみを使用してください。 参加する前に、プレゼント企画の主催者を確認してください。 Robloxアカウントで二要素認証を有効にしてください。 正当な無料ペットは、ゲームプレイ、取引、イベント情報、信頼できるコミュニティ活動を通じて得られることを忘れないでください。 まとめ Adopt Meで無料のペットを入手するのに、Robuxを使う必要はありません。毎日ログインし、タスクをこなし、イベント情報に参加し、卵を孵化させ、プレゼント企画に参加し、賢く取引することで、着実に素晴らしいペットコレクションを築くことができます。 最も成功したプレイヤーはこれらの方法をいくつか組み合わせ、ゲーム内で活動し続けます。時間をかけて、忍耐強く継続すれば、リアルマネーを使わずにレア、超レア、さらにはレジェンダリーのペットをアンロックできるようになります。 初めてペットを飼いたい初心者の方も、コレクションを増やしたいベテランの方も、Adopt Meで無料のペットを手に入れるためのこのトップ10の方法を使えば、お財布に負担をかけずにAdopt Meのすべてを楽しむことができます。
View full article
S32K314 UART I recently encountered a problem while debugging the S32K314 serial port. Previously, I was using the GD32/STM32 platform, and when using the serial port for real-time printing, my approach was as follows: the application layer processed the printed characters, and the underlying write function was called to send them out via interrupt. This data is written directly to the data register and sent out quickly. Therefore, there's no need to panic when the application layer receives a large amount of data, as there's a queue, and data transmission is fast. However, when using S32K3, I found that the asynchronous send function `Lpuart_Uart_Ip_AsyncSend` is relatively slow, with nested layers. Relatively speaking, for the same number of bytes of printed data, S32K3 is much slower than GD32. AI provides a solution. In the application layer, the write-by-write method is changed to writing to the underlying layer using a large buffer. Then, the underlying write function and interrupt are handled in the following way. This method does improve speed, but it requires a lot of RAM. Is there a better way that is better in terms of both space and efficiency? Re: S32K314 UART do you use any operating system at MCU level or just baremetal? Re: S32K314 UART Operating system used Re: S32K314 UART Hi@ Joker_Y If possible, you can try to implement LPUART transmission directly using registers. Re: S32K314 UART Could you please provide an example of how to do this?
View full article
S32プラットフォームの問題に対するS32 Design StudioでのRTDインポート S32 Design Studioで直面している主な問題は、.cの統合時に問題ですおよび .hファイルを作成してプロジェクトエクスプローラーから選択したら、SDKsにバージョンが表示されず、次の問題は設定ツールで、つまりMCUが選択されていないと表示されます。外部からRTDをインポートしても、MCUは選択されません。このツールでもプロジェクトを選択できません。 Re: RTD Import in S32 Design Studio for S32 Platform issue ハイ 動画の説明書(「S32 Design Studio 3.6.0でRTD 5.0.0のダウンロード、インストール、構成方法」)をご参照ください。必要なS32K3 RTDの特定バージョンをダウンロードしてインストールしてください。最新バージョンはS32K3 RTD 7.0.1にアップデートされました。 そして、 Arm プロセッサ用のNXP GCC v10.2 build 1728 をインストールする のも忘れないでください よろしくお願いします、 ロビン ------------------------------------------------------------------------------- 注記: この投稿があなたの質問への回答になっている場合は、「解決策として承認」ボタンをクリックしてください。ありがとう! - 前回の投稿から7週間Threadをフォローしており、その後の返信は無視しています もし後で関連する質問があれば、新しいThreadを開き、閉じたThreadを参照してください。 -------------------------------------------------------------------------------
View full article
eMIOSまたはGTMを使用してS32Z280で4.9MHzのクロック/PWM出力を生成する NXPチームの皆様、こんにちは。 私はS32DSとRTD 2.0.1を使用してS32Z280 EVBを開発しています。 私の要件は、外部ピンから約4.9MHzの連続出力クロック/方形波を生成することです。 最初は、以下の設定でeMIOS PWMを使ってみました。 MCU:S32Z280 RTDバージョン:2.0.1 eMIOSインスタンス: eMIOS_1 チャネル:CH4 モード: OPWFMB タイムベース: EMIOS_PWM_IP_BUS_INTERNAL 期間数: 100 デューティサイクル:50 eMIOSクロック:48MHz ピンマルチプレクサはeMIOS_1_CH4(PAD_007 / AD12)に設定されています。 初期化コード: Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); while (CLOCK_IP_PLL_LOCKED != Clock_Ip_GetPllStatus()) { } Clock_Ip_DistributePll(); Emios_Pwm_Ip_InitChannel(1U, &Emios_Pwm_Ip_I1_Ch4); しかし、オシロスコープを使って出力ピンに波形を観測しても何も現れません。 私の質問は以下のとおりです。 eMIOSはS32Z280で4.9 MHzの方形波を生成するための推奨ペリフェラルでしょうか? OPWFMBモードでは、マスターバス/タイムベースの追加設定が必要ですか? 安定した4.9MHz出力を生成するには、GTM TOM/ATOMの方がより良い解決策でしょうか? 外部ピンで~5 MHzの出力信号を生成するための例(eMIOSまたはGTM)を教えてもらえますか? eMIOSクロックを有効にする以外に、何か特別なクロック設定が必要ですか? 何かご指導や参考となるプロジェクト例があれば、大変ありがたく思います。 よろしくお願いします。 BR、 カルティク Re: Generating a 4.9 MHz Clock/PWM Output on S32Z280 using eMIOS or GTM こんにちは、 karthik_nikilさん PWMの例はRTDパッケージ内の以下の写真で見ることができます。それぞれの例は、異なる基盤となるモジュールに対応しています。アプリケーションの要件に応じて必要な波形を生成するモジュールを試してみるのも良いでしょう。 他に問題がある場合はいつでもお問い合わせください。 BR ジョーイ Re: Generating a 4.9 MHz Clock/PWM Output on S32Z280 using eMIOS or GTM こんにちは、 karthik_nikilさん お問い合わせいただきありがとうございます。 ご質問を拝受いたしました。確認させていただきます。 BR ジョーイ
View full article
S32K用のコンパイルスクリプトの使い方は? NXPのエキスパートの皆様、こんにちは。 現在、私はIDE(「S32 Design Studio for S32 Platform 3.4」)を使用して、プロジェクトを手動でコンパイルしています。 スクリプトを使用して、プロジェクト内のリンクファイルのクリーンアップ、更新、ビルディング、切り替えなどの操作を実行することはできますか? こうすることで、IDEを開いて操作することなく、ある程度の自動コンパイルを実現できます。 Re: How to use the compilation script for S32K? petervlnaさん、ありがとうございます! 試してみます、どうもありがとうございます! Re: How to use the compilation script for S32K? こんにちは、 はい、S32 Design StudioのビルドはIDEのGUIを開かなくても自動化できます。S32 Design StudioはEclipseベースなので、Eclipseのヘッドレスビルドメカニズムを利用してコマンドラインコンパイルを行うことができます。 こちらのリンクからチュートリアルをご覧いただけます。 https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/S32DS-list-of-HOWTOs/ta-p/1113475 コマンドラインインターフェースの場合: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-S32-Design-Studio-Command-Line-Interface/ta-p/1112410 よろしくお願いいたします。 ピーター
View full article
Could you provide the Motor Control eTPU Library source package? I am using MPC5777C eTPU PWMM for 3-phase motor PWM generation. The Motor Control eTPU Library document states that the library release package includes eTPU source files: etpuc_ .c / etpuc_ .h For PWMM, I need: etpuc_pwmm.c etpuc_pwmm.h the CodeWarrior eTPU project or build environment I need to modify the PWMM edge placement algorithm, specifically the center-aligned / inverted center-aligned edge calculation, to implement phase-dependent carrier polarity for AZSPWM/NSPWM. Could you provide the Motor Control eTPU Library source package or advise how to obtain AN5335SW / the PWMM eTPU source code? Re: Could you provide the Motor Control eTPU Library source package? Hello, In order to get source code, please rise a ticket at NXP.com as this wont be handled over the public community. Best regards, Peter
View full article
LCU 输出通过 S32K344 上的 TRGMUX 路由到 eMIOS 输入 大家好, 我正在研究 S32K344,使用LCU + TRGMUX + EMIOS实现正交解码器,遵循参考架构(编码器--> TRGMUX--> LCU--> TRGMUX--> EMIOS)。 编码器 A/B 信号通过 TRGMUX 正确路由至 LCU LCU 逻辑已配置并生成预期输出(CW/CCW 脉冲) 我可以观察到 内部的 LCU_OUT 信号(通过调试验证) 使用当前的 LCU 逻辑配置,我可以检测到旋转方向。不过,为了进行速度测量,我想使用 LCU 输出信号(AO 和 BO),并通过 TRGMUX 将其内部路由到 eMIOS,而不是使用外部引脚环回。   但是我无法使用emiOS输入捕获来测量或捕获LCU输出信号,即使我通过TRGMUX进行路由。 S32K344 是否完全支持 LCU → eMIOS 通过 TRGMUX 的内部路由? 在这种情况下,哪些 eMIOS 通道支持 TRGMUX 输入? 是否需要在 LCU/TRGMUX/eMIOS 中进行额外配置以启用信号传播? 将 LCU_OUTx 用作 TRGMUX 信号源是否有已知的限制或约束? 任何有关 IPP 输入映射和 TRGMUX 路由的工作示例、配置提示或说明都将非常有用。 我附上了我的项目配置以供参考。   先行致谢。 Re: LCU output routing to eMIOS input via TRGMUX on S32K344 你好@kapidlitap 请分享您的测试项目,以便我帮您检查、 Re: LCU output routing to eMIOS input via TRGMUX on S32K344 你好@kapidlitap 使用 TRGMUX 时,不要忘记为 emios 配置正确的 SIUL_IMCR 值。 默认值为 0,因此无法捕捉到任何信号。 为 emios0_ch2、 Siul2_Port_Ip_SetInputBuffer(NULL, 0, FALSE, 562-512, PORT_INPUT_MUX_ALT5);//eMIOS0_CH2 IMCR562 to 0x5 (TRGMUX_INT_OUT33) Re: LCU output routing to eMIOS input via TRGMUX on S32K344 你好@Senlent、 谢谢您的答复。正如你所建议的那样,它成功了。 关于同样的配置,我还需要一些帮助。 如何以良好的分辨率测量 1 赫兹至 10 千赫兹的频率? 有没有办法更改特定 emiOS 频道的预分频器,而不是更改整个总线的预分频器? 或者,您能否建议其他更精确测量 PWM 频率的模式或方法? 预先感谢您的支持。 Re: LCU output routing to eMIOS input via TRGMUX on S32K344 你好@kapidlitap 对于 S32K3 上的 1 Hz 至 10 kHz 测量,请使用带有模数计数器时基的 ICU (IPWM/IPM),是的,eMIOS 通道预分频器可以通过 Cn[UCPRE] 按通道进行调整,而 MCR[GPRE] 保持全局。
View full article
帮助 IMX8QM 上的 M4 和 Linux 之间进行 RPMSG TTY 通信 你好! 我最近一直在尝试使用 Linux 内核 6.6 在已有的 Buildroot 项目中设置 imx_rpmsg_tty 示例。我无法让它正常工作,因为 virtio 通常是由 M4 填充的(因为 virtio 的驱动程序看到了通道),但我没有收到返回的通信。我尝试了多种组合,尝试从我找到的不同设备树中汲取灵感,并尝试使用SCFW对所有必需的资源进行分区,但无济于事。我们使用 mkimage 将 M4 图像嵌入图像中。在工作时将 JTAG 连接到 M4 似乎效果不佳,或者根本不起作用,但大家一致认为 M4 在 Linux 启动后会出现硬故障。 您能否提供我们的项目中需要具备的必要元素,以便我们利用这一机制?这里我的意思是必需的设备树条目,包括配置、SCFW 分区片段等。或者是非常详细的清单提示,告诉我需要检查哪些内容,哪些配置可能有误。我真的很茫然。 i.MX 8 系列 | i.MX 8QuadMax (8QM) | 8QuadPlus Linux
View full article
Reboot command operation and reset mechanism on i.MX8MP and i.MX93 Background: This article discusses the reboot mechanism on the i.MX8MP and i.MX93 platforms. It aims to help customers understand how the reboot command works. We will discuss two different kernel versions separately.   1. Linux version : LF_6.12.34_2.1.0 The executable file for the reboot command is as follows: When the ”reboot“ command is executed, the system enters the ”do_kernel_restart()“ function and executes the reboot mechanism by determining the priority of the registered functions. Since the ”reboot.c“ file does not print out the registered functions, a print function is added to the file to identify the function that is ultimately executed.   The print output is as follows: As shown in the figure above, in version 5.12, the reboot is performed via a reset executed by psci. Continuing to trace the ”psci_sys_reset()“ function, we can see that the system sends the function ID via the PSCI interface to initiate an SMC call, instructing the underlying firmware (ATF/EL3) to perform a system reboot (typically a cold reset). The value of PSCI_0_2_FN_SYSTEM_RESET is 0x80000009   According to the Arm Power State Coordination Interface Platform Design Document, this ID represents a cold reset of the system.     2. Linux version : LF_6.18.2_1.0.0 Use the same debugging method to examine the reboot mechanism in version 6.18 As shown in the output below, in version 6.18, the system reset is triggered by the `sys_off_notify()` function. The final execution function is pca9450_i2c_restart_handler()   By examining the `pca9450_i2c_restart_handler()` function, we can see that the system writes a `SW_RST_COMMAND` value to the PMIC via I²C, where `SW_RST_COMMAND = 0x14`. According to the PMIC data sheet, 10b = Cold Reset; all voltage regulators are reset except LDO1/LDO2 Summary: Regardless of the kernel version, the `reboot` command triggers a system cold reset. The triggering mechanism has been updated in versions 6.18 and later. IMX8MPLUSEVK
View full article
functional group properties question Hi Nxp experts, I opened a few examples, found the functional group is like: PortContainer_0_VS_0, and some examples the functional group is: PortContainer_0_BOARD_InitPeripherals. What is the purpose of the Functional Group, and is it possible to modify it manually?   Thanks   Re: functional group properties question Hi @cszhang  While the available documentation on this topic is somewhat limited, it has been discussed in several community threads. I recommend referring to the thread Resources to understand functional groups in S32 Design Studio for S32 Platform IDE, as it provides useful insights and can help you better understand how functional groups work in S32DS. BR, VaneB
View full article