Video - product demo_i.MX53.mov http://www.youtube.com/watch?feature=player_embedded&v=fQjQPpfExTQ   Uploaded by dexterji on Nov 1, 2011 One XMBC and DLNA demo on i.MX53 for chinese customers. Category: Entertainment License: Standard YouTube License   General

Q&A: How to make MX53 splash screen working on QSB's VGA? Q: MX53 u-boot doc to enable the splash screen and went through Re: MX53 u-boot Splash Screen support but I can't seem to get the splash working on the VGA output.  A: FSL do not have solution / recommendations for VGA splash screen under U-boot. Only LVDS is supported. Typically, the Uboot bootloader does not interact with any display interface and does not have a splash screen displaying capability. To add this feature to Uboot on i.MX5 platform, the IPU driver should be included into the Uboot code. Looks like we do not have ready to use solution for the LCD. As an example for LCD configuring it makes sense to use LCD settings from Linux driver. Another approach - to use Linux (Penguin) logo (assuming Linux is booted quickly after U-boot) - at least, Linux supports more display drivers and its logo using is specified. follow up question is since the Tux the penguin logo is only 80x80 is it possible to make a larger image for the Linux start up logo? yes, you should configure kernel for the new image on make menuconfig That doesn’t help this H/W guy, but I think this may - https://community.freescale.com/thread/304300    look for  “#To change the splash screen of linux kernel (small penguine on top left corner)..“ i.MX53

IMX6Dデュアルディスプレイの異なるビデオ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> i.mx6D evbボードを使用してください。 [email protected] IMX6Dデュアルディスプレイの異なるビデオ。 (マイビデオで視聴)

北京科技大学 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 2013年全球飞思卡尔杯冠军。 视频链接：1589 车辆规格： 定制K60控制板

i.MX Yocto Proyect:新しいレイヤーを作成するにはどうすればよいですか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> メタデータファイル(レシピ、設定ファイル、またはクラス)を作成または変更するときは、レイヤーを作成することをお勧めします。主な理由は単純で、 モジュール性です。次の手順に従います 1. Yoctoスクリプトにアクセスするには、BASEフォルダから環境を設定します FSL -コミュニティ-BSP $ 。setup-environment ビルド 2.レイヤーを作成する場所に移動し、名前を選択します(例:'fsl-custom') ソース $ yocto-layer create fsl-custom # 質問に答える。優先度が正しく設定されていることを確認します(数値が大きい、 # 優先度が高い)。優先度をすでに存在する最小のものに設定します。 # 他のレシピと同じ名前で新しいレシピを導入し、シャドーしたいとき #元のもの。 3. メタデータコンテンツを追加します。提案: Git でレイヤーをバージョン管理し、ローカルの Git リポジトリをサーバーにアップロードします 4. レイヤーを編集して 'build/conf/bblayers.conf' ファイルに追加します。 5. BitBakeがレイヤーを「表示」していることを確認するには、 build フォルダで次のコマンドを実行します ビルド $ bitbake-layers show-layers このドキュメントは、次のディスカッションから作成されました: i.MX Yocto Proyect: 新しいレイヤーを作成するにはどうすればよいですか?

在 ls-5.15.71-2.2.0_distro 中编译内核 在 ls-5.15.71-2.2.0_distro 中编译内核 在LLDPUG_RevL5.15.71-2.2.0中，似乎在进行一些重新配置时 内核、rootfs 应该重新打包以完成更改。 这里将生成内核，无需在 Linux 主机上重新打包 编译内核。

S32K118 : Internal Wakeup from VLPS mode using LPTMR0 This is an example project which is created to do an internal wake up from VLPS mode using LPTMR0.   From S32KRM, it tells us that internal wakeup is achievable using LPTMR0.     What code does? ======================================= 1) LPTMR0 is configured for 5 Seconds. So for interrupt occurs for every 5 seconds 2)LPTMR0  wakes up MCU for every 5 seconds and again it goes back to sleep for next 5 seconds. This cycle repeats forever. 3) When MCU is in RUN mode, GREEN color LED will be ON and it will in OFF if it goes to VLPS. Project Configurations: =======================================   Other Informations: ======================================= Design studio: S32DS3.4 SDK                    : RTM 4.0.2 EVB                     : S32K118EVB2Q048 Note:   Following symbols should be included if you are creating the project from scratch to properly put MCU to sleep and wakeup from POR.   Thanks & regards, Krishnakumar V

