Processor Expertとは何ですか? <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Processor Expertソフトウェアは、フリースケール製半導体製品のソース・コードを生成するソフトウェア・コンポーネントの作成、設定、最適化、移行、配布を行うための開発システムです。 PExの主な機能は次のとおりです。 すべてのピン、レジスタなどをカプセル化する、サポートされているすべてのシリコンに関する広範で包括的なナレッジベース シリコンリソースの競合は設計時にフラグが立てられ、早期修正が可能 シリコンのドキュメントを読むことなく、ペリフェラルドライバを簡単に作成 RTOSとペリフェラルドライバの容易な統合 生成されたドライバーには、サポートされているプロセッサ間で簡単に移行できるクロスプラットフォーム API があります。 ユーザーは、すべての一般的なタスク(シリアル通信、タイマ、ADC、DAC、デジタルI/Oなど)をカバーする 組み込みコンポーネント と呼ばれる幅広い基本的なビルディングブロックを使用して、アプリケーションまたはライブラリを構築します 。これらのコンポーネントはグラフィカル・ユーザー・インターフェースで構成でき、Processor Expertは、プロセッサとその周辺機器の初期化およびランタイム制御ドライバーのCソースコードを生成します。 Processor Expertは、以下のものでご利用いただけます。 マイクロコントローラ用のCodeWarriorと統合 Microcontroller Driver Suiteと呼ばれるスタンドアロンパッケージとして。KinetisおよびColdFire+マイクロコントローラをサポートしています。コンパイラやリンカは含まれておらず、CodeWarrior 以外の他の IDE で使用できます。 Kinetis Design Stuido (KDS) との統合 詳細については、フリースケールのWebサイト http://www.freescale.com/processorexpert を参照してください。

Configuring USB composite HID mouse + keyboard MCUXpresso Config Tools provide a USB configuration component that allows configuring USB settings in a graphical environment and generates a configuration and sample C code according to the configuration.  This tutorial shows how to create the configuration and sample code for the mouse and keyboard HID USB class for the RT1050 EVKB board and build it using the MCUXpresso IDE.  Note: The i.MX RT1050 EVKB board is used; however, the instructions are applicable in a similar way on other NXP EVK boards.   Prerequisites EVKB-IMXRT1050 board  MCUXpresso IDE (v.11.x)  The SDK package for the board (EVKB-IMRT1050)  must be imported and ready to use into MCUXpresso IDE (in the installed SDKs)  Steps 1. Launch MCUXpresso IDE and click Create a new C/C++ project…:  2. Select the EVKBIMXRT1050 board in the MIMXRT1050 processor folder, click  Next:  3. Specify the project name (for example, Test_USB). In the Middleware section, select USB > USB Device. Then click Finish: 4. Unfold the drop-down menu (down arrow) of the Config tools icon (X) and launch the Peripherals tool: 5. In the Peripherals view of the Peripherals tool, click the USB1 peripheral checkbox, ignore the error for now: 6. When the Add configuration component instance dialog appears, select the USB configuration component, click  OK: 6. The USB configuration component instance is added. As it requires the component for MPU initialization, click the + icon to add it.  Confirm the selection of the MPU utility component in the dialog that appeared. Keep the MPU component in the default setting and close its editor tab. 7. In the USB component settings editor, select the HID Keyboard (bare metal) in the preset drop-down list:   The keyboard interfaces are now added to the Supported interfaces list and pre-configured. 8. To add the mouse interface, click the + in the Supported interfaces section. Select the newly added item and change the Class item to HID.   9. Check that the Use case Preset for the interface #1 is set to 'Mouse':   10. The Problems view shows an error as the clock function is inactive by default. To enable it, right-click on the error and select “Enable USBPHY1 PLL clock”: Note:  Optionally, it's possible to click the Show the problem… and adjust it in the Clocks tool. 11. Click the Update Code button in the main toolbar, a pop-up appears: In the pop-up, confirm the code update by clicking the OK button: Build the application using the Build Command in the Quickstart Panel.   13. Now connect the board to the computer via the USB debug connection. Note: The EVKB-IMXRT1050 board provides multiple USB connectors. For flashing the application, it is it’s necessary to use the debug connection.  Also ensure that the board power is configured properly. There are several other configuration jumpers on the board. So in case the application cannot be flashed or debugged,  follow the user guide of the board. 14. To launch the application in the debugger, click the Debug text located in the bottom-left corner of the IDE.   This launches the debugging and the connected board should be detected. Confirm the selection of the debug probe.   Once the connection is successful, launch the application by clicking the Run button. If the application connects successfully, connect an additional USB cable from the application USB connector to your PC. The generated source code files contain a sample code that moves a mouse cursor in a loop and sends Home and End keys. After the cable is connected and the application runs, the movement of the mouse cursor and the text cursor moves left to right are visible.    

Adeneo Embedded 的 Andrea 平板电脑多媒体应用桌面 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好，在这里您可以看到 Adeneo Embedded 的演示 Andrea's Tablet 在 Freescale 的 i.MX6 Sabre SDP 平台上运行 Android 操作系统 该视频采用了带有 Open GL 的 Adeneo 嵌入式启动器、视频播放器应用程序、图片查看器应用程序和音频播放器应用程序。 想要更多信息吗？ 请访问我们的网站： www.adeneo-embedded.com （在 “我的视频” 中查看）

