NXP：蓝牙与信道探测天线 这些幻灯片是为马德里卡洛斯三世大学的欧洲天线学校准备的。内容： - 关于NXP和无线控制器 - 关于信道探测和NXP解决方案 - CS天线设计及功能测试 - CS天线阵列与CS定位

下一代功能安全架构 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 概述 S32x 下一代安全架构，涵盖 ASIL B 至 ASIL D。有哪些新功能以及我们如何更好地为客户提供全套安全附属品，包括 MCU HW、SW 和 SBC HW。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 概述 S32x 下一代安全架构，涵盖 ASIL B 至 ASIL D。有哪些新功能以及我们如何更好地为客户提供全套安全附属品，包括 MCU HW、SW 和 SBC HW。

HMB-N1937 接続デバイス用のAndroidベースのBrillio OSの紹介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Brilloは、Androidをベースにした軽量OSで、オープンで拡張性があり、安全な小さなフットプリントを備えたコネクテッドデバイス向けです。Brilloは、Androidプラットフォームを接続されているすべてのデバイスに拡張するため、セットアップが簡単で、相互に連携したり、スマートフォンとシームレスに連携したりできます。Googleの通信API「Weave」が付属しており、Brilloデバイスが相互に通信して交換したり、データをクラウドに保存したりするのを簡単に行うことができます。このクラスでは、Brillo と、NXP が Google と協力して Brillo を i.MX 6UltraLite プロセッサやその他のプラットフォームに導入した方法を紹介します。 ビデオプレゼンテーションを見る <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Brilloは、Androidをベースにした軽量OSで、オープンで拡張性があり、安全な小さなフットプリントを備えたコネクテッドデバイス向けです。Brilloは、Androidプラットフォームを接続されているすべてのデバイスに拡張するため、セットアップが簡単で、相互に連携したり、スマートフォンとシームレスに連携したりできます。Googleの通信API「Weave」が付属しており、Brilloデバイスが相互に通信して交換したり、データをクラウドに保存したりするのを簡単に行うことができます。このクラスでは、Brillo と、NXP が Google と協力して Brillo を i.MX 6UltraLite プロセッサやその他のプラットフォームに導入した方法を紹介します。 ビデオプレゼンテーションを見る スマートホーム&ビル