What is Processor Expert ? Processor Expert Software is a development system to create, configure, optimize, migrate, and deliver software components that generate source code for Freescale silicon. The main features of PEx are: Extensive and comprehensive knowledgebase for all supported silicon encapsulating all pins, registers, etc. Silicon resource conflicts flagged at design time, allowing early correction Simple creation of peripheral drivers without reading silicon documentation Easy integration of an RTOS with peripheral drivers The generated drivers have a cross-platform API that allows easy migration among supported processors. The user builds an application or library using a wide range of basic building block called Embedded components covering all common tasks (for example, serial communication, timers, ADC, DAC, digital I/O etc.). These components can be configured in graphical user interface and Processor Expert generate a C source code of initialization and runtime control drivers of the processor and its peripherals. Processor Expert is available: Integrated with CodeWarrior for Microcontrollers As a standalone package called Microcontroller Driver Suite. It supports Kinetis and ColdFire+ microcontrollers. It does not include a compiler or linker and can be used with other non-CodeWarrior IDEs. Integrated with Kinetis Design Stuido (KDS) For more details, refer to the Freescale website http://www.freescale.com/processorexpert.

FreeMaster_03.07.2013.PEupd <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 更新 PE 的 FreeMASTER 组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 更新 PE 的 FreeMASTER 组件

飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何安装伺服喇叭。更具体地说是飞思卡尔杯套件。[无音频] （在 “我的视频” 中查看） 飞思卡尔杯内容 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我的理解是伺服器的行程可以是 90 度、180 度或 360 度。顺时针。0 是课程的起点。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 它说在固定手臂之前伺服器要处于 0 度。汽车直行时，难道不应该处于中立位置（90 度）吗？ 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 没有声音就很好。消息已发送。 接下来我们将有黑白视频 查理·卓别林来到城里。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 没有声音是故意的。我需要买一个好的麦克风并找一个更安静的地方来录音！ 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 视频有声音吗？因为我什么都没听到.... 顺祝商祺！ 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 是的——在绝对确定一切控制正常之前，绝对不要将伺服器连接到转向机构。在软件中添加保护带以防止可能损害物理机制的“过度转向”。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 一旦启动，您就必须对其进行调整，并编写程序将伺服器“归零”。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢——在使用喇叭之前如何定位伺服角度以使其具有完整的运动范围？我觉得必须先将其电气连接起来，以确保在最终组装之前能够将位置归零。

USB HID Keyboard Host of the USB stack 4.1.1 Hi, I have a project created by Processor Expert and CodeWarrior 10.2 for TWR-K20 demo kit. Becasue I have some problem to use the Processor Expert USB HID Keyboard Host of the USB stack 4.1.1, I need to change to add the non-PE USB HID Keyboard Host into the project. Can anyone tell me how to do it? It will be very appreciated to give me a simple 'PE' example project, and add the non-PE USB HID keyboard host stack. Thank you! Stanley Kinetis K Series MCUs USB

FreeMaster_03.07.2013.PEupd Update of FreeMASTER component for PE Update of FreeMASTER component for PE

