Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
New SDK Generator Docs New SDK generator docs have been released. You can get it from: 1. SDK generator repo: https://bitbucket.sw.nxp.com/projects/MCUCORE/repos/mcu-sdk-generator/browse/doc  2. Gitbook: http://10.193.108.154:4000/ Here is a snapshot Getting Started With SDK Generator.md Getting Starts. It illustrates why we need sdk generator, how to install and use it. Basic concepts and working scenarios are introduced. Yaml Data Record Guide.md Illustrate yaml data record rule, syntax, concepts. It covers every aspect of the SDK data. Yaml Data Record For Project Settings.md Illustrate yaml data record syntax for project settings. Yaml Data Record Component Naming Conventions.md Illustrate SDK component naming conversation. Yaml Example Reference.md The reference index for yml/batch set demos. Release Actions Of SDK Generator.md Illustrate the release actions of SDK. SDK Docs Generation Flow.md Illustrate how to integrate SDK docs generation into sdk generator. How To Configure Release_config File.md Illustrate how to config release config yml. Frequently Asked Questions.md Frequently asked questions, still on-going, we will add more.  
View full article
NXP Wireless Charging Solution Design—Deep Dive Today, wireless charging is not only used for mobile devices but also expanding to many industrial applications. This session will provide the in-depth technical detail and guidance of the design of wireless charging transmitter and receiver. Also a review of NFC/RFID cards protection that cover both low-power and medium-power applications. Today, wireless charging is not only used for mobile devices but also expanding to many industrial applications. This session will provide the in-depth technical detail and guidance of the design of wireless charging transmitter and receiver. Also a review of NFC/RFID cards protection that cover both low-power and medium-power applications.
View full article
Example MPC5748G eMIOS BCTU ADC trigger S32DS2.1 ******************************************************************************** * Detailed Description: * * Example shows how to trigger ADC conversion on falling edge of PWM signal. * eMIOS ch1 is set to SAIC mode and a flag generated on selected edge detection * triggers BCTU channel which starts conversion of ADC1 ch9. On this channel * the board's trimmer is connected. * * EVB connection: * * J3.1 .. PA[1] - connect external PWM signal * J3.3 .. PA[2] - toggled in BCTU interrupt after ADC measurement * * ------------------------------------------------------------------------------ * Test HW: DEVKIT-MPC5748G * Maskset: 0N78S * Target : FLASH * Fsys: 160 MHz PLL * Debugger: Lauterbach * ******************************************************************************** Revision History: 1.0 Nov-5-2019 Petr Stancik Initial Version *******************************************************************************/ General
View full article
Amazon Alexa音声サービス <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Amazon Alexaは音声制御を永遠に変えました。Amazon Alexaの i.MX ベースのソリューションをご覧ください。リファレンスプラットフォーム、AVS認定システムIntegraotsを使用したソリューション、音声制御ソリューションを設計する際に考慮すべき重要な要素、およびAlexaを次世代デバイスに簡単に追加できる方法をご覧ください。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Amazon Alexaは音声制御を永遠に変えました。Amazon Alexaの i.MX ベースのソリューションをご覧ください。リファレンスプラットフォーム、AVS認定システムIntegraotsを使用したソリューション、音声制御ソリューションを設計する際に考慮すべき重要な要素、およびAlexaを次世代デバイスに簡単に追加できる方法をご覧ください。
View full article
带有CANLIN MC33907/908的FS PowerSBC资源 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MC33907/33908 是带有高速 CAN 和 LIN 收发器的电力系统基础芯片。 PN 为: 资源为: 最新版本数据表: https://www.nxp.com/docs/en/data-sheet/MC33907-MC33908D2.pdf 安全手册: https://www.nxp.com/webapp/sps/download/preDownload.jsp?render =true 硬件指南: https://www.nxp.com/webapp/sps/download/pending.jsp MPC5744P 和 MC33907/08 的安全应用: https://www.nxp.com/docs/en/application-note/AN5099.pdf 封装信息: https://www.nxp.com/docs/en/application-note/AN4388.pdf 变更信息: https://www.nxp.com/docs/en/product-change-notice/PCN16630.htm EVB 和工具: MC33908 | 安全系统基础芯片 DC/DC 高达 1.5A | 恩智浦 MPC5643L 和 MC33908 SBC 的 EVB|恩智浦 评估套件 - MC33908,带降压、升压、LIN 的安全 SBC|NXP 评估子板 - NXP MPC5744P,32位微控制器|NXP HEV/EV 和 BMS EVB 适配器板|恩智浦                            参考设计:恩智浦 - 合作伙伴简介信息 更多信息和文档,请联系当地 NXP 支持。 BRS    本文档由以下讨论生成: FS PowerSBC 与 CANLIN MC33907/908 资源 MC339078
View full article
如何使用面向动力总成和VDS应用的Green Box平台 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何借助Green Box开发工具进行面向新一代汽车动力和安全(VDS)应用的S32P2/S2器件的早期开发。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何借助Green Box开发工具进行面向新一代汽车动力和安全(VDS)应用的S32P2/S2器件的早期开发。
View full article
ハンズオンワークショップ:i.MX RTの概要とトレーニング <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、i.MX RTシリーズの概要、主要な周辺機器、i.MX RT EVKを使用したハンズオンチュートリアルを提供します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このクラスでは、i.MX RTシリーズの概要、主要な周辺機器、i.MX RT EVKを使用したハンズオンチュートリアルを提供します。
View full article
ZigBee 3.0 Adding cluster on KW41Z This document describes how to add additional cluster to the router application in the AN12061-MKW41Z-AN-Zigbee-3-0-Base-Device Application Note.   The Router application's main endpoint contains Basic, Groups, Identify and OnOff server. The steps below describe how to add two clusters to Router: Temperature Measurement server and OnOff client. Note that these changes only go as far as making the new clusters added and discoverable, no functionality has been added to these clusters. Router/app_zcl_cfg.h The first step is to update the application ZCL Configuration file to add the new clusters (OnOff Client, Temperature Measurement Server) to the Router application endpoint. The HA profile already contains few clusters but Temperature Measurement cluster was added:   /* Profile 'HA' */ #define HA_ILLUMINANCEMEASUREMENT_CLUSTER_ID (0x0400) #define HA_DEFAULT_CLUSTER_ID                (0xffff) #define HA_OTA_CLUSTER_ID                    (0x0019) #define HA_TEMPMEASUREMENT_CLUSTER_ID        (0x0402) Router/app_zcl_globals.c The OnOff client was already present in Router endpoint but made discoverable and the Temperature Measurement cluster was added and made discoverable into Router application endpoint.The clusters are added to the Input cluster list (Server side) and output cluster list (Client side) and made discoverable using DiscFlag only for the cluster list for which it is enabled. So, assuming you need to add OnOff cluster client, you would need to use add the cluster id (0x0006 for OnOff) into input cluster list (Server side of cluster) and output cluster list (Client side of the cluster) and make it discoverable for output cluster list as it is a client cluster. For temperature measurement, you need to make it discoverable for input Cluster list as below: PRIVATE const uint16 s_au16Endpoint1InputClusterList[6] = { 0x0000, 0x0004, 0x0003, 0x0006, HA_TEMPMEASUREMENT_CLUSTER_ID , 0xffff, }; PRIVATE const PDUM_thAPdu s_ahEndpoint1InputClusterAPdus[6] = { apduZCL, apduZCL, apduZCL, apduZCL, apduZCL, apduZCL, }; PRIVATE uint8 s_au8Endpoint1InputClusterDiscFlags[1] = { 0x1f }; PRIVATE const uint16 s_au16Endpoint1OutputClusterList[5] = { 0x0000, 0x0004, 0x0003, 0x0006, HA_TEMPMEASUREMENT_CLUSTER_ID, }; PRIVATE uint8 s_au8Endpoint1OutputClusterDiscFlags[1] = { 0x08 }; Now update Simple Descriptor structure (see the declaration of zps_tsAplAfSimpleDescCont and ZPS_tsAplAfSimpleDescriptor structures to understand how to correctly fill the various parameters) to reflect the input cluster and output cluster list correctly as below : PUBLIC zps_tsAplAfSimpleDescCont s_asSimpleDescConts[2] = { {    {       0x0000,       0,       0,       0,       84,       84,       s_au16Endpoint0InputClusterList,       s_au16Endpoint0OutputClusterList,       s_au8Endpoint0InputClusterDiscFlags,       s_au8Endpoint0OutputClusterDiscFlags,    },    s_ahEndpoint0InputClusterAPdus,    1 }, {    {       0x0104,       0,       1,       1,       6,       5,       s_au16Endpoint1InputClusterList,       s_au16Endpoint1OutputClusterList,       s_au8Endpoint1InputClusterDiscFlags,       s_au8Endpoint1OutputClusterDiscFlags,    },    s_ahEndpoint1InputClusterAPdus,    1 }, }; Router/zcl_options.h This file is used to set the options used by the ZCL. Enable Clusters The cluster functionality for the router endpoint was enabled: /****************************************************************************/ /*                             Enable Cluster                               */ /*                                                                          */ /* Add the following #define's to your zcl_options.h file to enable         */ /* cluster and their client or server instances                             */ /****************************************************************************/ #define CLD_BASIC #define BASIC_SERVER #define CLD_IDENTIFY #define IDENTIFY_SERVER #define CLD_GROUPS #define GROUPS_SERVER #define CLD_ONOFF #define ONOFF_SERVER #define ONOFF_CLIENT #define CLD_TEMPERATURE_MEASUREMENT #define TEMPERATURE_MEASUREMENT_SERVER Enable any optional Attributes and Commands for the clusters /****************************************************************************/ /* Temperature Measurement Cluster - Optional Attributes */ /* */ /* Add the following #define's to your zcl_options.h file to add optional */ /* attributes to the time cluster. */ /****************************************************************************/ #define CLD_TEMPMEAS_ATTR_TOLERANCE /****************************************************************************/ /* Basic Cluster - Optional Commands */ /* */ /* Add the following #define's to your zcl_options.h file to add optional */ /* commands to the basic cluster. */ /****************************************************************************/ #define CLD_BAS_CMD_RESET_TO_FACTORY_DEFAULTS /****************************************************************************/ /* OnOff Cluster - Optional Commands */ /* */ /* Add the following #define's to your zcl_options.h file to add optional */ /* commands to the OnOff cluster. */ /****************************************************************************/ #define CLD_ONOFF_CMD_OFF_WITH_EFFECT  Add the cluster creation and initialization into ZigBee Base device definitions The cluster functionality for some of the clusters (like OnOff Client) is already present on ZigBee Base Device. For Temperature Measurement cluster the functionality was added into ZigBee Base Device. /middleware/wireless/Zigbee_3_0_6.0.6/core /ZCL/Devices/ZHA/Generic/Include/base_device.h The first step was including the Temperature Measurement header files into base device header file as shown below:  #ifdef CLD_TEMPERATURE_MEASUREMENT #include "TemperatureMeasurement.h" #endif The second step was adding cluster instance (tsZHA_BaseDeviceClusterInstances) into base device Instance as shown below: /* Temperature Measurement Instance */ #if (defined CLD_TEMPERATURE_MEASUREMENT) && (defined TEMPERATURE_MEASUREMENT_SERVER) tsZCL_ClusterInstance sTemperatureMeasurementServer; #endif The next step was to define the cluster into the base device structure (tsZHA_BaseDevice) as below: #if (defined CLD_TEMPERATURE_MEASUREMENT) && (defined TEMPERATURE_MEASUREMENT_SERVER) tsCLD_TemperatureMeasurement sTemperatureMeasurementServerCluster; #endif /middleware/wireless/Zigbee_3_0_6.0.6/core/ZCL/Devices/ZHA/Generic/Include/base_device.c The cluster create function for Temperature Measurement cluster for server was called in ZigBee base device registration function:   #if (defined CLD_TEMPERATURE_MEASUREMENT) && (defined TEMPERATURE_MEASUREMENT_SERVER)    /* Create an instance of a Temperature Measurement cluster as a server */    if(eCLD_TemperatureMeasurementCreateTemperatureMeasurement(&psDeviceInfo->sClusterInstance.sTemperatureMeasurementServer,                                                    TRUE,                                                    &sCLD_TemperatureMeasurement,                                                    &psDeviceInfo->sTemperatureMeasurementServerCluster,                                                    &au8TemperatureMeasurementAttributeControlBits[0]) != E_ZCL_SUCCESS)   {       return E_ZCL_FAIL;    } #endif Router/app_zcl_task.c Temperature Measurement Server Cluster Data Initialization - APP_vZCL_DeviceSpecific_Init() The default attribute values for the Temperature Measurement clusters are initialized: PRIVATE void APP_vZCL_DeviceSpecific_Init(void) {    sBaseDevice.sOnOffServerCluster.bOnOff = FALSE;    FLib_MemCpy(sBaseDevice.sBasicServerCluster.au8ManufacturerName, "NXP", CLD_BAS_MANUF_NAME_SIZE);    FLib_MemCpy(sBaseDevice.sBasicServerCluster.au8ModelIdentifier, "BDB-Router", CLD_BAS_MODEL_ID_SIZE);    FLib_MemCpy(sBaseDevice.sBasicServerCluster.au8DateCode, "20150212", CLD_BAS_DATE_SIZE);    FLib_MemCpy(sBaseDevice.sBasicServerCluster.au8SWBuildID, "1000-0001", CLD_BAS_SW_BUILD_SIZE);    sBaseDevice.sTemperatureMeasurementServerCluster.i16MeasuredValue = 0;    sBaseDevice.sTemperatureMeasurementServerCluster.i16MinMeasuredValue = 0;    sBaseDevice.sTemperatureMeasurementServerCluster.i16MaxMeasuredValue = 0; } KW41Z31Z21Z
View full article
S32 Design Studio for Power Architecture 2017.R1 - Update 2 available       Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture 2017.R1 Update 2          What is new? S32 SDK for Power Architecture 0.9.0 BETA for MPC574x-B-C-G and MPC574xP derivatives (see attached release notes for more details) S32 SDK  Power Architecture v0.9.0  BETA Examples - "Create S32DS Project from Example" Updated version of GNU Build tools for e200 (see the release notes attached below) Support of GHS compiler in New Project Wizard - please contact GreenHills support to obtain toolchain plugin compatible with Eclipse Neon version Updated P&E Plugin (v1.7.3.201803261737) and drivers (v12.7.0) Fixed Defects • S32DS-3506 - [e200][MPC5744P] unable to connect to secured device - addressed by adding unsecure support for MPC5744P devices • S32DS-7326 - [e200][MPC5634M] Exception occurs when accessing peripheral A registers - MMU init script error is resolved by updating the script • S32DS-7991 - [e200 2017.R1] Semihosting disabling interrupts is resolved by not disabling interrupts when stepping over specific instruction • S32DS-7177 - [MPC5634M] unable to access RAM in the debug session • S32DS-7896 - [e200] default linker sections (.got2, .jsr...) are missing in the linker script file • S32DS-3681 - [S32DS E200 B170421] Project build fail with Library support = newlib, the startup.S update to add section _fini Installation instructions The update is available for online (via S32DS Eclipse Updater) or offline installation (direct download link) online installation:  go to menu "Help" -> "Install New Software..." dialog  select predefined update site "S32DesignStudio - http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_POWER_2017.R1/updatesite" select all available items and click "Next" button   offline installation:   go to S32 Design Studio for ARM product page -> Downloads section or use  direct link to download the update archive zip file Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select all available items and click "Next" button.   This will starts the update installation process. General Re: S32 Design Studio for Power Architecture 2017.R1 - Update 2 available Added tags for resolved issues in this update. GCC: CMPE200GCC-168 cmpe200gcc-181 cmpe200gcc-183 CMPE200GCC-184 Binutils: CMPE200GCC-176 Newlib: cmpe200gcc-126 cmpe200gcc-178 CMPE200GCC-170 #CMPE200GCC-180
View full article
ハンズオン・ワークショップ: MCUXpresso IDE による高度なデバッグとトレース <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MCUXpresso IDEに搭載されている高度なデバッグ機能とトレース機能について、ハンズオンクラスで詳しく説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MCUXpresso IDEに搭載されている高度なデバッグ機能とトレース機能について、ハンズオンクラスで詳しく説明します。 キネティスCortex®-Mマイクロコントローラー LPCマイクロコントローラ ソフトウェアとツール
View full article
S32 Design Studio for Arm v2.0 - Update 3 available         Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for ARM v2.0 Update 3          What is new? S32 SDK 0.8.6 EAR (Early Access Release)  for S32K142, S32K144, S32K146, S32K148)- see attached release notes for more details Installation instructions The update is available for online (via Eclipse Updater) or offline installation (direct download link) online installation:  go to menu "Help" -> "Install New Software..." dialog  select predefined update site "S32 Design Studio for ARM v2.0 - http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_ARM_2_0/com.freescale.s32arm.updatesite" select all available items and click "Next" button   offline installation:   go to S32 Design Studio for ARM product page -> Downloads section or use this direct link to download the update archive zip file Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select all available items and click "Next" button. This will starts the update installation process.
View full article
RAppID Bootloader rbf file for MPC5777C CAN communication is supported in the latest version of MPC5777C Bootloader .rbf file (attached below) + Supported UART0/eSCI_0(J20 on DB): GPIO89-90 pins(Speed: 115200b/s) + Supported  MCAN0(J5 on MB):  GPIO83-84 pins(Speed: 500Kb/s)   Tested on the dev board:   Motherboard MPC57xxMB Development Board X-MPC5777C-516DS Processor SPC5777CDMMO3 3N45H Also included is a version of the .rbf file where the delay before app start is 1 second (instead of 3 seconds) Re: RAppID Bootloader rbf file for MPC5777C Thanks mikedoidge‌ Appreciate the concise explanation... very helpful.  I'm up and running now, so thanks! Looks like I had some settings incorrect out of the box in the IDE, which is a fresh install on this machine for this project.  I did attempt to program .rbf / .srec files (via both PROGPPCNEXUS and S32DS environments) and received similar errors pertaining to memory addressing.  I see from your release notes that the bootloader occupies 0x00020000 - 0x0002FFFF.  As you can see from the PROGPPCNEXUS screen cap, I get invalid memory addresses (similar response from S32DS).  This is with both methods using NXP_MPC5777C_1x32x2048k_CFlash_highspeed.pcp algorithm, which is the default in the S32DS IDE.     Now, when I change the algorithm to NXP_MPC5777C_Cflash_Dflash_highspeed.pcp and flash your MPC5777C_S32DS_UART0_CAN0_1sec_delay.rbf file via S32DS, the rbf sticks and it appears to have worked.  I will say that I had much better luck with your 1sec delay rbf than the other native when it comes to getting the timing right between physical module reset and the RAppID BL process' reset timing idiosyncrasies.  For the benefit of others, here's where to make and verify that change in S32DS: After this, it's smooth sailing when building in Simulink and programming via USB-to-Onboard Serial (not via the PEMicro FX JTAG) onto the MPC5777C-416DS daughter card. Simulink settings below for continuity: Thanks again for your assistance! Best- Tom Re: RAppID Bootloader rbf file for MPC5777C Hi [email protected]‌, First let's clear up some confusion. There is no OpenSDA support on the MPC5777C-416DS board. The MPC57xx Motherboard does not have it either. The OpenSDA is powered by another device which would execute the OpenSDA firmware. In this scenario, when the board is connected to your PC, you would see a drive letter appear on Windows Explorer and you could drag and drop an S-record file to the the drive letter and it would be programmed to the MPC5777C device. This does not exist for this EVB. For this EVB, the programming of the application executable to the device can be done via JTAG (using the PE Multilink), serial using the USB port (there is a USB to Serial chip installed to the daughtercard for this), or CAN. For the serial or CAN communication methods, the RAppID Bootloader is required. The RAppID Bootloader tool is integrated with MBD Toolbox, so you won't need to install it separately. To use the RAppID Bootloader, you must first program the MPC5777C.rbf file. It is an S-record file so it can be programmed easily with the PE Multilink. You can use S32 Design Studio for Power Architecture for this. Once this SREC has been programmed, then the RAppID Bootloader GUI will communicate via either the Serial or CAN connection to the EVB (which is now executing the MPC5777C.rbf algorithm). You should be able to program your application executable using the RAppID Bootloader GUI, assuming you have the correct port/communication speed selected. Since the file attached to this document is configured for pins 89 and 90 for serial, and this is also what is routed on the EVB, there should be no issue using this file on the MPC5777C-416DS. Hope that helps. Best Regards, Mike Re: RAppID Bootloader rbf file for MPC5777C mikedoidge‌ Hoping you could point us in the right direction.. Wondering if there is an OpenSDA rbf file available for the setup below...  We are using the following:   MPC57xx Motherboard Rev C MPC5777C-416DS  Daughtercard S32DS Environment PE Micro Multilink Universal FX connected at JTAG J31 MBD Toolbox for Matlab / Simulink Using the files for the 5777C that you attached above, the boot loader doesn't connect via the FX device.  If we use one of the available SDA rbf files for MPC574xP with OpenSDA, we seem to be able to at least talk to the target and flash a boot loader. Ultimately the goal is to be able to integrate with the upcoming MBDT 3.2.0 release with this development setup. Thx in advance. Tom
View full article
NFCアンテナ設計 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> はじめに NFCアンテナの設計に関するすべての有用な情報を含む1つのページを作成しようとしています。私は更新を続け、何か役に立つものを見つけたらこのページに情報を追加します。 トレーニング まず、NFCアンテナの設計に関する6つのウェビナーがあります。NFCのアンテナ設計を開始する前に、良いトレーニングになります。 トレーニング&イベント |NXP (「アンテナ設計」を検索) アプリケーション・ノート AN11740:PN5180アンテナ設計ガイド AN11706 : PN7462AU アンテナ設計ガイド AN11019 : CLRC663、MFRC630、MFRC631、SLRC610アンテナ設計ガイド AN11755 : PN7150 アンテナ設計およびマッチングガイド AN11564 : PN7120 アンテナ設計およびマッチングガイド AN11741:DPCを使用してアンテナを設計する方法 AN11535:MiniVNAを用いたNFCおよびリーダライタICアンテナの測定とチューニング ツール NFCアンテナ設計ハブ
View full article
eIQ Sample Apps - TfLite Lab 4[1] This Lab 4 explains how to get started with TensorFlow Lite application demo on i.MX8 board using Inference Engines for eIQ Software. eIQ Sample Apps - Overview eIQ Sample Apps - Introduction Get the source code available on code aurora: TensorFlow Lite MobileFaceNets MIPI/USB Camera Face Detection Using OpenCV   This application demo uses Haar Feature-based Cascade Classifiers for real time face detection. The pre-trained Haar Feature-based Cascade Classifiers for face, named as XML, is already contained in OpenCV. The XML file for face is stored in the opencv/data/haarcascades/ folder. It is also put on code aurora. Read Face Detection using Haar Cascades for more details. TensorFlow Lite implementation for MobileFaceNets  The MobileFaceNets is re-trained with a smaller batch size and input size to get a higher performance on a host PC. The trained model is loaded as a source file in this demo. Setting Up the Board Step 1 - Download the demo from eIQ Sample Apps and put it in /opt/tflite folder. Then enter the src folder: root@imx8mmevk:~# cd /opt/tflite/examples-tflite/1-example/src/ root@imx8mmevk:/opt/tflite/examples-tflite/1-example/src# This folder should include these files: . ├── face_detect_helpers.cpp ├── face_detect_helpers.h ├── face_detect_helpers_impl.h ├── face_recognition.cpp ├── face_recognition.h ├── haarcascade_frontalface_alt.xml ├── Makefile ├── mfn.h ├── profiling.h └── ThreadPool.h Step 2 - Compile the source code on the board: root@imx8mmevk:/opt/tflite/examples-tflite/1-example/src# make Step 3 - Run the demo: root@imx8mmevk:/opt/tflite/examples-tflite/1-example/src# ./FaceRecognition -c 0 -h 0.85 NOTE: -c is used to specify the camera index. '0' means the MIPI/USB camera is mounted on /dev/video0. -h is a threshold for the prediction score. Step 4 - Add a new person to the face data set.  When the demo is running, it will detect one biggest face at real time. Once the face is detected, you can click keyboards on the right of GUI to input the new person's name. Then, click 'Add new person' to add the face to data set.  In brief, 1. Detect face. 2. Input new person's name. 3. Click 'Add new person'. NOTE: Once new faces are added, it will create a folder named 'data' in current directory. If you want to remove the new face from the data set, just delete it in 'data'.
View full article
iMX8X Adjust display brightness contrast saturation In this doc will show how to adjust display brightness/contrast/saturation by using i.MX8  Display Controller (DC) Subsystem.   HW: i.MX8QXP MEK board SW: Linux 4.14.98_2.0.0 BSP release.   See i.MX 8DualXPlus/8QuadXPlus Applications Processor Reference Manual, Rev. 😧 This kind Matrix total number is 5 , that is 0/1/4/5/9. In this doc using Matrix0 to adjust whole display brightness/contrast/saturation. Matrix0 unit position is located between FramGen unit and Tcon unit, that means using Matrix0 will impact on the whole display contents. Note, this Matrix is applied on RGB color space.    The Matrix is consist of two parts: and  You can program any value into register of A11 to A44 and C1 to C4, Matrix will applied on input RGB data, then output RGB data will changed as you want. In this way, we can change the display brightness/contrast/saturation. The Matrix entry from A11 to A44, their register format is same as below: Each register entry of A11 to A44 , total 13 bit, bit 12 is symbol bit , bit 11 and bit 10 is integer bit, bit 9 to bit 0 is floating point bit. The Matrix entry from C1 to C4, their format is same as below: Each register entry of C1 to C4, total 13 bit, bit 12 is symbol bit, others are integer bit. Now let us choose the matrix that will be used for adjust brightness/contrast/saturation. See this link  https://docs.rainmeter.net/tips/colormatrix-guide/ So we can set matrix as below to change brightness/contrast/saturation   A11=c(sr+s)   A12=c(sg)    A13=c(sb)   A21=c(sb)     A22=c(sg+s)  A23=c(sb)   A31=c(sr)     A32=c(sg)    A33=c(sb+s)   C1=C2=C3=t+b   b as brightness , range[-1.0, 1.0], zero means no change , >0 will increases brightness, <0 will reduce brightness. c as contrast, range [0,2.0) , default is 1.0 , >1.0 is increase , <1.0 is reduce. s is saturation, range [0,1.0], default is 1.0.  Other matrix entry is related to alpha, in this doc not change it, just keep them as zero.   Note here sr,sb,sg value will depend on lumR/ lumG/ lumB constant value you choose, this value may depend on different color standard.   Due to each matrix value is floating point number, and in this doc , i.MX8X run Linux OS. So you can choose do floating point operation in user space program, then pass related register value into kernel space , let driver write them into register. But in this doc, to make Linux kernel driver more simple, I will convert floating point operation into integer operation , then user space app just pass brightness/contrast/saturation value into kernel space, then kernel driver to do left operation in kernel space. So 1024*c and 1024*s is integer number that user space app will passed into kernel space. And in kernel space could be do left integer number operation, then write register value. The kernel patch 8qxp_4.14.98_brightness_contrast_saturation.diff could be used on 4.14.98_2.0.0 BSP release. Test usage, need used one patch that for proptest which from libdrm test case, see 8qxp_prop_test.diff, recompile the proptest case. root@imx8qxpmek:~# ./proptest     //list current drm property CRTC 32         42 bringhtness:                 flags: range                 values: 0 131071                 value:0x0         43 contrast:                 flags: range                 values: 0 2048                 value:0x400         44 saturation:                 flags: range                 values: 0 1024                 value:0x400         45 update:                 flags: range                 values: 0 1                 value:0x0 I add four drm property , brightness, contrast, saturation, update. The “update property” should be set as 1 at last, otherwise kernel space will not update related property. Reference API usage ( in 8qxp_prop_test.diff) +     drmModeObjectSetProperty(fd_rend, obj_id, obj_type, 42, b_int); +     drmModeObjectSetProperty(fd_rend, obj_id, obj_type, 43, c_int); +     drmModeObjectSetProperty(fd_rend, obj_id, obj_type, 44, s_int); +     drmModeObjectSetProperty(fd_rend, obj_id, obj_type, 45, 1);    //run cmd as below , will ask you input related brightness/contrast/saturation value , then will get result in display root@imx8qxpmek:~# ./proptest 32 crtc 45 1   input brightness [-1,1] 0.3 input contrast, >1.0 or <1.0 1.2 input saturation, [0,1] 0.3 brightness 0.300000  0x133 from [-1,1] percent contrast  1.200000  0x4cc >1.0 or <1.0 saturation 0.300000 0x133  from 0.0 to 1.0 Known Issue: For demo this feature , I need run proptest and weston at same time. Due to the set property drm ioctl default allowed by DRM master and DRM control client. But 4.14. kernel, removed the DRM control device node, so I changed to open drm render node fd, and allow DRM render client to using set property drm ioctl.  This is just a workaround, you may not use it. Reference: 1.https://www.nxp.com/docs/en/reference-manual/IMX8DQXPRM.pdf  2.https://docs.rainmeter.net/tips/colormatrix-guide/ i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Re: iMX8X Adjust display brightness contrast saturation I tried. it works as expected. Thanks for your work 
View full article
Suite56 ツールのダウンロード <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 現在、DSP56300とDSP5672xにはロードマップがなく、NXPのホームページではSuite56ツールが削除されています。しかし、ツールを使用する必要があるお客様がいますので、お客様が無料でダウンロードできるように、ここにツールを配置しました。これには、asm56300.exeアセンブリコンパイラ、gds56300.exeデバッガーが含まれています。 現在、DSP56300ファミリとDSP5672xファミリの両方でアセンブリ言語のみをサポートしており、C言語はサポートしていません。お客様がCコンパイラを使用したい場合は、タスクCから3番目の部分のCコンパイラがあります。 GDS56300.exeはWiggler(パラレルコマンドコンバータ)デバイスのみをサポートしており、USBタイプのデバイスはサポートしていません。 元の添付ファイルは次の場所に移動しました DSP56300Tools.rar Re: Suite56 tools downloading <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは。DSP56300Tools.rarへのリンクが利用できません。バックアップを私のメールアドレスに送っていただけますか? よろしくお願いいたします。[email protected]
View full article
DPM マルチコア GHS614 の例 MPC5748G <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** *詳細な説明: * この例では、lauterbach マルチコアプロジェクトの使用方法を示しています。 ※MPC5748Gコア(z4a、z4b、z2)はすべてアクティブです。コアz4aを搭載したマイクロブーツ。 * z4a では、マイクロ設定が実行され、その後 Core_Init() で実行されます。機能 ※他の2コア(Z4B、Z2)で開始します。 *例には、Lauterbachマルチコア(マルチパワービュー)サンプルスクリプトも含まれます * + T32設定ファイル * ------------------------------------------------------------------------------ *テストHW:MPC57xx MB + *マスクセット:1N81M * 対象:SRAM * Fsys:160 MHz PLL * ******************************************************************************** 改訂履歴: 1.0 2014年10月29日 b21190(VLNA Peter) 初期バージョン 1.1 2014年11月20日 b21190(VLNA Peter) Cut2.0 用修正 1.2 2014年11月20日 b21190(Vlna Peter) 起動時にSWT_0の無効化を追加 1.3 Feb-12-2016 b21190(Vlna Peter) マルチコアプロジェクト用に修正 *******************************************************************************/ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** *詳細な説明: * この例では、lauterbach マルチコアプロジェクトの使用方法を示しています。 ※MPC5748Gコア(z4a、z4b、z2)はすべてアクティブです。コアz4aを搭載したマイクロブーツ。 * z4a では、マイクロ設定が実行され、その後 Core_Init() で実行されます。機能 ※他の2コア(Z4B、Z2)で開始します。 *例には、Lauterbachマルチコア(マルチパワービュー)サンプルスクリプトも含まれます * + T32設定ファイル * ------------------------------------------------------------------------------ *テストHW:MPC57xx MB + *マスクセット:1N81M * 対象:SRAM * Fsys:160 MHz PLL * ******************************************************************************** 改訂履歴: 1.0 2014年10月29日 b21190(VLNA Peter) 初期バージョン 1.1 2014年11月20日 b21190(VLNA Peter) Cut2.0 用修正 1.2 2014年11月20日 b21190(Vlna Peter) 起動時にSWT_0の無効化を追加 1.3 Feb-12-2016 b21190(Vlna Peter) マルチコアプロジェクト用に修正 *******************************************************************************/
View full article
利用人脸识别技术实现新一代无摩擦界面 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如今,人们面临着太多的选择,尤其是那些可以轻松包含 50 多种功能设置的所谓智能设备。由于大多数人仅使用几个首选设置,本课程向产品经理、UI 设计师和工程师展示了如何利用 NXP 开箱即用的基于 Face Rec 的无摩擦接口生产级平台,快速为设备(如家用电器、家庭舒适系统、警报/安全/安保面板以及多种类型的工业设备)添加真正无缝的接口。通过根据过去的使用情况识别您是谁以及您的喜好,当今的智能机器可以定制其界面以满足最终消费者的个性化需求(包括控制访问),从而显著提高客户满意度。无需 Wi-Fi 和/或云连接即可将您的界面设计提升到一个新的水平! <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如今,人们面临着太多的选择,尤其是那些可以轻松包含 50 多种功能设置的所谓智能设备。由于大多数人仅使用几个首选设置,本课程向产品经理、UI 设计师和工程师展示了如何利用 NXP 开箱即用的基于 Face Rec 的无摩擦接口生产级平台,快速为设备(如家用电器、家庭舒适系统、警报/安全/安保面板以及多种类型的工业设备)添加真正无缝的接口。通过根据过去的使用情况识别您是谁以及您的喜好,当今的智能机器可以定制其界面以满足最终消费者的个性化需求(包括控制访问),从而显著提高客户满意度。无需 Wi-Fi 和/或云连接即可将您的界面设计提升到一个新的水平! i.MX 应用处理器 Power Architecture®处理器
View full article
Linux L4.14.98_2.0.0_GA; SDK2.5.2_8QXP/8QM_PostGA, SDK2.5.1_7ULP_GA3 Release Announcement The Linux L4.14.98_1.0.0_GA; and SDK2.5 for 8QM/8QXP Post GA, SDK2.5.1 for 7ULP GA3 release are now available. Linux on IMX_SW web page, Overview -> BSP Updates and Releases -> Linux L4.14.98_2.0.0 SDK on https://mcuxpresso.nxp.com Files available: Linux:  # Name Description 1 imx-yocto-L4.14.98_2.0.0_ga.zip L4.14.98_2.0.0 for Linux BSP Documentation. Includes Release Notes, User Guide. 2 L4.14.98_2.0.0_ga_images_MX6QPDLSOLOX.zip i.MX 6QuadPlus, i.MX 6Quad, i.MX 6DualPlus, i.MX 6Dual, i.MX 6DualLite, i.MX 6Solo, i.MX 6Solox Linux Binary Demo Files 3 L4.14.98_2.0.0_ga_images_MX6SLLEVK.zip i.MX 6SLL EVK Linux Binary Demo Files 4 L4.14.98_2.0.0_ga_images_MX6UL7D.zip i.MX 6UltraLite EVK, 7Dual SABRESD, 6ULL EVK Linux Binary Demo Files 5 L4.14.98_2.0.0_ga_images_MX7DSABRESD.zip i.MX 7Dual SABRESD Linux Binary Demo Files  6 L4.14.98_2.0.0_ga_images_MX7ULPEVK.zip i.MX 7ULP EVK Linux Binary Demo Files  7 L4.14.98_2.0.0_ga_images_MX8MMEVK.zip i.MX 8MMini EVK Linux Binary Demo Files  8 L4.14.98_2.0.0_ga_images_MX8MQEVK.zip i.MX 8MQuad EVK Linux Binary Demo files 9 L4.14.98_2.0.0_ga_images_MX8QMMEK.zip i.MX 8QMax MEK Linux Binary Demo files 10 L4.14.98_2.0.0_ga_images_MX8QXPMEK.zip i.MX 8QXPlus MEK Linux Binary Demo files 11 imx-scfw-porting-kit-1.2.tar.gz System Controller Firmware (SCFW) porting kit of L4.14.98_2.0.0 12 imx-aacpcodec-4.4.5.tar.gz Linux AAC Plus Codec v4.4.5 13 VivanteVTK-v6.2.4.p4.1.7.8.tgz Vivante Tool Kit v6.2.4.p4.1.7.8   SDK: On https://mcuxpresso.nxp.com/, click the Select Development Board, EVK-MCIMX7ULP//MEK-MIMX8QM/MEK-MIMX-8QX to customize the SDK based on your configuration then download the SDK package.  Target board: MX 8 Series MX 8QuadXPlus MEK Board MX 8QuadMax MEK Board MX 8M Quad EVK Board MX 8M Mini EVK Board MX 7 Series MX 7Dual SABRE-SD Board MX 7ULP EVK Board MX 6 Series MX 6QuadPlus SABRE-SD and SABRE-AI Boards MX 6Quad SABRE-SD and SABRE-AI Boards MX 6DualLite SDP SABRE-SD and SABRE-AI Boards MX 6SoloX SABRE-SD and SABRE-AI Boards MX 6UltraLite EVK Board MX 6ULL EVK Board MX 6ULZ EVK Board MX 6SLL EVK Board What’s New/Features: Please consult the Release Notes.   Known issues For known issues and more details please consult the Release Notes.   More information on changes of Yocto, see: README: https://source.codeaurora.org/external/imx/imx-manifest/tree/README?h=imx-linux-sumo ChangeLog: https://source.codeaurora.org/external/imx/imx-manifest/tree/ChangeLog?h=imx-linux-sumo# i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano i.MX6DL i.MX6Dual i.MX6DualPlus6QuadPlus i.MX6Quad i.MX6SoloX i.MX6UL i.MX7Dual i.MX7ULP Linux Re: Linux L4.14.98_2.0.0_GA; SDK2.5.2_8QXP/8QM_PostGA, SDK2.5.1_7ULP_GA3 Release Announcement I figured out uuu is the future of mfgtools. Please follow the thread to get a complete picture. https://community.nxp.com/message/1270236?commentID=1270236&et=watches.email.thread#comment-1270236  Re: Linux L4.14.98_2.0.0_GA; SDK2.5.2_8QXP/8QM_PostGA, SDK2.5.1_7ULP_GA3 Release Announcement Is there a corresponding mfgtool package to flash images from Linux 4.14.98? The previous version doesn't work for the latest images.
View full article
ApexCVライブラリ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> インデックス | 前へ | 次に (マイビデオで視聴)
View full article