Matlab2023a Envokes S32DS3.5 Encountered Error Dear MBDT Team. We are using MATLAB2023a scripts to generate code after compiling Simulink models, then call eclipsec.exe to perform headless background compilation. Once the build is completed, a hyperlink is created in the Simulink Diagnostic Viewer to directly open the workspace corresponding to the compiled project. This workflow worked perfectly with S32DS 3.4. However, after upgrading to S32DS 3.5.8, two issues have occurred: Issue 1: Clicking the hyperlink that's created by Simulink will launch the background process s32ds.exe, which then pops up and exits immediately. We have tried several solutions like adding the parameter "-vm \bin\javaw.exe" to s32ds.ini (this has no effect on s32ds.exe), and prioritizing the JDK 11 path in system environment variables. None of these attempts resolved the problem. Issue 2: As previous described, calling eclipsec.exe via MATLAB scripts triggers the error shown in the screenshot: Java was started but returned exit code=1. We set "\bin\javaw.exe" and JDK 11 path at the top of system environment variables. The Command Prompt correctly displays Java 11 (64-bit), yet Simulink compilation still attempts to load jvm.dll. After deleting "client\jvm.dll" or "server\jvm.dll", the program will locate java.exe instead, but still reports an error with exit code=4. In addition, manual compilation remains successful in all cases. All the related files and settings will be uploaded for your reference. Please help give your advice to fix this. Thank you. Re: Matlab2023a Envokes S32DS3.5 Encountered Error Hello, From what I understand from your message, you have a Simulink Model and generate code for it using the Embedded Coder. Then you have set up a workflow to compile the code using eclipsec. The main problem I see is that MATLAB do not currently use the correct Java version. Have you tried to contact them about this problem? Moreover, I suspect that you don't use Model Based Design Toolboxes developed by NXP (e.g. S32K3, S32K1 etc). Let me know if I am wrong. Best regards, Sorin Bancila

Debug interface recommendations for Kinetis and LPC? I do most of my development on the Kinetis series, and potentially some LPC parts in the near future. I've got a drawer full of debug interfaces from P&E Micro, including a Cyclone ACP that I use most. I sometimes find myself switching from the $600 Cyclone to the $20 LPC-Link2 because the Cyclone has so many weird problems with MCUXpresso. Honestly the LPC-Link2 does most of what I need, it's just a bit slow. Should I be looking at Segger interfaces? Can someone recommend a reliable, reasonably fast interface that's well-supported in MCUXpresso (and hopefully CodeWarrior 11 as well) that doesn't cause crashes all of the time, or fail to halt a running target? Trace support would be nice. Thanks! Re: Debug interface recommendations for Kinetis and LPC? Hi @richard37  Thank you for your post! You may want to consider a SEGGER J-Link. It supports both Kinetis and LPC devices when used with MCUXpresso, and it is also natively supported by CodeWarrior 11. This makes it a good alternative if you need a debug probe that can be used across both development environments and device families.

Random occurences of timeouts while reading variables Hello, I have been working on a battery test rig set up by my predecessors on the project. The test rig uses an nxp S32K144EVB board connected via usb to a computer. The code is built from a simulink file and monitoring of the test is made via FreeMASTER 3.2. The project has been working on a laptop for a few months and it has been necessary to configure a new laptop as a replacement. However, even while installing the same FreeMASTER version, the same drivers and using the same project files, all variable reads as "?" due to timeout errors after a seemingly random duration. Any help would be greatly appreciated. Logged errors after 12 minutes of runtime with no issues : fbw_0-1784820901163.png Re: Random occurences of timeouts while reading variables Hello, I don't think I encounter that problem yet but I have a few suggestions, maybe they can help: Try to power up the S32K144EVB from a 12V power supply instead from the USB. Getting Started with the S32K144EVB  Try different methods to connect the FreeMASTER project to the EVB: Use the onboard USB connector External Serial2USB convertor Use a debug probe to connect directly to the S32K144 MCU Try to reduce the refresh time for non critical variables Prevent the laptop to enter sleep mode (as it might cut USB power to save battery). Try to create a new FreeMASTER project from scratch. Best regards, Sorin Bancila

MBDT FOR S32K1XX MEIDEI_0-1783149479446.png Could you please explain why this configuration prevents the message from being sent successfully? Is there a need for additional modules? Re: MBDT FOR S32K1XX Hello, What board are you using? If you are using the S32K146 evaluation board, please note that the UART instance connected to the microUSB is actually LPUART1. If you are using an external serial converter, please check the schematic for the board to see that it is actually connected to LPUART0 (the instance you configured in the model). You might want to check included examples in the toolbox to see how to configure and use different peripherals. You can check the Quick Start Guide for S32K146 to have an overview of the most important connectors found on it: Getting Started with the S32K146 Evaluation Board for General Purpose  Best regards, Sorin Bancila.

S32 IDE开发环境RTD插件无法安装 需要S32 IDE开发环境安装S32ZE RTD插件开展S32Z280处理器软件开发工作，在环境中无法安装，提示如图1，在NXP官网无法下载，提示需要License，请提供License获取渠道，谢谢。 Re: S32 IDE开发环境RTD插件无法安装 不客气，有任何问题随时联系！ Re: S32 IDE开发环境RTD插件无法安装 第一个连接要求账号登录，登录后没有显示安装包下载路径。第二个连接进入“汽车软件包管理器”后成功下载到安装包，谢谢。 Re: S32 IDE开发环境RTD插件无法安装 Hi,Flynn_T 1.您看这个链接可以下载吗？最新的RTD版本应该是2.0.1 QLP01，版本列表中没有你提到的1.1.45。另外注意，2.0.1 QLP01的RTD，需要的S32DS IDE的版本是3.6.1。 Design : Product Information : Automotive SW - S32Z/E - Real Time Drivers (RTD) Joey_z_0-1786528248987.png 2.这个链接您也可以看下，是否可以下载。 汽车软件包管理器 | NXP 半导体 BR Joey Re: S32 IDE开发环境RTD插件无法安装 Hi， BR Joey     我使用的S32 IDE的版本是3.6.10。需要安装的RTD版本是1.1.45，我NXP官方网站没有找到S32Z/E RTD插件的下载路径，请提供一个下载连接。 Best Regard Flynn_T Re: S32 IDE开发环境RTD插件无法安装 Hi，Flynn_T 您使用的S32 IDE的版本是多少呢？RTD版本是多少呢？ 在IDE中加载S32Z/E RTD插件一般不需要license。 BR Joey