NTAG5 Link Energy Harvesting - Supercapacitor Introduction NTAG5 offers a powerful energy harvesting feature (up to 30mW). One useful application can be charging the supercapacitor which then might be used as the supply of customer MCU, Sensor, etc.   See the typical schematic below:  C1 and C1P are used for the impedance tuning. The antenna is typically tuned at 13.56 MHz-14MHz.  R1 is used to limit the charging current of the supercapacitor. Its value depends on the selected VOUT voltage, keep in mind that the maximum output current is 12.5 mA.  E.g. VOUT=2.4V, Icharging=10mA -> R1=240 Ohm Keep in mind, that if the charging current is too high and/or the amount of the received magnetic field is not high enough, the VOUT may drop.  D1 should be a low-drop diode e.g. RB520CS30L Used super cap: CPX3225A752D Antenna size  Generally, it is best to attempt to match the tag and the reader antenna geometries for maximum efficiency. A significant difference between the reader and tag antenna dimensions result in bad communication and energy harvesting performance because of the small coupling factor. As smartphone NFC antennas can have different dimensions. It might be challenging to design one NFC Tag antenna that will deliver the best performance for multiple smartphones.  The phone's NFC Antenna dimensions are typically between approximately 25 mm vs 20 mm (NFC Forum Poller Class 6) & 50 mm vs 30 mm (NFC Forum Poller Class 3). Note: But this might be different e.g., iPhones  So customers can consider the following form factors of NFC antennas for their Energy harvesting NTAG5 Link design:  For bigger designs (NFC Forum Listener Class 3):    For circle NFC Antenna ->Outer diameter is approx. 44 mm    For smaller designs (NFC Forum Listener Class 6):  For circle NFC Antenna ->Outer diameter is approx. 25 mm   Tomas Parizek  Customer Application Support  Connected Tag Solutions

Zephyr build fails: missing pinctrl file and HAL_NXP When using the MCUXpresso extension for VS Code and building a Zephyr application, one error that may occur is a missing pinctrl file.  The VS Code Output tab would show an error like this when the build fails: [cmake] In file included from zephyrproject/zephyr/boards/nxp/frdm_mcxn947/frdm_mcxn947.dtsi:7, [cmake] from zephyrproject/zephyr/boards/nxp/frdm_mcxn947/frdm_mcxn947_mcxn947_cpu0.dts:10, [cmake] from : [cmake] zephyrproject/zephyr/boards/nxp/frdm_mcxn947/frdm_mcxn947-pinctrl.dtsi:7:10: fatal error: nxp/mcx/MCXN947VDF-pinctrl.h: No such file or directory [cmake] 7 | #include This file is included in the HAL_NXP repo, which West should clone when the Zephyr repo is imported.  You can verify if this repo is missing.  If the Zephyr repo is at zephyrproject/zephyr, the HAL_NXP repo is at zephyrproject/modules/hal/nxp.  If the pinctrl file is missing, or this HAL_NXP repo is missing, it likely means the `west update` command failed or was interrupted when the repo was imported.  One option to resolve this is to re-import the Zephyr repo.  But this can take a long time, and needs to download and clone a large amount of files.  A faster option is to run the `west update` command using CLI. Open a command window, and Activate the Python Virtual Environment.  Change to the Zephyr repo directory.  The Windows command below uses the default path, but the VS Code Output log will show your local path: cd C:\Users\ \zephyrproject\zephyr Run the `west update` command.  Depending on how many repos are missing or need updating, this may take awhile.  Poor network bandwidth is one reason the `west update` command may have failed the first time.  If updating the repos times out or is interrupted, you can run `west update` multiple times until all the repos are updated, and west gives no more errors.

