Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
IMX8M Plus GPU 动态随机存取存储器(DRAM) 竞争 我们在 IMX8M Plus 上运行 Yocto Linux。 我们注意到,在任何 GPU 活动期间,CPU 访问内存时都会出现巨大的延迟峰值(1-3 毫秒峰值)。这是一个大问题,因为我们使用 XDP 进行网络连接。 我们尝试调整 IMX8MP_ICM_A53、IMX8MP_ICM_GPU3D 和 IMX8MP_ICM_GPU2D,将它们设置为 7、2、2 以进行 QoS 控制。这使得延迟峰值出现的频率降低,但它们仍然存在。我们发现的唯一选择是完全不进行任何 GPU 活动或从设备树中删除 GPU,但这对于我们的使用场景来说是不可接受的。是否还有其他设置可以调整以缓解这种现象?GPU锁定动态随机存取存储器\(DRAM\)的时间不能超过50-100微秒。 图形与显示 Linux Re: IMX8M Plus GPU DRAM contention 嗨@richardlovgren , 感谢您联系恩智浦技术支持! 请问您使用的是哪个BSP版本? 这个问题在 EVK 上也会出现吗?还是只出现在你的定制硬件上? 能否也提供日志文件、设备树以及其他相关信息,以便我能够调查和诊断问题? 此外,请分享重现问题的具体步骤,以便我可以在我的环境中尝试重现该问题。 此致, 查维拉
View full article
SGTL5000XNLA3/R2 部分处于激活状态 大家好, SGTL5000XNLA3/R2 这个部件是否处于激活状态?我们可以把它用于新设计吗? 数据手册中提及的EOL Re: SGTL5000XNLA3/R2 is part is active 好的,谢谢你的回复。 Re: SGTL5000XNLA3/R2 is part is active SGTL5000XNLA3 产品信息 | 恩智浦半导体 数据表显示:
View full article
SGTL5000XNLA3/R2 is part is active Hi Team, is this part is active SGTL5000XNLA3/R2? Can we use it for new design Datasheet mentioned asEOL Re: SGTL5000XNLA3/R2 is part is active Ok. Thanks for the response Re: SGTL5000XNLA3/R2 is part is active SGTL5000XNLA3 Product Information | NXP Semiconductors datasheet shows :
View full article
IMX8M Plus GPU DRAM競合 IMX8M PlusでYocto Linuxを運用しています 私たちが気づいたのは、GPUの作業中にCPUからのメモリアクセス時に1〜3msの急激なレイテンシスパイクが発生することです。これは非常に大きな問題です。なぜなら、私たちはネットワーク接続にXDPを使用しているからです。 QoS制御のために、IMX8MP_ICM_A53、IMX8MP_ICM_GPU3D、IMX8MP_ICM_GPU2Dを7、2、2に設定して調整を試みました。これによりレイテンシの急上昇は少なくなりましたが、それでも存在しています。唯一見つけた選択肢は、GPUの活動を一切行わないか、デバイスツリーからGPUを削除することでしたが、これは私たちの用途には受け入れられません。この挙動を緩和するために調整できる他の設定はありますか?GPUがDRAMをロックする時間はせいぜい50〜100μs以上は許されません グラフィックスとディスプレイ Linux Re: IMX8M Plus GPU DRAM contention こんにちは@richardlovgren。 NXPサポートにご連絡いただきありがとうございます! どのBSPバージョンを使っているのか教えていただけますか? この問題はEVKでも再現しますか?それとも、カスタムハードウェアでのみ発生しますか? ログファイルやデバイスツリー、その他関連情報も教えていただけますか?私側で問題を調査・診断できるように。 また、問題を再現するための正確な手順も教えてください。私のセットアップで再現できるよう。 よろしくお願いします、 チャビラ
View full article
Automotive Steering Control Using FRDM-A-S32K3XX Microcontrollers 1. Overview This module demonstrates how to implement a steering control system using Pulse Width Modulation (PWM) on NXP S32K3 microcontrollers. The application reads an analog input from a potentiometer (simulating a steering wheel) and converts it into a servo motor position. As the input changes, the servo motor reacts in real time, mimicking how steering systems work in modern vehicles. This example is based on Application Code Hub demonstrations for: PWM-Based Steering Control for FRDM-A-S32K344 PWM-Based Steering Control for FRDM-A-S32K312 In this workshop, a POT Click simulates the steering wheel position. When the student rotates it, an analog voltage proportional to the angle is read by the MCU through the ADC, scaled in software, and converted into a PWM duty cycle. The PWM is generated by the Servo Click (configured by the MCU over I²C) and drives a Micro Servo motor SG 180°, whose angle tracks the potentiometer in real time. Beyond the technical implementation, the course serves as a foundation for the Eat-Sleep-Code-Repeat learning initiative, encouraging a hands-on approach where students continuously learn, develop, test, and improve automotive embedded applications using real hardware and practical examples. 2. Learning Scope After completing this course, participants should be able to:   Understand a basic steering control system and the ideas behind EPS and steer-by-wire. Use the POT Click as a simulated steering-wheel input. Acquire analog values (0–3.3 V) using the ADC and understand analog-to-digital conversion. Perform signal scaling from the ADC range to a servo angle / PWM duty cycle. Generate PWM signals to drive a servo motor. Configure the Servo Click over I²C using the OE (Output Enable) pin. Recognize the actuation data flow: sensor input → MCU processing → PWM actuation. Import, build, flash, and debug an ACH project in S32 Design Studio 3.6.5. Understand why steering functions are relevant for functional safety. 3. System Architecture The three elements capture exactly the basic idea of the system in the demo: Input: Potentiometer (POT Click simulates the steering-wheel position) Processing: S32K3 MCU (reads the ADC, scales the value, commands the actuator) Output: Servo motor controlled via PWM (Micro Servo SG 180°) This matches the classic flow of an embedded actuation system: sensor → processing → actuator. Functional Flow The system operates continuously as follows: The potentiometer generates an analog voltage based on its position The ADC converts this voltage into a digital value The application scales this value into a steering angle The system generates a PWM signal based on the angle The servo motor moves accordingly This loop runs continuously to ensure real-time control. Steering Monitoring Application Architecture 4. Key Concepts 4.1 ADC (Analog-to-Digital Converter) The POT Click outputs 0–3.3 V depending on the wiper position. The ADC samples this voltage at regular intervals and quantizes it into a digital code (a 12-bit ADC produces values between 0 and 4095). The further the potentiometer is turned, the higher (or lower) the digital sample. ADC acquisition is the foundation of automotive sensing — used for torque, throttle, battery voltage, and many others. 4.2 Signal Scaling — From ADC to Servo Angle The ADC range (for example 0–4095) and the servo range (0°–180°, expressed as a PWM duty cycle) are different. The application performs a linear mapping so that one end of the potentiometer corresponds to one steering extreme and the other end to the opposite. This is the same scaling used in real EPS systems, where a hardware reading is converted into a normalized control command. 4.3 PWM — Pulse-Width Modulation and Servo Control PWM switches a digital output on and off at a fixed frequency, varying the duty cycle (the fraction of time the signal is high). A hobby servo such as the SG 180° interprets this duty cycle as a position command. In this demo, the PWM is not generated by the MCU itself but by the Servo Click's dedicated PWM controller, which the MCU configures over I²C — a typical embedded pattern that offloads time-critical signal generation and keeps the CPU free for application logic. 4.4 I²C — Configuring the Servo Click I²C — Inter-Integrated Circuit is a two-wire serial bus made of SDA (data) and SCL (clock). The S32K3 uses LPI2C1 on PTC6 (SDA) and PTC7 (SCL) to configure the Servo Click — PWM frequency, channel, and duty cycle. The OE — Output Enable pin on PTB17 is an additional control line that enables or disables the PWM outputs without reconfiguring the chip, which is also useful for a quick "safe stop" behavior. 4.5 POT Click as Steering Wheel The POT Click is a simplified, safe stand-in for a real steering sensor. The student rotates it by hand, the voltage changes, the MCU reads it through the ADC, scales it, and the servo reacts. 4.6 Data Flow at a Glance Physical rotation → analog voltage → ADC sample → scaled command (angle / duty cycle) → I²C configuration of the Servo Click → PWM signal → servo angle. This direct chain from the student's hand to the servo shaft is the main educational value of the demo. 5. Hardware and Software Setup Required Hardware Component Image Purpose FRDM-A-S32K312 Alternative MCU platform used to run the steering application and process steering inputs. FRDM-A-S32K344 Alternative MCU platform used to run the steering application and control connected peripherals. FRDM-K64 Click Shield mikroBUS expansion board used to connect Click modules to the FRDM platform. Servo Click PWM driver board used to control the servo motor position. POT Click   Potentiometer module used to simulate steering wheel input. Micro Servo SG 180°                     Actuator used to convert control signals into steering movement. USB-C / 12 V supply — Provides power and enables programming and debugging of the system. The example applications demonstrate how these peripherals are connected to the MCU pins and used to simulate steering wheel input and actuator control. Steering Control Monitoring on FRDM-A-S32K312 Steering Control Monitoring on FRDM-A-S32K344       Software Environment S32 Design Studio IDE S32K3 Automotive Software Package Application Code Hub project import PWM-Based Steering Control for FRDM-A-S32K344 PWM-Based Steering Control for FRDM-A-S32K312 6. Implementation Guide Step Action Sub-steps Expected Result 1 Import the Project Open S32 Design Studio Select “Import project from Application Code Hub” Search for the steering demo Use the GitHub link for automatic configuration Select main branch Import project Project successfully appears in workspace 2 Build the Application Right-click project Select “Update Code and Build Project” Confirm SDK component management Build completes with no errors and generates .elf file 3 Connect Hardware Connect USB cable (and 12V supply for S32K312) Attach click boards Verify wiring Board is powered and detected by IDE 4 Flash and Run Open Debug Configurations Select “debug_flash_pemicro” Start debugging Application runs continuously 5 Functional Validation Rotate the potentiometer Observe servo movement Servo follows potentiometer position in real time 7. Signal Behavior and Control Logic Figure: Steering control signal mapping. The 12-bit ADC value (0–4095) is linearly mapped to a servo angle (0°–180°) and a matching PWM duty cycle (1.0–2.0 ms), with reference points at Left, Center and Right. At startup the servo moves to the neutral position; during operation, any input change produces an immediate, proportional reaction — implementing a basic steer-by-wire behavior. 8. Troubleshooting Issue Possible Actions Board Not Detected Check USB cable and drivers Verify debugger connection Restart IDE No Servo Movement Verify PWM configuration Check servo wiring Ensure correct power supply Incorrect Behavior Check ADC configuration Validate scaling function Ensure PWM duty cycle mapping is correct Unstable Movement Add signal filtering Check power stability 9. Extending the Application The basic implementation can be extended in several ways: Steering Range Control Restrict or extend the actuator's range of motion Define software-based limits to protect the mechanics Input Direction Inversion Reverse how the actuator responds to the input Useful for left-hand vs. right-hand drive calibration Noise Filtering Apply software filtering to stabilize readings Avoid jitter near the center position Scaling Logic Exploration Identify and analyze how the input is mapped to the output Connect software math with hardware behavior Fault-Handling Behavior Add a mechanism that reacts to a detected fault Transition the system into a safer state State Machine Implementation A more advanced approach is to implement a state machine: Idle Active Fault 10. Safety Context This example reflects key automotive principles: Continuous monitoring of driver input Immediate response to control signals Reliable actuator control In real systems: Redundancy is required Fault detection mechanisms are implemented Systems must comply with ISO 26262 (functional safety standard) Steer-by-wire systems require high reliability since there is no direct mechanical link. 11. Conclusion This module demonstrates how a simple embedded system can implement steering control using ADC input and PWM output. It shows how: Analog input is acquired Data is processed in real time Actuators are controlled using PWM Result on FRDM-A-S32K312 Result on FRDM-A-S32K344 The course provides a strong foundation for more advanced systems, including filtering, state machines, and safety-oriented designs.
View full article
Automotive Transmission Control Using FRDM-A-S32K344 Microcontrollers 1. Overview The application demonstrates actuator control concepts commonly encountered in automotive transmission systems using the FRDM-A-S32K344 development platform. The application showcases how analog input acquisition, signal processing, and actuator control can be combined to emulate the behavior of an automotive transmission control module. The solution is based on an Application Code Hub example designed for the FRDM-A-S32K344 platform. Transmission Control Module On FRDM-A-S32K344  The demonstration uses a potentiometer as the primary input device, representing the driver's throttle command. The analog signal is sampled using the ADC peripheral and fed into a transmission model that simulates vehicle speed, automatically selects one of six forward gears or neutral, and estimates engine RPM. The current gear is physically indicated by a servo motor, while a DC motor reflects the throttle input through a variable PWM duty cycle, emulating the drivetrain response of a real vehicle.   The example highlights the interaction between analog sensing, ADC conversion, transmission control algorithms, I²C communication, PWM generation, and actuator control commonly found in automotive embedded systems.   More than a technical course, this program embodies the Eat-Sleep-Code-Repeat approach to learning, where students learn by doing. By repeatedly designing, coding, testing, and refining automotive embedded applications on real hardware platforms, participants build both practical skills and the confidence needed to tackle real-world engineering challenges. 2. Learning Scope This article focuses on both practical implementation and core embedded system concepts: Analog signal acquisition using ADC Potentiometer-based continuous control inputs PWM generation using the eMIOS peripheral I²C communication with an external PWM controller Servo motor position control through an external PWM driver DC motor speed control with a dead-band region Automatic gear selection with shift hysteresis Engine RPM estimation and smoothing Real-time embedded control loops running at a fixed update rate Signal mapping and actuator response The example provides a practical introduction to automotive control systems where continuous sensor values drive actuator behavior through a simulated transmission model. 3. System Architecture The system follows a typical embedded control structure organised around a periodic control loop: Input: Analog throttle signal from the potentiometer Processing: S32K3 microcontroller running the transmission model (vehicle speed, gear selection, RPM) Output: Servo motor position (via I²C to an external PWM controller) and DC motor speed (via eMIOS PWM) Functional Flow The potentiometer voltage is sampled by the ADC and converted into a throttle command The MCU updates the transmission model, computing the simulated vehicle speed and selecting the appropriate gear The current gear is sent to the external PWM controller through I²C, which positions the servo motor accordingly The DC motor speed is updated through an eMIOS PWM channel proportional to the throttle command The entire cycle repeats at a fixed update rate to keep the actuators synchronised Transmission Control Application Architecture 4. Key Concepts 4.1 Control Principle Unlike systems based on push buttons or digital switches, this implementation uses a continuous analog input signal. The potentiometer provides a variable voltage level that represents the driver's throttle command. This value is continuously monitored and converted into a digital representation using the ADC peripheral. The processed value feeds a transmission model that simulates vehicle speed, selects a gear, and estimates engine RPM, which are then translated into commands for the servo (gear display) and the DC motor (speed). This approach allows smooth transitions instead of abrupt state changes and better reflects real-world automotive control systems. 4.2 Analog Input Acquisition The potentiometer acts as a variable voltage divider. As the potentiometer position changes, the output voltage changes continuously, the ADC acquires the voltage, and the MCU converts it into a throttle percentage. This value becomes the primary input variable for the transmission model. This process mirrors how many automotive sensors operate, where physical movement or operating conditions are converted into an analog voltage signal that must be processed by the control unit. 4.3 Servo Motor Control via I²C and External PWM Controller Unlike the DC motor, the servo motor is not driven directly by an MCU PWM channel. Instead, the MCU sends I²C commands to an external PWM controller located on the Servo Click board, which in turn generates the PWM pulses required to position the servo shaft. The transmission model computes the current gear and provides it as an input; the MCU translates the gear number into a pulse-width value and sends it to the external controller. Each discrete gear position corresponds to a specific servo angle, so the servo acts as a physical gear indicator on a graduated scale. 4.4 PWM-Based DC Motor Control The DC motor is driven directly by the MCU through the eMIOS peripheral, which generates the PWM signal required by the DC Motor 2 Click H-bridge driver. As the potentiometer value increases, the PWM duty cycle also increases, resulting in higher motor speed. When the throttle is at zero, the motor is stopped; above zero, the duty cycle is clamped to a minimum dead-band value (approximately 20 % of the full range) to guarantee reliable motor start-up, and then scales linearly up to full speed. This mirrors the response of a real drivetrain to a throttle input. 4.5 Automatic Gear Selection with Hysteresis The transmission model implements six forward gears plus neutral. Rather than mapping the throttle directly to a gear, the model maintains an internal simulated vehicle speed, which increases when the throttle is applied and decreases when it is released. Gear selection is performed by comparing the vehicle speed against a set of predefined thresholds: An upshift occurs when the simulated speed rises above the upper threshold of the current gear. A downshift occurs when the speed drops below the lower threshold of the current gear. The distance between the up and down thresholds forms a hysteresis band, preventing rapid oscillation between two gears when the speed hovers near a shift point. When the throttle is held at zero for a sustained period, the model detects idle and gradually downshifts back to neutral, mirroring the behaviour of a real automatic gearbox. 4.6 Engine RPM Estimation In parallel with gear selection, the model estimates an engine RPM value based on the throttle input and the currently engaged gear. On each gear change, the RPM is smoothly adjusted — decreasing on upshifts and increasing on downshifts — to reproduce the characteristic behaviour of an automatic transmission. This smoothing avoids abrupt jumps and gives a more realistic feel to the simulation. 4.7 Signal Mapping The application transforms the continuous throttle input into two coordinated actuator commands: a discrete gear position displayed by the servo, and a continuous PWM level applied to the DC motor. The conceptual mapping is shown below. Throttle Input Transmission State Servo Position (Gear Indicator) DC Motor Speed 0 % (idle) Neutral Rest position Stopped Low 1st – 2nd gear Low-gear positions Dead-band minimum → low speed Medium 3rd – 4th gear Mid-range positions Medium speed High 5th – 6th gear High-gear positions Maximum speed This mapping demonstrates how a continuous sensor input can be transformed into both a discrete state (gear) and a continuous actuator command (motor speed). 4.8 Data Flow at a Glance Physical rotation of the potentiometer → analog voltage → ADC sample → throttle percentage → transmission model (vehicle speed, gear, RPM) → I²C command to the external PWM controller (servo position) and eMIOS PWM signal (DC motor speed). All stages are re-evaluated at a fixed update rate to keep the actuators synchronised. This direct chain from the student's hand to the actuators is the main educational value of the demo. 5. Hardware and Software Setup Required Hardware Component Image Purpose FRDM-A-S32K344 FRDM-A-S32K344FRDM-A-S32K344 MCU platform used to run the transmission control application, execute the transmission model, and drive the connected peripherals through ADC, eMIOS PWM, and I²C. FRDM K64 click shield                  mikroBUS expansion adapter that connects Click modules to the FRDM board. Servo Click                          Expansion board carrying an external PWM controller. It receives I²C commands from the MCU and generates the PWM pulses that drive the servo motor. Micro Servo Motor SG 180°                         Actuator used to physically indicate the currently selected gear on a graduated scale. DC Motor 2 Click   Compact add-on board with a PWM-controlled, full-bridge brushed DC motor driver. It receives the eMIOS PWM signal directly from the MCU. DC Motor                       DC MotorDC Motor Simulates the vehicle drivetrain speed, reflecting the throttle input applied by the user. USB-C cable — Provides power and enables programming and debugging. The example application demonstrates how these peripherals are connected to the MCU pins and used to simulate a complete transmission control chain, from throttle input to gear indication and drivetrain speed. Transmission Control Full Setup on FRDM-A-S32K344 Transmission Full SetupTransmission Full Setup The hardware configuration allows simultaneous control of a position actuator (servo motor driven through I²C) and a speed-controlled actuator (DC motor driven through eMIOS PWM). Software Environment S32 Design Studio IDE S32K3 Real-Time Drivers (RTD) Application Code Hub project import Transmission Control Module On FRDM-A-S32K344  6. Implementation Guide Step Action Sub-steps Expected Result 1 Import the Project Open S32 Design Studio Select “Import project from Application Code Hub” Search for transmission control example Use the GitHub link for automatic configuration Select main branch Import project Project appears in workspace 2 Build the Application Compile the project Check for errors Confirm SDK component management Successful build with no errors 3 Connect Hardware Connect the board via USB-C Attach FRDM K64 Click Shield, Servo Click and DC Motor 2 Click Wire the servo motor, DC motor and potentiometer Verify wiring before powering the system Board powers up and is detected by IDE 4 Flash and Run Program the MCU Start execution Application runs continuously 5 Functional Validation Rotate the potentiometer Observe the servo pointer moving between the gear positions Observe the DC motor speed changing proportionally to the throttle Release the potentiometer and observe the transmission gradually downshifting back to neutral Gear indicator and motor speed respond consistently to throttle changes 7. Signal Behavior and Control Logic The following diagram illustrates how the transmission model selects the current gear based on the simulated vehicle speed, applying a hysteresis band to prevent frequent shifting around each threshold.   The transmission continuously compares the simulated vehicle speed against a set of predefined speed thresholds, one per gear. An upshift occurs when the vehicle speed rises above the upper threshold of the current gear (blue lines), while a downshift occurs only when the speed drops below the lower threshold of that gear (red dashed lines). The distance between the two thresholds forms a hysteresis band that prevents rapid oscillation between adjacent gears when the vehicle speed hovers near a shift point. When the throttle is held at zero for a sustained period, the transmission detects idle and gradually downshifts back to neutral, mirroring the behaviour of a real automatic gearbox. 8. Troubleshooting Issue Possible Actions Board Not Detected Verify USB connection Check drivers Restart IDE DC Motor Not Responding Check eMIOS PWM configuration Verify motor driver wiring and external power supply Confirm code execution Servo Not Moving Check I²C wiring (SDA / SCL) and pull-up resistors Verify that the external PWM controller is powered Confirm the servo is connected to the correct channel and powered by 5 V Incorrect Behavior Validate the ADC input range Inspect GPIO configuration for motor direction pins Verify transmission control logic implementation Unstable / Jittery Output Add software filtering on ADC readings Check power supply stability Verify grounding between motor drivers and MCU 9. Extending the Application The application can be enhanced by adding: Closed-Loop Control Integrate feedback sensors to dynamically adjust actuator outputs Compare commanded vs. actual position/speed for corrective action Additional Transmission Modes Extend the current six-gear + neutral model with Park and Reverse modes for a full PRND emulation Map potentiometer regions or dedicated inputs to specific transmission states Safety Functions Implement input plausibility checks on the throttle signal Add fault monitoring and safe-state transitions in case of sensor or actuator failure CAN Communication Transmit gear, RPM, and speed information over CAN or CAN FD networks Integrate with larger automotive powertrain systems Continuous Versus Discrete Control Compare button-based (discrete) and potentiometer-based (continuous) input styles Emulate electronic throttle control, position sensing, or actuator positioning applications 10. Safety Context Transmission control is part of vehicle motion systems, requiring: Reliable signal processing Deterministic control behavior Safety-aware design In production systems: Redundant checks are implemented Fault detection is mandatory Standards such as ISO 26262 apply Automotive transmission control units also implement input plausibility checks and safe-state fallback strategies to prevent unintended gear engagement or actuator runaway. 11. Conclusion This transmission control demonstration illustrates how the S32K344 platform can combine analog sensing, ADC conversion, I²C communication, PWM generation, and actuator control to implement a complete embedded control application. Using a potentiometer as a continuous input source, the system processes the throttle signal through a transmission model with six forward gears plus neutral, hysteresis-based gear selection, and RPM estimation, and translates the result into real-time commands for both a servo motor (gear indicator) and a DC motor (drivetrain speed). The project provides practical insight into the operation of automotive control systems and serves as a foundation for more advanced transmission, actuator, and motion-control applications. Result on FRDM-A-S32K344 Transmission resultTransmission result The course provides a strong foundation for more advanced systems, including closed-loop feedback control, additional transmission modes, CAN communication, and safety-oriented designs typical of automotive transmission control modules. The course serves as a foundation for the Eat-Sleep-Code-Repeat learning initiative, encouraging a hands-on approach where students continuously learn, develop, test, and improve automotive embedded applications using real hardware and practical examples.
View full article
sCheck 集成功能安全文档 设备:NXP S32K388 微控制器 元器件:SAF 软件包 - SW32K3_SAF_1.0.6_HF01_D2603,sCheck 插件(SRAM ECC 测试) 可用资料: S32K3xx 参考手册(S32K3XXRM_Rev12_2025_11_11.pdf / S32K3XXRM 1_fullReferenceManual.pdf,sCheck UserManual、sCheck SRAM ECC 测试源代码。 差距:缺乏端到端的技术规范、设备寄存器映射、依赖关系交互和预期结果。 版本说明:明确指出以下版本存在一些限制 所需信息: 假定明确的功能安全目标和ECC方案 S32K388 中哪些 SRAM 实例/存储体/分区在范围内,哪些不在范围内 逐步流程包括初始化、故障注入方法、验证和恢复。 所需运行条件(时钟、MPU/XRDC 设置、缓存/TCM 状态、从 RAM/Flash 运行) 跨插件的前置条件/后置条件;元器件间初始化序列示例 SAF/sCheck/eMcem/SafetyBase 基于 S32K388 的版本兼容性矩阵 及格/不及格标准、结果代码及其解读方法 使用的中断、NMI 或错误报告路径;用于应用程序级处理的钩子/回调 Re: Safety documentation for sCheck integration 你好, 对于 sCheck 集成,请主要参考 sCheck 用户手册,特别是“软件集成”章节。本章包含集成要求、假设、内存段定义、链接器文件更新、MPU 配置要求以及任何特定于测试的先决条件。 除了 sCheck 用户手册外,请查阅相应的 S32K3 功能安全手册,其中列出了 sCheck (SM2.*.SCHECK) 涵盖的功能安全机制,并解释了它们在整体功能安全概念中的作用。 SAF 文档代码包,软件包还包含针对其他 SAF 元器件(sBoot、mSel、eMCEM、BIST 等)的模块特定集成指南。因此,集成要求分散在 SAF 模块用户手册中,而不是集中在一个独立组网 \(SA\) 功能安全集成文档中。 我们至少建议您查看以下内容: sCheck 用户手册 → 软件集成 查看用户手册 → 条件、限制和副作用 S32K3 功能安全手册 → SAF/sCheck 涵盖的功能安全机制 SAF 集成文档,涵盖链接器、MPU、启动和 API 集成要求 [[ ## completed ##]] 这些文档提供了将 sCheck 集成到功能安全应用程序所需的信息。 顺祝商祺! Peter
View full article
Safety documentation for sCheck integration Device: NXP S32K388 microcontroller Components: SAF Package -  SW32K3_SAF_1.0.6_HF01_D2603, sCheck plugin ( SRAM ECC test) Available artifacts: S32K3xx Reference Manual (S32K3XXRM_Rev12_2025_11_11.pdf / S32K3XXRM 1_fullReferenceManual.pdf, sCheck UserManual, sCheck SRAM ECC test source code. Gap: lack of end-to-end tehnical specification, device register mapping, dependecny interactions and expected outcomes. Release Note : specifies that following release has limitations Information requested: Precise safety goal(s) and ECC scheme assumed Which SRAM instances/banks/partitions are in scope and out of scope on S32K388 Step-by-step flow including initialization, fault injection method, verification, and restoration Required operating conditions (clock, MPU/XRDC settings, caches/TCM state, run-from-RAM/Flash) Cross-plugin preconditions/postconditions; example initialization sequence across components Version compatibility matrix for SAF/sCheck/eMcem/SafetyBase on S32K388 Pass/fail criteria, result codes, and how to interpret them Interrupts, NMI, or error reporting paths used; hooks/callbacks for application-level handling Re: Safety documentation for sCheck integration Hello, For sCheck integration, please refer primarily to the sCheck User Manual, especially the chapter"Software Integration". This chapter contains the integration requirements, assumptions, memory section definitions, linker file updates, MPU configuration requirements, and any test-specific prerequisites. In addition to the sCheck User Manual, please review the corresponding S32K3 Safety Manual, which identifies the safety mechanisms covered by sCheck (SM2.*.SCHECK) and explains their role within the overall safety concept. The SAF documentation package also contains module-specific integration guidance for the other SAF components (sBoot, mSel, eMCEM, BIST, etc.). The integration requirements are therefore distributed across the SAF module User Manuals rather than being collected in a single standalone safety integration document. As a minimum, we recommend reviewing: sCheck User Manual → Software Integration sCheck User Manual → Conditions, Limitations and Side Effects S32K3 Safety Manual → safety mechanisms covered by SAF/sCheck SAF integration documentation for linker, MPU, startup, and API integration requirements These documents provide the information required to integrate sCheck into a safety application. Best regards, Peter
View full article
sCheck統合のためのセーフティドキュメント デバイス:NXP S32K388 マイクロコントローラ コンポーネント:SAFパッケージ - SW32K3_SAF_1.0.6_HF01_D2603、sCheckプラグイン(SRAM ECCテスト) 利用可能なアーティファクト:S32K3xxリファレンスマニュアル (S32K3XXRM_Rev12_2025_11_11.pdf / S32K3XXRM 1_fullReferenceManual.pdf、ユーザーマニュアルを確認し、SRAM ECC テストのソースコードを確認してください。 ギャップ:エンドツーエンドの技術仕様、デバイスレジスタマッピング、依存関係の相互作用、および期待される結果が不足している。 リリースノート:以下のリリースには制限事項があることを明記します 要求された情報: 正確なセーフティ目標とECCスキームの仮定 S32K388において、どのSRAMインスタンス/バンク/パーティションが対象範囲内であり、どのSRAMインスタンス/バンク/パーティションが対象範囲外であるか 初期化、故障注入方法、検証、復元を含むステップバイステップのフロー 必要な動作条件(クロック、MPU/XRDC設定、キャッシュ/TCM状態、RAM/フラッシュからの起動) プラグイン間の前提条件/事後条件。コンポーネント間の初期化シーケンスの例。 S32K388上のSAF/sCheck/eMcem/SafetyBaseのバージョン互換性マトリックス 合否判定基準、結果コード、およびその解釈方法 割り込み、NMI、またはエラー報告経路の使用;アプリケーションレベルのハンドリングのためのフック/コールバック Re: Safety documentation for sCheck integration こんにちは、 sCheck統合については、主にsCheckユーザーマニュアル、特に「ソフトウェア統合」章を参照してください。この章では、統合要件、前提条件、メモリセクションの定義、リンカファイルの更新、MPU構成要件、およびテスト固有の前提条件について説明します。 sCheckユーザーマニュアルに加え、対応するS32K3セーフティマニュアルもご確認ください。そこではsCheck(SM2.*.SCHECK)でカバーされているセーフティ機構が記載され、全体的なセーフティ概念における役割を説明しています。 SAFのドキュメントパッケージには、他のSAFコンポーネント(sBoot、mSel、eMCEM、BISTなど)に関するモジュール固有の統合ガイダンスも含まれています。したがって、統合要件は単一の独立したセーフティ統合文書にまとめられるのではなく、SAFモジュールのユーザーマニュアル全体に分散されています。 最低限、以下の項目を確認することをお勧めします。 sCheck ユーザーマニュアル → ソフトウェア統合 sCheck ユーザーマニュアル → 状態、制限および副作用 S32K3 セーフティマニュアル → SAF/sCheckで扱われる安全機構 リンカー、MPU、スタートアップ、API統合要件に関するSAF統合ドキュメント これらの書類は、sCheckをセーフティアプリケーションに統合するために必要な情報を提供します。 よろしくお願いいたします。 ピーター
View full article
IMX8 ISP 仅在 ROI 上运行 你好。 我们的 IMX8 产品在 ISP 服务方面遇到了一些问题。 我们应该能够让 ISP 仅在 MIPI 提供的图像达到确定的投资回报率时才工作。 事实上,现在我们只能对来自 ISP 的整个图像使用 ISP。 例如,在我们的例子中,我们有一个大小为 1120x1376 的图像,但最后 16 行是嵌入数据,我们无法将其发送到另一个 VC 中。ISP 应该处理图像(1120x1360),而不是处理嵌入的数据(这些数据始终位于图像底部)。 这样做可行吗? 提前致谢! 祝你今天过得愉快。 Federico Rachelli,Datalogic得利捷有限公司 Re: IMX8 ISP operating only on ROI 你好@federico_rachelli 希望你一切都好。 我们没有这方面的例子,但这让我觉得你可以在驾驶员层面做到这一点。 例如,ACQ 模块使用bounds_width和bounds_height参数来了解原始 MIPI 有效载荷尺寸,然后使用top 、 left 、 width和height来提取有效的感兴趣区域 (ROI)。 你可以在 i.MX 8M Plus相机与显示器指南中看到这些信息。 要丢弃 1120x1376 图像框底部的 16 行嵌入数据,您需要设置 .size 属性。传感器ISP驱动程序配置中的属性: .size = { .bounds_width = 1120, .bounds_height = 1376, /* Total MIPI payload including embedded data */ .top = 0, .left = 0, .width = 1120, .height = 1360, /* Effective image height (1376 - 16) */ }, 请参阅第 4.1.2 节。上述文档中驱动程序的传感器尺寸配置。 顺祝商祺! 萨拉斯。
View full article
S32K312 Secureboot Authentication When changing to a different FBL while Secureboot is enabled, the META Data values ​​generated via the HMAC Key change. As the FBL is changed, the HSE needs to recalculate the META Data using the HMAC Key; however, because the HMAC Key is deleted due to the new FBL, recalculating the META Data becomes impossible. Consequently, a reset occurs due to a verification failure at the FBL, making it impossible to launch the application. Is there a way to re-authenticate the changed FBL using the HMAC Key, thereby allowing both the FBL and the application to run normally?  When running the HSE_SRV_ID_SMR_ENTRY_INSTALL service, HseResponse returns 0xA5AA5317. This corresponds to the following definition: #define HSE_SRV_RSP_KEY_EMPTY ((hseSrvResponse_t)0xA5AA5317UL) This indicates that the key is empty. (As I asked previously, I suspect this response appears because that region has been erased.) I have checked the smrEntry values. When I set a breakpoint at the point where SecureBootState is 0, I confirmed that smrEntry was entirely 0. When I set a breakpoint at the return point where Fota_S32k3_SecureBootProcess ends, I confirmed that the values appeared. At the time of return, the SecureBootState value was 1. I would greatly appreciate it if you could guide me on how to inject the key or otherwise resolve this issue. 1) When a breakpoint is set at if(SecureBootState == 0) / Result: smrEntry = 0 2) A breakpoint at return secureBootProcessResult, the last part of the Fota_S32k3_SecureBootProcess function Re: S32K312 Secureboot Authentication All cryptographic keys declared within the NVM and RAM key catalogs, except for the key type HSE_KEY_TYPE_SHE, can be provisioned (i.e. initialized and updated) by the host via a key import service, defined by the structure hseImportKeySrv_t. The SHE keys is provisioned by the host via services hseSheLoadKeySrv_t or hseSheLoadPlainKeySrv_t.The keys can be installed in plain or encrypted text as shown in the above figure, in the demo all keys are installed in plain text. Do you try the reference code about S32K344_Update_NVM_keys_related_test at \S32K3_HSE_DemoExamples\? # Update NVM keys. ## 1. Objective The main purpose of this example is to a import symmetric key and AES GMAC generate keys. ## 2. Procedure The steps followed to achieve this are: 1. Format Key Catalogs. 2. Declare the HMAC key info that will update initial version. 3. Declare a key container. 4. Copy the key info to the key container. 5. Copy the key data in the container. 6. *You can add any other data to the container*. 7. Import in RAM a copy of the AES provision key to sign the container using the HSE. 8. Sign the container and generate GMAC ## 3. Hardware This example requires the following hardware in order to properly execute: - S32K344-EVB or S32K344-CVB. - If using S32K344-CVB, then an external debugger is also required (PEmicro Multilink rev. C). Re: S32K312 Secureboot Authentication Hi @jeongwoo  It seems that the primary issue currently blocking further progress is that we do not know whether the HMAC key is still available. As a first step, could you please confirm whether you have performed the check I suggested previously and what the result was? “To confirm if the key is erased or not, you can use service HSE_SRV_ID_GET_KEY_INFO, structure struct hseGetKeyInfoSrv_t. Using this service, you will get information in hseKeyInfo_t, so you can check the state of key.” Once we have confirmed the state of the key, we can proceed with the next steps. If the key is missing or has been erased, we can try to install it again. Alternatively, you could also attempt to install the key directly using the same procedure that was originally used during provisioning and see whether the operation succeeds. Regards, Lukas Re: S32K312 Secureboot Authentication A key can be imported or update by HSE service HSE_SRV_ID_IMPORT_KEY. Take a look at these tables in HSE Firmware reference manual rev. 2.7: Table 47. Key provisioning usage when importing a key in an empty slot in the NVM key catalog Table 48. Key provisioning usage when updating  a key (non-empty slot) in the NVM Key Catalog This explains when a key can be imported in plain and when authentication and encryption is needed. If a key slot is empty and you have SU rights, a key can be imported in plain without authentication. If a key slot is not empty (you are updating a key) and you have SU rights, authentication is mandatory and encryption is optional. With user rights only, authentication and encryption is always mandatory regardless of fact that a slot is empty or not. S32K344_Update_NVM_keys_related_test example only shows, how to prepare and sign a key container which is needed for authenticated key import. But the key is not imported in this example. Import of a key is shown in S32K344_AES_EncryptDecrypt, for example. Used API for AES key is LoadAesKey in this project. For HMAC, there’s LoadHmacKey API. This can be used for import of HMAC key in plain without authentication or encryption. Re: S32K312 Secureboot Authentication If Crypto driver is used, a key can be imported using API Crypto_43_HSE_KeyElementSet and Crypto_43_HSE_KeySetValid. You can check RTD SW example like this one (or similar, depending or RTD version you have): c:\NXP\SW32K3_S32M27x_RTD_R23-11_7.0.0_QLP02\eclipse\plugins\Crypto_43_HSE_TS_T40D34M70I0R0\examples\S32DS\S32K3XX\Crypto_43_HSE_SymmetricPrimitives_S32K388\ There’s no API to request super user rights in Crypto module. The procedure is described in section “8.5  Request for Super User rights” in HSE firmware reference manual rev. 2.7. You can also follow function Grant_SuperUser_Rights() in file hse_crypto.c which can be found in HSE DemoExamples package: https://www.nxp.com/webapp/Download?colCode=S32K3_HSE_DemoExamples Regards, Lukas Re: S32K312 Secureboot Authentication Hello Lukas I defined and called the HSE_SRV_ID_GET_KEY_INFO API you mentioned in Crypto_hse.c. However, the If statement in GetKeyInfo is not entered, so I am unable to reference the KeyInfo value. If the key is missing or has been erased, you can try installing it again. Alternatively, could you guide me on how to install the key directly using the same procedure used during provisioning and verify if that operation succeeds? I proceeded by importing a new HSE and adding a different FBL in the Life-Cycle In-Field. How can I obtain SU privileges?
View full article
Profinetデモ RT1180をベースにしたPROFINETデバイスを開発したいと考えています。PROFINETスタックライブラリ、インダストリアル Communication Creator(ICC)、ICE、PROFINET評価バイナリがダウンロードされました。 ICC用のICEユーザーガイドはありますが、Profinetスタックガイドのユーザーガイドは見つかりません。Stackライブラリにプロジェクトのデモはありますか?「goal_appl.c」と「goal_config.h」ファイルはどのプロジェクトに配置すればよいですか?ICCによって生成されるデータは何ですか?  PROFINETデバイスプロジェクトの周期データを変更するにはどうすればよいでしょうか? Re: Profinet demo @wlfworld様、 PROFINETのガイダンス文書は以下の通りです: PROFINET-Stack-Library.zip\ProfiNet\Documents ShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.png スタックは特定のツールチェーンやソフトウェアバージョンに依存しているため、ドキュメントで指定された環境およびソフトウェアバージョンに特に注意を払ってください。 VS CodeでPROFINETプロジェクトを構築するためのガイダンスは、VS Code.mp4 CodeでPROFINETプロジェクトを構築するためのビデオチュートリアル(RT1180-EVKのビルディング Image)を参照してください。   よろしくお願いいたします。 シェリー Re: Profinet demo UG10361はVS Codeでイメージを作成する方法のユーザーガイドです。10320はバイナリのフラッシュ用ユーザーガイドです。 Profinetスタックライブラリのユーザーガイドが必要です。例えば、入力データと出力データをどのように設定するか。 Re: Profinet demo こんにちは、 @wlfworld さん。 PROFINETスタックライブラリ専用のユーザーガイドはまだ公開されておらず、現在開発中です。 PROFINET API に着目する場合は、港湾局の Web サイトに掲載されているガイダンスを参照してください。 アプリケーションプログラミングインターフェース - PROFINET - コンフルエンス さらに、ICCはアプリケーション固有の入力および出力データの構成や修正にも利用できます。関連情報はICCヘルプページでご覧いただけます。 ご不明な点がございましたら、お気軽にお問い合わせください。 よろしくお願いいたします。 シェリー Re: Profinet demo UG10361はVS Codeでイメージを作成する方法のユーザーガイドです。UG_10320はバイナリのフラッシュ用ユーザーガイドです。 Profinetスタックライブラリのユーザーガイドが必要です。例えば、Profinetスタックから入力データを設定し、出力データを取得する方法などです。 Re: Profinet demo こんにちは、 @wlfworld さん。 1.EtherCATに元々割り当てられたPHYでPROFINETを実行することができます。EtherCATハードウェアは100 Mbpsの動作のみをサポートしているため、これらのPHY上のPROFINET通信も100 Mbpsに制限されます。この変更をサポートするためにソフトウェアの修正が必要です。 2. RT1186JVJ8CとRT1186KVJ8Cはどちらも購入可能です。ご注文の詳細は、お近くの代理店またはNXPの営業担当者までお問い合わせください。 3. ソフトウェアは、AN15104のガイダンスに従ってポーテーションできます:インダストリアル イーサネットプロトコルのポーティングガイド |NXP Semiconductors よろしくお願いいたします。 シェリー Re: Profinet demo @ShellyZhang情報ありがとうございます。 3. PROFINETがIMXRT1186CVJ8Cに基づくFRDM-IMXRT1186で評価できるなら、IMXRT1186CVJ8CとIMXRT1186JVJ8Cの違いは何でしょうか?IMXRT1186C VJ8Cをベースにしたファームウェアをリリースできますか? Re: Profinet demo 1. 同じハードウェア(PHY)をベースに、異なるファームウェアを使用してEtherCATとPROFINETを選択することは可能ですか?EthercatスレーブまたはPROFINET IO型のIOデバイスを開発したいと考えています。デモでは、PHYとRJ45が異なります。 2. RT1186JVJ8CまたはRT1186KVJ8Cはいつ入手可能になりますか?*JVM または KVM は大きすぎます (14*14)。 3. FRDM-IMXRT1186に基づいてProfinetを評価することは可能ですか? Re: Profinet demo @ShellyZhang情報ありがとうございます! パッチファイル(AN15104.zip)が添付されています。AN15104に記載されていますが、そのファイルが見つかりません。ウェブサイトwww.nxp.comで検索してもファイルを入手できませんでした。ダウンロードリンクを教えてもらえますか? よろしくお願いいたします! Re: Profinet demo https://www.nxp.com/docs/en/application-note-software/AN15104SW.zipからファイルをダウンロードしてください。 Re: Profinet demo こんにちは、 @wlfworld さん。 ShellyZhang_0-1787016615574.pngShellyZhang_0-1787016615574.pngShellyZhang_0-1787016615574.png MIMXRT1186CVJ8Cにはインダストリアルプロトコルライセンスは含まれていません。したがって、インダストリアルプロトコルアプリケーション向けにMIMXRT1186CVJ8Cに基づく商用ファームウェア製品をリリースすることはできません。   よろしくお願いいたします。 シェリー Re: Profinet demo @ShellyZhangご支援ありがとうございます。 パッチを適用した後、AN15104に従って以下の項目を修正しました。 1. .vscode/mcuxpresso-tools.json "boardId": "frdmimxrt1186" "deviceId": "MIMXRT1186xxxxx" 「デバイス」: 「MIMXRT1186」 2. mcux_include.json 「BOARD」: 「frdmimxrt1186」 3. rj.conf 追加: CONFIG_MCUX_COMPONENT_driver.trdc=y 4. #if (defined(CPU_MIMXRT1186CVJ8C_cm33).... FreeRTOSconfig.h で configENABLE_FPU を定義します (ガイドには含まれていません)。変更されていない場合はコンパイルが失敗します。 rt1180_cm33_cm33.bin(422832バイト)が生成され、FRDM-IMXRTt1186にダウンロードされました。J12とJ18を1-2にコネクテッドしてジャンプし、J60を100に設定します。ICEではスキャンできません。 質問: I.何か手術を見落としてしまったのでしょうか? 2. なぜbinのサイズが400Kバイトを超えるのですか?ダウンロードしたPROFINET評価バイナリのサイズは70KB未満です。何が違うのでしょうか? よろしくお願いいたします! Re: Profinet demo こんにちは、 @wlfworld さん。 遅れてごめんなさい。 お客様からご報告いただいた最新の問題に基づくと、スキャンプロセス中にPROFINETデバイスを正常に検出できるようになったようです。これは良い兆候です。 すべての技術的な議論を一か所にまとめ、最新情報を見逃さないために、NXPコミュニティThreadで議論を続けましょう。 NXPコミュニティディスカッション スレッドを追い、残る接続問題の調査を続けます。 よろしくお願いいたします。 シェリー
View full article
Can an eBike motor get wet? Yes! An eBike motor can get wet from rain, mud, and splashing puddles, but it is water-resistant, not waterproof. This means your eBike can handle normal wet weather, but it will suffer severe damage if it gets submerged in deep water or blasted with a pressure washer. Using the Himiway D5 2.0 as a reference, here is everything you need to know about how your motor handles water, its safety limits, and how to maintain it after a wet ride. Real-World Boundaries: What's Safe vs. What's Dangerous The Himiway D5 2.0 is an all-terrain fat-tire eBike built to handle mud, rain, and off-road trails. However, its powerful 750W rear hub motor still operates under key physical limits. What is safe: Riding through steady rain, splashing through shallow puddles, navigating wet off-road trails, and wiping down your frame with a damp cloth or soft brush. What is dangerous: Riding through deep streams or flooded streets where water reaches the center of the wheel hubs, riding in torrential downpours for hours, or using a high-pressure hose. High-pressure water forces moisture past rubber gaskets and into internal electronics. The "Thermal Vacuum" Risk: When you push your Himiway D5 2.0 hard up a steep hill, the hub motor warms up. If you immediately plunge that hot motor into a cold puddle or creek, the air inside contracts rapidly. This sudden cooling creates a vacuum effect that can pull moisture past the seals and directly into the internal circuitry. Understanding Ingress Protection (IP) Ratings Most eBikes use standard IP (Ingress Protection) ratings to define how well their motors and battery systems resist dust and moisture: IP Rating Level of Protection Real-World Application IPX4 Splashes from any angle Light drizzle and small splashes IPX5 Low-pressure water jets Moderate rain and road spray (Standard for Himiway D5 2.0 components) IPX6 Powerful high-pressure jets Heavy downpours and thick mud spray IPX7 Temporary submersion Shallow submersion up to 30 mins (Rarely found on standard eBikes) Note on the Himiway D5 2.0: The D5 2.0's motor, battery, and display screen carry solid IPX5/IPX6-equivalent weather sealing. It is engineered to keep wet trail spray and heavy rain out, provided the seals are not blasted with high pressure. 4 Rules for Wet Weather Maintenance Taking care of your eBike after a wet ride keeps the electronics dry and prevents corrosion over time. Ditch the Pressure Washer: Stick to a bucket of warm water, a gentle soap, a soft brush, and a low-pressure garden hose spray if needed. Dry Key Components Immediately: After riding through rain or mud, use a micro-fiber towel to wipe down the rear motor casing, display, throttle controls, and battery contacts. Never Store It Wet: Park your bike in a warm, dry room or garage so lingering surface humidity can evaporate naturally. If water got near the battery housing, drop the battery out to let the compartment air dry. Don't Power On a Flooded Bike: If you suspect deep water reached the interior of the motor or controller, leave the power off. Allow the bike to dry completely for 24 to 48 hours before turning it back on to avoid short-circuiting the system.
View full article
S32DS 3.4 - .mex file and ConfigTools Pins do not open Hi, I'm using S32 Design Studio 3.4 with the S32K1xx SDK RTM 4.0.1 for the S32K142. I'm facing an issue where the .mex file and ConfigTools (Pins/Clocks/Peripherals) no longer open. What happens: Double-clicking the .mex file does nothing. ConfigTools → Pins also does nothing. Once, the .mex editor opened correctly and I could see the Pins view, chip package, and peripherals, but after clicking OK, it never opened again. This happens even in a new workspace   I have already tried: Creating a new workspace. Importing the project again. Updating the S32 Design Studio Platform Tools package. Selecting S32 Configuration Tools as the editor for .mex. Restarting S32DS. The project builds correctly, but the Configuration Tools editor never opens. Has anyone seen this issue before? Is this caused by an SDK installation problem, corrupted Config Tools, or a workspace issue? Any suggestions would be appreciated. Eclipse IDE Usage and Settings SDKs Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open Hi @VaneB, Thank you for your reply. I installed S32K1xx SDK RTM 4.0.3 in S32 Design Studio 3.4 and created a new Hello project using the 4.0.3 SDK (not an imported project). The project builds correctly, but the .mex file still does not open in the Configuration Tools editor. When I double-click the .mex file, I can select S32 Configuration Tools as the editor, but after clicking OK, nothing happens. I also verified that the Configuration Tools plugins (Pins Tool, Clocks Tool, Peripherals Tool, Framework, etc.) are installed. Could you please advise what else I should check? Is there a known issue with the Configuration Tools editor not opening in S32DS 3.4? Thank you. Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open Hi @Resham_Bhattad  Please note that S32K1xx SDK RTM 4.0.1 is not compatible with S32DS 3.4. For IDE version, the supported SDK versions are S32K1xx SDK RTM 4.0.2 and 4.0.3. Based on the error, it looks like the IDE cannot find the SDK path. This can happen if the SDK is not installed, the project was imported, or the SDK location configured in the project does not match the SDK installed on your machine. BR, VaneB Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open Hi @Resham_Bhattad  If you access any of the ConfigTools tools, are you able to see and select the project you created from the drop-down list? Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open edit .mex file by `Notepad.exe` search keyword " " replace "s32sdk_s32k1xx_rtm_403" with "s32sdk_s32k1xx_rtm_xxx" save open it ! Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open And  .project file  :  s32sdk_s32k1xx_rtm_402/platform/drivers/src/lptmr/doxygen/lptmr_driver.dox 不知道為什麼 別的 .dox檔案 都是 :  s32sdk_s32k1xx_rtm_402/platform/pal/src/adc/doxygen/adc_pal.dox 就是偶爾會冒出幾個 硬要標新立異 用 S32SDK_S32K1XX_RTM_4.0.2   Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open Similar conflicts have occurred many times before. Didn't your company think about resolving the conflict? When installing SDK 4.xx, the installer automatically determines whether it is compatible with the current IDE version! At least display a warning message. Instead of having a bunch of people using the same equipment for so long, only to have problems arise later... You all replied one by one saying that your IDE version is not suitable for installing the ooxx version of the SDK. Some end-users will know in advance which "which" version of the IDE their SDK version is compatible with. You should have prevented this from happening in the first place. Instead of trying to stop everyone from misusing it like this, you then come to criticize it. Those who agree, please click.👍 
View full article
Profinet demo I want to develop a profinet device based on RT1180. The PROFINET stack library, Industrial Communication Creator(ICC), ICE and PROFINET Eval Binaries have been downloaded.  There is a user guide for ICE for ICC, but I can't find a user guide for the Profinet stack guide. Is there a project demo in the stack library? Which project shall I put the file 'goal_appl.c‘ and ’goal_config.h‘ which are gererated by ICC?  How to modify the cyclic data of profinet device project? Re: Profinet demo Dear @wlfworld , The PROFINET guidance documents can be found in: PROFINET-Stack-Library.zip\ProfiNet\Documents ShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.pngShellyZhang_0-1785807755309.png Please pay special attention to the environment and software version requirements specified in the documentation, as the stack depends on specific toolchain and software versions for proper operation. You can refer to the video tutorial (Building Image on RT1180-EVK using VS Code.mp4) for guidance on building the PROFINET project in VS Code.   Best Regards, Shelly Re: Profinet demo The UG10361 is the user guide for how to building image with VS Code. The 10320 is the user guide for flashing binaries. I need the user guide on the profinet stack library. For example, how to set the input data and output data. Re: Profinet demo The UG10361 is the user guide for how to building image with VS Code. The UG_10320 is the user guide for flashing binaries. I need the user guide on the profinet stack library. For example, how to set the input data and get the output data from Profinet stack. Re: Profinet demo Hi @wlfworld , A dedicated user guide for the PROFINET stack library has not been released yet and is currently under development. If your focus is on the PROFINET API, please refer to the guidance available on the Port website: Application Programming Interface - PROFINET - Confluence In addition, ICC can be used to configure and modify application-specific input and output data. Relevant information can be found in the ICC Help pages. Please let us know if you have any further questions. Best Regards, Shelly Re: Profinet demo @ShellyZhang Thanks for you information. 3. If the PROFINET can be evaluated on FRDM-IMXRT1186 which is based on IMXRT1186CVJ8C, what's the different between IMXRT1186CVJ8C and IMXRT1186JVJ8C? Can I release the firmware based on the IMXRT1186CVJ8C?  Re: Profinet demo 1. Is it possible to choose Ethercat and PROFINET by different firmware based on the same hardware(PHY)? I want to develop a IO device which can be Ethercat slave or PROFINET IO. It is different PHY and RJ45 in the Demo. 2. When will the RT1186JVJ8C or RT1186KVJ8C availible? The *JVM or KVM are too big for us(14*14). 3. Is it possible to valuate the Profinet based on the FRDM-IMXRT1186? Re: Profinet demo Hi @wlfworld , 1. You can run PROFINET on the PHYs originally assigned to EtherCAT. Since the EtherCAT hardware only supports 100 Mbps operation, the PROFINET communication on these PHYs will also be limited to 100 Mbps. Software modifications will be required to support this change. 2. Both the RT1186JVJ8C and RT1186KVJ8C are available for purchase. Please contact your local distributor or NXP sales representative for ordering details. 3. The software can be ported by following the guidance provided in  AN15104: Porting Guide for Industrial Ethernet Protocols | NXP Semiconductors Best Regards, Shelly Re: Profinet demo @ShellyZhang Thanks for you information! There is an attached patch(AN15104.zip) mentioned in the AN15104 , but I can't find the file. I also  cann't get the file by searching on website www.nxp.com. Could you provide the downloading link to me? Best Regards! Re: Profinet demo Hi @wlfworld , ShellyZhang_0-1787016615574.pngShellyZhang_0-1787016615574.pngShellyZhang_0-1787016615574.pngShellyZhang_0-1787016615574.png The MIMXRT1186CVJ8C does not include an industrial protocol license. Therefore, you cannot release a commercial firmware product based on the MIMXRT1186CVJ8C for industrial protocol applications.   Best Regards Shelly Re: Profinet demo Please download the file on https://www.nxp.com/docs/en/application-note-software/AN15104SW.zip Re: Profinet demo @ShellyZhang Thanks for your supoort. I applied the patch, and then modified the following items according to AN15104. 1. .vscode/mcuxpresso-tools.json "boardId": "frdmimxrt1186" "deviceId": "MIMXRT1186xxxxx" "device": "MIMXRT1186" 2. mcux_include.json "BOARD": "frdmimxrt1186" 3. rj.conf add: CONFIG_MCUX_COMPONENT_driver.trdc=y 4. #if (defined(CPU_MIMXRT1186CVJ8C_cm33).... to defind configENABLE_FPU in FreeRTOSconfig.h(It is not include in the guide. Compilation will be failed if it is not modified) The rt1180_cm33_cm33.bin(422832 bytes) was generated and downloaded to the FRDM-IMXRTt1186.  Jump J12 and J18 to 1-2 connected and set J60 to 100. It can't be scanned by the ICE.  Question: I. Did I miss some operation?  2. Why the bin is more than 400K bytes? The downloaded PROFINET Eval Binaries is less than 70K. What's the difference? Best regards! Re: Profinet demo Hi @wlfworld , Sorry for the delay. Based on the latest issue you reported, it appears that you are now able to discover the PROFINET device successfully during the scan process, which is a good sign. To keep all technical discussions in one place and avoid missing any updates, let's continue the discussion in the NXP Community thread: NXP Community Discussion We are following the thread and will continue investigating the remaining connection issue there. Best regards, Shelly
View full article
S32K312 安全启动认证 当启用安全启动时,切换到不同的 FBL 时,通过 HMAC 密钥生成的 META 数据值会发生变化。由于 FBL 发生更改,HSE 需要使用 HMAC 密钥重新计算 META 数据;但是,由于新的 FBL 删除了 HMAC 密钥,因此无法重新计算 META 数据。因此,由于 FBL 验证失败,发生 RESET,导致应用程序无法启动。是否可以通过HMAC密钥重新验证已更改的FBL,从而使FBL和应用程序都能正常运行? 运行 HSE_SRV_ID_SMR_ENTRY_INSTALL 服务时,HseResponse 返回 0xA5AA5317。这对应于以下定义: #define HSE_SRV_RSP_KEY_EMPTY ((hseSrvResponse_t)0xA5AA5317UL) 这表示钥匙为空。(正如我之前所问,我怀疑出现此回复是因为该区域已被擦除。) 我已经检查了 smrEntry 值。当我在 SecureBootState 为 0 的位置设置断点时,我确认 smrEntry 完全为 0。当我在 Fota_S32k3_SecureBootProcess 结束的返回点设置断点时,我确认这些值出现了。返回时,SecureBootState 值为 1。 如果您能指导我如何注入密钥或以其他方式解决此问题,我将不胜感激。 1) 当在 if(SecureBootState == 0) 处设置断点时 / 结果:smrEntry = 0 2) 在返回 secureBootProcessResult 处设置断点,这是 Fota_S32k3_SecureBootProcess 函数的最后一部分。 Re: S32K312 Secureboot Authentication 除了 HSE_KEY_TYPE_SHE 密钥类型之外,NVM 和 RAM 密钥目录中声明的所有加密密钥都可以配置(即,由主机通过密钥导入服务初始化和更新,该服务由结构 hseImportKeySrv_t 定义。 SHE 密钥由主机通过 hseSheLoadKeySrv_t 或 hseSheLoadPlainKeySrv_t 服务进行配置。密钥可以以明文或加密文本的形式安装,如上图所示,在演示中,所有密钥均以明文形式安装。 您是否尝试过 \S32K3_HSE_DemoExamples\ 中的 S32K344_Update_NVM_keys_related_test 参考,引用代码? # 更新 NVM 密钥。 1. 目标 本示例的主要目的是导入对称密钥和 AES GMAC 生成密钥。 2. 程序 实现这一目标的具体步骤如下: 1.格式化关键目录。 2.声明将更新初始版本的 HMAC 密钥信息。 3.声明一个密钥容器。 4.将密钥信息复制到密钥容器中。 5.复制容器中的密钥数据。 6. *您可以向容器中添加任何其他数据* 。 7.将 AES 配置密钥副本导入 RAM,以便使用 HSE 对容器进行签名。 8.对容器进行签名并生成 GMAC。 3. 硬件 本示例需要以下硬件才能正确运行: - S32K344-EVB 或 S32K344-CVB。 -如果使用 S32K344-CVB,则还需要外部调试器(PEmicro Multilink rev. C)。 Re: S32K312 Secureboot Authentication 嗨@jeongwoo 目前阻碍进一步进展的主要问题似乎是我们不知道 HMAC 密钥是否仍然可用。 首先,请您确认是否已按照我之前建议的方法进行检查,以及检查结果如何? “要确认密钥是否已被擦除,您可以使用服务 HSE_SRV_ID_GET_KEY_INFO,结构 struct hseGetKeyInfoSrv_t。使用此服务,您将在 hseKeyInfo_t 中获取信息,以便您可以检查密钥的状态。 一旦我们确认了密钥的状态,就可以进行下一步操作了。如果密钥丢失或已被删除,我们可以尝试重新安装。或者,您也可以尝试使用与最初配置过程中相同的步骤直接安装密钥,看看操作是否成功。 此致, Lukas Re: S32K312 Secureboot Authentication 密钥可通过 HSE 服务 HSE_SRV_ID_IMPORT_KEY 导入或更新。 请查看 HSE 固件参考手册修订版中的这些表格。2.7: 表47. 在 NVM 密钥目录中将密钥导入到空槽位时,密钥配置的使用情况 表48。在 NVM 密钥目录中更新密钥(非空槽位)时,密钥配置的使用情况 这解释了何时可以以明文形式导入密钥,以及何时需要进行身份验证和加密。 如果密钥槽为空且您拥有 SU 权限,则可以无需身份验证即可直接导入密钥。如果密钥槽不为空(您正在更新密钥)并且您拥有 SU 权限,则身份验证是强制性的,加密是可选的。 仅使用用户权限时,无论插槽是否为空,身份验证和加密始终是强制性的。 S32K344_Update_NVM_keys_related_test 示例仅展示了如何准备和签署用于身份验证密钥导入的密钥容器。但是,在这个例子中,密钥并没有被导入。 例如,S32K344_AES_EncryptDecrypt 中显示了密钥的导入。本项目中使用的 AES 密钥 API 为 LoadAesKey。对于 HMAC,可以使用 LoadHmacKey API。这可用于以明文形式导入 HMAC 密钥,无需身份验证或加密。 Re: S32K312 Secureboot Authentication 如果使用加密驱动程序,则可以使用 API Crypto_43_HSE_KeyElementSet 和 Crypto_43_HSE_KeySetValid 导入密钥。 您可以查看类似这样的RTD软件示例(或类似的示例,具体取决于您的RTD版本): c:\NXP\SW32K3_S32M27x_RTD_R23-11_7.0.0_QLP02\eclipse\plugins\Crypto_43_HSE_TS_T40D34M70I0R0\examples\S32DS\S32K3XX\Crypto_43_HSE_SymmetricPrimitives_S32K388\ Crypto 模块中没有用于请求超级用户权限的 API。 该程序在 HSE 固件参考手册修订版的“8.5 超级用户权限请求”部分中进行了描述。2.7. 您还可以参考 hse_crypto.c 文件中的 Grant_SuperUser_Rights() 函数。可以在 HSE DemoExamples 包中找到: https://www.nxp.com/webapp/Download?colCode=S32K3_HSE_DemoExamples 此致, Lukas Re: S32K312 Secureboot Authentication 你好,卢卡斯。 我在 Crypto_hse.c 中定义并调用了您提到的 HSE_SRV_ID_GET_KEY_INFO API。 但是,GetKeyInfo 中的 If 语句没有被执行,所以我无法引用 KeyInfo 值。如果密钥丢失或已被删除,您可以尝试重新安装。 或者,您能否指导我如何使用与配置过程中相同的步骤直接安装密钥,并验证该操作是否成功? 我接着导入了一个新的 HSE,并在生命周期现场管理中添加了一个不同的 FBL。如何获得SU权限?
View full article
eバイクのモーターはCAN濡れることはありますか? はい!eバイクのモーターは雨や泥、水たまりで濡れることがありますが、水道ではなく水道耐性があります。 つまり、eバイクは通常の雨天にも耐えられますが、深い水道に浸かったり高圧洗浄機で洗浄したりすると大きな損傷を受けます。 Himiway D5 2.0を参考にして、モーターの水道の扱い方、セーフティ限界、そして濡れた走行後のメンテナンス方法について知っておくべきことをすべてご紹介します。 現実世界の境界線:安全なものと危険なもの Himiway D5 2.0は、泥道、雨天、オフロードコースにも対応できるよう設計された、全地形対応のファットタイヤ電動自転車です。しかし、その強力な750Wリアハブモーターは、依然としていくつかの物理的な限界の中で動作する。 安全な走行方法:降り続く雨の中を走行すること、浅い水たまりをはためきながら走ること、濡れたオフロードを走行すること、そしてフレームを湿らせた布や柔らかいブラシで拭くこと。 危険なこと:深い小川や水没した通りを走り、水道がホイールハブの中心に達すること、豪雨の中を何時間も走ること、または高圧ホースの使用。高圧の水道はゴム製ガスケットを通って湿気を内部の電子機器に送り込みます。 「熱真空」のリスク: Himiway D5 2.0 を急な坂道で強く押すと、ハブモーターが熱くなります。熱くなったモーターをすぐに冷たい水たまりや小川に浸けると、内部の空気が急速に収縮します。この急激な冷却により真空効果が発生し、湿気がシールを越えて内部回路に直接引き込まれます。 侵入保護等級(IP等級)の理解 ほとんどの電動自転車は、モーターとバッテリーシステムが粉塵や湿気にどれだけ耐えられるかを定義するために、標準的なIP(侵入保護)規格を使用しています。 IP評価 保護レベル 実世界でのアプリケーション IPX4 あらゆる角度からの飛沫 小雨と小さな水しぶき IPX5 低圧水道噴射 中程度の雨と路面からの水しぶき(Himiway D5 2.0コンポーネントの標準仕様) IPX6 強力な高圧ジェット 激しい豪雨と濃い泥しぶき IPX7 一時的な水没 最大30分間の浅い水没に耐える(一般的な電動自転車ではめったに見られない機能) Himiway D5 2.0に関する注記:D5 2.0のモーター、バッテリー、およびディスプレイ画面は、IPX5/IPX6相当の優れた防水性能を備えています。シール部分に高圧が加えられない限り、濡れた路面からの水しぶきや激しい雨を防ぐように設計されています。 雨天時のメンテナンスに関する4つのルール 雨天走行後に電動自転車を適切に手入れすることで、電子機器を乾燥した状態に保ち、経年劣化による腐食を防ぐことができます。 高圧洗浄機をやめましょう:温かい水道の入ったバケツ、優しい石鹸、柔らかいブラシ、必要なら低圧のガーデンホーススプレーを使いましょう。 キー部品をすぐに乾燥させる:雨や泥の中を走った後は、マイクロファイバータオルでリアモーターケース、ディスプレイ、スロットルコントロール、バッテリーお問い合わせを拭き取ってください。 濡れた状態で保管しないでください:自転車は暖かく乾燥した部屋やガレージに停め、表面の湿気が自然に蒸発しやすくしましょう。もし水道がバッテリーハウジングの近くに入った場合は、バッテリーを抜いてコンパートメントを自然乾燥させてください。 浸水したバイクの電源を入れないでください:モーターやコントローラの内部に深い水道が達していると疑われる場合は、電源を切ったままにしてください。システムのショートを防ぐため、バイクの電源を入れる前に、24時間から48時間かけて完全に乾燥させてください。
View full article
S32DS 3.4 - .mexファイルとConfigTools Pinsが開かない こんにちは、 私はS32 Design Studio 3.4と、S32K142用にS32K1xx SDK RTM 4.0.1を使っています。 .mexファイルとConfigTools(ピン/クロック/ペリフェラル)が開かなくなる問題に直面しています。 [[ ## completed ##]] 何が起こるのですか: .mexファイルをダブルクリックするファイルは何もしません。 ConfigTools → Pins も何も機能しません。 かつて、.mexエディターは正しく起動し、ピンズビュー、チップパッケージ、ペリフェラルは見えましたが、 OKボタンを押した後は再び開きませんでした。 これは新しいワークスペースでも起こります   私は既に以下のことを試しました: 新しいワークスペースを作成しています。 プロジェクトを再度インポートしています。 S32 Design Studioプラットフォームツールパッケージの更新。 .mex ファイルのエディタとしてS32 設定ツールを選択します。 S32DSを再起動しています。 プロジェクトは正しくビルドされるが、構成ツールエディタが開かない。 この問題に遭遇したことがある方はいらっしゃいますか?これはSDKのインストール問題、設定ツールの破損、あるいはワークスペースの問題が原因でしょうか? 何かご提案があれば、ぜひお聞かせください。 Eclipse IDEの使用と設定 SDK Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open こんにちは、 @VaneB さん。 ご返信よろしくお願いします。 S32K1xx SDK RTM 4.0.3をS32 Design Studio 3.4にインストールし、4.0.3を使って新しいHelloプロジェクトを作成しましたSDK(インポートされたプロジェクトではありません)。 プロジェクトは正しくビルドされますが、.mexファイルは依然として構成ツールエディタで開きません。 .mex をダブルクリックするとファイルとしてS32設定ツールをエディターに選べますが、OKをクリックしても何も起こりません。 また、設定ツールのプラグイン(Pins Tool、Clocks Tool、ペリフェラル Tool、Frameworkなど)がインストールされていることも確認しました。 他に何を確認すればよいかアドバイスいただけますか?S32DS 3.4で設定ツールエディタが開かないという既知の問題はありますか? よろしくお願いします。 Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open こんにちは、 @Resham_Bhattad さん なお、S32K1xx SDK RTM 4.0.1はS32DS 3.4と互換性がないことにご注意ください。IDEバージョンでは、サポートされているSDKバージョンはS32K1xx SDK RTM 4.0.2および4.0.3です。 エラーを見る限り、IDEはSDKパスを見つけられないようです。SDKがインストールされていない、プロジェクトがインポートされた場合、またはプロジェクト内で設定されたSDKの位置があなたのマシンにインストールされているSDKと一致しない場合にCANが起こり得ます。 BR、VaneB Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open こんにちは、 @Resham_Bhattad さん ConfigToolsのツールにアクセスした場合、ドロップダウンリストから作成したプロジェクトを表示・選択できますか? Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open 同様の紛争は過去にも何度も発生している。 御社は紛争解決について考えなかったのですか? SDK 4.xxをインストールする際、インストーラーは現在のIDEバージョンとの互換性を自動的に判断します。 せめて警告メッセージを表示してください。 多くの人が同じ機器を長期間使用し、後になって問題が発生するのではなく… 皆さんから次々と返信があり、お使いのIDEのバージョンはooxxバージョンのSDKをインストールするのに適していないとのことでした。 エンドユーザーの中には、自分のSDKバージョンがどのIDEバージョンと互換性があるかを事前に知っている人もいる。 そもそもこんな事態にならないように防ぐべきだった。 あなたは、皆がこのように悪用するのを止めようとする代わりに、それを批判し始める。 賛同される方は、こちらをクリックしてください。👍  Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open .mexを編集`Notepad.exe`によるファイル 検索キーワード「 」 「s32sdk_s32k1xx_rtm_403」を「s32sdk_s32k1xx_rtm_xxx」に置き換える セーブ 開けて! Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open そして .project ファイル: s32sdk_s32k1xx_rtm_402/プラットフォーム/ドライバ/src/lptmr/doxygen/lptmr_driver.dox 不知道為什麼 別的 .dox檔案都是 :  s32sdk_s32k1xx_rtm_402/platform/pal/src/adc/doxygen/adc_pal.dox 就是カップ爾會冒出幾個硬要標新立異用 S32SDK_S32K1XX_RTM_4.0.2  
View full article
S32DS 3.4 - .mex文件和 ConfigTools Pins 无法打开 您好, 我正在使用S32 Design Studio 3.4和S32K1xx SDK RTM 4.0.1来开发S32K142 。 我遇到的问题是.mex 文件和 ConfigTools(引脚/时钟/外设)无法打开。 会发生什么: 双击 .mex 文件该文件没有任何作用。 配置工具 → 引脚也没有任何作用。 曾经,.mex编辑器已正确打开,我可以看到引脚视图、芯片代码包,软件包和外围设备,但单击“确定”后,它再也没有打开过。 即使在新的工作空间中也会发生这种情况   我已经尝试过了: 创建新工作区。 正在重新导入项目。 正在更新 S32 设计工作室平台代码包,软件包。 选择S32 配置工具作为 .mex 文件的编辑器。 重启S32DS。 项目版本正确,但配置工具编辑器始终无法打开。 有人以前遇到过这个问题吗?这是由 SDK 安装问题、配置工具损坏还是工作区问题引起的? 欢迎提出任何建议。 Eclipse IDE 使用和设置 SDK Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open 嗨@VaneB , 感谢您的回复。 我在 S32 Design Studio 3.4 中安装了 S32K1xx SDK RTM 4.0.3,并使用 4.0.3 创建了一个新的 Hello 项目。SDK(非导入项目)。 项目版本正确,但 .mex 文件有问题。文件仍然无法在配置工具编辑器中打开。 当我双击 .mex 文件时在文件中,我可以选择 S32 配置工具作为编辑器,但是点击确定后,没有任何反应。 我还确认了配置工具插件(引脚工具、时钟工具、外设工具、框架等)已安装。 请问我还需要检查哪些方面?S32DS 3.4 中是否存在配置工具编辑器无法打开的已知问题? 谢谢! Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open 你好@Resham_Bhattad 请注意,S32K1xx SDK RTM 4.0.1 与 S32DS 3.4 不兼容。对于 IDE 版本,支持的 SDK 版本为 S32K1xx SDK RTM 4.0.2 和 4.0.3。 根据错误信息来看,IDE 似乎找不到 SDK 路径。如果 SDK 未安装、项目已导入,或者项目中配置的 SDK 位置与计算机上安装的 SDK 不匹配,则可能会发生这种情况。 BR,VaneB Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open 類似衝突 狀況已經發生過很多次了  貴公司 就沒有想到 要解決衝突 嗎? 安裝 SDK 4.xx 時,安裝程式 自己判斷 是否適合當前IDE版本! 至少 跳個警告提示出來吧  而不是 一堆人 這樣混用好久了,等到出問題了  你們才一個個回復說 你的IDE版本 不適合安裝SDK ooxx版  有幾個 End-user 會事先知道 手上這一版 SDK只適用在哪"幾"版IDE的  應該是 你們事先就避免這樣的事情發生  而不是 在大家都這樣亂用了之後, 你們再來牽拖  認同的按 👍  Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open 你好@Resham_Bhattad 如果您访问任何 ConfigTools 工具,您是否能够从下拉列表中看到并选择您创建的项目? Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open 编辑 .mex由 `Notepad.exe` 生成的文件 搜索关键词“ ” 将“s32sdk_s32k1xx_rtm_403”替换为“s32sdk_s32k1xx_rtm_xxx” 节省 打开它! Re: S32DS 3.4 - .mex file and ConfigTools Pins do not open 以及 .project 文件: s32sdk_s32k1xx_rtm_402/platform/drivers/src / lptmr/doxygen/lptmr_driver.dox 不知道为什么还有其他 .dox 文件都是:  s32sdk_s32k1xx_rtm_402 /platform/pal/src/adc/doxygen/adc_pal.dox 就是偶尔会冒出几个硬要标新立异用S32SDK_S32K1XX_RTM_4.0.2  
View full article
电动自行车电机可以进水吗? 是的!电动自行车电机可能会被雨水、泥浆和溅起的水坑弄湿,但它是防水的,不是完全防水的。 这意味着您的电动自行车可以应对一般的潮湿天气,但如果浸入深水中或被高压水枪冲洗,则会遭受严重损坏。 以Himiway D5 2.0为参考,引用,以下是您需要了解的有关电机如何处理水、其功能安全限制以及如何在湿滑路面行驶后对其进行维护的所有信息。 现实世界的界限:什么是安全的,什么是危险的 Himiway D5 2.0 是一款全地形胖胎电动自行车版本,专为应对泥泞、雨天和越野路段而设计。然而,其强大的 750W 后轮毂电机仍然受到关键物理限制的影响。 安全行为包括:在持续的雨中骑行、溅过浅水坑、行驶在潮湿的越野小径上,以及用湿布或软刷擦拭车架。 危险行为包括:骑车穿过水淹到车轮轮毂中心的深溪流或被洪水淹没的街道;在暴雨中骑行数小时;或使用高压水枪。高压水流会将水分压过橡胶垫圈,渗入内部电子元件。 “热真空”风险:当您用力推着 Himiway D5 2.0 上陡坡时,轮毂电机就会发热。如果你立即将滚烫的发动机浸入冰冷的水坑或小溪中,发动机内部的空气会迅速收缩。这种突然的冷却会产生真空效应,可以将水分吸入密封件之外,直接进入内部电路。 了解防护等级(IP) 大多数电动自行车使用标准的 IP(防护等级)来定义其电机和电池系统防尘防潮的性能: IP防护等级 实际应用 IPX4 任何角度溅起的水花 毛毛细雨和零星小雨 IPX5 低压水射流 中等雨量和路面溅水(Himiway D5 2.0 元器件的标准配置) IPX6 强劲的高压喷射 暴雨倾盆,泥浆飞溅 IPX7 暂时浸没 浅水浸泡时间最长可达 30 分钟(标准电动自行车很少具备此功能) 关于 Himiway D5 2.0 的说明:D5 2.0 的电机、电池和显示屏具有可靠的 IPX5/IPX6 等效防水密封性能。它经过特殊设计,可以防止潮湿的路面溅水和暴雨进入,前提是密封件不受高压冲击。 雨天维护的 4 条规则 雨天骑行后妥善保养电动自行车,可以保持电子元件干燥,防止长期腐蚀。 别用高压清洗机:只需一桶温水、温和的肥皂、软刷,必要时可用低压花园水管喷水即可。 立即擦干关键元器件:在雨中或泥泞中骑行后,使用超细纤维毛巾擦拭后电机外壳、显示屏、油门控制装置和电池触点。 切勿潮湿存放:将自行车停放在温暖干燥的房间或车库中,以便残留的表面湿气能够自然蒸发。如果水溅到电池仓附近,请取出电池,让电池仓风干。 不要启动进水的自行车:如果您怀疑深水已进入电机或控制器内部,请保持电源关闭。为避免系统短路,请让自行车完全干燥 24 至 48 小时后再重新启动。
View full article