LPCXpresso IDE - Latest Release : v8.2.2 To download installers for all platforms, please visit: http://www.nxp.com/lpcxpresso   For installation and migration hints and tips, please visit: Migrating to a new version of LPCXpresso IDE   Current release: LPCXpresso 8.2.2 (build 650) September 2016   Changes in this release include: Upgraded GNU tools to ARM launchpad GCC 5 update 2 Fixed issues with debugging FreeRTOS applications Fixed issue with startup code generated by the New Project Wizard for LPC177x_8x family Latest LP18xx/43xx LPCOpen packages included in Examples : https://community.nxp.com/community/lpc/blog/2016/09/02/lpc43xx-lpcopen-updates-are-here  New LPC8xx series "code bundles" added to Examples : LPC8xx family code example bundles  Previous releases: LPCXpresso 8.2.0 (build 647) July 2016   Changes in this release include: Upgraded GNU tools to ARM launchpad GCC 5 update 1 Updated supported C/C++ dialects in IDE preferences and wizards Fixed issue with optimization level of CM4/HardABI Redlib C library build Fixed issue with Redlib strncasecmp() function incorrectly matching for some input strings Corrected size of third RAM bank from 32KB to 16KB on LPC1820, LPC1810 and LPC18S10 Fixed issue causing some peripheral registers not to be displayed debugging LPC5411x MCUs Target CPU automatically selected if possible when debugging multicore MCUs, based on project's CPU settings New "Resume all" and "Pause all" buttons for multicore debug sessions Enabled disassembly view to show opcodes by making GDB alway return opcodes when CDT requests disassembly information. Fixed backtrace issue when debugging inside interrupt handlers Fixed issue with IDE failing to use selected GDB when debug launch configuration modified to use different executable Resolved Mac OS X specific issue with USB reenumeration which could cause a Linkserver crash Fixed issue where flash driver could start with incorrect XPSR and improved error reporting Added support for additional devices in SPIFI flash drivers Added SPIFI flash driver for use with LPC40xx family (see FAQ: LPC40xx SPIFI Flash Driver ) Updated LPC-Link2 CMSIS-DAP firmware to allow SWO Trace and power measurement to run at the same time. Also to provide an alternative firmware variant that provides higher priority for serial-VCOM data Fixed issue with SWO Trace which could trigger IDE crash if trace collected for long period of time Improved SWO Performance Counters view Fixed a Power measurement buffering issue which could result in upto 20 samples per 3k being overwritten with newer data.   LPCXpresso 8.1.4 (build 606) Mid March 2016   Changes in this release include: Fixed issue with some debugger writes to memory silently failing LPCXpresso 8.1.2 (build 603) March 2016   Changes in this release include: Fixed issue with IDE failing to boot debug Linkserver on certain non-English Windows variants Fixed issue triggering GDB to occasionally crash when debugging interrupt handlers Upgraded Eclipse to Mars SR2 (4.5.2) and CDT 8.8.1   LPCXpresso 8.1.0 (build 597) February 2016   Changes in this release include: Upgraded GNU tools to ARM launchpad GCC 5 Added support for LPC5411x devices Updated LPC-Link2 CMSIS-DAP firmware, providing probe serial number support and additional power measurement functionality Support for debugging via multiple LPC-Link2 probes concurrently using the latest CMSIS-DAP probe firmware All Cortex-M debug connections are now made via Redlink LinkServer Project wizard mechanism updated to add -fno-common compiler option and -print-memory-usage linker option to new projects IDE no longer compares Freemarker linker script with a linker script created by the pre-LPCXpresso IDE v7.90 linker script generator Makefile projects now correctly save MCU settings, including memory configuration and flash drivers (required for debugging) "Average Power" view added to compliment existing "Power Measurement Tool" view (for use with latest CMSIS-DAP firmware on LPCXpressoV3 boards) Fixed issue with GUI / command-line flash programmer when programming images with certain complex layouts Fixed issue when connecting in attach mode to LPC18xx/LPC43xx projects that use the Generic SPIFI flash driver Old SPIFI flash drivers for LPC18xx/LPC43xx removed and replaced by copies of the Generic SPIFI driver Documentation restructured, splitting the old User Guide up into several manuals Resolved issues with LPC-Link1 booting on Mac OS X 10.11 El Capitan.The use of Mac OS X 10.11.3 or later is recommended LPC-Link2 Redlink firmware is no longer provided or supported. Use the default CMSIS-DAP firmware instead "Red Trace" (SWO Trace via Red Probe+) is no longer supported. Use SWO Trace via LPC-Link2 instead   LPCXpresso 8.0.0 (build 526) November 2015   Changes in this release include: Upgraded Eclipse to Mars SR1 / CDT 8.8 (plus Java 1.8) Upgraded GNU tools to ARM launchpad GCC 4.9 update 3 Support for multiple flash drivers within a single project Generic SPIFI flash driver source project debug build fixed so that it will execute on parts with internal flash (and less RAM) SWO ITM Trace Console View added to provide printf support via ITM Stimulus Port 0 Fixed an issue triggering error dialogs when the "Terminate All" option was used for non-multicore debug sessions Updated Redlink server/CMSIS-DAP LPC-Link2 firmware to support ISP reset of target MCU (requires target hardware support) Restart button now enabled on Mac OS X by default Note: Restart workaround on Mac OS X (due to an issue with GDB) may leave an unknown "thread" in the debug view - hit terminate again to remove this. Last release to support LPC-Link2 Redlink firmware. Use the default CMSIS-DAP firmware instead Last release to support "Red Trace" (SWO Trace via Red Probe+). Use SWO Trace via LPC-Link2 instead   LPCXpresso 7.9.2 (build 493) September 2015   Changes in this release include: Various fixes and improvements for  Freemarker linker script templates: Fixed link templates for LPC29xx and LPC3xxx Added '__base...' symbols for each memory region Fixed reporting of template errors in headless builds Corrected base address of SRAM2 block for LPC1517/47 Fixed issue with multicore symbols being defined by the IDE for non-multicore parts in some circumstances Improved handling of debug termination to allow target to clean up Instruction trace and SWO trace updated to avoid conflicts when both are trying to use DWT comparators SCT code generation updated to support latest LPCOpen register names Fixed rare issue with creating activation serial number on Linux hosts The use of LPC-Link2 Redlink firmware is now deprecated, and support will be removed in a future LPCXpresso IDE release. Use the (now default) CMSIS-DAP firmware instead The use of "Red Trace" (SWO Trace via Red Probe+) is now deprecated, and support will be removed in a future LPCXpresso IDE release. Use SWO Trace via LPC-Link2 instead   LPCXpresso 7.9.0 (build 455) July 2015   Changes in this release include: Initial support for Windows 10 Upgraded GNU tools to ARM launchpad GCC 4.9 update 2 New Generic SPIFI flash driver mechanism, which will autoconfigure based on SPIFI device detected in target system Enhanced managed linker script template mechanism Known as Freemarker linker script templates Simplifies projects which relocate code from Flash to RAM Support for generating LPC MCU vector table checksums directly in the image, using the startup file and linker script "Active Config" is now the default for the indexer Fixes to Multicore projects Fixed data sections placement Slave image now has bss and noinit sections removed, as they are not required Fixed an issue that was preventing MTB trace with LPC82x parts Extended CMSIS-DAP JTAG support (for Cortex-M parts) to include Keil ULINK2/ULINK-ME probes   LPCXpresso 7.8.0 (build 426) June 2015   Changes in this release include: New SWO Interrupt Trace Graph and Table views (Pro Edition only) LPC-Link2 will now soft-boot with CMSIS-DAP rather than Redlink firmware by default Improved selection of JTAG vs SWD connections - requires launch configurations to be recreated Fixed an issue with flash programming occasionally failing to initialize or complete Fixed an issue with debugging of LPC11A parts through LPC-Link2 Fixed a problem with semihosting output for C++ projects Fixed an issue with reading and displaying unaligned data from the target Fixed an issue with making an attach-only debug connection Fixed an IDE hang if resuming a debug session mid-way through editing a peripheral register Performance improvements when displaying registers Optimized display of Peripherals when editing fields or registers It is now possible to add miscellaneous command-line options to the GUI flash programming dialog Fixed an issue with the reset target option not working when flash programming an AXF file Added path when disambiguating Launch Configurations Wizards now generate liblinks.xml 'smart update' file in library projects, which will still work after a project is renamed Code generated by LPCOpen project wizards now calls SystemCoreClockUpdate() in all cases, not just when linking to a board library For multicore-capable systems an LPCOpen project wizard-generated main.c now only calls Board_Init() for a master core and not for slaves. LPC43xx wizards now generate code using new-style multicore defines Fixed an issue with SymbolViewer not being able to display source for C++ symbols De-cluttered the toolbar by removing the duplicate quickstart toolbar (this can be re-enabled using the User Interface Enablement preferences)   LPCXpresso 7.7.2 (build 379) March 2015   Changes in this release include: Added support for LPC18Sxx and LPC43Sxx parts Upgraded Eclipse to Luna SR2 (4.4.2) and CDT 8.6 Added Technology Preview of SWO Trace support with LPC-Link2 (Redlink) Further major improvements to Flash Download performance Added "Terminate, Build and Debug" Quickstart button SPIFI flash drivers now check for recognised parts CMSIS-DAP support extended to allow multi-core and JTAG debug connections (where supported by probe implementation) Fixed issue with managed linker script for multi-core projects which caused misalignment of slave data section Added support for M4 multi-core projects to use HardABI floating point variant Redlib realloc() fixed to handle heap memory becoming exhausted The LPCXpresso54102 board Power measurement tool is now included   LPCXpresso 7.6.2 (build 326) February 2015   Changes in this release include: Fixed managed linker scripts for GCC 4.9 NewlibNano library names Stopped tracking project selection in Symbol Viewer Added toolbar button for hide/show Red Trace views. Note that a restart of LPCXpresso is required after showing these views before Red Trace can be used. Fixed problem with MCU settings not being saved if changed by using the Quickstart Panel's Edit project settings button Display target chip and core type alongside executable name in Debug View   LPCXpresso 7.6.0 (build 321) January 2015   Changes in this release include: Upgraded GNU tools to ARM launchpad GCC 4.9 Significantly improved flash programming performance across all Cortex-M targets and debug probes Support for additional SPIFI flash parts based on latest LPCSPIFI Library v1.03 Added new Symbol Viewer feature to display the symbols in an object/library/executable Redlink firmware enhanced to improve performance and provide bridging capabilities similar to latest CMSIS-DAP Managed linker scripts now contain start and end symbols for all data and bss sections Improved highlighting of changed registers when single stepping Change colors of stub console messages - dark yellow for warnings and green for information Added support for m0 small-multiplier Redlib now implements single precision fmodf() in math.h Redlib free() will now coalesce with any consecutive free blocks Fixed problem with assembler -D option when selecting No library headers Fixed issue with Memory Configuration Editor when merging memory blocks during import Fixed issue with semihosting SEEK operation (affecting Redlib and Newlib fseek()) always resetting to the start of the file Fixed linker script generation for Internal builder Fixed display of second core index for LPC5410x part (from 16->1) Fixed Build All Projects if no project selected Fixed target connection sequence to avoid timeout when downloading very large applications   LPCXpresso 7.5.0 (build 254) November 2014   Changes in this release include: Upgraded Eclipse to 4.4.1 ('Luna SR1') and CDT to v8.5.0. Upgraded GNU tools to ARM launchpad GCC 4.8 update 3. Added support for LPC5410x devices. Default optimisation level reverted to -O0 (rather than -Og) for Debug builds. LPC18/43 project wizards now provide access to Memory Configuration Editor. Add ability to Merge memory configurations and join contiguous memory blocks in Memory Configuration Editor. Enhanced link-time-optimisation (LTO) options. Disable "Set library type" on projects where it is not applicable. Added a default workspace location for Linux. Redlib string.h functions extended to include implementations of (non-ANSI-standard) strcasecmp() and strncasecmp(). Fixed very rare cause of hard fault in Redlib malloc(). Prevented changing Peripheral registers while target is running. Fixed a problem preventing debug display of arrays within a structure within a union. Fixed issue with viewing of byte-sized peripheral registers, such as CM3/CM4 NVIC priority registers. Fixed issue with writing to byte-sized variables/registers. LPCXpresso 7.4.0 (build 229) September 2014   Changes in this release include: Support for LPC82x family. Upgraded to latest Eclipse release (4.4 'Luna') and CDT 8.4. This fixes a number of display problems with complex datastructure variables. Several improvements have been made to the Opcode display in the disassembly view. Opcodes can be displayed by right-clicking in the disassembly view margin and selecting 'Show Opcodes'. Eclipse Luna requires Java 7, which is installed on all platforms in the 'jre' subdirectory. This is independent of the 'System' Java installation, which is not affected. Disabled inline editing of the Pre/Post build steps and forced editing via a dialog. Peripherals displayed in Memory View now display hexadecimal, decimal, and binary in hover for 'numeric' values. Tidied up the toolbar to remove little-used buttons (which are still available in the Quickstart panel). Added new preprocessor defines for multicore projects. LPCOpen Project wizards will now prepopulate the chip library name where possible. Cleaned up inconsistencies in various Redlib header files. Redlib memcpy and related functions now avoid use of unaligned LDR/STR instructions on Cortex-M3/M4. Fixed various single-precision Redlib math.h functions. Fixed a peripheral problem with LPC11U6x/11E6x GPIO word registers. LPCOpen code bundles are now shipped inside the Examples subdirectory, though users are recommended to check LPCware.com for the latest versions. Absolute rather than relative paths are now used in the debugger for breakpoints by default for new workspaces. The default make command is now 'make -r', which should reduce build times, particularly on Windows. Added new Quick Settings menu for changing a project's FP type. Fixed a flash programming issue for LPC15x7 parts. Fixed a flash programming issue for certain LPC21xx/22xx parts. Updated SPIFI flash drivers based on LPCOpen 'LPCSPIFI' library to use v0.07, adding drivers for more SPIFI devices Improved support for the 'Dark' Theme. Now possible to modify the start address of the heap without modifying linker scripts/templates Mac OS X 10.7 (Lion) is no longer an officially supported platform. LPCXpresso may continue to work on Mac OS X 10.7, but this can no longer be guaranteed. LPCXpresso is no longer tested on Mac OS X 10.7.   LPCXpresso 7.3.0 (build 186) July 2014   Changes in this release include: Upgraded GNU tools to ARM launchpad GCC 4.8 update 2 Run->Debug As... now works correctly for MCU targets Fix problem that caused CMSIS-DAP to not be available for some targets Correctly terminate Redlink Server after using the Flash Utility Updated LPC15xx startup code generated by new project wizards to match interrupt handler names used by LPCOpen. LPC43xx M0 startup code no longer references systick (which is only implemented on M4 cpu in LPC43xx MCUs, not M0 cpus). Fixed issue with LPC43xx (Cortex-M0 basic) wizards failing to create startup file. Quickstart Debug button now respects the build setting in the launch configuration Additional LPC18/43 SPIFI flash drivers supplied, based on LPCOpen lpcspifilib. C Library memory allocator no longer checks new heap end against current stack pointer. New "boot_link1" and "boot_link2" scripts available on all platforms for downloading probe firmware from command line. Peripheral rendering "Refresh" option now forces re-read from target. Peripheral register fix for LPC15xx GPIO port word pin registers.   LPCXpresso 7.2.0 (build 153) May 2014   Changes in this release include: Improvements to reliability of Redlink server connections Add __MULTICORE_type pre-processor symbol to compiler for multicore projects Project wizards now place default main() into projname.c rather than main.c On Mac OS X, prevent occasional hang during Debug Probe discovery On Windows, the debug drivers are now built with Visual Studio 2013 to increase compatibility with latest version of Windows. Remove crt_directory.xml to build parts database dynamically at runtime     LPCXpresso 7.1.1 (build 125) April 2014   This is a bug fix release that solves a problem found in the initial release of v7.1.0. Fixed in this release are: Fix problem affecting LPC-Link2 debug connections to Cortex-M0+ cores Fix regression preventing debugging with CMSIS-DAP Fix for a Red State UI regression which prevented users from graphically adding an output pin to a signal     LPCXpresso 7.1.0 (build 122) April 2014   Changes in this release include: Upgraded IDE to Kepler SR2 and CDT 8.3 Upgraded GNU tools to ARM launchpad GCC 4.8 update 1 Fixed problem with C/C++ indexer being disabled on startup Further reliability improvements with LPC-Link2 connections Default optimisation level is now -Og for Debug builds Improvements to Create Binary option to allow multiple commands (for example checksum the created binary) Improved NVIC/SCB peripheral displays Added preference to display peripheral registers with leading zeroes Added preference for the array "chunk" size in variable and expression views Fixed issue with instruction trace when restart carried out Redlib limits.h updated for when compiler configured to treat unspecified chars as signed (instead of default of unsigned) Redlib now implements integer only version of vprintf() as well as floating point compatible version The wrench overlay icon is now correctly displayed on a file/folder with local build settings Prevent a Redlink Server debug session on a target that is already being debugged Updated RAMFUNC definitions provided by cr_section_macros.h Note: Due to the imminent discontinuation of support by Microsoft, Windows XP is no longer an officially supported platform. LPCXpresso may continue to work on Windows XP but this can no longer be guaranteed. LPCXpresso is no longer tested on Windows XP.   LPCXpresso 7.0.2 (build 102) March 2014   Note - there is a know issue with the indexer in v7.0.2. This can be fixed by a simple change to a configuration file. For details see here.   Changes in this release include: Fixed problem with setting breakpoints on Windows with source paths containing spaces Fixed problem with Memory Configuration editor losing changes Debugging of LPC12xx and LPC11A02/LPC11A04 are now supported with LPC-Link2 mproved reliability of LPC-Link2 when downloading large images SCT code generator version updated to 2.6: switched from using register names that are undocumented on some parts, e.g. CAP_L[0] to CAP[0].L. Users should regenerate their SCT code Managed linker script support for placing specific functions into RAM Fixed display of memory if first displayed when target is executing   LPCXpresso 7.0.0 (build 92) February 2014   Major new release with features including: Support for latest NXP MCUs (including LPC1500) New release of the GNU compilers – v4.8.3. Includes new ‘general’ optimization level, -Og. This new optimization level, aims at providing fast compilation, a superior debugging experience and reasonable runtime performance. Adds Link Time Optimization (LTO). This allows all the different compilation units that make up a single executable to be optimized as a single module (not suitable for debugging). Inclusion of a new small-footprint variant of the Newlib C and C++ library, known as NewlibNano. Use of this library can result in significantly smaller code size, especially of C++ applications. Note that further details on the use of these new options can be found in the compiler documentation that is provided in the IDE help system.] New release of the base Eclipse IDE – Kepler (v4.3). The Managed Linker script mechanism has been extended to support the features of new GNU compiler. 'New project' wizards can now invoke import wizards directly to allow importing of library projects required in creating of new project. gdbserver debug connections enabled -> Enables use of Segger J-Link.   LPCXpresso 6.1.4 (build 194) January 2014 Changes in this release include: Added support for LPC11U6x. Fixed profile and interrupt trace on LPC13xx (12-bit ADC) parts Fixed regression introduced in 6.1.2 where a wizard-generated dual-core slave startup file failed to compile Removed display of CRP option in the wizard for creating dual-core slave apps Fixed various file resource leaks in the IDE; ensure temporary files are cleaned up on exit Fixed linker script generation for LPC1102/1104 Startup files fixed for various parts to prevent name mangling issues in C++ projects Corrected flash driver references for certain LPC11A, LPC11E, LPC11xxLV parts Redlink connections now display correct debug protocol in debug log In project wizards, LPCOpen wizards are listed first if available LPCOpen project wizards for LPC13xx, LPC175x_6x, LPC177x_8x, LPC407x_8x now provided LPCOpen packages can now be browsed from the Import Project page CGU related updates to LPC18/43 CMSIS driver libraries (Windows) Rebuilt version of make provided (Linux) Added new udev rules for CMSIS-DAP probes   LPCXpresso 6.1.2 (build 177) December 2013 Changes in this release include: Added support for LPC11x37H parts including support for IOHandler. Added LPCOpen V2 project wizards for LPC18 and LPC43 families Fixed issue where not all slaves were displayed in the linker properties of a MultiCore project Added missing breakpoint/watchpoint menu items while debugging in the Develop perspective Fixed issue where Watchpoints not trapping with Redlink Fixed issue where Hard fault not trapped / VectPC updated with Redlink Fixed issue with Cycle count registers broken on LPC43xx using an LPC-Link2 Fixed failure of LPC12 project wizards to set "__DISABLE_WATCHDOG" symbol On Windows 8, use the LPC-Link1 WinUSB driver instead of HID   LPCXpresso 6.1.0 (build 164) Late October 2013 Changes in this release include: Introduced Red Trace SWV support for Red Probe+ Fixed issue connecting to a third core when debugging LPC4370 Extended range of prebuilt LPC18/43 SPIFI flash drivers Fixed problem with Watchpoints not being cleared Corrected debug startup with Red Probe+ when more than one FTDI-based device is present Fixed possible null pointer exception after editing memory configuration Fixed lost highlight when using keyboard to scroll through MCU selection Windows) Updated dfu-util/libusb to support additional USB3 hubs   LPCXpresso 6.0.4 (build 159) Early October 2013 Changes in this release include: Added support for ULink-2 CMSIS-DAP interface Fixed display of C++ global variables in Expression view Prevents use of JTAG for CMSIS-DAP connections (it is not currently supported) Added missing launch shortcut preventing display of correct launch config in Run/Debug Settings dialog Stopped display of debug probes when deleting JTAG configuration Fixed display of multiple debug probes reported by Redlink Server "Quickstart->Build all" now works when no projects are selected Fixed problem with memory configurations not being stored correctly Fixed Redlib problem with free() of null pointer Added c++0x and gnu++0x C++ compiler dialect options   LPCXpresso 6.0.2 (build 151) September 2013 LPCXpresso Forum