KW45 / MCX W71 - Trimming adjust of 32MHz & 32kHz external crystals  Introduction The KW45-EVK & FRDM-MCX W71 include an RSIM (Radio System Integration Module) module with an external 32 MHz crystal oscillator and 32kHz external oscillator. 32MHz clock source reference is mainly intended to supply the Bluetooth LE Radio peripheral, but it can be used as the main clock source of the MCU as well. This oscillator includes a set of programmable capacitors to support crystals with different load capacitance needs. Changing the value of these capacitors can modify the frequency the oscillator provides, that way, the central frequency can be tuned to meet the wireless protocol standards. This configurable capacitance range is from C: 3.74pF to C: 10.67pF and it is configured through the RFMC Register XO_Test field at the CDAC. The KW45 comes preprogrammed with a default load capacitance value (0x1Eh). However, since there is variance in devices due to tolerances and parasite effects, the correct load capacitance should be checked by verifying that the optimal central frequency is attained.  You will need a spectrum analyzer to measure the central frequency. To find the most accurate value for the load capacitance, it is recommended to use the Connectivity Test demo application. 32kHz clock source reference is mainly intended to run in low power when the 32MHz clock is switched off. This 32kHz clock enable to leave the low power mode and enter in Bluetooth LE events. Adjusting 32MHz Frequency Example Program the KW45 /MCX W71 Connectivity Test software on the device. This example can be found in SDK_2_15_000_KW45B41Z-EVK_MR5\boards\kw45b41zevk\wireless_examples\genfsk\connectivity_test folder from your SDK package. Baremetal and FreeRTOS versions are available. In case that KW45-EVK board is being used to perform the test, you should move the 15pF capacitor populated in C3 to C4, to direct the RF signal on the SMA connector.                               3. Connect the board to a serial terminal software. When you start the application,              you will be greeted by the NXP logo screen: Press the enter key to start the test. Then press "1" to select "Continuous tests":        5. Finally, select "6" to start a continuous unmodulated RF test. At this point, you should be able to measure the signal in the spectrum analyzer. You can change the RF channel from 0 to 127 ("q" Ch+ and "w" Ch- keys), which represents the bandwidth from 2.360GHz to 2.487GHz, stepping of 1MHz between two consecutive channels. To demonstrate the trimming procedure, this document will make use of channel 42 (2.402GHz) which corresponds to the Bluetooth LE channel 37. In this case, with the default capacitance value, our oscillator is not exactly placed at the center of the 2.402GHz, instead, it is slightly deflected to 2.40200155 GHz, as depicted in the following figure:       6. The capacitance can be adjusted with the "d" XtalTrim+ and "f" XtalTrim- keys. Increasing the capacitance bank means a lower frequency. In our case, we need to increase the capacitance to decrease the frequency. The nearest frequency of 2.402 GHz was 2.40199940 GHz      7. Once the appropriate XTAL trim value has been found, it can be programmed as default in any Bluetooth LE example, changing the BOARD_32MHZ_XTAL_CDAC_VALUE constant located in the board_platform.h file:   Adjusting 32kHz Frequency Example You could adjust the capacitor bank on the 32kHz oscillator. You need to observe the 32kHz frequency at pin 45 (PTC7) using an spectrum analyzer or a frequency meter. Inserting this below code in the main(void) in your application: Hello_world application in this example. 32kHz frequency is not active by default on pin45(PTC7). You need to configure the OSC32K_RDY at 1 in the CCM32K register Status Register (STATUS) field to observe the 32kHz frequency at pin 45 (PTC7). Configure the CAP_SEL, XTAL_CAP_SEL and EXTAL_CAP_SEL field available in the CCM32K register 32kHz Oscillator Control Register (OSC32K_CTRL). XTAL_CAP_SEL and EXTAL_CAP_SEL values are from 0pF (0x00h) to 30pF (0x0Fh). You could configure those 2 registers in the clock_config.c file. Default values are 8pF for both registers.   Protocol: BLE -> connectivity

VS Code の MCUXpresso: はじめに この入門ガイドでは、以下について説明します。 VS Code 拡張機能用の MCUXpresso のインストール MCUXpresso Installler を使用した依存関係のインストール SDKのインポート方法 (マイビデオで視聴) MCUXpresso for VS Code

Introduction to RW61x and FRDM-RW612 Step by Step video: (view in My Videos) FRDM-RW612 FRDM-Training Wireless

RW61xおよびFRDM-RW612の紹介 ステップバイステップのビデオ: (マイビデオで視聴) FRDM-RW612 FRDMトレーニング ワイヤレス

IEEE 1588 外部 PPS (パルス/秒) 信号 (LS1046ARDB および LS1043ARDB) PPS（1秒あたりのパルス）信号は、DPAA1プラットフォームを含むLayerscapeのほとんどのネットワークコントローラーに適用されます。 PPS信号は、1588タイマーパルスアウトピンを介して出力されます。QorIQ PTPドライバは、デフォルトで固定インターバル周期パルス(FIPER)ジェネレータをPPS信号として構成しました。 このドキュメントでは、他のリファレンスクロックソースの選択、必要なPPS信号を生成するための公称クロック周期、FIPERS周期、出力クロック周期の設定など、1588タイマーの設定をカスタマイズするためのdtsファイルの作成方法について説明します。

