S32K312 安全启动和编程闪存 附件中的 CMM 文件是一个脚本，它将 FBL 和应用程序写入 S32K312 MCU，然后激活 SecureBoot、SecureDebug 和配置锁定。 我们希望对运行此 CMM 时出现的 HardFault 问题进行审查和改进。 如屏幕截图所示，之前在执行“Go”时，导入 FBL 和应用程序后发生 HardFault，JTAG 时钟始终设置为 5 MHz。 作为一项更改，我们在导入应用程序文件后将 SYStem.JtagClock 设置为 1 MHz。通过这一改变，在运行 CMM 时，“Go”步骤很少发生硬故障，因此我们得出结论，降低 JTAG 时钟速度是一种有效的方法。但是，当应用修改后的 CMM 时，在导入 FBL 和 App 后，偶尔会在“Go”时出现“被 vectbl 停止”错误。 请您检查一下 CMM，确保其整体运行稳定。同时，我们也想了解一下如何改进它，以彻底消除“被 vectbl 停止”的错误。 原始三坐标测量机：GN7_PE_MAIN_G_SECURE_260412.cmm 修改后的 CMM（JTAG 时钟已更改为 1 MHz）：GN7_PE_MAIN_G_SECURE_260412_0714RE.cmm 此外，我们希望在启用安全启动后导入不同的 FBL。在启用安全启动的情况下，是否可以导入不同的 FBL？如果可以的话，我们希望您能提供一份指南。 Re: S32K312 Secureboot and Program Flash 嗨@jeongwoo 我看到的主要问题是： 这意味着：加载粉色文件并重置设备。After this RESET, SBAF 应该会安装 HSE 固件。但关键是——这个操作大约需要 1 秒钟。但是，在 0.1 秒后，您将再次重置 MCU，并且您将立即通过 fbl 对 0x40_0000 处的粉色文件进行重新编程。至少将等待时间增加到 1.3 秒。否则，SBAF 会尝试安装 HSE 固件，而您同时会尝试重新编程 fbl。 此致， Lukas Re: S32K312 Secureboot and Program Flash 您好，谢谢您的回复。 关于目前在添加 HSE 后延迟时间设置为 0.1 秒的部分，即使将时间设置得更短，写入控制器的程序功能也没有任何问题。我想请问是否真的有必要将延迟时间增加到 1 秒。

Wi-Fi芯片组MCU控制 大家好， 我正在寻找一些具有 AP+STA 功能的 Wi-Fi 模块。例如，我找到了一些来自恩智浦半导体（NXP）、微芯科技（Microchip）和英飞凌科技（Infineon）的模块。然而，大多数模块仅通过 PCIe 和高级操作系统启用 wifi 接口。 不过，我找到了一套来自英飞凌的名为 AIROC CYW55X（系列）的 MCU+Wifi 模块。 您在集成和控制这类模块方面有经验吗？如果可以的话，您能否分享一下您之前使用过并成功与外部MCU集成的不同模块？我的目的不是将数据卸载到微控制器，而只是为了控制例如网状网络和接入点功能。 我想使用 MCU（例如 STM）对一些基本的 AI 模型进行一些推理，同时控制 wifi 模块。 谢谢大家 Re: Wi-Fi Chipset MCU Control 亲爱的@ajihu ， 根据您的描述，特别是对于运行基本 AI 模型而言，RW61X（RW610/RW611/RW612）可能已经足以满足您的应用需求。 RW61X 集成了： - MCU - 无线上网 - 低功耗蓝牙 - （RW612 也支持 802.15.4 / Thread） 对于基本的 AI 推理工作负载，RW61X 可以在单个设备上运行应用程序和无线连接协议栈，从而可能无需额外的 MCU。 但是，有必要澄清一下您所说的“网状物”是什么意思。 RW61X 不支持： - IEEE 802.11s 网状网络 - EasyMesh RW61X 支持： - 事情 - 线 - Zigbee（通过 802.15.4 生态系统） - STA + uAP 并发模式 [注意] 如果需要额外的AI处理性能，您可以考虑： - i.MX RT700 + IW61X - i.MX RT1170 + IW61X - i.MX RT1180 + IW61X 请注意，这些解决方案也不支持： - IEEE 802.11s 网状网络 - EasyMesh 他们支持： - 事情 - 线 Zigbee - STA + uAP 并发模式 谢谢您！ 顺祝商祺！ 卫东

S32N55: How to build a blob image for fast wake-up boot. Hello Team, As we know, the S32N55 supports Fast Wake-up Boot. I tried building a blob image using the same format as Full Wake-up Boot, but the boot process failed. Could you please guide me on how to correctly build a blob image for Fast Wake-up Boot? Thank you! Best regards, Tangsheng. FSS_FW Priority: MEDIUM Re: S32N55: How to build a blob image for fast wake-up boot. Hello @Tangsheng_Zhou, The team has picked up the case and will provide an answer as soon as possible.  Best regards, Radu  Re: S32N55: How to build a blob image for fast wake-up boot. Hello @RaduBraga  I noticed that this ticket has been closed. Is there any update on the progress?   Best regards, Tangsheng. Re: S32N55: How to build a blob image for fast wake-up boot. Hello @Tangsheng_Zhou , I took over the case and will provide a response as soon as possible.   Best regards, Paul Re: S32N55: How to build a blob image for fast wake-up boot. Hello @Tangsheng_Zhou , If you are supporting a Direct Customer, please provide: BSSM Contract: Yes / No Customer Company*: Project Name*: Customer Contact Point* (Name & Email): Software & Hardware Information: SW Package Info*: HW* (Board/Chipset/Platform): SW Version*: *required I am still working with the development team for this case Best regards, Paul Re: S32N55: How to build a blob image for fast wake-up boot. Hello @Tangsheng_Zhou , Thank you for these details, I am working on this case and will provide an answer as soon as possible! Best regards, Paul Re: S32N55: How to build a blob image for fast wake-up boot. Hello @PaulB0bes  This case is not tied to any specific customer or project. However, I believe customers may encounter similar questions in the future, which is why I raised this request.   Best regards, Tangsheng. Re: S32N55: How to build a blob image for fast wake-up boot. Hello @PaulB0bes  Below are the detailed steps for testing.   1. built a small FSS image within AOSRAM memory region(reserved the IVT header), which only have a while loop in main.c 2. build the FSS Firmware image,  do I need to fill the FRB Threshold Reg? If so, how to fill it or any special thing need to be considered. 3. built the IVT blob image in IVT tool, with start address from 0x24800000 4. write the IVT blob image into flash at 0xD00000. 5. before the system enter sleep, copy the IVT blob image into AOSRAM, and configure the WKPU mode for FSS_WKUP0 as fast wake-up mode. 5. wakeup the system image via FSS_WAKUP0. The FSS could not reach the while(1) loop. It appears that a reset event was triggered during the wake-up process instead of a fast wake-up.   Thanks for your support!   Best regards, Tangsheng. Re: S32N55: How to build a blob image for fast wake-up boot. Hello @Tangsheng_Zhou , It would help if you could share the exact steps you followed when you tried to build the blob image. I think it would be easier for us to identify the issue that way.   Best regards, Paul Re: S32N55: How to build a blob image for fast wake-up boot. Hi @Tangsheng_Zhou , FRB is for TCM memory (ITCM +DTCM). In theory we have 2 cases 1: FAST wakeup Boot      for fast wakeup FRB is not needed, due to the fact that image boots from AON SRAM Memory. 2: FULL wakeup Boot      Can you tell me if you want to boot to ITCM? if yes FRB threshold 0 should be provided in FSS Image header, the address is 12 bit masked and address will be calculated as multiple of 8kb for FRB .       Hope this helps a little. Also could you provide me the IVT blob? Best regards, Paul

Top Generative AI Development Company in 2026 Apptunix  is a trusted generative AI development company delivering advanced generative AI solutions that help businesses automate processes and build intelligent digital products. The company develops AI-powered applications such as smart chatbots, AI assistants, recommendation engines, and content generation tools. With strong expertise in AI, mobile app development, and enterprise software, Apptunix helps startups and large organizations integrate generative AI into their digital strategies. Re: Top Generative AI Development Company in 2026 In 2026, finding the right team for your AI project is less about big promises and more about real capability. Many companies position themselves as leaders, but only a few truly stand out when it comes to delivering practical, business-focused solutions. When evaluating a Generative AI Development Company, the first thing to notice is how well they understand your use case. The best teams don’t just talk about models or tools—they focus on outcomes, efficiency, and how AI fits into your workflow. Strong portfolios, clear communication, and a problem-solving mindset are what separate top companies from the rest. Instead of chasing trends, they build solutions that actually work in real environments and continue improving over time. It’s also important to choose a company that thinks beyond development. The real value comes from long-term support, updates, and the ability to adapt as your needs grow. In the end, the “top” company isn’t the most popular one—it’s the one that understands your goals and helps you achieve them without unnecessary complexity. Re: Top Generative AI Development Company in 2026 Businesses adopting generative AI chatbot development gain a competitive edge through automation, personalization, and 24/7 engagement. Our AI development services focus on building intelligent, context-aware chatbots tailored for web and React Native app development environments. We leverage cutting-edge machine learning, prompt engineering, and conversational AI frameworks to create bots that understand user intent, improve customer journeys, and increase lead generation. Re: Top Generative AI Development Company in 2026 There’s no single “top” generative AI company in 2026-it depends on your use case. Large firms like Accenture or IBM are strong for enterprise-scale projects but can be costly and slower. Mid-sized AI specialists are better for custom LLM apps, RAG pipelines, and integrations. Agile teams often focus on faster execution and real deployments. I’ve seen companies like Tabdelta Solutions mentioned for building practical AI products and automation systems. Ultimately, choose based on expertise, speed, and ability to deliver production-ready solutions. Re: Top Generative AI Development Company in 2026 Great addition. Apptunix has built a solid track record, especially in mobile AI. For anyone evaluating vendors beyond this one, it helps to separate companies by their core orientation: some are mobile-first shops that have added Gen AI to their stack, while others have built their entire practice around AI from the ground up. One company worth adding to this thread is Maruti Techlabs. They've been in AI for 15+ years, with 100+ projects delivered. Their Gen AI work spans custom LLM development, RAG pipelines, AI agents, and enterprise automation. Clients include names like Red Bull and Harvard Business Review. Clutch and GoodFirms both recognize them as a top AI firm. Depending on what you're building, whether it's an AI-powered product or an enterprise workflow layer, the right fit can vary quite a bit between these vendors. Re: Top Generative AI Development Company in 2026 Choosing the right AI partner depends on expertise, innovation, and the ability to deliver business-focused solutions. Nimble AppGenie is a trusted Generative AI development company that helps startups and enterprises build intelligent applications powered by Generative AI, LLMs, AI agents, and automation technologies. Our team develops custom AI solutions that enhance productivity, streamline business operations, improve customer experiences, and support digital transformation. With a focus on scalability, security, and real-world business outcomes, Nimble AppGenie enables organizations to leverage the full potential of AI across industries, including fintech, healthcare, eCommerce, logistics, and education.