mc9s08qg8 compiler proto type: i have a product using this chip. it is not obsolete. i have the code to compile, from 1980. what i want to do, is update the cs v6.3 code on windows 11. i want to update the product from and evaluation unit to a working unit, to be released to manufacturers of sewing equipment. I have three lines of c code to update the product for production.  HISTORY: BOBBIN SHOW < 1980. displayed prototype of unit at the show and sold 15 copies for $150 each. I developed specialized gate array chips at International Microciruits INC(IMI) to implement functions. WELL, the unit was a single use. I got a patent and I put the  BOBBIN CONTROLLER "BC" away until 1983.  Used the mc9s08qg8 chip to up grade the BC to many more functions. living on welfare, i did not have money to further my business. NOW i took the developed unit out of storage, and being 72 i am trying to finish off the last coding to get the latest functions. i am going to try to sell it big before i die. my last move before i die, i can not loose. If u can not help me further, i am going to TI and use their chips. U have me locked out of your devlopment software. So i got maybe 12 years left, and ur chip is the core of the product. If U R not intersested in this product, i will go to TI. I do not have time to play with you business cycles. I figure if the unit takes off, i can sell 20,000 units. It works better than i tought 43 years ago, So am I in or out. I need the BDM drive for my wiztronics. com board interface and cw 11.1 to finish the final unit off. ALSO, i am still on SS. NO money, only a dream. i can not afford $500 fora P&E USB multilink Universal prgrammer. Maybe u would like to "venture capital" the device. u got the whole c code, which i downloaded to u!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! the ball is in ur court. Re: mc9s08qg8 compiler Hello I give you a suggestion on your other post if it could help you in repairing the BDM driver to use the device in CodeWarrior mc9s08qg8 drivers Could you confirm if you have consulted with Wiztronics about the driver's usage in their boards, do you have any feedback? Best Regards

MIMXRT1160 XIP fails randomly I have multiple boards running XIP from octal flash at 166 MHz. One of them fails occasionally  with "undefined instruction" error.  I've suspected signal integrity issues but I do not have test points on the PCB, so the only way to check that has been reducing speed from 166 MHz to 133 MHz, which appears to "fix" the problem with that particular board.  It's probably telling that the error appears most often when chainloading the application from mcuboot. It is more rare during application runtime. I can't find a reliable way to trigger it too - need to power-cycle the board several times until the fault appears.  Is there a way I can diagnose this XIP failure with more precision? Re: MIMXRT1160 XIP fails randomly Hi @tbonkers , The behavior you describe is most likely caused by insufficient read-sampling margin (setup/hold) at 166 MHz, due to tight PCB-routing/signal-integrity headroom on the Flash data lines. This also explains both symptoms: dropping to 133 MHz widens the sampling window so the issue "disappears"; and the mcuboot chainload is the first, dense, cache-cold instruction fetch right after a cold reset, where margin is tightest — hence it fails most often there, while runtime fetches mostly hit cache and rarely trigger it. We suggest the following checks, all software-side and requiring no PCB test points: Start with dummy cycles. Verify that the dummy-cycle count in the read LUT strictly matches your Octal Flash datasheet spec at 166 MHz. If an auto-generated FCB (e.g., from the provisioning tool) uses a lower value, set it to the datasheet-specified value, and you may add 1–2 extra dummy cycles to widen the data-valid window and increase sampling margin. Insufficient dummy cycles place the first data beat in the turnaround/not-yet-settled region — a classic source of intermittent errors. Verify the read sample-clock source . 166 MHz is only in-spec when readSampleClksrc=3 (kFlexSPIReadSampleClk_ExternalInputFromDqsPad: read strobe/DQS provided by the Flash device). If it is currently 0 or 1, 166 MHz is out of spec, which is fully consistent with "133 MHz fixes it." Please confirm a real DQS trace exists on the PCB and use this mode. If intermittent faults persist after these adjustments, you can run at 133 MHz as a safe baseline while isolating the 166 MHz margin bottleneck via steps 1–3 above. And this post may also help: https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs/Octal-flash-IS25WX256-dummy-cycles/m-p/2178828   Best wishes, Gavin Re: MIMXRT1160 XIP fails randomly Error log or schematics sharing could be helpful, how about the failing rate till now? Re: MIMXRT1160 XIP fails randomly Hi @Gavin_Jia , I've tested the read command with different dummy cycles count, and the failure is still there. I've set the number of dummy cycles in the flash volatile register to 20 so that it can support 166 Mhz. According to the flash datasheet it should support up to 200 MHz with 20 dummy cycles. readSampleClksrc=3 is set by the bootROM, confirmed with debugger connected. The DQS trace does exist.  Sometimes the fault happens while application is running, after the first major flash read. Re: MIMXRT1160 XIP fails randomly Hi @tbonkers , Thanks for the detailed testing. Based on your findings, this is most consistent with the 166 MHz Octal DDR XIP read path operating at the edge of its sampling / signal-integrity margin. readSampleClksrc=3 and the DQS trace are necessary but not sufficient conditions: in DDR DQS mode, the RT1160 side still requires the DQS-to-SIO relative skew to stay within ~±1 ns, and 166 MHz is the interface's upper limit, so margin is minimal.  I’ve looked into more resources, and the following solutions may help you resolve the current issue without modifying the PCB: Apply DLL errata ERR011377. The RT1160 errata states that after the DLL lock-status bit is set, an immediate read/write to the external flash may still return wrong data due to a timing issue; the workaround is to wait at least 512 FlexSPI root-clock cycles after the lock bit is set before accessing flash. Please ensure this delay is applied in every path in the bootloader and application that reconfigures FlexSPI/DLL/clock — this fits well with "most frequent at chainload, intermittent at runtime." Run a quantifiable RAM-resident stress test (more effective than repeated power-cycling). Place the test code and fault handler in ITCM/OCRAM, repeatedly read large flash blocks from the AHB memory map with CRC comparison, sweeping 166/133/120 MHz. If the error rate drops sharply as frequency decreases, it confirms a timing/SI-margin issue. For the mcuboot case:  if the bootloader ever erased/programmed the external NOR, you must invalidate I/D-cache before jumping to the application; also confirm the application does not re-initialize FlexSPI with different clock/DLL/LUT/pad settings. If in the end only 166 MHz fails while 133 MHz is stable, we recommend 133 MHz as the safe operating frequency for the current board; if 166 MHz is mandatory for production, the PCB DQS/SCLK/SIO length-matching, impedance, crosstalk, and pad drive strength should be reviewed, with test points added for these signals in the next revision. Best regards, Gavin

