Yocto 项目™ 101 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用Yocto Project开发i.MX应用处理器的指南。 了解如何利用Yocto Project快速使用恩智浦参考板。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用Yocto Project开发i.MX应用处理器的指南。 了解如何利用Yocto Project快速使用恩智浦参考板。 i.MX 应用处理器

Infotainment, Connectivity & Security: CAN Secure (CSEc + FlexCAN on S32K) Explore how to build secure CAN connections by using data encryption or CMAC, while taking the best performance on S32K144. Explore how to build secure CAN connections by using data encryption or CMAC, while taking the best performance on S32K144. Identification & Security Interface & Connectivity

CAN in Future Car Networks—Understanding the Different Trends and Solutions Future networks will still use CAN to a huge extend - but the variety of trends is also significantly increasing. This session shows key values, technical background and differentiators of the different CAN trends and the NXP implementation. Future networks will still use CAN to a huge extend - but the variety of trends is also significantly increasing. This session shows key values, technical background and differentiators of the different CAN trends and the NXP implementation.

Beyond Studio Common Errors The “BeyondStudio for NXP” Integrated Development Environment (IDE) provides a platform for the development of wireless network applications to be run on NXP’s JN516x family of wireless microcontrollers. For more details and installation guide.  JN-UG-3098 (BeyondStudio for NXP Installation and User Guide). This document explains the common issues that the user will face when trying to develop a new application using BeyondStudio IDE. First of all, be sure that you are working with the latest SDK version and application note.    Import Problems After you import some application note that you want to take as reference. 2.2 Importing a Project. BeyondStudio for NXP Installation and User Guide.     1. Wrong Path A  common issue is a user uses another path for the installation of the SDK than the default one (C:\nxp\bstudio_nxp\workspace). When trying to find the Makefile ("SDK/JN-SW-4168/Stack/Common/Build/config.mk"), the IDE uses a relative path, for that reason it assumes that the file is in the correct directory. As the path was changed, the file can’t be found.   2.Project Directory After you select the Application Note (AN) you want to import remember that there will be an option for the JN517x as most of the projects are compatible between them (Zigbee 3.0, ZigBee Link Light). Nonetheless, BeyondStudio is not compatible with the JN517x.  While importing the project you only must select the JN516x project and none of the options must not be selected. Linking Errors Open a source file (.c) or a header file (.h),  you will notice that the IDE shows a lot of errors even though the project has not been compiled yet. The errors you are seeing is Eclipse not being able to resolve various variables and functions within the SDK. You might see some errors like: Symbol “xxx” could not be resolved for example. After starting the compilation process, look at the console log and notice that the bin file is being generated correctly. Do not try to add another file in the path and Symbols trying to avoid all those errors; the IDE will look for the includes that the project needs. If you used the default path location, it will not have any problem with the compilation. The OS_Gen, ZPS_Gen, and PDUM_Gen, for example, are all files automatically generated based on the configuration files, performing a clean will remove those files but will be created again after a new compilation. File app.zpscfg Problems Encountered The next error will appear if the Zigbee Plug-in is not installed. Follow the installation procedure for the plug-ins 1.2.3 Installing the ZigBee Plug-ins BeyondStudio for NXP Installation and User Guide. Look at the installation folder that is included in the SDK. C:\NXP\bstudio_nxp\sdk\JN-SW-41xx\Tools\Eclipse_plugins\com.nxp.sdk.update_site For a better reference the ZPS Configuration Editor provides a convenient way to set ZigBee network parameters ZigBee PRO Stack User Guide I hope it helps. Regards, Mario

Yocto Project™ Advanced A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. A guide to developing with the Yocto Project for i.MX application processors. Learn how to leverage the Yocto Project in development by adding layers and recipes, customizing images, working with the kernel, and other essential Yocto development tasks. i.MX Applications Processors Re: Yocto Project™ Advanced These slides use the 3.10 Kernel and meta-fsl-arm?  Isn't this stale?  The last commit to meta-fsl-arm was in 2016:  meta-fsl-arm - Layer containing Freescale ARM hardware support metadata  I was very much looking forward to reading about the current tips & tricks for building with i.MX & Yocto, but I don't think this is it. 