在 i.MX8 QuadMax 上使用 AAOS 15 启用多用户功能，并设置多显示器 各位同事好， 我们 在 i.MX8 QuadMax 平台 上使用 Android Automotive OS( AAOS) 15 。 我们目前的硬件配置包括三个显示器： 主中央显示屏（驾驶员/中央显示屏） 乘客显示屏 仪表盘显示 我们 希望 在 该 平台 上 启用 和 验证 Android 多用户 功能 ， 包括 支持 用户 切换、 访客 用户 和 用户特定的 应用 程序/设置 。 请问 您 能否 就 以下 问题 提供 指导 ： 在 i.MX8QM 上 启用 AAOS 15 的 多 用户 支持 需要 哪些 配置 ？ NXP 方面 是否 需要 对 电路板支持包 进行 任何 特定的 更改 ？ 必须 启用 哪些 框架 覆盖层、 功能 标志 或 系统 属性 ？ 任何指导或建议都将不胜感激。   谢谢！

S32K358 multi core data sharing Hello , I am trying to use shared memory in s32k358 multi core. I am following user define example,  When i try to assign some value in buzzer_state_shared_data_U32 ( currently only core 0 is accessing this memory), core 0 is hanging and swt resetting the controller. But when i flash the code in debug flash, its running properly. With power on reset, core 0 is hanging.  Why its running properly in when flashing and not running in power off and on. Re: S32K358 multi core data sharing Hello @Julián_AragónM , Thank you for your quick response, I check the startup files, SRAM Init is happening. I have attached my startup files and linker files. Please support me to resolve this issue Re: S32K358 multi core data sharing Hello @nirmal_masilamani, But when i flash the code in debug flash, its running properly. With power on reset, core 0 is hanging.  This is most likely caused by ECC RAM error. Usually, debuggers initialize the ECC on volatile memories, however, when powering on and off, debugger does not initialize RAM, and hardfault occurs when trying to access memory. This is usually done in the startup code, before main. The section should be also configured as non-cacheable. Regarding your second issue: but when i try to access it from timer ISR or OS task, core 0 going to hardfault. You can try to trace back your hardfault. Halt the core in the HardFault_Handler(), and find the SP value in the core registers: How To Debug A Fault Exception On ARM Cortex-M(V7M) MCU(S32K3XX). Best regards, Julián Re: S32K358 multi core data sharing Hello, When i access shared memory in main(), its working fine even in power off and on, but when i try to access it from timer ISR or OS task, core 0 going to hardfault. Please support me in this. Re: S32K358 multi core data sharing Hello @Julián_AragónM , Please support on this query. What i am missing here? Re: S32K358 multi core data sharing Hello @nirmal_masilamani, Are you able to access shared memory in main() after POR reset without debugger? Was the issue RAM initialization? but when i try to access it from timer ISR or OS task, core 0 going to hardfault. Were you able to identify the fault type as I mentioned in my previous reply? Have you also made sure the variable is placed in a non-cacheable area, or the cache is disabled? As suggestions: Keep volatile on core1Status and use __DMB()/__DSB() barriers on both the read (Core0) and write (Core1) sides. Your issue could also be caused by MPU configuration, if MPU_ENABLE is defined, please call the MPU config before any ISR or OS task starts executing. You can refer to the following links: Arm Cortex-M7 Devices Generic User Guide r1p2 & AN14715: S32K3XX Hardware Resource Isolation and Protection. Best regards, Julián Re: S32K358 multi core data sharing Hello @Julián_AragónM , Thank you for your response, Unfortunately, i was unable to continue on this, I will check your points.

HSE return "HSE_SRV_RSP_INVALID_PARAM" when request for HMAC verify job Hello Nxp team, I have use case to use HMAC verify job. After triggering the job crypto driver throw DET and the response from HSE is "HSE_SRV_RSP_INVALID_PARAM". I am not able to understand what wrong with my current configuration. could you please check attached config zip file?  Need support to resolve issue. Thanks, Aditya Re: HSE return "HSE_SRV_RSP_INVALID_PARAM" when request for HMAC verify job Hi @lukaszadrapa , Details: Device: S32K311 HSE FW: HSE_FW_S32K311_0_2_55_0 RTD: SW32K3_S32M27x_RTD_R21-11_6.0.0_QLP01 Thanks, Aditya Re: HSE return "HSE_SRV_RSP_INVALID_PARAM" when request for HMAC verify job Hi @WagdeoA  Could you confirm which device, which RTD and which HSE firmware version you have? Regards, Lukas Re: HSE return "HSE_SRV_RSP_INVALID_PARAM" when request for HMAC verify job Hi @WagdeoA  There’s no problem in your configuration. It works on my side. But one possible issue could be the length of tag (secondaryInputLength). This can be found in function Crypto_Ipw_HmacVerify: If redirection is disabled, it’s necessary to provide the length of tag in bits, not in bytes. Isn’t this the problem? Regards, Lukas Re: HSE return "HSE_SRV_RSP_INVALID_PARAM" when request for HMAC verify job Hi Lukas, Sorry for late reply. Yes, with length of tag in bits. It works at myside as well. Thank you! Best Regards, Aditya

S32N55：如何版本 blob 映像以实现快速唤醒启动。 你好，团队、 众所周知，S32N55 支持快速唤醒启动。 我尝试使用与完全唤醒启动相同的格式构建 blob 映像，但启动过程失败了。 你能否指导我如何正确版本 Fast Wake-up 启动的 blob 镜像？ 谢谢！ 顺祝商祺！ 唐生。 FSS_FW 优先级：中等 Re: S32N55: How to build a blob image for fast wake-up boot. 你好@唐生_周、 该小组已受理此案，并将尽快给出答复。 致以最崇高的敬意， Radu Re: S32N55: How to build a blob image for fast wake-up boot. 你好@RaduBraga 我注意到该票已被关闭。有没有最新进展？   顺祝商祺！ 唐生。 Re: S32N55: How to build a blob image for fast wake-up boot. 你好@Tangsheng_Zhou ， 我已经接手此案，并将尽快给予答复。   顺祝商祺！ 保罗 Re: S32N55: How to build a blob image for fast wake-up boot. 你好@Tangsheng_Zhou ， 如果您正在为直接客户提供支持，请提供以下信息： BSSM合同：是/否 客户公司*： 项目名称*： 客户联系人*（姓名和邮箱）： 软件和硬件信息： 软件软件包信息*： 硬件*（主板/芯片组/平台）： 软件版本*： *必需的 我仍在与开发团队合作处理此案例。 顺祝商祺！ 保罗 Re: S32N55: How to build a blob image for fast wake-up boot. 你好@PaulB0bes 此案与任何特定客户或项目无关。但是，我认为客户将来可能会遇到类似的问题，所以我提出了这个请求。   顺祝商祺！ 唐生。 Re: S32N55: How to build a blob image for fast wake-up boot. 你好@Tangsheng_Zhou ， 感谢您提供的详细信息，我正在处理此案，会尽快给您答复！ 顺祝商祺！ 保罗 Re: S32N55: How to build a blob image for fast wake-up boot. 你好@PaulB0bes 以下是详细的测试步骤。   1. 在 AOSRAM 内存区域内构建了一个小型 FSS 镜像（保留了 IVT 头部），该镜像的 main.c 文件中只有一个 while 循环。 2. 构建 FSS 固件镜像时，我需要填写 FRB 阈值寄存器吗？如果需要填写，则需要考虑如何填写或任何特殊事项。 3. 使用 IVT 工具构建 IVT blob 映像，起始地址为 0x24800000 4. 将 IVT blob 映像写入闪存的 0x D00000 地址。 5. 在系统进入睡眠状态之前，将 IVT blob 映像复制到 AOSRAM 中，并将 FSS_WKUP0 的 WKPU 模式配置为快速唤醒模式。 5. 通过 FSS_WAKUP0 唤醒系统映像。 FSS 无法到达 while(1) 环。看来在唤醒过程中触发了重置事件，而不是快速唤醒。   感谢您的支持！   顺祝商祺！ 唐生。 Re: S32N55: How to build a blob image for fast wake-up boot. 你好@Tangsheng_Zhou ， 如果您能分享一下您在尝试构建 blob 镜像时所遵循的具体步骤，那就太好了。我认为那样我们更容易找出问题所在。   顺祝商祺！ 保罗 Re: S32N55: How to build a blob image for fast wake-up boot. 嗨@Tangsheng_Zhou ， FRB 是 TCM 存储器（ITCM +DTCM）。 理论上我们有两种情况。 1：快速唤醒启动 由于镜像从 AON SRAM 内存启动，因此快速唤醒不需要 FRB。 2：完全唤醒启动 请问您是否要启动到 ITCM？如果是，则需要在 FSS 映像头中提供 FRB 阈值 0，地址采用 12 位掩码，FRB 地址将按 8kb 的倍数计算。 希望这能帮上一点忙。另外，您能否提供一下 IVT blob？ 顺祝商祺！ 保罗

