Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
DES-N1952 实践研讨会:使用 Kinetis 逐个保护物联网边缘节点 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 确保数十亿终端节点的安全部署是未来互联网的关键推动因素。Kinetis K8x 和 Kinetis KL8x 系列旨在为多应用 MCU 提供无与伦比的安全性,具有信任、加密加速和防篡改等硬件功能,为嵌入式开发人员提供可扩展的安全平台。本次实践课程将涵盖安全嵌入式应用程序的需求、执行加密固件更新、利用硬件加密加速器以及使用动态 AES 解密模块将可信执行扩展到外部存储器。加入此会议以了解您的客户如何开始创建他们的下一个安全节点设计。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 确保数十亿终端节点的安全部署是未来互联网的关键推动因素。Kinetis K8x 和 Kinetis KL8x 系列旨在为多应用 MCU 提供无与伦比的安全性,具有信任、加密加速和防篡改等硬件功能,为嵌入式开发人员提供可扩展的安全平台。本次实践课程将涵盖安全嵌入式应用程序的需求、执行加密固件更新、利用硬件加密加速器以及使用动态 AES 解密模块将可信执行扩展到外部存储器。加入此会议以了解您的客户如何开始创建他们的下一个安全节点设计。 设计 | 软件与服务
View full article
HMB-N1995 午餐学习 - 便携式射频加热应用的设计挑战 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在设计烹饪设备时,需要充分考虑家庭有线电气系统所需的电力以及维持安全和工作温度所需的性能。NXP 固态射频烹饪团队与 Wayv Technology 合作开发了使用固态射频能量的便携式食品加热器具。本次会议将讨论通过便携式、便携设备提供能量来加热食物所面临的主要挑战和方法。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在设计烹饪设备时,需要充分考虑家庭有线电气系统所需的电力以及维持安全和工作温度所需的性能。NXP 固态射频烹饪团队与 Wayv Technology 合作开发了使用固态射频能量的便携式食品加热器具。本次会议将讨论通过便携式、便携设备提供能量来加热食物所面临的主要挑战和方法。 观看视频演示 智能家居和智能建筑
View full article
AUT-N1797 MagniV 电机控制集成解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 将传统 MCU 功能与高压模拟元件结合在单个芯片中,可以节省系统成本。提高质量并减少占地面积的整体解决方案。这是针对车窗升降、天窗和滑动门等关闭解决方案的 S12 MagniV MCU 系列的概述。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 将传统 MCU 功能与高压模拟元件结合在单个芯片中,可以节省系统成本。提高质量并减少占地面积的整体解决方案。这是针对车窗升降、天窗和滑动门等关闭解决方案的 S12 MagniV MCU 系列的概述。 安全互联汽车和自动化汽车
View full article
欢迎来到电机控制和智能能源社区! <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该社区分享有关电机控制和智能能源的一般信息。   所有电机类型的控制:可以讨论 PMSM、BLDC、ACIM、SR 和智能能源主题。通常,应用程序基于电机控制库(FSLESL 和 API 转换器)和框架,这使得解决方案变得非常简单。   立即开始贡献! 概述
View full article
飞思卡尔无线充电技术 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 概述当前无线充电市场的情况和趋势。介绍飞思卡尔无线充电消费类低功耗、中功耗解决方案以及汽车低功耗解决方案。 由 Beta Chen 主讲 2015 年 5 月 7 日,台北 DwF 展 会话 ID:APF-SHB-T1455 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 概述当前无线充电市场的情况和趋势。介绍飞思卡尔无线充电消费类低功耗、中功耗解决方案以及汽车低功耗解决方案。 由 Beta Chen 主讲 2015 年 5 月 7 日,台北 DwF 展 会话 ID:APF-SHB-T1455 电源管理
View full article
使用 Kinetis MCU 系列和 MQX RTOS 实现物联网 (IoT) 的互联家庭网关 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本文档介绍了物联网 (IoT) 的联网家庭网关及其在运行 Android 操作系统的智能设备(平板电脑)中实现的控制器。 该网关旨在充当 WiFi/以太网和 ZigBee 协议之间的通信桥梁,使每个支持 ZigBee 的设备都可以从任何具有 Wi-Fi 功能的智能设备(如智能手机或平板电脑)访问和控制。这样一来,每个试图控制家用电器的移动设备就不再需要配备 ZigBee 收发器。一般来说,用户将能够: 使用 ZigBee 协议远程控制家用电器 任何支持 WiFi 的设备都可以控制没有 ZigBee 收发器的电器 实现用户与设备之间的双向通信 实际系统实施需要一个功能强大的 MCU 来管理所有 WiFi/以太网通信,以及另一个 MCU 来管理所有 ZigBee 通信。在众多可用选项中,我们选择了 Kinetis K60 和 KW24 。 BLE软件 KW01Z
View full article
フリースケールi.MX6によるデジタルサイネージ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> デジタルサイネージは、i.MX6プロセッサが最適であるアプリケーションです。ハードウェアのエンコードとデコード、ビデオの出力と入力、処理能力により、デジタルサイネージにi.MX6を使用することは非常に人気があります。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> デジタルサイネージは、i.MX6プロセッサが最適であるアプリケーションです。ハードウェアのエンコードとデコード、ビデオの出力と入力、処理能力により、デジタルサイネージにi.MX6を使用することは非常に人気があります。 全般
View full article
The Freescale Cup Worldwide Finals 2015 This document is addressed to the participants and visitors that will join us for The Freescale Cup 2015 Worldwide Finals 2015 The Freescale Cup 2015 Worldwide Finals will be held on 14-15 September 2015 at the Fraunhofer Institute for Integrated Circuits (Fraunhofer IIS) in Erlangen, Germany. Full address is: Fraunhofer IIS Am Wolfsmantel 33 91058 Erlangen Germany Google Maps location The attendees official guide is now online at https://community.nxp.com/docs/DOC-106164 Agenda of the event for the participants (subject to change): Sunday September 13th: Arrival at Hotels Get together in the evening (approximate time 18:00) at A&O Hostel Monday September 14th: 8:30: Departure from Hotel for City Tour 11:30: Prepare for departure for Fraunhofer IIS 12:00: Buses depart for Fraunhofer IIS 13:00: Lunch 14:00: Opening session 15:00: Start of Practice 17:30: High School and Innovation Challenge Demos 18:00: End of Practice - Start of the evening event 21:00: End of evening event - boarding buses for return to hotel Tuesday September 15th: 8:00: Buses depart for Fraunhofer IIS 9:00: Practice 13:00: Technical Inspection & Lunch 14:30: Final Race 16:00: Awards Ceremony 17:30: Buses depart for Awards Dinner 20:30: Buses depart for Hotel The event will be presented via LiveCast by the Fraunhofer IIS. URL is http://www2.iis.fraunhofer.de/freescale/  Hotel information: Students Hotel: Nuremberg Hostel - Stay at the A&O Hostel & Hotel Nuremberg  Google Maps Location Professors and Press Hotel: NH Nürnberg City Center hotel in Nuremberg Bahnhofstr. 17-19 | NH Hotel Group Google Maps Location Freescale will cover the cost of travel, accommodation and meals for the event for all Freescale Cup qualified teams and one faculty advisor per the rules in place. For Visa invitation letters, please contact [email protected] or [email protected] Travel booking will be organized by your regional Freescale University Program contact. Please have your faculty advisor get in touch with them for more information Freescale Cup Content
View full article
Kinetis Design Studio: Migrating KDS V2.0.0 Projects to GNU Tools for ARM Embedded (Launchpad, KDS V3.0.0) Introduction Up and including to version 2.0.0, the Kinetis Design Studio (KDS) is using a custom GNU toolchain built by SOMNIUM Technologies, referred here as 'legacy'. That toolchain is built from the Free Software Foundation (FSF) source base, with a few minor modifications. Starting with v3.0.0, KDS will use the unmodified GNU Tools for ARM Embedded (launchpad, GCC ARM Embedded in Launchpad) toolchain (4.8-2014-q3-update : Series 4.8 : GCC ARM Embedded release), referred here as 'launchpad'. Projects created with KDS v3.0.0 will use the 'launchpad' tools by default. The reasons for 4.8-2014-q3 instead of using the later 4.9 release is because of stability and smaller footprint of 4.8 applications.   Outline This document outlines what are the differences between the 'legacy' and 'launchpad' toolchain, and what is needed to port existing 'legacy' projects to the 'launchpad' ones. It is already possible to use the 'launchpad' tools with KDS v2.0.0 today (see Switching ARM GNU Tool Chain and Libraries in Kinetis Design Studio | MCU on Eclipse), therefore the information in this document can be applied to KDS v2.0.0 to with using the 'launchpad' toolchain.   KDS Upgrade Assistant Kinetis Design Studio V3.0.0 comes with a migration assistant to migrate projects to the GCC ARM Embedded (launchpad) tools. The migration assistant is accessible from the menu Project > KDS Upgrade Assistant: This opens a dialog with the currently open projects in the workspace:   NOTE: if the Upgrade Assistant does not list your project, then you still can do the manual steps as listed below (changing the linker flags).   Select the project(s) you want to migrate and press Next. In the next dialog you can configure the details of the conversion, then press Finish: A report will be generated in each project directory:   Migration of KDS Projects To migrate an existing 'legacy' project to a 'launchpad' project, usually only the linker settings need to be changed. For this go into the project properties, and check the 'Other linker flags' settings of the Linker. The table below shows the difference between the two: Legacy 'Other linker flags' Launchpad 'Other linker flags' -specs=nosys.specs -nanolibc -specs=nano.specs -specs=nosys.specs   For example this project is a legacy project using the newlib-nano library: To use it with the 'launchpad' toolchain, use -specs=nano.specs -specs=nosys.specs as shown below: With this, normally projects are converted from the 'legacy' to the 'launchpad' toolchain.   NOTE: after switching toolchains, delete all intermediate or object files (e.g. delete the Debug/Output folder inside the project. Mixing object files or libraries from different toolchains and compilers will likely cause problems.   Now your project should compile fine. However, if you face a problem about wrong Thumb mode, see the following subsection.   Wrong or missing Thumb mode If getting errors like      Error: selected processor does not support Thumb mode      error: interrupt Service Routines cannot be coded in Thumb mode This means that the project settings do not properly pass the processor to the compiler. That problem mainly occurs with Kinetis SDK projects, and with Cortex-M0+ (Kinetis-L) projects. As explained in the next section, the launchpad tools by default use the ARM, not the thumb mode. The solution is to add      -mcpu=cortex-m0plus for these Kinetis-L projects to the compiler 'Other target flags'.   The following sections provide more detailed information about the differences.     Differences Both the 'launchpad' and the 'legacy' toolchains are GNU toolchains, and largely compatible. However there are notable differences between the two toolchains:   legacy launchpad GNU Binaries Microsoft 32bit binaries, Linux 64bit binaries Microsoft 32bit binaries, Linux 32bit binaries(1) GNU binutils 2.32.2 2.23.2.20140731(*) GCC 4.8.0(*) 4.8.4 (ARM/embedded-4_8-branch) NewLib 1.19.0(*) 2.1.0(*) Newlib-nano 1.0(*) 2.1 GDB 7.6(2) 7.6.0.20140731-cvs(2) ARM Mode Thumb ARM (non-Thumb) (*) Modified. (1) See next section about running 32bit GNU tools on 64bit Linux. (2) The legacy GDB has Python support, while this is not present in the launchpad 4.8-2014-q3 build. Python support has been added by ARM in 4.9-Q4-2014 release.   Launchpad 32bit Binaries to run on 64bit Linux Because the 'launchpad' tools are 32bit binaries on Linux only, this can cause issues on 64bit Linux systems (e.g. Ubuntu 14.04 64bit) if the needed 32bit support libraries are not installed. A usual error message is that arm-none-eabi-gcc could not be found, even if that file is present, because the system does not know how to run it. This is because the 'launchpad' tools are built as 32bit binaries, an the compatibility package needs to be installed. See http://gnuarmeclipse.livius.net/blog/toolchain-install/ how to install the necessary compatibility libraries for Linux.   ARM Default Mode The default options for the 'legacy' toolchain produce code for the ARM Cortex-M0+ (Thumb mode), while the 'launchpad' tools default to the 'ARM' mode (non-Thumb). Therefore it is important that the command line options -mthumb with the appropriate -mcpu= or -march= options are used if using the tools in command line only mode. If using the GNU ARM Eclipse plugins, then no changes are needed as these options are set in the project already:     Default Libraries and Options The GNU compiler driver and linker is using default pre-built libraries in certain sub directories. These directories contain a default set of libraries, based on the compiler and architecture options specified during the build and link phase. Using linker options like -L to include a specific library or using options like -nostdlib or similar have an effect which libraries in which subdirectory are used. The library folder location is in \toolchain\arm-none-eabi\lib   The following table lists the specific options used for both the legacy tools and launchpad tools to link for a specific architecture and floating point ABI used: Target Legacy Options Legacy Subdir Launchpad Options Launchpad Subdir ARM Cortex-M0+ -mthumb -march=armv6s-m armv6-m ARM Cortex-M4 -mcpu=cortex-m4 m4 -mthumb -march=armv7e-m armv7e-m ARM Cortex-M4F -mcpu=cortex-m4 -mfloat-abi=hard -mfpu=fpv4-sp-d16 m4/fp/v4-sp-d16 -mthumb -march=armv7e-m -mfloat-abi=hard -mfpu=fpv4-sp-d16 armv7e-m/fpu ARM Cortex-M4F with softfp ABI -mcpu=cortex-m4 m4 -mthumb -march=armv7e-m -mfloat-abi=softfp -mfpu=fpv4-sp-d16 arm7e-m/softfp   Newlib-nano Both the legacy and the launchpad toolchain include the newlib-nano library, a standard library more optimized for embedded devices than the normal newlib one. The option to select the newlib-nano library is different: Newlib-nano for Legacy Newlib-nano for Launchpad -nanolibc --specs=nano.specs   Application _start() The startup code needs to call the _start() function of the library which then calls the main() function. The _start() function in the library is responsible to initialize the library and prepare it to be used by the application. In order to do this, the library needs to have the __stack symbol defined in the linker file which points to the top of stack. For this, the __stack symbol needs to be defined in the linker file as in the example below: /* Highest address of the user mode stack */ _estack = 0x20000000;    /* end of m_data */ __SP_INIT = _estack; __stack = _estack;   Semihosting The legacy library has semihosting included in the libraries, and users can use _isatty() and _write() to overwrite the existing semihosting hooks. With the launchpad tools semihosting is enabled with the -specs=rdimon.specs linker option, and users can implement their own hooks with _sbrk(), _write(), _close(), _fstat(), _isatty(), _lseek() and _read(). To completely disable semihosting, the options -specs=nosys.specs can be passed to the linker.   Application Exit Function The legacy library includes a default implementation of _exit(), while the launchpad tools do not include this. Using the -specs=nosys.specs linker option will ensure that the linker does not complain about the missing _exit() function.   Summary A typical legacy Kinetis Design Studio (KDS) V2.0.0 project can be easily migrated to the launchpad toolchain with adding -specs=nosys.specs linker option and replacing the -nanolibc legacy option with -specs=nano.specs linker option.   Links Kinetis Design Studio: Kinetis Design Studio Integrated Development |Freescale GNU Tools for ARM Embedded: GCC ARM Embedded in Launchpad Q3 2014 GNU Tools for ARM Embedded Release: 4.8-2014-q3-update : Series 4.8 : GCC ARM Embedded Blog article about how to switch KDS toolchain: Switching ARM GNU Tool Chain and Libraries in Kinetis Design Studio | MCU on Eclipse GNU ARM Eclipse plugin website and blog by Liviu: Welcome to the GNU ARM Eclipse plug-ins! | GNU ARM Eclipse Article by Liviu how to install toolchain: http://gnuarmeclipse.livius.net/blog/toolchain-install/ General Re: Kinetis Design Studio: Migrating KDS V2.0.0 Projects to GNU Tools for ARM Embedded (Launchpad, KDS V3.0.0) It seems that your project already has a file exit.c with _exit() in it, so you do not need to do this last step. Erich Re: Kinetis Design Studio: Migrating KDS V2.0.0 Projects to GNU Tools for ARM Embedded (Launchpad, KDS V3.0.0) Hi Erich, I have tried to use the "KDS upgrade assistant" tool to migrate KDS2.0 projects with KSDK1.1 to KDS3.0 version. I am trying to convert the KSDK libs, MQX libs, USBH libs and usb host demo projects. All succeeded except the usb host demo. I got a failure message as follows.   Project name: host_msd_fatfs_frdmk64f_mqx_frdmk64f   Project location: C:/Freescale/KSDK_1.1.0/usb/example/host/msd/msd_fatfs/sdk/kds/host_msd_fatfs_frdmk64f_mqx   Conversion status: failure.   Add exit() file failure: A resource exists with a different case: '/host_msd_fatfs_frdmk64f_mqx_frdmk64f/sources'. So do I need to apply the last step in upgrade option? Hao Re: Kinetis Design Studio: Migrating KDS V2.0.0 Projects to GNU Tools for ARM Embedded (Launchpad, KDS V3.0.0) I found this guide very useful, thoughI think it is worth mentioning that launchpad toolchain in KDS3.0.0 has no support for C++ exceptions. Any throw will cause the execution to end up in the unhandled exception handler regardless a suitable catch is available in the call chain. (See: Question #230716 : Questions : GCC ARM Embedded ) Best Re: Kinetis Design Studio: Migrating KDS V2.0.0 Projects to GNU Tools for ARM Embedded (Launchpad, KDS V3.0.0) Hi BlackNight​, thanks for sharing this document.  I have a question regarding the project conversion process.  For those project previously written using KSDK 1.1, KDS 3.0 is going to ask us to install the KSDK 1.1.0-GA update: When I first loaded the project, I clicked "Skip loading", and then proceeded with the project conversion.  It completed successfully.  My thought was that after closing and re-opening the upgraded project, I would no longer get this message.  However, that's not the case. At this point, I'm not sure what to do because I don't know how the 1.1.0-GA update will interact in KDS 3 when the 1.2.0-GA update is already installed.  I do know that clicking Continue loading results in a project that doesn't work.
View full article
FreeMASTER 3.2.3 Update - Release Announcement Version 3.2.3 of the NXP FreeMASTER tool has just been published online.  This version is backward compatible and fully replaces older 3.2.x releases (see previous announcements). It brings new features and bugfixes described below. The updated installer is available along with documentation and other resources at http://www.nxp.com/freemaster.   Release description FreeMASTER is a powerful data visualization tool developed and provided by NXP to help users monitor and control embedded applications running on NXP’s targets. It works with almost all NXP Arm ® Cortex®-M microcontrollers from both Edge Processing and Automotive business lines as well as with DSC and legacy Power Architecture, ColdFire and HCS12/Z platforms. Note that the license terms and conditions does not allow using FreeMASTER with non-authorized systems from other vendors. Version 3.2.3 is a minor update of the 3.2.x mainline release line. It overwrites previous 3.2 version installed on the host computer. Older 2.x, 3.0 and 3.1 versions are not removed.  This version backward compatible with all previous versions. It supports variable monitoring, oscilloscope real time graphs, fast transient recorder graphs, array-to-graph views and connectivity to 3rd party applications. There are CEF and Microsoft Edge WebView2 as two Chromium-based HTML rendering engines with full support of JSON-RPC, HTML5 and JavaScript to create custom dashboards and other user interfaces that run inside FreeMASTER. Older Internet Explorer rendering engine with ActiveX interface and protocol defined for versions 2.x is also still supported. FreeMASTER Lite service which is part of the FreeMASTER installation package provides the communication core for Windows and Linux systems. It is accessible similarly as the FreeMASTER desktop application over the JSON-RPC interface. FreeMASTER Lite also embeds the popular Node-RED framework for graphical programming and provides many examples of use with the FreeMASTER tool. Find more information related to Node-RED in the dedicated training video.  FreeMASTER Node.js Installable Modules enable convenient use of the FreeMASTER JSON-RPC components in a Node.js applications managed by the ‘npm’ package manager. Version 3.2.3 contains FreeMASTER Lite and Node.JS modules internally referred as version 1.3. Installing FreeMASTER Lite will require you to enter an activation code generated for this version. Get your free code on the License Keys tab at the license information page. New Features Version 3.2.3 introduces the following new features extending data visualization and communication options: Segger RTT plug-in extended The RTT communication plug-in now enables extra connection options to be provided by user. This may be needed to specify memory address or range of addresses where JLink RTT client searches for a communication buffer. Segger JLink plug-in extended The JLink plug-in now enables a custom script file (JLinkScript) to be executed by JLink library while connecting to target. This may be needed when extra steps are necessary e.g. to enable target memory access point (MEM-AP) interface. P&E Micro plug-in extended The P&E Micro plug-in has been extended. The latest firmware and device files have been added to support new NXP microcontrollers. ELF/Dwarf version 5 support Application executable files compiled using the latest GCC which use Dwarf V5 format by default can now be directly parsed by FreeMASTER. X-Y graphs extended Recorder, oscilloscope and Array Viewer X-Y graphs now enable to break the graph line when negative delta is detected on X axis. This may be useful when tracking inter-variable dependencies during cyclic events. CEF component updated CEF Chromium browser component has been updated to version 121.3.4+g2af7b91+chromium-121.0.6167.139. This solves issues observed after January 2024 update of Chrome browser. Regular-expression MAP file parser extended Parsing the text-based MAP files is quite outdated way of loading the MCU application symbolic information. However, this option may still be useful when other methods such as reading the ELF file or loading runtime TSA tables are not available. The latest version extends the MAP file parsing by options to define and load symbol type information. Loading ELF or MAP file from HTTPS URL The ELF/MAP files are now possible to be downloaded from HTTP/HTTPS server using an URL address.  Connection string as command-line argument The connect-string can now be specified using the "/cs" command-line argument. This may be extremely useful during automated test procedures or when starting multiple concurrent FreeMASTER instances to interface different target boards. Bugfixes and other extensions: FreeMASTER Fixed the warning dialog showing the full connect string when connection takes longer than expected. Fixed format of JSON-RPC responses of WriteMultipleVariables() and ReadMultipleVariables() methods. FreeMASTER Lite The Segger JLink, RTT and P&E Micro plug-in configuration options have been extended the same as in the desktop version. Added BDM plugin to FreeMASTER Lite for Windows x64. Added health check endpoint. Default path is `/health`, can be customized via input argument `--health `. Upgraded Internal NodeJS to version 18.5.0. Fixed write 1 byte variable function. Issue: FreeMATER Lite was writing the ASCI code of the first character of the string argument instead of the numeric value (ex: “1” was written as 49 instead of 1) Release target audience Both FreeMASTER and FreeMASTER Lite are primarily targeted to our customers, engineers and developers of NXP embedded applications from Industrial, IoT and Automotive areas who want to monitor and control their applications at runtime. FreeMASTER is also a strong framework which can be used to create interactive demos and user interfaces helping to use the embedded applications by yet wider target audience. Prerequisites FreeMASTER tools run on the host computer and communicates with the target microcontroller application using Serial, CAN, Ethernet/WiFi network, JTAG, BDM or other physical interface. The microcontroller communication drivers are available as part of MCUXpresso SDK, S32 Design Studio or as a standalone installation package. Get familiar with the communication protocol and the microcontroller driver API before using the FreeMASTER tool. License terms and conditions permit use of FreeMASTER solely with systems based on NXP microprocessor or microcontroller systems. Packages A single self-extracting installation package which contains both FreeMASTER desktop application and the new FreeMASTER Lite service is available for Windows platforms. JTAG/ BDM Serial CAN TCP/IP Segger RTT FreeMASTER Desktop app. x86 for Windows ✓ ✓ ✓ ✓ ✓ Separate packages are available for FreeMASTER Lite containing x64 binaries for Windows & Linux platforms with the following supported communication interfaces. JTAG/ BDM Serial CAN TCP/IP Segger RTT FreeMASTER Lite x64 for Windows ✓* ✓ ✓ ✓ ✓ FreeMASTER Lite x64 for Linux ✗ ✓ ✗ ✓ ✗ *Requires 64 bit version of the 3 rd party library. Tested with Segger (JLink_x64.dll). Access the installation and documentation at the FreeMASTER home page at https://www.nxp.com/freemaster.
View full article
MCUXpresso IDE v11.8.1 が利用可能になりました MCUXpresso IDE v11.8.1(ビルド1197)が利用可能になりました。 こちらは、前回のMCUXpresso IDE v11.8.0リリースを基にしたメンテナンス・リリースであり、この新しいバージョンをダウンロードしてインストールすることを既存ユーザーにお勧めします。   インストーラーのダウンロード  全プラットフォーム向けインストーラをダウンロードするには、当社のダウンロード・サイトに以下のリンクからログインしてください。 https://www.nxp.com/mcuxpresso/ide/download   ドキュメント  最新ユーザーガイドおよびその他のドキュメントに補足情報が掲載されています。これらドキュメントには、「IDEのヘルプ・メニュー」から利用可能な内蔵ヘルプ・システムから、およびインストレーション・ディクショナリ内からPDFフォーム形式でアクセス可能です。   今後のリリースの通知  今後のリリースに関する通知を受け取るには、こちらのリンクをフォローしてください:MCUXpresso IDE - リリース履歴    変更の概要 - バージョン11.8.1 - 2023年10月 アップグレード:新しいSEGGER J-Linkソフトウェア(v7.92l)。 アップグレード:新しいPEmicroプラグイン(v5.7.3)。 追加:i.MX RT1180デバイスおよびMIMXRT1180-EVKボードのサポート。 追加: KE1xZ512 デバイスおよび X-FRDM-KE17Z512 ボードのサポート。 追加:MCXA153デバイスおよびFRDM-MCXA153ボードのサポート。 改善:[ツールチェーン統合]サポートされているコンパイラ方言のリストにC++20とC++23のエントリを追加。 修正済み:[デバッガー][RW61x] セキュアプロジェクトがフラッシュにある場合、SYSRESET後にConnectスクリプトが停止しない問題を修正しました。 修正:[Flashプログラマ]Flashブランク・コマンドに関連するいくつかの問題を修正。 修正:[SDK統合]デバイス・パッケージを変更する際に、デバイス固有のプリプロセッサ定義が考慮されない問題を修正。   既知の問題  詳細なリストについては、インストール・レイアウトのKnownIssues.txtファイルを参照してください。  
View full article
TJA1410 接收信号RX+ED 如何进行RZI解码? 根据手册中的波形可以看到,RX 忽略了第一次又高阻(或者0)开始的跳变,导致RX少一个跳变,RZI解码出错。 想问一下NXP,TJA1410 这种情况下,有建议的解码方式吗? Ethernet Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 首先,请您澄清一下,这是基于图 11 的理论问题,还是您在实现中观察到的实际 RZI 解码错误? 如果发现实际错误,请提供以下信息: TX、RX、ED 和差分线路电压波形涵盖了传输命令和数据传输的开始阶段 连接到 TJA1410 的数字 PHY 或自定义解码实现 实现开始将 RX 视为有效值的点 预期和实际解码的数据序列 如图 11 所示,突出显示的 VLINE 转换发生在从正常模式到传输模式的转换过程中。此时,线路阻抗从高阻抗变为有源阻抗,发射器开始驱动差分线路。在此转换过程中,RX 输出被明确标记为未定义。因此,高亮区域中显示的初始 VLINE 移动不应被解释为有效的 RZI 数据转换,该转换必须由 RX 上的脉冲表示。 在正常模式和发射模式下,接收端的默认电平为高电平。当差分 MDI 电压超过接收器触发阈值时,TJA1410 会在 RX 上产生一个低电平脉冲。此行为适用于有效的接收数据间隔。 因此,图 11 并不表明 TJA1410 忽略了第一个有效的 RZI 转换。这表明在发射器激活期间未定义 RX。有效的 RZI 解码应该只在 RX 处于有效工作区间时开始,而不是从模式转换引起的初始模拟 VLINE 移动开始。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? Hi, PavelL 请问怎样可以获取  S32K5 + TJA1410测试套件? 谢谢 Li.Wang Re: TJA1410 接收信号RX+ED 如何进行RZI解码? TJA1410 实际测试波形, TJA1410 处于Normal 模式,只接收数据,不发送数据。 图中从上到下的信号分别为:ED, RX, Vline, TRX_P, TRX_N 接收到RX 信号,并进行解码时,按RZI规则,解码出来的数据为0x04,  实际上Vline 上的数据为0x08 (BEACON) 观察信号RX,发现在Vline 由高阻变为高时,RX 没有输出低电平脉冲,也就是说RX 少了1 bit 数据,导致解码错误。 非常感谢您的回复, 谢谢! Li.Wang Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 是的,TJA1410 可以通过常见的 10BASE-T1S 网络与 LAN8670 通信。 在“安全文件”下的“文档”中,有一个 TJA1410 VHDL-AMS 仿真模型。 本产品所需文档属于受控版本,可通过签署保密协议 (NDA) 后的安全文件访问。 请在此处申请访问权限: https://www.nxp.com/webapp-signup/docstoreReg 请注意,在提交表格时,您将被要求上传有效的保密协议副本。如果贵公司目前还没有任何保密协议,请先填写保密协议申请表: https://www.nxp.com/webapp-signup/ndaReqForm 保密协议准备就绪后,您可以申请安全文件访问权限。 请查看常见问题解答以了解流程: https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS https://www.nxp.com/support/support/secure-access-rights/secure-access-rights-faqs:SEC-ACCESS-FAQS 请注意,汽车以太网受出口管制政策约束,即使在授予保密协议和安全文件访问权限后,可能仍需要额外的批准。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 感谢您提供测量数据。然而,当前的屏幕截图没有提供足够的时间分辨率来确定第一个预期的 RX 事件是否真的丢失,或者解码是否在接收到的突发信号的开头处错误对齐。 请问您能否提供以下信息: 数字 PHY 或自定义解码器的详细信息,包括 ED 和 RX 如何用于接收和比特对齐。 更高分辨率的捕获显示了突发信号开始附近的 ED、RX、TX 和差分 VLINE,理想情况下覆盖前 8 到 16 位周期。 根据目前的捕获结果,我们还不能断定 TJA1410 丢失了有效数据位。0x08 与 0x04 不匹配也可能是由于解码器如何使用 ED 和 RX 建立初始位对齐造成的。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , https://www.nxp.com/design/design-center/development-boards-and-designs/TJA1410-EVB可直接订购。 S32K5 是一款尚未正式发布的新产品 (NPI)。请注意,已获准提前体验此类产品的客户已指派了现场工程师。您指定的现场工程师应作为您解决有关本产品任何问题、疑虑或疑问的主要支持渠道。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 如图中,VLINE 由高阻变为高电压,这一变化没有在RX 上产生低电平脉冲,会导致RX 在进行RZI 解码时少产生1bit. 我还有两个问题: 1) TJA1410 可以和LAN8670 互联通行吗? 2) 贵公司由TJA1410 的 verilog 模型文件吗,或者其他可以用仿真的模型文件?用于设计数字PHY。 非常感谢回复! Li.Wang Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 文件下载下来了,非常感谢! 里面由两个模型,如下是特定软件用的,想问一下,这两个文件支持在Synopsis VCS 中仿真吗,有没有帮助文档? Xpedition is registered trademark of Siemens. SABER is a registered trademark of Synopsis. 另外文档中有一个波形,如下,其中TX 不是RZI 编码的,我理解TAJ1410 芯片TX 发送通信时,应该是给RZI 编码格式的波形是吗? Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 感谢您确认软件包已成功下载。 由于仿真模型及其文档是通过安全文件提供的,我们应该避免在公共社区论坛上讨论其详细内容。 这两个问题在下载软件包中包含的仿真模型文档中均有解答。请参阅有关支持的仿真环境、模型接口和仿真示例的章节。 贝茨致意, 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 上图为 digital PHY 发送 beacon 时的波形, 从上到下信号分别为 ED, RX, TX, TRX_P. TX 上分别为 TRANSMIT cmd,  5 times BEACON code, RESET cmd. 由几个疑点: 1 在TX 发送TRANSMIT cmd 后,RX 上多了一个低电平脉冲; 2 在TX 发送RESET cmd 后, ED 没有在130ns 内变低。 想问一下,是什么原因引起的? 谢谢! Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 图 7 提供了完整传输序列的简化概述,而图 10 则详细显示了正常模式到传输模式的转换。因此,这两个图形展现了不同层次的细节,并且彼此一致。 图 7 显示了 TRANSMIT 命令之前和 RESET 命令之后的 VLINE 高 Z 区域。当 TJA1410 正在积极传输数据时,它们并不代表 VLINE 状态。 在发送数据之前,数字 PHY 必须发出图 13 所示的 TRANSMIT 命令。该命令包含两个低电平脉冲,中间由一个高电平间隔隔开。一旦识别到命令,TJA1410 就会进入发射模式,并将线路阻抗从高阻抗变为有源阻抗,如图 10 所示。 TX 上随后出现的短低电平脉冲代表已发送的数据。每个低电平脉冲都会反转差分总线信号的极性。 数据传输完成后,数字 PHY 发出如图 12 所示的 RESET 命令。这样 TJA1410 就恢复到正常模式,发射器输出再次变为高阻抗。 因此,数据传输前的正确顺序是 TRANSMIT 命令,而不是 RESET 命令或单个数据脉冲。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 根据图10, 进入Transmitting 模式之后,Vline 就不是高阻态。但是图7中显示在Transmiiting 模式下,Vline 为高阻,并且在一个低电平脉冲之后,Vline 变位高。 所以正式发送数据前,究竟是法两个低电平脉冲的RESET 命令,还是 发送一个低电平脉冲? Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 在发送命令之后,接收端可能会出现额外的低电平脉冲,这是因为发射器从高阻抗状态变为主动驱动状态,并且差分 MDI 电压超过了接收机阈值。在此模式转换期间的 RX 不应被解释为有效的接收数据,因此该脉冲不应包含在 BEACON 解码中。 关于 ED,RESET 命令指定的 55 ns 至 120 ns 时间是TX 命令解除断言时间,而不是 ED 的最大解除断言时间。即使 MDI 仍检测到活动,ED 也可能仍然很高。 为了进行更精确的评估,您应该测量差分 VLINE。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 上图为 digital PHY 发送 beacon 时的波形,测试中只有一个TJA1410,TRX_P. TRX_N 为floating 状态。 从上到下信号分别为 ED, RX, VLINE,TRX_P. TRX_N TX 上分别为 TRANSMIT cmd, 5 times BEACON code, RESET cmd. 与上一副图片一样。 TX  发送 TRANSMIT cmd, VLINE 上产生了一个变高的pulse;  不期望的异常情况; RESET cmd 之后,VLINE 为0, 但ED 持续了近20us; 不符合预期; 帮忙看一下是什么原因造成的? 请问Pavel, 贵公司有发送数据时的流程吗?以及对应的波形吗? 有的话可以提供给我,或在发我的邮件,谢谢! Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 请问在这种单节点架构下,MDI是如何终止的?尤其请确认是否使用了推荐的总线接口网络,以及是否启用了终端节点终止功能。 目前尚无来自两个 TJA1410 设备之间通信的测量参考波形。我也无法重现此设置,因为所需的数字 PHY 集成在 S32K5 中,而 S32K5 仍然是 NPI 设备,如前所述。因此,我的分析仅基于现有的 TJA1410 文档。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? 你好@li_wang , 由于 TRX_P 和 TRX_N 处于浮空状态,因此测量结果不能代表正确连接的 10BASE-T1S 接口。 请将MDI端接至所需的差分阻抗,并重复测量。 顺祝商祺! 帕维尔 Re: TJA1410 接收信号RX+ED 如何进行RZI解码? Hi, PavelL 可能"floating 状态"  表述引起误解,这里实际时表示双绞线上只有一个Node 设备,即只有一个TJA1410. 所以没有任何其他干扰因素。同时VLINE 信号为TRX_P - TRX_N。 贵公司是否有demo 板上的测试波形,比如两个TJA1410 相关通行时的接收和发送实测波形?
View full article
Verify a csf header file is associated with a specific fit image. I have secure boot working and I understand roughly what Uboot is doing using esbc_validate. However, I'm trying to create an upgrade utility that verifies that a specific header file, generated with cst 2.x, is associated with a specific fit (kernel, dtbs, rootfs) image. Placing the csf security header at its correct offset, and placing the fit image at its offset works just fine for booting. However I want to verify those PRIOR to placing them in their respective locations.  I understand the public key is embedded in the csf so I have to extract that. I'm a little confused after that. I think I need to extract the RSA signature and use the extracted public key on that to get a hash, and somehow that hash is tied to the fit image, but its not simply a hash of the fit image? I've already managed to pull the SRKH from the blown fuses so I can compare that. At the moment Google/Gemini isn't being much help. Thoughts?  QorIQ LS1 Devices Re: Verify a csf header file is associated with a specific fit image. The signature is not just a hash of the FIT . For this secure-boot flow, it authenticates a SHA-256 digest of the CSF header, the image bytes specified by that header, the public key material, and the SG table if used. Validation also checks the key against the fused SRKH.  So, before installing either file , your utility must parse the candidate header, use its size and offset fields to select the correct bytes from the candidate FIT, calculate the digest over the complete signed data, and verify the extracted RSA signature with the validated public key. If verification passes, that header is associated with those authenticated FIT bytes. A FIT-only SHA-256 comparison will not work.
View full article
Choosing an MPU for PXI controller I want to create an open-source PXI chassis controller (if someone doesn't know, it's basically an ARM SBC, connected to backplane via PCIe, peripheral PXI modules do the same, but have PCIe EP instead of RC) So, I need an MPU that can run linux distr, e.g. Ubuntu, in graphic mode with decent performance, as some specialised software would be running on it, e.g. LabVIEW and custom peripheral modules control utilities, that process Gbs of raw data per second. It should also have at least 2 independent PCIe RCs, as denanded by PXI spec, and the faster they are the better: if they are fast enough, it would be possible to e.g. feed DAC in RF AWG with raw data continuously, not limited by AWG ram size. Also a possibility to connect a lot of LPDDR4 would be cool, not just typical 32 bit bus, but 64+ The new TI Am69a looks like a cool thing, but it seems like it's going to cost a lot, and it's very new, so no full errata, no software examples, drivers and so on - looks too challenging for me, being a hardware developer and coding only as hobby Another way would be Rockchip RK3588, it's more affordable and older, but it's PCIe is too slow, just 2x2 gen 3. I could definitely live with it, but... Maybe you have better ideas or done something similar recently? Would be grateful to hear them 🙂 USB Re: Choosing an MPU for PXI controller Hi, Thank you for your interest in NXP Semiconductor products, For PCIe requirement, latest PCIe generation in industrial processors is Gen 3. LS2048/88A has 4 PCIe controllers (Gen3) supporting 1x8, 4x4, 4x2, 4x1 lane configurations and LX2160A has Up to 24 PCIe Gen3 lanes, supporting ports as wide as x8. Layerscape also has the outperforming ethernet connectivity capable of processing more than a couple Gbps of data. DDR is also satisfied with 2x controllers of 64 and 72 bits respectively, however, they run on DDR4. https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-processors:QORIQ-ARM Another con is that they cannot run graphical interfaces natively, industrial graphics processors are i.MX processors, they run on 32-bit DDR, up to 10 Gbps ethernet, up to 2x PCIe Gen 3, they can run graphics though. Regards
View full article
Example S32K358 PWM ADC_HWtrig BCTU_TriggerMode RTD600 EBTresos29 ********************************************************************************* * Detailed Description: * * ADC hardware trigger demonstration using BCTU Trigger Mode on S32K358. * * An eMIOS1 Channel 23 reload event is used as a trigger source for the BCTU). * The BCTU initiates a hardware-triggered conversion of an ADC1 group containing * three channels. * * The result of the third ADC channel, connected to the on-board potentiometer * (ADCPOT0), is used to dynamically update the duty cycle of an * eMIOS Channel 5 PWM output. * * The PWM output drives the on-board LED, allowing the potentiometer position * to control LED brightness. * * Key Functionality: * - eMIOS-triggered BCTU operation. * - BCTU Trigger Mode configuration. * - ADC1 hardware-triggered group conversion. * - ADC notification callback processing. * - PWM duty-cycle update based on ADC result. * - LED brightness control using the potentiometer. * * ------------------------------------------------------------------------------ * Test HW: S32K3x8EVB-Q289 * MCU: S32K358 * IDE: EB Tresos 29.0.0 * RTD Release: S32K3_RTD_6_0_0_D2506_ASR_REL_4_7_REV_0000_20250610 * Debugger: Lauterbach * Target: Internal_FLASH ******************************************************************************** * Revision History: * Ver Date Author Description of Changes * 1.0 02-10-2026 Petr Stancik Initial version ********************************************************************************
View full article
wifi driver crashes- 88w8997 I am facing an intermittent Wi-Fi driver crash issue with the FN-Link L297B-SR module (Wi-Fi and Bluetooth sharing a single antenna). The issue occurs randomly, sometimes after 1 day, sometimes after 2 days, and occasionally only after 4 to 5 days of continuous operation. please check the logs  [64622.321614] mwifiex_sdio mmc2:0001:1: info: successfully disconnected from ca:c6:5c:cb:ad:7e: reason code 3 [64624.050010] mwifiex_sdio mmc2:0001:1: info: trying to associate to bssid ca:c6:5c:cb:ad:7e [64624.072596] mwifiex_sdio mmc2:0001:1: event: unknown event id: 0x95 [64624.085770] mwifiex_sdio mmc2:0001:1: info: associated to bssid ca:c6:5c:cb:ad:7e successfully [64987.640381] Bluetooth: hci0: Frame reassembly failed (-84) [65060.466817] Bluetooth: hci0: Frame reassembly failed (-84) [65184.303423] mwifiex_sdio mmc2:0001:1: info: successfully disconnected from ca:c6:5c:cb:ad:7e: reason code 0 [65204.712100] ieee80211 phy0: sched_scan start : n_ssids=4 n_match_sets=4 [65204.725038] ieee80211 phy0: n_channels=41 interval=10 ie_len=13 [65259.046894] ieee80211 phy0: sched scan stop! [65259.067983] mwifiex_sdio mmc2:0001:1: info: trying to associate to bssid ca:c6:5c:cb:ad:7e [65260.594440] mwifiex_sdio mmc2:0001:1: ASSOC_RESP: failed, status code=2 err=0xfffa a_id=0x3fff [65260.611662] mwifiex_sdio mmc2:0001:1: assoc failure: reason Unknown connect failure [65260.624191] mwifiex_sdio mmc2:0001:1: info: association to bssid ca:c6:5c:cb:ad:7e failed [65260.636278] ieee80211 phy0: sched_scan start : n_ssids=4 n_match_sets=4 [65260.645499] ieee80211 phy0: n_channels=41 interval=10 ie_len=13 [65271.191030] mwifiex_sdio mmc2:0001:1: mwifiex_cmd_timeout_func: Timeout cmd id = 0x6b, act = 0x1 [65271.199985] mwifiex_sdio mmc2:0001:1: num_data_h2c_failure = 0 [65271.205896] mwifiex_sdio mmc2:0001:1: num_cmd_h2c_failure = 0 [65271.211654] mwifiex_sdio mmc2:0001:1: is_cmd_timedout = 1 [65271.217064] mwifiex_sdio mmc2:0001:1: num_tx_timeout = 0 [65271.222454] mwifiex_sdio mmc2:0001:1: last_cmd_index = 0 [65271.227893] mwifiex_sdio mmc2:0001:1: last_cmd_id: 6b 00 28 00 16 00 12 00 6b 00 [65271.235303] mwifiex_sdio mmc2:0001:1: last_cmd_act: 01 00 13 00 01 00 ca c6 01 00 [65271.242862] mwifiex_sdio mmc2:0001:1: last_cmd_resp_index = 4 [65271.248670] mwifiex_sdio mmc2:0001:1: last_cmd_resp_id: 0c 81 28 80 16 80 12 80 6b 80 [65271.256568] mwifiex_sdio mmc2:0001:1: last_event_index = 3 [65271.262131] mwifiex_sdio mmc2:0001:1: last_event: 18 00 0b 00 0a 00 65 00 0a 00 [65271.269514] mwifiex_sdio mmc2:0001:1: data_sent=0 cmd_sent=1 [65271.275248] mwifiex_sdio mmc2:0001:1: ps_mode=1 ps_state=0 [65271.281497] mwifiex_sdio mmc2:0001:1: Ignore scan. Card removed or firmware in bad state [65271.290880] mwifiex_sdio mmc2:0001:1: ===mwifiex driverinfo dump start=== [65271.317907] mwifiex_sdio mmc2:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.92.21.p76) [65271.326650] mwifiex_sdio mmc2:0001:1: scan failed: -14 [65271.350746] mwifiex_sdio mmc2:0001:1: SDIO register dump start [65271.369462] mwifiex_sdio mmc2:0001:1: SDIO Func0 (0x0-0x9): 43 03 02 02 03 02 00 02 03 00 [65271.385505] mwifiex_sdio mmc2:0001:1: SDIO Func1 (0x10-0x17): 00 00 00 00 00 00 e0 ff [65271.396619] mwifiex_sdio mmc2:0001:1: SDIO Func1: (0x8) c3 (0x58) 00 (0x5c) 48 (0x5d) 00 (0x60) 07 (0x61) 0c (0x62) 00 (0x64) 10 (0x65) 00 (0x66) 00 (0x68) 00 (0x69) 00 (0x6a) 00 [65271.416154] mwifiex_sdio mmc2:0001:1: SDIO Func1 (0xe8-0xf2): dc fe 7e 00 62 00 3f a7 24 14 70 [65271.580586] mwifiex_sdio mmc2:0001:1: SDIO Func1 (0xe8-0xf2): dc fe 8f 00 73 00 3f a7 24 14 70 [65271.594858] mwifiex_sdio mmc2:0001:1: SDIO register dump end [65271.610712] mwifiex_sdio mmc2:0001:1: ===mwifiex driverinfo dump end=== [65271.628592] mwifiex_sdio mmc2:0001:1: == mwifiex firmware dump start == [65271.666427] mwifiex_sdio mmc2:0001:1: Fail to pull ctrl_data [65271.676062] mwifiex_sdio mmc2:0001:1: firmware dump failed [65271.693018] mwifiex_sdio mmc2:0001:1: == mwifiex dump information to /sys/class/devcoredump start [65271.710201] mwifiex_sdio mmc2:0001:1: == mwifiex dump information to /sys/class/devcoredump end [65271.723737] mwifiex_sdio mmc2:0001:1: PREP_CMD: FW is in bad state [65271.735173] mwifiex_sdio mmc2:0001:1: info: shutdown mwifiex... [65271.769056] mwifiex_sdio mmc2:0001:1: PREP_CMD: card is removed [65271.812192] mwifiex_sdio mmc2:0001:1: PREP_CMD: card is removed [65271.855652] Bluetooth: hci0: Frame reassembly failed (-84) [65271.870925] Bluetooth: hci0: Frame reassembly failed (-84) [65271.967852] Bluetooth: hci0: Frame reassembly failed (-84) [65272.068050] Bluetooth: hci0: Frame reassembly failed (-84) [65272.168010] Bluetooth: hci0: Frame reassembly failed (-84) [65272.268029] Bluetooth: hci0: Frame reassembly failed (-84) [65272.368215] Bluetooth: hci0: Frame reassembly failed (-84) [65272.468007] Bluetooth: hci0: Frame reassembly failed (-84) [65272.567994] Bluetooth: hci0: Frame reassembly failed (-84) [65272.668015] Bluetooth: hci0: Frame reassembly failed (-84) [65272.768055] Bluetooth: hci0: Frame reassembly failed (-84) [65272.839448] mwifiex_sdio mmc2:0001:1: info: FW download over, size 622240 bytes [65273.607175] mwifiex_sdio mmc2:0001:1: WLAN FW is active [65273.641454] mwifiex_sdio mmc2:0001:1: Unknown api_id: 5 [65273.687228] mwifiex_sdio mmc2:0001:1: info: MWIFIEX VERSION: mwifiex 1.0 (16.92.21.p76) [65273.713221] mwifiex_sdio mmc2:0001:1: driver_version = mwifiex 1.0 (16.92.21.p76) [65277.145122] mwifiex_sdio mmc2:0001:1: info: trying to associate to bssid ca:39:a3:cb:ad:7e [65278.668157] mwifiex_sdio mmc2:0001:1: ASSOC_RESP: failed, status code=2 err=0xfffc a_id=0x3fff [65278.677711] mwifiex_sdio mmc2:0001:1: assoc failure: reason CONNECT_ERR_ASSOC_ERR_TIMEOUT [65278.691251] mwifiex_sdio mmc2:0001:1: ASSOC_RESP: AUTH timeout [65278.710528] mwifiex_sdio mmc2:0001:1: info: association to bssid ca:39:a3:cb:ad:7e failed [65279.781236] mwifiex_sdio mmc2:0001:1: info: trying to associate to bssid ca:c6:5c:cb:ad:7e [65281.310722] mwifiex_sdio mmc2:0001:1: ASSOC_RESP: failed, status code=2 err=0xfffa a_id=0x3fff [65281.320307] mwifiex_sdio mmc2:0001:1: assoc failure: reason Unknown connect failure I found same issue on below github link but it show it is still open https://www.bing.com/ck/a?!&&p=6f8995a9ee8bc78d51549c45a34f5deee2c26e49fb129fa9306c277b1df3c48cJmltdHM9MTc5MDQ2NzIwMA&ptn=3&ver=2&hsh=4&fclid=28fe8c6f-37d9-6a8e-3ad5-9b0736ee6b90&psq=wifi+driver+crashes+while+trying+to+reconnect+-+88w8997&u=a1aHR0cHM6Ly9naXRodWIuY29tL254cC1pbXgvaW14LWZpcm13YXJlL2lzc3Vlcy81 thanks in advance Re: wifi driver crashes- 88w8997 Hi, Thank you for the detailed logs. Based on the crash information, we can see you are running firmware version 16.92.21.p76. Please note that the 88W8997 is no longer included in the standard imx-firmware releases. However, we have a dedicated hotfix branch with the latest firmware available here: https://github.com/nxp-imx/mwifiex/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 https://github.com/nxp-imx/imx-firmware/tree/hotfix/lf-6.12.49_2.2.0_hotfix_w8997 We recommend upgrading to the firmware available in that branch, which is significantly newer than your current version and includes stability fixes that may address the command timeout and firmware bad state issue you are experiencing. Regards, Daniel. Re: wifi driver crashes- 88w8997 DanielRuvalcaba thanks for the support. We loaded the hotfix firmware on the combo chip and ran it continuously for approximately one week. During this period, we encountered a different issue. Unlike the previous problem where the Wi-Fi firmware crashed, this time the Wi-Fi functionality remained operational, but BLE stopped working after 3-4 days of continuous operation. The BLE failure was not recoverable by simply resetting the HCI interface. To restore BLE functionality, we had to reload the firmware on the combo chip. We have attached the latest logs captured during the BLE failure for further analysis. [308423.524163] Bluetooth: hci0: command 0x0406 tx timeout [308454.723609] Bluetooth: hci0: command 0x2011 tx timeout [308454.728959] Bluetooth: hci0: Opcode 0x2011 failed: -110 [308454.734354] Bluetooth: hci0: Unable to add to allow list: -110 [308456.771606] Bluetooth: hci0: Opcode 0x200b failed: -110 [308456.776986] Bluetooth: hci0: command 0x200b tx timeout [308456.782265] Bluetooth: hci0: start background scanning failed: -110 [308458.819547] Bluetooth: hci0: Opcode 0x2011 failed: -110 [308458.824925] Bluetooth: hci0: command 0x2011 tx timeout [308458.830210] Bluetooth: hci0: Unable to add to allow list: -110 [308460.867534] Bluetooth: hci0: Opcode 0x200b failed: -110 [308460.872908] Bluetooth: hci0: command 0x200b tx timeout [308460.878263] Bluetooth: hci0: start background scanning failed: -110 [308462.915455] Bluetooth: hci0: Opcode 0x2011 failed: -110 [308462.920957] Bluetooth: hci0: command 0x2011 tx timeout [308462.926341] Bluetooth: hci0: Unable to add to allow list: -110 [308464.963435] Bluetooth: hci0: Opcode 0x200b failed: -110 [308464.968817] Bluetooth: hci0: command 0x200b tx timeout [308464.974104] Bluetooth: hci0: start background scanning failed: -110 [308467.747431] Bluetooth: hci0: command 0x200a tx timeout Thanks in advance.
View full article
The TCP client in S32K358 is not receiving the handshake packet. I've created a TCP client thread. When the handshake function is executed, I can see the messages sent by the client to the server and the messages sent by the server to the client using Wireshark. However, in the final step, the TCP client doesn't return a frame. I've been monitoring the GMAC receive interrupt and found it's stuck in a loop. The MCU TCP client hasn't received the final acknowledgment frame, so it hasn't sent the final handshake acknowledgment frame. What could be the reason? Re: S32K358 中TCP 客户端握手包接收不到 Hello @sunshine88, Are you using the lwip example provided inside the RTD package? If yes, could you share your RTD version?  Can you also share which status is being returned to RxStatus?  As requested on your other community post (LWIP TCP/IP Server-Client Hands-On), I've sent you a private message with the Lwip_HandsOn project for S32K148. Best regards, Julián
View full article
外部启动 S32k S32k344 设备最初是否从内部 ROM 执行不可变的第一阶段引导加载程序?如果可以,能否将此 ROM 引导加载程序配置为从外部源(例如外部闪存)加载辅助引导加载程序(或应用程序映像)? 如果支持外部启动,应该如何配置才能让初始引导加载程序知道从哪里获取启动项? Re: External Boot S32k 嗨@CTCoder1 是的,S32K344 包含 SBAF 代码,该代码在 RESET 后执行。然而,这不应被视为可以直接从任意外部存储器加载应用程序的可配置引导加载程序。不支持外部启动。 正常的 S32K3 启动流程仅要求启动信息/应用程序位于内部代码闪存中。例如,可以将用户引导加载程序放置在内部闪存的开头(IVT 地址为 0x00400000),然后执行所需的任何更新/加载机制。 因此,如果目的是将应用程序存储在外部闪存中,通常的解决方案是将用户引导加载程序放在内部闪存中。该引导加载程序初始化所需的外部/外部存储器接口,从外部设备读取映像,然后将其编程到内部闪存中,或根据应用程序的要求对其进行处理。 没有 SBAF(或者我们可以说 BootROM)配置,您只需指定外部闪存地址/设备,S32K344 SBAF 就可以直接从那里启动应用程序。这需要完全由您的软件来管理。 此致, Lukas
View full article
i.MX8DXL CAAM COVER 对 P-384 私钥/黑斑用例的限制 您好,NXP团队: 我们正在评估 i.MX8DXL CAAM 对 ECDSA P-384 黑键/blob 的支持情况。 观察到的结果 P-256 从外部提供的明文 P-256 私钥开始: 明文密钥 → 封面 → 黑键斑点 从黑斑中恢复黑键 ECDSA 签名/核实 结果:通过 P-384(CAAM 生成的黑键) 生成 ECDSA 私钥,颜色为 KEY_COLOR_BLACK 无需 COVER 操作即可从私钥生成黑块 从黑斑中恢复黑键 ECDSA 签名/核实 结果:通过 P-384(外部明文私钥) 从外部提供的明文 P-384 私钥(48 字节)开始: 明文密钥 → 封面 → 黑键斑点 从黑斑中恢复黑键 ECDSA 签名/核实 结果:失败 补充观察 我们在NXP的补丁中注意到以下注释: https://github.com/nxp-imx-support/imx_sec_apps/blob/master/caam-ecdsa-blackkey/patch/0002-caam-black-key-blob-feature.patch /* * KEY 命令似乎限制为 32 字节,因此我们应该使用加载方式。 * 改为使用最多可加载 64 字节的命令。 * * TODO:KEY 命令表明它应该能够加载更大的密钥。 * 小于 32 字节,但实际上行不通 * * TODO:LOAD 命令表明它应该能够加载最多 96 个文件 * 字节键在实践中不起作用,并且限制为 64 字节。 */ 我们观察到了类似的行为。 使用 LOAD 命令而不是 KEY 命令,我们可以处理大于 32 字节的密钥,包括 48 字节的 P-384 私钥。 然而,这并不能解决上述问题。虽然可以将密钥覆盖并存储在一个块状物中,但恢复后的黑密钥不能成功用于 ECDSA 签名/验证。   我们的疑问: CAAM COVER 操作对于大于 32 字节的 ECC 私钥是否存在任何已知限制? 通过 COVER 导入外部 P-384 明文私钥,然后将其用作 ECDSA 黑密钥,这是否是支持的用例? 观察到的这种现象是否是由于 CAAM 硬件限制造成的? 是否有推荐的 CAAM 方法可以导入外部生成的 P-384 明文私钥并将其用作 ECDSA 操作的黑密钥? 任何指导都将不胜感激。 谢谢,并致以最诚挚的问候! 霍詹姆斯。 Re: i.MX8DXL CAAM COVER limitation for P-384 private key / black blob use case 补充说明:   我们关注的重点不仅限于 ECDSA 用例。   即使通过 COVER 导入外部 P-384 私钥不是 ECDSA 支持的工作流程,我们仍然想了解 COVER 操作本身的局限性。   在我们的应用中,COVER 操作不仅可以用于保护 ECDSA 私钥,还可以用于保护一般敏感数据。因此,支持大于 32 字节的有效载荷大小是一个重要的考虑因素。 根据我们的测试,使用 LOAD 命令变通方法可以处理大于 32 字节的有效载荷。小于约 80 字节的有效载荷似乎可以正常工作,而更大的有效载荷则表现出不稳定的行为。我们想了解这些观察结果反映的是 CAAM 的实际局限性还是实施问题。 NXP能否也澄清一下,COVER 操作本身是否存在任何已记录的大小限制,而与 ECDSA 用例无关?   谢谢! Re: i.MX8DXL CAAM COVER limitation for P-384 private key / black blob use case 我们需要搭建测试CAAM功能的环境。一旦有了结果,我们会立即通知您。 Re: i.MX8DXL CAAM COVER limitation for P-384 private key / black blob use case 王一平您好, 谢谢回复。 >>对于这一部分,您观察到了什么CAAM错误? >>请提供错误代码? 我们对所有与 ECDSA 相关的操作都使用以下代码补丁: " https://github.com/nxp-imx-support/imx_sec_apps/blob/master/caam-ecdsa-blackkey/patch/0001-linux-imx-4.14.78_1.0.0_ga-ecdsa-primitives-using-caam.patch " 当调用 caam_ecdsa_verify() 进行签名验证时, 它返回“ECDSA_VERIFY_FAIL (0)”。 仅当使用“P-384(外部明文私钥)”时才会出现错误。 >> 应用笔记“AN12838-使用 CAAM 安全密钥加强公钥密码学”描述了使用黑密钥的 ECDSA 签名演示,您是否正在使用类似的实现进行测试? 对于我们成功的案例,是的,它们很相似。 但对于我们失败的案例“P-384(外部明文私钥)”, 情况略有不同:密钥来自外部。 顺祝商祺! Re: i.MX8DXL CAAM COVER limitation for P-384 private key / black blob use case “明文密钥 → 封面 → 黑键斑点 从黑斑中恢复黑键 ECDSA 签名/核实 结果:失败 在这一部分,你观察到了什么CAAM错误?能否提供错误代码?应用笔记“AN12838-使用 CAAM 安全密钥加强公钥密码学”描述了使用黑密钥的 ECDSA 签名演示,您是否正在使用类似的实现进行测试?谢谢。 关于KEY命令的限制,目前仍在调查中。 Re: i.MX8DXL CAAM COVER limitation for P-384 private key / black blob use case 对于失败的案例,您是否使用“KEY”命令和“FIFO STORE”命令根据明文私钥生成黑密钥?您能否提供故障案例中使用的 CAAM 描述符(十六进制单词)?检查命令和参数会更容易些。谢谢。 Re: i.MX8DXL CAAM COVER limitation for P-384 private key / black blob use case 王一平您好, >>对于失败的案例, >>您是否使用了“KEY”命令和“FIFO STORE”命令? >>如何根据明文私钥生成黑密钥? 不,我们使用的是 LOAD 命令而不是 KEY 命令。 在这种情况下,密钥为 48 字节 (P384)。 如 < https://github.com/nxp-imx-support/imx_sec_apps/blob/master/caam-ecdsa-blackkey/patch/0002-caam-black-key-blob-feature.patch > 中所述 “KEY 命令似乎限制为 32 字节,因此我们应该使用加载 * 改为使用最多可加载 64 字节的命令。 如果使用 KEY 命令输入 48 字节的密钥,则会报告 DECO 错误: 作业环状态:0x40000106 DECO,06h - 无效的 KEY 命令 因此,我们修改了代码,使其使用与上述补丁代码相同的 LOAD 命令。 谢谢,并致以最诚挚的问候! Re: i.MX8DXL CAAM COVER limitation for P-384 private key / black blob use case 我已经验证过,可以使用KEY命令将ECC P-384密钥加载到PKHA-E内存中,并且该密钥随后可用于ECDSA签名和验证。 请检查您是否在 KEY 命令中使用“Class 1”寄存器,MX8DXL 上的 Class 1 Key 寄存器为 32 字节。所以请改用PKHA-E内存。 以下是 CAAM 描述符供您参考:将明文私钥转换为黑钥,CAAM 命令为“KEY” + “FIFO STORE”。 b0800005 02010030    // 密钥 60220030 ....0.....t.0."` // FIFO SOTRE 请根据问题查看回复: CAAM COVER 操作对于大于 32 字节的 ECC 私钥是否存在任何已知限制? KEY 命令可以有效地将数据加载到 KEY 寄存器中,但只能加载到各自的最大值。因此,1 类密钥寄存器、2 类密钥寄存器和 PKHA E 寄存器都可以通过 KEY 命令加载,但它们的大小各不相同。一般来说,2 类密钥寄存器(128 字节)比 1 类密钥寄存器大,因此可以在此过程中用 2 类密钥寄存器代替 ECC 密钥(ECC 密钥的大小不会超过 1028 字节)。更一般地说,您可以始终使用 KEY 命令将 ECC 钥匙放入 PKHA E 中,然后将其作为黑钥匙存储。 通过 COVER 导入外部 P-384 明文私钥,然后将其用作 ECDSA 黑密钥,这是否是支持的用例? 是的,ECDSA Sign 操作接受黑色钥匙进行签名。 观察到的这种现象是否是由于 CAAM 硬件限制造成的? 是的。 如果加载(或存储)的数据超过寄存器的大小,就会进入死区——因此,加载到死区的字节会丢失,而存储的字节的值将为零。MX8DXL 上的 Class 1 密钥寄存器为 32 字节(256 位),足以处理 AES 等可用对称密码引擎的密钥。 是否有推荐的 CAAM 方法可以导入外部生成的 P-384 明文私钥并将其用作 ECDSA 操作的黑密钥? 是的。将其加载到 PKE(PKHA E 寄存器)中,然后像处理 1 类密钥一样从那里执行 FIFO 存储(只需使用不同的寄存器源)。
View full article
88W9098 Energy Detect (ed_mac) tuning Hello, We are using the 88W9098 in a u-blox M2-JODY-W377 over SDIO running at SDR50. We have driver/firmware versions lf-6.18.20_2.0.0 from github. We are using it as an Access Point in 2.4ghz channel 6. We are encountering an issue where enabling ed_mac (with "init_hostcmd_cfg=nxp/ed_mac.bin" in wifi_mod_para.conf, or using mlanutl with ed_mac_ctrl_V3_909x.conf) leads to much worse stability/latency of our in-house applicative tests : ed_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.pnged_mac_test.png I can't go too much into detail about the test here, but it is end-to-end latency measurement of specific in-house steps, using multiple machines with a 88W9098 Access Point in the middle. Not only are some curves 200-250ms higher in average with ed_mac than without, but overall they are also more spiky and tend to have random "bursts" of added latency. We have tried tuning the offsets "ed_ctrl_2g.offset" and "ed_ctrl_5g.offset" to values different than the default 0x8, but no value that we tried had any effect on the test. The only way to have an impact is to set both enable (2g/5g) to 0, or to not load the file at boot. Is there anything else we can try? Re: 88W9098 Energy Detect (ed_mac) tuning Dear @mjourdan , Thank you for the detailed description and test data. The behavior you are seeing is actually expected given how the ed_mac (Energy Detect MAC) feature is designed, but there are several things worth checking and clarifying. Why ed_mac causes higher latency in AP mode The ed_mac feature is designed specifically for the EU ETSI EN 300 328 adaptivity compliance test. Its core mechanism is to actively suppress transmissions when the firmware detects energy on the channel above a threshold. In an Access Point scenario, this directly delays buffered downlink packets whenever the radio detects ambient energy, resulting in the latency spikes and "bursts" you are measuring. Adjusting the offset parameter changes the threshold sensitivity (how easily the radio is triggered), but it does not remove the suppression behavior itself — which is why no offset value had any measurable effect on your end-to-end latency test. Configuration file mismatch I notice you are using ed_mac_ctrl_V3_909x.conf. According to our application note AN13756, the correct configuration file for 88W9098 is ed_mac_ctrl_V2_909x.conf (with default ed_ctrl_2g.offset = 0x08 and ed_ctrl_5g.offset = 0x08). The V3 variant uses a different ed_ctrl_txq_lock field value and is not the validated configuration for this device. Please try using ed_mac_ctrl_V2_909x.conf and test whether the latency impact improves. Key question: Is EU adaptivity compliance required for your deployment? The ETSI EN 300 328 adaptivity requirement only applies to devices operating in EU/EEA markets and with a declared maximum RF output power of 10 dBm EIRP or above. Could you confirm: Is this device deployed in the EU and subject to ETSI EN 300 328 certification? What is the declared RF output power of your module (u-blox M2-JODY-W377)? If EU compliance is not required for your use case, the correct solution is simply to not load the ed_mac configuration — which you have already confirmed resolves the latency issue completely. If compliance is required, we recommend switching to ed_mac_ctrl_V2_909x.conf first, and if the latency issue persists, we can explore whether there is a newer firmware version that may improve the AP-mode behavior. Please let us know the answers to the above and we will follow up accordingly. Best Regards, Weidong Re: 88W9098 Energy Detect (ed_mac) tuning Thanks weidong. Yes the product definitely outputs more than 10dBm EIRP and needs to be EN 300 328 compliant. I have tried with ed_mac_ctrl_V2_909x.conf (https://github.com/u-blox/u-blox-sho-host-based/blob/main/JODY-W3/txpower_config/ed_mac_ctrl_V2_909x.conf) but there was no change in behavior. What we don't understand is that if we swap the module with one from DoodleLabs (QCA988X based) and perform the same test in the same environment, it also honors EN 300 328 but we have zero latency issues with it. So I am wondering why the 88W9098's implementation of ed_mac specifically would trigger such issues but not one from another chip maker. Besides version lf-6.18.20_2.0.0, we have also tried hotfix/lf-6.12.49_2.2.0_hotfix but the issue is still present. Some more information: * There are 2 stations associated to the JODY's access point.  * The bandwidth used during the test between a station and the JODY is very low (~6KiB/s) but consists of many small packets, mostly in STA->AP direction. Re: 88W9098 Energy Detect (ed_mac) tuning Dear @mjourdan ,   I have escalated your issue to our internal team. Let's wait for the expert's response together — I will share any updates with you as soon as I have them.   Best regards, Weidong Re: 88W9098 Energy Detect (ed_mac) tuning Dear @mjourdan , Internal team is analyzing the issue, could you please provide the following information? I got the following feedback from internal team. ====================================================== Driver loading parameters, along with the complete driver load/unload command sequence used to reproduce the issue. ed_mac_ctrl_V2_909x.conf configuration file. Logs captured while reproducing the issue for further investigation. Host details, including: Host platform Kernel version Driver version Interface being used (PCIe/SDIO)   These details will help us correlate the customer's setup with our internal testing and expedite the analysis. ====================================================== Thanks, Best Regards, Weidong Re: 88W9098 Energy Detect (ed_mac) tuning Hi weidong, I am currently troubleshooting the issue with u-blox so in order to prevent a collision in case it also gets escalated to NXP, I will be seeing with them only for now. Thank you for your help. Re: 88W9098 Energy Detect (ed_mac) tuning Dear @mjourdan , Any update? Thanks! Regards, Weidong Re: 88W9098 Energy Detect (ed_mac) tuning Dear @mjourdan , OK, got it. Thanks for your update. Best Regards, Weidong Re: 88W9098 Energy Detect (ed_mac) tuning Dear @mjourdan , Our internal team has conducted additional testing related to the issue you reported. We would like to share the test results with you and hope they can provide useful insights for your investigation. ================================================ We verified the issue on the QA setup using release SD9098---17.92.1.p149.159-MM6X17552.p22 (FP92), and the issue was not reproducible. The observed ping latency was around 1 to 2 seconds. Test Steps: Loaded the build and enabled EDMAC using the default ed_mac_ctrl_V2_909x.conf available in the release config folder. Brought up APUT in CH6. Connected two Ex-STAs. Performed ping tests from the Ex-STAs to the APUT. Scenarios Tested: auto_ds=1, ps_mode=1 auto_ds=2, ps_mode=2 APUT configured with HT20 and HT40 Security modes: OPEN and WPA3 Ex-STA power save: Enabled and Disabled To help us analyze and reproduce the customer-observed issue, could you also please provide: Load file/build details used by the customer Complete configuration and test environment details Noise/interference level observed in the customer setup Relevant logs from the customer side Once we have this information, we can perform a deeper analysis and attempt to reproduce the issue. ================================================ Thanks. Best Regards, Weidong
View full article