i.MX8MP: SError & Page Fault when running M7 with SAI3 audio enabled NXP 官方团队，您好： 我们在使用 i.MX 8M Plus 平台开发系统，运行 Linux A53 与 FreeRTOS M7。在尝试将 SAI3 音频接口分配给 Linux 使用的同时运行 M7 时，遇到了内核崩溃（SError / 页错误）。 1. 软件版本与环境： Kernel 版本：Linux 5.10.72 U-Boot 版本：U-Boot 2021.04 M7 SDK：MCUXpresso SDK for i.MX8MP (rpmsg_lite_str_echo_rtos) 参考官方文章：NXP Knowledge Base: Test SAI3 while running M7 firmware with remoteproc 2. 系统配置情况：   <1> M7 固件（m7.bin）存放在系统分区，并在 U-Boot 阶段通过 bootaux 0x007e0000 命令直接启动。 <2> 在 Cortex-A53 Linux 侧，我们使用挂载在 SAI3 + I2C3 + SDMA3 总线上的物理声卡芯片（SGTL5000）。 <3> Cortex-M7 负责 GPIO2_IO09 管脚上的 采集并触发高频采样中断，并通过 RPMsg 虚拟串口（/dev/ttyRPMSG30）与 A53 Linux 进行跨核数据交互。 3. 遇到的问题： 不调整声卡资源到A53的话，/dev/ttyRPMSG30设备操作是正常的； 目前需要应用A53的声卡设备，参考了官方帖子<Test SAI3 while running M7 firmware with remoteproc>后做出了以下调整，但内核启动会存在问题，改动部分如下： <1> 内核 dts配置已恢复声卡配置到A53，如附件 <2> u-boot dts： 分配了声卡资源到A53，如 <3> ATF，将 SAI3、sdma3 和 i2c3 分配给 A53，修改imx8mp_bl31_setup.c，如： <4> M7 SDK： 注释BOARD_BootClockRUN和BOARD_RdcInit函数涉及AUDIO的改动，如附件 和 4. 内核 dmesg 崩溃日志： 开机进入内核会卡主，log如下： [ 2.992289] i2c i2c-1: IMX I2C adapter registered [ 2.997631] SError Interrupt on CPU2, code 0xbf000002 -- SError [ 2.997634] CPU: 2 PID: 135 Comm: kworker/2:1 Not tainted 5.10.72-gf8ca51a867fa-dirty #56 [ 2.997636] Hardware name: EMB-3512-V11-M7 (DT) [ 2.997638] Workqueue: events deferred_probe_work_func [ 2.997642] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) [ 2.997644] pc : i2c_imx_probe+0x31c/0x8fc [ 2.997645] lr : i2c_imx_probe+0x2b0/0x8fc [ 2.997647] sp : ffff8000126a3af0 [ 2.997648] x29: ffff8000126a3af0 x28: ffff80001135c3f0 [ 2.997654] x27: ffff0000c50aa880 x26: 0000000000000023 [ 2.997660] x25: ffff0000c50aaca0 x24: ffff0000c50aa8f0 [ 2.997666] x23: ffff800011d7c090 x22: ffff0000c4410e40 [ 2.997672] x21: ffff80001135c428 x20: ffff0000c041d800 [ 2.997677] x19: ffff0000c041d810 x18: 0000000000000020 [ 2.997683] x17: 0000000000000000 x16: 0000000000000000 [ 2.997689] x15: ffff0000c44112b8 x14: 0000000000000000 [ 2.997695] x13: ffff0000c4410e40 x12: ffff8000126a3a70 [ 2.997700] x11: aaaaaaaaaaaaaaab x10: 0000000000000060 [ 2.997706] x9 : ffff800011b993b4 x8 : ffff800011b99000 [ 2.997712] x7 : 00007dfed2122a00 x6 : 000000000007a120 [ 2.997718] x5 : 0000000000b71aff x4 : 0000000000000002 [ 2.997723] x3 : 0000000000000002 x2 : 0000000000000000 [ 2.997729] x1 : ffff0000ff86ea08 x0 : ffff800013c8000c [ 2.997736] Kernel panic - not syncing: Asynchronous SError Interrupt [ 2.997741] CPU: 2 PID: 135 Comm: kworker/2:1 Not tainted 5.10.72-gf8ca51a867fa-dirty #56 [ 2.997742] Hardware name: EMB-3512-V11-M7 (DT) [ 2.997744] Workqueue: events deferred_probe_work_func [ 2.997747] Call trace: [ 2.997748] dump_backtrace+0x0/0x1a0 [ 2.997750] show_stack+0x18/0x70 [ 2.997751] dump_stack+0xd0/0x12c [ 2.997752] panic+0x16c/0x334 [ 2.997754] nmi_panic+0x8c/0x90 [ 2.997755] arm64_serror_panic+0x78/0x84 [ 2.997757] do_serror+0x64/0x6c [ 2.997758] el1_error+0x90/0x110 [ 2.997760] i2c_imx_probe+0x31c/0x8fc [ 2.997762] platform_drv_probe+0x54/0xb0 [ 2.997763] really_probe+0xec/0x4d0 [ 2.997765] driver_probe_device+0x58/0xc0 [ 2.997766] __device_attach_driver+0xa8/0x10c [ 2.997768] bus_for_each_drv+0x78/0xd0 [ 2.997769] __device_attach+0xd8/0x180 [ 2.997771] device_initial_probe+0x14/0x20 [ 2.997773] bus_probe_device+0x9c/0xa4 [ 2.997774] deferred_probe_work_func+0x80/0xc0 [ 2.997776] process_one_work+0x1cc/0x350 [ 2.997777] worker_thread+0x2bc/0x46c [ 2.997779] kthread+0x154/0x160 [ 2.997780] ret_from_fork+0x10/0x30 [ 2.998109] SMP: stopping secondary CPUs [ 2.998111] Kernel Offset: disabled [ 2.998113] CPU features: 0x0240002,2000200c [ 2.998114] Memory Limit: none 请帮忙看看问题点，是否有相关文档和改动可以解决，期待你们的建议和答复！感谢！ 回复： i.MX8MP: SError & Page Fault when running M7 with SAI3 audio enabled 已解决，需要完整关闭M7端的音频配置才可以