imx93 lpddr4x 配置 JSL4BAG16 不稳定 各位专家好： 我有一个关于 JSL4BAG16 的 lpddr4x 配置的问题，配置后，它通过了“功能”测试，但有时会在“优化->Vref 进行 CA 优化”处失败，不是每次都失败，只是偶尔会失败。 当测试“vTSA ->CA eye”时，显示通过，但同时也显示了一些“错误日志”。 我有一个关于如何调整“Vref DQ 配置”和“Vref CA 配置”的问题？JSL4BAG16 的 Vref 值与“EVK 中使用的 Microns”不同，是否需要设置范围 0 或范围 1？ 据我所知，Vref DQ 是根据“眼图”测试结果进行配置的，但是眼图有“读取图”和“写入图”之分，我应该使用哪一个呢？ 我已附上 JSL4BAG 的数据表和“CA eye”测试日志及 mex 文件。     此致。 Re: imx93 lpddr4x config for JSL4BAG16 unstable 你好， LPDDR4X 是https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-93-Memory-Compatibility-Guide/ta-p/1725656的一部分 对于 Vref DQ 调谐，请使用 JSL4BAG16 的范围 1（默认值），并使用写入眼图，而不是读取眼图。   不要重复使用 Micron/EVK 设置，务必为您的JSL4BAG16 重新调整 Vref。 Re: imx93 lpddr4x config for JSL4BAG16 unstable 嗨 Oswalag： 谢谢回复。我已经通过了“i.MX 配置工具”的测试，并在“优化”测试结果中使用了 DQ 和 CA 的“Vref”。 但它仍然存在两个问题： 1.某些板无法显示“CA图表”，“CA Eye”测试也存在一些错误，但显示通过。 2.更新 lpddr4x_timing.c 后使用“i.MX 配置工具”生成，所有板都已通过测试，当我在系统中运行“memtest”时，它会在“地址卡住”处失败，并非总是如此，但有时会失败。 此致。 Re: imx93 lpddr4x config for JSL4BAG16 unstable 我的 frdm-imx93 板上也有同样的芯片，但它无法使用现成的镜像正常启动。如何解决这个问题？

imx93 lpddr4x config for JSL4BAG16 unstable hi experts:     I have a problem about lpddr4x config for  JSL4BAG16,  after config , it passes "functional" test,  but sometimes fail at "Optimization->Vref for CA optimization",  not fail all the time, but sometimes.     When test "vTSA ->CA eye",  it shows pass, but some "error log" shows also.     I have a question about how to tune the "Vref DQ config" and "Vref CA config" ? JSL4BAG16's Vref  value  is difference with "Microns which used in EVK", does it need to set rang 0 or rang 1 ?      And as I know, the Vref DQ is config according to "eye diagram" test result , but there are "read diagram" and "write diagram" , which one should I use?      I have attached the datasheet of JSL4BAG and "CA eye" test log and mex file.        Best Regards. Re: imx93 lpddr4x config for JSL4BAG16 unstable Hello, The LPDDR4X is part of the https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/i-MX-93-Memory-Compatibility-Guide/ta-p/1725656 For Vref DQ tuning use Range 1 (default) for JSL4BAG16 and use the write eye diagram, not read.   Do not reuse Micron/EVK settings, always retune Vref for your JSL4BAG16. Re: imx93 lpddr4x config for JSL4BAG16 unstable HI Oswalag:        Thanks for reply . I have passed the test with "i.MX config tool",  and use the "Vref" of DQ and CA in the "Optimization" test result.       But still has two problem:     1. some board , it could not show "CA Charts" , "CA Eye" test has some error, but it shows pass     2. After update the lpddr4x_timing.c which generated by "i.MX config tool" with all passed board,  when I run "memtest" in system, it will fail at "Stuck Address" , not always, but sometimes.     Best Regards.  Re: imx93 lpddr4x config for JSL4BAG16 unstable I have the same chip on my frdm-imx93 board that doesn't boot properly with the off the shelf images. How to solve it?

Zone Node Software & Hardware Environment 1 Table of Contents • Introduction • Required Software • Required Hardware • References • Conclusion 2 Introduction This article is part of the Zone Node series and describes the software and hardware environment used throughout the project. The purpose of this article is to describe the software and hardware setup required to follow the series and reproduce the results. Before examining communication routing, control logic, or integration challenges, it is important to understand the tools and platforms that support the development and execution of the zonal node application. This article introduces the software components used to develop, configure, and deploy the application, as well as the hardware platforms used to demonstrate the zonal controller functionality. This information provides the foundation required for the remaining articles in the series. Overview of the development flow The zonal node application presented in this series is developed using a combination of Model-Based Design tools, NXP software components, and automotive-grade hardware platforms. At a high level: Application modeling starts in MATLAB® and Simulink®, where communication routing and control logic are implemented graphically. Code generation converts the model into production-ready embedded software using the code-generation tools provided by MathWorks and NXP. Deployment compiles the generated software and loads it onto the target hardware, where it is used to demonstrate communication between multiple vehicle networks. This environment was selected to support rapid development, easier validation, and improved traceability between model design and generated software. By using a Model-Based Design approach, algorithm development, communication integration, and application verification can be performed within a common framework. The software and hardware presented here are used consistently throughout the series and will be referenced when discussing communication routing, system behavior, and integration scenarios. Figure 1. Development flow diagram The workflow begins with application development in Simulink. Communication routing logic, control functions, and software configuration are implemented within the model. The NXP Model-Based Design Toolbox (MBDT) provides hardware-specific blocks that enable integration with S32K3 peripherals and communication interfaces. Following code generation, the application is compiled and deployed to the target hardware, where communication routing functionality can be validated. This article is intended for: Engineers interested in reproducing the zonal node demonstration Simulink users developing automotive communication applications Developers evaluating Model-Based Design workflows Engineers working with NXP automotive microcontrollers and evaluation boards By understanding the software and hardware environment early in the series, readers will be better prepared to follow the implementation details presented in subsequent articles. 3 Required Software The following software components are used throughout the project: MATLAB® and Simulink® – model development and simulation Embedded Coder® (required MATLAB toolbox) – automatic code generation from the model Simulink models – the zonal node routing application model referenced throughout the series NXP Model-Based Design Toolbox (MBDT) – S32K3 support and peripheral configuration NXP additional tools – FreeMASTER and S32 Design Studio for build, deployment, and debugging CAN analysis software – monitoring and validating CAN communication LIN analysis software – monitoring and validating LIN communication 3.1 MATLAB® and Simulink® MATLAB® and Simulink® form the foundation of the development environment. They are used to create the zonal node application, implement communication routing logic, configure software behavior, and perform model-based verification activities. The application described throughout this series is developed as a Simulink model and later translated into embedded software using automatic code-generation tools (Embedded Coder®). 3.2 NXP Model-Based Design Toolbox (MBDT) The NXP Model-Based Design Toolbox (MBDT) extends Simulink with hardware-specific support for NXP automotive microcontrollers. For this project, MBDT for S32K3 version 1.8.0 is used. The toolbox provides blocks and configuration interfaces for communication peripherals, timers, digital I/O resources, and other hardware modules available on the target device. It also integrates with the code-generation workflow, allowing Simulink models to be converted into software that can run directly on the S32K3 microcontroller. Note: Installation and configuration instructions are provided in the dedicated article series (How to install .MLTBX). Readers who have not yet installed the toolbox should complete that step before continuing with this series. 3.3 CAN Analysis Software CAN analysis tools are used during development and validation to observe CAN and CAN FD traffic exchanged between the zonal node and other network participants. Typical use cases include: Monitoring transmitted and received CAN frames Verifying CAN-to-CAN routing behavior Measuring message timing and bus utilization Troubleshooting communication issues Examples of commonly used software include PCAN-View, CANalyzer, and CANoe. 3.4 LIN Analysis Software LIN analysis tools are used to monitor communication between the zonal node and LIN-connected edge devices. Typical use cases include: Verifying LIN schedule execution Monitoring frame transmission and reception Validating signal timing and integrity Testing LIN-to-CAN routing scenarios Examples of commonly used software include PLIN-View and LINalyzer. 4 Required Hardware The following hardware components are used throughout the project: S32K344 automotive microcontroller – used to execute the zonal node application S32K344-WB Evaluation Board – used as the development and validation platform CAN analysis hardware – used to monitor and verify CAN/CAN FD communication LIN analysis hardware – used to monitor and verify LIN communication 4.1 S32K3 Microcontroller The S32K3 family provides: Arm® Cortex®-M7 processing cores CAN FD communication interfaces LIN communication support Safety-oriented automotive features Low-power operating modes Rich peripheral connectivity These capabilities make the device suitable for implementing communication aggregation and routing functions within the scope of this project. 4.2 Evaluation Hardware The zonal node application runs on the S32K344-WB Evaluation Board, a development platform based on the NXP S32K344 microcontroller. The board provides access to the communication interfaces and processing capabilities of the target device while offering an integrated platform for software development, debugging, and validation activities. Within the scope of this project, the board is used to execute the routing application and exchange messages with nodes connected through CAN and LIN networks. Its communication interfaces, debugging connectivity, and expansion capabilities make it suitable for evaluating zonal communication architectures and routing scenarios. Figure 2. S32K344-WB evaluation board 4.3 Communication Networks The examples presented throughout this series use CAN and LIN networks to demonstrate message forwarding, routing, and protocol translation scenarios. These networks provide the communication backbone between the zonal node, central controller, and edge nodes, and are referenced throughout the upcoming routing and integration articles. 4.4 Network Analysis Hardware Additional hardware tools are used during development and validation to observe network traffic and verify communication behavior. CAN analysis interfaces can be connected to the network to monitor transmitted and received CAN/CAN FD frames, validate routing functionality, and troubleshoot communication issues. LIN analysis interfaces can be used to monitor LIN schedules, frame exchanges, and LIN-to-CAN routing scenarios. These tools provide visibility into network activity and support verification of the communication flows presented in later articles of this series. 5 References Model-Based Design Toolbox (MBDT) Embedded Coder® Documentation MATLAB® and Simulink® Documentation S32K3 Microcontrollers S32K344-WB Evaluation Board 6 Conclusion This article introduced the software and hardware environment used throughout the zonal node project. It presented the development tools, code-generation workflow, and target hardware that support the implementation of the communication routing application. The next article will build on this foundation by examining the internal logic control mechanisms used within the zonal node and how they contribute to communication handling across multiple networks.

