Multi Source Translation Content

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Multi Source Translation Content

ディスカッション

ソート順:
Are you having trouble implementing AI/ML into your embedded devices? What can NXP's AI/ML solution, eIQ, do for you? (Japanese blog) Introduction Are you having trouble implementing AI/ML into your embedded devices? (From here on, AI/ML will be abbreviated as AI) Although there are ideas for incorporating AI into your company's products, there are likely to be some challenges, such as: ・Challenge 1: "I can't imagine to what extent AI/ML can be achieved with embedded devices." ・Challenge 2: "I don't know where to start." "I'm concerned about the cost of development tools and learning costs." ・Challenge 3: "I developed the AI components on a PC, but I'm worried about whether I can port it to embedded devices." ・Challenge 4: "I'm interested in the recently popular generative AI, LLM, but I'm not sure if it can be realized on embedded devices." In this article, we will introduce the benefits of NXP's AI solution, eIQ, in addressing these anticipated challenges ! What is eIQ?   Figure 1: eIQ Overview As shown in Figure 1, the eIQ ® ML software development environment is comprised of the software libraries and AI model development environment required to run AI applications on NXP's MCUs (microcontrollers) and MPUs (processors), and is provided free of charge . Issue 1: "I can't imagine how much AI/ML can be achieved with embedded devices."   Figure 2: AI hardware portfolio NXP is a semiconductor vendor with a wide portfolio, ranging from extremely lightweight microcontrollers equipped with the Cortex-M series, a CPU suitable for AI, to processors equipped with the multi-core Cortex-A series, as well as an AI accelerator NPU.   Figure 3: Go point / Application Code Hub   Various AI-related demos for various MCUs/MPUs are available at the links below. By checking the details of these demos, you can get an idea of how much AI processing is possible with each grade of MCU/MPU. ・MCU demo Application Code Hub | NXP Semiconductors ・MPU demo GoPoint for i.MX Applications Processors | NXP Semiconductors Additionally, the following page, modelzoo, has published various models converted for NXP devices along with evaluation data. By checking this page, you can get an idea of how much processing time will be required for each type of processing . modelzoo: GitHub - NXP/eiq-model-zoo: A collection of machine learning models for vision optimized for NXP products   Figure 4: Model Zoo Issue 2: "I don't know where to start" "I'm concerned about the cost of development tools and learning costs"   Figure 5: Model Convert The free eIQ Toolkit allows you to develop AI models using GUI operations from time-series data/image data from sensors you have prepared, without any complicated setup. By combining it with the various sample software mentioned above, you can start developing and evaluating embedded AI without incurring significant learning costs for AI tools. ・Time series model development tool (eIQ Time Series Studio) Figure 6: eIQ Time Series Studio Overview           Figure 7: eIQ TSS training screen Using eIQ Time Series Studio (TSS), you can develop machine learning models that perform anomaly detection, classification, and regression (prediction) using a GUI. End-to-end development functionality reduces the cost of developing time-series AI models for edge devices. Input values from various sensors can be used as training data, making it useful for introducing AI to a variety of devices, as shown below.   Figure 8: eIQ Time Series Studio usage example Click here for "eIQ Time Series Studio (time series model development tool) Overview and Usage " ・Image processing model development tool (eIQ Portal)   Figure 9: eIQ image processing model development function Using the image processing model development function of eIQ Toolkit, you can develop deep learning-based object detection/image classification models using a GUI.It offers a complete set of functions, including an augmentation function that augments the training data by processing images, training with specified hyperparameters, exporting in a state optimized for NXP MCU/MPU, and testing the developed model.   Figure 10: Overview of eIQ Model Water Marking Technology Additionally, the eIQ model watermarking technology function helps protect your models by providing a way to prove whether your image processing models have been illegally copied. For details, please refer to the link below and the eIQ_Toolkit_UG.pdf included in the eIQ Toolkit. eIQ ® Model Watermark Technology | NXP Semiconductors   Issue 3: "I developed the AI components on a PC, but I'm worried about whether I can port it to embedded devices." ・eIQ Portal Model Convert function     Figure 11: eIQ Convert function overview   eIQ not only has a model development function, but also has a function to optimize users' own models for NXP MCUs/MPUs. During conversion, it is possible to specify options such as quantization format and per channel/per tensor, and it is configured so that assets built in a PC or rich SoC- based evaluation environment can be smoothly reused for NXP 's MCUs/MPUs suitable for embedded use in product development. ・Nvidia TAO Tool Extension   Figure 12: Nvidia Tao Toolkit Extension Overview   NXP is the first semiconductor vendor to directly integrate the NVIDIA TAO Toolkit API into its eIQ machine learning development environment, an AI enablement tool, enabling the deployment of NVIDIA pre-trained AI models on NXP edge processing devices. For details, please refer to the article below and the eIQ_Toolkit_UG.pdf included in the eIQ Toolkit. NXP Collaborates with NVIDIA to Accelerate AI Adoption by Making TAO Toolkit Available on NXP Edge Devices | NXP Semiconductors Issue 4: "I'm interested in the recently popular generative AI, LLM, but I'm not sure if it can be realized on embedded devices." ・LLM Solutions/GenAI Flow (Pre-release)   Figure 13: LLM Pipeline NXP is one of the industry's first companies to offer an embedded generative AI/LLM solution called Gen AI Flow. For detailed implementation instructions, please refer to the article " [Getting Started] i.MX 95: LLM_RAG Implementation Hands-on - eIQ Gen AI Flow - ". ------- [Added 4/7/2025] The first revision of eIQ genAI Flow was released in the BSP update for Q1 2025. Please see below for details. GitHub - nxp-appcodehub/dm-eiq-genai-flow-demonstrator: The eIQ GenAI Flow Demonstrator is a Conversational AI Pipeline application designed for NXP i.MX95 devices. ------ This can be achieved by providing an environment incorporating RAG (Figure 14), providing an environment that combines sufficient practicality and security for embedded devices.   Figure 14: RAG Overview   *LLM: Large Language Model *RAG: Retrieval Augmented Generation LLM support enables embedded devices to provide more intuitive, conversational user experiences, from smart home devices that support voice commands to industrial equipment that can be controlled with natural language, to in-vehicle infotainment systems that allow users to command and operate in-vehicle functions through hands-free, two-way conversation. Please also refer to the following white papers: https://www.nxp.jp/webapp/Download?colCode=GEN-AI-RAG-WHITEPAPER   summary NXP's eIQ provides the industry's highest level of functionality required for edge AI development, as shown below, reducing customers' AI implementation and development costs. ・We provide a free environment for developing time-series AI and image processing models using a GUI. - Model conversion function and collaboration with NvidiaTool allow for smooth migration from evaluation environments such as PCs ・By utilizing GenAI Flow , you can respond to the latest trend , generative AI (LLM) . ----- -This article is based on information current as of the time of writing (September 25, 2025). ========================= We are currently unable to respond to comments in the "Comment" section of this post. We apologize for the inconvenience, but when making inquiries, please refer to `` Technical Questions to NXP - How to Contact Us( Japanese Blog) ''. (If you are already an NXP distributor or have a relationship with NXP, you may ask the person in charge directly.) We will introduce the benefits of using NXP's AI/ML solution eIQ to address the challenges of introducing AI/ML to embedded devices. - Plan to release LLM+RAG solution -Developed time series AI and image processing AI models -Convert function allows smooth migration of existing AI/ML assets i.MX RT Processors i.MX Processors introduction MCX SW | Downloads Technology Focus Japanese blog
記事全体を表示
Watch The Freescale Cup EMEA Finals LIVE A Livecast has been set up for you to enjoy The Freescale Cup EMEA Finals on 28-29 April that are hosted at the Politecnico of Torino. Connect on Freescale Cup 2015 live streaming - SeLM - Politecnico di Torino Freescale Cup Content
記事全体を表示
RW610 / RW612 Knowledge Hub The RW61x series is a highly integrated, low-power tri-radio wireless MCU with an integrated MCU and Wi-Fi® 6 + Bluetooth® Low Energy (LE) 5.4 / 802.15.4 radios designed for a broad array of applications, including connected smart home devices, enterprise and industrial automation, smart accessories and smart energy. The RW61x series MCU subsystem includes a 260 MHz Arm® Cortex®-M33 core with Trustzone™-M, 1.2 MB on-chip SRAM and a high-bandwidth Quad SPI interface with an on-the-fly decryption engine for securely accessing off-chip XIP flash. The RW61x series includes a full-featured 1x1 dual-band (2.4 GHz/5 GHz) 20 MHz Wi-Fi 6 (802.11ax) subsystem bringing higher throughput, better network efficiency, lower latency and improved range over previous generation Wi-Fi standards. The Bluetooth LE radio supports 2 Mbit/s high-speed data rate, long range and extended advertising.  The on-chip 802.15.4 radio can support the latest Thread mesh networking protocol. In addition, the RW612 can support Matter over Wi-Fi or Matter over Thread offering a common, interoperable application layer across ecosystems and products. NXP RW61x Block DiagramNXP RW61x Block Diagram Documents RW610 Datasheet: RW610 Datasheet RW612 Datasheet: RW612 Datasheet RW61x User Manual: UM11865: RW61x User Manual RW61x Register Manual: RM00278: RX16x Registers   Certifications FRDM-RW612 Radio Equipment Directive Declaration of Conformity  User Guide Getting Started with FRDM-RW612 Quick Start Guide - FRDM-RW612 UG10185: RW612 Matter-Zigbee Bridge User Guide UG10178: Matter Demo Using NXP Chip Tool App for FRDM-RW612 and FRDM-MCXW71  UG10612: NXP Wi-Fi and Bluetooth Feature Debug for FRDM-RW612 UG10182: NXP 802.15.4 Demo Applications for FRDM-RW612 UG10160: Getting Started with Wireless on FRDM-RW612 Board Running RTOS  UG10171: NXP Wi-Fi and Bluetooth Demo Applications for FRDM-RW61X   RW61x Modules Azurewave: RW612 - AW-CU570 is a highly integrated, low-power tri-radio Wireless RW612 MCU with an integrated MCU and Wi-Fi 6 + Bluetooth Low Energy (LE) 5.2 / 802.15.4 radios designed for a broad array of applications. RW610 - AW-CU598 is a highly integrated, low-power tri-radio Wireless RW610 MCU with an integrated MCU and Wi-Fi 6 + Bluetooth Low Energy (LE) 5.3 radios designed for a broad array of applications U-blox: RW612 - IRIS-W10 Series are small, stand-alone, dual-band Wi-Fi and Bluetooth Low Energy wireless microcontroller unit (MCU) modules. The modules are ideal for users looking to add advanced wireless connectivity to their end products. RW610 - IRIS-W16 Series are small, stand-alone, dual-band Wi-Fi and Bluetooth Low Energy wireless modules, with everything needed for integration into end-products. The modules are ideal for users looking to add advanced wireless connectivity to their end products.  Murata: RW612 - LBES0ZZ2FR-580 Murata’s Type 2FR is a small and very high-performance module based on NXP RW612 combo chipset, supporting IEEE 802.11a/b/g/n/ac/ax + Bluetooth LE 5.4 / IEEE 802.15.4. RW610 - LBES0ZZ2FP-580 Type 2FR/2FP is a family of small and highly integrated multi-radio modules with built-in high-performance MCU with advanced security features for connected smart devices in smart homes, enterprise and industrial automation, smart accessories, and smart energy. It supports the latest Matter smart home connectivity protocol. California Eastern Laboratories (CEL): RW612 - CMP4612 is a fully integrated Dual-Band, Tri-mode (Wi-Fi 6, BT5.4, 802.15.4) radio, that includes a host MCU, Flash, RAM, peripherals, and numerous interfaces (SDIO, UART, USB, Ethernet. SPI, I2C) to support both HOSTLESS (RTOS) and HOSTED (NCP mode) architectures. CEL's solution includes either an on-board antenna or connector.   Evaluation boards  FRDM-RW612 FRDM-RW612 is a compact and scalable development board for rapid prototyping of the RW61x series of Wi-Fi 6 + Bluetooth Low Energy + 802.15.4 tri-radio wireless MCUs. It offers easy access to the MCU’s I/O's and peripherals, integrated open-standard serial interfaces, external flash memory and on-board MCU-Link debugger. FRDM-RW612 Getting Started Getting Started with FRDM-RW612 FRDM-RW612 User Manual: UM12160: FRDM-RW612 Board User Manual Current Measurement configuration: Remove the 0-ohms resistor R103 Solder a couple of pins in JP5. When trying to measure the RW61x current consumption, connect your current meter using the pins in JP5. When using the FRDM board in normal operation, connect a jumper to the pins in JP5.   u-blox   USB-IRIS-W1 The USB-IRIS-W1 development platform is built on the dual-band Wi-Fi 6 and Bluetooth LE module IRIS-W1, based on the NXP RW610/612 chip. The board is designed with a USB interface to simplify evaluation and prototyping directly from a PC. In addition to the IRIS-W1 module with integrated antenna, it also integrates four buttons, an RGB LED, and a USB/UART converter, to further support an easy evaluation. u-blox   EVK-IRIS-W1 The EVK-IRIS-W1 evaluation kit provides stand-alone use of the IRIS-W1 module series featuring the NXP RW610/612 chipset. Azurewave    AW-CU570-EVB Evaluation board for AW-CU570 module includes wireless MCU with Integrated Tri-radio Wi-Fi 6 + Bluetooth Low Energy 5.3 /802.15.4. Murata   2FR EVK Evaluation kit for Murata Type 2FR module (Murata part number LBES0ZZ2FR) includes 3 radios: Wi-Fi, BLE and 802.15.4. It is based on NXP’s RW612 chip. California Eastern Laboratories (CEL) CMP4612-2-EVB The CMP4612 Evaluation Board (CMP4612-2-EVB), based on the NXP RW612 chipset, features dual-band Wi-Fi 6, BLE 5.4 and 802.15.4 radios. The CMP4612 Evaluation Board includes an onboard Ethernet port and PHY hardware as well as an Arduino header, MCULink SWD, and USB ports. This board is designed to facilitate a seamless and efficient evaluation process for customers wanting a certified module for their end product.   Application Notes RM00287: Wi-Fi Driver API for SDK 2.16.100     The radio driver source code provides APIs to send and receive packets over the radio interfaces by communicating with the firmware images. This manual provides the reference documentation for the Wi-Fi driver and Wi-Fi Connection Manager.  UM12133: NXP NCP Application Guide for RW612 with MCU Host - User manual     This user manual describes: • The NXP NCP application for RW612 with MCU host platform i.MX RT1060 as example. • The hardware connections for one of the four supported interfaces to enable NCP mode on the NXP RW612 BGA V4 board (UART, USB, SDIO, or SPI). • The method to build and run the NCP applications on both the NCP host (i.MX RT1060) and the NCP device (RW612). The applications apply to Wi-Fi, Bluetooth Low Energy and OpenThread (OT)    UM12095:  NXP NCP Application Guide for RW612 with MPU Host - User manual      This user manual describes: • The NXP NCP application for RW612 with MPU host platform i.MX 8M Mini as example. • The hardware connections for one of the four supported interfaces to enable NCP mode on the NXP RW612 BGA V4 board (UART, USB, SDIO, or SPI). • The method to build and run the NCP applications on both the NCP host (i.MX 8M Mini) and the NCP device (RW612). The applications apply to Wi-Fi, Bluetooth Low Energy and OpenThread (OT).  AN14439: Migration Guide from FRDM-RW612 Board to Third-Party Module board This Application note provides an overview of what it means to migrate the application to a different board with different flash and pSRAM AN14111: Target Wake Time (TWT) on RW16x This application note describes the target wake time feature and provides examples for RW61X AN13006: Compliance and Certification Considerations This application note provides guidance and tips on how to test products on NXP Wi-Fi devices for regulatory compliance. AN13049: Wi-Fi/Bluetooth/802.15.4 M.2 Key E Pinout Definition This Application note defines M.2 usage for both NXP Wi-Fi/Bluetooth and Tri-Radio M.2 module design AN14489 – Wi-Fi Firmware Automatic Recovery on RW61x Describes Wi-Fi automatic recovery feature as well as how to enable and verify it on RW61x SDK. AN14464 - Low Power Checklist RW61x Family This document provides an overview on how to use the low power consumption features of the RW61x. AN14476 - NXP Dual PAN Feature and Performance Results This document provides a comprehensive exploration of the Dual Personal Area Network (Dual-PAN) feature on NXP Wireless Connectivity products implementing IEEE 802.15.4 low-rate wireless protocol area network standard. Security: AN14544 – EdgeLock 2GO Services for MPU and MCU This application note introduces various methods that the EdgeLock 2GO service can be used with MCU and MPU devices and the features available for each method. AN13813 – Secure Boot on RW61x Describes how to generate and run the secure boot (signed image) on RW61x. AN13814 – Debug Authentication on RW61x Describes the steps for debug authentication using the secure provisioning SDK tool. Import Wrapped Blob using ELS Cryptolib - Uses ELS Cryptolib to import a blob from OTP that was wrapped using HSM_STORE_KEY trust provisioning command.  Import Wrapped Blob using PSA APIs - Uses PSA API to import a blob from OTP that was wrapped using HSM_STORE_KEY trust provisioning command. Community Support If you have questions regarding RW61x series, please leave your comments in our Wireless MCU Community! here    Training FRDM-RW612 Training Wi-Fi 6 Tri-Radio in a secure i.MX RT MCU RW61x Series Training - NXP Community   Equipment Wireless Equipment: This article provides the links to the wireless equipment to help you accelerate your project development Development Tools  SDK builder The MCUXpresso SDK brings open-source drivers, middleware, and reference example application to speed your software development. NXP MCUXpresso MCUXpresso IDE offers advanced editing, compiling and debugging features with the addition of MCU-Specific debugging and supports connections with all general-purpose Arm Cortex-M.  VSCode MCUXpresso for Visual Studio Code (VS Code) provides an optimized embedded developer experience for code editing and development. Zephyr RTOS  The Zephyr OS is based on a small-footprint kernel designed for use on resource-constrained and embedded systems: from simple embedded environmental sensors and LED wearables to sophisticated embedded controllers, smart watches, and IoT wireless applications. NXP Application Code Hub Application Code Hub (ACH) repository enables engineers to easily find microcontroller software examples, code snippets, application software packs and demos developed by our in-house experts. This space provides a quick, easy and consistent way to find microcontroller applications. NXP SPSDK Is a unified, reliable, and easy to use Python SDK library working across the NXP MCU portfolio providing a strong foundation from quick customer prototyping up to production deployment. NXP SEC Tool The MCUXpresso Secure Provisioning Tool us a GUI-based application provided to simplify generation and provisioning of bootable executables on NCP MCU devices. NXP OTAP Tool Is an application that helps the user to perform an over the air firmware update of an NXP development board. SDK Examples for Wireless MCUs The wireless examples feature many common connectivity configurations.   Useful Links Bluetooth Interested in Bluetooth technology? Bluetooth® Low Energy Primer – Essential reading for understanding BLE fundamentals. Bluetooth® Specifications – Full list of standards, protocols, and technical documents. Bluetooth Feature Overview Bluetooth_5.0_Feature_Overview  Bluetooth_5.1_Feature_Overview  Bluetooth_5.2_Feature_Overview Bluetooth_5.3_Feature_Overview Bluetooth_5.4_Feature_Overview Bluetooth_6_Feature_Overview   FRDM-Training Hands-On Training Product: WiFi RW6XX Protocol: 802.15.4 Protocol: BLE -> connectivity Protocol: Bluetooth Protocol: Matter Protocol: Thread Protocol: Wi-Fi Protocol: Zigbee
記事全体を表示
VLM Edge Studio VLM Edge Studio In this post, I want to share a quick walkthrough of VLM Edge Studio, an NXP launcher application designed to interact with supported Vision-Language Models running locally on FRDM i.MX platforms with Ara240 DNPU acceleration. VLM Edge Studio provides a Qt/QML-based GUI for model selection, prompt input, and visual interaction with locally running VLMs at the edge. It communicates with the Ara240 Runtime SDK through the eIQ AAF Connector using a REST-based interface and streaming token responses.   Key Features Local Vision-Language Model inference on supported i.MX platforms Ara240 DNPU acceleration GUI-based model selection and prompt input Streaming token output Integration with eIQ AAF Connector and Ara240 Runtime SDK Support for camera-based visual input using a USB-C HD camera   Supported Model Qwen2.5-VL-7B-Instruct-Ara240 This model is provided as an Ara240-compatible model.dvm file and is intended for local execution on the target platform.   Basic Installation After making sure the Ara240 Runtime SDK is installed on the target board, copy the Debian package: scp vlm-edge-studio.deb root@ : Install it with: dpkg -i vlm-edge-studio.deb The installation may take a few minutes because the model needs to be extracted during setup.   Running VLM Edge Studio Start the application with: run_vlm_edge_studio Before launching, make sure the Ara240 runtime service is running: systemctl status rt-sdk-ara2.service --no-pager -l Once the GUI appears, click LOAD to load the model. After the model is ready, enter a prompt and submit it to interact with the VLM locally on the i.MX platform.   Walkthrough Video In the attached video, I show how to launch VLM Edge Studio, load the supported Vision-Language Model, submit a prompt, and interact with the model running locally with Ara240 DNPU acceleration. (function() { var wrapper = document.getElementById('lia-vid-6396694743112w960h540r549'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (view in My Videos) Summary VLM Edge Studio is a useful tool for evaluating local Vision-Language Model inference on NXP i.MX platforms using Ara240 DNPU acceleration. It provides a simple workflow for loading the model, entering prompts, and interacting with visual-language AI directly at the edge.   Link VLM Edge Studio repository ARA2-M2-16G-GT ARA240 Hands-On Training
記事全体を表示
[不正行為] 投稿者: @RishavKaaraTech / 掲示板: TapLinx-SDK / 報告者: wtgrre wtgrre は、 @RishavKaaraTech が投稿した 「RFIDDiscover ツールを入手したが、その使い方はわからない」という 投稿を以下の理由で報告しました。 理由:裸体または性行為 詳細: 購入ロゲイン・ハミルトン canロゲインを注文します 5mgのコスト ロゲイン60ml ロゲインタブレット配信 ロゲインを次に買う場所 ロゲイン100mg オンライン薬局 ロゲイン最も安い井戸を購入する 母乳育児 ロゲインを購入する ロゲインを購入したい ロゲイン処方薬に関する情報 ロゲインの購入方法 ロゲインの注文方法 購入ロゲイン医薬品の迅速配送 購入ロゲイン ノバスコシア acロゲインの費用 最も安いロゲイン PayPal アメリカン・エキスプレス ロゲインを購入したい 検索ロゲイン処方箋不要 カーマーゼンシャー ロゲインの購入方法 インフラ株価 ロゲイン2 どこで次のロゲインを購入する 薬局ロゲインロイズクーポン2 薬局ロゲインロイズクーポン2 購入ロゲイン医薬品の迅速配送 ロゲイン120 価格 5 最安値のロゲイン、送料無料 購入ロゲイン ノバスコシア コストロゲイン30mg ジェネリックミノキシジル ロゲイン グリーンスボロ ロゲインを次に購入する場所 ロゲインオンライン薬局(処方箋不要) ロゲインタブレット端末の配送 薬局ロゲイン ロイズ クーポン 2 次へロゲインの当日配送 安いロゲイン オンライン ロゲイン錠剤の配送 ロゲインを購入したい ac cost rogaine コストロゲイン30mg otcミノキシジル ロゲイン ソリハルでの費用 投稿リンク: https://community.nxp.com/t5/TapLinx-SDK-TagWriter-and/RFIDDiscover-tool-acquired-but-how-to-use-it/mp/2164324#M205 投稿者: @RishavKaaraTech |作成者に電子メールを送信する 報告者: wtgrre |メールによる報告 報告された投稿には3件の返信があります。
記事全体を表示
S32K311 中的 JTAG 网络安全关于网络安全级别和大规模擦除 你好、 我想知道锁定和解锁过程的步骤。 能否在 S32K311 微控制器中实现大规模擦除和解锁机制? Re: JTAG security in S32K311 about Security levels and Mass erase 你好@truptikavadi1、 谢谢您的帖子。 不,S32K1xx的工作原理与您描述的完全相同,但S32K3xx 并非如此。 如果您想获得与 S32K3xx 网络安全相关的更多信息,请注意,由于这是 K32L 频道,该产品不在我的支持范围内。 我建议在S32K - 恩智浦社区上创建一个新的帖子,那里的相关支持者将能为您提供进一步的帮助。 感谢您的理解。 BR 西莱斯特   ---------------------------------------------------------------------------------------------------------------------- 注:如果本帖回答了您的问题,请点击"ACCEPT AS SOLUTION" 按钮。Thank you! ----------------------------------------------------------------------------------------------------------------------
記事全体を表示
SPIサンプルコード こんにちは。私は「Spi_Transfer_S32K312」というプロジェクトでNXP が提供する spi サンプル コードを勉強しています。コード内の各関数の意味を知りたいのですが、ヘッダーファイルの場所を知ることはCANですか? Re: spi example code こんにちは@mingimin ヘッダー ファイルは、プロジェクト ディレクトリ内の RTD → include の下にあります。 さらに、S32K3/S32M27x SPI ドライバ統合マニュアルと RTD に付属のユーザー マニュアルを確認することをお勧めします。これらのドキュメントには、ドライバの制限、ハードウェアとソフトウェアの要件、使用ガイドライン、構成手順など、ドライバに関する詳細情報が記載されています。これらは、ドライバの行動や能力をより深く理解するのに役立ちます。 これらのリソースは、たとえば次のパスにあります: C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32K3\RTD\Spi_TS_T40D34M50I0R0\doc 正確なパスは、S32DS のバージョンとインストール ディレクトリによって異なる場合があることに注意してください。 BR、ヴェインB
記事全体を表示
S32K314 の ADC セルフテスト (スクエアチェック) サポート こんにちは、 UM Square Checkのドキュメントには、ADCセルフテスト機構について記載されています。しかし、「セーフティ機構」を確認すると、ADCセルフテストは「NONE(なし)」と表示されており、S32K314パッケージのSquare Check (SCheck)設定にもこのオプションは見つかりません。 この機能をCANで有効にする方法や設定方法を教えてください。 優先度: 高 SAFETY_SW Re: ADC Self-Test (Square Check) Support for S32K314 こんにちは、チームの皆さん アップデートはありますか? よろしくお願いします。 Re: ADC Self-Test (Square Check) Support for S32K314 こんにちは、チームの皆さん アップデートはありますか? よろしくお願いします。 Re: ADC Self-Test (Square Check) Support for S32K314 こんにちは@JasonTsengSG 、 私の理解では、これらはより高いパフォーマンスとトラクションインバーターおよびモーター制御 (eTPU) の追加サポートを備えた新しい K3 派生製品です。 S32K3E_SW_アーキテクチャ.docx RMとSMはイントラネットで見つけることができます。ここでは(K3Eの代わりに、このK3サブグループを指すために特定のK396派生名を使用することもできます): Zebra - ドキュメント - S32K396 - すべてのドキュメント オートモーティブ セーフティ ソフトウェア - リリース_1.0.6 - すべてのドキュメント 敬具、 ラドスラフ Re: ADC Self-Test (Square Check) Support for S32K314 こんにちは、ラドスラフさん。 S32K3E と S32Kxx の違いは何ですか? どちらも S32K396、S32K394、S32K376、S32K374、S32K366、S32K364 のグループだそうです。 S32K3E 固有の RM および HW セーフティマニュアルはどこにあるか教えていただけますか? よろしくお願いします。 Re: ADC Self-Test (Square Check) Support for S32K314 わかりやすい説明をありがとう、ラドスラフ。
記事全体を表示
how to change mode to 8g on MMA8451Q? Hello, i´m using accelerometer MMA8451Q on LFSTBEB3110 sensor kit. after testing i want to change the mode to 4g oder better 8g but i don´t know how. i read that i have to use code warrior and change something in the registers but i have neither the knowledge nor the devices for connecting and programming the kit. so my question is, do some options exist like switch a jumper or change settings in the toolbox? thank you for helping stefan Re: how to change mode to 8g on MMA8451Q? hey Jose, thank you for your help. so I will test the other evaluation kit you recommend. ciao Re: how to change mode to 8g on MMA8451Q? Hi Stefan, Unfortunately no, the designers of the SW GUI for this kit didn’t added the function to change g range or the registers values, and it is not possible to do this change via Hardware, so, the only way to change it from 2g to 4g or 8g would be programming the board externally via Code Warrior. If you do not have access to Code Warrior, and you need to check the full functionality of the Accelerometer MMA845x Family, then I would recommend you to get the LFSTBEB845X Evaluation kit compatible with Sensor Toolbox GUI: https://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=LFSTBEB845X In the following User Guide, you can find all the windows and features available for this kit: http://cache.freescale.com/files/sensors/doc/user_guide/MMA845xQSTUG.pdf Regards, Jose Re: how to change mode to 8g on MMA8451Q? Hello, Thank you for your post, however please consider moving it to the right community place (e.g. Sensors) to get it visible for active members. For details please see general advice Where to post a Discussion? Thank you for using Freescale Community.
記事全体を表示
[不正使用] 記事作成者: @jeremyzhou / ナレッジベース: imxrt@tkb / 報告者: eikewp eikewp は、 @jeremyzhou が投稿した記事 「マイクロコントローラ使用の認識モデル」を 以下の理由で報告しました。 理由:ヌードまたは性行為 詳細: CANゼニカルを注文します 安いゼニカル 土曜日配送 インターネット ジェネリックゼニカル 購入安いゼニカル60mg ロイズ薬局のゼニカル インドにおけるゼニカルの価格 次のゼニカルをどこで注文できるか ゼニカルの割引 ゼニカルを購入したい 一般ゼニカル錠 CANゼニカルを注文します 注文ゼニカル 安いゼニカル錠 ゼニカルはどこで買える? ゼニカルアメックスの迅速な配達 ゼニカルの割引 ゼニカルイギリスでオンライン購入 ゼニカルを購入したい ジェネリックゼニカル ゼニカルを注文する ゼニカルを注文したい ゼニカルイギリスでオンライン購入 できるゼニカルを購入しました ゼニカルを次に注文する場所 ゼニカルの購入方法 ゼニカル肥満 スクリプトなし バジルドン 一般ゼニカル錠 一般ゼニカル薬の割引 ゼニカルヴァイタイジェネリック フィナステリド ゼニカルのオンライン購入情報 ジェネリックゼニカル薬の割引 購入安いゼニカル60mg ゼニカルブランド 安い kchge ジェネリックゼニカル錠 安いゼニカル 英国 オンライン ゼニカルブランド 安い kchge 欲しいゼニカルを注文する ジェネリックゼニカル錠 ゼニカル オンライン購入 5bdvi ロイズ薬局のゼニカル 記事リンク: https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/Recognition-model-for-microcontroller-use/ta-p/1103364 記事の著者: @jeremyzhou |メールアドレス 報告者: eikewp |メールレポーター 報告された記事には 8 件のコメントがあります。
記事全体を表示
KW47 知识中心 KW47 系列具备 96 MHz Arm® Cortex®-M33 内核,并搭载蓝牙低功耗(LE)子系统。独立的无线子系统具有专用核心和存储器,可减轻主CPU的负载,将其留给主要应用,并允许固件更新以支持未来的无线标准。KW47 还通过集成的 EdgeLock® 安全飞地核心配置文件提供高级安全性,并将由 NXP 的 EdgeLock 2GO 云服务支持凭证共享。 KW47 系列具备蓝牙信道探测功能,以及专用的片上定位计算引擎,可降低测距延迟。它集成了额外的内存,可支持特定应用代码、连接协议栈和无线固件更新。这意味着无线电子系统的实时活动在能够与应用程序不同的核心上运行,实现可靠的无线性能。 基于 NXP 在汽车解决方案领域的深厚历史,KW47 系列提供从 -40 °C 到 125 °C 的宽操作温度范围以及用于汽车应用的外围设备。KW47 将成为 NXP 15 年产品寿命计划的一部分,以支持长期使用。 KW47 系列配备 MCUXpresso Developer Experience 支持,可优化、简化和加速嵌入式系统的开发工作。 KW47 处于试生产阶段,开发人员可以立即开始使用与其引脚和软件兼容的 KW45。       早期访问计划 立即加入KW47早期访问计划:KW47 Early Access 您可以通过联系 NXP 销售团队来申请访问权限。   信道探测 信道探测简介 演示文稿 CCC CS 功率估算工具可用(附有 Excel 文件)   蓝牙规范 蓝牙 5.0 功能概述 蓝牙 5.1 功能概述 蓝牙 5.2 功能概述 Bluetooth_5.3_功能概述 Bluetooth_5.4_功能概述 Bluetooth_6_Feature_Overview   培训 蓝牙低能耗 6.0 NXP 简介 射频开关比较 吸收型/反射型 ETSI / FCC / ARIB 标准比较与要求 BLE 信道探测  - 概述 BLE 信道探测 - RF 硬件 BLE 信道探测 - ANSYS 建模工具 BLE 信道探测 - 天线原型验证测量 设备 无线设备: 本文提供了有助于项目开发的设备链接  有用链接 参考设计 - NXP 社区 使用 KW45/KW47/MCXW71/MCXW72 的信号频率分析仪 (SFA) 模块进行时钟测量 - NXP 社区:该社区提供了如何使用信号频率分析仪的步骤 [MCUXSDK] 如何使用 GitHub SDK 适用于 KW4x、MCXW7x、MCXW2x - NXP 社区此社区帖子逐步介绍了如何使用 GitHub SDK [MCUXSDK] GitHub SDK - 蓝牙 LE 平台文档 - NXP 社区此社区帖子提供了 BLE 平台的文档。  首次正确构建 PCB 的最佳方法,使用 KW47(汽车)或 MCXW712(IIoT)…… 社区:在此社区中,提供了使用 KW45 或 K32W148 和 MCXW71 构建 PCB 的重要链接,以及所有关于无线性能、低功耗和无线认证(CE/FCC/ICC)的内容。 如何在 Kinetis 系列产品上使用 HCI_bb 并进入 DTM 模式:本文分为两部分: 如何将HCI_bb二进制文件烧录到Kinetis产品中。 使用 R&S CMW270 进行射频测量 BLE HCI 应用程序用于设置发射机/接收机测试命令:本文提供了步骤,展示用户如何向设备发送串行命令 。Bluetooth LE HCI Black Box Quick Start Guide:本文介绍了一个简单的过程,用户可以通过串行命令控制无线电。 Kinetis (K32/38/KW45 & K32W1/MCXW71)功率配置工具: 此页面专门介绍 Kinetis (KW35/KW38/KW45) 和 MCX W7x (MCX W71) 功率配置工具。它将帮助您估算您的应用程序(汽车或物联网)的功耗,并评估您解决方案的电池寿命。  
記事全体を表示
i.MX8MP 添加 HD3SS3220 Type-C 导致 LAN 唤醒失败 我正在开发 6.12.34 内核并修改内核设备树 imx8mp-evk.dts。 nxp-imx/imx-Manifest:i.MX 版本清单 (imx-linux-wal nascar) 当按如下方式在设备树中添加 hd3s3220 type-c 控制器时,WOL 失败了。 /{ connector { compatible = "usb-c-connector"; label = "USB-C"; data-role = "dual"; status = "disabled"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; hs_ep: endpoint { remote-endpoint = <&usb3_hs_ep>; }; }; port@1 { reg = <1>; ss_ep: endpoint { remote-endpoint = <&hd3ss3220_in_ep>; }; }; }; }; }; &iomux { pinctrl_hd3ss3220: hd3ss3220grp { fsl,pins = < MX8MP_IOMUXC_ECSPI2_MISO__GPIO5_IO12 0x140 >; }; }; &i2c2 { clock-frequency = <400000>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_i2c2>; status = "okay"; hd3ss3220@67 { compatible = "ti,hd3ss3220"; reg = <0x67>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_hd3ss3220>; interrupt-parent = <&gpio5>; interrupts = <12 IRQ_TYPE_LEVEL_LOW>; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; hd3ss3220_in_ep: endpoint { remote-endpoint = <&ss_ep>; }; }; port@1 { reg = <1>; hd3ss3220_out_ep: endpoint { remote-endpoint = <&usb3_role_switch>; }; }; }; }; }; &usb_dwc3_1 { dr_mode = "otg"; hnp-disable; srp-disable; adp-disable; usb-role-switch; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; usb3_hs_ep: endpoint { remote-endpoint = <&hs_ep>; }; }; port@1 { reg = <1>; usb3_role_switch: endpoint { remote-endpoint = <&hd3ss3220_out_ep>; }; }; }; }; 调用挂起命令后,WOL 功能失败。 根据我的检查,唤醒功能是受支持的 root@imx8mpevk:~# ethtool -s eth0 wol g root@imx8mpevk:~# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Full 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Full 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on master-slave cfg: preferred slave master-slave status: slave Port: Twisted Pair PHYAD: 1 Transceiver: external MDI-X: Unknown Supports Wake-on: ug Wake-on: g Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes root@imx8mpevk:~# dmesg | grep -i wake [ 3.148381] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported [ 13.933830] stmmac: wakeup enable root@imx8mpevk:~# cat /sys/class/net/eth0/device/power/wakeup enabled 但是 6.6.52 内核(imx-linux- scarthgap)上同样的设备树设置效果很好!! 谁能帮帮我? i.MX 8 系列 | i.MX 8QuadMax (8QM) | 8QuadPlus Linux Re: i.MX8MP adding HD3SS3220 Type-C cause Wake on LAN failed 你好, 请尝试在 dts 中使用IRQ_TYPE_EDGE_FALLING。 致敬, Zhiming Re: i.MX8MP adding HD3SS3220 Type-C cause Wake on LAN failed 虽然将中断信号改为"IRQ_TYPE_EDGE_FALLING" ,但唤醒功能仍然不起作用。 目前,通过以下设置,唤醒功能运行良好。 / { connector { compatible = "usb-c-connector"; label = "USB-C"; data-role = "dual"; status = "disabled"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; hs_ep: endpoint { remote-endpoint = <&usb3_hs_ep>; }; }; port@1 { reg = <1>; ss_ep: endpoint { remote-endpoint = <&hd3ss3220_in_ep>; }; }; }; }; }; &i2c2 { clock-frequency = <400000>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_i2c2>; status = "okay"; hd3ss3220@67 { compatible = "ti,hd3ss3220"; reg = <0x67>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_hd3ss3220>; interrupt-parent = <&gpio5>; interrupts = <12 IRQ_TYPE_LEVEL_LOW>; wakeup-source; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; hd3ss3220_in_ep: endpoint { remote-endpoint = <&ss_ep>; }; }; port@1 { reg = <1>; hd3ss3220_out_ep: endpoint { remote-endpoint = <&usb3_role_switch>; }; }; }; }; }; &iomux { pinctrl_hd3ss3220: hd3ss3220grp { fsl,pins = < MX8MP_IOMUXC_ECSPI2_MISO__GPIO5_IO12 0x140 // USB_SW_INTn (AH20) >; }; }; &usb3_phy1 { fsl,phy-tx-preemp-amp-tune-microamp = <1800>; fsl,phy-tx-vref-tune-percent = <116>; status = "okay"; }; &usb3_1 { status = "okay"; }; &usb_dwc3_1 { dr_mode = "otg"; hnp-disable; srp-disable; adp-disable; usb-role-switch; role-switch-default-mode = "host"; snps,dis-u1-entry-quirk; snps,dis-u2-entry-quirk; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; usb3_hs_ep: endpoint { remote-endpoint = <&hs_ep>; }; }; port@1 { reg = <1>; usb3_role_switch: endpoint { remote-endpoint = <&hd3ss3220_out_ep>; }; }; }; }; 但如你所见,连接器的状态被设置为"disabled" ,这是为什么呢? 删除这一行后,唤醒功能就失效了。 Re: i.MX8MP adding HD3SS3220 Type-C cause Wake on LAN failed 嗨 @AlanWen 我个人认为,这个问题可能与内核通用元器件的升级有关,不应归因于 i.MX 相关的驱动程序。由于我没有相同的硬件平台,所以无法准确找出问题所在。 致敬, Zhiming Re: i.MX8MP adding HD3SS3220 Type-C cause Wake on LAN failed 但在 6.6.52 内核版本中,使用相同的设置,在没有连接器状态行的情况下,唤醒功能也能正常工作。 如下所示: / { connector { compatible = "usb-c-connector"; label = "USB-C"; data-role = "dual"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; hs_ep: endpoint { remote-endpoint = <&usb3_hs_ep>; }; }; port@1 { reg = <1>; ss_ep: endpoint { remote-endpoint = <&hd3ss3220_in_ep>; }; }; }; }; }; &i2c2 { clock-frequency = <400000>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_i2c2>; status = "okay"; hd3ss3220@67 { compatible = "ti,hd3ss3220"; reg = <0x67>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_hd3ss3220>; interrupt-parent = <&gpio5>; interrupts = <12 IRQ_TYPE_LEVEL_LOW>; wakeup-source; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; hd3ss3220_in_ep: endpoint { remote-endpoint = <&ss_ep>; }; }; port@1 { reg = <1>; hd3ss3220_out_ep: endpoint { remote-endpoint = <&usb3_role_switch>; }; }; }; }; }; &iomux { pinctrl_hd3ss3220: hd3ss3220grp { fsl,pins = < MX8MP_IOMUXC_ECSPI2_MISO__GPIO5_IO12 0x140 // USB_SW_INTn (AH20) >; }; }; &usb3_phy1 { fsl,phy-tx-preemp-amp-tune-microamp = <1800>; fsl,phy-tx-vref-tune-percent = <116>; status = "okay"; }; &usb3_1 { status = "okay"; }; &usb_dwc3_1 { dr_mode = "otg"; hnp-disable; srp-disable; adp-disable; usb-role-switch; role-switch-default-mode = "host"; snps,dis-u1-entry-quirk; snps,dis-u2-entry-quirk; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; usb3_hs_ep: endpoint { remote-endpoint = <&hs_ep>; }; }; port@1 { reg = <1>; usb3_role_switch: endpoint { remote-endpoint = <&hd3ss3220_out_ep>; }; }; }; };
記事全体を表示
CSEc エラー S32K144 で CSEc を使用する場合、BOOT_DEFINE 中に KEY_INVAILD エラーが返されるのはいつですか? 答えが得られることを祈り、毎日幸せになることを祈っています! Re: CSEc Error こんにちは@xiaozhi BOOT_DEFINE 関数を呼び出すときにこのようなエラーが発生する理由がCANわかりません。この関数は、BOOT_MAC_KEY がまだプロビジョニングされていない場合でも呼び出すことができるため、キーは必要ありません。 よろしくお願いいたします。 ルーカス
記事全体を表示
[SAF85xx] GMAC生成ツール/例 お客様は、HSE_FW の結果と比較して、IVT_AUTH 構成として GMAC 値を計算しました。現在、お客様は HSE_FW で同じ結果を得ることができませんでした。GMAC 計算のツールや例を示していただくことは可能でしょうか? たとえば、お客様は添付の IVT データを計算し、HSE_FW から GMAC 値を取得できます。 HSE_FW Re: [SAF85xx] GMAC Generation Tool/Example こんにちは、Himanshuさん。ご協力ありがとうございます。 1. HSE_FW 1.2.39.0 2. お客様に問い合わせる必要があります。 3. お客様はNIST特別出版物800-38Dを参照しています タイトル: ブロック暗号動作モードに関する推奨事項: ガロア/カウンタモード (GCM) と GMAC URL: https://csrc.nist.gov/publications/detail/sp/800-38d/final rm649929-HSE-H&Mファームウェアリファレンスマニュアル(2.9).pdfの8.3ホストシステムイメージの認証 4. お客様に問い合わせる必要があります。 Re: [SAF85xx] GMAC Generation Tool/Example こんにちは@hiroshiHirashimaさん 取り組んでいます。さらに分析するために、以下の情報を提供していただけますか? 1. HSE FWバージョン 2. GMACを計算したツールは何か 3. IVT上のGMACを計算するためにどのような方法を使用しているか 4. HSE 出力 MAC と比較する GMAC のもう 1 つの値は何ですか? よろしく ヒマンシュ・クマール Re: [SAF85xx] GMAC Generation Tool/Example こんにちは@hiroshiHirashimaさん 質問2と質問4の回答を教えていただけますか? よろしくお願いいたします。 ヒマンシュ・クマール Re: [SAF85xx] GMAC Generation Tool/Example 2. と 4. の質問に関しては、お客様が Python スクリプトを共有しました。スクリプトを確認して、問題や提案が見つかった場合はお知らせください。 Re: [SAF85xx] GMAC Generation Tool/Example こんにちは@hiroshiHirashimaさん お客様名を教えていただけますか? よろしくお願いいたします ヒマンシュ・クマール Re: [SAF85xx] GMAC Generation Tool/Example デンソー株式会社および DTS Insight 社 Re: [SAF85xx] GMAC Generation Tool/Example あなたが生み出した価値を両方とも私と共有してもらえますか? Re: [SAF85xx] GMAC Generation Tool/Example 添付スクリプトとして SHA-256 および AES-256 を使用してスクリプトを変更しようとしました。しかし、それでも HSE_FW の計算結果と同じ結果を得ることはできません。 Re: [SAF85xx] GMAC Generation Tool/Example 添付のスクリプト、データ、および HSE_FW と Python スクリプトからの GMAC 値をご覧ください。 Excel ファイルでは、HSE_FW による GMAC 値が左側に表示され、テスト スクリプトの結果が右側に表示されます。 Re: [SAF85xx] GMAC Generation Tool/Example こんにちは@hiroshiHirashimaさん いくつか情報を教えていただけますか? どの soc Cut お客様が使用していますか? お客様は、このサービスHSE_SRV_ID_BOOT_DATA_IMAGE_SIGN を使用して IVT の GMAC タグを生成した後、この HSe サービス HSE_SRV_ID_BOOT_DATA_IMAGE_VERIFY を使用して IVT を検証しましたか? Re: [SAF85xx] GMAC Generation Tool/Example 1. 2.1 2. IVTはHSE_SRV_ID_BOOT_DATA_IMAGE_SIGNを使用して検証されませんでした Re: [SAF85xx] GMAC Generation Tool/Example こんにちは@hiroshiHirashimaさん ご指摘のとおり、この GMAC も HSE による検証を受けていないため、HSE 側からの検証を受ける必要があります。HSE がそれを検証できない場合は、タグ自体に問題がある可能性があります。Python スクリプトは正しく機能しているため、生成されたタグを HSE が検証できないことは、タグが破損しているか、正しく生成されていない可能性があることを示しています。したがって、最初のステップは、HSE 側からタグを生成して検証することです。 よろしくお願いいたします ヒマンシュ・クマール Re: [SAF85xx] GMAC Generation Tool/Example こんにちは@hiroshiHirashimaさん 共有されたタグとデータを確認しましたが、HSE 側で検証されていません。自分の側でタグを生成すると、タグは正常に作成され、問題なく検証されます。 お客様にHSEから直接タグを生成して検証していただくようご依頼いただけますでしょうか? お客様が使用しているタグが破損している可能性があります。 よろしくお願いいたします。 ヒマンシュ・クマール Re: [SAF85xx] GMAC Generation Tool/Example ご評価とご提案ありがとうございます。お客様側で確認していただくようお願いいたします。お客様からのフィードバックを受けて、さらに詳しい情報が公開され、共有されます。
記事全体を表示
S32K358 基于 AUTOSAR 驱动程序的 HSE 随机数生成器 亲爱的支持者 客户 Aptiv 与 S32K358 合作 RTD 版本:Crypto_43_HSE_TS_T40D34M60I0R0 HSE FW 版本:HSE_FW_S32K358_9_2_72_0 在尝试在微控制器上集成加密RTD并刷新HSE固件后生成随机数时,我们观察到一个问题,即固件似乎停留在HSE_IP_ServiceRequest () 函数上,特别是在等待 mu_IP_isResponseReady () 时。请查看随附的调用堆栈屏幕截图以参考。 请您帮助我们理解: 固件卡在这一点上的可能原因是什么? 解决此问题的建议方案或调试步骤? PS: 我已在 BSWM 配置中配置了 CSM_Init、CriIf_Init 和 Crypto_Init 在 Vector Davinci 中配置的 CSM、CryIf,从 BSWM_Init 调用中调用的 CSM、CryIF、Crypto 的初始函数。使用 Demo APP 安装了 HSE,并通过读取版本号和 MU 状态寄存器进行了验证,如下图所示: 客户要求提供基于 AUTOSAR xdm 配置 CSM、CriIf 和 Crypto 驱动程序的 AUTOSAR 示例(而不是 DEMOAPP 的代码)。附上他们的 Crypto xdm 文件。 (到目前为止,恩智浦方面的 Sunny X 和 Dhan Raj 参与了一次调试呼叫,但我们尚未找到最终的根本原因......)。 顺祝商祺! 维克托 板:S32K358 优先权:紧急 SW 变体:标准 Re: S32K358 HSE Random Number Generation based on AUTOSAR drivers 你好 Cuong、 我们得到了帮助和[email protected]创建了一个例子。 让我们把这张票保留到下周客户试用时。 我会允许你访问 Sharepoint 上的示例。 顺祝商祺! 维克托   Re: S32K358 HSE Random Number Generation based on AUTOSAR drivers 你好@viktorfellinger ,我正在为你创建一个示例。 同时,您能否告诉我: 1.您多久会遇到这个问题?是经常发生还是偶尔发生 2.pRequest 的值 pRequest 和 pHseSrvDesc 的 值。 Hse_Ip_ServiceRequest() 时的 pRequest 和 pHseSrvDesc 值。 您能否尝试增加 pRequest中的超时值 ,看看能否解决这个问题? Re: S32K358 HSE Random Number Generation based on AUTOSAR drivers 您好@viktorfellinger ,您收到反馈了吗? 如果没有更新,我想关闭这个话题。 客户稍后可以提出另一个问题,然后您可以再次提及此主题
記事全体を表示
BD-SL-i.MX6 运行 Qt 5.4(Qt 公司出品) <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> BD-SL-i.MX6 以前称为 SABRE Lite 板,是一种低成本的 i.MX6 开发平台。该主板的最佳特性之一是其提供的强大软件支持。这篇文章介绍了 QT 公司的 Qt5.4。下面的视频展示了Qt 公司的企业设备创建产品,这是一个针对 Qt 优化的预构建软件堆栈,可让您立即开始在真实设备上进行嵌入式 Linux 和 Android 开发的原型设计。该演示运行 Qt5.4,并且该图像可用于 BD-SL-i.MX6 以及我们的 Nitrogen 系列产品。以下是一段简短的视频,展示了部分功能: 上面的视频展示了为嵌入式 Linux 创建的图像,更具体地说,是使用Yocto 项目和飞思卡尔社区 BSP 的工具构建的。因此,您的产品可以利用这些项目提供的软件包,并且您可以使用 Yocto 构建系统来集成您的组件并定制您的构建。 有关更多详细信息,请访问http://qt.io或http://boundarydevices.com/qt-for-device-creation/ 概述
記事全体を表示
Ara240 Run Time Environment (rt-sdk-ara2) The Runtime SDK for AI/ML acceleration using the Ara240 NPU on NXP i.MX SoCs, provides the runtime environment for the Ara‑2 NPU.   Main Purpose of the Package    1. Provide the runtime environment for the Ara‑2 NPU This runtime sdk package installs everything needed for an i.MX system to communicate with and utilize the Ara240 NPU hardware, including: NPU drivers  Low‑level utilities (metrics, hardware bring‑up, flash tools) Proxy services that interface applications with the NPU Firmware loaders and NPU configuration files 2. Allow users to run AI/ML inference models on the NPU The Ara240 runtime environment includes tools for: Downloading pre‑compiled AI/ML models Running performance tests on the NPU Running classification, detection, pose, and segmentation models Inspecting HW IPS (inference/second) and real hardware performance   Scripts such as: fetch_models.sh ara_metrics.sh chip_info.sh program_flash.sh run_models_perf.sh 3. Automatically configure and optimize the i.MX system Installation does the following automatically: Expands system partition to handle large models (LLMs/VLMs) Sets up an 8GB SWAP for devices with limited RAM Prepares the runtime environment for AI workloads 4. Manage and update Ara‑2 firmware The package contains scripts to: Check the installed firmware version ( chip_info.sh ) Update firmware if needed ( program_flash.sh ) 5. Provide systemd service for automatic startup The SDK installs: A systemd service: rt‑sdk‑ara2.service   Walkthrough Video Below is the walkthrough video for this package (function() { var wrapper = document.getElementById('lia-vid-6396594498112w960h540r402'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (view in My Videos) ARA2-M2-16G-GT ARA240 Hands-On Training
記事全体を表示
FXTH87xx 最低功耗 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好 我正在调试 FXTH870911 的功耗。 目前的最小电流为 98-115μA。 经过计算,目前的耗电量无法满足需求。 我想知道该芯片的最小工作电流是多少,以及它是如何实现的。 提前感谢! Re: FXTH87xx minimum power consumption <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您好, 下面是 25°C 时的典型电流消耗: 您可以在设备数据表中找到停止模式的详细描述。 在项目中,如果选择了 LF_COMMUNICATION(通信)模式,则在 STOP1 中启用 LF 块。   模式的选择应在项目的 user_configuration.h 文件中进行。 在该文件中,可以选择三种不同的模式,一种使用 LF(LF_COMMUNICATION),另两种不使用 LF。 我建议选择 NO_LF_PWU 模式:在该模式下,FXTH 会定期唤醒以发送 RF 帧,在两次发送之间,FXTH 会转到 STOP1 并禁用低频。在这种模式下,两次射频传输之间的功耗应为 500nA。 顺祝商祺! 托马斯 PS:如果此答案有助于解决您的问题,请标记为"正确" 或 "有帮助"。谢谢。
記事全体を表示
以太网驱动程序读取 PHY 地址(LAN 9646) 大家好 我尝试用Eth_43_GMAC_ReadMii 函数读取 LAN 9646 的 PHY 地址,但返回的结果出乎意料。我只想问,这个功能是否适合用于读取 PHY 地址。感谢您的阅读。 Re: Read PHY address (LAN 9646) by Ethernet driver 您好, 是的,Eth_43_GMAC_ReadMii 是使用第 22 条通过 MDIO 读取 PHY 寄存器的函数。 不清楚您在函数中使用了哪些参数,以及得到了什么读数。确保使用设备数据表中指定的正确的 PHY 和寄存器地址进行标准 MIIM 寄存器(直接)访问。 还要确保选择了 MIIM 接口,根据设备 DS,它不是默认接口,而是通过捆绑选项配置的。   BR, Petr
記事全体を表示
ADC Self-Test (Square Check) Support for S32K314 Hello,  In the UM Square Check documentation that an ADC self-test mechanism is mentioned. However, when reviewing the Safety Mechanisms, the ADC self-test is marked as NONE, and we are also unable to find this option in the Square Check (SCheck) configuration for the S32K314 package. Please advise how this feature can be enabled or configured? Priority: HIGH Safety_SW Re: ADC Self-Test (Square Check) Support for S32K314 Hello Team, Is there any update? Thanks Re: ADC Self-Test (Square Check) Support for S32K314 Hello Team, Is there any update? Thanks Re: ADC Self-Test (Square Check) Support for S32K314 Hello Radoslav, What is the different between S32K3E and S32Kxx? It seems both of them are the group of S32K396, S32K394, S32K376, S32K374, S32K366 and S32K364? Can you please point out where to find the S32K3E specific RM and HW Safety Manual ? Thanks Re: ADC Self-Test (Square Check) Support for S32K314 Hello @JasonTsengSG , my understanding is that these are new K3 derivatives with higher performance and some additional support for traction inverters and motor control (eTPU): S32K3E_SW_Architecture.docx You can find RM and SM via intranet e.g. here (sometimes instead K3E you can use just specific K396 derivative name to address this K3 sub-group): Zebra - Documents - S32K396 - All Documents Automotive Safety Software - Release_1.0.6 - All Documents Kind Regards, Radoslav Re: ADC Self-Test (Square Check) Support for S32K314 Thank you, Radoslav, for the clear explanation.
記事全体を表示