NXP SR040 Peak Power Consumption Hello, what is the peak power consumption of the SR040? And can I get a breakdown of Tx/Rx/idle? Re: NXP SR040 Peak Power Consumption Hello, Hope you are doing well. Sorry for the inconvenience this might cause you but as the information of this product it's under NDA (Non-Disclosure Agreement) the information it's not public. For more information about the chip could you please contact one of our distributors available in the Distributor Network|NXP? Or if you have any direct contact who helped you getting this device, please contact them. If you are looking for information about our UWB products or you are interested in this technology, I would recommend you check these Development Kits and Modules from our Partners (Trimension UWB Partners). In case you are interested in one of these Kits/Modules, you would need to go directly with them to know the process and the support that they can provide them, as the support path for this technology is through them. The documentation and software are distributed by the corresponding UWB Module partner. By selecting a module, you will be guided to our partner’s page where you can access datasheets, application notes, and the required enablement Regards, Ricardo

Could someone please help me find the Safety Manual for the S32K3? Hi everyone, I'm looking for the Safety Manual for the NXP S32K3 MCU family. Could someone help me find it or provide information on how to access it? Re: Could someone please help me find the Safety Manual for the S32K3? Hi Have you already signed an NDA with NXP? If you are unsure whether company has signed an NDA with NXP, please tell me company's full name or address. If you already have a valid NDA, please refer to this document to register a Secure File account. Once you have Secure File access, you can click on Secure in the documentation section of the S32K3 product page and download the Safety Manual. Safety Manual S32K3.png Best Regards, Robin

MCUXpresso SDK Latest Version - Recommended Approach for Flash Data Storage Hi Team,   I am evaluating the latest version of the MCUXpresso SDK and working with an NXP MCU.       For saving small configuration parameters (device settings, calibration values, counters, etc.) into internal Flash memory, what is the currently recommended approach?     Specifically:   1. Is it better to use a dedicated Flash storage area or EEPROM emulation (where supported)?   2. Are there any performance or reliability considerations when performing frequent Flash write operations? 3. Does NXP provide any example projects demonstrating best practices for parameter storage and wear leveling? 4. Are there any SDK libraries recommended for managing persistent configuration data? I have reviewed the available SDK documentation, but I would appreciate guidance on the recommended implementation approach for new projects.   Re: MCUXpresso SDK Latest Version - Recommended Approach for Flash Data Storage Hello @Manjuanth, I see you've posted this on the S32K's product forum, however, S32K's MCUs are not compatible with MCUXpresso, and use S32 Design Studio instead. Could you share which NXP MCU you are using? Best regards, Julián 

MCX W23 Power Profile Tools for CGM This page is dedicated to the Kinetis MCX W23 Power Profile Tool for Continuous Glucose Monitoring (CGM). It will help you to estimate the power consumption in your CGM application and evaluate the battery life time of your solution. This page will contain dedicated power profile tool for: CGM full application using the MCX W23 product christophe_menard_0-1786027418500.png AN14157 Power consumption analysis AN14660 Power management id: Wireless connectivity forum [start:July 31 2026]

Kinetis MCX Wxx (KW47 & MCX W72) 蓝牙定位电源我的工具 本页面专用的 Kinetis KW47 和 MCX W72 功率我的本地化工具 (CCC CS)。 它将帮助您估算应用（汽车和工业物联网）中的功耗，并评估解决方案的电池寿命。 本页面包含一个专用的、用于以下用途的我的电源工具： 汽车和工业物联网定位应用（CCC CS） 汽车行业： KW47 SDK 中提供了 2 个汽车应用示例： ...\kw47b41zevk\wireless_examples\bluetooth\digital_key_car_anchor_cs ...\kw47b41zevk\wireless_examples\bluetooth\digital_key_device_cs 工业物联网 (IIoT) ... MCX W72 SDK 中提供了 2 个 IIoT 应用示例： ...\MCX W72\boards\mcxw72w148evk\wireless_examples\bluetooth\loc_reader ...\MCX W72\boards\mcxw72w148evk\wireless_examples\bluetooth\loc_user_device AN14628_KW47_CCC_CS_Power_Profile_estimator tool_release.pdf id:NXP知识库 [开始日期：2021年5月27日] [截止日期：2021年6月27日]

Kinetis MCX Wxx (KW47 & MCX W72) Power Profile Tools for Bluetooth Localization This page is dedicated to the Kinetis KW47 and MCX W72 Power Profile Tool for Localization (CCC CS). It will help you to estimate the power consumption in your application (Automotive & IIoT]) and evaluate the battery life time of your solution. This page contains a dedicated power profile tool for: Localisation application (CCC CS) for Automotive & IIoT Automotive : 2 automotive applications example are available in the KW47 SDK: ...\kw47b41zevk\wireless_examples\bluetooth\digital_key_car_anchor_cs ...\kw47b41zevk\wireless_examples\bluetooth\digital_key_device_cs IIoT 2 IIoT applications example are available in the MCX W72 SDK: ...\MCX W72\boards\mcxw72w148evk\wireless_examples\bluetooth\loc_reader ...\MCX W72\boards\mcxw72w148evk\wireless_examples\bluetooth\loc_user_device AN14628_KW47_CCC_CS_Power_Profile_estimator tool_release.pdf id:NXP-Knowledge-Base [start:May 27 2021] [end:June 27 2021]

Kinetis MCX Wxx(KW47およびMCX W72)Bluetoothローカライゼーション用パワープロファイルツール このページはKinetis KW47およびMCX W72 Power Profile Tool for Localization (CCC CS)に特化しています。 これにより、あなたの用途(オートモーティブおよび工業電気)での消費電力を推定し、ソリューションのバッテリー寿命を評価するのに役立ちます。 このページには、以下の用途に特化した電源プロファイルツールが含まれています。 オートモーティブ&IIoT向けのローカリゼーションアプリケーション(CCC CS) オートモーティブ : KW47 SDKには2つの自動車アプリケーションの例があります: ...\kw47b41zevk\wireless_examples\bluetooth\digital_key_car_anchor_cs ...\kw47b41zevk\wireless_examples\bluetooth\digital_key_device_cs IIoT MCX W72 SDKには2つのIIoTアプリケーション例があります: ...\MCX W72\boards\mcxw72w148evk\wireless_examples\bluetooth\loc_reader ...\MCX W72\boards\mcxw72w148evk\wireless_examples\bluetooth\loc_user_device AN14628_KW47_CCC_CS_Power_Profile_estimator tool_release.pdf id:NXPナレッジベース [開始日: 2021年5月27日] [終了日：2021年6月27日]