How to generate a Standalone IAR toolchain project from MCUXSDK application example - KWX/MCWX To generate a hello world (suppose) example for KW47-EVK for IAR toolchain. We asume that IAR toolchain is already installed. Set IAR_DIR environment variable. In Windows, this can be done via Edit environment variables system option. Example: IAR_DIR=C:\iar\ewarm-9.60.1.    Note: IAR toolchain version may change. Type the following commands on your MCUXSDK workspace: cd mcuxsdk west build -b kw47evk ./examples/demos_apps/hello_world --toolchain=iar -t standalone_project -Dcore_id=cm33_core0 --pristine -d ./build/kw47evk/kw47evk_standalone_hello_world_iar​ IAR project should have been generated on  MCUXSDK_WS/mcuxsdk/build/kw47evk/kw47evk_standalone_hello_world_iar/iar directory. IAR project has .eww file extension.   Relevant links IDE Project Generation: https://mcuxpresso.nxp.com/mcuxsdk/latest/html/develop/build_system/IDE_Project.html# Note: Ruby is required for this feature. Typically, this tool is installed via MCUXpresso Installer. However, if having issues with this tool refer to the next link: Ruby Environment Setup: https://mcuxpresso.nxp.com/mcuxsdk/latest/html/develop/build_system/IDE_Project.html#ruby-environment-setup Suppose you want to generate a hello world example for KW47-EVK for IAR toolchain as the previous example, but this time LPTMR driver is required for low-power timer operating purposes. We asume that IAR toolchain is already installed and IAR_DIR variable is already set. The easiest way to accomplish this is to add the lptmr Kconfig symbols with ‘yes’ value at Board-Application level (Refer to Kconfig User Guide). In this case, the target prj.conf file is located on  MCUXSDK_WS/mcuxsdk/examples/_boards/kw47evk/demo_apps/hello_world.​ Edit this file and add the LPTMR required symbols:  CONFIG_MCUX_COMPONENT_driver.lptmr=y CONFIG_MCUX_COMPONENT_component.lptmr_adapter=y​ Type the following command on your MCUXSDK workspace:  west build -b kw47evk ./examples/demo_apps/hello_world --toolchain=iar -t standalone_project -Dcore_id=cm33_core0 --pristine -d ./build/kw47evk/kw47evk_standalone_hello_world_iar IAR project should have been generated on MCUXSDK_WS/mcuxsdk/build/kw47evk/kw47evk_standalone_hello_world_iar/iar directory. IAR project has .eww file extension. This time LPTMR drivers should be included in iar/drivers/lptmr    

