Multi Source Translation Content

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Multi Source Translation Content

讨论

排序依据:
<video> CHN L8 : S32G2 XRDC CHN L8 - S32G XRDC, by Danny(EN)/Peter(CHN) reference doc - AN13024: S32G2 Extended Resource Domain Controller (XRDC) – Application Note part 1 : XRDC Summary (view in My Videos) part 2 : XRDC MDAC (view in My Videos) part 3 : XRDC MRC and PAC (view in My Videos) part 4 : XRDC error handling (view in My Videos) part 5 : XRDC software enablement (view in My Videos) part 6 : XRDC wrap up questions (view in My Videos)
查看全文
Q&A: Can i.MX6Solo LDB/LVDS & LCD Ports be active simultaneously Q: Some background; this instrument has one display connected to the LVDS output of the i.MX6Solo and the SVGA monitor is using the IPU port with an external Analog Devices ADV7125 DAC to actually drive the monitor (or projector).  From Tektronix: We got our kernel logo to show up on an external SVGA monitor as well as on the internal LVDS display so we now at least know that the hardware is functional. However, when our application starts running and writing to the fb0 (background) and fb1 (foreground/overlay) frame buffers, the external monitor (fb2 frame buffer) doesn't get updated. We need to know how to get the same data going to the external monitor as goes to the internal LVDS display.  the external monitor is 800x600 and the internal is 800x480 so we'd further like those 480 lines to show up centered in the 600 line monitor. We are also hoping that this can be down without having to write/DMA all of the data twice. The answer given is SR #1122663812 was "If the customer is using Linux, fb2 should also be drawed by their application."  This was considered in adequate and Tek replied: I would like to know if they are saying that the IPU absolutely cannot automatically do what we want and if not, why not?  I would like to have some detailed information to at least convince us that they've looked into this and it really isn't possible. A: In our Linux BSP we don't support such feature. And in android BSP it was already supported. The customer must draw the fb2 by their application, ipu doesn't have the feature that combining the fb0 and overlay fb1, then resize it to fb2 automatically. The customer application can drawing their UI into a memory, then use v4l2 output to draw this buffer to both fb0 and fb2, in this case, resizing will be implemented in V4l2 output driver with IPU hardware. And if the customer needs overlay on fb2, they must combine the two layer into memory with IPU task first, then using V4l2 output to render it to display fb2. For how to use IPU task, the customer can reference to BSP unit test code: imx-test-1.1.0\test\mxc_ipudev_test The summary: for dual display case, the fb0 and fb2 are just two framebuffer memory, they must be filled before rendering to display, on iMX6S/DL, only the fb0 has the hardware overlay (fb1); if the customer wants to show same contents on two displays in Linux, their application must draw the two framebuffers, but we had some hardware method to improve the performace, using GPU or IPU task. In Android, the application will not draw frame buffer directly, it will use Android surface flinger middleware to draw, so this feature was implemnted in surface flinger; but in Linux, there is no such middleware, and application draws the framebuffer directly, so the application should handle it. This document was generated from the following discussion: i.MX6Solo LDB/LVDS & LCD Ports Active Simultaneously
查看全文
Lab Tutorial_TPM_Output Compare Find the complete material at: https://community.freescale.com/docs/DOC-95205 This video has been deleted (view in My Videos)
查看全文
Length of connection line for Kinetis L series debugging and programming Recently, some customers have provided us with feedback stating they have been experiencing difficulties when connecting  Kinetis L series  microcontrollers using Multilink Universal probes, after checking the connection and software settings no obvious errors could be found. This recurrent problem has been confirmed by several customers, the  problem is caused by a long connection line. My suggestion is to keep connection line length to 10cm or less; otherwise, the IDE may not be able to establish the connection through the Multilink Universal. Kinetis L Series MCUs Re: Length of connection line for Kinetis L series debugging and programming Thank you! I was facing this problem days and had found no solution, in my case, I could eventually write the microcontroller in use and other times not. Now I made a cable 5 cm and not used the USB MULTIKINK connector and I'm getting program the microcontroller without problems. Microcotnrolador used: MKL15Z128VLH4
查看全文
19-iMX_Serial_Download_Protocol.py <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 19-iMX_Serial_Download_Protocol.py zip ファイル <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 19-iMX_Serial_Download_Protocol.py zip ファイル
查看全文
フリーダムボード --- Crystal / PLL搭載に関する警告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 警告(WARNING) 「はじめに」ページに出くわした場合は、 FREEDOM BOARD / CORTEX M0 +はじめに 注意してください。 コースで多数の Freedom ボードを使用していると、Init Clock Routines が機能しないことが観察されました。フリーダムボードのクリスタルの*いくつか*は、「HIGH_GAIN」モードを好みません。 行を変更する pll_init(8000000、HIGH_GAIN、クリスタル、4、24、マクガウト); ~ pll_init(8000000、LOW_POWER、クリスタル、4、24、マクガウト); フリースケール・カップの内容 学生プロジェクト Re:フリーダムボード --- オンボードクリスタル/ PLLに関する警告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> すべての場合において、R25は削除されました。 また、R25を2つのボードに実装してみましたが、それでも同じ結果(1M)が得られました。通常、*直列*抵抗は、ドライブレベルを制限するためにEXTALパスに配置されます。 Re:フリーダムボード --- オンボードクリスタル/ PLLに関する警告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> これは、抵抗R25が大部分のボードにまだ実装されていないためであり、それを持っている人はこの問題を示していません。
查看全文
congatec QMX6 Adeneo Embedded Solution Of The Month Adeneo's entry for solution of the month in collaboration with Congatec Adeneo's entry for solution of the month in collaboration with Congatec General
查看全文
FRDM-IMX91 Board Flashing Guide The FRDM-i.MX 91 development board enables Advance HMI Solutions supporting Industrial and consumer HMI, Enriched user experience, Immersive Audio Processing, Voice Solutions, and Interconnected Devices (smarter edge devices) among other applications. This document explains how to set up FRDM-i.MX 91 development board. This includes the hardware connections, flashing the Linux image, and accessing the debug console. FRDM-IMX91 Board Flashing Guide Video (view in My Videos) Community Support If you have questions regarding this training, please leave your comments in our Wireless MCU Community! here  FRDM-IMX91 FRDM-Training Hands-On Training i.MX Application Processors Wireless
查看全文
Processor Expertソフトウェア - QorIQ Configuration Suite <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Freescale.com に関する製品情報 製品概要ページ ドキュメント ダウンロード トレーニングとサポート
查看全文
LS1-TWRのファームウェアアップデート <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
查看全文
Touch-screen, wireless motor control using Tower K70, with MQX, Processor Expert and PEG software - Demo See how to use the Tower Kinetis 70 development hardware and programmed with PEG GUI, MQX Software Solutions RTOS and processor expert software development tools to create this touch screen controlled, wireless motor control demonstration.   Features Hardware and software modular system that NXP provides for the Kinetis Microcontrollers K series One TWR-K70F120M board communicates with another TWR-K70F120M board wirelessly and then the second TWR-K70F120M board controls a motor Usage of LCD touch panel to control the speed of the motor   Featured NXP Products CodeWarrior Development Tools|NXP Processor Expert Software and Embedded Compon|NXP Kinetis K70 120 MHz Tower System Module|NXP MQX Industrial Re: Touch-screen, wireless motor control using Tower K70, with MQX, Processor Expert and PEG software - Demo The content is missing?  Also I need some direction, say an app note for example that shows how the KDS,SDK,MQX and PEG+ integrate PEG c++ MQX C SDK C How does this eco system integrate?... are there any examples Thanks
查看全文
G5 Engineering: IP Camera Solution based on the i.MX 6 Applications Processor G5 Engineering demonstrates an IP camera solution based on i.MX6 apps processor at the FTF Americas 2014.   Features Multiple IP cameras that are aggregated by one i.MX6 and then sent over an IP backhaul to a second i.MX 6 for integration into a single image The images are brought out to the screen. No need to use Windows reducing virus instances With a click of a button can change the display to 1x1 or 1x2 to 4x4 views Featured NXP Products ARM® Cortex®-A9 Cores: i.MX 6 Series Multicore Processors Links G5- NXP Partner   Industrial
查看全文
QorIQでのネットワーク機能仮想化 (NFV) によるマルチテナント・データ・センター - デモ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> デモオーナー: Jeffrey Maguire OpenStack®クラウドOSをQorIQマルチコアSoC上で実行する完全なマルチテナント・データセンター・プラットフォームをご覧ください。     特長 QorIQプロセッシングプラットフォームP4080/T4240マルチコアScC上でNFVサービスチェーンをサポートするOpen Stack Cloud OSマルチテナントデータセンタープラットフォーム テナント分離のためのcirtualサービスとしてのIPTables / EBTテーブルファイアウォール 仮想サービスとしての HAProxy サーバーの負荷分散   注目のNXP製品 T4240: QorIQ Tシリーズ T4240/T4160/T4080 24/16/8 バーチャル・コア P4080:データ・パスを備えたQorIQ P4080/P4040/P4081通信プロセッサ   通信インフラストラクチャ
查看全文
Why add Deglither in Pre-Exc 2 of AR6000? In pre excitation mode 2, you can have any duty cycle between pre exc value and 100% depending on battery and Vset voltage. On some alternators, with high duty cycles, the switching of excitation causes so much noise through the phase that this noise can be interpreted as valid phase signal. Thus, the device can go to regulation. To avoid that, we added the ability to deglitch the phase input only in pre excitation mode 2 to be sure that the signal we have are real phase signals. Depending on the duration of the noise our customer can see during pre excitation mode2, they can set the value of deglitcher. If they don't use pre excitation mode2, this value is "don't care".   Alternator Regulator
查看全文
Connected Home: Smart Mobile Devices - Use Case I'M Smartwatch, Smart TV's, and an interview by UI Labs CEO about natural user interfaces. The consumer experience is leading the way for the Connected Home. When technology emerges in the market, it's adopted by consumers first and then spreads into enterprise and industrial organizations.       Features See different demos showing different types devices that can be found in the home Tablets, Wearable Android watch and set top boxes interacting with TVs and smart phones Taking advantage of the i.MX6 features using Natural User Interface and showing fluid movement and seamless transitions in videos displayed using the i.MX6 processor Featured NXP Products i.MX6Q: i.MX 6Quad Processors – Quad Core Links Consumer Block Diagram Smart Home
查看全文
36V eXtremeスイッチ搭載Tower Systemoモジュール - デモ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MC06XSD200、MC10XSD200、MC16XSD200、MC50XS4200 eXtremeスイッチ製品について、 Tower Systemを使用して産業用照明およびモータ・アプリケーション向けに展示しています。 NXPの36Vシステム用のインテリジェントなデュアルハイサイドeXtremeスイッチファミリは、PQFNサブファミリ内のフットプリントとソフトウェアで完全に互換性のある、1〜12A DCの範囲の電流能力を持つデバイスを提供します。各出力は、ランプ、LED、モーター、ソレノイドなど、あらゆる種類の負荷に使用するようにプログラムできます。これにより、お客様はソフトウェアを通じて特定のアプリケーションに合わせて具体的かつ最適化できる柔軟なモジュールを設計できます。NXPの36V eXtremeスイッチソリューションは、最大36Vの電源電圧の産業用アプリケーションに必要な堅牢な設計、インテリジェンス、および安全性を提供します。統合性の向上により、このスイッチは、より軽量で小型のシステムを推進し、部品点数を削減します。       特長 チャネルあたり最大12Aの定常電流 電球とDCモーターの個別のラッチ式過電流処理 スリープ・モードでの最小供給電流(24Vで10µA未満) 内部/外部のPWMクロック信号を個別にプログラム可能 自動リトライ機能の設定による過電流、短絡、および過熱の防止 温度および電流の正確な判定 オープン負荷検出機能(チャネル・オフ/オン状態)、LEDアプリケーションにも利用可能(標準値7.0mA) 動作電圧範囲:8.0~36V、拡張動作電圧範囲:6.0~58V 3.3Vと5.0Vに対応する16ビットのSPIポートによるデバイスの制御/設定/診断の実行、最大速度8.0MHz ファミリ内でのPCBフット・プリントとSPIソフトウェア・ドライバの互換性 これらの製品は、NXPの 長期製品供給プログラム に含まれており、発売後最低15年間の供給が保証されています 注目のNXP製品 MC06XSD200:MC06XSD200、デュアル6.0mΩハイサイド・スイッチ - 製品仕様書 MC10XSD200:MC10XSD200、デュアル10mΩハイサイドスイッチ - 製品仕様書 MC16XSD200: MC16XSD200、デュアル 16 mΩ ハイサイド・スイッチ - 製品仕様書 MC50XS4200   インダストリアル
查看全文
读取Kinetis K64内部闪存导致硬故障 症状 我们知道:擦除操作后必须对 Flash 进行编程。违反此规则将导致 Kinetis K64 部件编程失败,甚至出现硬故障(AHB 读取时)。 客户意外地使用 SDK 的 API 对同一扇区进行两次编程(过度编程),而没有进行擦除操作。然后当对该扇区执行 AHB 读取(包括使用 JFLash 读取该扇区)时,会发生 Hardfault。 诊断 K64 闪存的每个扇区都有内部 ECC。当发生过度编程时,ECC 将被破坏,并在 AHB 读取该扇区时触发 Hardfault。 解决方案 使用 SDK API FLASH_VerifyErase 检查该扇区是否已被擦除。每次对闪存进行编程之前,请调用 FLASH_VerifyErase。 该问题将影响所有具有 FTFE 闪存模块的 Kinetis 设备。 感谢 Alex Yang 提供的资料。
查看全文
PN7462 Interface configuration Overview The PN7462 family consists of 32-bit Arm® Cortex®-M0-based NFC microcontrollers offering high performance and low power consumption. Because of the integrated NFC, many of the applications in which this product is used require interaction between some controllers, either to send data or instructions. In this case the board serves as a device for reading or writing NFC devices. Required Material OM27462CDKP: NFC Controller development kit  MCUXpresso Software and Tools  Step-by-Step Download MCUXpresso Download and unzip attachment Open the Project in MCUXpresso Build it Connect LPC Link to PN7462 card Connect the two cards to the pc Debug the Project Use GPIO 4 and 5 for select interface Use GPIO 6, 7 and 8 for select operation mode
查看全文
Reading Kinetis K64 Internal Flash Causes HardFault Symptoms As we know: Flash must be programmed after an erase operation. Violation of this rule will cause programming fail and even hardfault(when AHB reading) on Kinetis K64 parts. Customer accidently uses SDK’s API programming same sector twice(over-programming) without an erase operation. Then when perform AHB reading of this sector(include using JFLash to read this sector), an Hardfault occurs. Diagnosis K64 flash has internal ECC on each sector. When over-programming happens, ECC will be crushed and trigger Hardfault when AHB reading of this sector. Solution Using SDK API FLASH_VerifyErase to check if this sector is erased. Call FLASH_VerifyErase every time before you want to program the flash. This problem will impact all Kinetis device which has FTFE flash module. Thanks for Alex Yang provide the material.
查看全文
RDDSCPMSMVCSMO: Sensorless PMSM Vector Control for Compressors Reference Design Using MC56F8013 Overview Features Block Diagrams Design Resources Overview This NXP® reference design of a 3-phase sensorless PMSM vector control drive with a sliding mode observer (SMO) is targeted mainly for compressor control and other consumer and industrial applications. This cost-effective solution uses the NXP MC56F8013 device dedicated for motor control. Software written in C-code using some library algorithms Available for the MC56F8013 and MC56F8346 digital signal controllers Hardware-based on the NXP universal motor control h/w modules Features The system is designed to drive a three-phase PM synchronous motor. Application features are: 3-phase sensorless PMSM speed vector control (FOC) Sliding mode observer with adaptive velocity estimation Based on NXP ®  MC56F8013 (resp. 56F8346) controller Running on a 3-phase high voltage (230/115V) power stage FreeMASTER software control interface and monitor Block Diagrams Design Resources Legacy Designs
查看全文