NXPのセキュリティ ～まとめページ～ (日本語ブログ) NXPのセキュリティ概要 と 本ページの目的   近年、IoTデバイスやエッジ機器の普及に伴い、セキュリティ要件はますます高度かつ複雑になっています。NXPでは、プロセッサ、セキュアエレメント、ソフトウェア/ツール、関連ドキュメントを含む総合的なセキュリティ・ソリューションを提供しており、開発者が設計段階からセキュアなシステムを構築できる環境を整えています。 本まとめページでは、NXPのセキュリティ関連情報を一つに集約し、必要な情報に素早くアクセスできるように整理しています。記事は、NXPデバイスの基礎知識から実装ハンズオンまで幅広くカバーしており、これからNXP製品を用いてセキュア設計を進める方に最適な構成となっています。 Tech Blog記事一覧（リンクと概要） ◆入門・導入事例◆ ポイント 記事 概要 JC-STAR概説とNXPの製品 日本におけるセキュリティ要件適合評価及びラベリング制度（JC-STAR）の開始と、セキュリティ機能を支えるNXP製品 (日本語ブログ) JC-STARで議論されているセキュリティ要件の概要を紹介。NXP製品がどのように要件に対応しているかを体系的に解説。セキュリティ設計の全体像を理解するための入門記事。 ユースケース例 製品・企業価値の向上にもつながる組み込み製品におけるセキュリティのユースケース例 (日本語ブログ) 組み込み製品におけるセキュリティの重要性を、ユースケースを例に脅威・インパクト、対策の観点からわかりやすく、簡潔に解説。 ハードウェア・セキュリティのメリット セキュリティ対応の容易化・工数削減に貢献するNXPのハードウェア・セキュリティ・ソリューション (日本語ブログ) NXPのハードウェア・セキュリティ（暗号アクセラレータ内蔵MCU/MPU、EdgeLock®セキュア・エンクレーブ内蔵MCU/MPU、セキュア・エレメント/オーセンティケータ、EdgeLock 2GO：セキュア・プロビジョニング・サービス）を活用すると何が良いのか？またそれぞれの特徴を解説。 NXP製セキュリティ機能搭載製品を選択するメリット (日本語ブログ) ◆テーマ別・実践コーナー◆　「重要なセキュリティ技術の実装」 セキュアブート テーマ 分類 記事 セキュアブート (i.MX) 解説 i.MX 93プロセッサ: セキュアブートの署名と認証の仕組みを解説 (日本語ブログ) i.MX 93 のセキュアブート構造を詳細解説。署名・検証の流れを図解ベースで理解できる内容。 実践 i.MX 93プロセッサ: セキュアブートの実装方法 - 実践編 (日本語ブログ) 上記「i.MX93の署名と認証の仕組み」を踏まえて、実際のハンズオン手順を解説。開発者が実際に動かしながら理解できる実践的な内容。 解説 実践 i.MX 95 SPSDK によるセキュアブート (日本語ブログ) i.MX 95を用いたセキュアブートの解説と実装方法をハンズオン形式で解説。開発者が実際に動かしながら理解できる実践的な内容。 セキュアブート (i.MX RT) 解説 実践 NXP® MIMXRT1060-EVKCで始めるZephyr®と MCUbootによるセキュアブート (アイティアクセス株式会社) NXPの高性能マイコン評価ボード「MIMXRT1060-EVKC」を例に、Zephyrとセキュアブートローダ「MCUboot」を組み合わせた実践的な開発手順を紹介しています。実機を用いたビルドから書き込み、ファームウェア更新までの流れを通じて、Zephyrを用いたセキュアな組込みシステム開発の具体像を理解できます。 セキュア・エレメント テーマ 分類 記事 セキュア・エレメントを使うための準備 解説 ＆ 実践 セキュアエレメントSE05xの使用方法 : Raspberry PiでのPlug and Trust Middlewareのセットアップ(日本語ブログ) セキュアエレメントSE05xの使用方法 : FRDM-IMX93開発ボード上でのPlug and Trust Middlewareのセットアップ(日本語ブログ) NXPのセキュア・エレメントSE05xには、Plug and Trust Middlewareというミドルウェアが提供されています。SE05xを使用するための専用APIに加えて、OpenSSLやmbed-TLSといった広く使用されているライブラリに対するプラグインも含まれています。Plug and Trust Middlewareのセットアップを、Raspberry PiとFRDM-IMX93(i.MX 93向け開発ボード) 向けに行う手順を紹介。 OpenSSL 実践 セキュアエレメントSE05xの使用方法 : OpenSSL経由でのSE050の使用(日本語ブログ) セキュア・エレメント(SE05x) と OpenSSL を連携させた実践的な使い方を解説 Azure IoT Hubへの接続 実践 セキュアエレメントSE05xの使用方法 : Eclipse Mosquitto clientを使用したAzure IoT Hubへの接続(日本語ブログ) Eclipse Mosquitto clientを使用したAzure IoT Hubへの接続方法を紹介します。   鍵管理 テーマ 分類 記事 SoC内のセキュリティエンジンを用いた鍵管理 解説 ＆ 実践 i.MX 93のEdgeLock® Secure Enclave(ELE)の使用方法 : PKCS#11経由での暗号鍵の保存と使用 (日本語ブログ) i.MX 93内蔵のEdgeLock® Secure Enclave(ELE)の暗号アクセラレータおよび鍵管理の機能をPKCS#11経由で使用する方法について解説します。 Secure Provisioning Tool  ~ NXP MCU向け セキュリティ機能を使用するためのツール ~  Keita_Nagashima_0-1782703328411.png Secure Provisioning Tool は、MCUXpresso for VSCや、MCUXpresso IDE にて開発評価済みのアプリケーションに対して、製品リリースに向けたイメージのセキュリティー対応や書き込みなどの作業を行うためのMCU向けツールです。セキュア・ブート、セキュア・アップデート、デバッグ認証、デバイス認識などを行えます。 テーマ 分類 記事 Secure Provisioning Tool 解説 実践 Secure Provisioning Tool のインストール方法、使い方 (株式会社マクニカ) Secure Provisioning Tool の便利機能紹介 (株式会社マクニカ) Secure Provisioning Tool（以降、SPT と略します）と呼ばれるツールの使い方を分かりやすく紹介しています。 ◆基礎技術・学習コーナー◆　 カテゴリ 記事 概要 用語解説 半導体ハードウェア・セキュリティでよく耳にする機能について解説 (セキュアエレメント、セキュアエンクレーブ、TPM、HSM、TEE、TrustZoneなど) (日本語ブログ) セキュアエレメント、セキュアエンクレーブ、TPM、HSM、TEE、TrustZoneなどについて、機能の役割、分類、それと概要を紹介します。 さいごに NXPのセキュリティ対応製品は、多様なユースケースの要件に対応できる柔軟性と拡張性を備えています。本まとめページを活用することで、必要な情報に素早くアクセスし、製品選定から実装までスムーズに進めることを期待します。新しい記事も随時追加予定ですので、最新情報をチェックいただければ幸いです。 セキュリティに関連するコンテンツの要望や改善点などございましたら、以下よりお気軽にお問い合わせください。 NXPジャパン 技術ブログ(日本語) コンテンツ要望・改善アンケート – フォーム​に記入する =========================​​ お問い合わせの際には「NXPへの技術質問 - 問い合わせ方法 (日本語ブログ)」もご活用ください。​ （既に弊社NXP代理店、もしくはNXPとお付き合いのある方は、直接担当者へご質問いただいてもかまいません。） 近年、IoTデバイスやエッジ機器の普及に伴い、セキュリティ要件はますます高度かつ複雑になっています。NXPでは、プロセッサ、セキュアエレメント、ソフトウェア/ツール、関連ドキュメントを含む総合的なセキュリティ・ソリューションを提供しており、開発者が設計段階からセキュアなシステムを構築できる環境を整えています。 本まとめページでは、NXPのセキュリティ関連情報を一つに集約し、必要な情報に素早くアクセスできるように整理しています。記事は、NXPデバイスの基礎知識から実装ハンズオンまで幅広くカバーしており、これからNXP製品を用いてセキュア設計を進める方に最適な構成となっています。 Security Technology Focus 日本語ブログ