Task #1 - Download the source code Yocto Project versions and names Preparing host environment For virtual machine (VirtualBox): Download the source code from NXP Code Aurora Yocto Project versions and names See here the list of all yocto version names: Releases - Yocto Project  The current stable release is Zeus Preparing host environment For virtual machine (VirtualBox): Please set memory size minimal to 1GB and disk size to 32GB. (24Feb2014 Ubuntu 12.04LTS)   First, make sure your host PC has the required packages to run Yocto The essential packages you need for a supported Ubuntu distribution are shown in the following command: $ sudo apt-get build-dep qemu $ sudo apt-get remove oss4-dev $ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib \   build-essential chrpath socat cpio python python3 python3-pip python3-pexpect \   xz-utils debianutils iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev \   xterm‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ For other Linux distribution or newer Yocto Project release see here the updated list. Download the source code from community Install the repo $ sudo apt-get install repo‍‍‍‍ Download the BSP source: $ mkdir fsl-community-bsp $ cd fsl-community-bsp $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b zeus $ repo sync‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Download the source code from NXP Code Aurora See here the list of all BSP releases from NXP: imx-manifest - i.MX Release Manifest  Currently, the latest NXP release how to is here: README - imx-manifest - i.MX Release Manifest  To understand the difference between the 2 source code (community X NXP BSP) see here Go to https://community.nxp.com/docs/DOC-94849  Go to Task #2 Yocto Project Re: Task #1 - Download the source code i tried as a root user. and still i got when i initialized repo. so, when i tried repo init -u https://github.com/Freescale/fsl-community-bsp-platform-b dora i got following error curl: (22) The requested URL returned error: 404 Server does not provide clone.bundle; ignoring. but i continued and there is no problem i think. i downloaded about 238MB as you described. and later i changed ownership of fsl-community-bsp directory. Thank you for your support. Re: Task #1 - Download the source code yes, you´re done and you can start task 2 from time to time, try to download repo again, and try to understand why you´re facing those errors. as repo are used for android there are SEVERAL foruns with SEVERAL repo errors. take your time and fix your env. from yocto perpective, you don´t need repo to get things done. There is small differences when not using fsl community bsp, it´s the setup enviroment script (you should use that one from poky it´s oe-init-build-env (http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/oe-init-build-env) And you must include all layers in your build/conf/bblayers.conf. Take a look here https://community.freescale.com/docs/DOC-94614 how your bblayers should look like. Re: Task #1 - Download the source code git clone git://git.yoctoproject.org/poky Cloning into 'poky'... remote: Counting objects: 226330, done. remote: Compressing objects: 100% (57269/57269), done. remote: Total 226330 (delta 164862), reused 225517 (delta 164064) Receiving objects: 100% (226330/226330), 100.81 MiB | 193 KiB/s, done. Resolving deltas: 100% (164862/164862), done. jigar@ubuntu:~/fsl-community-bsp$ git clone git://git.yoctoproject.org/meta-fsl-arm Cloning into 'meta-fsl-arm'... remote: Counting objects: 6917, done. remote: Compressing objects: 100% (2582/2582), done. remote: Total 6917 (delta 4165), reused 6788 (delta 4037) Receiving objects: 100% (6917/6917), 37.29 MiB | 206 KiB/s, done. Resolving deltas: 100% (4165/4165), done. i tried for meta-openembedded, fsl-community-bsp-base , meta-fsl-arm-extra, meta-fsl-demos.. and now i have 6 directories as described. Now what i have to do next? or is it finished and i can start task 2? :smileyconfused: Re: Task #1 - Download the source code ok. So let´s try the git clone: poky: $ git clone git://git.yoctoproject.org/poky meta-fsl-arm: $ git clone git://git.yoctoproject.org/meta-fsl-arm let´s start with only 2, next step would include meta-qt5. But let´s start with a core-image-minimal at first. please, let me know if it works (oh, and I´m so sorry, but I don´t know how to configure networks) Re: Task #1 - Download the source code yes, ofcourse git is installed. I have newest version of git.. apt-get install git Reading package lists... Done Building dependency tree       Reading state information... Done git is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. Re: Task #1 - Download the source code exactly the same I have. oh...... do you have git installed???????????? (only to make sure) (my python is 2.7.5+ and my git is 1.8.3.2, and my gcc is 4.8.1) Re: Task #1 - Download the source code No i haven't try git clone and i don't know how to use git clone.:smileysilly: i use this version repo version v1.12.13        (from https://gerrit.googlesource.com/git-repo) repo launcher version 1.21       git version 1.7.9.5 Python 2.7.3 (default, Feb 27 2014, 19:58:35) [GCC 4.6.3] Re: Task #1 - Download the source code are you using a updated repo file? Have you tried "git clone" of each meta layer? (please, let me know if you know how to do it ) Re: Task #1 - Download the source code i want it for cross compile qt5 HMI application. I have a imx6qsabreauto board. i want to flash this board. i want to use it for infotainment. i tried with http and https but its still not working. Re: Task #1 - Download the source code I had several errors regarding http and https mistakes on my local configuration. inside repo you may see a URL, you may change http to https (or vice-versa) and try the one different than default. OR, you can dowloand every metalayer one by one, using git clone, instead of using repo. the manifest: https://github.com/Freescale/fsl-community-bsp-platform/blob/dora/default.xml show you what to download and which branch to use. Re: Task #1 - Download the source code Okay. that means there is something wrong with my proxy. can you suggest me what steps can i take to download it successfully? i tried your given link but i got curl:(22) error at repo sync -init step. Re: Task #1 - Download the source code It´s working for me. I´m using the instructions from http://freescale.github.io/ Re: Task #1 - Download the source code let me try it here Re: Task #1 - Download the source code actually i tried this on my personal laptop at home and there also i got error. curl: (22) The requested URL returned error: 404 Server does not provide clone.bundle; ignoring. In office i work under a proxy and i set proxy as required. my port is also open. and i have a right access for external network also. Re: Task #1 - Download the source code Please, make sure you have the right access for external network. Are you under a proxy? Are your http/https port open? Re: Task #1 - Download the source code Hello Daiane, I try to download bsp. so, when i tried repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dora i got following error curl: (22) The requested URL returned error: 404 Server does not provide clone.bundle; ignoring. remote: Reusing existing pack: 147, done. remote: Total 147 (delta 0), reused 0 (delta 0) Receiving objects: 100% (147/147), 21.69 KiB, done. Resolving deltas: 100% (47/47), done. But i continued and i did repo snc . I downloaded about 42MB and its finished. but as you described above it should be 238MB. so i dont think this is complete. I have 1 more laptop which have virtual machine. on that laptop when i tried curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo i did not get complete repo file. so i download it and put that on my folder. And again now when i tried repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dora on virtual machine i got following error. fatal: cannot get https://gerrit.googlesource.com/git-repo/clone.bundle fatal:error Tunnel connection failed: 407 Proxy Authorization Required. so i tried to open  https://gerrit.googlesource.com/git-repo/clone.bundle link but i got not found message. i tried export http_proxy and https_proxy but not successfull. for your kind information i working behind proxy as i am using company's network. so can you suggest me something? Re: Task #1 - Download the source code It downloads only the new content. Except if you delete the downloads directory. Re: Task #1 - Download the source code Daiane, Initially I build image for 'imx6qsabresd' using Yocto and it works fine. $ MACHINE=imx6qsabresd . ./setup-environment build $  bitbake fsl-image-gui Now, I want to do the same for  'wandboard-solo', so I run below commands: $ MACHINE=wandboard-solo . ./setup-environment build $  bitbake fsl-image-gui I am seeing that again it is downloading some stuff. Will it download everything again ( 44GB) or only the difference ? ~Suman Re: Task #1 - Download the source code change the repo provider URL Re: Task #1 - Download the source code What was the solution for this?  I'm seeing the same issue. Thanks Re: Task #1 - Download the source code ohhhhhhhhhhhhhhhhhhhhhhhhhhh You are completely right, I´m sorry... it´s repo init -b dora :smileygrin: Re: Task #1 - Download the source code Daiane, repo init -u dora doesn't work Outputs "unknown repository url: dora" Re: Task #1 - Download the source code It worked on my side. Just tested one minute ago. What error did you get? Re: Task #1 - Download the source code 'git.yoktoproject.org' does not exit, it should be 'git.yoctoproject.org'. Did you change something on the manifest file? Leo Re: Task #1 - Download the source code Hi, we are working with the Freescale SDB and want to change vom LTIB to YOCTO. So I found this great Yocto training. I followed the tutorial step by step, but the ==> repo sync does not work correctly. I get the following errors: fatal: Unable to look up github.com (port 9418) (Der Name oder Dienst ist nicht bekannt) fatal: Unable to look up git.yoktoproject.org (port 9418) (Der Name oder Dienst ist nicht bekannt) error: Cannot fetch meta-fsl-demos I think it might be a firewall-item, but i´m not sure. Is there any possibility to change from git://...... to http:// port 8080 Best Regards and thx in advance Karsten Re: Task #1 - Download the source code Hi Daiane, Thanks for your Update - sadly the repo-command doesnt work Maybe it has to be $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dora Re: Task #1 - Download the source code dora is latest stable branch and was just formally released! Thanks florianl Re: Task #1 - Download the source code Hi everybody! You wrote in your tutorial: $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan Is it still recommended to use "dylan"? I heard about that "dora" would be a newer version with better support for the boards? (e.g. here: http://boundarydevices.com/yocto-dora-release-mx6/) If dora is better we should update this part in the DOC above Re: Task #1 - Download the source code Thans a lot, petersuciu! Re: Task #1 - Download the source code Diane, Please update the instructions, with latest curl URL, save people a couple hours and the hair on their heads. Thanks! Re: Task #1 - Download the source code In case you are having issues downloading the source. The repo (from google) has been updated to: curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo see Repo release 1.12.4 for more information Re: Task #1 - Download the source code are you under a proxy? Re: Task #1 - Download the source code Hi Daiane, Really useful article - Thanks. However, I have a problem - when I do the "repo init" step, I get lots of good things happening, but also an error: curl: (22) The requested URL returned error: 404 Not Found Server does not provide clone.bundle; ignoring. Any ideas what is happening here? Full command / response shown below: dchirgwin@dc-ubuntu2:~/fsl-community-bsp$ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan Get https://gerrit.googlesource.com/git-repo remote: Counting objects: 101, done remote: Finding sources: 100% (101/101) remote: Total 2533 (delta 1442), reused 2533 (delta 1442) Receiving objects: 100% (2533/2533), 1.71 MiB | 813 KiB/s, done. Resolving deltas: 100% (1442/1442), done. From https://gerrit.googlesource.com/git-repo * [new branch]      maint      -> origin/maint * [new branch]      master     -> origin/master * [new branch]      stable     -> origin/stable * [new tag]         v1.0       -> v1.0 * [new tag]         v1.0.1     -> v1.0.1 * [new tag]         v1.0.2     -> v1.0.2 * [new tag]         v1.0.3     -> v1.0.3 * [new tag]         v1.0.4     -> v1.0.4 * [new tag]         v1.0.5     -> v1.0.5 * [new tag]         v1.0.6     -> v1.0.6 * [new tag]         v1.0.7     -> v1.0.7 * [new tag]         v1.0.8     -> v1.0.8 * [new tag]         v1.0.9     -> v1.0.9 * [new tag]         v1.1       -> v1.1 * [new tag]         v1.10.0    -> v1.10.0 * [new tag]         v1.10.1    -> v1.10.1 * [new tag]         v1.10.2    -> v1.10.2 * [new tag]         v1.10.3    -> v1.10.3 * [new tag]         v1.10.4    -> v1.10.4 * [new tag]         v1.11.0    -> v1.11.0 * [new tag]         v1.11.1    -> v1.11.1 * [new tag]         v1.12.0    -> v1.12.0 * [new tag]         v1.12.1    -> v1.12.1 * [new tag]         v1.12.2    -> v1.12.2 * [new tag]         v1.2       -> v1.2 * [new tag]         v1.3       -> v1.3 * [new tag]         v1.3.1     -> v1.3.1 * [new tag]         v1.3.2     -> v1.3.2 * [new tag]         v1.4       -> v1.4 * [new tag]         v1.4.1     -> v1.4.1 * [new tag]         v1.4.2     -> v1.4.2 * [new tag]         v1.4.3     -> v1.4.3 * [new tag]         v1.4.4     -> v1.4.4 * [new tag]         v1.5       -> v1.5 * [new tag]         v1.5.1     -> v1.5.1 * [new tag]         v1.6       -> v1.6 * [new tag]         v1.6.1     -> v1.6.1 * [new tag]         v1.6.10    -> v1.6.10 * [new tag]         v1.6.10.1  -> v1.6.10.1 * [new tag]         v1.6.10.2  -> v1.6.10.2 * [new tag]         v1.6.2     -> v1.6.2 * [new tag]         v1.6.3     -> v1.6.3 * [new tag]         v1.6.4     -> v1.6.4 * [new tag]         v1.6.5     -> v1.6.5 * [new tag]         v1.6.6     -> v1.6.6 * [new tag]         v1.6.7     -> v1.6.7 * [new tag]         v1.6.7.1   -> v1.6.7.1 * [new tag]         v1.6.7.2   -> v1.6.7.2 * [new tag]         v1.6.7.3   -> v1.6.7.3 * [new tag]         v1.6.7.4   -> v1.6.7.4 * [new tag]         v1.6.7.5   -> v1.6.7.5 * [new tag]         v1.6.8     -> v1.6.8 * [new tag]         v1.6.8.1   -> v1.6.8.1 * [new tag]         v1.6.8.10  -> v1.6.8.10 * [new tag]         v1.6.8.11  -> v1.6.8.11 * [new tag]         v1.6.8.2   -> v1.6.8.2 * [new tag]         v1.6.8.3   -> v1.6.8.3 * [new tag]         v1.6.8.4   -> v1.6.8.4 * [new tag]         v1.6.8.5   -> v1.6.8.5 * [new tag]         v1.6.8.6   -> v1.6.8.6 * [new tag]         v1.6.8.7   -> v1.6.8.7 * [new tag]         v1.6.8.8   -> v1.6.8.8 * [new tag]         v1.6.8.9   -> v1.6.8.9 * [new tag]         v1.6.9     -> v1.6.9 * [new tag]         v1.6.9.1   -> v1.6.9.1 * [new tag]         v1.6.9.2   -> v1.6.9.2 * [new tag]         v1.6.9.3   -> v1.6.9.3 * [new tag]         v1.6.9.4   -> v1.6.9.4 * [new tag]         v1.6.9.5   -> v1.6.9.5 * [new tag]         v1.6.9.6   -> v1.6.9.6 * [new tag]         v1.6.9.7   -> v1.6.9.7 * [new tag]         v1.6.9.8   -> v1.6.9.8 * [new tag]         v1.7       -> v1.7 * [new tag]         v1.7.1     -> v1.7.1 * [new tag]         v1.7.2     -> v1.7.2 * [new tag]         v1.7.3     -> v1.7.3 * [new tag]         v1.7.3.1   -> v1.7.3.1 * [new tag]         v1.7.4     -> v1.7.4 * [new tag]         v1.7.4.1   -> v1.7.4.1 * [new tag]         v1.7.4.2   -> v1.7.4.2 * [new tag]         v1.7.4.3   -> v1.7.4.3 * [new tag]         v1.7.5     -> v1.7.5 * [new tag]         v1.7.6     -> v1.7.6 * [new tag]         v1.7.6.1   -> v1.7.6.1 * [new tag]         v1.7.7     -> v1.7.7 * [new tag]         v1.7.7.1   -> v1.7.7.1 * [new tag]         v1.7.7.2   -> v1.7.7.2 * [new tag]         v1.7.7.3   -> v1.7.7.3 * [new tag]         v1.7.7.4   -> v1.7.7.4 * [new tag]         v1.7.7.5   -> v1.7.7.5 * [new tag]         v1.7.7.6   -> v1.7.7.6 * [new tag]         v1.7.8     -> v1.7.8 * [new tag]         v1.7.8.1   -> v1.7.8.1 * [new tag]         v1.7.8.2   -> v1.7.8.2 * [new tag]         v1.8.0     -> v1.8.0 * [new tag]         v1.8.1     -> v1.8.1 * [new tag]         v1.8.2     -> v1.8.2 * [new tag]         v1.9.0     -> v1.9.0 * [new tag]         v1.9.1     -> v1.9.1 * [new tag]         v1.9.2     -> v1.9.2 * [new tag]         v1.9.3     -> v1.9.3 * [new tag]         v1.9.4     -> v1.9.4 * [new tag]         v1.9.5     -> v1.9.5 * [new tag]         v1.9.6     -> v1.9.6 Get https://github.com/Freescale/fsl-community-bsp-platform   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                  Dload  Upload   Total   Spent    Left  Speed   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0 curl: (22) The requested URL returned error: 404 Not Found Server does not provide clone.bundle; ignoring. remote: Counting objects: 90, done. remote: Compressing objects: 100% (63/63), done. remote: Total 90 (delta 27), reused 87 (delta 26) Unpacking objects: 100% (90/90), done. From https://github.com/Freescale/fsl-community-bsp-platform * [new branch]      danny      -> origin/danny * [new branch]      denzil     -> origin/denzil * [new branch]      dylan      -> origin/dylan * [new branch]      master     -> origin/master * [new tag]         1.2        -> 1.2 * [new tag]         1.4        -> 1.4 Your identity is: David Chirgwin <[email protected]> If you want to change this, please re-run 'repo init' with --config-name Testing colorized output (for 'repo diff', 'repo status'):   black    red      green    yellow   blue     magenta   cyan     white   bold     dim      ul       reverse Enable color display in this user account (y/N)? repo has been initialized in /home/dchirgwin/fsl-community-bsp Re: Task #1 - Download the source code Hi, when I remember right, for my Gentoo it was 'emerge sys-devel/gettext media-libs/libsdl dev-util/diffstat dev-vcs/git' Re: Task #1 - Download the source code For Ubuntu (12.04), I needed to install "curl". (sudo apt-get install curl) Maybe you can add it, in the first section. Thanks ssinfod. Re: Task #1 - Download the source code Thanks Ajay, I´m going to fix my doc. I use Ubuntu only, so please, keep doing the tasks and please, keep reporting any issue you face! It will help a lot of other people that may follow it in future Re: Task #1 - Download the source code Hi, On fedora there is no eglibc-devel only glibc-devel Ajay Re: Task #1 - Download the source code I would write: ""First, make sure your host PC has the required packages to run Yocto"" Re: Task #1 - Download the source code Thanks a lot Re: Task #1 - Download the source code Daiane, what do you think if we use the word 'Download' instead of 'Take'? Or even 'Obtain'? it is just a semantic opinion Leo