FreeRTOS 与 MQX RTOS 的快速概述 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> FreeRTOS 与 MQX RTOS 的快速概述 MQX实时操作系统是专为单处理器、多处理器和分布式处理器嵌入式实时系统设计的。飞思卡尔半导体公司在其微处理器中采用了该软件平台。这包括 Kinetis、Coldfire、PowerPC、ARC、ARM、StrongARM、xscale CPU。MQX RTOS 的主要特点是可扩展的大小、面向组件的架构和易于使用。 FreeRTOS 是一种流行的嵌入式设备实时操作系统内核，已移植到 35 种架构。它在 GPL 下分发，但有一个可选例外。FreeRTOS 占用空间非常小，开销很低，执行速度非常快。内核本身仅由三或四个 C 文件组成。最少 4-8k 字节闪存。 类似功能：[待完成] 任务、事件、信号量、互斥量、消息队列、空闲省电                                                                  Freertos 的独特功能： 1 任务通知：每个 RTOS 任务都有一个 32 位通知值，该值在创建 RTOS 任务时初始化为零。RTOS 任务通知是直接发送给任务的事件，可以解除对接收任务的阻塞，并可选择更新接收任务的通知值。 2 递归互斥锁：递归使用的互斥锁可以被所有者反复“获取”。直到所有者为每次成功的 xSemaphoreTakeRecursive() 请求调用 xSemaphoreGiveRecursive() 之后，互斥锁才会再次可用。例如，如果某个任务成功“获取”同一个互斥锁 5 次，则该互斥锁将无法供任何其他任务使用，直到该任务也将互斥锁“归还”5 次为止。 3 堆栈溢出钩子/通知：每个任务维护自己的堆栈。任务堆栈使用的内存在任务创建时自动分配，并由传递给 xTaskCreate() API 函数的参数确定大小。堆栈溢出是导致应用程序不稳定的一个常见原因。因此，FreeRTOS 提供了两种可选机制，可用于协助检测和纠正此类事件 4 延迟中断处理：从应用程序中断服务程序中使用，将功能的执行延迟到 RTOS 守护进程任务。提供了一种机制，允许中断直接返回到随后将执行挂起功能的任务。这使得回调函数能够与中断连续执行 - 就像回调在中断本身中执行一样 5 多个对象上的阻塞：队列集是 FreeRTOS 的一项功能，它使 RTOS 任务能够在同时从多个队列和/或信号量接收时阻塞（挂起）。队列和信号量被分组为集合，然后，任务不再阻塞在单个队列或信号量上，而是阻塞在集合上。 MQX 的独特功能： 1 基于所有权的资源破坏：[待完成] 2 名称服务：任务可以将一个 32 位数字与一个字符串或符号名称关联起来。MQX RTOS 将这种关联存储在名称数据库中，该数据库中的所有任务 处理器可以使用。数据库避免使用全局变量。 3 处理器间通信：应用程序可以在多个处理器上同时运行，每个处理器上都有一个 MQX RTOS 的可执行映像。图像使用由内存或通过处理器间通信的通信链路传输的消息进行通信和协作。每个图像中的应用任务不必相同，而且实际上通常是不同的。 4 看门狗：看门狗是可选组件，可让用户检测任务级别的任务饥饿和死锁情况。 5 任务队列调度：您可以使用任务队列来显式调度任务，或创建更复杂的同步机制。由于任务队列提供的功能很少，因此速度很快。应用程序可以在创建任务队列时指定先进先出 (FIFO) 或循环 (Round Robin) 调度策略。