SD-CPE—A CPE to be Deployed with VM (Docker, etc.) and Managed by Orchestrator Concept of SD-CPE, virtualization of functions/applications on CPE, centralized management of CPE by orchestrator, advantages, and applications scenario in home, enterprise and industry. Concept of SD-CPE, virtualization of functions/applications on CPE, centralized management of CPE by orchestrator, advantages, and applications scenario in home, enterprise and industry.

HOWTO: S32 Design Studio Command Line Interface Building Projects There is already a significant amount of information already available on this topic. Please explore the external references listed below for detailed information. External References Building Projects with Eclipse Build Several CDT C++ projects from command line With the following command line, it is possible to build the project KEA128: eclipsec -nosplash -application org.eclipse.cdt.managedbuilder.core.headlessbuild -data C:\Users\username\workspaceS32DS.ARM2.0 -build KEA128/Release   The project was located in workspace - C:\Users\username\workspaceS32DS.ARM2.0 Project Name is: KEA128 Build Configuration is: Release Emitting Source Code S32 Design Studio for Vision Emitting the source code from the command line: There are 2 sections in the Reference Manual, one for each of the ISP and APEX2 Visual Graph Tools. Processor Expert Software - S32 Design Studio There is a section in the Processor Expert User Guide titled 'Command Line Interface' Re: HOWTO: S32 Design Studio Command Line Interface Hi @mikedoidge ,  I need support for S32D 3.4, S32DS.ARM2.0 No support for S32K3XX

Tools & Enablement: Service-Oriented Architecture—Automotive Linux BSPを使用した設計と実装 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> サービス指向アーキテクチャの認識と理解を促進します。AMP Linux BSP に基づく概念とステータスの図。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> サービス指向アーキテクチャの認識と理解を促進します。AMP Linux BSP に基づく概念とステータスの図。 ソフトウェアとツール

Mine BitCoins on i.MX8x platform Bitcoin is a cryptocurrency which is quite popular among many investors, tech enthusiasts, and some digital sellers/buyers due to its flexible, anonymous and robust nature.  BFG Miner is a bitcoin miner which has the ability to mine bitcoins on a range of devices from ASIC, to FPGA, to GPU, to obsolete CPU systems. This article will guide you step by step to do bitcoin mining on a i.MX8x platform by using the bfgminer. 1) Download the necessary software. bfgminer https://github.com/luke-jr/bfgminer.git jansson https://github.com/akheron/jansson.git uthash https://github.com/troydhanson/uthash.git 2) Cross compile the software: bfgminer: ./configure --prefix=${YourDirectory} --host=aarch64-linux-gnu --enable-scrypt --enable-cpumining --without-libevent --without-libmicrohttpd make jansson ./configure --prefix=${YourDirectory} --host=aarch64-linux-gnu make If everything runs correctly, you should get the following binaries and libraries: Ubuntu14:/opt/output$ ls -R .: bin include lib sbin share ./bin: bfgminer bfgminer-rpc start-bfgminer.sh ./include: jansson_config.h jansson.h libbase58.h libblkmaker-0.1## ./include/libblkmaker-0.1: blkmaker.h blkmaker_jansson.h blktemplate.h ./lib: libbase58.la libbase58.so.0 libblkmaker-0.1.la libblkmaker-0.1.so.6 libblkmaker_jansson-0.1.la libblkmaker_jansson-0.1.so.6 libjansson.a libjansson.so libjansson.so.4.10.0 libbase58.so libbase58.so.0.0.2 libblkmaker-0.1.so libblkmaker-0.1.so.6.1.0 libblkmaker_jansson-0.1.so libblkmaker_jansson-0.1.so.6.1.0 libjansson.la libjansson.so.4 pkgconfig 3) Install those binaries and libraries onto the i.MX8x target filesystem under directory /usr/bin and /usr/lib. Run the following command to start mining: #bfgminer -o stratum+tcp://us.ss.btc.com:1800 -u nxa001.001 -p ""   General

SD-CPE——与虚拟机（Docker 等）一起部署并由 Orchestrator 管理的 CPE <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> SD-CPE的概念、CPE上功能/应用的虚拟化、编排器对CPE的集中管理、优势以及在家庭、企业和工业中的应用场景。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> SD-CPE的概念、CPE上功能/应用的虚拟化、编排器对CPE的集中管理、优势以及在家庭、企业和工业中的应用场景。

S32K 损坏的演示 - 仍然运行良好！ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32K144 和 MPC5744P 电机控制演示平台被 UPS 运输公司破坏。电路板本身完好无损，第一次通电时运行良好。 （在 “我的视频” 中查看）