NXP Security - Summary Page (Japanese blog) NXP Security Overview and the Purpose of This Page   In recent years, with the spread of IoT devices and edge equipment, security requirements have become increasingly sophisticated and complex. NXP provides comprehensive security solutions including processors, secure elements, software/tools, and related documentation, creating an environment in which developers can build secure systems from the design stage . This summary page brings together all of NXP's security-related information in one place , organized for quick access to the information you need. The articles cover a wide range of topics, from basic knowledge of NXP devices to hands-on implementation exercises, making it ideal for anyone planning to use NXP products to design secure systems. Tech Blog Article List (Links and Summary) ◆Introduction and Case Studies◆ point article overview JC-STAR Overview and NXP Products The launch of the Japan Security Requirements Conformity Assessment and Labeling System (JC-STAR) in Japan and NXP products that support security functions (Japanese blog) This article provides an overview of the security requirements discussed in JC-STAR. It systematically explains how NXP products meet the requirements. It is an introductory article to help you understand the overall picture of security design. Use Case Example Security use cases for embedded products that can improve product and corporate value (Japanese blog) The importance of security in embedded products is explained in an easy-to-understand and concise manner from the perspectives of threats, impacts, and countermeasures, using use cases as examples. The Benefits of Hardware Security NXP's hardware security solutions simplify security implementation and reduce man-hours (Japanese blog) What are the benefits of using NXP's hardware security (MCU/MPU with built-in cryptographic accelerator, MCU/MPU with built-in EdgeLock ® Secure Enclave, Secure Element/Authenticator, EdgeLock 2GO: Secure Provisioning Service)? We also explain the features of each. The benefits of choosing products with NXP security features (Japanese blog) ◆Theme-specific/Practical Corner◆ "Implementation of Important Security Technologies" Secure Boot theme classification article Secure Boot (i.MX) Commentary i.MX 93 Processor: Explaining Secure Boot Signing and Authentication A detailed explanation of the i.MX 93 secure boot structure. The signing and verification process is explained with diagrams. Practice i.MX 93 Processor: How to Implement Secure Boot - Practical Guide (Japanese blog) Based on the above explanation of "i.MX93 signing and authentication mechanisms," this section explains the actual hands-on procedure. It's practical content that developers can understand by actually running the code. Explanation and Practice Secure Boot with i.MX 95 SPSDK (Japanese Blog) This guide provides a hands-on explanation of secure boot using i.MX 95 and how to implement it. It's practical and allows developers to understand the concepts by actually running the code. Secure Boot (i.MX RT) Explanation and Practice Getting Started with Zephyr ® and Secure Boot using MCUboot on NXP ® MIMXRT1060-EVKC (IT Access Co., Ltd.) This guide uses NXP's high-performance microcontroller evaluation board "MIMXRT1060-EVKC" as an example to demonstrate practical development procedures combining Zephyr and the secure bootloader "MCUboot." Through the entire process, from building and programming to firmware updates using actual hardware, you can gain a concrete understanding of secure embedded system development using Zephyr. Secure element theme classification article Preparing to use the secure element Explanation & Practice How to use Secure Element SE05x: Setting up Plug and Trust Middleware on Raspberry Pi (Japanese blog) How to use Secure Element SE05x: Setting up Plug and Trust Middleware on the FRDM-IMX93 development board (Japanese blog) NXP's Secure Element SE05x comes with middleware called Plug and Trust Middleware. In addition to a dedicated API for using the SE05x, it also includes plugins for widely used libraries such as OpenSSL and mbed-TLS. This document describes the procedure for setting up Plug and Trust Middleware for Raspberry Pi and FRDM-IMX93 (a development board for i.MX 93). OpenSSL Practice How to use SecureElement SE05x: Using SE050 via OpenSSL (Japanese blog) This article explains practical ways to use Secure Element (SE05x) in conjunction with OpenSSL. Connecting to Azure IoT Hub Practice How to use Secure Element SE05x: Connecting to Azure IoT Hub using Eclipse Mosquitto client (Japanese blog) This guide explains how to connect to Azure IoT Hub using the Eclipse Mosquitto client.   key management theme classification article Key management using the security engine within the SoC Explanation & Practice How to use the EdgeLock® Secure Enclave (ELE) on i.MX 93: Storing and using encryption keys via PKCS#11 (Japanese blog) This document explains how to use the cryptographic accelerator and key management functions of the i.MX 93's built-in EdgeLock® Secure Enclave (ELE) via PKCS#11. Secure Provisioning Tool ~ A tool for using security features for NXP MCUs ~ Keita_Nagashima_0-1782703328411.png The Secure Provisioning Tool is an MCU-specific tool for performing tasks such as securing and writing images for product releases of applications developed and evaluated using MCUXpresso for VSC or MCUXpresso IDE. It enables secure boot, secure updates, debug authentication, device recognition, and more. theme classification article Secure Provisioning Tool Explanation Practice How to install and use the Secure Provisioning Tool (Macnica, Inc.) Introduction to the useful features of the Secure Provisioning Tool (Macnica, Inc.) This guide provides a clear explanation of how to use a tool called the Secure Provisioning Tool (hereinafter abbreviated as SPT). ◆Basic skills and learning corner◆ category article overview Glossary Explaining Common Semiconductor Hardware Security Features (Secure Element, Secure Enclave, TPM, HSM, TEE, TrustZone, etc.) (Japanese blog) This article introduces the functional roles, classifications, and overviews of secure elements, secure enclaves, TPMs, HSMs, TEEs, TrustZones, etc. Finally NXP's security-enabled products are flexible and scalable to meet the requirements of a wide variety of use cases. We hope that by using this summary page, you will be able to quickly access the information you need and smoothly proceed from product selection to implementation. New articles will be added from time to time, so please check back for the latest information. If you have any requests or suggestions for improvements regarding security-related content, please feel free to contact us using the information below. NXP Japan Technical Blog (Japanese) Content Request/Improvement Survey – Fill out the form ============================ When making inquiries, please also use the " 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.) In recent years, with the spread of IoT devices and edge equipment, security requirements have become increasingly sophisticated and complex. NXP provides comprehensive security solutions including processors, secure elements, software/tools, and related documentation, creating an environment in which developers can build secure systems from the design stage . This summary page brings together all of NXP's security-related information in one place , organized for quick access to the information you need. The articles cover a wide range of topics, from basic knowledge of NXP devices to hands-on implementation exercises, making it ideal for anyone planning to use NXP products to design secure systems. Security Technology Focus Japanese Blog