MCUXpresso for VS Code: Importing Projects from the MCUXpresso SDK MCUXpresso SDK The MCUXpresso SDK has been reengineered to make use of CMake and Kconfig. This article will demonstrate how to use the SDK in VS Code. *Note: The SDK has switched to CalVer versioning convention. *Note: The SDK will contain previews of possible changes for a later release. The previews are available for early evaluation but are not intended to substitute a release. Importing the SDK Navigate to the QUICKSTART PANEL in the MCUXpresso for VS Code extension. Click on Import Repository. Select the REMOTE option if you have not yet obtained the SDK. Designate a destination to save locally in the Location field. Select the latest release of the MCUXpresso SDK in the Repository field. The latest version for this walkthrough is MCUXpresso SDK - 24.12.00. Select the main revision in the Revision field.  Note: The SDK can be cloned directly from GitHub. Select the Local option to import if you've already obtained the SDK. Importing an example project The process of importing a project into MCUXpresso for VS Code does not vary from previous versions. To do so, simply use the Import Example from Repository option. Exploring the CMake format You will notice several folders when navigating the SDK directory. To examine the CMake project format, let's take a look at the led_blinky_peripheral project. This project is found in examples/demo_apps/led_blinky_peripheral. In this directory, you will find generic project files including the CMakeLists file. For example, the file that holds the main function in this example project can reference different board files and their respective peripherals. The files are generic to allow reusability and support for many other devices. This reduces the overall size of the SDK. The CMakeLists file is used to specify the device and project options for the build. In another article, we will cover how the variables in the CMakeLists files are referenced when a build for a specific device is initiated. For now, let's take a look at structure of the file. You'll notice that the variables in this file are generic and will be referenced later for the build. For example, the following two variables are needed for the build system to know which board to build for and where to reference the files. SdkRootDirPath - This specifies the root path to the SDK. board - This specifies the board name. Once the build is initiated all the necessary files will be drawn in to the project. MCUXpresso for VS Code

Device Tree Standalone Compile under Windows Sometime need standalone compile device tree. Only Linux headers and device tree directory are needed.  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.MX6DualPlus | 6QuadPlus i.MX6Quad i.MX6S i.MX6SL i.MX6SoloX i.MX6UL i.MX7Dual i.MX7Solo i.MX7ULP i.MX8ULP Linux Windows

Example_Reg_Prot_Flash_Controller_S32K344 *********************************************************************************** * Detailed Description: * The example locks * PFC PFCBLK2_SSPELOCK REG_PROT soft lock * and PFC REG_PROT hard lock. * ------------------------------------------------------------------------- * Test HW: : S32K344EVB-Q172 * MCU: : S32K344 * Project : RTD AUTOSAR 4.7 * Platform : CORTEXM * Peripheral : S32K3XX * Dependencies : none * * Autosar Version : 4.7.0 * Autosar Revision : ASR_REL_4_7_REV_0000 * SW Version : 5.0.0 * Build Version : S32K3_RTD_5_0_0_D2408_ASR_REL_4_7_REV_0000_20241002 ***********************************************************************************

HC08 ブートローダー application.pdfライブラリ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ブートローダアプリケーションのHC08ライブラリの割り当て方法。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ブートローダアプリケーションのHC08ライブラリの割り当て方法。 全般