割り込みの背景 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> マイクロコントローラの割り込みを一般的な観点から見てみましょう。これは、ARM コアの割り込みに関連する他のビデオをコンテキストに配置するために使用されます。 (マイビデオで視聴) Re:割り込みの背景 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ビデオ チュートリアルの完全なセットについては、「The Book of Eli - Microcontrollers, robotics and warp drives」をご覧ください。

PN7220 i.MX Miniへのブリングアップ カードとモバイル決済、Europay、Mastercard、Visaのリーチ拡大を目指す (EMV)POS(Point of Sale)端末は、ハードウェアに取って代わり、より軽量化が進んでいます ソフトウェアとバックエンドのセキュリティによるセキュリティ。スマートフォンなどの既製のモバイルデバイスは、支払いカード、いわゆるSoftPOSの受け入れポイントになる可能性があります。 日時:PN7220 i.MX Miniのブリングアップ 「Androidの実行」セクションには、次のように記載されています。 NCI 通信を取得するには、次のコマンドを使用します ADBログキャット |skynet.pl skynet.pl をダウンロードできる場所を教えてください。 ありがとうございます

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

CodeWarriorプロジェクトをゼロから-パートI <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Codewarriorでフリーダムボード向けの基本的なプロジェクトをゼロから作成する方法。 ビデオリンクを見る：1459 (マイビデオで視聴) Re:ゼロからのCodeWarriorプロジェクト - パートI <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ビデオ チュートリアルの完全なセットについては、「The Book of Eli - Microcontrollers, robotics and warp drives」をご覧ください。