NXP Security - 摘要页面（日语博客） NXP 安全概述及本页目的   近年来，随着物联网设备和边缘设备的普及，安全需求变得日益复杂。恩智浦提供全面的安全解决方案，包括处理器、安全元件、软件/工具及相关文档，为开发人员从设计阶段构建安全系统创造了有利环境。 本汇总页面将恩智浦所有安全相关信息集中于一处，方便您快速查找所需信息。文章涵盖广泛的主题，从恩智浦器件的基础知识到实践操作练习，是计划使用恩智浦产品设计安全系统的人员的理想之选。 技术博客文章列表（链接和摘要） ◆引言和案例研究◆ 要点 文章 概述 JC-STAR 概述和 NXP 产品 日本安全要求合格评定和标签系统（JC-STAR）在日本的推出以及恩智浦支持安全功能的产品（日本博客） 本文概述了JC-STAR中讨论的安全要求，并系统地阐述了恩智浦产品如何满足这些要求。这是一篇入门文章，旨在帮助您了解安全设计的整体框架。 用例示例 嵌入式产品的安全应用案例，可提升产品和企业价值（日文博客） 本文从威胁、影响和应对措施的角度，以通俗易懂的方式，通过用例举例说明了嵌入式产品安全性的重要性。 硬件安全的优势 恩智浦的硬件安全解决方案简化了安全实施，并减少了人工工时（日本博客） 使用恩智浦半导体的硬件安全解决方案（内置加密加速器的MCU/MPU、内置EdgeLock ®安全隔离区的MCU/MPU、安全元件/认证器、EdgeLock 2GO：安全配置服务）有哪些优势？我们还将解释每项解决方案的特性。 选择具有恩智浦安全功能的产品的好处（日文博客） ◆专题/实用专栏◆ “重要安全技术的实施” 安全启动 主题 分类 文章 安全启动 （i.MX） 评论 i.MX 93 处理器：安全启动签名和身份验证详解 本文详细解释了 i.MX 93 安全启动结构，并用图表说明了签名和验证过程。 实践 i.MX 93 处理器：如何实现安全启动 - 实用指南（日语博客） 基于以上对“i.MX93签名和认证机制”的解释，本节将介绍实际操作步骤。这些实用内容可以通过实际运行代码来理解。 讲解与练习 使用 i.MX 95 SPSDK 实现安全启动（日本博客） 本指南通过实际操作讲解了如何使用 i.MX 95 实现安全启动。它注重实践，使开发人员能够通过实际运行代码来理解相关概念。 安全启动 （i.MX RT） 讲解与练习 在 NXP ® MIMXRT1060-EVKC (IT Access Co., Ltd.) 上使用 MCUboot 实现 Zephyr ®和安全启动入门 本指南以恩智浦半导体的高性能微控制器评估板“MIMXRT1060-EVKC”为例，演示结合Zephyr和安全引导加载程序“MCUboot”的实际开发流程。通过从构建、编程到使用实际硬件进行固件更新的整个过程，您可以深入了解如何使用Zephyr进行安全嵌入式系统开发。 安全元件 主题 分类 文章 准备使用安全元件 解释 & 实践 如何使用安全元件 SE05x：在树莓派上设置即插即用中间件（日文博客） 如何使用安全元件 SE05x：在 FRDM-IMX93 开发板上设置即插即用中间件（日文博客） NXP 的安全元件 SE05x 附带名为 Plug and Trust Middleware 的中间件。除了用于 SE05x 的专用 API 外，它还包含 OpenSSL 和 mbed-TLS 等常用库的插件。本文档介绍了在 Raspberry Pi 和 FRDM-IMX93（i.MX 93 的开发板）上设置 Plug and Trust Middleware 的步骤。 OpenSSL 实践 如何使用 SecureElement SE05x：通过 OpenSSL 使用 SE050（日语博客） 本文介绍了将安全元件 (SE05x) 与 OpenSSL 结合使用的实用方法。 连接到 Azure IoT 中心 实践 如何使用安全元件 SE05x：使用 Eclipse Mosquitto 客户端连接到 Azure IoT 中心（日语博客） 本指南说明如何使用 Eclipse Mosquitto 客户端连接到 Azure IoT 中心。   关键管理 主题 分类 文章 利用SoC内部的安全引擎进行密钥管理。 解释 & 实践 如何在 i.MX 93 上使用 EdgeLock® 安全隔离区 (ELE)：通过 PKCS#11 存储和使用加密密钥（日语博客） 本文档解释了如何通过 PKCS#11 使用 i.MX 93 内置 EdgeLock® 安全隔离区 (ELE) 的加密加速器和密钥管理功能。 安全配置工具 ~用于启用NXP MCU安全功能的工具~ Keita_Nagashima_0-1782703328411.png 安全配置工具是一款专为 MCU 设计的工具，用于执行诸如保护和写入使用 MCUXpresso for VSC 或 MCUXpresso IDE 开发和评估的应用程序的产品版本镜像等任务。它支持安全启动、安全更新、调试身份验证、设备识别等功能。 主题 分类 文章 安全配置工具 解释 实践 如何安装和使用安全配置工具（Macnica公司） 安全配置工具（Macnica公司）实用功能简介 本指南清晰地解释了如何使用名为安全配置工具（以下简称 SPT）的工具。 ◆基本技能和学习角◆ 类别 文章 概述 词汇表 解释常见的半导体硬件安全特性（安全元件、安全隔离区、TPM、HSM、TEE、TrustZone 等）（日语博客） 本文介绍了安全元件、安全飞地、TPM、HSM、TEE、TrustZones 等的功能角色、分类和概述。 最后 恩智浦的安全产品灵活且可扩展，能够满足各种应用场景的需求。我们希望通过本概要页面，您能够快速获取所需信息，并顺利完成从产品选型到实施的整个流程。我们将不定期更新文章，敬请关注最新资讯。 如果您对安全相关内容有任何改进要求或建议，请随时使用以下信息与我们联系。 NXP日本技术博客（日语）内容请求/改进调查——请填写表格 ============================ 如有疑问，请同时参考“ NXP 技术 问题 咨询 - 如何 联系我们 （ 日语博客 ） ”。 （如果您已经是 恩智浦的 分销商或 与 恩智浦 有业务往来 ，您可以直接咨询负责人。） 近年来，随着物联网设备和边缘设备的普及，安全需求变得日益复杂。恩智浦提供全面的安全解决方案，包括处理器、安全元件、软件/工具及相关文档，为开发人员从设计阶段构建安全系统创造了有利环境。 本汇总页面将恩智浦所有安全相关信息集中于一处，方便您快速查找所需信息。文章涵盖广泛的主题，从恩智浦器件的基础知识到实践操作练习，是计划使用恩智浦产品设计安全系统的人员的理想之选。 安全 技术聚焦 日本博客