Importing a Wrapped Key Blob Using PSA Crypto APIs on RW612 Introduction In a previous article, we demonstrated how to import an RFC3394-wrapped key blob into ELS by manually performing the following operations: Deriving NXP_DIE_KEK_SK using CKDF-SP800-108 Importing the wrapped blob with mcuxClEls_KeyImport_Async() Deleting the temporary KEK after import While this approach provides full visibility into the underlying ELS operations, applications using the PSA Crypto API can achieve the same result with significantly less code. This article demonstrates how to use psa_import_key() together with PSA_KEY_LOCATION_S50_RFC3394_STORAGE to import a wrapped key blob stored in OTP. The PSA Oracle driver transparently handles the secure key loading sequence, including KEK derivation, key unwrapping, ELS slot management, and cleanup. Prerequisites FRDM-RW612 Key blob wrapped using RFC3394 format using HSM_STORE_KEY Key blob programmed to OTP fuses using LoadKeyBlob command. Required Headers: #include "mcux_els.h" #include "psa/crypto.h" #include "mcuxClPsaDriver_Oracle_Interface_key_locations.h" #include "fsl_romapi_otp.h" Step 0 – Read the Wrapped Key Blob from OTP The example reads the blob directly from OTP memory. static psa_status_t read_blob_from_otp(uint8_t *blob_data, uint32_t blob_length, uint32_t starting_fuse_index) { status_t otp_status; uint32_t num_fuse_words = blob_length / 4u; PRINTF("Reading %d fuse words starting from index %d\n", num_fuse_words, starting_fuse_index); otp_status = otp_init(DEFAULT_SYSTEM_CLOCK); if (otp_status != kStatus_Success) { PRINTF("Error: otp_init failed: 0x%x\n", otp_status); return PSA_ERROR_HARDWARE_FAILURE; } for (uint32_t i = 0u; i < num_fuse_words; i++) { uint32_t fuse_word = 0u; otp_status = otp_fuse_read(starting_fuse_index + i, &fuse_word); if (otp_status != kStatus_Success) { PRINTF("Error: Failed to read fuse word %d, status: 0x%x\n", starting_fuse_index + i, otp_status); return PSA_ERROR_HARDWARE_FAILURE; } /* Store fuse word as 4 bytes in little-endian order */ blob_data[i * 4u + 0u] = (uint8_t)((fuse_word >> 0u) & 0xFFu); blob_data[i * 4u + 1u] = (uint8_t)((fuse_word >> 8u) & 0xFFu); blob_data[i * 4u + 2u] = (uint8_t)((fuse_word >> 16u) & 0xFFu); blob_data[i * 4u + 3u] = (uint8_t)((fuse_word >> 24u) & 0xFFu); PRINTF(" Fuse[%d] = 0x%08X\n", starting_fuse_index + i, fuse_word); } PRINTF("Blob data read from OTP successfully\n"); return PSA_SUCCESS; } Each fuse word contains four bytes.   These words are assembled into a contiguous buffer: blob_data[i * 4 + 0] = (fuse_word >> 0) & 0xFF; blob_data[i * 4 + 1] = (fuse_word >> 8) & 0xFF; blob_data[i * 4 + 2] = (fuse_word >> 16) & 0xFF; blob_data[i * 4 + 3] = (fuse_word >> 24) & 0xFF; The resulting buffer contains the RFC3394 wrapped key. Step 1 – Configure PSA Key Attributes Before importing the blob, PSA key attributes must describe how the key should be managed. The most important configuration is the key location: psa_set_key_lifetime( &attributes, PSA_KEY_LIFETIME_FROM_PERSISTENCE_AND_LOCATION( PSA_KEY_PERSISTENCE_VOLATILE, PSA_KEY_LOCATION_S50_RFC3394_STORAGE)); The PSA_KEY_LOCATION_S50_RFC3394_STORAGE location informs the Oracle driver that: The provided data is an RFC3394-wrapped key blob. The blob requires unwrapping before use. NXP_DIE_KEK_SK must be derived automatically during key loading. In this example we used an AES 128-bit key. The key type and size must match the wrapped key: psa_set_key_type(&attributes, PSA_KEY_TYPE_AES); psa_set_key_bits(&attributes, 128); Usage permissions are then assigned: psa_set_key_usage_flags( &attributes, PSA_KEY_USAGE_ENCRYPT | PSA_KEY_USAGE_DECRYPT); Finally, specify the algorithm: psa_set_key_algorithm( &attributes, PSA_ALG_ECB_NO_PADDING); Step 2 – Import the Wrapped Blob The blob is imported using a single PSA API call: psa_import_key( &attributes, blob_data, blob_length, &key_handle); For developers familiar with the low-level ELS implementation, this single call effectively replaces: derive_nxp_die_kek_sk() import_wrapped_key_blob() delete_key_from_slot() At this point, PSA stores the wrapped blob and returns a key handle: psa_key_id_t key_handle; The returned handle is subsequently used for cryptographic operations. Next Steps At this point, the wrapped key blob has been successfully imported into the target ELS key slot, and the temporary  NXP_DIE_KEK_SK  has been removed. The imported key is now available for use by ELS-protected cryptographic operations without exposing the underlying key material to application software. The next step is to validate the imported key by performing the operation it was provisioned for.  For this example, we used AES-ECB encryption: psa_cipher_encrypt( key_handle, PSA_ALG_ECB_NO_PADDING, plaintext, sizeof(plaintext), ciphertext, sizeof(ciphertext), &ciphertext_length); Step 4 – Cleanup Once the key is no longer required, destroy it using: psa_destroy_key(key_handle); This releases the PSA key object and allows the Oracle driver to clean up any associated secure resources. Unlike the low-level ELS implementation, the application does not need to explicitly manage ELS keyslots. PSA vs Direct ELS Implementation Direct ELS API PSA Crypto API Derive KEK manually Automatic Import blob manually Automatic Manage keyslots Managed by Oracle Delete temporary KEK Automatic Greater control Simpler application code Higher implementation effort Faster integration Both approaches ultimately leverage the same secure hardware mechanisms within RW612. The PSA approach simply abstracts the underlying ELS operations behind a standardized cryptographic interface.

