Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
iMX6 IPU TVIN Application Notes Attached is an application note for iMX6 TVIN use case, some internal review was done. 2016-10-08, change it to pdf file. Re: iMX6 IPU TVIN Application Notes Dear Qiang Li - Mpu Se, It makes some problems in QT application (video stream freeze) have you ever noticed that kind of problems? Could you please have a look at : i.MX6_IPU_TVIN_Application_Notes patch cause problem in QT application  Yours,
View full article
MCX W23 Knowledge Hub The MCX W23 is a family of devices. All devices are Arm Cortex®-M33 based wireless microcontrollers for embedded applications supporting Bluetooth Low Energy 5.3. It can be used to develop IoT solutions. MCX W23xA supports LV_SM mode. MCX W23xB supports HV_SM and XR_SM mode. Building on NXP's strong history of providing industrial edge solutions, the MCX W series offers a wide operating temperature range from -40 °C to 125 °C. The Arm Cortex-M33 provides a security foundation, offering isolation to protect valuable IP and data with Trust Zone technology. It simplifies the design and software development of digital signal control systems with the integrated digital signal processing (DSP) instructions. To support security requirements, the MCX W23 also offers support for SHA-1, SHA2-256, AES, RSA, ECC, UUID, dynamic encryption, and decryption of the flash data using a PRINCE engine, debug authentication, and TBSA-M compliance. neidys_vargas_1-1760378278216.png   Documents Reference Manual Fact sheet Data Sheet Errata for MCX W23xUIK MCX W23 Hardware Design Guide Secure Reference manual** European Union Declaration of Conformity for FRDM-MCXW23 FRDM-MCXW23 Board User Manual Bluetooth Specifications The MCX W23 is compatible with the Bluetooth Low Energy 5.3 specification: – Bluetooth Low Energy 5.3 controller subsystem (QDID 200592) – Bluetooth Low Energy 5.3 host subsystem (QDID 226395) – Includes a 48-bit unique Bluetooth device address – Up to 4 simultaneous connections supported The MCX W23 supports the following Bluetooth Low Energy features: – Device privacy and network privacy modes (version 5.0) – Advertising extension PDUs (version 5.0) – Anonymous device address type (version 5.0) – Up to 2 Mbps data rate (version 5.0) – Long range (version 5.0) – High-duty cycle, Non connectable advertising (version 5.0) – Channel selection algorithm #2 (version 5.0) – High output power (version 5.0) – Advertising channel index (version 5.1) – Periodic advertising sync transfer (PAST) (version 5.1) – Supports LE power control feature (version 5.2) RF antenna: 50 Ω single-ended RF receiver characteristics: – Sensitivity −94 dBm in Bluetooth Low Energy 2 Mbps – Sensitivity −97 dBm in Bluetooth Low Energy 1 Mbps – Sensitivity −100 dBm in Bluetooth Low Energy 500 kbps – Sensitivity −102 dBm in Bluetooth Low Energy 125 kbps – Accurate RSSI measurement with ±3 dB accuracy Flexible RF transmitter level configurability: – TX mode 1 (TXM1): Range from −31 dBm to +2 dBm when VDD_RF exceeds 1.1 V – TX mode 2 (TXM2): Range from −28 dBm to +6 dBm when VDD_RF exceeds 1.7   Bluetooth_5.0_Feature_Overview Bluetooth_5.1_Feature_Overview  Bluetooth_5.2_Feature_Overview Bluetooth_5.3_Feature_Overview   Training MCX W Series Training - NXP Community   Equipment Wireless Equipment: This article provides the links to the Equipment that helps to the project development    Application Notes Power Management: AN14660: Power Management for MCX W23: This App Note provides information about the power manager software component. The application uses this component and the operating system to achieve optimal low-power states, based on the requirements of the application. RF: AN14575: MCX W23 Health Care IoT Peripheral Software Architecture: This App Note provides an overview of the software architecture for the MCX W23 Health care IoT Peripheral application. Designed as a model implementation, this application showcases the key features of the MCX W23 platform and serves as a foundation for developing product-quality applications. AN14659: MCX W23 Bluetooth Low Energy Power Consumption Analysis: This App Note describes the power consumption of the MCX W23 Bluetooth Low Energy (LE) device and the procedure to measure the current consumption using the MCXW23_EVK_BB and MCXW236B_RDM boards. AN2731: Compact Planar Antennas for 2.4 GHz Communication: This App Note is not an exhaustive inquiry into antenna design. It is instead focused on helping the customers understand enough board layout and antenna basics to select a correct antenna type for their application, as well as avoiding typical layout mistakes that cause performance issues that lead to delays Security: AN14657: Getting Started with Secure Boot on MCX W23: This application note covers the design of the bootloader ROM code that NXP has developed on the MCX W23, and how to use all its features. Useful Links Bluetooth LE FSCI Host Application running on FRDM-MCXN947 and MCXW23B-Click Board: The Bluetooth LE FSCI Host application demonstrates a host-side implementation for the Health Thermometer use case. It is designed to work alongside the FSCI Blackbox application, which runs on platforms such as the MCXW236 Click Board, FRDM-MCXW236, or other compatible Bluetooth LE wireless MCUs. Transmitter Maximum Output Power Override Application Note Kinetis (../45/47/43;MCX W71/72/70) & MCX W23 Power Profile Tools (including Localization):  This page is dedicated to the Kinetis (KW35/KW38/KW45/KW47/KW43) and MCX W7x (MCX W71/W72/W70) Power Profile Tools. It will help you to estimate the power consumption in your application (Automotive or IIoT) and evaluate the battery lifetime of your solution. Development Tools  VSCode: MCUXpresso for Visual Studio Code (VS Code) provides an optimized embedded developer experience for code editing and development. Zephyr RTOs  NXP Application Code Hub: Application Code Hub (ACH) repository enables engineers to easily find microcontroller software examples, code snippets, application software packs and demos developed by our in-house experts. This space provides a quick, easy and consistent way to find microcontroller applications. NXP SPSDK: Is a unified, reliable, and easy to use Python SDK library working across the NXP MCU portfolio providing a strong foundation from quick customer prototyping up to production deployment. NXP SEC Tool: The MCUXpresso Secure Provisioning Tool us a GUI-based application provided to simplify generation and provisioning of bootable executables on NCP MCU devices. NXP OTAP Tool: Is an application that helps the user to perform an over the air firmware update of an NXP development board. MCXW23
View full article
FRDM-IMX91S ハードウェアの紹介 FRDM-IMX91S ハードウェアの紹介 FRDM i.MX 91S開発ボードは、i.MX 91アプリケーション・プロセッサを中心に構築された、組み込みLinux開発用に最適化されたコスト効率の高いコンパクトなプラットフォームです。NXP IW610ワイヤレス・モジュールを内蔵し、インダストリアル&IoTアプリケーション向けの堅牢なWi-Fi 6 + Bluetooth LE 5.4 / 802.15.4コネクティビティを実現します。迅速なプロトタイピング用に設計されたこのボードは、i.MXアプリケーション・プロセッサ向けのGoPointをサポートしており、事前統合されたデモとリファレンス実装のスイートを提供します。 FRDM i.MX 91Sは、ダイレクトブート(NANDブート)をサポートする256MBのNANDフラッシュメモリを内蔵しています。これには、信頼性と最小限のリソース消費のために最適化された、徹底的にトリミングされた軽量のファイルシステムが含まれます。フットプリントが小さいため、使用可能なストレージを最大化しつつ、効率的な動作を実現します。このファイルシステムは理想的な出発点となります。モジュール式デザインは完全にカスタマイズ可能で、特定のアプリケーションニーズに合わせてさらに調整し、パフォーマンスを最適化することができます。 FRDM-IMX91S開発ボードについて 仕様 1x Arm® Cortex®-A55を搭載したi.MX 91アプリケーションプロセッサ LPDDR4 16ビット 512MB QSPI NANDフラッシュ、 256MB パワーマネジメントIC(PMIC) MicroSD 3.0 カードスロット USB 2.0 Type-Cコネクタ x 1 デバッグ用のUSB 2.0 Type-Cポート x 1 USB 2.0 Type-Aコネクタ x 1 USB Type-C PD x 1 オンボード Wi-Fi® 6 + Bluetooth® LE 5.4/802.15.4 モジュール 次の機能を備えた2×5ピンNXPカスタムインターフェース × 1: CANポート x 1 ADCチャネル × 2 I2C/I3C拡張 1 Gbpsイーサネット (ETER) x 1 コインセルコネクタ付き外部RTC 40ピン(2 x 20)拡張I/O 特長 FRDM-IMX91S SoCパッケージ 11 x 11 NVM NANDフラッシュ 256 MB DRAM NANYA 512MB PMIC PF9453 Wi-Fiモジュール u-blox MAYA-W476搭載 USB Type-C Type-C+Type-A ENET 1 x GBE ディスプレイ(パラレルRGB LCD) 2 x 20のEXPI カメラ(パラレルカメラ) 2 x 20のEXPI 2 x 20 拡張インターフェース あり CANバス あり microSD あり UART あり オーディオ MQS 電源コネクタ Type-C PCB層 6 ベースボード DIM 6.5 x 9.5 cm NXPデバイス搭載 PMIC PF9453 リアルタイム・クロック/カレンダー PCF2131 WIFI/BLE/802.15.4 トライラジオ IW610(u-bloxモジュール内) CANトランシーバ TJA1051T/3 IICによるGPIO拡張 PCAL6524 拡張ボード ​8MIC-RPI-MX8:音声イネーブルメント用8マイクロフォンアレイプロトボード MX93AUD-HAT:多機能オーディオ拡張ボード 便利なリンク −i.MX Yocto プロジェクトユーザーガイド − i.MX Linuxユーザーガイド − i.MX Linux リファレンスマニュアル −i.MX 移植ガイド -i.MX Debian Linux SDK ユーザーガイド FRDMトレーニング ハンズオン・トレーニング i.MXアプリケーション・プロセッサ
View full article
i.MX RT700 eIQ Neutron NPU ラボ ガイド これらのラボガイドでは、量子化された TensorFlow Lite モデルを取得し、Neutron変換ツールを使用する方法について、段階的な手順を説明します。 eIQ Neutron SDK モデルをi.MX RT700デバイスに搭載されているeIQ Neutron NPU上で動作するように変換する。 の eIQ Neutron NPU for i.MX RT700 ラボガイドでは、eIQ Neutron SDK に含まれる Neutron Converter ツールを使用してモデルを変換し、変換後のモデルを eIQ MCUXpresso SDK のサンプルにインポートする方法を解説しています。VSCode、GCC、MCUXpresso IDEs 用のラボが用意されています。 これらのラボはi.MX RT700 EVK上で動作するように設計されていますが、同じ概念はMCX Nボードにも適用でき、 MCX N eIQ Neutron NPUラボと類似しています。TFLM入門ガイドを参照すると、独自のモデルとデータを使用して推論を行う方法に関する情報が得られます。 また、 i.MX RT700に搭載されているeIQ Neutron N3-64 NPUについてさらに詳しく解説したAN14700 - i.MX RT700 eIQ Neutron NPUのイネーブルメントとパフォーマンスもぜひご確認ください。 --- MCUXpresso SDK 26.03およびeIQ Neutron SDK 3.1.0向けに2026年4月下旬に更新されました。 実践形式トレーニング
View full article
LS1043A で Aquantia AQR107 をサポートするパッチ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 添付のパッチは、LS1043AでAquantia AQR107をサポートするためのものです。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 添付のパッチは、LS1043AでAquantia AQR107をサポートするためのものです。 QorIQ LS1デバイス Re:LS1043AでAquantia AQR107をサポートするためのパッチ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> どうもありがとうございます!AQC108 イーサネット制御とPCI Expressのデータシートがあります。残念ながら、.uid に関する情報は見つかりません。正しいuidを知るために使用できるキーワードはありますか? Re:LS1043AでAquantia AQR107をサポートするためのパッチ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> パッチの下に追加する必要がありますが、AQR108のデバイスIDがわかりません。 スペックを確認する必要があります。 + +struct phy_driver aqr108_driver = { + .name = "Aquantia AQR108", + .uid = 0x3a1????, <- 仕様を確認する必要があります + .mask = 0xfffffff0、 + .features = PHY_10G_FEATURES、 + .mmds = (MDIO_MMD_PMAPMD |MDIO_MMD_PCS| + MDIO_MMD_PHYXS |MDIO_MMD_AN | + MDIO_MMD_VEND1)、 + .config = &aquantia_config、 + .startup = &aquantia_startup、 + .shutdown = &gen10g_shutdown、 +}; + int phy_aquantia_init(void) { phy_register(&aq1202_driver); phy_register(&aq2104_driver); phy_register(&aqr105_driver); + phy_register(&aqr108_driver);   0を返します。 } Re:LS1043AでAquantia AQR107をサポートするためのパッチ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> LS1043AでAquantia AQR108はサポートされていますか?
View full article
问答:LVDS1_CLK 终端 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 问题: 使用分割模式的 LVDS(双 LVDS)。在此配置中,仅使用 LVDS0_CLK。对于 LVDS1_CLK 有什么建议?HW 用户指南说,如果未使用,则将其保持浮动。对于这个案例,我们是否也建议采取同样的措施,或者终止合同是否更为合适?或者有没有什么可能的方法来控制这个时钟?(如果是这样,在 RM 中并不明显) 回答: 根据 MX6 开发人员指南,任何未使用的 LVDS 引脚都应保持浮动,因此在这种情况下 LVDS1_CLK 对应保持浮动。为了尽量减少任何潜在的 EMC,这些球的焊盘上不应该有任何额外的走线。 为了添加更多信息,客户进行了一些测试,发现在双模式下 LVDS1 的时钟门位基本上被忽略了。禁用它的唯一方法是将它们都禁用,但在这种情况下没有帮助。看来双模式设置会覆盖 CG。 i.MX6_全部
View full article
i.MX Yocto Project: How can I find out the packages include on an image? On the build folder, type bitbake -g && cat pn-depends.dot | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq where is the image name (e.g. core-image-minimal). In case you want to know if a certain <package> is included on an image, just grep the output bitbake -g && cat pn-depends.dot | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print $1}' | sort | uniq | grep Yocto Project Re: i.MX Yocto Project: How can I find out the packages include on an image? Hi Diego, Thanks for sharing those tips. I will definitely include your comments on the main post soon, so people can find it faster. Leo Re: i.MX Yocto Project: How can I find out the packages include on an image? Hello again As forever_newbies we are yet fighting with package names. We have found useful to add build history to compilation: INHERIT += "buildhistory" BUILDHISTORY_COMMIT = "1" The list of all files included in image and the package-names lists let us see if our try to add a particular file/binary is included without testing the image on the board. Also we found that spec files seem to list all possible sub-package names in a package source. We do:   cd build/tmp/work   find . \( -name '*.spec'  \) -exec grep "filename" {} \; -print to look for the sub-package with a particular file. The problem comes when the package is not included in the image at all. Then its directory does not exist at build/tmp/work. Then we googled and merged the results with this list of existing packages: http://packages.yoctoproject.org/ I don´t know if there are better ways to do it. Maybe somewhere is an index of what package have a particular binary. Maybe not. If anybody knows, feel free to let us know. Thank you Re: i.MX Yocto Project: How can I find out the packages include on an image? Hi Leonardo I am speechless :smileyshocked: Step over the link several times without seeing it. I only got to bitbake -g and tried to load the .dot files in my Ubuntu 12.04. It hung forever. I opened them in textmode and close it inmediately :smileysilly: Thank you
View full article
CSCI E-251、2012年秋 - 最終プロジェクトプレゼンテーション - Eric Pedersen <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ハーバードエクステンションスクール CSCI E-251、2012年秋:オペレーティングシステムの原則 最終プロジェクトプレゼンテーション エリック・ペダーセンによるプレゼンテーション (マイビデオで視聴) 学生プロジェクト
View full article
FreeMASTER 3.2 - 发布公告 NXP FreeMASTER 工具 3.2 版刚刚在线发布。 这是新 3.2.x 的第一个版本发布线。它向后兼容以前的 3.x 和 2.x 版本(请参阅以前的版本 公告)。最新版本带来了本文描述的新功能和错误修复。 更新后的安装程序以及文档和其他资源可在http://www.nxp.com/freemaster上获取。 发布说明 FreeMASTER是 NXP 开发和提供的一款强大的数据可视化工具,可帮助用户监视和控制在 NXP 目标上运行的嵌入式应用程序。它可与边缘处理和汽车业务线的几乎所有 NXP Arm ® Cortex ® -M 微控制器以及 DSC 和传统 Power Architecture、ColdFire 和 HCS12/Z 平台配合使用。请注意,许可条款和条件不允许将 FreeMASTER 与其他供应商的未经授权的系统一起使用。 3.2.0 版本是新 3.2.x 的第一个版本发布线。该安装程序不会取代系统中的旧安装,3.2 版本可能会与旧版本同时共存。 3.2 版完全向后兼容所有以前的版本,并添加了此处描述的新功能。传统上,它支持嵌入式应用程序的运行时监控,显示变量值、示波器实时图表、快速瞬态记录器图表,并支持与第三方应用程序的连接。此版本引入的主要新功能是支持 Microsoft Edge WebView2 浏览器组件,该组件可用于呈现在 FreeMASTER 主应用程序窗口中嵌入运行的仪表板和其他控制应用程序。 总的来说,现在有三种在 FreeMASTER 内部托管活动 HTML 内容的选项:版本 1.x 和 2.x 中引入的传统 Microsoft Internet Explorer 组件;版本 3.0 中引入的 Chromium CEF 组件和新的 Microsoft Edge WebView2 组件。 新的 Edge WebView2 也基于 Chromium 引擎,因此它与 FreeMASTER 的 JSON-RPC 客户端界面完全兼容。此外,Edge 还部分支持 COM+ 主机对象嵌入,从而可以访问“传统” FreeMASTER ActiveX 接口。这种多功能性使得最初为 Internet Explorer 创建的旧仪表板和控制页面能够顺利迁移到现代浏览器框架中。请注意,Microsoft 正在逐步淘汰 Internet Explorer 浏览器和相关技术,并且基于 IE 的应用程序在不久的将来可能无法再正常运行。 请在 FreeMASTER 欢迎页面上阅读 IE 迁移白皮书以了解更多信息。 FreeMASTER Lite服务是 FreeMASTER 安装包的一部分,为 Windows 和 Linux 系统提供通信核心。它可以通过 JSON-RPC 接口以类似 FreeMASTER 桌面应用程序的方式进行访问。FreeMASTER Lite 还嵌入了流行的Node-RED框架用于图形编程,并提供了许多使用 FreeMASTER 工具的示例。在专门的培训视频中查找与 Node-RED 相关的更多信息。 注意:安装 FreeMASTER Lite 将需要您输入激活码。在 许可证信息页面 的“许可证密钥” 选项卡上获取免费代码。 FreeMASTER Node.js 可安装模块支持在由“npm”包管理器管理的 Node.js 应用程序中方便地使用 FreeMASTER JSON-RPC 组件。 新增功能 关键的新功能是支持 Microsoft Edge WebView2 浏览器组件,该组件可用于将在 FreeMASTER 中运行的旧仪表板和其他 HTML 应用程序从 Internet Explorer 迁移到现代浏览器,而对 HTML 和 JScript 代码的更改却很少。 此外,ActiveX 和 JSON-RPC 接口已通过新方法进行了扩展,可以从脚本环境以编程方式访问项目内容和项目选项。 发布的目标受众群体 FreeMASTER 和 FreeMASTER Lite 主要针对希望在运行时监控和控制其应用程序的工业、物联网和汽车领域的 NXP 嵌入式应用程序的客户、工程师和开发人员。FreeMASTER 也是一个强大的框架,可用于创建交互式演示和用户界面,帮助更广泛的目标受众使用嵌入式应用程序。 前提条件 FreeMASTER 工具在主机上运行,并使用串行、CAN、以太网/WiFi 网络、JTAG、BDM 或其他物理接口与目标微控制器应用程序通信。微控制器通信驱动程序可作为 MCUXpresso SDK、S32 Design Studio 的一部分或独立安装包提供。在使用 FreeMASTER 工具之前,请熟悉通信协议和微控制器驱动程序 API。 许可条款和条件仅允许在基于NXP微处理器或微控制器系统的系统上使用FreeMASTER。 封装 包含 FreeMASTER 桌面应用程序和新 FreeMASTER Lite 服务的单个自解压安装包可用于 Windows 平台。带有 FreeMASTER Lite 服务的软件包也适用于 Linux。 访问 FreeMASTER 主页https://www.nxp.com/freemaster 上的安装和文档。
View full article
Energy Efficiency - Kinetis vs. Competitors - Demo Demo Owner: Eduardo Montanez   Watch how Kinetis K Series and Kinetis L Series MCUs beat out the competition.     Features Latest Kinetis K2 microcontrollers running a CoreMark benchmark from EEMBC 4 different Microcontrollers are put to the test. Running all the same iteration benchmark with same capacity for all of the products Featured NXP Products K22F KL02 Links Kinetis MCUs|ARM® Cortex®-M Cores|NXP Kinetis L Series MCUs: Energy-Efficiency Benchmark Demo Kinetis L Series MCUs Energy Efficiency Benchmark - YouTube   Industrial
View full article
使用 KDS 中 FRDM-MK64 板上的加速度计 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDS中的加速度计 说明:   这是在 KDS 中使用 FRDM-MK64FN1M0VLL12 板上的加速度计制作的一个小项目。 当板子平放或倒置时,蓝色 LED 亮起 当电路板侧放时,红色 LED 亮起 当滑板处于机头或机尾位置时,绿色 LED 亮起   代码部分取自http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDS中的加速度计 说明:   这是在 KDS 中使用 FRDM-MK64FN1M0VLL12 板上的加速度计制作的一个小项目。 当板子平放或倒置时,蓝色 LED 亮起 当电路板侧放时,红色 LED 亮起 当滑板处于机头或机尾位置时,绿色 LED 亮起   代码部分取自http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/ 概述
View full article
KDS Debug Configurations (OpenOCD, P&E, Segger) NOTE: the screenshots below are for KDS V1.0.1-beta!   After creating a new debug configuration is simple: Select either 'GDB OpenOCD Debugging', 'GDB PEMicro Interface Debugging' or 'GDB SEGGER J-Link Debugging' and use the 'new' button: Verify the project and application settings:   After that, there are a few settings to be checked or set, depending on your connection.   OpenOCD with CMSIS-DAP Make sure '-f kinetis.cfg' is specified as 'Other Options':   P&E with OpenSDA or Multilink Select your Interface, Port and Device Name:   Segger J-Link Make sure you use the correct device name (link to Segger web page (scroll there down!) lists all supported devices). OpenSDAv1 and OpenSDAv2 is using SWD. Disable SWO if not supported by your connection: General Re: KDS Debug Configurations (OpenOCD, P&E, Segger) I am using KDS 3.2.0 by selecting PnE as debug option on the FDRM-KE06Z board. I follow the steps above to configure the Debug configurations. But an error message keeps popping-up: "Launching xxx_Debug_PnE' has encountered a problem. Error in services launch sequence Details>> Error in services launch sequence PEmicro GDB Launch Failure : Another GDB Server debug session is alreadyusing the same Server Port number. To run simultaneous debug sessions, please specify a unique Server Port and GDBMI Port in the Debug Configuration for each project. If another session is not running simultaneously, make sure that the pegdbserver_console and the arm-none-eabi-gdb processes have terminated. May i know what's wrong with my PnE configuration on Server Port number? I just have a project file open and build in my project explorer for this time being? Re: KDS Debug Configurations (OpenOCD, P&E, Segger) In case this is helpful: here is how to reprogram the Hexiwear docking station bootloader and firmware: Reprogramming the Mikroelektronika Hexiwear Dockingstation | MCU on Eclipse  I hope this helps, Erich Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Hi Jaime, OpenOCD only supports a limited number of Kinetis devices, and if I'm not mistaken, the KW40 is not supported. I have not used it for the KW40 and used P&E and Segger instead. I can look into how to re-program the K20 on the docking station with the DAPLink bootloader, but for this you will need an external probe in any case. Erich Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Hello! Thanks for your quick response. Heres an image of my debug configuration  The OpenOCD .exe exists on that path. My Hexiwear docking station has Switch 5, (OpenSDA pin) up and both Switches 3 and 4 up to target the KW40Z MCU.  More information that could be helpfull; when i run the openocd.exe from the command line, i get the following text: Thank you very much for your help Jaime Re: KDS Debug Configurations (OpenOCD, P&E, Segger) It would be helpful if you could post screenshots of your debug launch configuration settings. It basically means the GDB client cannot connect to the OpenOCD server (see the same message for Segger J-Link: Fix for GDB and “The system tried to join a drive to a directory on a joined drive”). Can you check that: - openOCD binary is properly referenced in your settings (${openocd_path}/${openocd_executable}) - OpenOCD binary actually exists on that path - Start OpenOCD locally is checked - Your Hexiwear docking station has the properl OpenOCD/CMSIS-DAP firmware loaded ? I hope this helps, Erich Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Hello!  I get this error when trying to program the Hexiwear device with OpenOCD. Error in final launch sequence Failed to execute MI command: -target-select remote localhost:3333 Error message from debugger back end: localhost:3333:The system tried to join a drive to a directory on a joined drive. Any idea on how to fix it? Thanks Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Please, give an example of setting a debug session for OpenOCD FTDI debug interface for K60 Re: KDS Debug Configurations (OpenOCD, P&E, Segger) thanks for a very helpful page! The setup options in KDS are different (more complex) than CW, and I was scratching my head regarding what to do with my j-link (segger).  Lifesaver once again Erich!
View full article
Single Wire Output (SWO) support within S32 Design Studio, enabled by PEmicro's GDB Server PEmicro’s GDB Server can take advantage of four useful SWO debug tools: Power Measurement SWO ITM Console SWO Data capture Real-Time Expressions. This document describes how to enable and use these features. Note: To set up streaming for SWO debug features, the user should check the “Enable Streaming” checkbox in Debug Configurations during setup. Then the port should be specified in the Streaming Server Port text box. Hardware Requirements The following versions (or later) of PEmicro hardware interfaces are required to take advantage of SWO streaming functionality: Multilink FX Rev. C Multilink Universal Rev. D Multilink ACMP Rev. B Real-Time Power Measurement To enable Power Measurement capture, an active debug session must already be in process. Click the Gear Icon on the title bar of the PEmicro "Power Measurement” window. Select the frequency of data capture and check the Enable box. After clicking OK, Power Recording is now active. Note:    The Multilink FX debug probe is required for Real-Time Power Measurement Power Configuration Dialog The next time the target MCU is run, real-time power measurement readings will be shown. The user can start/stop power recording, zoom, export data, and more SWO Printf Console The SWO Printf Console will display messages which are streamed through the SWO pin and captured by the Multilink. There are two main configuration steps needed to leverage this feature. First, the project must be configured to re-direct the printf() statements to the SWO Printf peripheral. This is done at project creation time. Second, the green "Play" button on the SWO ITM Console needs to be clicked during an active debug session. This will cause data collection of SWO printf information to occur on the next Resume. Once data is streaming, the red “Stop” button will stop data streaming. Printf() Statements Displayed In SWO ITM Console The Multilink automatically measures the data communication rate on the SWO pin and adjusts to it automatically. This auto-detect sequence is done each time the processor is stopped in debug mode. If the running code changes the core frequency, a breakpoint should be set after the frequency change so the Multilink can adjust to the new SWO communications rate (which is a function of the core frequency). SWO Data capture The SWO Data view allows the user to configure variables to be tracked such that any reads and writes to these variables are captured and streamed to the Multilink via the SWO pin. This view shows all of the realtime access which have occurred along with the timing of the different accesses. For SWO data, there is a bit more setup.  The user needs to select the 'Eyeglasses+' symbol which will bring up a popup of Add datawatch items.  Simply enter the information of the different variables to be tracked. Up to four separate variables can be tracked simultaneously. In this example, we select that we wish to capture read and writes of the ledsOn and seconds variables. Once added, the user needs to select which watches data will be captured by checking the "Enable trace" boxes in the SWO Data window and then click the Green Arrow to set the program to start capture on Resume.Upon resuming the application, the right side of the window will show the access which are occurring. Note that this happens in real-time; the microcontroller is not stopped when accesses occur (i.e. the is separate from data breakpoints). Variable Read/Writes Displayed In Real Time The Multilink automatically measures the data communication rate on the SWO pin and adjusts to it automatically. This auto-detect sequence is done each time the processor is stopped in debug mode. If the running code changes the core frequency, a breakpoint should be set after the frequency change so the Multilink can adjust to the new SWO communications rate (which is a function of the core frequency). Real-Time Expressions This view is similar to the standard Eclipse "Expressions" window with the exception that its contents will update in real-time without the device being halted in debug mode. Just add the appropriate variables to the Real Time Expressions window and you will see them updating in real-time. Add Variables To Real-Time Expressions Windows 3-rd party (premium) plug-ins Eclipse IDE Usage and Settings General
View full article
RDDSP56F8SRDS: 3-Phase SR Motor Sensorless Control Reference Design using 56F80X or 56F8300 DSCs Overview Features Block Diagram Board Design Resources Overview The reference design demonstrates sensorless control of the 3-Phase Switched Reluctance (SR) motor using 56F80x or 56F83XX Digital Signal Controllers. It can also be adapted to 56F81XX Digital Signal Controllers. The concept of this application is that of a sensorless speed closed loop SR drive using flux linkage position estimation. An inner current loop with PI controller is included. The change in phase resistance during motor operation due to its temperature dependency creates errors in the position estimation and significantly affects the performance of the drive. Therefore, a novel algorithm for on-the-fly estimation of the phase resistance is included. The Digital Signal Controller runs the main control algorithm. Rotor position is evaluated using the sensorless flux linkage estimation algorithm. The actual flux linkage is calculated at the rate of the PWM frequency and is compared with the reference flux linkage for a given commutation angle. When the actual flux linkage exceeds the reference, the commutation of the phases is done; the actual phase is turned off and the following phase is turned on. Flux linkage error is used for estimation of the phase resistance at low speeds (US Patent No.: 6,366,865). The actual speed of the motor is determined using the commutation instances. Based on the speed error, the speed controller generates the desired phase current. When the phase is commutated, it is turned on with a duty cycle of 100%. Then, during each PWM cycle, the actual phase current is compared with the desired current. As soon as the actual current exceeds the desired current, the current controller is turned on. The current controller controls the output duty cycle until the phase is turned off (following commutation). Finally, the 3-Phase PWM control signals are generated. The procedure is repeated for each commutation cycle of the motor. Features Sensorless control of an SR motor using a flux linkage estimation technique Targeted for 56F80X, 56F83XX, and 56F81XX Digital Signal Controllers Running on a 3-Phase SR HV Motor Control Development Platform The control technique: current control with a speed closed loop Position estimation based on flux linkage estimation Phase resistance measurement during start-up Phase resistance estimation at low speeds Motor starts from any position with rotor alignment Encoder position reference for evaluation of sensorless position estimation Manual interface FreeMASTER software control interface and monitor Fault protection Block Diagram Board Design Resources Legacy Designs
View full article
Flash Programming Algorithms for MPC57xx Hi,    Please update your Cyclone Flash Programming Algorithms for MPC57xx through the link.      http://www.pemicro.com/support/flash_list_menu.cfm     Older code algorithms includes area of HSM. If there are ECC errors in these blocks, the device may stuck in reset. During reset, the SSCM module searches for valid boot header. If it reads corrupted data from HSM blocks, it will not exit the reset.     Newer should be with “NO_BASE_ADDRESS=00F90000/”   https://community.nxp.com/thread/444748   Failed sample waves on PORST vs RESET are as below.    Algorithms in S32DS_Power_v2_1 and S32DS_Power_v2017_R1 are good.     Regards Oliver
View full article
功能安全与保障:NXP ®汽车网络安全计划 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍汽车网络安全。除其他外,我们将概述:恩智浦的汽车安全产品组合;行业标准和最佳实践;以及恩智浦的全球安全组织、网络安全设计和业务实践。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将介绍汽车网络安全。除其他外,我们将概述:恩智浦的汽车安全产品组合;行业标准和最佳实践;以及恩智浦的全球安全组织、网络安全设计和业务实践。
View full article
HOWTO: debug multi-core project in S32 Design studio Build your project and choose Debug Configuration option  On the left side select Launch Group of your choice (Flash/RAM) and press Debug button Wait while debug session is fully started. If you left default startup configuration - all cores has active break-point at the beginning of main() function. You can chose any core for debugging just by clicking on the core's thread. Sometimes are init functions - including startup of other cores - inside main() of boot core (for S32R274 is boot core Z4). In this case you should let boot core perform init sequence first and then try debug other cores. On next picture are all cores halted.  On this picture are core 1 (Z4) and 2 (Z7_0) running - and third one is stopped. You can perform any debug operation on this core (memory/registers view, instruction step...) without effect on other cores.  On the last picture are running cores 1 (Z4) and 3 (Z7_1) and second core (Z7_0) is stopped and any debug operation can be performed on this core.  Re: HOWTO: debug multi-core project in S32 Design studio Hey Jiri, What debug configurations have you used for this sample project? I am getting following error:  Error in services launch sequence. PEmicro GDB Launch Failure : The GDB Server was not able to establish a connection to the target processor. Please check your connections and power. Verify that the launch settings in the Debug Configuration are accurate. I have checked and made sure that it is not a hardware issue. I am not able to establish a connection with the target processor. I wantd to know what are the GDB run parameters that you are giving. Thanks, Su
View full article
ADAS 和驱动程序替换:支持下一代 S32 产品的 S32 配置工具 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32 Design Studio 3.0 S32V234 专注于配置工具引脚向导、时钟配置、SDK 配置、FreeRTOS 配置以及使用构建和运行项目,展示在 m4 上使用 S32 调试器进行调试,并在目标上使用代码。由引脚、时钟、外设、DCD、IVT 组成的配置工具套件提供了平台的完整视图,可以直接从工具中访问所有细节,并可以生成、构建和调试应用程序。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32 Design Studio 3.0 S32V234 专注于配置工具引脚向导、时钟配置、SDK 配置、FreeRTOS 配置以及使用构建和运行项目,展示在 m4 上使用 S32 调试器进行调试,并在目标上使用代码。由引脚、时钟、外设、DCD、IVT 组成的配置工具套件提供了平台的完整视图,可以直接从工具中访问所有细节,并可以生成、构建和调试应用程序。
View full article
射频电路集 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 描述 通过 RF 电路集合,NXP 客户可以浏览、下载和订购大量参考电路文档。 视频 RF电路集合简介 分步指南 1. 访问www.nxp.com/rfcollection 。 2. 接受点击许可。 3. 使用排序工具或直接在搜索引擎中搜索,按频率或功率浏览 400 个参考电路 4. 根据文档的可用性,单击相应的按钮下载或请求所需的文档。 5. 你需要一块板子吗?使用集合中的分销商按钮通过我们的分销商合作伙伴订购。 产品 恩智浦产品 链接 NXP RF Cicruit系列 www.nxp.com/rfcollection 移动设备
View full article
Green Hills Software:i.MX 8およびS32上の安全でセキュアな自動車システムのための信頼できるソフトウェア基盤 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自動車メーカーとそのTier 1は、自動運転、車車間通信、OTA(Over-the-Air Updates)、ヘッドアップディスプレイ(HUD)などの新しい利便性と安全機能により、自動車に革新的な機能をもたらしています。現代の自動車では、車両の運用寿命にわたって日常的に安全でない環境で動作するために、重要なソフトウェアコンポーネントの認証、識別、分離が求められています。信頼性の高いランタイムソフトウェア基盤を重要な構成要素として開始することで、ADAS、自動運転、統合統合コックピット、C2C/V2X、Linux / Androidインフォテインメント、およびGPUアクセラレーションOpenGLグラフィックスを備えたセーフティクリティカルなインストルメントクラスタ向けのNXPの i.MX 8および次世代S32プロセッサファミリで将来のスケーラブルなプラットフォームを設計しています。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自動車メーカーとそのTier 1は、自動運転、車車間通信、OTA(Over-the-Air Updates)、ヘッドアップディスプレイ(HUD)などの新しい利便性と安全機能により、自動車に革新的な機能をもたらしています。現代の自動車では、車両の運用寿命にわたって日常的に安全でない環境で動作するために、重要なソフトウェアコンポーネントの認証、識別、分離が求められています。信頼性の高いランタイムソフトウェア基盤を重要な構成要素として開始することで、ADAS、自動運転、統合統合コックピット、C2C/V2X、Linux / Androidインフォテインメント、およびGPUアクセラレーションOpenGLグラフィックスを備えたセーフティクリティカルなインストルメントクラスタ向けのNXPの i.MX 8および次世代S32プロセッサファミリで将来のスケーラブルなプラットフォームを設計しています。
View full article