MCX W72 Knowledge hub The MCX W72x family features a 96 MHz Arm® Cortex®-M33 core coupled with a multiprotocol radio subsystem supporting Matter, Thread, Zigbee and Bluetooth LE. The independent radio subsystem, with a dedicated core and memory, offloads the main CPU, preserving it for the primary application and allowing firmware updates to support future wireless standards. The MCX W72x also offers advanced security with an integrated EdgeLock® Secure Enclave Core Profile and will be supported by NXP's EdgeLock 2GO cloud services for credential sharing. The MCX W72x family includes Bluetooth Channel Sounding capabilities, with a dedicated on-chip Localization Compute Engine to reduce ranging latency. It incorporates additional memory to support application-specific code, connectivity stacks and over-the-air firmware updates. In addition, the radio subsystem can run the full Thread or Zigbee stack alongside the Bluetooth Low Energy stack. This delivers reliable wireless performance, as the real-time activities of the radio run on a separate core from the application. Building on NXP's strong history of providing industrial edge solutions, the MCX W series offers a wide operating temperature range from -40 °C to 125 °C and peripherals for industrial applications, including an optional CAN interface and will be part of NXP's 15-year Product Longevity program to support long-term industrial use. The MCX W series is supported by the MCUXpresso Developer Experience to optimize, ease and help accelerate embedded system development.   Security Certifications  PSA Certified Level 2 SESIP Level 2 Security Target  SESIP Level 2 KW47/MCXW72 SESIP certificate and ST are on TrustCB website Regulatory Certifications European Union Declaration of Conformity - FRDM MCXW72 European Union Declaration of Conformity - MCXW72-LOC Bluetooth Qualifications Qualified Products | Bluetooth® Technology Website Q360996: KW47 / MCX W72 Bluetooth LE 6.0 (Channel Sounding) Controller Q332147: KW47 / MCX W72 Bluetooth LE 6.0 (Channel Sounding) Host Documents MCX W72 Product Family Data Sheet MCX W72 Reference Manual Errata Sheet for MCX W72 MCXW72 Hardware Design Guide   Getting Started with Matter on MCX W72 platforms Getting Started with OpenThread on NXP MCX W72    FRDM-MCXW72 User Manual Getting Started with the FRDM-MCXW72   MCX W72-LOC User Manual 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. Awards and Recognition - Every year, the Bluetooth Special Interest Group (SIG) celebrates the hard work and commitment of working groups, committee members, and contributors who have been recognized by their peers as making a difference in advancing Bluetooth technology.  2024: Channel Sounding 2025: Channel sounding amplitude-based attack resilience, LE test mode enhancements and Ranging profile and service.  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 Bluetooth_6.1_Feature_Overview Bluetooth_6.2_Feature_Overview Bluetooth_6.3_Feature_Overview Application Notes Software, Hardware and Peripherals: AN14850 Boosting application performance with MCX W72: This application note describes the usage of the dual-core architecture in the MCX W72 microcontroller to improve performance in generic embedded applications. AN14937 32kHz Crystal-less mode on MCX W72: This application note provides information on the 32 kHz Crystal-less mode on the MCX W72 device. This mode allows you to reduce the cost of the system, without compromising the 32 kHz clock accuracy. The Free‑Running Oscillator (FRO32K) is used as the 32 kHz clock source and is calibrated against the 32 MHz RF oscillator through the Signal Frequency Analyzer (SFA) module of MCX W72 AN14745 Features, Usage, and Capabilities of Smart Power Switch on the MCX W72: This application note describes the use of the smart power switch in the MCX W72microcontroller. The MCX W72 integrates a programmable solid-state switch that turns connected components on or off, including MCX W72 power domains. AN14747 Loadpull test Report for MCX W72: This document explains the purpose of measuring the supply current, the transmit power, and the harmonics level. These measurements are monitored while the complex output load seen by the device under test (DUT) is tuned in amplitude and phase. Power Management:  AN14739 MCX W72 Bluetooth Low Energy Power Consumption Analysis: This document provides the power consumption analysis of the MCX W72 (IIOT) wireless MCU using the MCXW72-EVK board AN14745 Features Usage and Capabilities of Smart Power Switch on MCX W72 Microcontroller:  This application note describes the use of the smart power switch in the MCX W72 microcontroller. The MCX W72 integrates a programmable solid-state switch that turns connected components on or off, including MCX W72 power domains. AN14841 802.15.4 Matter and Zigbee Power Consumption Analysis for MCX W72: This document provides the power consumption analysis of the Kinetis MCX W72 (IIoT) wireless MCUs. AN14742 Power Management Hardware for the MCX W72: This application note describes the usage of the different modules dedicated to power management in the MCX W72microcontroller AN14664 Coincell Hardware Recommendations for Kinetis BLE Applications: his document describes some hardware and software solutions to minimize the peaks of current at the coin cell level AN14889: FRDM-MCXW72 Radio Frequency System Evaluation Report for Bluetooth Low Energy and for IEEE 802.15.4 This document provides the radio frequency (RF) evaluation test results of the FRDM-MCXW72 board for Bluetooth Low Energy (2FSK modulation) and IEEE 802.15.4 (OQPSK modulation) applications.  RF: AN14865 Channel Sounding Fundamentals for the KW47 and MCX W72: This document provides an overview of the fundamentals for CS technology and how it can be used for custom solutions and applications. AN14779 Printed Channel Sounding Antennas for the KW47 and MCX W72: his application note is focused on printed antennas implemented on printed-circuit boards (PCB), designed by NXP for the KW47 and MCX W72 controllers AN14832 Fundamental Steps to Design a Channel Sounding Board - Creating a Simple PCB without Diversity: In this document, an example of a minimalistic CS subsystem is presented. Attention is paid to the Radio-Frequency (RF) path, since RF circuitry strongly influences the properties of the whole CS application. AN14747 Loadpull Test Report for MCX W72: This document explains the purpose of measuring the supply current, the transmit power, and the harmonics level. These measurements are monitored while the complex output load seen by the device under test (DUT) is tuned in amplitude and phase. AN14868 RF Modeling of Channel Sounding in ANSYS: focuses on techniques for simulating and analyzing channel sounding in wireless communication systems using ANSYS tools AN14855 Channel Sounding Tests in Different Environments: This application note is about Bluetooth Channel Sounding (CS), a technique for measuring the distance between two devices in the Bluetooth frequency band. It explains key factors affecting accuracy AN14869 Fundamental Steps to Design a Complex Channel Sounding Board:  It focuses on creating hardware that supports advanced CS features, including antenna diversity and optimized RF paths, to improve accuracy and mitigate issues like multipath propagation. AN2731 Compact Planar Antennas for 2.4GHz Communication: This document is not an exhaustive inquiry into antenna design. It is instead focused on helping the customers understand enough board layout and antenna basics to select a correct antenna type for their application, as well as avoiding typical layout mistakes that cause performance issues that lead to delays Security: AN14648 MCX W72 In-System Programming Utility: The document provides steps to boot the MCX W72 MCU in ISP mode and establish various serial connections to communicate with the MCU AN14613 MCX W72 Secure Boot using SEC tool: The MCX W72 is a low-power, highly secure, single-chip wireless MCU, the contents of flash memory can be saved as encrypted data, which can be decrypted instantly. It helps in protecting the sensitive data and algorithms. AN14646 Debug Authentication on MCX W72: This application note describes the steps for debug authentication using the MCUXpresso Secure Provisioning Tool (SEC). AN14728 MCX W72 Flash Encryption using NPX: There is an increasing requirement to protect the application code and data stored in flash memories in an encrypted form due to security reasons. The NVM PRINCE XEX (NPX) is a module inside the Flash Memory Controller (FMC) that allows customers to protect the contents of flash regions (up to four regions). It performs on-the-fly, low-latency encryption and decryption of flash contents, and it is transparent to the developer and to the Cortex-M33 platform. No special handle is needed from the perspective of the developer. AN14644 MCX W72 Managing Lifecycles: This document describes the following: Lifecycle stages that are available to the user, how to access the lifecycles, limitations of the lifecycles, how to transition to the next lifecycle AN14670 EdgeLock 2GO Provisioning via SPSDK for MCUs: EdgeLock 2GO is a fully managed cloud platform operated by NXP that provides secure provisioning services for easy deployment and maintenance of IoT devices that integrate NXP MCU, MPU, and EdgeLock SE05x secure elements. AN14624 EdgeLock 2GO PRovisioning via Secure Provisioning Tool (SEC) for MCUs: EdgeLock 2GO is a fully managed cloud platform operated by NXP that provides secure provisioning services for easy deployment and maintenance of IoT devices that integrate NXP MCU, MPU, and EdgeLock SE05x secure elements. AN14544 EdgeLock 2Go Services for MPU and MCU: EdgeLock 2GO is the service platform of NXP for provisioning and managing IoT devices. It lets you securely install keys and certificates into your devices, either during manufacturing or in the field, and then keep credentials up to date during the device life cycle. EdgeLock 2GO uses the security capability of each device, for optimal levels of security across your entire IoT fleet. Bluetooth Training Bluetooth Low Energy 6.0 NXP Training MCX W Series Training - NXP Community   RF Switch Comparison Absorptive/Reflective Standards Comparison ETSI / FCC / ARIB requirements BLE Channel Sounding  - Overview BLE Channel Sounding - RF Hardware BLE Channel Sounding - ANSYS Modeling Tools  BLE Channel Sounding - Antenna Prototypes Validation Measurements Equipment Wireless Equipment: This article provides the links to the Equipment that helps to the project development  Useful Links Debug probe firmware installation for the KW47-EVK and FRDM-MCXW72 This post will cover how to install the CMSIS-DAP/SEGGER J-link firmware for the KW47-EVK and FRDM-MCXW72 using NXP’s MCU-LINK installer. How to generate a Standalone IAR toolchain project from MCUXSDK application example - KWX/MCWX  Updating NBU for Wireless Examples on KW47/MCXW72This post will cover how to update the NBU firmware How to import and run demo examples with MCUXpresso for Visual Studio Code: This article gives information on how to import and run demo examples from the new SDK with ARM GCC toolchain, in MCUXpresso for Visual Studio Code. [MCUXSDK] How to use GitHub SDK for KW4x, MCXW7x, MCXW2x - NXP Community this community post provides step by step how to use GitHub SDK [MCUXSDK] GitHub SDK - Documentation for Bluetooth LE platforms - NXP Community this community post provides the documentation for BLE platforms.  The best way to build a PCB first time right with KW47 (Automotive) or MCXW72 (IoT/Industrial): In this community provides the important link to build a PCB using a KW45 or K32W148 and MCXW71 and all concerning the radio performances, low power and radio certification (CE/FCC/ICC) Workaround implementation for DCDC failure during drive strength change a DCDC failure can occur infrequently during a drive strength change to low, and the DCDC output voltage becomes greater than or equal to the current output voltage. How to use the HCI_bb on Kinetis family products and get access to the DTM mode:  This article is presenting two parts: How to flash the HCI_bb binary into the Kinetis product. Perform RF measurement using the R&S CMW270 BLE HCI Application to set transmitter/receiver test commands: This article provides the steps to show how user could send serial commands to the device. Bluetooth LE HCI Black Box Quick Start Guide : This article describes a simple process for enabling the user controls the radio through serial commands. Kinetis (../45/47/43;MCX W71/72/70) & MCX W23 Power Profile Tools (including Localization):  This page is dedicated to the Kinetis (KW35/KW38/KW45/KW47/KW43) and MCX W7x (MCX W71/W72/W70) Power Profile Tools. It will help you to estimate the power consumption in your application (Automotive or IIoT) and evaluate the battery lifetime of your solution. KW47/MCXW72 32MHz & 32kHz Oscillation margins: this article provides the properly configuration for the Oscillation margins for the circuit. Errata ERR053377: Use Cases for Different Message Buffer ConfigurationsThis article discusses the different use cases and configuration of the errata "ERR053377: FlexCAN: Message Buffer (MB) and Enhanced RX FIFO Filter Element (ERFFEL) Memory Corruption" Videos NXP Channel Sounding technology interfacing with Google Pixel 10 This is a demo showing the MCX W72 LOC board interacting with Google Pixel 10 phone using channel sounding Exploring Bluetooth Channel Sounding on FRDM-MCXW72 - Part 1: In this video, you will see step‑by‑step how Bluetooth® Channel Sounding works using NXP’s Rate2 distance‑estimation solution. Performing the demonstration includes a computer with VS Code, the MCUXpresso extension and toolchains installed, a FRDM‑MCXW72 development board and a smartphone running the BLE Hero application. Exploring Bluetooth Channel Sounding on FRM-MCXW72 - Part 2:  Concluding the demonstration of Bluetooth® Channel Sounding, part two of this presentation continues with a brief review of the testing setup and walks you through running board‑to‑board measurements