i.mxrt1176 不带 DQS 的最大 NOR 闪存速度 我正在尝试更好地了解连接到 FlexSpi2 的串行 NOR 速度限制，因为我们遇到了性能问题。 在一篇关于使用不带 DQS 引脚的 FlexSPI 的 1060 系列的知识库文章中，似乎将 serialClkFreq 限制为 60MHz。 但是，对于 RT1176，我们已经成功地在 SDR 模式下以 100MHz 运行了 或非 Flash，尽管未能以 120MHz 启动，但看似没有问题。 同样，DDR 的频率为 50MHz，而 60MHz 则失效。 第"30.3.17.2 节 接收时钟源特性" 简单说明了不带 DQS 引脚的最大频率"最低" 。 是像 1060 系列知识库文章提到的那样将接口限制在 60MHz 还是以 100MHz 运行 SDR 模式符合规格？还是以 50MHz 运行 DDR 模式更好？ 在没有 DQS 的情况下，有什么优化性能的技巧吗？ https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/Everything-you-need-to-know-about-DQS-pin-on-FlexSPI-and-SEMC/ta-p/1977399 Re: i.MXRT1176 Max NOR flash speed without DQS 你好@anbn、 感谢您对 NXP MIMXRT 系列的关注！ 如果使用 MCR0[RXCLKSRC]=0x0 （内部环回，不使用 DQS 引脚），数据手册限制在 SDR 模式下为 60 MHz，在 DDR 模式下为 30 MHz。因此，在这种模式下，100 MHz SDR 不在公布的规格范围内。 参考手册将 RXCLKsrc=0x0 标记为 “最低”， RXCLKsrc=0x1 标记为 “中”；实际频率限制在数据表中定义。数据表指定 RXCLKsrc=0x0 为 60 MHz SDR / 30 MHz DDR， RXCLKsrc=0x1 为 133 MHz SDR。 如果使用 FlexSPi2 辅助引脚组，则该引脚组不提供 DQS 键盘，因此 ROM 启动仅支持低速读取。因此，此引脚选项不适用于高性能 XIP/启动 操作。 因此，如果您当前的主板连接没有可用的 DQS 焊盘，则应将其评估为 60 MHz SDR/30 MHz DDR。如果需要更高的读取性能，建议使用具有 DQS 的引脚组，并配置 RXCLKsrc=0x1 。 致以最诚挚的问候， Gavin

Using the HiFi DSP for Inferencing ML Models on i.MX RT Devices This article will describe how to use the HiFi modules found on certain NXP microcontrollers as an optional method for inferencing a model.  There are several ways of running a TFLite neural network model on NXP microcontrollers: Inference a model only using the main core of the device (CM33 or M7) MCX N i.MX RT1050 i.MX RT1060 i.MX RT1170 i.MX RT1180 i.MX RT595 i.MX RT685 i.MX RT700 Inference a model directly on the HiFi4 or HiFi1 core (on supported platforms) i.MX RT595 i.MX RT685 i.MX RT700 Use the Neutron NPU to accelerate inference of a model - with the CM33 controlling the NPU and acting as a fallback for any non-NPU supported layers i.MX RT700 MCX N Use the Neutron NPU to accelerate inference of a model - with the HiFi4 controlling the NPU and acting as a fallback for any non-NPU supported layers i.MX RT700   This article will cover options #2 and #4 which make use of the HiFi DSP module. Running a model on the HiFi4 (option #2) will be much faster than running a model just on the CM33/M7 (option #1). However using the NPU (options #3 and #4) will be significantly faster than only using the DSP due to the hardware optimizations that an NPU provides for neural network calculations. The exact performance gains will be model specific, and also depend on the layer(s) that may not have been converted to use the NPU as NeutronGraph nodes. The accuracy should remain the very similar regardless of method being used. Any type of TFLite neural network model can be ran on the HiFi1/HiFi4 as those DSP modules are just being used accelerate the neural network math that the model uses. CIFAR10 on i.MX RT700 using default MCUXpresso SDK projects: CM33: 105.925ms HiFi1*: 148.487ms HiFi4: 12.312ms NPU w/ CM33 Fallback: 1.048ms NPU w/ HiFi4 Fallback: 0.983ms *HiFi1 runs at 32MHz   Software requirements: Go to the Cadence i.MX RT700 or Cadence i.MX RT685 pages to download the following software. Xtensa Xplorer IDE License Key HIFI DSP Configuration File (NEWLIB) If using a HiFi4 example then download the HiFi4 license and DSP configuration files. Likewise, if using a HiFi1, then will need the HiFi1 license and DSP configuration files. Also you will need to download the Windows or Linux version of these files depending on which host OS you are using on your PC. Finally add the following global system variables which should be set based on the location that Xtensa Explorer was installed (assuming RT700 with HiFi4): XCC_DIR= \XtDevTools\install\tools\RI-2023.11-win32\XtensaTools XTENSA_CORE= rt700_hifi4_RI23_11_nlib MCUXpresso SDK HiFi ML Examples: There are several HiFi related examples in MCUXpresso SDK for i.MX RT700: tflm_cifar10 – Uses Neutron NPU to inference the CIFAR10 model and uses the CM33 as the fallback for any non-NPU operators. tflm_cifar10_hifi1 – Uses HiFi1 to inference the CIFAR10 model. Does not use the Neutron NPU tflm_cifar10_hifi4 – Uses HiFi4 to inference the CIFAR10 model. Does not use the Neutron NPU tflm_cifar10_hifi4_neutron – Uses Neutron NPU to inference the CIFAR10 model and uses the HiFi4 as the fallback for any non-NPU operators. tflm_label_image – Uses Neutron NPU to inference the CIFAR10 model and uses the CM33 as the fallback for any non-NPU operators. tflm_label_image_hifi4 - Uses HiFi4 to inference the Mobilenet model. Does not use the Neutron NPU When using the HiFi eIQ projects provided in MCUXpresso SDK, ensure that the SDK is: Located in a short filename path (ie C:\nxp\RT700), as an excessively long filename path can cause compile issues Directory path contains no spaces If using VS Code import as a Repository project instead of Free Standing. Ensure using at least MCUXPresso SDK 26.03 as there are several important fixes in the 26.03 release for HiFi4 projects Extending Memory Area in HiFi4 Examples for Larger Models: Open:  \boards\mimxrt700evk\eiq_examples\tflm_cifar10_hifi4_neutron\linker\hifi4\min-rt\ldscripts\elf32xtensa.x  And make modifications below to extend the memory used for models.  dsp_core_seg :  org = 20200000, len = 0x200000  dsp_core_ncache_seg :  org = 0x20400000, len = 0x180000  anthony_huereca_9-1783320725255.png   _memmap_mem_dsp_core_start = 0x20200000;  _memmap_mem_dsp_core_end   = 0x20580000;  _memmap_seg_dsp_core_start = 0x20200000;  _memmap_seg_dsp_core_max   = 0x20580000;    anthony_huereca_10-1783320808490.png  Ensure that the stack heap is at 0x2058_0000:    PROVIDE(__stack = 0x20580000);    _heap_sentry = 0x20580000;    anthony_huereca_11-1783320872686.png   Now larger models will compile successfully in Xtensa.    Then after copying in the compiled HiFi4 binary files into the MCUXpresso IDE project, modify source/dsp_config.h file to update the DSP_SRAM_ADDRESS:    anthony_huereca_12-1783321027565.png  Then clean and build the project.   HiFi Lab: See the attached lab document for more details on using the HiFi DSP modules to inference models.    