Bluetooth LE チャネルサウンディングコンテンツ チャネル・サウンディング

RT600/1170 UAC change OUT endpoint interval methods 1.    Abstract When using the RT600 SDK USB composite example, the customer found that the default HS interval was 125us, and the code was: mimxrt685audevk_dev_composite_hid_audio_unified_bm. However, in actual applications, the 125us packet interval for data transmission will cause a large interrupt load on the CPU, so the customer hopes to change the interval to a larger during, such as 1ms. After changing interval to 1ms, it is found that the data packet can be sent to the RT chip, but there is indeed a problem with the playback on the RT side, speaker no voice. Changing it to 500us in synchronous mode is possible work, but at 500us, the customer's CPU load still reaches more than 80%, which is not convenient for subsequent application code expansion, so it is still hoped to achieve a 1ms method. This article will give the transmission of different intervals of UAC and provide a solution for 1ms intervals. 2.    Test situation    Board：MIMXRT685-AUD-EVK    SDK：SDK_2_15_000_MIMXRT685-AUD-EVK    USB Analyzer：Lecroy USB-TOS2-A01-X 2.1 Platform connection situation First, given the connection between MIMXRT685-AUD-EVK, USB analyzer and audio source. This article mainly tests the RT685 UAC speaker function, that is, USB transmits audio source data to RT685, and plays the audio source through a player (which can be headphones), or speaker. The J7 USB port of EVK is connected to the A port of Lecroy, and the B port of Lecroy is connected to the audio source, which can be a PC or a mobile phone. If using a PC, the speaker needs to be selected as USB AUDIO+HID DEMO, because the name of the board after UAC enumeration is USB AUDIO+HID DEMO. The other end of Lecroy is connected to the PC for transmitting USB bus data. The specific connection diagram is as follows:      Fig 1 EVK USB analyzer connection 2.2 Different audio interval data package situation This chapter gives the modifications under different intervals, as well as the results of USB analyzer packet capture. The clock system of the audio synchronous/isochronous audio endpoint can be synchronized through SOF. The USB 1.0 sampling rate must be locked to the 1ms SOF beat. The USB2.0 high-speed HS endpoint can be locked to the 125us SOF beat. If you want to change the interval, it is usually a multiple of 125us, that is, it can be 250us, 500us, 1ms, etc. The modification method is usually to directly modify the USB stack's usb_audio_config.h:   #define HS_ISO_OUT_ENDP_INTERVAL (0x01) The relationship between HS_ISO_OUT_ENDP_INTERVAL and the real during time is: 125us*2^( HS_ISO_OUT_ENDP_INTERVAL -1) So: HS_ISO_OUT_ENDP_INTERVAL=1 : 125us HS_ISO_OUT_ENDP_INTERVAL=2 : 250us HS_ISO_OUT_ENDP_INTERVAL=3 : 500us HS_ISO_OUT_ENDP_INTERVAL=4 : 1000us The following are the four situations mentioned above respectively through USB analyzer packet capture test. 2.2.1 125us interval packet situation #define HS_ISO_OUT_ENDP_INTERVAL (0x01) Fig 2 125us interval It can be seen that when the interval is configured to 125us, the SOF beat interval in front of each OUT packet is 125us, and the length of the OUT data packet is 24Byte. The data in this 24Byte packet is the actual audio data. In this case, the playback is normal   2.2.2 250us interval packet situation #define HS_ISO_OUT_ENDP_INTERVAL (0x02) The packet capture configured as 250us is shown in the figure below. It can be seen that the SOF beat interval in front of the two OUT packets is 250us, and the length of the OUT data packet is 48 Byte. In other words, as the interval increases, the length of the data packet also increases proportionally, that is, the transmission time is longer, but a packet contains more data packets. At this time, the RT side also needs to provide more USB receiving buffers to receive data. Fig 3 250us interval This situation, the speaker play normally, have the audio sound. 2.2.3 500us interval packet situation #define HS_ISO_OUT_ENDP_INTERVAL (0x03) Fig 4 500us interval SYNC mode At this time, you can see that the data packet has become 96 Bytes, and the data content is also normal audio data, but the playback has problems and no sound can be heard. However, if you configure: #define USB_DEVICE_AUDIO_USE_SYNC_MODE (0U) It is not the SYNC mode, it can hear the audio sound, the packet situation is: Fig 5 500us interval no SYNC mode However, the asynchronous mode also has problems. After a long period of operation, it may become out of sync and the playback may become stuck. Therefore, it is still necessary to use the 1ms method in the synchronous mode. 2.2.4 1ms interval packet situation #define HS_ISO_OUT_ENDP_INTERVAL (0x04) Fig 6 interval 1ms It can be seen that the data packet length has become 192 bytes, and the SOF beat interval in front of the OUT packet has indeed become 1ms. The audio data packet also looks like normal audio data, so the audio data here is successfully transmitted from USB to RT. However, the playback is abnormal and no sound can be heard. 3. 1ms interval solution Now let's debug the project to find the problem. Because the USB analyzer can show that the audio data of the USB bus is actually transmitted, we must first check whether the USB receives the data packet in the kUSB_DeviceAudioEventStreamRecvResponse event in USB_DeviceAudioCompositeCallback of audio_unified.c, whether the data packet length is correct, and whether the data content looks like audio data. The following is the debug result: Fig 7 data packet received situation So from this point of view, the USB interface data packet is received, and the data looks like real audio data. If it is abnormal data, it is either all 0 or irregular data that changes, but the test result cannot be played. So now to check the I2S playback function, composite.h file, TxCallback function: Fig 8 I2S play data buffer We can see, the real data transfer to the I2S data buffer are always 0, and the reality should be g_composite.audioUnified.startPlayFlag none zero, and also use: s_TxTransfer.dataSize = g_composite.audioUnified.audioPlayTransferSize; s_TxTransfer.data=audioPlayDataBuff + g_composite.audioUnified.tdReadNumberPlay; But, after testing, audioPlayDataBuff data are also 0. So the issue should be the USB received side, receive the data, but when save the data to the audioPlayDataBuff have issues, go back to audio_unified.c Fig 9 USB_DeviceAudioCompositeCallback Fig10 USB_AudioSpeakerPutBuffer After testing, in the Fig 9, audioUnified.tdWriteNumberPlay never larger than g_deviceAudioComposite->audioUnified.audioPlayTransferSize * AUDIO_CLASS_2_0_HS_LOW_LATENCY_TRANSFER_COUNT=192*6 #define AUDIO_CLASS_2_0_HS_LOW_LATENCY_TRANSFER_COUNT \ (0x06U) /* 6 means 6 mico frames (6*125us), make sure the latency is smaller than 1ms for sync mode */ The low latency here is a delay buffer. Therefore, the USB cache data must at least be able to hold the delayed data packet. Unit 1 represents an interval frame. Now it is changed to an interval of 1ms, 6 delay units, which means that the delay here is 6ms. Here, the receiving buffer size needs to be larger, which is related to the following definition: Fig 11 USB device callback g_composite.audioUnified.audioPlayBufferSize = AUDIO_PLAY_BUFFER_SIZE_ONE_FRAME * AUDIO_SPEAKER_DATA_WHOLE_BUFFER_COUNT; #define AUDIO_PLAY_BUFFER_SIZE_ONE_FRAME AUDIO_OUT_TRANSFER_LENGTH_ONE_FRAME #define AUDIO_OUT_FORMAT_CHANNELS (0x02U) #define AUDIO_OUT_FORMAT_SIZE (0x02) #define AUDIO_OUT_SAMPLING_RATE_KHZ (48) /* transfer length during 1 ms */ #define AUDIO_OUT_TRANSFER_LENGTH_ONE_FRAME \ (AUDIO_OUT_SAMPLING_RATE_KHZ * AUDIO_OUT_FORMAT_CHANNELS * AUDIO_OUT_FORMAT_SIZE) #define AUDIO_SPEAKER_DATA_WHOLE_BUFFER_COUNT \ (2U) /* 2 units size buffer (1 unit means the size to play during 1ms) */ Here, try to set larger AUDIO_SPEAKER_DATA_WHOLE_BUFFER_COUNT, let it should be at least can put 6ms data, as 1 unit is 1ms play data size, and it needs to have more than 6ms, so, set to 12 unit, the modified definition: #define AUDIO_SPEAKER_DATA_WHOLE_BUFFER_COUNT 12 Build the project and download it, now capture the USB bus data again: Fig 12 1ms interval data packet play successfully This data waveform is the data that can be played normally. Below is the video of the MIMXRT685-AUD-EVK test. The attachment provides two demos of RT685 and RT1170, both modified to 1ms interval, and the modification method of RT1170 is exactly the same 4.    Summarize Whether it is RT600, RT1170, or more precisely the UAC code of the entire RT series, if you need to modify the interval, the main focus is on the following macros in usb_audio_config.h, the following is for 1ms interval: #define HS_ISO_OUT_ENDP_INTERVAL (0x04)//(0x01)//(0X04) #define AUDIO_CLASS_2_0_HS_LOW_LATENCY_TRANSFER_COUNT \ (0x06U) /* 6 means 16 mico frames (6*125us), make sure the latency is smaller than 1ms for ehci high speed */ #define AUDIO_SPEAKER_DATA_WHOLE_BUFFER_COUNT \ (12U)//(2U) /* 2 units size buffer (1 unit means the size to play during 1ms) */ Test video: (view in My Videos) i.MXRT 106x i.MXRT 600 Re: RT600/1170 UAC change OUT endpoint interval methods Thanks so much for my colleague  @tim_wang and @jia_guo endless help!