KW47ナレッジハブ KW47 ファミリでは、96 MHz Arm® Cortex®-M33コアをBluetooth LEサブシステムとカップリングしています。この無線サブシステムは独立しており、コアやメモリも専用で、メインCPUの負荷を軽減するので、プライマリ・アプリケーションの分が保持され。また、ファームウェア・アップデートによる将来のワイヤレス標準のサポートも可能です。EdgeLock® Secure Enclave Core Profileを統合した高度なセキュリティのKW47は、NXPのEdgeLock 2GOクラウド・サービスによるサポートで認証情報の共有にも対応します。 KW47ファミリにはBluetoothのチャネル・サウンディング機能が搭載されており、オンチップの専用Localization Compute Engineで測距遅延を短縮します。アプリケーション固有のコード、コネクティビティ・スタック、OTA（Over-The-Air）ファームウェア・アップデートをサポートするための追加メモリも搭載されています。これにより、無線のリアルタイム動作がアプリケーションとは別のコアで実行されるため、信頼性の高いワイヤレス性能が得られます。 オートモーティブ・ソリューションを提供してきたNXPの豊富な経験に基づくKW47ファミリは、-40°C～125°Cの幅広い動作温度範囲と、車載アプリケーション向けペリフェラルを備えるほか、KW47は、長期使用をサポートするNXPの15年間の長期製品供給プログラムの対象ともなっています。 KW47シリーズは、MCUXpresso開発者エクスペリエンスによってサポートされ、組込みシステム開発の最適化、簡素化、迅速化に役立ちます。 KW47は製造開始前ですが、開発者はピンやソフトウェアの互換性があるKW45なら今すぐ使用を開始できます。       早期アクセスプログラム KW47早期アクセスプログラムはこちらKW47 Early Accessから参加できます。 アクセスのリクエストはNXPセールスチームまでご連絡ください。   チャネル・サウンディング チャネル・サウンディングご紹介プレゼンテーション CCC CS消費電力計算ツールあり（Excelファイル添付）   Bluetooth仕様 Bluetooth_5.0_Feature_Overview  Bluetooth_5.1_Feature_Overview Bluetooth_5.2_機能_概要 Bluetooth_5.3_機能_概要 Bluetooth_5.4_Feature_Overview Bluetooth_6_Feature_Overview   トレーニング Bluetooth Low Energy 6.0 NXPご紹介 RFスイッチの比較 吸収型と反射型 規格の比較 ETSI/FCC/ARIB要件 BLEチャネルサウンディング - 概要 BLEチャネル・サウンディング - RFハードウェア BLEチャネル・サウンディング - ANSYSモデリング・ツール BLEチャネル・サウンディング - アンテナのプロトタイプの検証測定 機器 ワイヤレス機器：この記事には、プロジェクト策定に役立つ機器へのリンクが掲載されています。 便利なリンク リファレンスデザイン - NXP Community KW45/KW47/MCXW71/MCXW72でのSignal Frequency Analyzer（SFA）モジュールを使用したクロック測定 - NXPコミュニティ：このコミュニティでは、Signal Frequency Analyzerの使用方法に関する手順を提示しています。 ［MCUXSDK］KW4x、MCXW7x、MCXW2xにGitHub SDKを使用する方法 - NXPコミュニティ GitHub SDKの使用方法をステップ別に紹介しています。 ［MCUXSDK］GitHub SDK - Bluetooth LEプラットフォームのドキュメント - NXPコミュニティ BLEプラットフォーム用ドキュメントを提供しています。  KW47（オートモーティブ）またはMCXW712（IIoT）を使用してPCBを初めて正しく構築するための最適な方法 - コミュニティ：このコミュニティには、KW45またはK32W148/MCXW71を使用してPCBを構築するための重要なリンクと、無線性能、低電力、無線認証（CE/FCC/ICC）に関するあらゆる情報があります。 HCI_bbをKinetisファミリ製品で使用してDTMモードにアクセスする方法：この記事は次の2つの部分に分かれています。 HCI_bbバイナリを Kinetis製品へフラッシュする方法。 R&S CMW270を使用してRF測定を行う BLE HCIアプリケーションによるトランスミッタ/レシーバテストコマンドの設定：この記事では、ユーザーはどのようにすればシリアルコマンドをデバイスに送信できるかを示す手順を説明します。 Bluetooth LE HCI Black Boxクイックスタートガイド：この記事では、ユーザーが無線をシリアルコマンドで制御できるようにするためのシンプルなプロセスを説明します。 Kinetis（K32/38/KW45およびK32W1/MCXW71）パワー・プロファイル・ツール：Kinetis（KW35/KW38/KW45）およびMCX W7x（MCX W71）パワー・プロファイル・ツールに的を絞ったページです。お使いのアプリケーション（自動車またはIoT）での電力消費量を試算したり、ソリューションのバッテリ寿命を評価したりするのに役立ちます。  

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) 功率配置工具。它将帮助您估算您的应用程序（汽车或物联网）的功耗，并评估您解决方案的电池寿命。  

KW47 Knowledge Hub KW47 family features a 96 MHz Arm® Cortex®-M33 core coupled with a Bluetooth LE subsystem. The independent radio subsystem, with a dedicated core and memory, offloads the main CPU, preserving it for the primary application and allowing firmware updates to support future wireless standards. The KW47 also offers advanced security with an integrated EdgeLock® Secure Enclave Core Profile and will be supported by NXP's EdgeLock 2GO cloud services for credential sharing. The KW47 family includes Bluetooth Channel Sounding capabilities, with a dedicated on-chip Localization Compute Engine to reduce ranging latency. It incorporates additional memory to support application-specific code, connectivity stacks and over-the-air firmware updates. This delivers reliable wireless performance, as the real-time activities of the radio run on a separate core from the application. Building on NXP's strong history of providing automotive solutions, the KW47 family offers a wide operating temperature range from -40 °C to 125 °C and peripherals for automotive applications, KW47 will be part of NXP's 15-year Product Longevity program to support long-term use. The KW47 series is supported by the MCUXpresso Developer Experience to optimize, ease and help accelerate embedded system development.   KW47 boards KW47-EVK Getting Started with the KW47 EVK KW47-EVK Board User Manual KW47-M2 Board User Manual  KW47-EVK Quick Start Guide KW47-M2 Quick Start Guide   KW47-LOC Getting Started with the KW47-LOC KW47-LOC Board User Manual KW47-LOC Quick Start Guide KW47: Bluetooth Channel Sounding MCU with On-Chip Localization Compute Engine the KW47 Security Certifications  PSA Certified Level 2 SESIP Level 2 Security Target  SESIP Level 2 KW47/MCXW72 SESIP certificate and ST are on TrustCB website  Regulatory Certifications European Union Declaration of Conformity - KW47-EVK European Union Declaration of Conformity - KW47-LOC Bluetooth Qualifications Qualified Products | Bluetooth® Technology Website Q360996: KW47 / MCX W72 Bluetooth LE 6.0 (Channel Sounding) Controller Q332147: KW47 / MCX W72 Bluetooth LE 6.0 (Channel Sounding) Host Documents  KW47 Product Family Data Sheet KW47 Reference Manual Errata for KW47 KW47 Hardware Design Guide 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. Awards and Recognition - Every year, the Bluetooth Special Interest Group (SIG) celebrates the hard work and commitment of working groups, committee members, and contributors who have been recognized by their peers as making a difference in advancing Bluetooth technology, like NXP! 2024: Channel Sounding 2025: Channel sounding amplitude-based attack resilience, LE test mode enhancements and Ranging profile and service.  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 Bluetooth_6.1_Feature_Overview Bluetooth_6.2_Feature_Overview Bluetooth_6.3_Feature_Overview Application Notes Software, Hardware and Peripherals: AN14884 32kHz Cristal-less mode on KW47: This application note provides information on the 32 kHz Crystal-less mode on the KW47 device. This mode allows you to reduce the cost of the system, without compromising the 32 kHz clock accuracy.  AN14846 Boosting Application Performance with the KW47 Dual-Core Architecture: This application note describes how to use the dual-core architecture in the KW47 microcontroller to improve performance in generic embedded applications AN14796 Migration Guide from the KW45 to the KW47:  This document describes the procedure to migrate from KW45B41Z to KW47 with emphasis on the connectivity software. The document is intended for software engineers, software testers, software integrators, and customers designing their own hardware. Power Management: AN14709 Power Management Hardware for the KW47: This application note describes the usage of the different modules dedicated to power management in the KW47microcontroller. TheKW47integrates a DC-DC buck converter, a couple of low-dropout regulators, and a programmable solid-state switch to turn on/off theKW47power domains AN14684 Features, Usage, and Capabilities of Smart Power Switch on the KW47 Microcontroller: This application note describes the use of the smart power switch in the KW47 microcontroller. The KW47 integrates a programmable solid-state switch that turns connected components on or off, including KW47 power domains AN14664 Coincell Hardware Recommendations for Kinetis BLE Applications: his document describes some hardware and software solutions to minimize the peaks of current at the coin cell level AN14554 KW47 Bluetooth Low Energy Power Consumption Analysis:  This document provides the power consumption analysis of the Kinetis KW47 (automotive) wireless MCU using the KW47-EVK board RF: AN14719 Integrating the OTAP Client Service into a KW47 BLE Peripheral Device: This application note outlines the use of the NXP Over the Air Programming (OTAP) custom Bluetooth Low Energy (Bluetooth LE) service to upgrade software on a Microcontroller Unit (MCU) without using physical cables. AN14940 KW47 Coexistence with RF System Evaluation Report for the Bluetooth LE Applications: This document provides the coexistence RF evaluation test results of the KW47-EVK for Bluetooth LE applications (2FSK modulation). It includes the test setup description and the tools used to perform the tests on your own. For the KW47 radio parameters AN14461 KW47-EVK RF System Evaluation Report for Bluetooth LE Applications: This document provides the RF evaluation test results of the KW47-EVK board for Bluetooth LE (2FSK modulation) applications. It includes the test setup description and the tools used to perform the tests. AN14826 KW47-LOC System Evaluation Report for BLE Applications: This document provides the RF evaluation test results of the KW47 Localization board (KW47-LOC) for Bluetooth LE (2FSK modulation) applications. It includes the test setup description, and the tools used to perform the tests on your own. AN14696 Loadpull Test Report for KW47: This document explains the purpose of measuring the supply current, the transmit power, and the harmonics level. These measurements are monitored while the complex output load seen by the device under test (DUT) is tuned in amplitude and phase. AN14628 KW47 CCC Channel Sounding Power Profile Analysis:  this document explains power consumption measurement at each step of the full distance measurement procedure, changing of the code to set the different option in the SDK software, and usage of the associated power profile estimator tool. AN14865 Channel Sounding Fundamentals for the KW47 and MCX W72: This document provides an overview of the fundamentals for CS technology and how it can be used for custom solutions and applications. AN14832 Fundamental Steps to Design a Channel Sounding Board - Creating a Simple PCB without Diversity: In this document, an example of a minimalistic CS subsystem is presented. Attention is paid to the Radio-Frequency (RF) path, since RF circuitry strongly influences the properties of the whole CS application. AN14779 Printed Channel Sounding Antennas for the KW47 and MCX W72: his application note is focused on printed antennas implemented on printed-circuit boards (PCB), designed by NXP for the KW47 and MCX W72 controllers AN14720 Creation of Firmware Update Image for KW47 using Over the Air Programming Tool: This document outlines the steps to create and upgrade the image on the KW47–EVK board AN14868 RF Modeling of Channel Sounding in ANSYS: focuses on techniques for simulating and analyzing channel sounding in wireless communication systems using ANSYS tools AN14855 Channel Sounding Tests in Different Environments: This application note is about Bluetooth Channel Sounding (CS), a technique for measuring the distance between two devices in the Bluetooth frequency band. It explains key factors affecting accuracy AN14869 Fundamental Steps to Design a Complex Channel Sounding Board:  It focuses on creating hardware that supports advanced CS features, including antenna diversity and optimized RF paths, to improve accuracy and mitigate issues like multipath propagation. AN2731 Compact Planar Antennas for 2.4 GHz Communication: This document is not an exhaustive inquiry into antenna design. It is instead focused on helping the customers understand enough board layout and antenna basics to select a correct antenna type for their application, as well as avoiding typical layout mistakes that cause performance issues that lead to delays Security: AN14727 KW47 Flash Encryption using NPX: There is an increasing requirement to protect the application code and data stored in flash memories in an encrypted form due to security reasons. The NVM PRINCE XEX (NPX) is a module inside the Flash Memory Controller (FMC) that allows customers to protect the contents of flash regions (up to four regions). It performs on-the-fly, low-latency encryption and decryption of flash contents, and it is transparent to the developer and to the Cortex-M33 platform. No special handle is needed from the perspective of the developer. AN14607 KW47 Secure Boot using SEC tool: The KW47 is a low-power, highly secure, single-chip wireless MCU, the contents of flash memory can be saved as encrypted data, which can be decrypted instantly. It helps in protecting the sensitive data and algorithms. AN14647 KW47-LOC In-System Programming Utility: The document provides steps to boot the KW47 MCU in ISP mode and establish various serial connections to communicate with the MCU AN14653 Debug Authentication on KW47: This application note describes the steps for debug authentication using the MCUXpresso Secure Provisioning Tool (SEC). AN14649 KW47-EVK In-System Programming Utility: This document provides steps to boot the KW47 MCU into ISP mode and establish various serial connections to communicate with the MCU. AN14643 KW47 Managing Lifecycles: This document describes the following: Lifecycle stages that are available to the user, how to access the lifecycles, limitations of the lifecycles, how to transition to the next lifecycle Training Bluetooth Low energy 6.0 NXP Introduction KW4x: Automotive Bluetooth Low Energy MCUs for Secure Car Access RF Switch Comparison Absorptive/Reflective Standards Comparison ETSI / FCC / ARIB requirements BLE Channel Sounding  - Overview BLE Channel Sounding - RF Hardware BLE Channel Sounding - ANSYS Modeling Tools  BLE Channel Sounding - Antenna Prototypes Validation Measurements   Equipment Wireless Equipment: This article provides the links to the Equipment that helps to the project development  Useful Links How to run KW47-M2 standalone - NXP Community How to generate a Standalone IAR toolchain project from MCUXSDK application example - KWX/MCWX  Debug probe firmware installation for the KW47-EVK and FRDM-MCXW72 This post will cover how to install the CMSIS-DAP/SEGGER J-link firmware for the KW47-EVK and FRDM-MCXW72 using NXP’s MCU-LINK installer. Updating NBU for Wireless Examples on KW47/MCXW72This post will cover how to update the NBU firmware How to import and run demo examples with MCUXpresso for Visual Studio Code: This article gives information on how to import and run demo examples from the new SDK with ARM GCC toolchain, in MCUXpresso for Visual Studio Code. [MCUXSDK] How to use GitHub SDK for KW4x, MCXW7x, MCXW2x - NXP Community this community post provides step by step how to use GitHub SDK [MCUXSDK] GitHub SDK - Documentation for Bluetooth LE platforms - NXP Community this community post provides the documentation for BLE platforms.  The best way to build a PCB first time right with KW47 (Automotive) or MCX W72 (IoT/Industrial) - NXP Community : In this community provides the important link to build a PCB using a KW47 and MCX W72 and all concerning the radio performances, low power and radio certification (CE/FCC/ICC). Workaround implementation for DCDC failure during drive strength change a DCDC failure can occur infrequently during a drive strength change to low, and the DCDC output voltage becomes greater than or equal to the current output voltage. How to use the HCI_bb on Kinetis family products and get access to the DTM mode:  This article is presenting two parts: How to flash the HCI_bb binary into the Kinetis product. Perform RF measurement using the R&S CMW270 BLE HCI Application to set transmitter/receiver test commands: This article provides the steps to show how user could send serial commands to the device. Bluetooth LE HCI Black Box Quick Start Guide : This article describes a simple process for enabling the user controls the radio through serial commands. Kinetis (../45/47/43;MCX W71/72/70) & MCX W23 Power Profile Tools (including Localization):  This page is dedicated to the Kinetis (KW35/KW38/KW45/KW47/KW43) and MCX W7x (MCX W71/W72/W70) Power Profile Tools. It will help you to estimate the power consumption in your application (Automotive or IIoT) and evaluate the battery lifetime of your solution. KW47/MCXW72 32MHz & 32kHz Oscillation margins: this article provides the properly configuration for the Oscillation margins for the circuit. Changing CAN interface configuration on KW47-EVK while using serial terminal:Most available example applications use UART as the serial interface for terminal communication. This approach is commonly chosen because a terminal provides a simple and efficient method for interacting with the application during development and debugging. Errata ERR053377: Use Cases for Different Message Buffer ConfigurationsThis article discusses the different use cases and configuration of the errata "ERR053377: FlexCAN: Message Buffer (MB) and Enhanced RX FIFO Filter Element (ERFFEL) Memory Corruption" Reference Designs Bluetooth Ranging Access Vehicle Enablement System - NXP Community Blue Ravens (Bluetooth Ranging Access Vehicle Enablement System) is a system solution developed by NXP to assist customers in designing their own BLE-based car access solutions using NXP products. Videos NXP Channel Sounding technology interfacing with Google Pixel 10 This is a demo showing the MCX W72 LOC board interacting with Google Pixel 10 phone using channel sounding

