Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
i.MXRT685S:通过 HS SPI 总线从外部闪存启动 我有一个外部 SPI 或非 闪存设备,通过 HS SPI 总线接口(Flexcomm 14)连接到 RT685s。我想从这个闪存设备启动;但是,我了解到只有 FlexSPI 启动、SD 启动和 eMMC 启动这三种主启动选项。是否可以使用高速 SPI 总线(Flexcomm 14)从该外部闪存启动?如果是这样,我需要遵循哪些要求/设置步骤才能执行此操作? Re: i.MXRT685S: Boot from external flash via HS SPI bus 以下是一些关于NOR启动的应用笔记,供您参考。 AN12751 如何从 QSPI Flash 启用恢复启动 AN12773 如何从串行 或非 Flash 启用主启动 Re: i.MXRT685S: Boot from external flash via HS SPI bus 嗨@lgibarra9 , 使用 FC14 的高速 SPI 总线无法从外部 SPI 或非 Flash 启动。除了运行时 SPI 通信外,该总线还可以在 MCU 处于 ISP 模式时下载图像。但是,对于从外部闪存进行正常启动操作而言,高速 SPI 总线不是一个选项,因此您的 SPI NOR 闪存应该连接到 FlexSPI 总线。 BR, 埃德温。
View full article
ビルド、デバッグ、プロジェクトのためにS32DSに設定ファイルを配置する方法 I just started with AUTOSAR and I have S32K144EVB I want to find instructions on how to use Tresos to generate config file and put it in S32DS for debug, build... Can anyone tell exactly where I should start from where? Re: How to put config file to S32DS for build, debug.... project これは、S32DS を扱っていて、ビルドとデバッグの設定を正しく行おうとしている人にとって、非常に役立つ質問です。参考資料としてパットナム裁判判例集などいくつかの関連資料を確認したところ、設定手順がより分かりやすくなった。重要なのは、設定ファイルを正しい場所に配置し、プロジェクト設定がそのファイルを指していることを確認することのようです。明確な手順を示す例があれば、初心者でもさらに理解しやすくなるでしょう。 Re: How to put config file to S32DS for build, debug.... project 所得税の概念は、個人、法人、パートナーシップ、その他の事業体が得た所得を評価し、課税することを含みます。 Re: How to put config file to S32DS for build, debug.... project 既存のプロジェクトファイルから新しいプロジェクトを生成する。構築 3. デバッグは 5 番目です。最終目的地。9 ...私たちのIDEsと開発環境であるEclipseが読み込みを開始します。これ なら...新しい>S32DSアプリケーションプロジェクト>ファイルへ移動...ビルドの設定で(1) C/C++ビルド、(2) 設定、(3) ターゲットプロセッサへ移動します。 Re: How to put config file to S32DS for build, debug.... project 既存のプロジェクトファイルから新しいプロジェクトを作成します。3. ビルディング。5. デバッグ。6. ターミナル。9 ...Eclipse環境とIDEの読み込みが始まり、コードを書 いたりテストしたりします。そうすれば...ファイル>新>S32DSアプリケーションプロジェクト...ビルド設定で、(1) C/C++ビルド、(2) 設定、(3) ターゲットプロセッサに進みます
View full article
i.MXRT685S: HS SPIバス経由で外部フラッシュからブート 私はRT685sのHS SPIバスインターフェース(Flexcomm 14)に接続した外部SPI NORフラッシュデバイスを使っています。このフラッシュデバイスから起動したいのですが、マスターブートのオプションはFlexSPIブート、SDブート、eMMCブートしかないと読みました。高速SPIバス(Flexcomm 14)を使用して、この外部フラッシュメモリから起動することは可能ですか?もしSOなら、実行するためにどのような要件やセットアップ手順に従うべきでしょうか? Re: i.MXRT685S: Boot from external flash via HS SPI bus 以下はNORブート用の参考となるアプリケーションノートです AN12751 QSPIフラッシュからのリカバリブートを有効にする方法 AN12773 シリアルNORフラッシュからのマスターブートを有効にする方法 Re: i.MXRT685S: Boot from external flash via HS SPI bus こんにちは、@lgibarra9 さん。 FC14の高速SPIバスを使用して、外部SPI NORフラッシュからブートすることはできません。このバスは(実行時SPI通信以外にも)MCUがISPモードの際にイメージをダウンロードするために使用できます。しかし、外部フラッシュからの通常の起動動作では高速SPIバスは使えないため、SPI NORフラッシュはFlexSPIバスにコネクテッドすべきです。 BR、 エドウィン。
View full article
MIMXRT1170-EVKB Debugger Usage with Custom Board & Serial Downloader Verification Hello Team, We have selected the MIMXRT1176 for our application and are currently using the MIMXRT1170-EVKB for evaluation and software development. Our custom board design is currently in progress, and we would like to clarify a few points before finalizing the hardware design. Q1: Using the EVKB Onboard Debugger with a Custom Board Is it possible to use the onboard debugger on the MIMXRT1170-EVKB to program and debug a custom RT1176-based board, or would a separate debugger be required? We expect this to be possible, but would appreciate confirmation from the NXP team. Additionally, could you please provide: The jumper settings that need to be modified on the EVKB. Any hardware changes required to disconnect the onboard debugger from the EVKB target MCU and route it to an external target. Details of the SWD/JTAG signals that should be connected to the custom board. As a practical test before our custom hardware arrives, we currently have two MIMXRT1170-EVKB boards (Board-A and Board-B). We would like to perform the following experiment: Use the onboard debugger of Board-A to program and debug the RT1170 MCU on Board-B. Similarly, use the onboard debugger of Board-B to program and debug Board-A. Could you please confirm whether this setup is supported and provide the required jumper settings and hardware modifications to achieve it? Q2: Verification of the Serial Downloader Path We would also like to verify our understanding of the Serial Downloader (SDP) mode implementation on the RT1170. From the EVKB schematic, it appears that jumpers J114 and J115 connect to LPUART1_RX and LPUART1_TX, respectively. If we remove these jumpers and connect an external USB-to-UART TTL adapter to the MCU side signals, and while Keeping the MCU in SDP mode can we: Use MCUXpresso Secure Provisioning Tool (SPT) or Boot Utilities to download and program images through the UART interface? We would appreciate confirmation that this is a valid flashing and recovery method for both the EVKB and our upcoming custom hardware. Thank you for your support and guidance. Best regards, Ruthvik R Re: MIMXRT1170-EVKB Debugger Usage with Custom Board & Serial Downloader Verification Hi @mayliu1 , Thank you for reply. Regarding Q1 : We will Be getting an external Debugger/Flasher. we wanted to know the if using the onboard debugger was possible in case we wanted to use it Regarding Q2 : We will Proceed ahead with testing the recovery SDP path. Thanks and Regards, Ruthvik Re: MIMXRT1170-EVKB Debugger Usage with Custom Board & Serial Downloader Verification Hi @Littell , Thank you for your reply and honest opinion.  Thanks and regards, Ruthvik Re: MIMXRT1170-EVKB Debugger Usage with Custom Board & Serial Downloader Verification Hi @ruthvik_1 , Thank you so much for your interest in our products and for using our community. A1: In principle, it is possible. However, this approach may require additional jumper configuration and hardware connection changes on the EVKB, which should be verified against the EVKB schematic. Therefore, we would generally recommend reserving a standard SWD/JTAG header on the custom board and using a dedicated external debugger, such as a J-Link or P&E Multilink, for development and debugging. A2: Based on the EVKB schematic, your understanding of the Serial Downloader path appears to be correct. RT1170 SDP mode supports image download through the ROM bootloader interfaces, including UART and USB. Based on the EVKB schematic, J114 and J115 are associated with the LPUART1 connection path. For UART SDP, the signals are: LPUART1_TX: GPIO_AD_24 LPUART1_RX: GPIO_AD_25 Therefore, after disconnecting J114/J115 on the EVKB, it should be possible.  Please ensure voltage-level compatibility, crossed TX/RX connections, and a common GND connection. Best Regards May Re: MIMXRT1170-EVKB Debugger Usage with Custom Board & Serial Downloader Verification Regarding "Q1: Using the EVKB Onboard Debugger with a Custom Board", that approach is just silly given the trivial cost of an MCU-Link.  You're compromising your base development boards and will regret it. Re: MIMXRT1170-EVKB Debugger Usage with Custom Board & Serial Downloader Verification Hi @mayliu1 , Thanks for the reply. We will be going with an external NXP MCU-Link Debug Probe. Thank you for the clarification. Thanks and Regards, Ruthvik  Re: MIMXRT1170-EVKB Debugger Usage with Custom Board & Serial Downloader Verification While it may be possible in principle, using the onboard debugger on one EVKB to debug another target board is not a recommended use case by NXP. We recommend reserving standard SWD/JTAG interfaces on the custom board and using a dedicated external debugger, such as J-Link, P&E Multilink, or MCU-Link, for development and debugging.
View full article
Software bring-up on custom hardware implementing RT-1170 Hi! I'm trying to get started with software development on the RT-1170 platform, but have run into problems when trying to configure booting from external flash on my custom board. To divide the problem I went back to the EVKB-board and tried getting a small (and verified on EVKB) program working using a barebones project (i.e. without the default files). It seems that I can program the flash by simply adding the region under "Edit project settings > MCU settings > memory details", but when I cycle power to the board it locks up and I have to switch to a different boot mode (serial downloader) to recover the MCU with an EVKB-example project. Could I please get some help with figuring out what is going wrong? Is there a software development guide for the imxrt MCUs similar to the hardware development guide (MIMXRT1170HDUG)? I of course know about the refernce manual but a checklist would have been nice for someone who has not gone through the "metal to hello world"-process onb this platform before. I have attached an export of the project. Thank you in advance! Re: Software bring-up on custom hardware implementing RT-1170 Hello @Henrik12345, In order to support you better, could you please provide me the following information? -Are you able to debug your project? -Which SDK version are you currently using? -Which flash device are you using? Is it the same one used on our EVK? If not, have you made any modifications to support your flash device? -I understand that you are using MCUXpresso IDE. Is my understanding correct? If so, could you please let me know which version you are currently using? Regarding your question about software development, there is no document equivalent to the Hardware Development Guide. However, you can take the SDK examples as a reference, as they provide demonstrations of the peripherals available on the RT1170. You can download the SDK through the SDK Builder. Instructions on how to obtain it are available in Part 2 "Get Software" of the Getting Started with the i.MX RT1170 Evaluation Kit. Although this guide is designed for the RT1170-EVK, it can also be used as a reference for the RT1170-EVKB. The SDK includes a project template that can be used as a starting point for your development. As shown the following image:   BR Habib Re: Software bring-up on custom hardware implementing RT-1170 Hello @Henrik12345, Additional changes are required if you want to boot from a different external flash device. I would recommend reviewing the following app notes to better understand the boot process and the image structure required for external flash devices. Although these app notes are designed for the RT1050, you can use them by reference for the RT1170: How to Enable Debugging for FLEXSPI NOR Flash AN12108: How to Enable Boot from QSPI Flash – Application Note The RT1170-EVKB only has incorporated the following memories:   As you may know each memory has specific commands to performing read, write or erase operations. For this reason, the LUT and drivers related to the RT1170-EVKB may not be compatible with your flash device. To properly evaluate your flash, you will need to perform the tests on your custom board.  I can suggest you use the Boot Memory Configuration feature in the MCUXpresso Secure Provisioning Tool v26.06. This feature allows you to test different flash configurations and generate the boot memory settings required by your device. Once you have completed the tests, please let me know the results. As a first step, I recommend verifying the communication with your MCU by following the instructions in the "Connection" section of the tool documentation. Please note that Secure Provisioning Tool supports communication through USB and UART, as it works through blhost commands for device access. Are you able to connect your custom board through either USB or UART? BR Habib Re: Software bring-up on custom hardware implementing RT-1170 Hi Habib! To clarify some things, I work with two different boards: The custom board which I have designed myself MIMXRT1175AVM8A DDR QSPI NOR flash, specifically the FS-S (1.8 V) series from Infineon Boot pins are strapped to BOOT_MODE = Internal Boot FLEXSPI_INSTANCE = FLEXSPI1 xSPI_FLASH_TYPE = Boot with default 0x03 Read Enabled FLASH_PROBE_TYPE = QuadSPI NOR ENCRYPT_XIP_EN = 0 FLASH_AUTO_PROBE_EN = 0 The official RT1170-EVKB kit Same boot pin settings I was not able to write to the flash memory on my custom board immediately so I tried to bring up the EVKB kit from scratch instead, which has not worked out. Are you able to debug your project? I'm able to debug the program on immediately after writing to flash on the EVKB-board and the program works as intended, but when I cycle power the core locks itself which leads me to believe that the boot rom program gets stuck. Probably by a bad header/data in the flash memory. I know that I'm able to write to the flash memeory as I can extract the data from the flash memeory and see that it changes between a working demo from the SDK and my "from scratch" program (which was the one I attached before). Which SDK version are you currently using? Which flash device are you using? Is it the same one used on our EVK? If not, have you made any modifications to support your flash device? No, it is not the same. See hardware specifics in answer for question 1. The only thing I modified was that I added the flash region in "Memory Details" under "MCU Settings" in the Project settings. I used the same driver script as the EVKB kit (MIMXRT1170_SFDP_QSPI.cfx) I understand that you are using MCUXpresso IDE. Is my understanding correct? If so, could you please let me know which version you are currently using? Yes, I'm using MCUXpresso v25.6.136 I'll try to use the demo project template and see if that solves the issue. How would I need to change this template to adapt it to my flash memory and MCU part number? BR Henrik
View full article
Eat-Sleep-Code-Repeat: Automotive Control Systems Using FRDM-A-S32K3XX Microcontrollers 1. Overview This article is the umbrella entry point for a series of automotive embedded workshops built on the FRDM-A-S32K3xx microcontroller family. It groups together five hands-on modules — Lights, Brakes, Steering, Comfort, and Transmission — each demonstrating a different real-world automotive function that a modern Body Control Module (BCM), Chassis ECU, or Powertrain ECU would implement in production vehicles. All five modules share the same educational philosophy: they take a simple, low-risk hardware setup (FRDM board + FRDM-K64 Click Shield + a few MikroE Click modules) and use it to teach the core embedded concepts that underlie automotive software: analog and digital signal acquisition, real-time processing, actuator control, and safety-aware system design. Together they cover the most common peripherals of the S32K3 family — ADC, GPIO, PWM, FlexIO, LPI2C, eMIOS — and expose students to the same tool-chain used by NXP customers: S32 Design Studio 3.6.5, the S32K3 Real-Time Drivers (RTD), the Application Code Hub (ACH), and the underlying Automotive Software Package. Learning philosophy — Eat-Sleep-Code-Repeat The whole workshop series is designed around the Eat-Sleep-Code-Repeat initiative — a learn-by-doing culture where students continuously iterate on real hardware, break things, fix them, refactor, and re-flash until the concepts stick. Every module is small enough to be completed in one lab session, yet rich enough to leave room for extensions (state machines, filtering, CAN networking, closed-loop control, safety fall-backs). Concepts covered across the series Analog sensing: potentiometers, force sensors, resistor-ladder buttons → ADC conversion, scaling, debouncing. Digital I/O: GPIO input handling (buttons, switches), GPIO output sequencing (stepper coils). Actuation: PWM-based motor speed control (DC motors, fans), PWM-based servo positioning, WS2812 LED driving through FlexIO. Communication: I²C configuration of external PWM drivers (Servo Click / PCA9685). Control patterns: continuous mapping, threshold-based decisions, state machines, safety interlocks. Automotive concepts: Body Control Module (BCM) behavior, functional safety (ISO 26262), fail-safe defaults, redundancy considerations. What this article gives you Each of the next five sections provides a short summary of one module — what it demonstrates, which hardware it uses, which peripherals are involved, and a direct link to the full detailed workshop article. Students should read this page first to understand where each module fits in the bigger picture, then dive into the individual articles for step-by-step instructions. 2. Vehicle Lighting Control The Lights module implements a simplified automotive lighting system that mirrors the behavior of a real vehicle Body Control Module. Six buttons on the Analog Key Click command different lighting functions — low beam, high beam, left/right turn signals, brake lights, and hazard lights — all displayed in real time on a 16-LED 4x4 RGB Click matrix. Key learning points Multi-button decoding on a single ADC channel (resistor-ladder input). Software debouncing and command decoding. Driving WS2812 LEDs through FlexIO (precise sub-microsecond timing without CPU load). BCM safety interlocks: high beam requires low beam ON; hazards synchronize left + right turn signals; high beam state preserved between blink cycles. Peripherals used: ADC0, FlexIO, GPIO. Boards: FRDM-A-S32K312 or FRDM-A-S32K344. Reference project:Automotive Lighting Control Using FRDM-A-S32K3XX Microcontrollers - NXP Community Demo: Vehicle Lighting Control on FRDM-A-S32K344 Automotive relevance: lighting is one of the most safety-critical driver-visibility functions in modern vehicles — this module teaches how a real BCM manages dependencies, blinking patterns, and fail-safe defaults. 3. Brake Status Monitoring The Brakes module implements a simplified brake status monitoring system where a Force Click sensor simulates the driver's brake-pedal pressure. As pressure increases, the ADC value grows and the application progressively lights up the 4x4 RGB Click LEDs in green → yellow → orange → red, providing immediate visual feedback of the current braking level. Key learning points Continuous analog sensor acquisition through ADC. Threshold-based decision logic: converting a raw ADC value into discrete alert levels. Driving the RGB LED matrix through FlexIO to reflect the current system state. Introduction to real-time monitoring and safety-oriented visual feedback. Peripherals used: ADC0, FlexIO. Boards: FRDM-A-S32K312 or FRDM-A-S32K344. Reference project: Automotive Brake Control Using FRDM-A-S32K3XX Microcontrollers - NXP Community Demo: Brake Status Monitoring on FRDM-A-S32K344 Automotive relevance: brake status is a core input for many downstream ECUs (ABS, ESC, hill-hold, brake lights). This module teaches the fundamental pattern of sensor → threshold → visual/electrical output that appears everywhere in automotive software. 4. Assisted Steering Control The Steering module demonstrates a simplified Electric Power Steering (EPS) / steer-by-wire concept. A POT Click potentiometer simulates the steering-wheel angle; the MCU reads it through ADC, scales it linearly, and generates a PWM command through the Servo Click (configured over I²C) that positions a Micro Servo SG 180° in real time. Key learning points Analog input scaling and linear mapping (ADC range → servo angle range). Using an external PWM controller configured over I²C (LPI2C1) — a common embedded pattern that offloads timing-critical work. Working with the Output Enable (OE) pin for safe-stop behavior. Understanding the actuation chain sensor → MCU → PWM → actuator. Peripherals used: ADC0, LPI2C1, GPIO. Boards: FRDM-A-S32K312 or FRDM-A-S32K344. Reference projects: Automotive Steering Control Using FRDM-A-S32K3XX Microcontrollers - NXP Community Demo: PWM-Based Steering Control on FRDM-A-S32K344 Automotive relevance: steering is a strictly safety-relevant function (ISO 26262 typically classifies it as ASIL C or D). This module introduces the concepts behind EPS and steer-by-wire and lays the foundation for future work with redundant sensors and fault detection. 5. Vehicle Comfort Control The Comfort module implements two independent comfort functions typical of vehicle body electronics: cabin cooling (a 5 V fan driven through a DC Motor 2 Click using PWM) and electric window control (a NEMA17 stepper motor driven through an H-Bridge Click using full-step GPIO sequencing). On-board push-buttons act as the driver's HVAC and window switches. Key learning points PWM motor speed control (fan simulation). Stepper motor full-step sequencing (A → B → C → D and reverse) through four GPIO outputs. Handling multiple independent actuators from a single MCU without blocking. Introduction to window anti-pinch and other real BCM safety concepts. Peripherals used: GPIO, eMIOS (PWM). Boards: FRDM-A-S32K344 (only). Reference project: Automotive Comfort Control Using FRDM-A-S32K344 Microcontrollers - NXP Community Demo: Vehicle Comfort Control on FRDM-A-S32K344 Automotive relevance: comfort systems (HVAC, windows, mirrors, seats) form a huge share of modern body electronics. This module shows how one ECU can coordinate multiple actuators of different types (rotational-speed and positional) using the same S32K3 platform. 6. Transmission Control The Transmission module demonstrates a continuous, proportional transmission control concept. A POT Click potentiometer represents the driver's acceleration command; the MCU samples it, applies linear scaling, and simultaneously drives two actuators: a Servo Click + Micro Servo that simulates the transmission selector position, and a DC Motor 2 Click + DC motor whose speed reflects the powertrain response. Key learning points Dual-actuator control from a single analog input (one MCU commands both servo angle and DC motor speed in parallel). Linear signal mapping to two different PWM ranges simultaneously. Combining I²C-configured PWM (Servo Click) and eMIOS-generated PWM (DC Motor 2 Click) in the same application. Understanding continuous vs. discrete control and how continuous mapping better mirrors real automotive behavior. Peripherals used: ADC0, LPI2C1, eMIOS. Boards: FRDM-A-S32K344 (only). Reference project: Automotive Transmission Control Using FRDM-A-S32K344 Microcontrollers - NXP Community Demo: Transmission Control on FRDM-A-S32K344 Automotive relevance: transmission control is part of the powertrain domain and requires deterministic response and safety-aware design. This module introduces the concepts and prepares students for more advanced topics such as closed-loop control, transmission-mode logic (P/R/N/D), and CAN networking with the engine ECU. 7. Conclusion Together, these five modules give students a complete tour of what a modern Body Control Module, Chassis ECU, and Powertrain ECU actually do in a vehicle — from reading sensors and buttons, through processing and safety interlocks, to driving lights, motors, and actuators. Each module can be studied independently, but the real value emerges when they are viewed as pieces of one coherent picture: the same MCU family (S32K3), the same tool-chain (S32 Design Studio + Application Code Hub), the same hardware base (FRDM-A-S32Kxxx + FRDM-K64 Click Shield + MikroE Click modules), applied to five different automotive domains. The series is intentionally aligned with the Eat-Sleep-Code-Repeat philosophy: start with a working example, then experiment — add filtering, replace polling with interrupts, introduce a state machine, add CAN communication, or refactor for functional safety. Every extension is a step closer to the way production automotive software is actually written. Recommended learning path: Lights — simplest, teaches ADC, FlexIO and BCM logic. Brakes — introduces continuous sensor thresholds. Steering — adds I²C-controlled PWM and actuator positioning. Comfort — multi-actuator, dual-technology control (PWM + stepper). Transmission — combines everything into a proportional, dual-actuator system. If you have questions, suggestions for improvement, or ideas for new modules that could extend this series, please leave a comment below — feedback from students and instructors is what keeps the workshops relevant and up to date.
View full article
S32DS ARM 2.2 issue After installing S32DSARM 2.2 on Windows 11, the following error message appears. The default project cannot be opened either. Re: S32DS ARM 2.2 issue Hi@ yeSerrui After installing S32 DS, you also need to install the RTM SDK, as shown below. In the project browsing box on the left, right-click "new" to select the included example.
View full article
NFC Cockpit 下载 大家好!不好意思问个傻问题,请问哪里可以下载适用于我的CLRC 663的NFC Cockpit? 软件页面上找不到相关信息:
View full article
NXP MIMXRT1062DVL6Bに関するヘルプ/質問 NXP MIMXRT1062DVL6B おもちゃのデザインについて。 ユニット番号:NXP MIMXRT1062DVL6B に関して 強力な600MHz CortexM7を搭載しているので、私には必要以上の性能かもしれません。 私はそれを2語のフレーズを認識するためだけに利用しています。VIT + 2つのマイク+カスタムウェイクフレーズを安定して動作させる、最も安価なNXPプロセッサはありますか? ご相談のため、[email protected]までメールをいただければ幸いです。 Re: NXP MIMXRT1062DVL6B help/questions こんにちは、 @toy_maker さん。 ご質問ありがとうございます! VITが提供するサポート対象部品番号のリストを参照してください。 また、このスレッドの議論も参考になるはずです:https://community.nxp.com/t5/MCX-Microcontrollers/Wake-Word-and-Voice-command-engines/m-p/2054222 MCXNに関する詳細情報については、関連するコミュニティフォーラムに質問を投稿することをお勧めします。ありがとう! よろしくお願いします、 ギャビン
View full article
LPC55xx API Hello, for a new project I want to use LPC550x microcontroller with IAR Embedded Workbench: in the past I have used other LPC MCU (LPC1317, LPC1788, LPC1788) Now i read everywhere that some functions can be managed only by using API but I don't understand how to use them; are these function available only with MCUXPRESSO? I would like to avoid API and write my own code but I don't fine the C code of these API. For example CAP BANK for oscillators are only documented with API so if I don't use API I can't use these CAP BANK. Is it correct? I have a big confusion in my mind about this. Can anyone help me? It's for my job Best regards. Re: LPC55xx API Hello @Lor75  For newer NXP MCUs, including the LPC55xx series, we recommend using the MCUXpresso SDK drivers, which include both APIs and source code. You can download the SDK from: https://mcuxpresso.nxp.com/builder?hw=LPCXpresso55S06&rel=943  For detailed instructions, please refer to: https://www.nxp.com/document/guide/getting-started-with-the-lpc55s06-evk-evaluation-board:GS-LPC55S06-EVK?section=get-software   Additionally, the LPC55xx series is supported by MCUXpresso IDE, which is free to use with no restrictions on functionality or code size. You can download MCUXpresso IDE from: https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE  If still have any question, please feel free to contact me. Thank you.  BR Alice Re: LPC55xx API Hello, Just like your past LPC microcontrollers, the LPC550x is a standard memory-mapped architecture. You are never forced to use NXP's driver APIs. You can write pure, direct-register C code using standard CMSIS header files (lpc55s06.h, etc.) provided by IAR or NXP. Best Regards
View full article
GUI Builder 2.0生成图片代码bug 生成的宏名带空格 Re: GUI Builder 2.0生成图片代码bug Hello @lqdjdy , 感谢你的帖子。试试看把图片的名字从face-id改成face_id能解决吗? BR Celeste Re: GUI Builder 2.0生成图片代码bug 是的,图片名称不能带中横线 Re: GUI Builder 2.0生成图片代码bug 感谢您的确认。我会向 SW 团队提出建议,在图片名称包含异常字符时弹出异常提示。
View full article
LPC55xx API こんにちは、 新しいプロジェクトでは、LPC550xマイクロコントローラとIAR Embedded Workbenchを使いたいと考えています。過去には他のLPC MCU(LPC1317、LPC1788、LPC1788)を使っていました どこでも「APIでしか管理できない関数もある」と読んだのですが、どう使えばいいのか分かりません。これらの機能はMCUXPRESSOでしか使えないのでしょうか? APIを使わずに自分でコードを書きたいのですが、これらのAPIのC言語コードが見つかりません。例えば、オシレーター用のCAP BANKはAPIでしかドキュメント化されていないので、APIを使わなければこれらのCAP BANKは使えません。それは正しいですか? これについて、私は大きな混乱を抱えています。 どなたか助けてくれませんか?仕事のためです よろしくお願いいたします。 Re: LPC55xx API こんにちは、 @Lor75さん LPC55xxシリーズを含む新しいNXP MCUでは、APIとソースコードの両方を含むMCUXpresso SDKドライバの使用を推奨します。 SDKは以下からダウンロードできます: https://mcuxpresso.nxp.com/builder?hw=LPCXpresso55S06&rel=943  詳細な手順については、以下を参照してください。 https://www.nxp.com/document/guide/getting-started-with-the-lpc55s06-evk-evaluation-board:GS-LPC55S06-EVK?section=get-software さらに、LPC55xxシリーズはMCUXpresso IDEでサポートされており、機能やコードサイズに制限なく無料で使用できます。 MCUXpresso IDEは以下からダウンロードできます: https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE  もし質問があれば、どうぞ気軽にお問い合わせください。ありがとう。 BR アリス Re: LPC55xx API こんにちは、 これまでのLPCマイクロコントローラと同様に、LPC550xは標準的なメモリマップアーキテクチャです。NXPのドライバーAPIを強制的に使う必要はありません。標準的なCMSISヘッダーファイル(lpc55s06.h、(など)IARまたはNXPによって提供されます。 よろしくお願いします
View full article
NXP MIMXRT1062DVL6B 帮助/问题 NXP MIMXRT1062DVL6B 关于玩具设计。 关于您的设备编号:NXP MIMXRT1062DVL6B 它配备了强大的 600MHz CortexM7 处理器,这可能超出了我的需求。 我用它来识别两个单词的短语。NXP 是否有价格最低的处理器能够可靠地运行 VIT + 两个麦克风 + 自定义唤醒词? 欢迎通过电子邮件联系,以便我们进一步讨论:[email protected] Re: NXP MIMXRT1062DVL6B help/questions 嗨@toy_maker , 谢谢你的提问! 请参考VIT提供的受支持零件编号列表。 此外,这个帖子里的讨论应该会有帮助: https://community.nxp.com/t5/MCX-Microcontrollers/Wake-Word-and-Voice-command-engines/mp/2054222 有关 MCXN 的更多信息,我们建议您在相关的社区论坛中发布您的问题。谢谢你! 此致, 加文
View full article
NXP MIMXRT1062DVL6B help/questions NXP MIMXRT1062DVL6B regarding toy design. In regards to your unit number: NXP MIMXRT1062DVL6B a powerful 600MHz CortexM7 and it may be more then I need. I am using it to only to recognize a two word phrase. IS there a least expensive NXP processor that can reliably run VIT + two microphones + a custom wake phrase? Would appreciate an email to discuss: [email protected] Re: NXP MIMXRT1062DVL6B help/questions Hi @toy_maker , Thanks for your questions! Please refer to the list of supported part numbers provided by VIT. Also, the discussion in this thread should be helpful: https://community.nxp.com/t5/MCX-Microcontrollers/Wake-Word-and-Voice-command-engines/m-p/2054222 For more information about MCXN, we recommend that you post your question in the relevant community forum. Thank you! Best regards, Gavin
View full article
NFC Cockpit download Hi all! Sorry for stupid question, but where i can download NFC Cockpit  for my CLRC 663? Cant see on software page :
View full article
NXP layoffs? Apparently a lot of people were laid off yesterday and more layoffs are coming this week and next. Anyone know anything about this? Power
View full article
GUI Builder 2.0の画像生成コードのバグ 生成されたマクロ名にはスペースが含まれます。 Re: GUI Builder 2.0生成图片代码bug こんにちは、 @lqdjdy さん。 投稿ありがとうございます。「face-id」という画像ファイル名を「face_id」に変更すれば問題は解決するでしょうか? BR セレステ Re: GUI Builder 2.0生成图片代码bug はい、画像名にはハイフンを含めることはできません。 Re: GUI Builder 2.0生成图片代码bug ご確認いただきありがとうございます。画像名に特殊文字が含まれている場合にエラーメッセージを表示するよう、ソフトウェアチームに提案いたします。
View full article
S32DS ARM 2.2 issue windows 11 安装S32DSARM 2.2安装后提示以下错误  也打开不了默认的 工程 Re: S32DS ARM 2.2 issue Hi@yeSerrui 安装完S32 DS,还需要安装RTM SDK,如下所示 在左侧工程浏览框中,右键new可选择自带的例程
View full article
GUI Builder 2.0 image generation code bug The generated macro name includes spaces. Re: GUI Builder 2.0生成图片代码bug Hello @lqdjdy , Thanks for your post. Would renaming the image from "face-id" to "face_id" solve the problem? BR Celeste Re: GUI Builder 2.0生成图片代码bug Yes, image names cannot contain hyphens. Re: GUI Builder 2.0生成图片代码bug Thank you for your confirmation. I will suggest to the SW team that an error message be displayed when the image name contains abnormal characters.
View full article
NFC Cockpitのダウンロード こんにちは、みんな!馬鹿な質問で申し訳ありませんが、CLRC 663用のNFCコックピットはどこでダウンロードできますか? ソフトウェアページには見当たりません:
View full article