车身与舒适度：S32K 完整产品组合更新 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32K11x、S32K14x产品和解决方案，迁移到未来的S32K产品。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32K11x、S32K14x产品和解决方案，迁移到未来的S32K产品。 Arm® 处理器

Body & Comfort: S32K コンプリートポートフォリオアップデート <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32K11x、S32K14x製品およびソリューション、将来のS32K製品への移行。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32K11x、S32K14x製品およびソリューション、将来のS32K製品への移行。 ARM®プロセッサ

How to create and use static library in MCUXpresso IDE For the previous KDS or CodeWarrior users, they may not create and use static library under MCUXpresso IDE without a hitch, because the methods are not exactly same. MCUXpresso IDE supports adding static library in user project with “Smart Update” wizard. This feature is derived from LPCXpresso IDE.  However, “Smart Update” wizard is only available for natively supported LPC products in MCUXpresso 10.1.0 and lower versions.  It will support all LPC and Kinetis product in MCUXpresso IDE future release. For MCUXpresso natively supported LPC product, using “Smart Update” to add library is very convenient. User can learn its usage from this article: Creating and Linking to Library Projectshttps://community.nxp.com/message/630594 For Kinetis product, the only way to add library to project is by hand. This article will take an example with MK64F demo, illustrating how to create and use static library under MCUXpresso IDE step by step.  It will also be good for all LPC and Kinetis users to understand how user project works with external static libraries under MCUXpresso.  If user needs demo code of this article, please send me community internal message. Thanks for the suggestion from LPCX support         Re: How to create and use static library in MCUXpresso IDE Now, I have created static library successful and used static library by another project successful. But, how to create the static library within another static library? I have to package another lib(no source code, only a '.a' lib file) into my lib.

FlexNVM used as code/data Flash Example shows how can be expanded default 512kB flash memory by 64 kB using FlexNVM as a program/data flash. In FlexNVM are stored two ASCII images and function PrintImage. FlexNVM is divided into 32kB data section and 32kB code section in the linker file. Output is printed on terminal. As a output device you can use putty or any other serial terminal. Terminal settings: 9600, 8N1 - no flow control. In debugger settings you have to Enable partitioning device with code 0F0C. This value is written into FCCOB4 and FCCOB5 registers before flashing. Putty settings: Test HW: S32K144EVB, MCU: S32K144 Debugger: OpenSDA Target: internal_FLASH (debug mode and release mode) Example shows how can be expanded default 512kB flash memory by 64 kB using FlexNVM as a program/data flash. In FlexNVM are stored two ASCII images and function PrintImage. FlexNVM is divided into 32kB data section and 32kB code section in the linker file. Output is printed on terminal. As a output device you can use putty or any other serial terminal. Terminal settings: 9600, 8N1 - no flow control. In debugger settings you have to Enable partitioning device with code 0F0C. This value is written into FCCOB4 and FCCOB5 registers before flashing. Putty settings: Test HW: S32K144EVB, MCU: S32K144 Debugger: OpenSDA Target: internal_FLASH (debug mode and release mode)

EMB-2230 - I.MX6 Board with 40-Pin Expansion Header for Production Products Habey USA's EMB-2230 is a Pico-ITX ARM Board built around an NXP i.MX6 Cortex A9 processor, featuring an expansion header like those found in development and hobbyist boards - but optimized for use in commercial and industrial products. The board brings the ease and adaptability of "maker-boards", and the reliability and long product availability life-cycle of commercial ARM boards together. Specifications: NXP i.MX6 Cortex A9 Processor 1GB On-Board DDR3 8GB (default) iNAND Flash Storage Ethernet, BT 4.1BLE, 802.11b/g/n Dual LCD Interfaces (24-Bit LVDS and MIPI DSI) Rich I/O Options, Including HDMI 3* USB (2* USB 2.0, 1* USB OTG) USB & RS-232 Headers RS-485/CAN Bus Terminal Block 40-Pin Expansion Header w/ PCIe. PoE Input Accelerate Time To Market With a Developer Friendly Design The inclusion of easy-development features on the EMB-2230 helps ensure a quick time to market for any product. Included expansion headers, terminal blocks, and available 7" and 10" touch panel LCD kits make it easy to connect any sensors, hardware, or other devices and move your product directly from development to production. Easy Expansion Modules - Or Use With Other Devices Habey offers a variety of ready to use expansion modules, offering features like PoE (Power over Ethernet) or dual GbE ports; or use the 40 pin expansion header with PCIe, CAN Bus, RS-232, UART, SPI, I2C, and other GPIO devices. Commercial Product Life-Cycle Reliability The EMB-2230 has been carefully designed for a five-to-ten year long service life-cycle, ensuring no need to constantly test and recertify products as components change. Learn more: EMB-2230 Datasheet EMB-2230 Product Page Tech News - The Maker Board Explosion and Industrial ARM Boards