i.MX 8M Plus（Scarthgap）上的 HDMI EDID 4 块读取失败 您好， 我正在 Yocto Scarthgap 电路板支持包 上使用 i.MX 8M Plus，在尝试读取 4 个 HDMI EDID 块（块 0 到 3）时遇到了问题。 [环境] SoC:i.MX 8M Plus 电路板支持包/操作系统：Yocto Project Scarthgap（内核版本：lf-6.6.52） [问题描述]尝试读取所有 4 个 EDID 块时，系统无法从块 2 开始读取（段 1）。区块 0 和区块 1（0 段）读取成功，但读取操作随即失败。 [根本原因/分析]经过调试，我发现问题与段切换命令后使用的 DDC 地址有关： 要读取区块 2 和 3，必须正确执行区段切换命令。 切换网段后，驱动程序应使用标准 DDC 地址0xA0/0xA1（I2C 地址 0x50）读取实际 EDID 数据。 但是，驱动程序错误地尝试使用地址0x60/0x61（即段指针地址）读取数据，导致读取错误。 看来驱动程序错误地在随后的数据读取序列中重复使用了分段指针地址。 [问题] 这是 i.MX 8M Plus Scarthgap BSP 上的 HDMI/DDC 驱动程序中的已知问题吗？ 是否有任何现有的修补程序或变通方法来修复这种地址不匹配问题？ 如能提供需要修改的相关驱动程序代码的指导或指点，将不胜感激。 先行致谢。 Re: HDMI EDID 4-block read failure on i.MX 8M Plus (Scarthgap) 这是一个已知的问题吗？ 实际上是的。恩智浦社区上至少有一份先前的 i.MX8MP 报告指出，i.MX8MP 无法正确读取块 1 / 段 0 以外的 E-EDID，该报告特别指出用户应访问 drivers/gpu/drm/bridge/synopsys/dw-hdmi.c 进行调查。 是否有现成的变通办法？ 是的。据报道，一种解决方法是绕过 HDMI 内部 DDC 引擎，通过在设备树中设置 ddc-i2c-bus 来使用普通的 SoC I2C 控制器进行 DDC。恩智浦社区线程报告称，将 HDMI DDC 引脚重新复用到 I2C5 并使用 ddc-i2c-bus = <&i2c5>; 解决了 i.MX8MP 上的多块 E-EDID 读取问题。 是否已经有公共补丁？ 我在搜索结果中没有找到上游或 NXP 发布的公开补丁来专门修复你的 BSP 行的 dw-hdmi 中的这个 0x30 / 0x50 从属地址处理问题。公开可见的 dw-hdmi.c 代码仍然显示可以触发这种行为的 “从属地址取自第一条 I2C 消息” 逻辑。   如果你的主板布线允许，风险最低且已经报告的解决方法是将 HDMI DDC 从内部 dw-hdmi I2C 引擎移出常规 SoC I2C 控制器上。在 i.MX8MP 上，报告了一种解决方案 &i2c5 { 时钟频率 =<100000> ； pinctrl-names ="默认" ； pinctrl-0 =<& pinctrl_i2c5> ； status ="okay" ； };   &hdmi { ddc-i2c-bus = < & i2c5 >; status ="okay" ； }; HDMI DDC 引脚与 I2C5_SCL / I2C5_SDA 复用。恩智浦社区线程中的用户报告说，这一变更解决了 i.MX8MP 上的多块 E-EDID 读取问题。

PN76xx - ULPCD Checklist As described in ES_PN7642 and AN15028 , the IC might rarely enter into a non-responsive state during ultra low-power card detection (ULPCD).  If there is a suspicion that the IC enters this state, NXP has provided a checklist to verify and confirm it. See the checklist in the attachment.  Tomas_Parizek_0-1779878865040.png NFC Controller Solutions

FRDM-MCXN947：Ee(42) 刷新 tflm_modelrunner 后无法连接到内核 刷新 tflm_modelrunner SDK 示例（FreeRTOS + lwIP，定义 USE_RTOS）后，我的 FRDM-MCXN947 不再响应 SWD。LinkServer v25.6 和 MCU-Link V3.128 报告 Ee(42)。所有操作（包括大量擦除）都无法连接到核心。在 “设备管理器” 中可以正确检测到 MCU-Link 探测器。按下 SW3+RESET 时，Windows 会检测到 USB 枚举，但未安装驱动程序，blhost 报告未找到任何设备。 我怎样才能找回板？ 更新：我能够在 Linux 上下载 led_blinky 示例，但在 Windows 10 上问题依然存在。 此外，在这两个操作系统上，我通常会收到以下警告： " 项目是为设备 MCXN947 配置的，但选定的探测器报告已连接到设备 MCXN947VDFT。你确定要继续吗？" 第一次尝试下载程序时（不知道是否与此有关）。 Re: FRDM-MCXN947: Ee(42) Could not connect to core after flashing tflm_modelrunner 最新情况--决议 通过从 Windows 设备管理器中卸载 MCU-Link 设备条目并允许 Windows 在重新连接时重新枚举这些条目，该问题得到了解决。 具体而言，删除了两个条目：通用串行总线设备下的 " MCU-LINK FRDM-MCXN947 CMSIS-DAP "，以及端口 (COM & LPT) 下相应的 MCU-Link vCom 端口。重新连接 USB 电缆后，Windows 自动重新安装了这两个驱动程序，LinkServer 可以正确打开探针。 根本原因似乎是Windows中USB设备状态损坏，很可能是在之前使用tflm_modelrunner固件（FreeRTOS + LwIP）的会话中触发的。该探针在系统中可见并被正确枚举，但其句柄无法被 redlinkserv.exe 打开，导致在所有操作（包括大量擦除、闪存和 gdbserver）中出现 Ee(42)。重新安装集成开发环境，替换 redlinkserv.exe、清除 USB 注册表项也无法解决这个问题。只有从设备管理器重新枚举设备才能解决问题。

VS code extension update broke RTOS viewer Hello, Until now we were using vscode tool version 1.9.20 (old), and we were using https://marketplace.visualstudio.com/items?itemName=mcu-debug.rtos-views to view the status of freertos threads (RT1189). After the update the tool no longer works and just shows "RTOS detection did not finish. It will be resumed on the next halt."  Any suggestions? Thanks Re: VS code extension update broke RTOS viewer Hi, MCUXpresso for VS Code has own RTOS viewer for a long time. Please check https://mcuxpresso.nxp.com/mcux-vscode/latest//html/RTOS-Details.html  Also, old change, the extension migrated from using Microsoft C/C++ Debug Adapter to own debug adapter based on Cortex-Debug. You have to create a new Debug Configuration that will automatically create one based on our debug adapter (you'll notice "mcuxpresso-debug" as type). PS. Please be aware that if you are using Segger debug probe, this requires special enablement for RTOS support (see https://mcuxpresso.nxp.com/mcux-vscode/latest//html/Debug-Views.html#enabling-rtos-awareness) Regards, Cristian Re: VS code extension update broke RTOS viewer Ok I got it working, we where compiling with -Og flag in debug and changing that to -O0 made the viewer work. But I guess the tool needs improvement as Og shall be default for standard edit-debug process?. Unrelated to this, I also see this warning in debug console "warning: could not convert ' \Main.cpp' from the host encoding (CP1252) to UTF-32. This normally should not happen, please file a bug report." Thanks Re: VS code extension update broke RTOS viewer Thanks, In fact the message is coming from MCUXpresso RTOS view itself (I incorrectly referred a different plugin).  I have attached the launch.json and custom device script (it is same as MIMXRT1180-EVK.json for Linkserver 26.3.123, but the "connect-script" is "RT1180_reset.scp".  Our app runs in hyperram and uses SDK 2.16. Freertos variables are correctly set. I can debug an step through our app, but RTOS Details view still shows "RTOS detection did not finish. It will be resumed on the next halt."  Thanks Re: VS code extension update broke RTOS viewer @cristiantepus any updates on this? Re: VS code extension update broke RTOS viewer Today I found that MCUXpresso RTOS viewer does not work in release mode, and does not show anything. But https://marketplace.visualstudio.com/items?itemName=mcu-debug.rtos-views works with -Og and in release modes, but cannot work with current mcuxpresso vscode plugin (gets disabled?). Is there a way to bring that back? Re: VS code extension update broke RTOS viewer Hi @arunkumar_g, The RTOS details view we offer is relying on the existence of some symbols inside the ELF file (e.g. "FreeRTOSDebugConfig", "pxCurrentTCB", "uxCurrentNumberOfTasks", and many more). I agree that the "RTOS detection did not finish. It will be resumed on the next halt." does not guide on what went wrong and we'll make sure to make this clearer. Regarding the results you obtained for "debug" vs. "release", I'd say this is the result of compiler/linker optimizations -- required symbols are stripped-out so any consumer will not find these. In this case, not only the RTOS Details view will fail but the low-level GDB Thread Awareness (LinkServer, J-Link, PEmicro) will be unable to show and debug FreeRTOS tasks in Call Stack view. In this case, I can only suggest you make sure you update the code so that you ensure the presence of the required symbols in both, "debug" and "release" build modes. We'll make sure to update the documentation and the information from the tool to make it clear what symbols are required but are missing -- thus making the views unable to show data. You also mentioned that MCU Debug RTOS view is working in this particular case. Could be, but the last time I checked there was no support any kind of versioning support (version is found by inspecting "FreeRTOSDebugConfig"). And keep in mind that the FreeRTOS data structures are really specific to the RTOS version. To enable MCU Debug views you could ask the maintainers how to add the "mcuxpresso-debug" debug adapter (MCUXpresso specific) in the supported list. Given that you're using a project based on an old SDK 2.16, I'd also suggest switching to the latest MCUXpresso SDK based on CMake & Kconfig.   Some useful links: - RTOS Details: RTOS Details — MCUXpresso for VS Code 26.04 documentation - MCUXpresso SDK: MCUXpresso SDK Documentation — MCUXpresso SDK Documentation   Thanks, Adrian