i.MX6 D/Q and i.MX6 DL/S Android JB4.2.2_1.0.0-GA release Hi All, The new Android JB4.2.2_1.0.0-GA release is now available on www.freescale.com ·         Files available Name Description IMX6_JB422_100_ANDROID_DOCS i.MX 6Quad, i.MX 6Dual, and   i.MX 6DualLite Android jb4.2.2_1.0.0 BSP Documentation. Includes Release   Notes, User's Guide, QSG and FAQ Sheet. IMX6_JB422_100_ANDROID_SOURCE i.MX 6Quad, i.MX 6Dual, and   i.MX 6DualLite Android jb4.2.2_1.0.0 BSP, Documentation and Source Code for   BSP and Codecs. IMX6_JB422_100_ANDROID_DEMO i.MX 6Quad, i.MX 6Dual, and   i.MX 6DualLite Android jb4.2.2_1.0.0 BSP Binary Demo Files ·         Target HW boards o   i.MX6DL  SABRE SD board o   i.MX6Q  SABRE SD board o   i.MX6DQ SABRE AI board o   i.MX6DL SABRE AI board ·         Release Description i.MX Android jb4.2.2_1.0.0-ga is GA release for Android 4.2.2 Jelly Bean(JB) on i.MX6Q SABRE SD, i.MX6DL SABRE SD and i.MX6Q/DL SABRE AI platform with key features integrated. i.MX Android jb4.2.2_1.0.0-ga release includes all necessary codes, documents and tools to assist users in building and running Android 4.2.2 on i.MX6Q and i.MX6DL hardware board from the scratch. The prebuilt images are also included for a quick trial on Freescale i.MX6Q, i.MX6DL SABRE SD and i.MX6Q/DL SABRE AI boards. Most of deliveries in this release are provided in source code with the exception of some proprietary modules/libraries from third parties. ·         Features Feature i.MX6Q   SABRE SD i.MX6DL   SABRE SD i.MX6   SABRE AI Comments Linux 3.0.35  kernel Y Y Y Based on Linux BSP   L3.0.35_4.0.0 GA release Google JellyBean   4.2.2 release Y Y Y Based on   android-4.2.2_r1 release Bootup with Android Y Y Y Boot source eMMC& External SD eMMC& External SD SD&Nand Default Nand chip   been support is Micron MT29F8G08ABABAWP Splash Screen for   LVDS Y Y N UI (input) Multi-touch on LVDS   panel Multi-touch on LVDS panel Multi-touch on LVDS   panel UI (display) LVDS panel, HDMI   display LVDS panel, HDMI   display LVDS panel, HDMI   display UI (dual display,   LVDS+HDMI, UI mirror displayed on second device) Y Y Y UI (brightness   control) Y Y Y UI (LiveWallpaper) Y Y Y Storage - External   Media Y Y Y SD, External SD and   UDisk Storage - MTP   (Media Transfer Protocol) Y Y Y Connectivity -   Ethernet Y Y Y Connectivity - BT     Y Y     N Hardware: ·           Atheros AR3001 ·           Atheros AR3002 Profiles: ·           A2DP ·           HID ·           OPP ·           PBAP Connectivity - WiFi Y Y     Y Hardware: ·           Atheros AR6103 SDIO card Features: ·           AP mode ·           Wake on Wireless Connectivity -   3G Y Y   N Hardware: ·           HUAWEI EM770W modem ·           Infinion Amazon 1 modem ·           ZTE FM210 modem Connectivity -   GPS Y Y N Connectivity - USB Tethering Y Y Y Support WIFI and   Ethernet as upstream Internet - SIP   voice call N N N Internet - VPN Y Y Y Power - Battery   status report Y Y N/A Known limitations   about the accuracy in some use cases Power - CPU Freq Y Y Y Power - Bus Freq Y Y Y Media - Music Play Y Y Y Media - Sound Record Y Y Y Media - Video Play Y Y Y Media - Camera Y Y N Media - TVIN N/A N/A Y PAL/NTSC Media - Dual Camera Y Y Y Hardware for SABRE SD: ·           Front Camera: OV5642 CSI camera ·           Rear Camera: OV5640 MIPI camera Hardware   for SABRE AI: ·           Front Camera: UVC camera ·           Rear Camera: TV IN Media - Camcorder Y Y N Media - USB Camera Y Y Y Logitech: ·           C250 ·           E3500 Media - USB Micro Y Y Y Media - Movie   Studio Y Y Y Media - HDMI audio output Y Y Y Graphic - HW 3D   acceleration Y Y Y OpenGLES 1.1/2.0   via GC2000 or GC800 3D core Graphic - HW   accelerated UI surface composition Y Y Y Misc - ADB over USB Y Y Y Misc - Fastboot   utility Y Y Y Misc - SW update   and factory reset Y Y Y Sensor - Magmatic Y Y N Sensor -   Accelerometer Y Y N Sensor - Light Y Y N NTFS-3G File System Y Y Y For external   Storage NAND N N Y Tested NAND chip: - Micro 29F8G08ABABA ·         Change List The below section lists the big changes in JellyBean which need the user’s attention when comparing to Freescale ICS version: o   Default Android multiple display implementation in JellyBean o   Display resolution change in Setting is not been supported o   New camera hal implementation based on JellyBean libcamera2 o   Add NTFS file system support for external storage ·         Known issues For known issues and limitations please consult the release notes Android i.MX6DL i.MX6Dual i.MX6Quad i.MX6S

GTK <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 所有主板 GTK 手动 所有主板 GTK Glade 所有主板 GTK+