i.Mx6 CSI Test Mode Question The customer would like to test BT.656 using Test mode. Is it supported? 38.4.3.3 Test mode in RM shows only one CSIx_SENS_CONG setting. Does it mean Test mode support only one as follows? Does Test mode support other settings? CSIx_EXT_VSYNC = 0x1 CSIx_DATA_WIDTH = 0x1 CSIx_SENS_DATA_FORMAT = 0x0 CSIx_PACK_TIGHT = 0x0 CSIx_SENS_PRTCL = 0x1 CSIx_SENS_PIX_CLK_POL = 0x1 CSIx_DATA_POL = 0x0 CSIx_HSYNC_POL = 0x0 CSIx_VSYNC_POL = 0x0 For example, customer want to know if Test mode support  CSIx_SENS_PRTCL=0x2or 0x3 instead of 0x1? customer want to know if Test mode support CSIx_SENS_DATA_FORMAT=0x1or 0x2 instead of 0x0? Answer: CSI CM TEST MODE is working as below: 1,only ungated mode. 2,data width should be configured to 8 3,data format should be configured to rgb888 It cannot be other format such as bt656. It uses CSI1_TST_CTRL register to configure {R,G,B} 24 bit value and taking it as RGB888/YUV444 format for further process.  The generated image size is due to the configured width & height in the registers. i.MX6DL i.MX6Dual i.MX6Quad i.MX6S

