Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
DES-N1846 - 关于 DDR4 你需要知道的一切 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 了解 DDR4 的基础知识以及如何在 QorIQ 设备上配置 DDR4 控制器。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 了解 DDR4 的基础知识以及如何在 QorIQ 设备上配置 DDR4 控制器。 观看视频演示 设计 | 软件与服务
View full article
HMB-N1962 IPv6 低功耗蓝牙® (6LoBLE) 讲座和演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该课程将详细介绍用于在物联网环境中传输 IPv6 帧的 RFC 7668(6LoBLE)、蓝牙®低功耗 4.2 和互联网协议支持配置文件。该演示将基于 Kinetis KW41 MCU。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该课程将详细介绍用于在物联网环境中传输 IPv6 帧的 RFC 7668(6LoBLE)、蓝牙®低功耗 4.2 和互联网协议支持配置文件。该演示将基于 Kinetis KW41 MCU。 智能家居和智能建筑
View full article
KE02Z EEPROM初始化示例 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这是 Kinetis KE02Z 设备的示例,展示了如何编程 当闪存被编程时,具有初始值的 EEPROM。该示例有效 在 FRDM-KE02Z40M 板上,使用 Kinetis Design Studio (KDS) 编写 v3.0.0。该示例还使用 Processor Expert (PEx) 来配置 UART 并擦除/编程 EEPROM。EEPROM编程与P&E配合使用 Micro Multilink Universal 调试器,以及 P&E Micro OpenSDA 调试器 FRDM-KE02Z40M 板的应用程序。 为了使用初始值对 EEPROM 进行编程,应用程序声明常量 用于 EEPROM 位置,并在 eeprom.c 中的源代码中初始化这些。 编译器指令/属性用于强制链接器将这些 EEPROM 中的常量,使用链接器中定义的 m_eeprom 内存部分 命令文件\Project_Settings\Linker_Files\ProcessorExpert.ld。P&E 微闪存编程算法以 4 字节字初始化 EEPROM。 因此,任何初始化的 EEPROM 位置都应是对齐的 4 字节字。 此示例将 EEPROM 中的前 4 个字节初始化为 0、64、128、192。 该示例使用终端程序显示 EEPROM 信息。它连接 使用 KE02Z 的 UART1 连接到 FRDM-KE02Z40M 板上的 OpenSDA COM 端口。 终端设置如下: 波特率:38,400 数据:8位 奇偶校验:无 停止:1位 流量控制:无 该示例在重置后将 5 个字节的 EEPROM 打印到终端:4 初始化的字节,加上未初始化的以下 EEPROM 字节。 然后示例将第一个字节增加,并将第二个字节减少, 并将新值写回 EEPROM。其余3个字节不变。 然后应用程序打印所有 5 个字节的新 EEPROM 值。每次 MCU 复位后,会打印现有的 EEPROM 数据,然后打印更改的 数据。下面是最初从终端输出的示例 对 KE02Z 进行编程,然后进行一次重置: 终端输出: KE02Z EEPROM示例 复位后 EEPROM 值 = 0 64 128 192 255 更新后的 EEPROM 值 = 1 63 128 192 255 KE02Z EEPROM示例 复位后 EEPROM 值 = 1 63 128 192 255 更新后的 EEPROM 值 = 2 62 128 192 255 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这是 Kinetis KE02Z 设备的示例,展示了如何编程 当闪存被编程时,具有初始值的 EEPROM。该示例有效 在 FRDM-KE02Z40M 板上,使用 Kinetis Design Studio (KDS) 编写 v3.0.0。该示例还使用 Processor Expert (PEx) 来配置 UART 并擦除/编程 EEPROM。EEPROM编程与P&E配合使用 Micro Multilink Universal 调试器,以及 P&E Micro OpenSDA 调试器 FRDM-KE02Z40M 板的应用程序。 为了使用初始值对 EEPROM 进行编程,应用程序声明常量 用于 EEPROM 位置,并在 eeprom.c 中的源代码中初始化这些。 编译器指令/属性用于强制链接器将这些 EEPROM 中的常量,使用链接器中定义的 m_eeprom 内存部分 命令文件\Project_Settings\Linker_Files\ProcessorExpert.ld。P&E 微闪存编程算法以 4 字节字初始化 EEPROM。 因此,任何初始化的 EEPROM 位置都应是对齐的 4 字节字。 此示例将 EEPROM 中的前 4 个字节初始化为 0、64、128、192。 该示例使用终端程序显示 EEPROM 信息。它连接 使用 KE02Z 的 UART1 连接到 FRDM-KE02Z40M 板上的 OpenSDA COM 端口。 终端设置如下: 波特率:38,400 数据:8位 奇偶校验:无 停止:1位 流量控制:无 该示例在重置后将 5 个字节的 EEPROM 打印到终端:4 初始化的字节,加上未初始化的以下 EEPROM 字节。 然后示例将第一个字节增加,并将第二个字节减少, 并将新值写回 EEPROM。其余3个字节不变。 然后应用程序打印所有 5 个字节的新 EEPROM 值。每次 MCU 复位后,会打印现有的 EEPROM 数据,然后打印更改的 数据。下面是最初从终端输出的示例 对 KE02Z 进行编程,然后进行一次重置: 终端输出: KE02Z EEPROM示例 复位后 EEPROM 值 = 0 64 128 192 255 更新后的 EEPROM 值 = 1 63 128 192 255 KE02Z EEPROM示例 复位后 EEPROM 值 = 1 63 128 192 255 更新后的 EEPROM 值 = 2 62 128 192 255 Kinetis E系列MCU Kinetis EA系列MCU
View full article
DwF物联网无线模块解决方案 - 广州 - 2015-06-11 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 智能家居和建筑 实践研讨会:物联网 Wi-Fi 模块开发套件 - 快速入门 智能网络
View full article
Multilink Rev C の問題 - MCU V10.6 Update3 のインストール後および MCF V7.2 の CW 後に動作しない <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MCU V10.6 Update3 以降、Multilink Rev C が動作しない Multilink Rev C が MCF V7.2 の CW で動作しない                                       A- 説明   この問題は、Mulitilink Universal Rev Cでのみ発生します。 MCU V10.6 Update 3 は Mulilink Universal Rev B で正常に動作しています。   デフォルトの MCU v10.6 では、S12Z ボード上の Multilink Universal Rev C は正常に動作しています。 MCU V10.6 Update 3 (+最新のパッチ/アップデート - 5月末) をインストールした後、デバッガを初めて起動すると、CodeWarrior は Multilink Universal インターフェイス用の新しいファームウェアが利用可能であることを検出します。 ファームウェアは自動的に更新されます。   ただし、新しいファームウェアには問題があります: Usbmlfsufbdmens.0930 場合によっては、オンボードでアプリケーションをデバッグできないことがあります。       B- ソリューション   MCU 10.6 update 3 には、ファームウェア Usbmlfsufbdmens.0930 が含まれています ただし、このファームウェアにはいくつかの問題があります。 P&Eは、9.30から9.35の間にS12関連の多くの問題に対処した。 最新バージョン(Usbmlfsufbdmens.0935)へのアップデートを推奨します。このデバッグモジュールでデバイスをターゲットにする場合。   最新バージョンは、P&EのWebサイトからダウンロードできます。                 http://www.pemicro.com/downloads/download_file.cfm?download_id=346   添付されているアップデートも見つかります。   この問題はCodeWarrior MCU V10.6.4で解決されました      新しい CodeWarrior for MCU v10.6.4 リリース     C- その他のケース – Classic IDE MCF V7.2   構成: Coldfire V7.2 の CW と ColdFire 54452 Ext FLASH のマルチリンク ユニバーサル Rev C。 アプリケーションをボードにロードしようとすると、「フラッシュIDの取得に失敗しました」というエラーが表示されます。 最後のP&Eファームウェアをインストールした後、問題も解決しました。   問題を回避するために、P&Eのフィードバックに従って、P&EのWebサイトからダウンロードできる最新のP&Eアップデート を常に インストールすることをお勧めします。                 http://www.pemicro.com/downloads/download_file.cfm?download_id=346 全般
View full article
How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Are you ready for IPv6? The worldwide transition to IPv6 networking is in progress.  Many governments and organizations have already mandated IPv6.  Are your connected products going to be ready? If you need a full-featured traditional host stack with Ipv6 support, Freescale MQX software has a solution for you.  You can even run Ipv4 and Ipv6 at the same time to ease the transition. Check out www.freescale.com/mqx/ipv6 for details and documentation. How to get IPv6? Purchase the add-on at the link above (evaluation available – see below).  The MQX TCP/IP stack (RTCS) supports IPv6 with this optional add-on patch.  Purchasing the add-on gets you all the source code and a year of basic support. How to Evaluate MQX IPv6? Freescale offers a 90-day evaluation of a pre-compiled library for a single low-cost Freescale development platform and toolchain.  In the future, evaluation versions are planned for a broader list of development platforms and toolchains. To evaluate MQX IPv6 today, you will need: MQX RTOS v4.1.1 FRDM-K64F, Freescale Freedom Development Platform for Kinetis K64 IAR Embedded Workbench® for ARM® v7.10.3 Note: Although the evaluation only covers a single board and toolchain, MQX RTCS with IPv6 source code can be purchased for ALL Freescale MCUs and tool-chains supported by MQX RTCS. If you need an evaluation library to support a different board or tool-chain, let me know! Step-By-Step Instructions 1. Obtain a FRDM-K64F Freedom development module from Freescale or a Freescale-authorized distributor (Details at www.freescale.com/frdm-k64f). 2. Plug in the USB cable for the debug connection and the Ethernet cable for the network connection between the board and your computer. 3. Download IAR for ARM® v7.10.3 or later (30-day evaluation available at www.iar.com). 4. Install MQX RTOS 4.1.1 (Available at www.freescale.com/mqxrtos). 5. Now get the evaluation package.  Go to www.freescale.com/mqx/ipv6. 6. Click the Download button, or download tab 7. Click IPv6 for MQX RTOS TCP/IP Stack (90-Day Binary Evaluation) 8. Read the software license agreement.  If it works for you, click I Accept. 9. After you accept, the zip file (e.g. Freescale_MQX_4_1_1_IP6_EVAL.zip) will download. After it downloads, extract the files to the root directory of the MQX 4.1.1 installation (a.k.a. directory).  The default for Windows is C:\Freescale\Freescale_MQX_4_1\. Note: The package does not overwrite or corrupt any MQX files.  It just adds new ones. 10. Open the readme file readme_ip6_eval.txt. The steps in this guide are listed there also. 11. Build the BSP, PSP, RTCS, MFS, and SHELL libraries for FRDM-K64F   a. Open IAR Embedded Workbench   b. Go to File…Open…Workspace.  Browse to \build\frdmk64f\iar   c. Open build_libs.eww 12. Got to Project…Batch Build…  (or press F8) Choose Debug Note, if you are trying to achieve the smallest code size, choose Release instead. Click Make Note: Even though this evaluation provides separate pre-compiled RTCS and SHELL libraries enabled with IPv6. Building RTCS and SHELL is needed to copy over RTCS header files into the appropriate \lib\ folder, which is referenced by application projects.     Wait for the libraries to finish building. 13.  Now, open an example project that has already been configured to use the special Ipv6-enabled rtcs and shell libraries that come with the evaluation.            Available example projects: HTTP Server example RTCS Shell example For this tutorial, I will show the HTTP Server example.      Select Project...Add Existing Project... and browse to \rtcs\examples\httpsrv\build\iar\httpsrv_ip6_frdmk64f 14. Double click on the project name httpsrv_frdmk64f Note: If you chose the Release option in the library builds: Right click on the dropdown box above the project explorer and select the Int Flash Release.  Otherwise chose Int Flash Debug, which is the default. 15. Choose Project… Make (or press F7) to build the project 16. Open the terminal program of your choice. Choose the COM port for the virtual serial connection provided by the board.  Choose 115200 baud. 17. Now, back in IAR. Choose Project…Download and Debug. Wait for it to download to the target and bring up the debug session.  Then click Go. You should see this in the terminal: Starting http server No.0 on IP 192.168.1.202 and fe80::200:5eff:fea8:1ca...[OK] Shell (build: Oct 13 2014) Copyright (c) 2013 Freescale Semiconductor; shell> shell> 18. Type help to see a list of other commands like ipconfig and ping. Windows includes IPv6 support already.  No configuration necessary.  Your computer will already have an auto-configured link-local Ipv6 address. 19. Now open a web browser 20. Type in the Ipv6 address of the board surrounded by brackets [fe80::200:5eff:fea8:1ca].  The webpage served by the board should appear. 21. You’re done.  You can now try out the shell example or use the Ipv6 evaluation library to evaluate it in your own application.  See below. Want to evaluate IPv6 in other applications? It’s easy. 1. In linker options of a user application project, replace the rtcs.a library by rtcs_ip6.a, and the shell.a library by shell_ip6.a 2. In C/C++ compiler preprocessor of a user application project, add defined symbol "RTCSCFG_ENABLE_IP6=1". 3. After that, the application is able to communicate over RTCS IPv6 communication. Best of Luck! Post any comments or feedback you have. Mac Re: How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Hello, I need an example that has a button in the HTML page by sending a command to the microconntrolador and getting an answer. I use the MQX4.0 with MK60DN512 Thanks. Samuel Re: How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Good point!  IPv6 is only a a 1-2 kB (flash) bigger than IPv4.  But when you run dual stack (IPv4 + IPv6) it does Not double the code size because they share common features.    The flash memory requirements look roughly like this: IPv4 with ARP, ICMP,UDP, Sockets enabled:  ~27k  IPv6 with ICMPv6, UDP, Sockets: ~28k IPv4+IPv6 with ARP, ICMP/ICMPv6, UDP, Sockets: ~41k If you add TCP, it increases it about ~14-15k. For RAM, Ipv6 takes just ~100 bytes extra for global data.  I don't have solid numbers on the heap, but I believe it is similar. Thanks, Mac Re: How To: Get started with IPv6 for MQX RTOS TCP/IP Stack Hi Mac. It would be nice to see what the flash and RAM usage is for IPV4 vs IPV6 vs dual stack.
View full article
Kinetisファミリーの紹介 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 発表者:LIANG PING 深センのDwF Kinetis MCUs Based on ARM® Technology (2015年1月27日)で発表 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 発表者:LIANG PING 深センのDwF Kinetis MCUs Based on ARM® Technology (2015年1月27日)で発表
View full article
FXTH8715 重型卡车 TPMS 解决方案 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 用于重型卡车的演示FXTH87 轮胎压力监测传感器解决方案将压力传感器、8 位 MCU、RF 发射器和双轴加速度计集成到单个封装中。该演示将显示 100–1500 kPa 的最高压力范围和最紧密的压力偏移。   1500 kPa 量程轮胎压力监测传感器 最小占用空间、低功耗、大客户内存容量 压力传感器、8位微控制器、射频发射器、加速度计     恩智浦特色产品 FXTH8715|胎压监测系统|压力传感器|恩智浦   其他 轮胎压力监测系统 (TPMS) | 恩智浦 汽车电子
View full article
EUF-ACC-T1574 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> フリースケールは、Kinetisマイクロコントローラを使用して自動車開発を容易にします。車載用Kinetis EAシリーズ・マイクロコントローラは、シンプルなツール、広範な開発環境、および-40°Cから125°Cの温度範囲にわたる車載グレードの認定により、市場投入までの時間を短縮します。フリースケール・オートモーティブのポートフォリオ (S32、S12、MagniV、Kinetis EA) とエコシステム <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> フリースケールは、Kinetisマイクロコントローラを使用して自動車開発を容易にします。車載用Kinetis EAシリーズ・マイクロコントローラは、シンプルなツール、広範な開発環境、および-40°Cから125°Cの温度範囲にわたる車載グレードの認定により、市場投入までの時間を短縮します。フリースケール・オートモーティブのポートフォリオ (S32、S12、MagniV、Kinetis EA) とエコシステム
View full article
Getting Started with eIQ Time Series Studio This lab will walk through how to use eIQ Time Series Studio (TSS) to create time series models for embedded microcontrollers.  It covers how to import time series data, shows how the tool can generate multiple machine learning (ML) algorithms, and describes how to deploy those generated models to your development board. eIQ Time Series Studio is available as a standalone installer or via a web interface.  This lab uses the FRDM-MCXN947 but the same steps will apply to any of the devices supported by eIQ Time Series Studio. You can also use NXP devices not listed here by selecting the closest related device family while going through the lab: MCX FRDM-MCXA156 FRDM-MCXC444 FRDM-MCXE247 FRDM-MCXN236 FRDM-MCXN947 FRDM-MCXW71 i.MX RT i.MXRT700-EVK i.MXRT685-EVK i.MXRT595-EVK MIMXRT1060-EVK MIMXRT1170-EVK MIMXRT1180-EVK i.MX6 MCIMX6ULL-EVK i.MX8 8MPLUSLPD4-PEVK i.MX9 i.MX93EVK RW FRDM-RW612 LPC LPC55S69-EVK Kinetis FRDM-K66F FRDM-KV31F FRDM-K32L3A6 DSC MC56F83000-EVK MC56F80000-EVK The labs are written for VS Code but the same concepts can be used for other IDEs.  You can also view the video below for a quick overview of the Time Series Studio process.  (function() { var wrapper = document.getElementById('lia-vid-6390665301112w960h540r760'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (view in My Videos) Also check out the ML Universal Datalogger on the App Code Hub for a tool to collect sensor data that can be used with the Time Series Studio, as well as the Time Series Studio examples on App Code Hub. Also see this document for details on how to add TSS libraries to existing projects.  --- Updated October 2026 for TSS 2.1.4 release i.MX RT
View full article
示例 S32K146-Set_whole_FlexRAM-as_RAM v0_0 S32DS.ARM.2.2 ******************************************************************************** * 文件:main.c * 所有者:David Tosenovjan * 版本:0.0 * 日期:2021年3月12日 * 分类:一般商业信息 ******************************************************************************** * 详细说明: * 示例代码将整个 4kB FlexRAM 区域配置为 SRAM 使用。 *默认情况下或批量擦除后,S32K1设备只有地址范围 * 0x1400_0000-0x1400_0DFF (3.5kB) 可供 SRAM 使用。 * 要启用剩余的 0.5kB,需要执行程序分区命令 *(使用示例中所示的设置),但只能使用空白的新 * 设备(或之前已批量擦除)。设置地址范围 * 0x1400_0000-0x1400_0FFF 用于 SRAM。 * ---------------------------------------------------------------------------------------------- *测试硬件:S32K146EVB-Q144 * 微控制器:PS32K146UAVLQ 0N73V QAC1735D * Fsys: 默认 * 调试器:Lauterbach Trace32、OpenSDA * 目标:Debug_RAM * 终端:无 * EVB连接:默认 ********************************************************************************
View full article
imx93 lvds,内核版本 6.12 我正在尝试让 LVDS 显示屏在 imx93 定制板上工作。我遇到了这个错误: imx-lcdif 4ae30000.lcd-controller: probe with driver imx-lcdif failed with error -2 添加一些跟踪信息后,发现这是驱动程序中的这一行代码(在函数 lcdif_load 中)。 lcdif->clk_axi = devm_clk_get(drm->dev, "axi"); if (IS_ERR(lcdif->clk_axi)) return PTR_ERR(lcdif->clk_axi); 所以,它似乎找不到“axi”时钟。 我使用的是内核中的设备树,即 imx93.dtsi。作为基础,其中包括以下几行: clock-names = "pix", "disp-axi", "disp-apb"; assigned-clocks = <&clk IMX93_CLK_VIDEO_PLL>, <&clk IMX93_CLK_MEDIA_DISP_PIX>, <&clk IMX93_CLK_MEDIA_AXI>, <&clk IMX93_CLK_MEDIA_APB>; 所以这里设备树和驱动程序之间存在一些不一致之处。问题是我不知道这些时钟是否正确,也不知道我应该使用哪个。 我尝试查看 6.18 分支的内容,但是这部分(lcdif 控制器)已从 imx93.dtsi 文件中完全消失了。 有什么提示吗? Re: imx93 lvds with kernel 6.12 好的,找到一个原因了,这是因为使用了错误的驱动程序。现在,使用 lcdif_v3 驱动程序,不存在时钟问题。 另一方面,我仍然会遇到这个问题。 imx93-ldb ldb-display-controller:无法与 4ae30000.lcd-controller 创建设备链接 (0x180)。 有什么提示吗? Re: imx93 lvds with kernel 6.12 你好@julienblanc 希望你一切都好。 你的问题仍然存在吗? 顺祝商祺! 萨拉斯。 Re: imx93 lvds with kernel 6.12 很遗憾,不行。 我一直遇到同样的错误。以下是我尝试的配置方法: backlight_lvds: backlight-lvds { compatible = "pwm-backlight"; status = "okay"; power-supply = <&display_power_12v>; brightness-levels = < 0 5 10 15 20 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100>; default-brightness-level = <30>; pwms = <&pwm_backlight 0 1000000 0>; }; pwm_backlight: pwm_gpio { compatible = "pwm-gpio"; #pwm-cells = <3>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_clko4_gpio>; gpios = <&gpio4 29 GPIO_ACTIVE_HIGH>; // gpio controller &gpio4, pin 29 status = "okay"; }; panel { compatible = "panel-lvds"; width-mm = <224>; height-mm = <126>; backlight = <&backlight_lvds>; status = "okay"; port { panel_in: endpoint { remote-endpoint = <&lvds_ldb_out>; }; }; panel-timing { clock-frequency = <72400000>; hactive = <1280>; vactive = <800>; hfront-porch = <72>; hback-porch = <88>; hsync-len = <20>; vfront-porch = <15>; vback-porch = <23>; vsync-len = <10>; de-active = <1>; pixelclk-active = <1>; }; }; &ldb { status = "okay"; lvds-channel@0 { #address-cells = <1>; #size-cells = <0>; status = "okay"; port@1 { reg = <1>; lvds_ldb_out: endpoint { remote-endpoint = <&panel_in>; }; }; }; &ldb_phy { status = "okay"; }; display_power 在 exander 上占用大量 GPIO: display_power_12v: gpio_regulator { gpio-hog; gpios = <12 GPIO_ACTIVE_HIGH>; output-high; label = "DISPLAY12V"; }; 这主要取材于设备树中的一些示例。我搞不清楚哪里出了问题,也不知道为什么显示屏无法启动,甚至连背光都打不开。我知道我应该使用 TPM 而不是软件 GPIO,但这需要硬件修复,目前我只能暂时这样处理,但我认为这并不是问题的根源。 感谢您的支持! 此致, 朱利安 Re: imx93 lvds with kernel 6.12 对于感兴趣的人,我终于让它运行起来了,即使是使用软PWM也是如此。原因如下: * 内核编译中缺少模块(CONFIG_BACKLIGHT_CLASS_DEVICE=y,CONFIG_BACKLIGHT_PWM=y,CONFIG_DRM_PANEL_LVDS=y) 背光灯必须使用稳压器供电
View full article
Getting Started with UWB Using NXP Trimension® SR250 - Part 1: UWB Basics and an Overview of the SR250 (Japanese Blog) Introduction   "Doors open with your smartphone still in your pocket," "Lights turn on automatically when you enter a room," "The moment you sit down on the sofa, the soundbar automatically adjusts the sound field to your position"—the NXP Trimension ® SR250 is a device that can make these experiences a reality. The SR250 is the world's first IC for IoT applications to integrate ultra-high-precision wireless ranging technology " UWB (Ultra-Wideband) " and " UWB radar " that can detect people and objects without an external device, all on a single chip with on-chip processing. This SR250, which holds so much potential, was finally released to the mass market in March 2026! The evaluation board SR250UWBSHIELD is available for purchase from NXP's e-commerce site . If you've been thinking, "That sounds interesting, but it might be difficult," now's your chance to give it a try. In this first installment, we'll cover everything from the basics of what UWB is to the features of the SR250. Read this article to expand your imagination, and then get your hands on an evaluation board and experience UWB together! Have you heard of UWB somewhere before?   If you're thinking, "Isn't UWB an old high-speed data transfer technology?", you're very perceptive! In the early 2000s, UWB attracted considerable attention as a high-speed wireless data transfer technology . The WiMedia Alliance worked to standardize it, but it ultimately failed to gain widespread adoption due to the rapid evolution of Wi-Fi and Bluetooth. However, in the late 2010s, UWB made a comeback in a completely different form. It was redefined as a precision distance measurement and positioning technology and standardized as IEEE 802.15.4z. Its inclusion in the iPhone 11 in 2019 brought it a surge in popularity. The fundamental characteristic of UWB—its wide bandwidth—remains unchanged. However, by using this characteristic not as "communication speed" but as "temporal resolution," entirely new applications have emerged. What is UWB? — Into the world of centimeters   UWB (Ultra-Wideband), as its name suggests, is a wireless technology that uses extremely wide bandwidth in terms of frequency, and conversely, very short pulse signals in terms of time. It has been standardized as the IEEE 802.15.4z standard and is currently rapidly gaining popularity in the field of short-range high-precision positioning. While Wi-Fi and Bluetooth have a positioning accuracy of ±1-2m, UWB can achieve centimeter-level accuracy of ±5-10cm. This technology can detect "here" rather than "somewhere." This combination of centimeter-level accuracy and high security enables smart car access and precise indoor positioning. In addition to Android smartphones and AirTag, it has also been announced that it will be integrated into Google Pixel Tag, and further widespread adoption is expected in the future. *Google Pixel Tag is scheduled for release in November 2026. Why is UWB so robust against multipath interference and secure? — A comparison with other wireless technologies   What is multipathing?   Radio waves don't just travel in a straight line like light; they also propagate by reflecting off walls, ceilings, furniture, and other objects. The receiver receives a mixture of radio waves that traveled in a straight line and those that have reflected from various points. This is called multipath. Indoors, in particular, there are many reflections, creating a multipath environment. RSSI (Radio Speed Indicator) based ranging methods like BLE and Wi-Fi estimate distance using the "strength of mixed radio waves," making them highly susceptible to reflected waves. Because UWB uses very short pulse signals (a few nanoseconds wide), it can temporally separate and distinguish signals that arrive directly from signals that are reflected and arrive later.   Why is UWB ranging secure? UWB uses an encrypted signal sequence called STS (Scrambled Timestamp Sequence). The STS is generated each time by an AES-128-based random number generator, producing a different value each time . The receiver calculates the same STS using a pre-shared key and verifies the legitimacy of the sender by comparing it with the received value. Because a different STS value is generated each time, attacks that involve retransmitting intercepted signals (replay attacks) or relaying/spoofing signals to misinterpret distance are impossible. Furthermore, in secure ranging, the session key used to generate the STS is managed in a secure environment and recalculated periodically. Even if the key information at a specific point in time is leaked, the scope of damage can be limited. As a result, UWB achieves stronger security than BLE or Wi-Fi-based ranging.   Comparison of distance measurement technologies   technology accuracy Multipath resistance security Main uses UWB ±5~10 cm High ( separates waves directly with pulses) High (STS encryption) Precision positioning and smart access BLE Channel Sounding ±0.5 m Medium (improved by phase measurement) Medium (Protected by RTT+ phase) Smart Access IoT Wi-Fi RTT (FTM) ±1 to 2 m low to medium low Indoor navigation and floor detection BLE RSSI ±1 to 5 m Low (intensity-based) low Proximity detection and beacons Other technologies, such as BLE Channel Sounding, offer advantages in terms of cost and power consumption, leading to an increase in their use depending on the application, as well as hybrid configurations with UWB. UWB ranging principle: ToF and AoA   ToF (Time of Flight) In TWR (Two-Way Ranging), the Initiator sends a pulse to the Responder, which then returns it. The Initiator measures the round-trip time of the radio waves and calculates the distance. Because radio waves travel at the speed of light, even a small time error directly translates to a distance error. The wider the bandwidth, the higher the time resolution and the better the distance accuracy. Furthermore, it supports TDOA (Time Difference of Arrival) by combining multiple devices, enabling real-time positioning over a wide area. AoA (Angle of Arrival) The angle at which a device is located is calculated from the phase difference of arrival (PDOA) of signals received by multiple antennas. Because the SR250 has three receiving ports, it can perform 3-single-shot 3D AoA , simultaneously calculating horizontal and vertical angles.   What is UWB radar?   While ranging measures distance through communication between two UWB devices, radar takes a completely different approach. By analyzing the signals reflected from pulses that hit people or objects, it can detect distance, direction, and presence even if the other party does not have a UWB device . UWB radar can detect even the slightest movement of the human body, allowing you to sense whether there is a person present and whether they are moving, while protecting privacy. Leave radar processing to the SR250! On-chip radar processing   Radar algorithms are complex and not easy to develop from scratch. The SR250 is designed to handle the detection of a single target's presence, distance, and angle on-chip , allowing you to use radar functionality without developing your own algorithms. For more complex radar processing, reflections can be sent to a host, enabling AI/ML applications. Applications pioneered by the SR250   The SR250, which integrates ranging and radar into a single chip, is expected to be used in a wide range of fields, from consumer devices such as smart locks and smart speakers to industrial applications such as collision prevention between AGVs (automated guided vehicles) and forklifts and workers in factories and warehouses. "Knowing location," "Knowing presence," and "Knowing movement"—what kind of devices could be created if these three things were possible without a camera? Please read the series while imagining these possibilities. Scheduled serialization   This series is planned to consist of four parts. Part 1 (This article) Basics of UWB and an overview of the SR250 2nd time Setting up the SR250 evaluation board (SR250UWBSHIELD) 3rd Let's try UWB ranging. 4th Try out UWB radar. Next time, we'll explain how to obtain an evaluation board and how to set up the hardware and software environment. Let's get ready to run UWB together! Reference links Trimension SR250 Product Page (Japanese) SR250 Evaluation Board (TRIMENSION-SR250) UWB Radar Fundamentals (AN13989) UWB Convergence Radar White Paper Introducing the Trimension SR250 Training (English, 24 minutes) ========================= We are currently unable to respond to comments left in the "Comment" section of this post. We apologize for the inconvenience, but please refer to " Technical Questions to NXP - How to Contact Us( Japanese Blog) " when making an inquiry. (If you are already an NXP distributor or have a relationship with NXP, you may ask your representative directly.) The NXP Trimension® SR250, which integrates centimeter-precision ranging and a UWB radar that does not require a separate device onto a single chip, was released for the mass market in March 2026. This article explains the basic principles of UWB and the features of the SR250. (Reading time: 10 minutes) Security Japanese Blog
View full article
SSEGold:Animo发布日期、游戏玩法指南以及如何快速获得更多货币 Aniimo 的出现为生物收集角色扮演游戏类型带来了一位全新的竞争者。这是一款免费的开放世界冒险游戏,融合了怪物收集、探索、战斗和多人游戏功能。如果你喜欢在游戏中发现新生物、组建强大的队伍并探索广阔的奇幻世界,那么 Aniimo 绝对是一款值得一看的游戏。 由 Pawprint Studio 开发的 Aniimo 将玩家带入 Idyll 的世界,在那里,被称为 Aniimo 的神秘生物生活在不同的环境中。除了收集伙伴之外,玩家还可以通过独特的“Twine”系统与 Aniimo 建立联系,并从 Aniimo 的视角体验这个世界。 Aniimo何时发布? Aniimo 计划于 2026 年 9 月 16 日在全球范围内正式上线,支持 PC 和游戏主机平台,包括 PlayStation 5 和 Xbox 平台。移动版将于 2026 年 9 月 23 日紧随其后推出。 该游戏将采用免费游玩模式,玩家无需购买基础游戏即可下载并体验核心玩法。游戏内将提供可选的付费项目和特殊礼包。 Aniimo 是什么类型的游戏? Aniimo 是一款开放世界生物捕捉角色扮演游戏。玩家扮演探路者的角色,探索伊迪尔大陆,寻找独特的阿尼莫伙伴。 主要游戏循环包括: 探索不同区域,发现隐藏的生物 使用特殊工具捕捉 Aniimo 训练和进化收集到的伙伴 通过实时战斗与敌人作战 与其他玩家一起完成挑战 定制您的个人空间并与您的 Aniimo 互动 与传统的生物收集游戏不同,《Animimo》非常注重探索。根据环境、天气状况和时间的不同,可能会出现不同的生物,因此探索是游戏进程中重要的一部分。 Aniimo Twine系统详解 Aniimo 的最大特色之一就是 Twine 机制。 玩家不仅可以控制人类角色,还可以与他们的 Aniimo 建立联系,并通过 Aniimo 体验世界。这样你就可以利用不同的生物能力进行探索,例如: 飞越区域 潜水 挖掘地下通道 解谜 以全新的视角进行战斗 这个系统赋予了每个阿尼莫更大的价值,因为它们不仅是战斗伙伴,还能帮助你探索世界。 Aniimo中的战斗机制是怎样的? Aniimo 的战斗侧重于实时战斗,而不是传统的回合制系统。 玩家可以: 组建一支由不同 Aniimo 组成的团队 充分利用生物的能力 与PvE敌人和首领战斗 参与 PvP 挑战 加入多人游戏活动 游戏还包含竞技模式,玩家可以组队或与其他玩家对抗。例如,PvEVP 模式“蛋壳劫案”中,团队需要搜索、战斗并争夺奖励。 Aniimo货币以及玩家为何需要更多资源 与许多免费角色扮演游戏一样,货币和资源在 Aniimo 中将发挥重要作用。 玩家可能需要游戏内货币来购买: 升级 Aniimo 能力 解锁进化材料 改进设备 购买实用物品 为战斗打造更强大的队伍 游戏初期,通过任务和探索获取资源可能就足够了。然而,随着玩家进入更高难度的游戏内容,收集材料和货币可能会变得非常耗时。 拥有足够的货币可以帮助玩家将更多的时间用于探索和战斗,而不是重复相同的刷怪活动。 如何更快地获得Animo货币? 玩家可以通过多种方式积累资源: 1. 完成每日活动 每日任务和限时活动通常是获得奖励最可靠的途径之一。 2. 探索和收集资源 由于 Aniimo 采用开放世界设计,探索可能会让玩家获得宝贵的材料和物品。 3. 参与多人游戏内容 合作活动和竞争挑战可能会带来额外的奖励,同时也会让游戏进程更加有趣。 4. 从信誉良好的卖家处购买 Aniimo 货币 对于想要节省刷怪时间的玩家来说,从可靠的第三方市场购买游戏货币可能是一个方便的选择。 SSEGold提供 Aniimo 货币和游戏相关服务,帮助玩家更快地获得所需的资源,并花更多时间享受实际的游戏体验。无论你是准备组建更强大的 Aniimo 队伍、升级你的伙伴,还是追赶朋友的进度,拥有额外的货币都能让你的进度更加顺利。 Aniimo值得玩吗? Aniimo 拥有许多吸引生物收集游戏爱好者的功能。它的开放世界设计、独特的 Twine 系统、不断进化的伙伴以及多人游戏活动,使其比简单的怪物捕捉游戏更具深度。 对于喜欢探索、收集稀有生物和组建强大队伍的玩家来说,《Animimo》可能会成为 2026 年最有趣的 RPG 版本之一。 体验这款游戏的最佳方式是探索伊甸园,发现新的阿尼莫,并打造你自己的冒险之旅。如果游戏进度变得太慢,通过 SSEGold 等值得信赖的服务获得额外的货币可以帮助你专注于游戏中有趣的部分,而不是无休止地刷资源。
View full article
PCA2131 RTC:间歇性周期性中断(丢失或运行速度快4倍) 大家好, 我目前正在将PCA2131 汽车实时时钟集成到电池管理系统 (BMS) 中,但遇到了周期性中断生成不稳定的问题。 问题描述:我们尝试按规定的时间间隔(例如,每 X 分钟)生成中断。核心问题在于这种行为极不稳定: 有时,中断会按预期触发信号。 有时,计数器似乎运行速度比正常速度快大约 4 倍。 有时,中断会被完全忽略。 由于这个问题是随机发生的,我们很难找出根本原因。 测试与观察: 硬件:我们测试了 3-4 个不同的 RTC 样品,并在多个单元中观察到了这种异常行为。 时钟配置:我们评估了默认的 32.768 kHz 时钟,以及 16 kHz 和 8 kHz 配置。 中断间隔:分别以 1 分钟、2 分钟和 5 分钟的间隔进行测试。 结果:在这些变化中,时间不稳定性依然存在。 请求:我已附上原理图和捕获的波形图供您参考。 请您查看附件,并帮助我们了解可能是什么原因导致这种情况?我们非常希望了解具体的寄存器配置、已知的错误或可能导致这种间歇性时序不稳定的噪声/硬件条件。 感谢您的支持。 RTC Re: PCA2131 RTC: Intermittent periodic interrupts (Missed or running 4x faster) 您好! 请您核对以下几点? 每次中断后,必须显式清除 MSF 标志(Control_2 的第 7 位,地址 01h)。 在你的中断服务例程 (ISR) 中,始终向 MSF(Control_2 的第 7 位)写入 0。使用数据手册第 7.11.5 节中描述的 AND 写入方法(写入 0 清除,写入 1 保持不变)。 如果 Control_1 的 MI(位 1)和 SI(位 0)都设置了,则结果是每秒发生一次中断,而不是每分钟发生一次中断。 仅将 Control_1 中的 MI = 1、SI = 0 设置为周期性分钟中断。查阅登记簿以确认。 请告知结果。 Re: PCA2131 RTC: Intermittent periodic interrupts (Missed or running 4x faster) 你好, 通过设置 AEN_x = 1 来禁用警报比较器的写入操作已被注释掉,请取消注释所有五行。这些写入操作必须在重新启动下一个警报之前执行。 在报警触发截图中,原始寄存器值 ctrl2.w= 18(0x12 = 0001 0010 二进制)正确显示: 位 4 = 1 → AF(报警标志)被设置 位 1 = 1 → AIE(报警中断使能)已设置 但是,在调试器中,结构体字段 ctrl2.b.af 显示为 0。这意味着您为 Control_2 定义的 C 位域结构体没有正确地将 af 字段映射到第 4 位。如果固件的任何部分在 ctrl2.b.af 而不是硬件中断线或 RTC_ALarm_Flag 软件变量上进行分支,则它将无法检测到警报并完全丢失中断,从而解释了丢失中断的症状。 请检查并更正 Control_2 寄存器结构的位域定义。af 字段必须在第 4 位位置声明。 Re: PCA2131 RTC: Intermittent periodic interrupts (Missed or running 4x faster) 我按照你的建议检查过了。为此,我在报警触发时和报警清除后分别截取 CTRL_REG_1 和 CTRL_REG_2 的屏幕截图。 Re: PCA2131 RTC: Intermittent periodic interrupts (Missed or running 4x faster) 你好ErikaC , 感谢您的评价。 我已经按要求取消了 AEN_x 的五行代码的注释。 我已验证位域定义,它是正确的。在“报警触发”图像中,ctrl2.b.af 位成功设置为 1。在“警报清除”图像中,它重置为 0。位域的行为完全符合预期。 Re: PCA2131 RTC: Intermittent periodic interrupts (Missed or running 4x faster) 期待您的回复,或者我们能否通过邮件讨论? 我的邮箱地址:[email protected]
View full article
S32 Design Studio for ARM Version 2.2 许可证到期,麻烦帮忙延期,谢谢! S32 Design Studio for ARM Version 2.2 许可证到期,麻烦帮忙延期,谢谢! Re: S32 Design Studio for ARM Version 2.2 许可证到期,麻烦帮忙延期,谢谢! 你好, 您的S32DS许可证已延期。
View full article
S32K342、HSE、設置に関する問題 S32K342カスタムボード + PEmicro。S32K344_HSE_FW_INSTALL サンプルを S32K342 に移植しました。ビルドは正常に完了し、S32K342.mac のリセットも完了しますが、 main に到達する前にコードが Default_Handler (BusFault/HardFault) にトラップされ、起動時に失敗します。ピンクは0.13.0_2.40.0 FULL_MEMです。S32K342では、どのようなスタートアップ/リンカーの変更が必要ですか? Re: S32K342, HSE , installation issues 最近似たような問題に直面したので、使用済みのライブラリ(セミホスティングなど)が原因かもしれません。newlib_nano を選択してください(I/O なし) それ以外の場合、S32K344_HSE_FW_INSTALLを別の派生製品に移植するのは非常に簡単です。S32K342のスタートアップコードとレジスタ定義を使用する必要があります。
View full article
ssscli 对 SE051 默认支持哪些 AES 模式? 你好, 我目前正在使用 Plug & Trust 中间件中的 ssscli 工具评估 SE051。 我的目标是使用 密码块链接(CBC)、ECB 等模式执行 AES 加密和解密操作,理想情况下,还可以使用 GCM 或 CCM 等 AEAD 模式。 在查看提供的 ssscli Python 源代码时,我注意到以下几点: 在 const.py 中,CRYPT_ALGO 字典仅定义了 AES_CTR。 在 cli.py 中,加密和解密命令的帮助文本只提到了 --algo oaep 和 --algo rsaes。 由于我计划将其用于商业产品,因此我希望避免修改 NXP 提供的源代码(例如 const.py 或 cli.py)。 请您澄清以下几点? 开箱即用的支持: 在不修改任何源代码的情况下,当前版本(04.07.01)中的 ssscli 加密/解密命令有哪些 AES 模式可用? 是否仅限于 AES_CTR? 替代方案: 如果我需要在不修改 Python CLI 脚本的情况下使用 密码块链接(CBC) 或 GCM 等其他模式,推荐的方法是否是使用 C-API 开发自定义应用程序? 或者,NXP 是否有其他预构建的工具/二进制文件可用于评估这些特定的 AES 模式? 环境: 板: MCIMX8M-WEVK 和 OM-SE051ARD SoC: i.MX 8M Linux 版本: 6.1.151-cip46 Plug & Trust MW 版本: 2001年7月4日 任何指导都将不胜感激。 Re: What AES modes are supported out-of-the-box by ssscli for SE051? 嗨@Uc_S , 是的,ssscli 对 AES 的开箱即用支持仅限于 AES_CTR,如果您不想修改 Python 代码,则必须用 C 开发自定义应用程序,例如 MW 中提供的示例,例如 ex_sss_symmetric 演示。 祝你有美好的一天, 坎 ------------------------------------------------------------------------------- 笔记: - 如果此回复解答了您的问题,请点击“标记为正确答案”按钮。谢谢你! - 我们会持续关注帖子,从最后一条回复发出后持续7周,之后的回复将被忽略。 如果您之后有相关问题,请另开新帖并引用已关闭的帖子。 ------------------------------------------------------------------------------- Re: What AES modes are supported out-of-the-box by ssscli for SE051? 感谢您的清晰答复。 我完全理解。值得注意的是,AES_CTR 是 ssscli 唯一开箱即用的受支持模式。 根据您的建议,我们将考虑使用提供的示例开发一个自定义的 C 应用程序来实现其他 AES 模式。
View full article
S32 Design Studio 3.6.7 RFP 版 S32K3 开发包中缺少 NXP GCC 10.2 根据发行说明,S32K3xx 开发包 3.6.7 RFP 包含 GCC 版本 11.4,10.2.0 和 9.4.0。 然而,安装完成后(SW32_S32DS_3.6.7_RFP_D2604_win32.x86_64.exe),目前只有 GCC 11.4 版本,不包括 10.2.0 和 9.4.0。 在“S32DS 扩展和更新”中,我也只能看到 GCC 11.4。GCC 10.2.0 或 GCC 9.4 没有相关选项。 我的操作系统是 Windows 10 x64 22H2。 我正在使用一台离线电脑。我不确定那是不是原因。 编译器 | 汇编器 | 链接器 Re: Missing NXP GCC 10.2 in S32K3 Development Pack for S32 Design Studio 3.6.7 RFP HI 在 Windows 11 上安装 S32 Design Studio 3.6.7 RFP 后,我发现我还需要在 S32DS 扩展和更新中选择并安装 " NXP GCC for Arm 嵌入式处理器 v10.2 build 1728 " 。 给您带来的不便,我们深表歉意! 祝好, Robin ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"ACCEPT AS SOLUTION" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题并参考已关闭的主题。 -------------------------------------------------------------------------------
View full article
FAQs – NXP TJA1445, TJA1446, TJA1465 and TJA1466 CAN Transceivers with Partial Networking Introduction This document summarizes the most common customer questions regarding the NXP TJA1445, TJA1446, TJA1465 and TJA1466 CAN transceivers. It is intended as a practical guide covering basic product selection, partial networking, wake-up behavior, low-power operation, and key implementation considerations. 1) What are the TJA1445, TJA1446, TJA1465 and TJA1466 devices? They are high-speed CAN transceivers that provide the physical interface between a CAN/CAN FD controller and the two-wire CAN bus. All four devices support partial networking via selective wake-up, enabling low-power ECU operation while still allowing wake-up by a valid bus event or local wake input. 2) What is the main difference between the 1445/1446 and 1465/1466 families? The TJA1445/TJA1446 are high-speed CAN FD transceivers, while the TJA1465/TJA1466 are CAN SIC transceivers with Signal Improvement Capability, which reduces ringing and enables reliable communication in more complex topologies and at higher CAN FD speeds. The TJA1465/TJA1466 can support CAN FD up to 8 Mbit/s, whereas the TJA1445/TJA1446 target up to 5 Mbit/s CAN FD. 3) What is the difference between TJA1445 and TJA1446? Both support CAN FD and partial networking, but the TJA1446 adds advanced system monitoring features such as a Q&A watchdog, RST_N, LIMPFSO_N, and accurate VIO undervoltage/overvoltage monitoring. The TJA1445 does not include these monitoring and safety interface features. 4) What is the difference between TJA1465 and TJA1466? Both devices support CAN SIC, partial networking, and CAN FD/XL passive behavior, but the TJA1466 additionally integrates the watchdog, VIO monitoring, RST_N, and LIMPFSO_N fail-safe/limp-home support. The TJA1465 is the simpler CAN SIC partial networking transceiver without these advanced monitoring functions. 5) What is Partial Networking (PN), and why is it useful? Partial Networking allows ECUs that are not needed to remain in low-power mode while selected ECUs remain active on the bus. A sleeping node can be woken by a local wake event or by a remote selective wake-up frame containing the ECU-specific CAN identifier. This reduces vehicle power consumption and is especially useful for modern vehicles and EVs. 6) What is selective wake-up? Selective wake-up is the PN feature in which the transceiver does not wake up on arbitrary CAN traffic, but only on a valid wake-up frame matching the configured identifier, and optionally also matching DLC and data mask conditions. This helps keep undesired ECUs asleep even while other CAN messages are present on the bus. 7) What is the difference between CAN wake-up pattern (WUP) and wake-up frame (WUF)? A Wake-Up Pattern (WUP) is a low-level CAN bus pattern used to activate biasing and trigger wake-up when selective wake-up is not active. A Wake-Up Frame (WUF) is a valid CAN frame checked by the PN filter and used for selective wake-up when PN is configured and enabled. 😎 Which device should I choose for 8 Mbit/s CAN FD or more demanding network topologies? For higher CAN FD speeds and more challenging topologies, the TJA1465/TJA1466 are the preferred options because they include Signal Improvement Capability, which significantly reduces signal ringing and enables reliable operation up to 8 Mbit/s CAN FD. 9) Which VIO voltages are supported? The TJA1445/TJA1465 support interfacing with 1.8 V, 3.3 V, and 5 V MCUs. The TJA1446/TJA1466 are offered as dedicated variants: A = 1.8 V, B = 3.3 V, and C = 5 V-oriented / higher-voltage VIO variants. The 1446/1466 variant must be chosen to match the target MCU I/O level. 10) What supply pins do these transceivers use? They use three main supply pins: VBAT, VCC, and VIO. VBAT is the main supply and must be present in all operating modes, VCC supplies the CAN transmitter and biasing, and VIO supplies the digital interface level adaptation to the MCU. 11) What operating modes are available? The devices support Normal, ListenOnly, Standby, and Sleep modes. In Normal, the node can transmit and receive. In ListenOnly, the receiver is active but the transmitter is disabled. Standby is the first-level low-power mode with INH active, and Sleep is the deeper low-power mode with INH inactive. 12) What is the purpose of ListenOnly mode? ListenOnly mode is intended for node diagnosis, failure containment, and pretended networking use cases. In this mode the device can receive CAN traffic but does not actively transmit onto the bus. In low-power ListenOnly configurations, the receiver can remain active while minimizing current consumption. 13) How is local wake-up performed? Local wake-up is performed through the WAKE pin, which can be configured to detect rising and/or falling edges. A local wake-up request is registered when the new WAKE level remains stable for at least the configured wake filter time. 14) What are typical WAKE pin application examples? Typical examples include a switch to ground, connection to an ignition signal, or using the INH output of another transceiver as the wake source. We also provide design guidance for ESD protection and resistor/capacitor selection in these WAKE circuits. 15) What is the INH pin used for? The INH output is used to control external regulators or high-side enable logic so that the MCU and related circuitry can be automatically powered down in low-power modes and re-enabled on wake-up. In Sleep mode, it allows the transceiver to keep wake-up capability while the rest of the ECU is powered down. 16) How is selective wake-up configured? Selective wake-up is configured via SPI by programming the PN ID registers, ID mask, frame control, and data rate/filter registers. If data-field-based wake-up is needed, the DLC and data mask registers are also configured. The configuration becomes active after setting CPNC = 1 and PNCOK = 1. 17) What happens if I change a PN register after configuration? When the content of any PN-related register is changed, PNCOK is automatically cleared, and it must be set again to load and activate the updated PN configuration. 18) Can the device wake on identifier only, or also on data? Both are possible. The devices support identifier-only filtering when PNDM = 0, and identifier + DLC + data mask filtering when PNDM = 1. With data mask filtering, the wake-up decision also depends on the configured DLC and data mask bits. 19) Can Remote frames be used for selective wake-up? If PNDM = 1 and the selective wake-up checks the data field, Remote frames are not supported because they do not carry data. If Remote frames need to be able to trigger wake-up, identifier-only filtering should be used instead PNDM = 0. 20) How many MCU pins are needed to interface these devices? For the TJA1445/TJA1465, typically six MCU pins are needed: four SPI pins plus TXD and RXD. For the TJA1446/TJA1466, typically seven MCU pins are needed because the RST_N pin should also be connected to the MCU. 21) Are the SPI pins shareable with other peripherals? Yes. SCK, SDI, and SDO may be shared with other devices, but the transceiver requires its own dedicated SCSN chip-select. Daisy-chain SPI connections are not supported. 22) What are the GPIO pins used for? On the TJA1445B/TJA1465B, three GPIOs are available, and on the TJA1446/TJA1466, two GPIOs are available. They can be configured for general-purpose I/O and various special functions, including additional TXD/RXD, status signaling, wake-up input behavior, and other remote I/O style uses. 23) Can one transceiver be connected to two CAN controllers? Yes. GPIO1/2 can be configured as RXD2/TXD2, allowing a second CAN controller in the MCU to connect to the same transceiver. 24) What is TXEN_N and how does it behave? On the TJA1445B/TJA1465B, TXEN_N is the transmitter enable/disable control. A HIGH level on TXEN_N disables the CAN transmitter. In low-power modes, special care is needed so that the pin does not unnecessarily increase quiescent current if VIO remains present. 25) What extra features do TJA1446/TJA1466 provide for safety and system monitoring? The TJA1446/TJA1466 provide a Q&A watchdog, RST_N, LIMPFSO_N, and VIO undervoltage/overvoltage monitoring. They can supervise the MCU, detect fault conditions, trigger system reset, and support limp-home or fail-safe strategies in the ECU. 26) What is LIMPFSO_N used for? LIMPFSO_N can be configured either as a limp-home output or as a fail-safe output, depending on the system safety concept. In a limp-home application, it can activate backup hardware in case of failure. In a fail-safe application, it can keep safety-relevant hardware disabled until correct system operation is confirmed. 27) What is RST_N used for on TJA1446/TJA1466? RST_N is a bidirectional active-low reset pin used both to reset the MCU in response to transceiver-detected failures and to allow the transceiver to detect reset-related fault conditions from the system side. It should be connected to the MCU reset input. 28) What ESD robustness is specified on CANH and CANL? The quick reference data in the datasheets specifies ±8 kV IEC 61000-4-2 ESD handling capability on CANH and CANL. External protection components can still be considered if required by the application environment. 29) Is there any timing requirement for the first SPI access after power-up or wake-up? Yes. For the TJA1445/TJA1465 family, the first SPI interaction should occur within the MCU reaction timeout after power-up or wake-up from Sleep; otherwise the device may automatically enter Sleep mode with wake-up sources enabled. This mechanism helps limit battery drain if the MCU fails to initialize correctly. 30) Are there any common pitfalls when entering Sleep mode? Yes. Before entering Sleep, the required wake-up sources must be enabled and pending wake-up interrupts should be cleared. The transceiver will not enter Sleep unless at least one main wake-up source is enabled and all wake-up interrupts are cleared. 31) Can these devices support in-system MCU flashing through the CAN bus? Yes. The datasheets describe Start-to-Normal (SNM) behavior, which allows the device to enter Normal mode directly after boot if the CAN bus is held dominant before the internal check completes. This can support generic bootloader or end-of-line flashing use cases. 32) Are these devices safety-oriented parts? Yes. All four families were developed in compliance with ISO 26262 and achieve ASIL B. The TJA1446/TJA1466 go further with advanced monitoring and fail-safe-oriented interfacing. 33) Which packages are available? The TJA1445A/TJA1465A are available in SO14 and HVSON14, while the B variants are available in DHVQFN18. The TJA1446/TJA1466 are available in DHVQFN18. 34) Where can I find example initialization and SPI command guidance? For practical implementation guidance, we provide AN14388 for TJA1445/TJA1465 and AN14452 for TJA1446/TJA1466. These application notes include SPI usage guidance, initialization considerations, PN setup recommendations, WAKE pin examples, GPIO usage examples, and low-power mode handling. 35) In one sentence, when should I choose each family? Choose TJA1445 for CAN FD + PN, TJA1446 for CAN FD + PN + advanced system monitoring, TJA1465 for CAN SIC + PN + higher-speed or more demanding networks, and TJA1466 when you need CAN SIC plus advanced monitoring and safety-oriented system supervision. CAN PHY Transceiver
View full article