KW43 Knowledge Hub The KW43 product family is a low-power, secure, single-chip wireless MCU that integrates a high performance, Bluetooth Low Energy, Bluetooth Channel Sounding, EdgeLock Secure Accelerators, and various MCU peripherals targeted for Automotive applications. The KW43 family utilizes an Arm® Cortex®-M33 core (Armv8-M architecture) running up to 96 MHz for customer applications. The family includes memory configurations of up to 1.5MB flash and 256 KB SRAM across all listed part numbers. All devices in the family integrate a state-of-the-art, scalable security architecture including Arm’s TrustZone®-M, a resource domain controller and an isolated EdgeLock Secure Accelerators supporting hardware cryptographic accelerators, random number generators and key generation, storage, and management along with secure debug. All members of the KW43 family are designed to be compliant to a SESIP Level 3 certification following the Arm PSA Level 3 profile. KW43 uses dual Arm Core Cortex-M33 (‘CM33’) and supports multiple interfaces and security features. One is for application and system use and other is for radio link layer and both cores share a common flash of 1.5 MB. The devices include a full certified Bluetooth LE 6.x controller stack with support for up to 10 simultaneous connections in any controller/peripheral combination. The multiprotocol radio subsystem integrated in the KW43 Family is energy efficient and is designed for Wi-Fi coexistence. The radio is supported with tested software stacks for Bluetooth Low Energy for standalone and hosted applications to enable a range of Automotive, IoT and industrial applications. There is also software and hardware support for 2.4 GHz proprietary protocols. To address ranging requirements, the Localization Engine (LCE) is integrated into the system for enhanced localization performance. The KW43 series is supported by the MCUXpresso Developer Experience to optimize, ease and help accelerate embedded system development. Early access program The KW43 is in pre-production, developers can get started today with the KW45/KW47, which is pin and software compatible.   you can request access contacting NXP sales team - Pascal Bernard ([email protected]) Join KW47 early access program here: KW43 Early Access Training Bluetooth Low energy 6.0 NXP Introduction Interested in Bluetooth technology? Bluetooth® Low Energy Primer – Essential reading for understanding BLE fundamentals. Bluetooth® Specifications – Full list of standards, protocols, and technical documents. Awards and Recognition - Every year, the Bluetooth Special Interest Group (SIG) celebrates the hard work and commitment of working groups, committee members, and contributors who have been recognized by their peers as making a difference in advancing Bluetooth technology.  2024: Channel Sounding 2025: Channel sounding amplitude-based attack resilience, LE test mode enhancements and Ranging profile and service.  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 Bluetooth_6.1_Feature_Overview Bluetooth_6.2_Feature_Overview Bluetooth_6.3_Feature_Overview RF Switch Comparison Absorptive/Reflective Standards Comparison ETSI / FCC / ARIB requirements BLE Channel Sounding  - Overview BLE Channel Sounding - RF Hardware BLE Channel Sounding - ANSYS Modeling Tools  BLE Channel Sounding - Antenna Prototypes Validation Measurements Equipment Wireless Equipment: This article provides the links to the Equipment that helps to the project development  Useful Links How to import and run demo examples with MCUXpresso for Visual Studio Code: This article gives information on how to import and run demo examples from the new SDK with ARM GCC toolchain, in MCUXpresso for Visual Studio Code. [MCUXSDK] How to use GitHub SDK for KW4x, MCXW7x, MCXW2x - NXP Community this community post provides step by step how to use GitHub SDK [MCUXSDK] GitHub SDK - Documentation for Bluetooth LE platforms - NXP Community this community post provides the documentation for BLE platforms.  How to use the HCI_bb on Kinetis family products and get access to the DTM mode:  This article is presenting two parts: How to flash the HCI_bb binary into the Kinetis product. Perform RF measurement using the R&S CMW270 BLE HCI Application to set transmitter/receiver test commands: This article provides the steps to show how user could send serial commands to the device. Bluetooth LE HCI Black Box Quick Start Guide: This article describes a simple process for enabling the user controls the radio through serial commands.