Video- Power management on i.MX6 Sabre SDP with WEC7 by iWave Systems Windows Embedded Compact 7 (WEC7) BSP customizations by iWave Systems for Freescale’s SABRE SDP/B platform now supports power management. Power management was successfully developed for the i.MX6 multicore platform and tested for the standard suspend and resume functionalities. The processor enters into dormant mode and consumes the least power. As of now, iWave has reduced it to consume as much power as it is currently uses in Linux and Android. i.MX6Q has four CPU cores. The suspend power state not only turns off 3 CPU cores, but also puts the primary CPU on low power mode. On resuming, all 4 cores restart successfully.The process of Power management is being intelligently handled in order to reduce the power consumption to a greater extent. The Power consumption in the idle mode is 800mA whereas in the deep sleep mode it is 380mA, which is very much lesser than in the idle mode. Power Management for multicore processors can be used in a wide variety of handheld devices like tablets, video cameras, mobile phones and other entertainment solutions.  http://www.youtube.com/watch?v=5vED0_U20Cc General

Installing and Configuring QT Creator (Ubuntu) Qt Creator can be a very good IDE in order to develop great QT applications. This IDE does not only helps with syntax highlighting, access to examples and tutorials, but also helps you to configure different toolchains Qt binary versions and target options. First download the binary installer from: For 32 bits: $ wget http://releases.qt-project.org/qtcreator/2.6.2/qt-creator-linux-x86-opensource-2.6.2.bin For 64 bits: $ wget http://releases.qt-project.org/qtcreator/2.6.2/qt-creator-linux-x86_64-opensource-2.6.2.bin execute the binary $ ./qt-creator-linux-x86_64-opensource-2.6.2.bin Follow the Installer GUI and choose a location. Default options should be OK. in my case the installation was done here: $ /home/b35153/qtcreator-2.6.2/bin Open Qt Creator (in my case from command line, use "&" to regain control of the terminal) $./qtcreator & Open Tools -> Options Choose Build & Run  on the menu of the left. and Select the Compilers Tab Here you can add the toolchain GCC compiler of your convenience. It will appear in the "Manual"  section. Now click on Qt Version Tab.  Here you can add the Qmake that you had created with your Qt installation; for example, the Qt5 installation described here: Building QT for i.MX6 It will appear in the Manual section. In my case I have Qmake for PC and Qmake for i.MX6. Now click on Kits Tab Here you can create combinations of Compilers and Qmake, and also specify where do you want the executables to go. In my case here I combined the i.MX6 toolchain and the Qmake for I.MX6 i had created. I did not set up device configuration since the sysroot is already shared to my device via NFS, but you can configure it so the files are sent via ssh to your device. And that's It! Next time you load a project you can choose which Kit you want to work on, and it will be compiled just as you need. i.MX53 i.MX6_All Multimedia Re: Installing and Configuring QT Creator (Ubuntu) That's the link which I've already seen earlier Setup QT Creator with Yocto Build I already was a bit confused that the link has changed. Ok thank you, it's clear now for me. Re: Installing and Configuring QT Creator (Ubuntu) Have a look for this Setup QT Creator with Yocto Build  Re: Installing and Configuring QT Creator (Ubuntu) The links are working, but is still 2.8   Choose You need here: http://download.qt-project.org/official_releases/qtcreator/2.8/2.8.0/ Re: Installing and Configuring QT Creator (Ubuntu) Hi, I followed your instructions but already stumbled by downloading QTCreator. Seems like QT have changed the folder structure. Files can be found with bellow Links now. x86 http://download.qt-project.org/official_releases/qtcreator/2.6/2.6.2/qt-creator-linux-x86-opensource-2.6.2.bin x64 http://download.qt-project.org/official_releases/qtcreator/2.6/2.6.2/qt-creator-linux-x86_64-opensource-2.6.2.bin All other steps was working fine for me. Regards Re: Installing and Configuring QT Creator (Ubuntu) The examples are installed when you insstall   Qt5.   you can install Qt5 for the PC  to try the examples first from here Download Qt, the cross-platform application framework | Qt Project, and then compile Qt5 for i.MX  with the guide here in the community. https://community.freescale.com/docs/DOC-94066 If you install the version for PC (ubuntu linux)   you can find the examples at:  /Home/Qt/5.1.0/gcc_64/examples If you download and compile i.MX Qt5  you can find the examples at: /opt/qt5/examples Re: Installing and Configuring QT Creator (Ubuntu) Followed your instructions.  Program ran, but there are no examples.  Do you know where I can find them? Re: Installing and Configuring QT Creator (Ubuntu) Well I can give you a consulting service if you wish, otherwise you'll need to read the docs 😉 Re: Installing and Configuring QT Creator (Ubuntu) I'm sorry to say this but to follow these instructions is the sheer horror. You start with a tab in the browser and ends after a short time at 7 tabs open and completely lose track! Any guidance expects the exact execution of another instruction, which again presupposes the execution of another instruction. :smileyconfused: Re: Installing and Configuring QT Creator (Ubuntu) You should take a look in Yocto's documentatation: http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-an-existing-toolchain-tarball" title="http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#using-an-existing-toolchain-tarball Re: Installing and Configuring QT Creator (Ubuntu) I do "bitbake meta-toolchain-qt" Results are joerg@ubuntu1204:~/yocto/rootfs_builder/build/tmp/deploy/images$ ls modules--3.0.35-r0-nitrogen6x-20130629065000.tgz    uImage--3.0.35-r0-nitrogen6x-20130629065000.bin README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt  uImage-nitrogen6x.bin uImage iḿ not sure what to do with that? Re: Installing and Configuring QT Creator (Ubuntu) meta-toolchain-qt Re: Installing and Configuring QT Creator (Ubuntu) Hello Otavio, QT4 should be good for me. I have to build a special image with yocto? Re: Installing and Configuring QT Creator (Ubuntu) Yocto currently is able to build a Qt toolchain for Qt4 but not yet for Qt5.     Re: Installing and Configuring QT Creator (Ubuntu) You need the qmake compiled for i.MX6 in order to create Qt5 programs that run in the i.MX6 processor. Otherwise you will create programs that run on the PC. I dont remember if the yocto build also creates this special qmake.  It should be in /opt/qt5/bin  or something similar Re: Installing and Configuring QT Creator (Ubuntu) Isn't it possible to set up QT Creator without building own make for I.MX6? It is really complicated to build it while using things building with ltib and ltib is horror !!! Qt is build on Yocto image. regards Joerg

i.MX6 D/Q L3.035_1.0.2 Patch Release The i.MX 6 D/Q L3.035_1.0.2 patch release is now available on the www.freescale.com ·         Files available # Name Description 1 L3.0.35_1.0.2_LDO_PATCH This patch release is based on the i.MX 6Dual/6Quad Linux   12.09.01 release. The purpose of this patch release is to manage the LDO and   PMIC ramp-up time correctly. i.MX6Dual i.MX6Quad

Embedded Image Processing - Color Segmentation on i.MX51 Freescale's ARM Processor General