Ara240 - LPDDR4 Memory Compatibility Guide The purpose of this document is to provide extended guidance for selection of compatible LPDDR4 memory devices that are supported by the Ara240 (aka Ara-2) processors. In all cases, it is strongly recommended to follow the DRAM layout guidelines outlined in the specific SoC requirement documents. LPDDR4 - maximum supported densities SoC Max Data bus width Maximum density Number of Interfaces Assumed memory organization Notes Ara240 64-bit 128Gb/16GB 2 Dual rank, Dual channel device with 17-row addresses 1   LPDDR4 - list of validated memories The validation process is an ongoing effort - regular updates of the table are expected. SoC Density Memory Vendor Validated Memory Part# Notes Ara240 64Gb/(8GB) Total 128Gb/(16GB) (2 x 64Gb/8GB) Micron   MT53E2G32D4DE-046 AUT:C  MT53E2G32D4DE-046 WT:C - 64Gb/(8GB) Total 128Gb/(16GB) (2 x 64Gb/8GB)   FORESEE FLXC4008G-30  2 16Gb/(2GB) Total: 32Gb/(4GB) (2 x 16Gb/2GB) Micron MT53E512M32D1ZW-046BAUT:B     - 32Gb/(4GB) Total 64Gb/8GB (2 x 32Gb/4GB)   Micron MT53E1G32D2NP-046 WT:B - 16Gb/(2GB) Total: 32Gb/(4GB) (2 x 16Gb/2GB) SK Hynix H54G46CYRQX053N - 32Gb/(4GB) Total 64Gb/8GB (2 x 32Gb/4GB) SK Hynix H54G56CYRB-X247 421Y H54G56CYRB-X247 316A - 4Gb/(512MB) Total 8Gb/1GB (2 x 4Gb/1GB) SK Hynix H54G26AYRBX256 - 16Gb/(2GB) Total: 32Gb/(4GB) (2 x 16Gb/2GB) Samsung K4F6E3S4HB-KHCL      - 32Gb/(4GB) Total 64Gb/8GB (2 x 32Gb/4GB) ISSI IS43LQ32K01B 2 32Gb/(4GB) Total 64Gb/8GB (2 x 32Gb/4GB) Samsung K4UBE3D4AB-MGCL - 8Gb/(1GB) Total 16Gb/2GB (2 x 8Gb/1GB)   Winbond W66DP2RQQAHJ 2 Note: This device supports operation with LPDDR4 memories only. LPDDR4x operation is not supported. Dual‑mode memories that support both LPDDR4 and LPDDR4x are allowed as long as the device can operate in LPDDR4 mode, including using LPDDR4 I/O voltage levels and initialization sequences. Note 1: The numbers are based purely on the IP documentation for the DDR Controller and the DDR PHY, on the settings of the implementation parameters chosen for their integration into the SoC, SoC reference manual and on the JEDEC standards JESD209-4C (LPDDR4). Therefore, they are not backed by validation, unless said otherwise and there is no guarantee that an SoC with the specific density and/or desired internal organization is offered by the memory vendors. Should the customers choose to use the maximum density and assume it in the intended use case, they do it at their own risk. Note 2: The memory part number did not undergo full JEDEC verification however, it passed all functional testing items. Note 3: Memory devices with binary densities (e.g., 1 GB, 2 GB, 4 GB) are preferred because they simplify memory management by aligning with system addressing schemes and reducing software complexity. Note 4: All memory parts are in production unless stated otherwise. Checked June 2026 Note 5: The processor does not support BYTE Mode (x8) memories.  Re: Ara240 - LPDDR4 Memory Compatibility Guide Cross reference: Ara-240 - NVM Memory Compatibility Guide

S32 平台的 S32 Design Studio 版本：3.5 你好，恩智浦团队。 希望你收到这条信息时一切安好。我想安装 S32DS 示例项目。由于内部网络安全策略，无法进行自动更新，因此我需要将其离线安装。 我查看了恩智浦网站，但未能找到必要的信息。能否提供网站链接和安装说明？ 以下是我的系统详细信息： -SDK 版本：适用于 S32 平台的 S32 Design Studio 版本：3.5 -内核：Cortex M0 -目标板：S32K118 感谢您的帮助，我期待您的指导。 example.png Re: S32 Design Studio for S32 Platform Version: 3.5 你好@宋俊 你已经安装了 S32K1 开发软件包吗？如果没有，可以从下面的链接下载，并通过 S32 扩展和更新 → 添加更新站点将其安装到 S32DS 中。 下载链接： https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=S32DS-3-6 导航到 S32 Design Studio IDE → 适用于 S32 平台的 S32 Design Studio v.3.5 → S32 Design Studio 3.5 开发软件包可供离线使用，支持 S32K1 (sw32k1_s32ds_3.5.4_d2307.zi p) 另请注意，S32K1_S32M24x 实时驱动程序 ASR R21-11 版本 2.0.0 QLP1 仅提供加密驱动程序。要获得全套驱动程序，请先安装 S32K1_S32M24X 实时驱动程序 AUTOSAR 4.4 & R21-11 版本 2.0.0，然后安装版本 2.0.0 QLP1。 BR、VaneB Re: S32 Design Studio for S32 Platform Version: 3.5 我使用 S32K118 MCU 创建了一个应用程序项目，但未应用设备设置（配置）。您能告诉我为什么会出现这种情况吗？ 错误信息 :无数据。请确保已安装所有必需的依赖项。 我安装了以下版本来使用 RTD。 安装：SW32K1_S32M24x_RTD_R21-11_2.0.0_QLP1_D2408

For S32G274A multi-core scenario, can the first 0x9100 bytes of fip.bin be neglected? When making ATF image for BSP42, we get information like this: Boot Core: A53_0 IVT Location: QSPI Load address: 0x342f8f00 Entry point: 0x34302000   Entry point - Load address = 0x9100 it's BL2 that sits at offset 0x9100 of fip.bin. So is "Entry point" refering to BL2?   For multi-core scenario, MCU runs bootloader to load BL2 for A53. If BL2 is the entry point, should bootloader just copy from offset 0x9100 of fip.bin(BL2) to 0x34302000 of RAM space(neglect the first 0x9100 bytes)？ GoldVIP Re: For S32G274A multi-core scenario, can the first 0x9100 bytes of fip.bin be neglected? Hello, @wansp  Thanks for your post The bootloader will move the data from QSPI to the Load address(SRAM), they would not be neglected. BR Chenyin

