QT5 Support for Qt3D Before QT5 Qt3D was a separate project and was maintained separately.  Now it is offered along with other official plugins. QT3D supports the addition of 3D elements. In order to install it this is needed: Clone the git Qt3D repository $ git clone git://gitorious.org/qt/qt3d.git Using the Qmake that you already created when installing Qt5, this will setup the Makefile in order to cross compile the plugin. $ qmake $ make $ sudo make install Ready to play with Qt3D! This is the HelloWorld of 3D,  teapot.bez  is a bezier curves file with the forms of the famous teapot. import QtQuick 2.0 import Qt3D 1.0 Viewport{    width: 640; height: 480    Item3D{    id: teapot    mesh: Mesh { source: "teapot.bez" }    effect: Effect {}   } }

[Solution] IAR version 8.32 can not debug revision '1B' of LPC55S69 silicon When you are the first time to debug LPC55S69, please read below document and double check your IDE, SDK and EVK version is correct. Usually, we prefer use the latest IDE, SDK and EVK boards. Important updates when using LPCXpresso55S69 Revision A2 boards and 1B silicon  [Problem Description] When you use IAR 8.32 to debug LPC55S69 '1B' silicon, the IDE will remind you "The debugging session could not be started", like below picture show: The reason of this failure is that IAR 8.32's LPC55S69 chip configuration files only support revision '0A' silicon, not '1B'. We strongly recommend customer download and use IAR 8.40.2 or latest version. The IAR IDE start support LPC55S68 '1B' silicon from 8.40.2. [Solution] If you have some reasons that must use IAR 8.32, you can download attached zip file. This zip file like a patch, include the IAR LPC55S69 '1B' support files. Un-zip this file and merge the same files under IAR installed path :IAR\arm\config\flashloader\NXP Then the IAR can support '1B' silicons. [How to identify LPC55(S)6x chip silicon versions] On the top-side marking code, there is '1B'  charactors at the end of mark strings. See below two pictures, the left one is '1B' version chips.                      LPC55(S)6x ver '1B'                                                               LPC55(S)6x ver '0A'                    LPC55xx

NXP Tech Session - CANopen and NXP Microcontrollers - Proliferating robust network communication with fast evaluation and deployment View Webinar Recording View Webinar Recording LPC55xx

eMMC RPMB Enhance和GP [中文翻译版] 见附件   原文链接： https://community.nxp.com/docs/DOC-343116  i.MX6_All i.MX6DL i.MX6Dual i.MX6DualPlus6QuadPlus i.MX6Quad i.MX6S i.MX6SL i.MX6SoloX i.MX6UL

恩智浦技术研讨会 - 了解S32G车载网络处理器 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 查看网络研讨会录音 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 查看网络研讨会录音

