Multi Source Translation Content

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Multi Source Translation Content

ディスカッション

ソート順:
バンドギャップ電圧測定 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> これは、マイクロコントローラに搭載されているバンドギャップ電圧の測定を示すSWの例です。 バンドギャップ電圧は、内部ATDチャネルにルーティングされます。ATDコンバータは入力電圧を測定し、フラッシュメモリにある変数に格納します。 SWサンプルプロジェクトは、MC9S12XEP100デバイス用のCodeWarrior v5.1で作成されています。 全般
記事全体を表示
How to Enable PCIe WiFi into i.MX6 Android Release? Overview The purpose of this doument is to introduce how to enable PCIe WiFi into i.MX6 Android release. Environment Setup Hardware: i.MX6 SABRE-SD board Software: Android Jelly Bean 4.2 Software Configurations The source codes of Intel PCIe WiFi have been integrated for i.MX6 SABRE-SD board into i.MX6 Android release. However it's disabled by default. To enable it for i.MX6 SABRE-SD board, you can do the following: Change BOARD_WLAN_VENDOR to INTEL in device/fsl board configuration files. For example, diff --git a/sabresd_6dq/BoardConfig.mk b/sabresd_6dq/BoardConfig.mk index 9c8a32d..912e752 100755 --- a/sabresd_6dq/BoardConfig.mk +++ b/sabresd_6dq/BoardConfig.mk @@ -11,7 +11,7 @@ TARGET_BOOTLOADER_BOARD_NAME := SABRESD PRODUCT_MODEL := SABRESD-MX6DQ # Wifi -BOARD_WLAN_VENDOR                       := ATHEROS +BOARD_WLAN_VENDOR                       := INTEL # for atheros vendor ifeq ($(BOARD_WLAN_VENDOR),ATHEROS) BOARD_WLAN_DEVICE                       := ar6003 @@ -30,6 +30,7 @@ WIFI_COMPAT_MODULE_ARG                         := "" endif #for intel vendor ifeq ($(BOARD_WLAN_VENDOR),INTEL) +BOARD_WLAN_DEVICE                       := INTEL BOARD_HOSTAPD_PRIVATE_LIB               ?= private_lib_driver_cmd BOARD_WPA_SUPPLICANT_PRIVATE_LIB        ?= private_lib_driver_cmd WPA_SUPPLICANT_VERSION                  := VER_0_8_X After changing BOARD_WLAN_VENDOR as "INTEL", the following files will be compiled for intel WiFi: device/fsl-proprietary/pcie-wifi/ external/wpa_supplicant_8 hardware/imx/wlan/intel/ hardware/libhardware_legacy/wifi/wifi_intel.c Enable PCIe WiFi driver in kernel_imx by running "make menuconfig" command: Select "System Type -> Freescale MXC Implementations -> PCI Express support" as "*" Select "Networking support -> Wireless ->  cfg80211 - wireless configuration API" as "*". Then select "Networking support -> Wireless -> Generic IEEE 802.11 Networking Stack (mac80211)" as "*" Select "Device Drivers ->  Network device support -> Wireless LAN -> Intel Wireless WiFi 4965AGN (iwl4965)" as "*" Then run "make" command to build kernel. The followings are the dependencies files to enable above configuration: Kernel configuration: * -> System Type -> Freescale MXC Implementations Select the PCI Express support. Then config intel WIFI driver: Generic IEEE 802.11 Networking Stack (mac80211) used by WIFI devices Symbol: MAC80211 [=y] Type : tristate Prompt: Generic IEEE 802.11 Networking Stack (mac80211) Defined at net/mac80211/Kconfig:1 Depends on: NET [=y] && WIRELESS [=y] && CFG80211 [=y] Location: -> Networking support (NET [=y]) -> Wireless (WIRELESS [=y]) Intel iwl4965 or iwl6300 card driver Symbol: IWL4965 [=y] Type : tristate Prompt: Intel Wireless WiFi 4965AGN (iwl4965) Defined at drivers/net/wireless/iwlegacy/Kconfig:65 Depends on: NETDEVICES [=y] && WLAN [=y] && PCI [=y] && MAC80211 [=y] Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) Then you can follow up the instructions into Android User guide to build Android image. Known Limitation PCIe low power mode is not supported according to BSP release note. So when building in PCIe, the system suspend/resume should be disabled now. Android i.MX6DL i.MX6Dual i.MX6Quad Re: How to Enable PCIe WiFi into i.MX6 Android Release? Hi Sandesh      can you tell me the changes?thank Re: How to Enable PCIe WiFi into i.MX6 Android Release? HI Ross      can you upload the doc? thanks~ Re: How to Enable PCIe WiFi into i.MX6 Android Release? Dear Sir, I tried to load iwlagn.ko, and i got those log when WIFI ON: D/WifiService( 2578): setWifiEnabled: true pid=2831, uid=1000 W/WifiHW  ( 2578): is_wifi_driver_loaded W/WifiHW  ( 2578): got module patch /system/lib/modules/iwlagn.ko E/WifiStateMachine( 2578): Failed to reload STA firmware java.lang.IllegalArgumentException: command '12 softap fwreload wlan0 STA' failed with '501 12 SoftAP command has failed' W/CommandListener( 2209): Failed to retrieve HW addr for wlan0 (No such device) D/CommandListener( 2209): Setting iface cfg E/WifiStateMachine( 2578): Unable to change interface settings: java.lang.IllegalStateException: command '14 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 14 Failed to set address (No such device)' D/WifiMonitor( 2578): startMonitoring(wlan0) with mConnected = false E/WifiHW  ( 2578): Unable to open connection to supplicant on "/data/misc/wifi/sockets/wlan0": No such file or directory D/BluetoothAdapter( 2831): 1102399976: getState() :  mService = null. Returning STATE_OFF D/Tethering( 2578): sendTetherStateChangedBroadcast 1, 0, 0 I/wpa_supplicant( 3398): Successfully initialized wpa_supplicant D/Tethering( 2578): InitialState.processMessage what=4 D/Tethering( 2578): sendTetherStateChangedBroadcast 0, 0, 0 E/WifiHW  ( 2578): Supplicant not running, cannot connect E/WifiHW  ( 2578): Supplicant not running, cannot connect E/WifiHW  ( 2578): Supplicant not running, cannot connect E/WifiHW  ( 2578): Supplicant not running, cannot connect E/WifiHW  ( 2578): Supplicant not running, cannot connect E/WifiMonitor( 2578): startMonitoring(wlan0) failed! E/WifiStateMachine( 2578): Failed to setup control channel, restart supplicant W/WifiHW  ( 2578): is_wifi_driver_loaded W/WifiHW  ( 2578): is_wifi_driver_loaded return 0 E/WifiStateMachine( 2578): Failed to reload STA firmware java.lang.IllegalArgumentException: command '17 softap fwreload wlan0 STA' failed with '501 17 SoftAP command has failed' D/CommandListener( 2209): Setting iface cfg D/CommandListener( 2209): Trying to bring down wlan0 E/WifiMonitor( 2578): startMonitor called with unknown iface=wlan0 D/BluetoothAdapter( 2831): 1102399976: getState() :  mService = null. Returning STATE_OFF I/wpa_supplicant( 3416): Successfully initialized wpa_supplicant But wifi still not work. Any suggestions for it ? Re: How to Enable PCIe WiFi into i.MX6 Android Release? Dear Sir, We are using i.MX6DL with Android 4.4.2 kitkat. WiFi module: Intel Wifi Link 5100  Model:512AN_HMW  When trying to turn on wifi , it shows: D/WifiService( 2625): setWifiEnabled: true pid=2943, uid=1000 W/WifiHW  ( 2625): got module patch /system/lib/modules/iwlagn.ko E/WifiStateMachine( 2625): Failed to load driver Any suggestions for it ? Re: How to Enable PCIe WiFi into i.MX6 Android Release? Dear Sir, Our customer would like to use WiFi module: Intel Wifi Link 5100  Model:512AN_HMW  on Android 4.4 system. Could you any suggestion for it? Re: How to Enable PCIe WiFi into i.MX6 Android Release? Everyone, It should be noted that this process will not work with the Intel 3160 due to its support of P2P (I have never tried using the Intel 4965, don't have that part on hand in any case). We also have had trouble with P2P with the Atheros 9k (AR9462 part), but finally got basic Wifi functionality working. In general, I have been very disappointed with Wifi support in the JellyBean 4.3 BSP. What would be nice to see is a patch released to upgrade  the wpa_supplicant to 2.1 stable (February 2014 release I think). Michael Robbeloth Re: How to Enable PCIe WiFi into i.MX6 Android Release? Sandesh, Thank you, yes I did. One of our engineers got our SX-PCEAN+ card (9280 based) working with the v3.0.35 Ubuntu BSP. Re: How to Enable PCIe WiFi into i.MX6 Android Release? Ross, Did you find solution to bringup wifi on Ath9K PCIe card? we modified the changes in hardware/imx/wlan/atheros/compat-wireless/Android.mk to bringup WiFi feature. Re: How to Enable PCIe WiFi into i.MX6 Android Release? Hi Xiaoli, Is there support for the Atheros AR9K family and what would the differences be in the above instructions to build JB for a AR9K PCIe card? I have two i.MX6 customers asking how to do this (one is Android JB and one is Linux). I plan on sharing your excellent document but wondered if you could share anything specific to the Atheros 9K family. Thanks..>Andy Re: How to Enable PCIe WiFi into i.MX6 Android Release? The attachment is some patches  to enable intel 4965 wifi card with android 4.2.2 on sabresd 6q.You can take it as a reference. Re: How to Enable PCIe WiFi into i.MX6 Android Release? Hi Xiaoli, I followed your instruction to build JB 4.2.2 with Intel mini-PCIe wifi support but got the error messages below. I was able to build ICS with the same configuration, strange. make: *** No rule to make target `out/target/product/sabresd_6dq/obj/STATIC_LIBRARIES/private_lib_driver_cmd_intermediates/export_includes', needed by `out/target/product/sabresd_6dq/obj/EXECUTABLES/hostapd_intermediates/import_includes'.  Stop.
記事全体を表示
Tricked out tech at MakerFaire Maker Faires, here we come! This weekend we'll be sharing some super cool projects in San Mateo, and in September we'll be in New York. After much work, our team has pulled together some super cool projects built around Kinetis mcus, i.MX 6 processors, Freedom development platforms, as well as popular community projects featuring the UDOO, Riotboard.org, Novena, CuBox-i, Wandboard.org, Wunderbar, ZumoBots and more. Here are a few things that we have planned. Who doesn't love blinking, flashy lights? The crew over at PJRC has created a LED display (4320 to be exact) all being controlled by ONE Teensy3.1 board, which is about the size of a stick of gum. Paul has cooked up some special Teensyduino sketch library's that take advantage of the Kinetis K20 MCU's direct memory access engine (DMA) features to pull off the video and audio shown in this demo. Not only did Paul manage the difficult LED timing, but it also serves all the video from the SDCard interface. Did we mention it plays audio as well?! https://community.nxp.com/docs/DOC-100844 Once you're done getting your fill of light from the sign, you can test your skills with our hacked Wii-Fi (yes it's WII + WiFi) Nerf Swarmfire.  Add a few servos, a little re-wiring and a custom built WiFi remote and viola ... instant fun!  To pull this off we use two FRDM-KL64Fs on the Nerf itself (base) and one acting as a wireless remote.  The base board processes data from the remote and corresponding controls the servos. This video has been deleted (view in My Videos) The remote board behaves somewhat like a Wii in that the user has to move the remote around and onboard accelerometers turn that into motion movements which it then passes via WiFi to the base controller. And to top it all off, we just had to 3D print a plastic controller to put it all in. https://community.nxp.com/docs/DOC-100845 Those are are my kickin' Kinetis MCUs based demos. Now let's talk multimedia and that means i.MX apps processors. While your in the area be sure to say hello to Mario. Mario is a DIY Android powered robot with voice recognition and Twitter connection. Mario’s heart is a UDOO Quad running Android 4.3 plus an Arduino Motor Shield which controls 2 servos (Mario’s arms) and 4 Motors that turn 4 wheels (Mario’s legs). To show his cute face Mario has a 7-inch LVDS display while his mouth is a little speaker. To make him talk we used the Google APIs voice recognition and text to speech in order to give him a life. We also used Twitter APIs to control Mario via Twitter, he can read tweets and it’s also possible to send commands to Mario with a simple chirp. Re: Tricked out tech at MakerFaire Technical links: Wandboard: At Maker Faire San Mateo, we're showing a Wandboard Quad running XBMC (Xbox Media Center) (I might change this to Ubuntu or yocto) Main www.wandboard.org Technical http://www.wandboard.org/index.php/details Supplied software images http://www.wandboard.org/index.php/downloads Forums (there is both a Google group and a forum) http://www.wandboard.org/index.php/forums Where to Buy http://www.wandboard.org/index.php/buy Solidrun/Cubox: They are providing a unti with XBMC (Xbox Media Center) Main http://www.solid-run.com/ Technical and Pricing http://cubox-i.com/table/ Teensy Small Kinetis K20 that is Ardunio sketch compatible. Works with the Ardunino IDE. Main http://www.pjrc.com UDOO i.MX6 with Arduino also. Main http://www.udoo.org/ Technical and Pricing http://shop.udoo.org/usa/?___from_store=usa&popup=no
記事全体を表示
The new TPPSDK (GD3000 driver) based on RTD for S32K3 Question As we know, the TPPSDK supports S32K144 MCU and various Kinetis MCUs to initialize GD3000 in NXP MC solutions. Because of the release of S32K3 and related SW RTD, it’s necessary to expand the capability of TPPSDK to support S32K3 MC based RTD LLD driver or MCAL driver. Unfortunately, the AA team will not maintain the TPPSDK anymore.  How could we configure the GD3000 chip for S32K3 platform? Answer I took some time to finish this work. Here I'd like to share you the The Expanded TPPSDK Based on S32K3 RTD that is suitable for S32K3 MC application. You can find the Application Note, the source code of new TPPSDK (GD3000 driver), two examples in the attachment. I hope these materials can help you get start with the expanded TPPSDK on S32K3.
記事全体を表示
RT1020 BSP for RT-Thread RTOS        该软件包为RT-Thread RTOS配套的BSP板级支持包,默认支持官方开发板MIMXRT1020-EVK,用户可以针对该BSP移植到自己的prototype上面,当前RT1020_EVK板级包在RT-Thread v3.1.3版本编译通过并运行测试成功。使用时,需要将附件源码解压后拷贝到\rt-thread\bsp\imxrt路径下。 Products Product Category NXP Part Number URL MCU MIMXRT1021 i.MX RT1020 Crossover MCU with Arm® Cortex®-M7 core    Tools NXP Development Board URL i.MX RT1020 Evaluation Kit MIMXRT1020-EVK: i.MX RT1020 Evaluation Kit  SDK SDK Version URL RT-Thread_v3.1.3 https://github.com/RT-Thread/rt-thread/tree/v3.1.3  SDK_v2.6.1 mcuxpresso.nxp.com Industrial
記事全体を表示
实践研讨会:利用恩智浦最新多媒体应用处理器 i.MX 8M Mini 快速推进您的产品开发 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 从 i.MX 8M Mini EVK 开始实践,我们将介绍开箱即用的支持,包括软件、工具、硬件设计指南和演示软件。参加者在完成本课程后应该能够自信地使用 i.MX 8M Mini 开始自己的设计。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 从 i.MX 8M Mini EVK 开始实践,我们将介绍开箱即用的支持,包括软件、工具、硬件设计指南和演示软件。参加者在完成本课程后应该能够自信地使用 i.MX 8M Mini 开始自己的设计。 i.MX 应用处理器
記事全体を表示
MCU 技術トピック: ハンズオン・ワークショップ: S32K MCU での CSEc セキュリティ・ソフトウェアの作成 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> CSEcセキュリティ運用のためのデバイスの準備とプログラミングの方法を示すハンズオンセッションです。このセッションでは、CSEcモジュールをプログラムするためのベアメタルとSDKの両方のアプローチについても説明します。NVMの部分では、NXPが耐久性を計算するために提供するさまざまなタイプのメモリとツールの有効化/構成について説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> CSEcセキュリティ運用のためのデバイスの準備とプログラミングの方法を示すハンズオンセッションです。このセッションでは、CSEcモジュールをプログラムするためのベアメタルとSDKの両方のアプローチについても説明します。NVMの部分では、NXPが耐久性を計算するために提供するさまざまなタイプのメモリとツールの有効化/構成について説明します。
記事全体を表示
基于模型的设计工具箱电机控制示例 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该视频显示: - 采用 S32K144 rev2.0 的电机控制典型设置评估板; - 用于 BLDC 电机控制的 Simulink 模型; - 如何设置 Simulink 为 S32K144 rev2.0 生成 ANSI C 代码单片机; - 快速浏览基于模型的设计工具箱; - 快速浏览 FreeMASTER 数据可视化工具; - 使用 DevKit S32K144EVB 和 MotorGD 屏蔽运行的电机控制示例; (在 “我的视频” 中查看) 视频库 回复:基于模型的设计工具箱电机控制示例 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 非常感谢! 回复:基于模型的设计工具箱电机控制示例 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢分享,但是 C 代码在哪里?
記事全体を表示
HMB-N1937 推出基于 Android 的互联设备 Brillio 操作系统 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Brillo 是基于Android的轻量级操作系统, 适用于小型联网设备,开放、可扩展且安全。 Brillo将Android平台扩展至您所有的联网设备, 使这些设备可以轻松安装并与其他设备和您的智能手机无缝协作。 它与谷歌'Weave'通信API配套提供,可以在Brillo设备之间轻松实现通信和交换,并在云中存储数据。 在本次课程中,我们将向您介绍Brillo以及恩智浦如何与谷歌合作,将Brillo扩展至i.MX 6UltraLite处理器和其他平台。 观看视频演示 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Brillo 是基于Android的轻量级操作系统, 适用于小型联网设备,开放、可扩展且安全。 Brillo将Android平台扩展至您所有的联网设备, 使这些设备可以轻松安装并与其他设备和您的智能手机无缝协作。 它与谷歌'Weave'通信API配套提供,可以在Brillo设备之间轻松实现通信和交换,并在云中存储数据。 在本次课程中,我们将向您介绍Brillo以及恩智浦如何与谷歌合作,将Brillo扩展至i.MX 6UltraLite处理器和其他平台。 观看视频演示 智能家居和智能建筑
記事全体を表示
TN013_LPCOpen UART RB示例Tx问题 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> lpcopen。uart #ring_buffer
記事全体を表示
HMB-N1984 开发 HomeKit 和 iPod -MFi- 配件,采用 NXP 处理器和软件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍如何开发 Made For iPod (MFi) 配件,包括基于 NXP 微控制器 (MCU)、微处理器 (MPU)、HomeKit 软件开发套件 (SDK)、MFi SDK 和 NXP 专业服务软件的音频、非音频、CarPlay、AirPlay 和 HomeKit 应用程序。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍如何开发 Made For iPod (MFi) 配件,包括基于 NXP 微控制器 (MCU)、微处理器 (MPU)、HomeKit 软件开发套件 (SDK)、MFi SDK 和 NXP 专业服务软件的音频、非音频、CarPlay、AirPlay 和 HomeKit 应用程序。 智能家居和智能建筑
記事全体を表示
KDS での KSDK と Processor Expert のサポートを使用した新しい USB プロジェクトの作成 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KSDKファンの皆さん、こんにちは。   ご存知かもしれませんが、KSDKはKinetisマイクロコントローラの包括的なソフトウェアサポートを提供し、アプリケーション開発を加速します。ハードウェアabstraccionレイヤーとペリフェラルドライバーを提供するだけでなく、Processor Expertにも対応できます。   以下は、KSDK と Processor Expert のサポートを使用して新しいプロジェクトを作成する方法の例です。   これは、KSDK ドライバーまたはプロセッサ エキスパート サポートを使用してアプリケーション コードを追加する準備ができている簡単な USB HID の例を示しています。   これがお役に立てば幸いです。   よろしくお願いします。   アイザック・アビラ 全般 Re:KDSでKSDKとProcessor Expertのサポートを使用して新しいUSBプロジェクトを作成する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この関数「USB_Class_HID_Send_Data()」はどのように機能しますか? この関数を使用したときに、Aなどの単語を送信し続けます。 AではなくAだけを送信する方法。 Re:KDSでKSDKとProcessor Expertのサポートを使用して新しいUSBプロジェクトを作成する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 私はこのガイドが示しているものと似たようなことを達成しようとしていますが、あまり役に立たないほど十分に異なります。TWR-K21F120M を使用しており、OS なしで Processor Expert コンポーネントを使用して USB MSD を実装する必要があります。これを達成するために私に示せるリソースはありますか?
記事全体を表示
APF-ACC-T0983 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、KEAシリーズとKFAシリーズを含む、新しいKinetisマイクロコントローラの自動車製品ファミリの概要を説明します。Kinetisマイクロコントローラの自動車ファミリは、車載市場向けの32ビットARM® Cortex-M0®+/M4ベースのAEC Q100認定マイクロコントローラの、拡張性に優れたポートフォリオです。このファミリは、コスト重視のアプリケーション向けに最適化されており、非常に低い消費電力でピン数の少ないオプションを提供します。2.7-5.5V電源を備え、優れたEMC/ESD堅牢性に重点を置いたKinetisマイクロコントローラ・オート・シリーズ・デバイスは、ボディ・アプリケーション、インフォテインメント接続モジュール、パーキング・アシスタンス、セーフティ・コンパニオン・チップ、汎用センサ・ノードなど、幅広いアプリケーションに適しています。Kinetisマイクロコントローラのオート・ファミリのすべての製品は、同様のペリフェラルを共有しており、さまざまなサードパーティ製およびフリースケールのHW/SW開発ツールによってサポートされています。開発者は、Kinetisマイクロコントローラのオート・ファミリを使用して、設計を迅速に開始できます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、KEAシリーズとKFAシリーズを含む、新しいKinetisマイクロコントローラの自動車製品ファミリの概要を説明します。Kinetisマイクロコントローラの自動車ファミリは、車載市場向けの32ビットARM® Cortex-M0®+/M4ベースのAEC Q100認定マイクロコントローラの、拡張性に優れたポートフォリオです。このファミリは、コスト重視のアプリケーション向けに最適化されており、非常に低い消費電力でピン数の少ないオプションを提供します。2.7-5.5V電源を備え、優れたEMC/ESD堅牢性に重点を置いたKinetisマイクロコントローラ・オート・シリーズ・デバイスは、ボディ・アプリケーション、インフォテインメント接続モジュール、パーキング・アシスタンス、セーフティ・コンパニオン・チップ、汎用センサ・ノードなど、幅広いアプリケーションに適しています。Kinetisマイクロコントローラのオート・ファミリのすべての製品は、同様のペリフェラルを共有しており、さまざまなサードパーティ製およびフリースケールのHW/SW開発ツールによってサポートされています。開発者は、Kinetisマイクロコントローラのオート・ファミリを使用して、設計を迅速に開始できます。
記事全体を表示
Technical Report Valasi.pdf The Freescale Cup High School Challenge technical report from team Valasi from Stredni Skola informatiky, Elektrotechniky a Remesel Roznov (Czech Republic) The Freescale Cup High School Challenge technical report from team Valasi from Stredni Skola informatiky, Elektrotechniky a Remesel Roznov (Czech Republic)
記事全体を表示
Example MPC5566EVB PinToggleStationery CW210 ******************************************************************************** * Detailed Description: * Application performs basic initialization, setup PLL to maximum allowed freq., * initializes interrupts, blinking one LED by interrupt, second LED by software * loop, initializes and display notice via UART terminal and then terminal ECHO. * The example configures the device for maximum performance (OPTIMIZATIONS_ON). * Its intention is to offer advanced startup code additional to CW stationery. * ------------------------------------------------------------------------------ * Test HW:        MPC5566EVB * MCU:            PPC5566MVR132 * Fsys:           144/132/112/80/12 MHz * Debugger:       Lauterbach Trace32 *                 PeMicro USB-ML-PPCNEXUS * Target:         RAM, internal_FLASH * Terminal:       19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection: TPU_PORT_37 -> USER_LED_8 *                 TPU_PORT_38 -> USER_LED_7 (to see blinking LEDs)    * ******************************************************************************** ******************************************************************************** * Detailed Description: * Application performs basic initialization, setup PLL to maximum allowed freq., * initializes interrupts, blinking one LED by interrupt, second LED by software * loop, initializes and display notice via UART terminal and then terminal ECHO. * The example configures the device for maximum performance (OPTIMIZATIONS_ON). * Its intention is to offer advanced startup code additional to CW stationery. * ------------------------------------------------------------------------------ * Test HW:        MPC5566EVB * MCU:            PPC5566MVR132 * Fsys:           144/132/112/80/12 MHz * Debugger:       Lauterbach Trace32 *                 PeMicro USB-ML-PPCNEXUS * Target:         RAM, internal_FLASH * Terminal:       19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection: TPU_PORT_37 -> USER_LED_8 *                 TPU_PORT_38 -> USER_LED_7 (to see blinking LEDs)    * ******************************************************************************** General
記事全体を表示
Porting Micro-ROS on Frdm-MCXN947 1. Overview The MCXN947 chip is a highly integrated microcontroller featuring robust processing capabilities, extensive peripheral support, and advanced security features. It is suitable for a wide range of complex applications. The NXP FRDM-MCXN947 board is a low-cost design and evaluation board based on the MCXN947 device. NXP provides a comprehensive set of tools and software support for the MCXN947, including hardware evaluation boards, an integrated development environment (IDE), example applications, and drivers. Micro-ROS is an embedded version of ROS 2 specifically designed to operate on embedded systems, enabling real-time control and communication for robotics and embedded devices. It extends the powerful features of ROS 2 to resource-constrained embedded platforms like microcontrollers and embedded systems. The introduction of Micro-ROS facilitates tighter integration between embedded systems and the ROS 2 ecosystem, enabling advanced robotic automation and control. This document explores the process of porting Micro-ROS to the MCXN947 board.‌ This document explores the process of porting Micro-ROS to the MCXN947 board. Hardware Environment:     FRDM-MCXN947 Software Environment:     Ubuntu 22.04     IDE:MCUXpresso IDE v11.9.0     SDK:SDK Builder | MCUXpresso SDK Builder (nxp.com) 2. ROS 2 Architecture Before delving into the Micro-ROS porting process, let us briefly introduce the new ROS 2 architecture. This is necessary because Micro-ROS heavily leverages ROS 2's abstraction layer source code in its design and implementation. Compared to its predecessor ROS 1, ROS 2 employs a distinct communication mechanism, most notably adopting the DDS (Data Distribution Service) protocol for communication and node discovery. ROS 1, by contrast, relies on the XML-RPC protocol and requires the master node to launch before other nodes can join. ROS 1's limited support for embedded devices stems from the XML-RPC mechanism, which introduces significant software dependencies in these environments. To address this issue, projects like rosserial developed lightweight communication protocols tailored for MCU-to-PC master node communication. ROS 2, on the other hand, integrates the industry-proven DDS protocol, which has demonstrated its stability in domains like military, aerospace, and financial systems. It is important to note that DDS is a standard protocol with various implementations, such as Cyclone DDS (Eclipse), Fast DDS, and Micro XRCE-DDS (eProsima). To ensure that upper-layer ROS 2 code remains unaffected by different DDS implementations, ROS 2 defines a series of abstract layer interfaces, such as RCL (ROS Client Library) and RMW (ROS Middleware). These DDS implementations provide a uniform RMW interface. On top of RMW is the RCL, implemented in C, which supports various programming languages, including C++, Python, and Java. Thus, successfully porting ROS 2 to a real-time operating system (RTOS) hinges on the RTOS supporting a specific DDS implementation and its corresponding RMW interface. Only then can upper-layer RCL and ROS application code run without modification. ROS 2 comprises RCL (ROS Client Library), RMW (ROS Middleware Interface), and DDS (Data Distribution Service). Porting ROS 2 to a new platform essentially involves creating a compatible RMW-DDS combination, leaving the RCL layer unaltered. Micro-ROS provides such an RMW-DDS combination. Specifically, Micro-ROS employs Micro XRCE-DDS (a DDS standard designed for extremely resource-constrained environments) with a corresponding RMW implementation. This enables Micro-ROS to be compatible with ROS 2's architecture while efficiently running on resource-limited embedded devices. Thus, porting Micro-ROS to different hardware platforms fundamentally involves interfacing communication protocols like UART (Universal Asynchronous Receiver-Transmitter) and UDP (User Datagram Protocol) with the Micro-ROS RMW-DDS combination. This process ensures effective communication between Micro-ROS and other nodes or external systems while maintaining the lightweight and efficient characteristics suitable for embedded devices. From the above introduction, we can see that MicroROS transplantation mainly has two parts: Connect UART/UDP communication and clock to implement the 5 functions in default_transport.cpp. Folder DDS+RMW+RCL generates libmicroros.a static library. 3. Micro-ROS Static Library Toolchain and Environment Configuration 3.1 Micro-ROS Static Library Toolchain and Environment Configuration First, install ROS 2 on Ubuntu 22.04 LTS and run the following commands: sudo apt update&&sudo apt install locales sudo locale-gen en_US en_US.UTF-8 sudo update-locale LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8 export LANG=en_US.UTF-8 sudo apt update && sudo apt install curl gnupg lsb-release sudo curl -sSL https://raw.githubusercontent.com/ros/rosdistro/master/ros.key -o /usr/share/keyrings/ros-archive-keyring.gpg (1) sudo apt update: Updates the system’s package list to fetch the latest package information. (2) sudo apt install locales: Installs the locales package, which provides tools for managing and configuring localization. (3) sudo locale-gen en_US en_US.UTF-8: Generates the localization settings for US English, including UTF-8 encoding. (4) sudo update-locale LC_ALL=en_US.UTF-8 LANG=en_US.UTF-8: Updates the system’s localization settings to use UTF-8 encoding for US English. (5) export LANG=en_US.UTF-8: Sets the current terminal’s language encoding to US English UTF-8. (6) sudo apt install curl gnupg lsb-release: Installs additional tools (curl for network requests, gnupg for encryption, lsb-release for distribution information). (7) sudo curl: Downloads the ROS public key for verifying package integrity. 3.2 Installing ROS on Ubuntu Set up and build the Micro-ROS development environment with the following commands: sudo apt update && sudo apt upgrade && sudo apt install ros-humble-desktop source /opt/ros/humble/setup.bash && echo “source /opt/ros/humble/setup.bash” >>~/.bashrc source /opt/ros/$ROS_DISTRO/setup.bash mkdir uros_ws && cd uros_ws git clone -b iron https://github.com/micro-ROS/micro_ros_setup.git src/micro_ros_setup rosdep update && rosdep install --from-paths src --ignore-src -y colcon build source install/local_setup.bash ros2 run micro_ros_setup create_firmware_ws.sh generate_lib (1) Update the software and install ROS (Robot Operating System) (2) Set and save the configuration of the ROS environment. (3) These two commands create a new directory uros_ws (workspace), and then switch to this directory. (4) Clone the project named micro_ros_setup from the GitHub repository and place it in the src directory of the workspace. (5) These two commands are used to install the dependencies required by the project. (6) This command uses the colcon build system to compile and install the project. Colcon is a general-purpose build tool suitable for multiple programming languages and platforms. (7) create_firmware_ws.sh: This is the name of the executable file to be run. It might be a script that creates a firmware workspace. The purpose of this command is to run the create_firmware_ws.sh script in the micro_ros_setup package and pass the parameter generate_lib to generate a firmware workspace containing the Micro-ROS library. This step requires downloading a large amount of source code from github. After failure, the next generation will prompt that the firmware already exists and you need to rm this folder. If the following picture appears, it proves that the code download is successful. 4. Generating the Micro-ROS Static Library If the toolchain and environment setup are successful, you should have five folders in your workspace: build, firmware, install, log, and src. The firmware folder contains the Micro-ROS workspace. 4.1 Configure the toolchain.cmake file according to the target processor Enter the fireware directory. The colcon.meta and toolchain.cmake inside are the configuration files we need to specify to generate the static library. Colcon.meta describes the configuration of our micro-ros, and toolchain.cmake describes the microcontroller platform. We can open MCUXpresso to find MCXN947 related configuration. and create toolchain.cmake. set(CMAKE_SYSTEM_NAME Generic) set(CMAKE_CROSSCOMPILING 1) set(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY) # SET HERE THE PATH TO YOUR C99 AND C++ COMPILERS set(PIX /opt/gcc-arm-none-eabi-10.3-2021.10/bin) set(CMAKE_C_COMPILER ${PIX}/arm-none-eabi-gcc) set(CMAKE_CXX_COMPILER ${PIX}/arm-none-eabi-g++) set(CMAKE_C_COMPILER_WORKS 1 CACHE INTERNAL "") set(CMAKE_CXX_COMPILER_WORKS 1 CACHE INTERNAL "") # SET HERE YOUR BUILDING FLAGS set(FLAGS "-O2 -ffunction-sections -fdata-sections -fno-exceptions -mcpu=cortex-m7 -mfpu=fpv5-d16 -mfloat-abi=hard -nostdlib -mthumb --param max-inline-insns-single=500 -D'RCUTILS_LOG_MIN_SEVERITY=RCUTILS_LOG_MIN_SEVERITY_NONE'" CACHE STRING "" FORCE) set(CMAKE_C_FLAGS_INIT "-std=c11 ${FLAGS} -DCLOCK_MONOTONIC=0 -D'__attribute__(x)='" CACHE STRING "" FORCE) set(CMAKE_CXX_FLAGS_INIT "-std=c++11 ${FLAGS} -fno-rtti -DCLOCK_MONOTONIC=0 -D'__attribute__(x)='" CACHE STRING "" FORCE) set(__BIG_ENDIAN__ 0) The above is how cmake is written. Among them, "-mcpu=cortex-m7 -mfpu=fpv5-d16 -mfloat-abi=hard": These options specify the architecture and floating point unit characteristics of the target processor. We can view the architecture and floating point unit characteristics of the MCXN947's target processor. We can open MCUXpresso IDE, open a MCXN947 project, and check mcpu=cortex-m33 -mfpu=fpv5-sp-d16 mfloat-abi=hard in All options in settings->MCU Linker. Therefore, the MCXN947 series is an M33 core. We need to change -mcpu=cortex-m7 to -mcpu=cortex-m33, and basically no other changes are needed. From this we can also see that a series of static libraries produced should be universal! 4.2 Configure the colcon.meta file according to Micro-ROS requirements The other file created sets the Micro-ROS library configurations. To set the transport layer type, here we want a custom transport layer, the configuration “-DUCLIENT_PROFILE_CUSTOM_TRANSPORT=ON” is set to “ON” and the configuration “-DRMW_UXRCE_TRANSPORT=custom” is set to “custom”. The other interesting settings are under the “rmw_microxrcedds” section. Here we can set the maximum number of nodes (1), publisher (5), subscribers (5), services (1) and clients (1) that should be supported, as well as the maximum message history (4) used for a reliable QoC mode. A more detailed description of all settings under this section, can be found in the eProsima Micro XRCE-DDS GitHub. An example configuration, the one I used, is shown below: touch colcon.meta { "names": { "tracetools": { "cmake-args": [ "-DTRACETOOLS_DISABLED=ON", "-DTRACETOOLS_STATUS_CHECKING_TOOL=OFF" ] }, "rosidl_typesupport": { "cmake-args": [ "-DROSIDL_TYPESUPPORT_SINGLE_TYPESUPPORT=ON" ] }, "rcl": { "cmake-args": [ "-DBUILD_TESTING=OFF", "-DRCL_COMMAND_LINE_ENABLED=OFF", "-DRCL_LOGGING_ENABLED=OFF" ] }, "rcutils": { "cmake-args": [ "-DENABLE_TESTING=OFF", "-DRCUTILS_NO_FILESYSTEM=ON", "-DRCUTILS_NO_THREAD_SUPPORT=ON", "-DRCUTILS_NO_64_ATOMIC=ON", "-DRCUTILS_AVOID_DYNAMIC_ALLOCATION=ON" ] }, "microxrcedds_client": { "cmake-args": [ "-DUCLIENT_PIC=OFF", "-DUCLIENT_PROFILE_UDP=OFF", "-DUCLIENT_PROFILE_TCP=OFF", "-DUCLIENT_PROFILE_DISCOVERY=OFF", "-DUCLIENT_PROFILE_SERIAL=OFF", "-UCLIENT_PROFILE_STREAM_FRAMING=ON", "-DUCLIENT_PROFILE_CUSTOM_TRANSPORT=ON", "-DUCLIENT_PROFILE_SHARED_MEMORY=ON", "-DUCLIENT_SHARED_MEMORY_MAX_ENTITIES=20" ] }, "rmw_microxrcedds": { "cmake-args": [ "-DRMW_UXRCE_MAX_NODES=5", "-DRMW_UXRCE_MAX_PUBLISHERS=6", "-DRMW_UXRCE_MAX_SUBSCRIPTIONS=4", "-DRMW_UXRCE_MAX_SERVICES=6", "-DRMW_UXRCE_MAX_CLIENTS=1", "-DRMW_UXRCE_MAX_HISTORY=4", "-DRMW_UXRCE_TRANSPORT=custom" ] } } } 4.3 Building the Micro-ROS Static Library Run the following commands: source install/local_setup.bash ros2 run micro_ros_setup build_firmware.sh $(pwd)/firmware/toolchain.cmake $(pwd)/firmware/colcon.meta If the static library is successfully generated, you will see libmicroros.a in the firmware/build file. 5. Integrating and Testing the Static Library Locally 5.1 Adding the Generated Micro-ros Static Library to the Local Project (1) Create a folder named bsp_include. (2) Add all files from the include directory into your project under bsp_include. (3) Add all paths in the include file to the include path. (4) Add the generated libmicroros.a static library to the project, for example, add it to bsp_include. (5) Add the libmicrorots.a static library and name path to Libraries(-l) and Library search path(-L). 5.2  Implementing the Serial Communication Interface Functions To port Micro-ROS to an MCU, you must provide transport layer functionalities for reading and writing through the communication interface. The required transport functions are defined as follows: rmw_ret_t rmw_uros_set_custom_transport( bool framing, void * args, open_custom_func open_cb, close_custom_func close_cb, write_custom_func write_cb, read_custom_func read_cb); ​ Through this structure, we can see that the communication interface function group mainly includes open, close, write, and read. open: This function is responsible for initializing (opening) peripheral devices used by the transport layer. This function is empty if the peripheral is initialized elsewhere and before the Micro-ROS function is called. close: This function is responsible for deinitializing (turning off) peripherals used by the transport layer. Because there is no need to deinitialize the function. This function is also empty. write: This function is responsible for writing data (bytes) on the peripheral device. The number of bytes to be written and the bytes themselves are given as parameters "len" and "buf" respectively. read: This function is responsible for reading data (bytes) from the peripheral device. The number of bytes to read is specified in the function parameter "len" and bytes should be returned via the function parameter "buf". bool transport_close(struct uxrCustomTransport * transport) { return true; } bool transport_open(struct uxrCustomTransport * transport) { return true; } size_t transport_write(struct uxrCustomTransport* transport, const uint8_t * buf, size_t len, uint8_t * err) { LPUART_WriteBlocking(DEMO_LPUART, buf, len); return len; } size_t transport_read(struct uxrCustomTransport* transport, uint8_t* buf, size_t len, int timeout, uint8_t* err) { LPUART_ReadBlocking(DEMO_LPUART, buf, len); return len; } Additionally, you need to implement a function to provide the system’s clock time. This clock does not have to provide real-time or world time, but rather elapsed time since startup or similar. For example: int clock_gettime(clock_t unused, struct timespec *tp) { (void)unused; IRTC_GetDatetime(RTC, &datetimeGet); tp->tv_sec = datetimeGet.second; tp->tv_nsec = (long)(datetimeGet.second) * 1000000; return 0; } 5.3 Testing To run Micro-ROS in practice, the setup includes two components: 1. A client running on the MCU. 2. An agent running on the host PC. Basic Micro-ROS Client (MCU) Below are the minimal steps and code needed to create and run a Micro-ROS client. These instructions are based on the Micro-ROS documentation for node creation. //Required global variables rcl_allocator_t allocator; rclc_support_t support; rcl_node_t node; rclc_executor_t executor; rmw_ret_t error; //Set Communication functions rmw_uros_set_custom_transport( true, NULL, rtt_transport_open, rtt_transport_close, rtt_transport_write, rtt_transport_read ); //Set Allocation functions (Optional) rcl_allocator_t allocator = rcutils_get_zero_initialized_allocator(); allocator.allocate = rtt_allocate; allocator.deallocate = rtt_deallocate; allocator.reallocate = rtt_reallocate; allocator.zero_allocate = rtt_zero_allocate; (void)!rcutils_set_default_allocator(&allocator); //Get allocator allocator = rcl_get_default_allocator(); //Create init_options error = rclc_support_init(&support, 0, NULL, &allocator); //Create node error = rclc_node_init_default(&node, "uROS_Terminal", "", &support); //Create executor error = rclc_executor_init(&executor, &support.context, 1, &allocator); //Call the executor periodically e.g. in the while(1) loop or a thread: while(1) { error = rclc_executor_spin_some(&executor, RCL_MS_TO_NS(100)); } ​ Setting up the Micro-ROS Agent (PC) The agent establishes an interface between the Micro-ROS client on the MCU and ROS 2 on the host PC. To set up the agent: # Go to the Micro-ROS workspace folder cd microros_ws # Source ROS 2 source /opt/ros/humble/setup.bash # Source local packages source install/local_setup.bash # Create Agent ros2 run micro_ros_setup create_agent_ws.sh # Build Agent ros2 run micro_ros_setup build_agent.sh # Possible ROS Update sudo rosdep init rosdep update  After successfully building the Micro ROS agent, the following bash command starts/runs the agent: # Go to the Micro-ROS workspace folder cd microros_ws # Source ROS 2 source /opt/ros/humble/setup.bash # Source local packages source install/local_setup.bash # Run Agent (serial connection) ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyACM0 Of these bash commands, the last one is the one that actually starts the Micro-ROS agent. It takes several parameters, the first is the type of connection to use, in this case a serial connection. Then there are two parameters that only apply to serial connections: "--dev/ttyACM0", which sets the serial interface to be used (to list all serial interfaces in linux, you can use the following bash command: "dmesg | grep tty".) After starting the Micro-ROS agent, the MCU can connect to the host PC via the serial interface and reset to establish a new connection. If the following Micro-ROS agent terminal output: This proves the success of transplanting Micro-Ros On Frdm-mcxm947.
記事全体を表示
i.MX RT1176 – 在现有 CM7 应用(支持 HAB)的基础上,为以太网启用 CM4 你好, 我们有一个应用程序,它只在 i.MX RT1176 的 Cortex-M7 上运行。目前未使用Cortex-M4。我们希望使 CM4 能够处理以太网(FreeRTOS + lwIP),而 CM7 则继续运行现有的应用程序,保持不变。 环境: - MCUXpresso IDE 11.6.1,SDK 2.13.0 - 从外部 FlexSPI 或非 闪存启动 - 已启用 HAB(安全启动)。 - CM7 上的 FreeRTOS 问题: 1. 从已运行的 CM7 应用程序中加载和启动 CM4 的推荐方法是什么?启用 HAB 时有哪些特殊注意事项? 2. 如何处理 CM4 崩溃或重启,才能使 CM7 继续运行而无需完全系统 RESET。 3. 推荐的内核间通信机制是什么,包括传输较大的数据块(几 KB)? 4. 时钟、引脚、中断、缓存和内存区域方面应该考虑哪些因素,才能使 CM4 不干扰 CM7? 5. SDK 2.13.0 是否适用于此需求,还是建议使用更新的 SDK 版本? 6.是否有在RT1170的CM4上运行以太网的SDK示例或应用笔记? 任何关于类似项目的指导或经验都将不胜感激。 谢谢! 开发板 Re: i.MX RT1176 – Enabling CM4 for Ethernet alongside an existing CM7 application (HAB enabled) 嗨@durgesh , 我建议查看AN13264 - i.MX RT1170 双核应用。本文档介绍了 i.MX RT1170 上的双核应用程序,包括启动过程、共享内存使用情况以及跨不同工具链的调试程序。 关于 SDK,我建议使用最新版本,因为它包含了最新的修复、增强和改进。 例如,有使用以太网的单核 CM4 SDK 示例。然而,我未能找到在 CM4 上实现以太网的双核应用程序示例。 此致, 巴勃罗
記事全体を表示
S32K118EVB2Q048:ADC读数与所选MCU供电电压不匹配 您好,NXP团队: 我正在使用 S32K118EVB2Q048 板(原理图 SCH-47530 Rev A1)测试 ADC。当输入电压超过约 3.3 V 时,我的读数就会出错。 设置: - MCU:S32K118(48-LQFP) - IDE:[S32 设计工作室版本] - 驱动程序:[RTD 版本 / SDK 版本 / 裸机版本] - ADC通道:[例如PTA7 – ADC0_SE3] 分辨率:12 位 - 输入:[外部直流电源/板载电位器] - 跳线:J10 = 2-3 (5V)、J107、J15 - 板供电方式:[USB / 12V] 问题: 我将 J10 设置为 2-3,这样 MCU 就可以在 5V 电压下运行。 - 输入 4.10 V:原始值 = 4095。以 5V 为参考电压,我预期读数约为 3358。 - 4V 至 5V 之间的任何输入:始终为 4095(满量程)。 - 当我使用 5V 电压进行计算时,随着输入电压的增加,误差也会增加。 问题: 在 SCH-47530 Rev A1 上,将 J10 设置为 2-3 是否足以使 VDDA 和 ADC 参考电压为 5V,还是我还需要更改其他任何东西(J15、J107、任何电阻器)? 能否分享一个适用于此EVB的S32K118 ADC工作示例,并用5V基准电压进行测试?能否也提供不同分辨率下的计算范围? Re: S32K118EVB2Q048: ADC readings do not match the selected MCU supply voltage 你好 请问您使用的是哪个RTD/SDK版本? 另外,我看到你正在使用 PTA7,但是你提到了 ADC_POT。由于 EVB 上未安装 R761,因此 ADC_POT 未连接: 我假设您是通过 J3.1 接头使用 PTA7。 请确认J10和J107都设置为 2-3,并尝试测量 VDD,以确保它确实设置为 5V。 我使用了RTD软件包中的Adc_Pdb_Ip_example_S32K118 ,并简单地修改了main函数,使其循环并启动软件转换: while(1) { /* Start a software trigger conversion */ Adc_Ip_StartConversion(ADCHWUNIT_0_VS_0_INSTANCE, ADC_IP_INPUTCHAN_EXT2, TRUE); /* Wait for the notification to be triggered and read the data */ while (notif_triggered != TRUE); notif_triggered = FALSE; delay(1000); } 之后,我使用电源测量了 0 到 5V 之间的电压,可以看到正确的数值。 ADC0_SE2 @3.3V: ADC0_SE2 @5V: 最后,检查 ADC_SC2[REFSEL] 中 REFSEL 是否设置正确: 此致, 朱利安
記事全体を表示
使用 NXP Trimension® SR250 入门 UWB - 第一部分:UWB 基础知识和 SR250 概述(日语博客) 介绍   “智能手机还在口袋里时,门就会打开”、“当你进入房间时,灯会自动打开”、“当你坐在沙发上时,条形音箱会自动调整声场以适应你的位置”——NXP Trimension ® SR250是一款能够将这些体验变为现实的设备。 SR250 是世界上首款用于物联网应用的集成电路,它集成了超高精度无线测距技术“ UWB(超宽带) ”和“ UWB 雷达”,无需外部设备即可在单个芯片上通过片上处理检测人和物体。 这款极具潜力的 SR250 终于在 2026 年 3 月面向大众市场发布!评估板SR250UWBSHIELD可从NXP 的电子商务网站购买。 如果你一直在想,“这听起来很有趣,但可能很难”,那么现在就是你尝试的机会。 在本系列文章的第一部分,我们将涵盖从UWB基础知识到SR250特性的所有内容。阅读本文,拓展您的想象力,然后入手一块评估板,一起体验UWB的魅力吧! 你之前听说过UWB吗?   如果你在想,“UWB 不是一种老旧的高速数据传输技术吗?”,那你真是太有洞察力了! 21世纪初,超宽带(UWB)作为一种高速无线数据传输技术引起了广泛关注。WiMedia联盟致力于将其标准化,但由于Wi-Fi和蓝牙的快速发展,最终未能得到广泛应用。 然而,在2010年代后期,UWB以一种截然不同的形式卷土重来。它被重新定义为一种精密距离测量和定位技术,并被标准化为IEEE 802.15.4z标准。2019年,iPhone 11搭载了这项技术,使其人气飙升。 超宽带(UWB)的基本特性——宽带宽——依然不变。然而,通过不再将这一特性视为“通信速度”,而是将其视为“时间分辨率”,全新的应用场景应运而生。 什么是UWB?——走进厘米的世界   超宽带(UWB)顾名思义,是一种无线技术,它使用极宽的频率带宽,相应地,使用极短的脉冲信号。该技术已被标准化为IEEE 802.15.4z标准,目前在短距离高精度定位领域正迅速普及。 虽然 Wi-Fi 和蓝牙的定位精度为 ±1-2 米,但 UWB 可以达到厘米级精度,为 ±5-10 厘米。这项技术可以检测“这里”,而不是“某个地方”。 厘米级的精度和高安全性相结合,实现了智能汽车门禁和精准的室内定位。除了安卓智能手机和AirTag之外,该技术还将集成到谷歌Pixel Tag中,预计未来将得到更广泛的应用。 *谷歌Pixel Tag计划于2026年11月发布。 为什么UWB对多径干扰的抵抗力如此之强且安全性如此之高?——与其他无线技术的比较   什么是多路径?   无线电波的传播方式并非像光一样沿直线传播;它们还会通过墙壁、天花板、家具和其他物体的反射而传播。在接收端,接收到的无线电波既有“沿直线传播的无线电波”,也有“从不同位置反射的无线电波”。这种现象被称为多径效应。尤其是在室内,反射现象更为普遍,从而形成多径环境。 基于 RSSI(无线电速度指示器)的测距方法,如 BLE 和 Wi-Fi,利用“混合无线电波的强度”来估算距离,因此极易受到反射波的影响。 由于超宽带使用非常短的脉冲信号(几纳秒宽),因此它可以将直接到达的信号与反射后稍后到达的信号在时间上分离和区分。   为什么UWB测距是安全的? 超宽带 (UWB) 使用一种称为STS (加扰时间戳序列)的加密信号序列。STS 每次都由基于 AES-128 的随机数生成器生成,每次生成的值都不同。接收方使用预共享密钥计算相同的 STS,并通过将其与接收到的值进行比较来验证发送方的合法性。 由于每次都会生成不同的STS值,因此涉及重传截获信号(重放攻击)或中继/欺骗信号以错误解读距离的攻击都无法实施。此外,在安全测距中,用于生成STS的会话密钥在安全环境中进行管理并定期重新计算。即使在特定时间点密钥信息泄露,造成的损失范围也有限。因此,UWB测距比基于BLE或Wi-Fi的测距具有更高的安全性。   距离测量技术比较   技术 准确性 多路径电阻 安全 主要用途 超宽带 ±5~10 厘米 高(直接用脉冲分离波) 高(STS加密) 精准定位和智能访问 BLE通道探测 ±0.5 米 介质(通过相位测量改进) 介质(受 RTT+ 相保护) 智能接入物联网 Wi-Fi RTT(FTM) ±1 至 2 米 低至中等 低的 室内导航和楼层检测 BLE RSSI ±1 至 5 米 低(基于强度) 低的 近距离检测和信标 其他技术,如 BLE 通道探测,在成本和功耗方面具有优势,因此根据应用的不同,其使用量有所增加,还可以与 UWB 进行混合配置。 UWB测距原理:飞行时间(ToF)和迎角(AoA)   飞行时间 (ToF) 在双向测距(TWR)中,发起方向响应方发送脉冲信号,响应方随后返回该信号。发起方测量无线电波的往返时间并计算距离。由于无线电波以光速传播,即使是很小的时间误差也会直接转化为距离误差。带宽越宽,时间分辨率越高,距离精度也越高。 此外,它通过组合多个设备支持 TDOA(到达时间差),从而实现大范围的实时定位。 到达角 (AoA) 设备所在位置的角度是通过多个天线接收到的信号的到达相位差 (PDOA) 计算得出的。由于 SR250 具有三个接收端口,因此可以执行3 次单次拍摄的 3D 到达角 (AoA)计算,同时计算水平角和垂直角。   什么是超宽带雷达?   测距是通过两个超宽带(UWB)设备之间的通信来测量距离,而雷达则采用完全不同的方法。它通过分析照射到人或物体上的脉冲反射信号,即使对方没有超宽带设备,也能探测到距离、方向和目标是否存在。 UWB 雷达甚至可以探测到人体最轻微的动作,让您能够感知周围是否有人以及他们是否在移动,同时保护隐私。 把雷达处理交给SR250吧!片上雷达处理   雷达算法复杂,从零开始开发并非易事。SR250芯片旨在处理单个目标的存在、距离和角度检测,无需自行开发算法即可使用雷达功能。对于更复杂的雷达处理,反射信号可以发送到主机,从而支持人工智能/机器学习应用。 SR250 开创的应用   SR250 将测距和雷达功能集成到单个芯片中,预计将广泛应用于各个领域,从智能锁和智能音箱等消费电子产品到工厂和仓库中 AGV(自动导引车)与叉车和工人之间的碰撞预防等工业应用。 “感知位置”、“感知存在”和“感知移动”——如果无需摄像头就能实现这三件事,那么可以创造出什么样的设备?请在阅读本系列文章的同时,畅想这些可能性。 计划序列化   本系列计划分为四部分。 第一部分(本文) UWB基础知识及SR250概述 第二次 设置 SR250 评估板 (SR250UWBSHIELD) 第三 我们来试试超宽带测距。 第四 试试超宽带雷达。 下次,我们将讲解如何获取评估板以及如何搭建硬件和软件环境。让我们一起准备运行UWB吧! 参考链接 Trimension SR250 产品页面(日语) SR250 评估板 (TRIMENSION-SR250) 超宽带雷达基础知识(AN13989) 超宽带融合雷达白皮书 Trimension SR250 培训介绍(英语,24 分钟) ========================= 即使您在本文的“评论”栏留言,我们目前也无法回复。 给您带来不便,我们深感抱歉。请在询问时参阅“NXP技术问题-联系方式(日本博客)”。 (如果您已经是NXP的代理商或与其有合作关系,可以直接向负责人咨询。) NXP Trimension® SR250 将厘米级精度的测距和无需单独设备的超宽带雷达集成到单个芯片上,于 2026 年 3 月面向大众市场发布。本文将解释超宽带的基本原理和 SR250 的特性。 (阅读时间:10分钟) 安全 日本博客
記事全体を表示
ウィンボンドW664GG6RB-06用IMX-8M-MINI DDRコントローラのタイミング こんにちは、 DDR4タイミングセットが正常に動作しない理由について説明を求めています。簡単に言えば、 DDRツールによって生成されたタイミングは校正および応力試験に合格しましたが、 断続的なLinuxカーネルは起動時にクラッシュし、「未定義命令」エラーが発生します。 設定(生の事実): - SoCはi.MX8M Mini Solo(シングルCortex-A53)、DDR4(Winbond W664GG6RB-06)です。 1200 MHz(DDR4-2400)は1:2 DFI(DDR PHYインターフェース)周波数比モードで、 単一のx16 4 Gbデバイス(512MB、ECCなし)。 - BSPはNXP L4.14.98_2.0.0(Linux 4.14.98、U-Boot 2018.03);DDRの設定は Mscale DDR Tool v3.31(Windows版)とPHYトレーニングファームウェアで生成 v201709。同じファームウェアがYoctoでU-Bootイメージの構築に使われています。 - 3つの交換可能な4Gb x16 DDR4メモリに対して、共通のタイミングセットを1つ認定しています。 部品(Alliance AS4C256M16D4、ISSI IS43QR16256B、Winbond W664GG6RB-06)はすべて動作しています 1200MHzで。 - 最も遅い部分 (Winbond) の tRCD/tRP/tAA (2400 bin で約 14.16 ns) を満たすために、 CL=17 (17-17-17) を設定すると、ツールはそれを MR0 = 0x0864 とエンコードし、対応する CL由来レジスタ(例:DFITMG0 = 0x038C8207、DRAMTMG2 = 0x0609050D)。 - DRAMは2400設定値で静的動作(デバイス内でDVFS/バス周波数が無効化) そのため、Linuxによる実行時の周波数スケーリングはありません。 観察結果: - 17-17-17構成は、DDRツールのストレステスト(約24時間)とU-Bootのmtest(約1時間)に合格します。 エラーなし。 - Linux上(シェルプロンプトに到達した起動時)ではstressapptest +にも合格します fio(CRC32C認証済み)は、Tj = 84°Cの温度で1時間以上連続かつ一定温度で、 データエラーはゼロです。 - それにもかかわらず、Linuxは起動時に「内部エラー: 未定義命令」(破損したカーネルの.text)、カーネル開始から約1.1秒後、 コールドブートの5~7%(自動コールド電源サイクルループで測定)。 - 故障はダイに依存しない:CL=17の画像も1秒間で同じ方法でクラッシュします これらの部分(ISSI)を使い、CL=16イメージは同じISSI上でLinuxを安定して起動します パート。 - 両方のeven-CL構成がLinuxを安定して起動します:16-16-16(当社の長年にわたる本番環境) タイミング)および新たに構築された18-18-18(カーネルクラッシュは見られません)—ただし、奇数CLのみです。 17-17-17は失敗。 - CL由来のレジスタのみが失敗設定と動作設定(MR0)で異なります CASビット、DFITMG0 dfi_t_rddata_en、DRAMTMG2リードレイテンシ/rd2wr、DFITMG2 rdcslat、 ODTCFG rd_odt_delay)。 仮説: 1:2のDFI比率での奇数CASレイテンシが根本原因、すなわち読み取りデータ(リードデータ)にあると推測しています 返還レイテンシはDFIクロックでCL/2であり、CL=17の場合は整数8.5、整数8.0は非整数です / 9.0 で CL=16 / 18。読み取りFIFO(DQSが書き、コントローラが読み取り)以降 クロック(リファレンス・マニュアル§9.3.2.2.2)は定常状態と定常応力を扱います 通過し、エッジ性は読み取りバースト間遷移で表面が現れると推測します。ここで 奇数CLの半DFIクロックオフセットは、RMが直面しない初拍・最後のビートのエッジCASEに当てはまります 記録を残す。 質問: CASレイテンシは奇数です(例:CL=17) は、1:2 DFI の i.MX8M Mini DDR4 PHY でサポートされています。 モード、または奇数CLに関する既知の制約/エラーはありますか?特にDDRは ツールは独自のストレステストを通過するが限界的な奇数CL構成を生成する 実際のブートトラフィックの下で、読書を制限する推奨方法はありますか? 奇数のCLのバースト・トゥ・バーストタイミングは? 添付ファイル:カーネルクラッシュコンソールダンプ、CL=17 .dsDDRツールのスクリプト、および ddr4_timing.c が生成されました。 どんなアドバイスでもありがたいです。 Re: IMX-8M-MINI DDR Controller timings for Winbond W664GG6RB-06 申し訳ありませんが、何らかの理由で添付ファイルが添付されませんでした。それらは以下の通りです。 Re: IMX-8M-MINI DDR Controller timings for Winbond W664GG6RB-06 以下の部品のタイミングパラメータで、CASレイテンシのtRCD(ns)tRP(ns)を確認してください。 Alliance AS4C256M16D4 DDR4-2400 17 14.1614.16 ISSI IS43QR16256B 2400Mbps 16-16-16 (-083R) ウィンボンド W664GG6RB-06 DDR4-2400 17-17-17 IS43QR16256Bの3番目のパラメータは異なります。そのため、3つのパーツごとに専用の設定が必要になるかもしれませんが、3つのパーツすべてに1つの設定を使うのではなく。問題は起動時のみ発生するようですね? Re: IMX-8M-MINI DDR Controller timings for Winbond W664GG6RB-06 こんにちは、 CL=17からCL=18に修正して再試し、DDRテストを実行し、Linuxを再度テストしてください。新しいバージョンへのアップグレードをおすすめします。
記事全体を表示