ENEDC(S32K3)に関する質問 こんにちはチーム K3のENEDCについてお伺いしてもよろしいでしょうか？ 顧客は RTD 付きの MCAL を使用します。 しかし、ENEDC に関する RTD の情報は見つかりませんでした。 MSCM からは、ISR コア割り当て構成のみが表示されます。 RTD(MCAL) を使用して ENEDC を有効にする方法を教えてください。 ありがとう。 SAFETY_SW 出典: 直接顧客 出典: NXP社内 Re: Question about ENEDC(S32K3) ご説明ありがとうございます！ Re: Question about ENEDC(S32K3) こんにちは@Luke_Chun 、 RM の説明から私が理解したところによると、ガスケットから FCCU へのレポート パスをアクティブにしたい場合は、これらのビットを有効にする必要があります。 このため、sCheck はこれらのビットを有効にします。そうしないと、レポート パスをテストできなくなります。 これは必須の設定であること、そしておそらく多くの K3 お客様がこの設定に気付いていない (関連する FCCU チャネルを有効にするだけで、これらのビットは有効にしない) ことには同意します。 敬具、 ラドスラフ Re: Question about ENEDC(S32K3) こんにちは@RadoslavB ご説明ありがとうございます。しかし、ENEDC の提案についてはよく分かりません。 私の理解を確認していただけますか？ ENEDC では「TEST」のみを使用する必要がありますか? または セーフティアプリケーションを有効にする必要はありますか?(たとえば、ユーザーが eDMA 読み取りのチェックを使用したい場合は、ENEDC のビット 2 を FCCU 構成で手動で「設定」します。) ありがとう。 Re: Question about ENEDC(S32K3) こんにちは@Luke_Chun 、 SAF で MSCM ペリフェラルレジスタを構成する要求はありません。 sCheck テストは、関連する EDC ガスケットの潜在的な障害をテストするときにこれらのレジスタを内部的に有効にしますが、アプリケーションに対してこれらのビットを有効にすることはどの NXP SW でもカバーされていません。 したがって、お客様はこれらのレジスタを手動で有効にする必要があります。 S32K5 の場合、これらのレジスタをイネーブルメントの sBoot チェックが定義されていますが、繰り返しますが、私の知る限り、構成はどの NXP SW の範囲にも含まれていません。 敬具、 ラドスラフ Re: Question about ENEDC(S32K3) こんにちは@Luke_Chun 、 セーフティドライバーに関連する問題はサポートしていません。彼らにサポートを依頼するには、投稿で「RTD」ラベルを削除し、「Safety_SW」ラベルのみを残す必要があります。または、Safety_SW のみに新しい投稿を作成することもできます。 よろしくお願いいたします。 ダン Re: Question about ENEDC(S32K3) こんにちは@DanNguyenDuy 更新情報をありがとうございます。 セーフティドライブも確認しましたが、どれがENEDCに関係するのかわかりませんでした... どうやって確認すればいいのでしょうか？ よろしくお願いします。 Re: Question about ENEDC(S32K3) こんにちは@Luke_Chun 、 RTD ドライバーは ENEDC の構成ではサポートされていません。私の観点からすると、このレジスタは FCCU に関連しているため、セーフティドライバのモジュールでこの機能を確認する必要があります。 よろしくお願いいたします。 ダン Re: Question about ENEDC(S32K3) K3 HW セーフティマニュアルからの抜粋を追加します: したがって、現時点ではこの AoU に従うかどうかはお客様の責任です。構成とチェックは現時点では NXP ではサポートされていません。 敬具、 ラドスラフ Re: Question about ENEDC(S32K3) こんにちは@Luke_Chun 、 INTM ペリフェラルの構成がサポートされており、RTD プラットフォーム プラグイン - 割り込みモニターで見つけることができます。 SAF 側では、sCheck は INTM 潜在的障害テストを備えていますが、sBoot は INTM 構成レジスタをチェックしません。私の意見では、割り込みがセーフティ関連の障害の検出/反応メカニズムである場合、SM1.INT_MON はアクティブである必要があり、顧客は SM4.INT_CHK を満たす必要があり、sBoot はそのような構成を再確認する必要があります。 敬具、 ラドスラフ Re: Question about ENEDC(S32K3) こんにちは@RadoslavB もう1つ質問してもよろしいでしょうか？ INTM_MMはどうでしょうか? これは ENEDC でも同じですか? (RTD または SAF は INTM_MM 有効構成をサポートしていません。ユーザーはユーザー コードによって INTM_MM の構成を行う必要があります。 ありがとう。  

S32K148 回路図ドキュメント (SCH-29643 REV C) こんにちは、NXP チームの皆様、 S32K148 評価ボードを使用しており、ボードの回路図ドキュメント SCH-29643、リビジョン C を探しています。 利用可能なリソースを検索しましたが、Rev C の回路図を見つけることができません。 S32K148 EVB の SCH-29643 Rev C 回路図ドキュメントを共有していただけますか (または適切なダウンロード リンクを提供していただけますか)? サポートいただきありがとうございます。 PIC1.jpg.jpeg Re: S32K148 schematic Document (SCH-29643 REV C) こんにちは、 添付したものを見つけました。 BR、ペトル

SAF - ASIL Certification Hi Support, Customer is using S32K31 with SW32K3_SAF_1.0.5_D2503.  They are asking for our SAF ASIL certificates, or any document to show it is ASIL "ready/compliance". Regards, Marcus Safety_SW Re: SAF - ASIL Certification Hi Support, Any updates? Re: SAF - ASIL Certification Hi Marcus, for every premium SAF package there is possible to download Safety SW Assessment Summary report. For SAF 1.0.5 I can see that on Flexera available as well: S32K3_SAF_1.0.5_Safety_SW_Assessment_Summary.pdf Kind Regards, Radoslav Re: SAF - ASIL Certification Hi @marcuslim , It is now technically and legally restricted to share files with customers, only legal way is via sales force I think. Anyway, I wanted screenshot from nxp.com from SAF product page, same as I have shared, to see that is really missing. How does customer get the release? Safety Assessment should be there, everybody else can see that. I'm attaching here internally the report and let you find the way how to legally share the file with the customer. But please try to explain the customer proper way how to get it nxp.com=>Software accounts=>Automotive SW - S32K3 Premium Software=>Automotive SW - S32K3 - Safety Software Framework Kind Regards, Radoslav Re: SAF - ASIL Certification Thanks Radoslav! The customer has found the document.  We can close this thread. Regards, Marcus

s32k312 hse ab-swap 重启方法？ 恩智浦专家，你好、 1.我使用的是 s32k312，HSE 版本为 1.13.0、2.40.0。 2.我正在实现 OTA 功能。 OTA 完成后，我需要致电 HSE 交换 ab，然后重启以运行新的应用程序。 我的问题是，我编写了一个演示程序，并调用" HSE_SRV_ID_ACTIVATE_PASSIVE_BLOCK" 服务。在不带任何参数的情况下，使用"IP_MC_ME" perphieral 重启单片机，但只起一次作用，然后单片机就无法运行了，可能是出现了一些硬故障。 那么，但是通过RESET引脚重启是可以的。 我的重启密码是 剧透 （高亮部分可供阅读） IP_MC_ME->MODE_CONF = mc_me_mode_conf_func_rst(1); IP_MC_ME->MODE_UPD = MC_ME_MODE_UPD_MODE_UPD(1); IP_MC_ME->CTL_KEY = mc_me_ctl_key_key(0x5AF0); IP_MC_ME->CTL_KEY = mc_me_ctl_key_key(0xA50F); IP_MC_ME->MODE_CONF = MC_ME_MODE_CONF_FUNC_RST(1); IP_MC_ME->MODE_UPD = MC_ME_MODE_UPD_MODE_UPD(1); IP_MC_ME->CTL_KEY = MC_ME_CTL_KEY_KEY(0x5AF0); IP_MC_ME->CTL_KEY = MC_ME_CTL_KEY_KEY(0xA50F)； 这个重启代码可以吗？还是我需要使用其他方法重启微控制器，使 ab 交换功能生效并运行新程序？ 谢谢。 Re: s32k312 hse ab-swap reboot method? 原则上是正确的，但请务必查看以下演示示例，您可以在其中详细调换程序 首先，我们提供了 Secure 启动 应用笔记，其中包括详细解释所有步骤的演示项目。可从以下网址下载 https://www.nxp.com/products/processors-and-microcontrollers/s32-automotive-platform/s32k-auto-general-purpose-mcus/s32k3-microcontrollers-for-automotive-general-purpose:S32K3 应用笔记可以在这里找到： 文档-> 安全文件-> 安全启动应用笔记 v0.1.1.0(AN744511) 相关演示项目可在此处下载： 设计资源 -> 软件 -> 安全文件 -> SecureBootAppNoteDemo (SW745310)

FlexGUI-PF8X PF8200 的编程问题 亲爱的； 当我使用 FlexGUI-PF8X 离线工具为 PF8200 的固件 (SC33PF8200KKES) 编程时，报告了以下问题： 脚本解析失败（格式错误）。具体信息见图 1。 我可以正常使用 PF8100 进行刻录和写入。 谢谢！ 致以最崇高的敬意 Re: Programming issue with FlexGUI-PF8X PF8200 我没测试OTP 的script我测试了TBB script是可以运行的，在GUI 选择TBB 以后 我用的是10.0.0的GUI 版本 guoweisun_1-1765352938071.png Re: Programming issue with FlexGUI-PF8X PF8200 Dear；          好的，我按照最新的GUI后测试一下。谢谢！         Best Regards! Re: Programming issue with FlexGUI-PF8X PF8200 TBB 的那个脚本能运行吗？ 不行的话现在最新的GUI！ GUI PMIC软件|汽车|恩智浦半导体 Re: Programming issue with FlexGUI-PF8X PF8200 Dear；         固件见附件。谢谢！         Best Regards！ Re: Programming issue with FlexGUI-PF8X PF8200 能发我看看是哪个script吗？ Re: Programming issue with FlexGUI-PF8X PF8200 Dear;         该次烧写的固件是直接NXP官网下载的，谢谢！       Best Regards！ Re: Programming issue with FlexGUI-PF8X PF8200 不会，我也是WIN11 Re: Programming issue with FlexGUI-PF8X PF8200 看这个附件的文档里面有更新的FW，从第12页开始看4 Installing and configuring software and tools 。 Re: Programming issue with FlexGUI-PF8X PF8200 Dear；          我现在使用的是windows 11操作系统，我看这个软件支持的操作系统是windows 10或windows 7，这个是否会影响GUI的正常工作？谢谢！           Best Regards！ Re: Programming issue with FlexGUI-PF8X PF8200 Dear；          谢谢您的支持，已经搞定了，谢谢！          Best Regards！