Multi Source Translation Content

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

Multi Source Translation Content

ディスカッション

ソート順:
例MPC5777C-eTPU_GPIO_test GHS714 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** *詳細な説明: * 簡単な例として、eTPU エンジン B チャネル 0/1 を GPO/GPI 用に設定します。そうです *これらのピンをワイヤーで接続する必要があります。出力波はeTPU GPIOによって生成されます ※出力機能、入力はfs_etpu_gpio_input_immed機能で読み出されます *現在のピン状態のみをラッチします。ピンの履歴は ISR に表示されます。 * *注:IGFモジュールを構成する必要があり、そうしないと入力が通過しません * eTPUモジュールへ。 * * ------------------------------------------------------------------------------ ※テストHW:MPC5777C-512DS Rev.A + MPC57xx マザーボード Rev.C * MCU:PPC5777CMM03 2N45H CTZZS1521A * Fsys: PLL1 = core_clk = 264MHz, PLL0 = 192MHz *デバッガ:Lauterbach Trace32 * 対象:internal_FLASH *端末:19200-8-パリティなし-1ストップビット-eSCI_Aのフロー制御なし ※EVB接続:ETPUB0(PortR P25-1) ---> ETPUB1(PortR P25-0)をワイヤーで> * ******************************************************************************** <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** *詳細な説明: * 簡単な例として、eTPU エンジン B チャネル 0/1 を GPO/GPI 用に設定します。そうです *これらのピンをワイヤーで接続する必要があります。出力波はeTPU GPIOによって生成されます ※出力機能、入力はfs_etpu_gpio_input_immed機能で読み出されます *現在のピン状態のみをラッチします。ピンの履歴は ISR に表示されます。 * *注:IGFモジュールを構成する必要があり、そうしないと入力が通過しません * eTPUモジュールへ。 * * ------------------------------------------------------------------------------ ※テストHW:MPC5777C-512DS Rev.A + MPC57xx マザーボード Rev.C * MCU:PPC5777CMM03 2N45H CTZZS1521A * Fsys: PLL1 = core_clk = 264MHz, PLL0 = 192MHz *デバッガ:Lauterbach Trace32 * 対象:internal_FLASH *端末:19200-8-パリティなし-1ストップビット-eSCI_Aのフロー制御なし ※EVB接続:ETPUB0(PortR P25-1) ---> ETPUB1(PortR P25-0)をワイヤーで> * ******************************************************************************** 日時:例MPC5777C-eTPU_GPIO_test GHS714 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> こんにちは、次の手順に従って、コミュニティスペースまたは新しいケースに新しいスレッドを作成してください。 https://community.nxp.com/docs/DOC-329745 日時:例MPC5777C-eTPU_GPIO_test GHS714 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 私は2つのケースで試してみました: - SDADC2 の ETPUA_15 チャネル - SDADC1 の ETPUA_9 チャネル。 ピンステートは常に 0 です。 日時:例MPC5777C-eTPU_GPIO_test GHS714 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 申し訳ございませんが、ETPUチャンネルはETPUA_15
記事全体を表示
MRFX Design Challenge Winners! NXP received a number of creative submissions over the course of the MRFX Design Challenge. We appreciate the enthusiasm from the community as designers were hard at work on their RF projects. Now is the moment everyone's been waiting for as NXP proclaims the MRFX Design Challenge winners. First Place Winner  Russell Kendrick | Bio + Full Project Description Project Video: MRFX1K80H 50 MHz Project Brief This amplifier is intended to be driven with a modern transceiver with 100 watts output on 50 MHz. To protect the MRFX1K80H from overdrive a series of RF pads are used to reduce the input to the proper level. The input matching is accomplished by using a 9:1 conventional RF transformer formed on an Amidon BN 61-202 core. An 82 nH inductance is in series with the high impedance winding of the transformer. This arrangement yielded an input match of 1.3:1 SWR over the entire 6-meter Amateur band when measured without the pads. Shunt gate resistance is used to prevent oscillation at low frequencies. This is the same approach used in the 27 MHz test circuit from NXP. Bias will be supplied by a DAC driven by the microcontroller that will manage the finished amplifier Second Place Winner        Floris Roosen | Bio                                                                         Project Video: Roosen Single-Ended Broadband (87-110 MHz) RF Design         Third Place Winner Mike Mysliwiec | Bio Project Video: 2xMRFX1K80H 1.8-54 MHz HF Amplifier   Overview  NXP is hosting an RF power amplifier design contest. Applicants will record a video of their power amplifier/demo using NXP’s new 65V LDMOS 1800 W RF Power transistor, MRFX1K80H The contest is open to students, professional engineers, companies or individuals Key Dates Contest kick-off: October 30, 2017 Submit a video (3-5 minutes in length) no later than Friday, January 26, 2018, by sending a link to any video website, such as YouTube, YouKu or others to [email protected] Results will be announced on Monday, February 12, 2018 Prizes • 1st prize: $3,000 cash award + 15 MRFX1K80H samples. Showcase designer bio and video in an NXP blog • 2nd prize: $1,000 cash award + 10 MRFX1K80H samples • 3rd prize: $500 cash award + 10 MRFX1K80H samples The prize amounts are before tax All accepted videos will be posted on www.nxp.com/videos  Judging Criteria How to enter the competition Please click on the link below for the latest details and to access the MRFX Design Challenge page www.nxp.com/MRFXdesign  Communications Infrastructure
記事全体を表示
Build Manufacturing Firmware   The mfgtool is the tool download the images to i.MX series of applications processors. It’s convenient and easy use to download the images to your board. About its introductions, work flow and use guide you can see details in the Document file of mfgtool. If customers use our reference boards, they can directly use the default mfgtools we supply for every version BSP and board. But when customers design board and do porting with our i.MX series processors. As they do many changes from our reference board, they need to rebuild the images for their board and for the download tool mfgtool. In the old version BSP, take the L3.0.35_4.1.0_130816 version as an example. When finishing porting the BSP for design board. Run the following command line to generate the manufacturing firmware. ./ltib --profile config/platform/imx/updater.profile --preconfig config/platform/imx/imx6q_updater.cf --continue –batch For android BSP Android4.2.2, one can use the follow command: make distclean make mx6dl_sabresd_mfg_config make In the newest BSP, for linux BSP in yocto use the command: $ bitbake fsl-image-mfgtool-initramfs For the newest android BSP, the command” make mx6dl_sabresd_mfg_config” can not use anymore. So how to get the \Profiles\Linux\OS Firmware\firmware\u-boot-imx6dlsabresd_sd.imx? The easiest way that you can use the u-boot you build for your board, and in the newest BSP, mfgtool can use the same u-boot with the normal u-boot for your board. You do not need to build the u-boot for mfgtool separately. They can use the same one. Hope this can do some help for you. Re: Build Manufacturing Firmware This says for the newest BSP you don't need a mfg version of U-Boot and can use the normal U-Boot. Can you clarify the version of "newest BSP". I am using Android N7.1.2 for iMX6  (U-Boot is u-boot-2017.03, kernel is 4.9.17). Will this version support using same U-boot for both normal and MFG? Thanks, Bruno
記事全体を表示
Example MPC5777C-eQADC_Simple GHS714 ******************************************************************************** * Detailed Description: * Initializes eQADC module and cyclically converts chosen channel, displaying * it into terminal window. * User could connect EVB pot's wiper to pin header W (see below) to see valid * conversion result. * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * 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:  For ADC: J53-1 (EVB pot's wiper) --> PW7  - ANB16 *                                                       PW8  - ANB17 *                                                       PW9  - ANB18 *                                                       PW10 - ANB19 ******************************************************************************** ******************************************************************************** * Detailed Description: * Initializes eQADC module and cyclically converts chosen channel, displaying * it into terminal window. * User could connect EVB pot's wiper to pin header W (see below) to see valid * conversion result. * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 2N45H CTZZS1521A * 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:  For ADC: J53-1 (EVB pot's wiper) --> PW7  - ANB16 *                                                       PW8  - ANB17 *                                                       PW9  - ANB18 *                                                       PW10 - ANB19 ********************************************************************************
記事全体を表示
ラボ・ガイド - Arm® TrustZone®およびMCUXpressoソフトウェアとツールを使用したセキュアなアプリケーションの開発 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> セキュア/非セキュア・アプリケーションを作成し、セキュアCortex-M33 NXPデバイスでデバッグする方法をご紹介します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> セキュア/非セキュア・アプリケーションを作成し、セキュアCortex-M33 NXPデバイスでデバッグする方法をご紹介します。 i.MXアプリケーション・プロセッサ キネティスCortex®-Mマイクロコントローラー LPCマイクロコントローラ ソフトウェアとツール
記事全体を表示
How to distinguish overflow & underflow interrupt in MCB mode of EMIOS.pdf General
記事全体を表示
i.MX RTによる音声ソリューション <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MCU Alexa Voiceソリューションの概要では、機能、アーキテクチャについて説明し、コストと使いやすさの利点を提示します。また、Wi-Fiを使用してAlexaをオンボードするOut-of-Box Experienceと、費用対効果の高い遠距離実装を使用してAlexaと対話するエクスペリエンスも紹介します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MCU Alexa Voiceソリューションの概要では、機能、アーキテクチャについて説明し、コストと使いやすさの利点を提示します。また、Wi-Fiを使用してAlexaをオンボードするOut-of-Box Experienceと、費用対効果の高い遠距離実装を使用してAlexaと対話するエクスペリエンスも紹介します。 i.MXアプリケーション・プロセッサ
記事全体を表示
EMIOS.pdfのMCBモードでオーバーフロー割り込みとアンダーフロー割り込みを区別する方法 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 全般
記事全体を表示
eIQ CMSIS-NN マイコン用ポーティングガイド MCUXPresso SDKパッケージに含まれる i.MX RTデバイス用のeIQ CMSIS-NNソフトウェアは、一部のLPCおよびKinetisデバイスだけでなく、RTファミリの他のマイクロコントローラ・デバイスにも移植できます。 非常に一般的な質問は、モデルの推論をサポートするプロセッサは何かということですが、その答えは、推論とは単に何百万もの多重計算と累積数学計算(ニューラルネットワークを処理する際の主要な操作)を行うことを意味し、これはほとんどすべてのMCUまたはMPUが実行できるということです。推論を行うために特別なハードウェアやモジュールは必要ありません。ただし、コアクロック速度が速く、メモリが高速であるため、推論時間を大幅に短縮できます。特定のモデルを特定のデバイスで実行できるかどうかの判断は、以下に基づいて行われます。 推論の実行にはどのくらいの時間がかかりますか。同じモデルを、性能の低いデバイスで実行するには、はるかに長い時間がかかります。許容される最大推論時間は、特定のアプリケーションと特定のモデルによって異なります。 重み、モデル自体、推論エンジンを保存するのに十分な不揮発性メモリがあるかどうか。 中間計算と出力を追跡するのに十分なRAMはありますか。 添付のガイドでは、CMSIS-NN 推論エンジンを LPC55S69 ファミリに移植する方法について説明します。同様の手順をeIQを他のマイクロコントローラデバイスに移植するためにも実行できます。このガイドは、他のデバイスでのeIQの探索に関心のあるユーザー向けのリファレンスとして提供されていますが、現時点では、eIQの一部としてMCU用のCMSIS-NNで公式にサポートされているのはRT1050およびRT1060のみです。 これらの他のeIQ移植ガイドも興味深いかもしれません。 マイコン用グローポーティングガイド RT685 の TensorFlow Lite 移植ガイド i.MX RT
記事全体を表示
S32DS for Vision - list of HOWTOs Installation & Activation HOWTO: Activate S32 Design Studio  HOWTO: Install Lauterbach TRACE32 debugger plug-in into S32 Design Studio  Create a New Project  HOWTO: Create APEX2 Project From Example in S32DS for Vision  HOWTO: Create An ISP Project From Example in S32DS for Vision  HOWTO: Create A53 Linux Project in S32DS for Vision  HOWTO: Create An ISP Project From Existing VSDK Graph in S32DS for Vision  HOWTO: Create A New Makefile Project With Existing Code From NXP Vision SDK Example Project   HOWTO: Build a Project and Setup a Debug Configuration for debugging in S32 Design Studio  HOWTO: Create A53 APEX2 and/or ISP Linux Project in S32DS for Vision DDR Configuration & Validation and Stress Test Tools HOWTO: Use DDR Configuration and Validation Tool  HOWTO: Use DDR Stress Test Tool  Hardware Setup HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP HOWTO: Prepare and boot S32V234 EVB from eMMC  HOWTO: Setup static IP address for S32 debug probe  Debugging HOWTO: Setup S32V234 EVB for debugging with S32DS for Vision and Linux BSP  HOWTO: S32V234-EVB debugging with Linux and gdbserver on target machine  HOWTO: Start Debug on an ISP Application Project with S32 Debugger and S32 Debug Probe  HOWTO: Start Debug on an APEX2 Application Project with S32 Debugger and S32 Debug Probe  Debugging the Startup Code with Eclipse and GDB | MCU on Eclipse   VSDK HOWTO: Change Vision SDK root in S32DS for Vision  HOWTO: Create A New Makefile Project With Existing Code From NXP Vision SDK Example Project  HOWTO: Prepare A SD Card For Linux Boot Of S32V234-EVB Using BSP From VSDK  Linux HOWTO: S32V234 EVB Linux - Static IP address configuration  HOWTO: S32V234 EVB Linux - DHCP IP address setup  HOWTO: Prepare A SD Card For Linux Boot Of S32V234-EVB Using BSP From VSDK  HOWTO: Access Linux BSP file system on S32V234-EVB from S32DS for Vision HOWTO: Setup A Remote Linux Connection in S32DS for Vision  General Usage HOWTO: S32 Design Studio Command Line Interface  HOWTO: Add user example into S32DS  HOWTO: Generate S-Record/Intel HEX/Binary file  HOWTO: Update S32 Design Studio  Troubleshooting Help! I just relaunched S32DS for Vision and my visual graph is collapsed!  Help! I just updated to new version of S32DS and now my projects have errors and I can't build!  Troubleshooting: PEmicro Debug Connection: Target Communication Speed  Troubleshooting: Indexer errors on header file  S32 Design Studio Offline activation issue hot fix  https://community.nxp.com/docs/DOC-345238  General
記事全体を表示
NXP Tech Session - セキュアな接続の確立の民主化 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ウェビナーの録画を見る <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ウェビナーの録画を見る QNの
記事全体を表示
eIQ Sample Apps - Object Recognition using OpenCV DNN This Lab 3 explains how to get started with OpenCV DNN applications demos on i.MX8 board using eIQ ™ ML Software Development Environment. eIQ Sample Apps - Overview eIQ Sample Apps - Introduction Get the source code available on code aurora: OpenCV DNN example - File-Based and MIPI Camera OpenCV Inference The OpenCV offers a unitary solution for both neural network inference (DNN module) and classic machine learning algorithms (ML module). Moreover, it includes many computer vision functions, making it easier to build complex machine learning applications in a short amount of time and without having dependencies on other libraries. The OpenCV DNN model is basically an inference engine. It does not aim to provide any model training capabilities. For training, one should use dedicated solutions, such as machine learning frameworks. The inference engine from OpenCV supports a wide set of input model formats: TensorFlow, Caffe, Torch/PyTorch. Comparison with Arm NN Arm NN is a library deeply focused on neural networks. It offers acceleration for Arm Neon, while Vivante GPUs are not currently supported. Arm NN does not support classical non-neural machine learning algorithms. OpenCV is a more complex library focused on computer vision. Besides image and vision specific algorithms, it offers support for neural network machine learning, but also for traditional non-neural machine learning algorithms. OpenCV is the best choice in case your application needs a neural network inference engine, but also other computer vision functionalities. Setting Up the Board Step 1 - Create the following folders and grant them permissions as it follows: root@imx8mmevk:# mkdir -p /opt/opencv/model root@imx8mmevk:# mkdir -p /opt/opencv/media root@imx8mmevk:# chmod 777 /opt/opencv Step 2 - To easily deploy the demos to the board, get the boards IP address using ifconfig command, then set the IMX_INET_ADDR environment variable as it follows: $ export IMX_INET_ADDR= Step 3 - In the target device, export the required variables: root@imx8mmevk:~# export LD_LIBRARY_PATH=/usr/local/lib root@imx8mmevk:~# export PYTHONPATH=/usr/local/lib/python3.5/site-packages/   Setting Up the Host Step 1 - Download the application from eIQ Sample Apps. Step 2 - Get the models and dataset. The following command-line creates the needed folder structure for the demos and retrieves all needed data and model files for the demo: $ mkdir -p model $ wget -qN https://github.com/diegohdorta/models/raw/master/caffe/MobileNetSSD_deploy.caffemodel -P model/ $ wget -qN https://github.com/diegohdorta/models/raw/master/caffe/MobileNetSSD_deploy.prototxt -P model/   Step 3 - Deploy the built files to the board: $ scp -r src/* model/ media/ root@${IMX_INET_ADDR}:/opt/opencv OpenCV DNN Applications This application was based on: SSD: Single Shot MultiBox Detector. Caffe SSD Implementation. 1 - OpenCV DNN example: File-Based The folder structure must be equal to: ├── file.py ├── camera.py ├── media └── ... ├── model │├── MobileNetSSD_deploy.caffemodel │└── MobileNetSSD_deploy.prototxt This example runs a single picture for example, but you pass as many pictures as you want and save them inside media/ folder. The application tries to recognize all the objects in the picture. Step 1 - For copying new images to the media/ folder: root@imx8mmevk:/opt/opencv/media# cp .   Step 2 - Run the example image: root@imx8mmevk:/opt/opencv# ./file.py  NOTE: If GPU is available, the example shows: [INFO:0] Initialize OpenCL runtime This demo runs the inference using a Caffe model to recognize a few type of objects for all the images inside the media/ folder. It includes labels for each recognized object in the input images. The processed images are available in the media-labeled/ folder. See before and after labeling: Step 3 - Display the labeled image with the following line: root@imx8mmevk:/opt/opencv/media-labeled# gst-launch-1.0 filesrc location= ! jpegdec ! imagefreeze ! autovideosink 2 - OpenCV DNN example: MIPI Camera This example is the same as above, except that it uses a camera input. It enables the MIPI camera and runs an inference on each captured frame, then displays it in a window interface in real time: root@imx8mmevk:/opt/opencv# ./camera.py 3 - OpenCV DNN example: MIPI Camera improved This example differs from the above due the additional support of GStreamer applied to it. Using the Leaky Bucket algorithm idea, the GStreamer pipeline enables the camera to continue performing its own thread (bucket overflow when full), even if the frame was not processed by the inference thread (bucket water capacity). As a result of this Leaky Bucket algorithm, this demo has smooth camera video at the expense of having some frames dropped in the inference process. root@imx8mmevk:/opt/opencv# ./camera_improved.py Go to the eIQ Sample Apps - Face Recognition using TF Lite. i.MX 8 Re: eIQ Sample Apps - Object Recognition using OpenCV DNN Hi coindu‌, As vanessamaegima‌ said before, we do not have a validated solution for video file source yet, but I can anticipate that using a video file directly on OpenCV VideoCapture property will return the worst possible results. So please, try applying the video file to a GStreamer pipeline, such as the example below: filesrc location=video_device.mp4 typefind=true ! decodebin !  imxvideoconvert_g2d ! video/x-raw,format=RGBA,width={},height={} ! videoconvert !  appsink sync=false BR, Marco Re: eIQ Sample Apps - Object Recognition using OpenCV DNN I reference the camera_improved.py demo, use video to instead of the v4l2 as input .   The fps of video is 15, it means the display on the screen time is 0.067sec. But it will cost 0.6sec to parse one frame,which frame is 480x272. So object recognition block diagram will be delayed than video. I want to parse the 10th frame when the first frame of the video is played. But this method cannot move to a certain frame. Re: eIQ Sample Apps - Object Recognition using OpenCV DNN Hi coindu‌, We provided a demo with improved performance in step 3 (3 - OpenCV DNN example: MIPI Camera improved). The same approach was not validated with video input yet. Could you please give it a try and see if it helps? marcofranchi‌, FYI. Thanks, Vanessa Re: eIQ Sample Apps - Object Recognition using OpenCV DNN hi:     I try to test this example with video.However, I found that the time for dnn to parse a frame is almost close to the display time of 10 frames of video. def dnn_parse(nn,frame,multipe=1):     height,width,color_lane=frame.shape     if multipe != 1:         height = int(height*multipe)         width = int(width*multipe)         print "h:{}w:{}".format(height,width)         frame=opencv.resize(frame,(height,width))     start_time=time.time()    blob = opencv.dnn.blobFromImage(frame,0.009718,(height,width),127.5)     nn.setInput(blob)    det=nn.forward()    end_time=time.time()    print "height{} width{} time{}".format(height,width,end_time-start_time) h:136w:240height136 width240 time0.264429092407height272 width480 time0.620328903198h:544w:960height544 width960 time2.25029802322   Then consider directly analyzing N * k frames when dnn analysis (k =, 1, 2, 3 ...). But found that opencv does not support frame skipping and calculating the total number of video frames. #!/usr/bin/env python # -*- coding: utf-8 -*- import cv2 as opencv import time if __name__ == "__main__": cap = opencv.VideoCapture('car.mp4') opencv.namedWindow("appFrame") frame_count = cap.get(opencv.CAP_PROP_FRAME_COUNT) print "frame_count.{}".format(frame_count) cap.set(opencv.CAP_PROP_POS_FRAMES,200) ret,frame = cap.read() opencv.imshow("appFrame",frame) opencv.waitKey(0) opencv.destroyAllWindows() cap.release() (python:4431): GStreamer-CRITICAL **: gst_query_set_position: assertion 'format == g_value_get_enum (gst_structure_id_get_value (s, GST_QUARK (FORMAT)))' failed Using Wayland-EGL Using the 'xdg-shell-v6' shell integration frame_count.-1.0 WARN: h264bsdDecodeSeiParameters not valid How to solve this problem? Re: eIQ Sample Apps - Object Recognition using OpenCV DNN Thanks man.. And one more thing, does Opencv perform inference on GPU or CPU? Re: eIQ Sample Apps - Object Recognition using OpenCV DNN Hi Dinesh, Go to the repository and click on "summary", below it will have a clone link so you can download the repository using git tool: $ git clone https://source.codeaurora.org/external/imxsupport/eiq_sample_apps Cloning into 'eiq_sample_apps'... remote: Counting objects: 87, done. remote: Compressing objects: 100% (79/79), done. remote: Total 87 (delta 30), reused 26 (delta 4) Unpacking objects: 100% (87/87), done. $ cd eiq_sample_apps/ Hope this helps Thanks, Diego Re: eIQ Sample Apps - Object Recognition using OpenCV DNN Hey hi diegodorta  how to download the source code to setup host machine from here..
記事全体を表示
Dual camera & dual display working on MYIR's MYD-JX8MX Dev Board MYD-JX8MX development board based on NXP i.MX8M quad processors provides powerful multi-media functions including dual displays, dual cameras, high-quality audio, etc. The target applications scale from consumer home audio to industrial building automation and mobile computers requiring high-performance and low-power processors. Highlights: - MYC-JX8MX CPU Module as Controller Board - NXP i.MX 8M Quad Application Processor - 1GB / 2GB LPDDR4, 8GB eMMC Flash, 256Mbit QSPI Flash - RS232, 4 x USB 3.0 Host, 1 x USB 3.0 Host/Device, PCIe 3.0 (x4) NVMe SSD Interface, TF Card Slot - Supports Gigabit Ethernet, WiFi/BT and 4G LTE - 2 x MIPI-CSI, HDMI, 2 x LVDS, MIPI-DSI, Audio Input/Output General
記事全体を表示
支持技术:Yocto Project ™工具 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用 Yocto 项目进行 i.MX 应用处理器开发的指南。了解如何通过添加层和配方、自定义图像、使用内核以及其他必要的 Yocto 开发任务来在开发中利用 Yocto 项目。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用 Yocto 项目进行 i.MX 应用处理器开发的指南。了解如何通过添加层和配方、自定义图像、使用内核以及其他必要的 Yocto 开发任务来在开发中利用 Yocto 项目。
記事全体を表示
Enabling Technologies: AAA Portfolio Update What is new, value proposition against competition, current and future plans for collateral, tools & reference designs; SPIDrive Hbridge, Q100 eSwitch. What is new, value proposition against competition, current and future plans for collateral, tools & reference designs; SPIDrive Hbridge, Q100 eSwitch.
記事全体を表示
Hands-On Workshop: Machine Learning with the i.MX RT1060 Crossover Processor Building on the classroom training presentation "Deploying eIQ Machine Learning on NXP MCU and Apps Processors", this hands-on session will allow attendees to take a trained neural network model and deploy it on a i.MX RT1060 crossover processor. Attendees will use MCUXpresso as the development environment and implement an end-to-end use case. See notes here. Building on the classroom training presentation "Deploying eIQ Machine Learning on NXP MCU and Apps Processors", this hands-on session will allow attendees to take a trained neural network model and deploy it on a i.MX RT1060 crossover processor. Attendees will use MCUXpresso as the development environment and implement an end-to-end use case. See notes here. i.MX Applications Processors Software & Tools Re: Hands-On Workshop: Machine Learning with the i.MX RT1060 Crossover Processor Hi, the elQ pack is not yet available on MCUXpresso SDK. Will it be updated soon?
記事全体を表示
System Design Concentration Using PMIC for Low-Power Wearables and IoT Applications Low-power wearable/IoT applications are becoming more and more popular. In this session, we will go over some of the key aspects when considering the system-level power management solution for these application, pros and cons when choosing different topologies (for example, DC/DC regulator vs. LDO), overall system level power optimization, and key components selection consideration, etc. Low-power wearable/IoT applications are becoming more and more popular. In this session, we will go over some of the key aspects when considering the system-level power management solution for these application, pros and cons when choosing different topologies (for example, DC/DC regulator vs. LDO), overall system level power optimization, and key components selection consideration, etc. Identification & Security Power Management
記事全体を表示
Clusters & Infotainment: Tuners – Mercury Car Radio Introduction Introduction to NXP’s state-of-the-art 1-chip next generation software defined radio(SDR) system solution covering global radio reception standards (Mercury family). Introduction to NXP’s state-of-the-art 1-chip next generation software defined radio(SDR) system solution covering global radio reception standards (Mercury family).
記事全体を表示
Functional Safety & Security: Safety by Software The talk on SbSW introduces a novel NXP solution for safety where the faults are detected through their effects in the actual application. The methodology is to be explained, the advantages elaborated, the challenges and their solutions described. Finally, a demo is to be presented as a proof of concept. The talk on SbSW introduces a novel NXP solution for safety where the faults are detected through their effects in the actual application. The methodology is to be explained, the advantages elaborated, the challenges and their solutions described. Finally, a demo is to be presented as a proof of concept.
記事全体を表示
Vehicle Dynamics: Cobra 55 Enhancing the performance of Cobra 55. Enhancing the performance of Cobra 55.
記事全体を表示