KW43 知识中心 KW43 产品系列是一款低功耗、安全的单芯片无线 MCU，集成了高性能、低功耗蓝牙、蓝牙信道探测、EdgeLock 安全加速器以及各种针对汽车应用的 MCU 外围设备。 KW43 系列采用运行频率高达 96 MHz 的 Arm® Cortex®-M33 内核（Armv8-M 架构），用于客户应用程序。该系列包括所有列出的部件号中高达 1.5MB 闪存和 256 KB SRAM 的内存配置。该系列中的所有设备都集成了最先进的可扩展安全架构，包括 Arm 的 TrustZone®-M、资源域控制器和隔离式 EdgeLock 安全加速器，支持硬件加密加速器、随机数生成器、密钥生成、存储和管理以及安全调试。KW43系列的所有成员均按照Arm PSA 3级配置文件设计符合SESIP 3级认证。 KW43 使用双核 Arm Core Cortex-M33（'CM33'），支持多种接口和安全功能。一个用于应用程序和系统，另一个用于无线链路层，两个内核共享一个 1.5 MB 的公共闪存。 这些设备包括经过全面认证的蓝牙 LE 6.x 控制器堆栈，在任何控制器/外设组合中支持多达 10 个同时连接。KW43 系列中集成的多协议无线电子系统节能，专为 Wi-Fi 共存而设计。该无线电由经过测试的低功耗蓝牙软件堆栈支持，适用于独立和托管应用程序，以支持一系列汽车、物联网和工业应用。软件和硬件还支持 2.4 GHz 专有协议。为满足测距要求，系统中集成了本地化引擎 (LCE)，以提高本地化性能。 KW43 系列受 MCUXpresso开发人员体验支持，可优化、简化并帮助加速嵌入式系统的开发。 早期使用计划 KW43 处于试生产阶段，开发人员现在就可以开始使用引脚和软件兼容的 KW45/KW47。 您可以联系恩智浦销售团队申请访问权限 - Pascal Bernard ([email protected]) 点击此处加入 KW47 早期访问计划： KW43 提前访问 培训 低功耗蓝牙 6.0 恩智浦简介 对蓝牙技术感兴趣？ 低功耗蓝牙 Primer – 理解 BLE 基础知识的必备读物。 蓝牙® 规格 - 标准、协议和技术文件的完整列表。 奖项与表彰- 每年，蓝牙特殊兴趣小组（SIG）都会表彰在推动蓝牙技术发展方面做出突出贡献的工作组、委员会成员和贡献者。 2024:通道探测 2025 年：基于信道探测振幅的攻击弹性、LE 测试模式增强以及测距配置文件和服务。 蓝牙功能概述 蓝牙 5.0 功能概述 蓝牙 5.1 功能概述 蓝牙_5.2_特性_概述 蓝牙_5.3_特性_概述 蓝牙_5.4_特性_概述 蓝牙_6_特性_概述 蓝牙_6.1_特性_概述 蓝牙_6.2_特性_概述 蓝牙_6.3_特性_概述 射频开关比较 吸收式/反射式 标准比较 ETSI / FCC / ARIB 要求 BLE 信道探测 - 概述 BLE 信道探测 - 射频硬件 BLE 信道探测 - ANSYS 建模工具 BLE 信道探测 - 天线原型验证测量 设备 无线设备：本文提供了有助于项目开发的设备链接 实用链接 如何使用适用于 Visual Studio Code 的 MCUXpresso 导入和运行演示示例：本文介绍了如何在适用于 Visual Studio Code 的 MCUXpresso 中使用 ARM GCC 工具链从新 SDK 导入和运行演示示例。 [MCUXSDK]如何为 KW4x、MCXW7x、MCXW2x 使用 GitHub SDK - NXP Community 本社区帖子将逐步介绍如何使用 GitHub SDK [MCUXSDK] GitHub SDK - 蓝牙 LE 平台文档 - NXP 社区 该社区帖子提供了 BLE 平台的文档。 如何在 Kinetis 系列产品上使用 HCi_BB 并获得 DTM 模式的访问权限：本文分为两部分： 如何将 HCi_BB 二进制文件闪存到 Kinetis 产品中。 使用 R&S CMW270 执行射频测量 用于@@ 设置发射器/接收器测试命令的 BLE HCI 应用程序：本文提供了演示用户如何向设备发送串行命令的步骤。 蓝牙 LE HCI 黑盒快速入门指南： 本文介绍了用户通过串行命令控制无线电的简单过程。

KW43 ナレッジハブ KW43製品ファミリーは、低消費電力でセキュアなシングルチップ無線MCUであり、高性能なBluetooth Low Energy、Bluetoothチャネルサウンディング、 EdgeLockセキュアアクセラレータ、および各種MCU周辺機器を統合し、車載アプリケーション向けに設計されています。 KW43ファミリーは、お客様アプリケーション向けに最大96MHzで動作するArm ® Cortex ® M33コア（Armv8-Mアーキテクチャ）を採用しています。このファミリには、記載されているすべての型番において、最大1.5MBのフラッシュメモリと256KBのSRAMを搭載したメモリ構成が含まれています。このファミリのすべてのデバイスは、ArmのTrustZone ® -M、リソースドメインコントローラ、ハードウェア暗号アクセラレータ、乱数発生器、鍵の生成、保存、管理、およびセキュアデバッグをサポートする独立したEdgeLockセキュアアクセラレータを含む、最先端のスケーラブルなセキュリティアーキテクチャを統合しています。KW43ファミリーの全製品は、Arm PSAレベル3プロファイルに準拠したSESIPレベル3認証を取得するように設計されています。 KW43はデュアルArmコアCortex-M33（「CM33」）を搭載し、複数のインターフェースとセキュリティ機能をサポートしています。一つはアプリケーションとシステム用、もう一つは無線リンク層用で、両方のコアは1.5MBの共通フラッシュメモリを共有している。 これらのデバイスには、認証済みのBluetooth LE 6.xコントローラースタックが搭載されており、コントローラーと**ペリフェラル**の組み合わせに関わらず、最大10台の同時接続をサポートします。KW43ファミリに統合されたマルチプロトコル無線サブシステムは、エネルギー効率が高く、Wi-Fiとの共存を前提に設計されています。この無線機は、スタンドアロンおよびホスト型アプリケーション向けに、Bluetooth Low Energy用のテスト済みソフトウェアスタックをサポートしており、自動車、IoT、産業用アプリケーションなど、幅広い用途に対応できます。2.4GHz帯の独自プロトコルに対するソフトウェアおよびハードウェアのサポートも提供されています。測距要件に対応するため、測位性能を向上させるために、測位エンジン（LCE）がシステムに統合されています。 KW43シリーズは、 MCUXpresso開発者エクスペリエンス 組み込みシステム開発を最適化、簡素化、加速化する。 早期アクセスプログラム KW43は現在試作段階ですが、開発者はピンとソフトウェアの互換性があるKW45/KW47を使用して本日より開発を開始できます。  アクセスをご希望の場合は、NXPの営業チーム（担当：パスカル・ベルナール、メールアドレス：[email protected]）までご連絡ください。 KW47早期アクセスプログラムへの参加はこちら： KW43早期アクセス トレーニング Bluetooth Low Energy 6.0 NXP 導入 Bluetooth技術にご興味がありますか？ Bluetooth Low Energy Primer – BLEの基礎を理解するために必読の書。 Bluetooth ®仕様 －規格、プロトコル、技術文書の完全なリスト。 表彰と評価- Bluetooth Special Interest Group (SIG) は毎年、Bluetooth 技術の発展に貢献したとして同業者から認められたワーキンググループ、委員会メンバー、貢献者の努力と献身を称えています。 2024: チャネル Sounding 2025年：チャネルサウンディング振幅ベースの攻撃耐性、LEテストモードの機能強化、および測距プロファイルとサービス。 Bluetooth機能の概要 Bluetooth_5.0_Feature_Overview  Bluetooth_5.1_Feature_Overview Bluetooth_5.2_機能概要 Bluetooth_5.3_機能概要 Bluetooth_5.4_機能概要 Bluetooth 6の機能概要 Bluetooth 6.1の機能概要 Bluetooth 6.2 機能概要 Bluetooth 6.3 機能概要 RFスイッチ比較：吸収型／反射型 規格比較：ETSI / FCC / ARIBの要件 BLEチャネルサウンディング - 概要 BLEチャネルサウンディング - RFハードウェア BLEチャネルサウンディング - ANSYSモデリングツール BLEチャネルサウンディング - アンテナプロトタイプの検証測定 装置 無線機器：この記事では、プロジェクト開発に役立つ機器へのリンクを提供します。 役立つリンク集 Visual Studio Code 用 MCUXpresso を使用してデモ例をインポートして実行する方法: この記事では、Visual Studio Code 用の MCUXpresso で、ARM GCC ツールチェーンを使用した新しい SDK からデモ例をインポートして実行する方法について説明します。 [MCUXSDK] KW4x、MCXW7x、MCXW2x 用 GitHub SDK の使い方 - NXP コミュニティこのコミュニティ投稿では、GitHub SDK の使い方をステップバイステップで解説します。 [MCUXSDK] GitHub SDK - Bluetooth LEプラットフォームのドキュメント - NXPコミュニティこのコミュニティ投稿では、BLEプラットフォームのドキュメントを提供します。 Kinetisファミリー製品でHCI_bbを使用し、DTMモードにアクセスする方法：この記事は2つのパートで構成されています。 HCI_bbバイナリをKinetis製品に書き込む方法。 R&S CMW270を使用してRF測定を実施する BLE HCIアプリケーションでトランスミッタ/レシーバのテストコマンドを設定する：この記事では、ユーザーがデバイスにシリアルコマンドを送信する方法を示す手順を説明します。 Bluetooth LE HCI ブラックボックス クイックスタートガイド：この記事では、シリアルコマンドを使用してユーザーが無線を制御できるようにする簡単な手順について説明します。

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. 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