SD-CPE:VM(Docker など)とともにデプロイされ、Orchestrator によって管理される CPE <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> SD-CPEの概念、CPE上の機能/アプリケーションの仮想化、オーケストレーターによるCPEの集中管理、利点、および家庭、企業、業界でのアプリケーションシナリオ。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> SD-CPEの概念、CPE上の機能/アプリケーションの仮想化、オーケストレーターによるCPEの集中管理、利点、および家庭、企業、業界でのアプリケーションシナリオ。

Example MPC5777C External SRAM_test GHS714 ******************************************************************************** * Detailed Description: * Application performs basic initialization then it initializes EBI for external * SRAM connected to MPC5777C-516DS and test it by write and read of block of * data. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 3N45H * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  jumper J4 on position 1-2 (choosing CS0) * ******************************************************************************** ******************************************************************************** * Detailed Description: * Application performs basic initialization then it initializes EBI for external * SRAM connected to MPC5777C-516DS and test it by write and read of block of * data. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 3N45H * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  jumper J4 on position 1-2 (choosing CS0) * ********************************************************************************

QorIQ LSシリーズ・プロセッサを使用した電力効率の設計方法 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、2つの関連するトピックを取り上げます。最初のパートでは、新しいQorIQ LS1製品ラインの概要について説明します。セッションの第2部では、新しいLS1021A QorIQプロセッサ・ファミリの堅牢な電源配電ネットワークを設計するための重要な考慮事項について説明します。新しいLS1021Aボードをケーススタディとして、ボードで使用されている効率、設計の簡素化、パワーシステム管理手法などの主要な要素を確認し、それらがどのように使用され、なぜ使用されるのかについて説明します。このセッションでは、配電ネットワークを設計する際の主要な概念について基本的な理解を提供します。 Linear TechnologyのSharad Khanal氏とFreescaleの飯田聡氏によるプレゼンテーション 2015年3月26日、DwF Silicon Valleyにて発表 セッションID: AMF-SNT-T1040 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このセッションでは、2つの関連するトピックを取り上げます。最初のパートでは、新しいQorIQ LS1製品ラインの概要について説明します。セッションの第2部では、新しいLS1021A QorIQプロセッサ・ファミリの堅牢な電源配電ネットワークを設計するための重要な考慮事項について説明します。新しいLS1021Aボードをケーススタディとして、ボードで使用されている効率、設計の簡素化、パワーシステム管理手法などの主要な要素を確認し、それらがどのように使用され、なぜ使用されるのかについて説明します。このセッションでは、配電ネットワークを設計する際の主要な概念について基本的な理解を提供します。 Linear TechnologyのSharad Khanal氏とFreescaleの飯田聡氏によるプレゼンテーション 2015年3月26日、DwF Silicon Valleyにて発表 セッションID: AMF-SNT-T1040 Layerscape処理プラットフォーム

複数のフローティングライセンスファイルとNLライセンスファイルを1つのファイルにマージする方法 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 複数のライセンスファイルを1つのファイルにマージする方法は?     複数の製品のライセンスファイルを同時に生成する方法を示す/説明する2つのビデオを作成しました。 このドキュメントでは、このプロセスを次のように説明しています。 1つの登録に基づいて、異なる製品の複数のNLライセンスファイルをダウンロード 1つの登録に基づいて、異なる製品の複数のフローティングライセンスファイルをダウンロードし、それらを1つのファイルにマージする方法。     注記： 複数のフローティング登録があり、ライセンスファイルを 1 つのファイルにマージする場合、プロセスは 2 と似ています。 すべてのライセンスファイルを1つのファイルにコピーし、最初の3つのサーバー行のみを保持する必要があります。 もう一方は、上記で説明したように # を追加してコメント化する必要があります。 全般