NXP「電源」まとめページ (日本語ブログ) NXPが電源製品を持っているってご存じでしたか？ 電源製品を使用するメリットや、電源の基礎に関する記事をこちらのサイトにまとめましたので、是非ブックマークを！ KeitaNaga_1-1744593225378.png ★マイコン/プロセッサ向け電源をお探しの方はこちら★ ■NXP電源製品を使用するメリット ・NXPのパワーマネージメントIC(PMIC)をi.MXアプリケーション・プロセッサ(MPU)向けに使用するメリット  ・NXPのパワーマネージメントIC(PMIC/SBC)がなぜ車載向けマイコン(S32シリーズ)に最適なのか？ ■i.MX 8/i.MX 9用の電源をお探しの方は、まずここからクリック！　 i.MX 対象PMIC PMICの紹介と 簡単使用例 より詳しい説明 i.MX 8M Plus PCA9450C PCA9450C紹介 Powering Guide AN14246 i.MX 8ULP PCA9460 PCA9460紹介 Powering Guide AN14468 i.MX 93 PCA9451A PCA9451A紹介 Powering Guide AN14413 i.MX 95 PF09 + PF53 Coming soon Coming soon ★初心者におすすめ ～電源の基礎講座シリーズ～★ ■「電源ICの選び方 - 3ステップ」 ・どのように電源ICを選べばいいのか？ [第１回]：Step 1 - 候補となる電源ICの選定 ・どのように電源ICを選べばいいのか？ [第２回]：Step 2 - 実装面積の確認 ・どのように電源ICを選べばいいのか？ [第３回]：Step 3 - 熱設計の確認 ■「電源とは？- 最初の一歩」 ・第一回　リニア・レギュレータ  ・第二回　スイッチング・レギュレータ ・第三回　ボルテージ・トラッカ   ・第四回　レシオメトリック測定  ・第五回　PMICとSBC 今後もコンテンツを拡充予定です！ ■関連情報 ・パワー・マネジメントIC (PMIC) とシステムベーシス・チップ (SBC) ・パワー・マネジメント集積回路 (PMIC) ・システム・ベース・チップ (SBC) 電源に関連するコンテンツの要望や改善点などございましたら、以下よりお気軽にお問い合わせください。 NXPジャパン 技術ブログ(日本語) コンテンツ要望・改善アンケート – フォーム​に記入する ========================= 本投稿の「Comment」欄にコメントをいただいても、現在返信に対応しておりません。 お手数をおかけしますが、お問い合わせの際には、NXP代理店、もしくはNXPまでお問い合わせください。 NXPが電源製品を持っているってご存じでしたか？ 我々の電源製品のメリットや、電源の基礎に関する記事をこちらのサイトにまとめましたので、是非ブックマークを！ i.MX Processors introduction PMIC 日本語ブログ

NXP“电源”概览页面（日文博客） 你知道恩智浦半导体也有电源产品吗？ 本站已汇总了有关使用电源产品的好处和电源基础知识的文章，请务必收藏本站！ KeitaNaga_1-1744593225378.png ★如果您正在寻找微控制器/处理器的电源，请点击这里★ 使用恩智浦电源产品的优势 ・使用恩智浦半导体（NXP）电源管理集成电路（PMIC）开发i.MX应用处理器（MPU）的优势 ・为什么恩智浦的电源管理IC（PMIC/SBC）是汽车微控制器（S32系列）的理想选择？ ■如果您正在寻找适用于 i.MX 8/i.MX 9 的电源，请先点击这里！ i.MX 目标PMIC PMIC简介 简单用法示例 更详细的解释 i.MX 8M Plus PCA9450C PCA9450C简介 电源指南 AN14246 i.MX 8ULP PCA9460 PCA9460简介 电源指南 AN14468 i.MX 93 PCA9451A PCA9451A 简介 电源指南 AN14413 i.MX 95 PF09 + PF53 即将推出 即将推出 ★推荐给初学者~电源基础课程系列~★ ■ “如何选择电源IC - 3个步骤” 如何选择电源IC？【第一部分】 ：步骤1 - 选择电源IC 如何选择电源IC？【第二部分】 ：步骤2 - 检查安装区域 如何选择电源IC？【第3部分】 ：步骤3 - 检查散热设计 ■ “什么是电源？——第一步” ・第一课：线性稳压器 ・第二部分：开关稳压器 ・第三电压跟踪器 ・第四次比率测量 ・第五届PMIC和SBC 我们计划继续拓展内容！ ■ 相关信息 电源管理集成电路（PMIC）和系统基础芯片（SBC） ・电源管理集成电路（PMIC） ・系统基础芯片（SBC） 如果您对电力相关内容有任何改进要求或建议，请随时使用以下信息与我们联系。 NXP日本技术博客（日语）内容请求/改进调查——请填写表格 ========================= 我们目前无法回复此帖子“评论”部分的评论。 由此给您带来的不便，我们深表歉意。如有任何疑问，请联系您的恩智浦经销商或直接联系恩智浦公司。 你知道恩智浦半导体也有电源产品吗？ 本站已汇总了有关我们电源产品优势和电源基础知识的文章，请务必收藏！ i.MX处理器 介绍 采购和市场营销中心 日本博客