i.MX 8QM MEK - IMX-AUD-IO - Audio out Quick notes on testing audio on the i.MX 8QuadMax MEK board with 4.19.35-1.1.0 BSP. Hardware:   - Connect the MCIMX8QM-CPU to the MCIMX8-8X-BB.  - Connect the IMX-AUD-IO to the Audio Slot 1 on the MCIMX8-8X-BB.  - Short 2 and 3 on J47 on the MCIMX8-8X-BB  - Connect an external powered speaker to RCA connectors Audio OUT FR and/or Audio OUT FL on the IMX-AUD-IO  - Optionally, connect a headphone on J15 on the MCIMX8QM-CPU Test: Power on the board. aplay -l shows the audio interface available. root@imx8qmmek:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: cs42888audio [cs42888-audio], device 0: HiFi cs42888-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: cs42888audio [cs42888-audio], device 1: HiFi-ASRC-FE (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: wm8960audio [wm8960-audio], device 0: HiFi wm8960-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: imxaudmix [imx-audmix], device 0: HiFi-AUDMIX-FE (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: imxaudmix [imx-audmix], device 1: HiFi-AUDMIX-FE (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 Play file on powered speaker via cs42888: root@imx8qmmek:~# aplay -Dhw:0,0 test.wav Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo Play file on headphone via wm8960: root@imx8qmmek:~# aplay -Dhw:1,0 test.wav i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus

Writing to a Compact flash If anybody meets an issue with MQX 3.8 (also 3.8.1, 4.0 and 4.0.1) writing to a Compact flash (/mfs/examples/cfcard), there is an error in the cfcard io driver. Compact flash can be read, but writing doesn't work. Fix for this is in the source file: c:\Freescale\Freescale MQX 3.8\mqx\source\io\pcflash\apcflash.c in function _io_apcflash_write() on line 452, change from: results = _io_apcflash_read_write_blocks(fd_ptr, info_ptr, data_ptr, num, FALSE); change to: results = _io_apcflash_read_write_blocks(fd_ptr, info_ptr, data_ptr, num, TRUE); Tested on M5329EVB and MQX 3.8.1.

i.MX27 ADS Board Video GST Encode Encode From YUV to H.264 gst-launch-0.10 filesrc location=file_in.yuv blocksize=w*h*1.5 ! \ mfw_vpuencoder codec type=std_avc framerate=fr ! filesink location=file_out.mpg Where: file_in.yuv: is the input file, a raw file. w*h*1.5: is the blocksize, it's calculated from input file dimensions: width * height * 1.5 mfw_vpuencoder: is the encoder with hardware acceleration for iMX27 std_avc: chooses the codec type for output file fr: indicates the framerate in that input file was created file_out.mpg: is the output file encoded in H.264 From Camera to H.264 gst-launch-0.10 mfw_v4lsrc ! mfw_vpuencoder codec-type=std_avc \ width=176 height=144 framerate=25 ! filesink location=test.video i.MX2x

Yoctoプロジェクト™ 101 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.MX アプリケーションプロセッサ用のYocto Projectを使用した開発のガイドです。Yocto Projectを活用してNXPリファレンスボードの作業を開始する方法を学びます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.MX アプリケーションプロセッサ用のYocto Projectを使用した開発のガイドです。Yocto Projectを活用してNXPリファレンスボードの作業を開始する方法を学びます。 i.MXアプリケーション・プロセッサ

GPISタッチセンスソリューション <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXPのタッチセンスソリューションの基本原理を紹介し、S32Kファミリに基づくリファレンスデザインをデモンストレーションします。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> NXPのタッチセンスソリューションの基本原理を紹介し、S32Kファミリに基づくリファレンスデザインをデモンストレーションします。

在 i.MX8MQ 和 i.MX8QM/QXP 上为 Yocto 项目启用 CLBlast <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> CLBlast（ https://github.com/CNugteren/CLBlast ）是一个用 C++11 编写的现代、轻量级、高性能且可调的 OpenCL BLAS 库。CLBlast 实现 BLAS 例程：对向量和矩阵进行操作的基本线性代数子程序。我在基于 Vivante GPU GC7000L 的 i.MX8MQ EVK/ i.MX8QXP MEK 和基于Vivante GPU GC7000XSVX 的i.MX8QM MEK上启用了该库。同时，我还根据https://github.com/CNugteren/CLBlast/blob/master/doc/tuning.md对其在 i.MX8MQ/8QM/8QXP 上的性能进行了调优。附件的 Yocto Recipe bb 文件基于 L4.14.98 GA 版本。 回复：在 i.MX8MQ 和 i.MX8QM/QXP 上为 Yocto 项目启用 CLBlast <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好， 路易斯·内托 我的调整结果也包含在0001-tuning-for-Vivante-OpenCL-Device-GPU.patch中。 回复：在 i.MX8MQ 和 i.MX8QM/QXP 上为 Yocto 项目启用 CLBlast <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 成功了！！ 可以分享一下你的调校结果吗？ 回复：在 i.MX8MQ 和 i.MX8QM/QXP 上为 Yocto 项目启用 CLBlast <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，路易斯·内托 您需要下载附加文件 clblast.tgz 并解压缩。然后将文件夹 clblast 复制到 /sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-support/。稍后，您可以在运行 i.MX Linux Yocto Project Setup 命令后运行“bitbake clbast”来构建它，例如“DISTRO=fsl-imx-wayland MACHINE=imx8mqevk source fsl-setup-release.sh -b imx8mqevk”。 回复：在 i.MX8MQ 和 i.MX8QM/QXP 上为 Yocto 项目启用 CLBlast <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 你好，你能告诉我如何将这一层添加到 yocto 吗？

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