Connect any Android-based M2M device seamlessly with Device Cloud by Etherios and instantly build solutions for the Internet of Things (IoT). This set of libraries, plug-ins, samples and tools simplifies the development of Device Cloud applications for Android devices (Android version 2.2 and later). Easy and immediate integration of IoT cloud connectivity into applications Supports any Android device version 2.2 and greater Two-way messaging for full cloud-to-device messaging and control Device management and troubleshooting tools including configuration edits, firmware updates and device reboots Application development tools Remote file system management Secure connections Installation via Eclipse Update Manager The download includes:  Eclipse plug-ins that extend the functionality of the IDE, simplifying development Cloud Connector for Android library, including an API that allows Device Cloud communication with just a few lines of code Examples and demos (Android and Web applications), with source code included Comprehensive documentation, including a Getting Started Guide, a General Users Manual and an API reference Visit Cloud Connector for Android and download the free Cloud Connector for Android. For an overview of the Device Cloud by Etherios IoT solution, please also take a look at Device Cloud: Driving the Internet of ANYthing

element14 presents the newly launched SABRE Lite evaluation platform featuring the powerful i.MX6 Quad-Core multimedia application processor from Freescale Semiconductor. The processor integrates ARM Cortex™-A9 kernel at 1GHz with rich peripheral interfaces such as 10/100/Gb Ethernet port, HDMI, LVDS, parallel RGB interface, touch screen interface, analog headphone/microphone, micro TF and SD card interface, USB, serial port, interface, JTAG, camera interface, and Android buttons.     The SABRE Lite development board is a low-cost development platform based on Freescale’s I.MX 6Quad ARM Cortex-A9 application processor which encompasses a quad-core platform running up to 1 GHz with 1 MB of L2 cache and 64-bit DDR3 or 2-ch., 32-bit LPDDR2 support. Integrated FlexCAN, MLB busses, PCI Express® and SATA-2 provide excellent connectivity, while integration of LVDS, MIPI display port, MIPI camera port and HDMI v1.4 makes it an ideal platform for leading-edge consumer, automotive and industrial multimedia applications.     The i.MX6 series unleashes a scalable multicore platform that includes single-, dual- and quadcore families based on the ARM Cortex™-A9 architecture for next-generation consumer, industrial and automotive applications. By combining the power-efficient processing capabilities of the ARM Cortex-A9 architecture with leading edge 3D and 2D graphics, as well as high-definition video, the i.MX6 series provides a new level of multimedia performance to enable an unbounded next-generation user experience.     The i.MX6 series also brings world-class integration with high-performance multimedia processing, making it the ideal platform for future multimedia-centric applications such as tablets, smart books and human-machine interface (HMI). With integrated options including LVDS, HDMI v1.4, MIPI DSI display port and MIPI CSI-2 camera port, as well as the ability to support up to four screens simultaneously, the i.MX6 series provides the flexibility to develop tailored, market-specific solutions with faster time to market.   To order this $179 solution please click here Key Applications: Netbooks (web tablets), Nettops (Internet desktop devices), High-end mobile Internet devices (MID), High-end PDAs, High-end portable media players (PMP) with HD video capability, Gaming consoles, Portable navigation devices (PNDs), Industrial control, Test and measurement (T&M), Single board computers (SBCs), Tablets, eReaders, Smartbooks, Automotive infotainment, HMI, Portable medical, IPTV, IP phones and Home energy management systems.             Click here for more inforamtion.

                                                  (Images are scaled to actual size) Accelerate time-to-market and optimize cost by using proven solutions from toradex​ We offer off-the-shelf System on Modules/ Computer on Modules and Customized SBCs based on i.MX 6Q, i.MX 6D, i.MX 6DL and i.MX 6S processors at competitive prices. These modules exposes majority of the extensive interfaces supported by i.MX 6 processors. Complemented with these robust and small form-factor modules, we also offer extensive online technical resources, free premium support, and open-source carrier board designs. BSPs and libraries for Windows Embedded Compact and Linux are available at no cost. For more information on our i.MX 6 solutions, please check https://www.toradex.com/products/freescale-i.mx6

NXP i.MX8M Mini SoC, quad-core ARM Cortex-A53, 1.8GHz Integrated 2D/3D GPU and 1080p VPU Up to 4GB LPDDR4 and 64GB eMMC Certified dual-band WiFi 802.11ac, BT 4.2 GbE, PCIe, 2x USB, 4x UART, 60x GPIO Tiny size and weight - 28 x 38 x 5 mm, 7 gram Yocto Linux and Android - BSPs and ready-to-run images Industrial temperature range: -40° to 85° C 10-year availability CompuLab's UCM-iMX8M-Mini is a miniature System-on-Module board designed for integration into industrial embedded applications. Measuring just 28 x 38 mm, UCM-iMX8M-Mini is an ideal solution for space constrained and portable systems. UCM-iMX8M-Mini Detailed Spec UCM-iMX8M-Mini Development Kit UCM-iMX8M-Mini Online Pricing

This video shows how the Crank Storyboard application framework is well suited to run on our i.MX7 Nitrogen7 board. Demo details This demonstration is based on the following: Nitrogen7 board​​ 800×480 LCD display​ Resistive touch Yocto Jethro release Linux kernel 3.14.52 Crank Software details Crank Software Inc. is an innovator in embedded graphical user interface (GUI) solutions. Their products and services enable R&D teams and UI Designers to quickly and collaboratively develop rich animated user interfaces for resource-constrained embedded. The demo above relies on the Crank Storyboard Engine which is: Multi-platform Supported on Linux, Android, QNX, WindowsCE among others Built for embedded Storyboard Embedded Engine scales from low-end to high-end processors 3D optimized For higher end products embedding a GPU For more information, please visit: https://boundarydevices.com/crank-software-demo-on-nitrogen7/

Technologic Systems carries a full spectrum of off-the-shelf products powered by the NXP/Freescale i.MX 6 ARM CPU including single board computers, computer-on-modules, and touch panel PCs.  Read about it in their iMX6 Boards, Modules, and Touch Panels Portfolio​ page.  The portfolio features off-the-shelf products: TS-4900 High Performance WiFi & Bluetooth Enabled 1 GHz i.MX6 Computer-on-Module TS-7970 WiFi & Bluetooth Enabled 1 GHz i.MX6 Single Board Computer TS-TPC-7990 7" Capacitive or Resistive Touch Panel PC TS-TPC-8950-4900 10'' High Performance Mountable Touch Panel PC TS-8550 TS-SOCKET Development Baseboard All i.MX6 products come with a choice of Linux, Windows, Android, or QNX operating system, have a plethora of industry standard connections, industrial temperature ranges, and long lifecycle guarantee.  If an off-the-shelf solution doesn't quite match your needs, custom hardware and software engineering services are also available. Thanks, Derek Hildreth eBusiness Manager Technologic Systems www.embeddedarm.com About Technologic Systems Technologic Systems has been in business for 32 years, helping more than 8000 OEM customers and building over a hundred COTS products that have never been discontinued. Our commitment to excellent products, low prices, and exceptional customer support has allowed our business to flourish in a very competitive marketplace. We offer a wide variety of single board computers, computer-on-modules, touch panel computers, PC/104 and other peripherals, and industrial controllers that satisfy most embedded project requirements. We also offer custom configurations and design services. We specialize in the ARM and X86 architectures, FPGA IP-core design, and open-source software support, providing advanced custom solutions using hardware-software co-design strategies.

iWave provides Android Lollipop and Linux 3.14 kernel BSP upgrades for its i.MX6 based products. iMX6 Board: From the launch of i.MX6 application processors, iWave Systems, a global leading SOM supplier has launched many variations of i.MX6 CPU modules and an SBC board catering to Industrial, automotive and medical applications. Complying with the Qseven R2.0 specification, the i.MX6 Q7 SOM supports industrial grade operation with 70mmx70mm size. The i.MX6 MXM SOM supports automotive grade i.MX6 CPU and the automotive specific interfaces with 314 pin MXM2 connector pinout in 85mmx85mm form factor. The recently launched i.MX6 SODIMM SOM module supports both commercial & industrial operating temperature with very compact form factor of 67.6mmx37mm. iMX6 Board Single Board Computer: Measuring 100mmx70mm, the Pico ITX size i.MX6 SBC board supports on-board connectors for all the i.MX6 interfaces with option to expand IOs through expansion connector.  All these three different form factor System on Modules and Single Board Computers are supported with different i.MX6 CPU variations such as Quad, Dual, Dual Lite & Solo. Besides this i.MX6 Qseven modules also supports i.MX6 Quad Plus and i.MX6 Dual plus CPU configurations. To enable quick prototyping of these different form factor SOMs, iWave systems supports independent development kit variation for each form factor SOMs with Linux, Android and WEC7* BSP support. These development kits help customer to save up to 60% of new product development cycle sothat the quick time to market can be achieved. All these i.MX6 products are getting Android Lollipop and Linux 3.14 kernel BSP upgrades which will be available for customers by the first quarter of 2016.

Since the launch of i.MX6 application processors, iWave Systems, one of the global leading SOM suppliers has launched many variations of i.MX6 CPU modules and an SBC boards catering to Industrial, automotive and medical applications.@ ! Complying with the Qseven R2.0 specification, the i.MX6 Q7 SOM supports industrial grade operation with 70mmx70mm size. The i.MX6 MXM SOMsupports automotive grade i.MX6 CPU and the automotive specific interfaces with 314 pin MXM2 connector pinout in 85mmx85mm form factor. The recently launched i.MX6 SODIMM SOM module supports both commercial & industrial operating temperature with very compact form factor of 67.6mmx37mm. Measuring 100mmx70mm, the Pico ITX size i.MX6 SBC board supports on-board connectors for all the i.MX6 interfaces with option to expand IOs through expansion connector. All these three different form factor SOMs and SBCs are supported with different i.MX6 CPU variations such as Quad, Dual, Dual Lite & Solo. Besides this i.MX6 Qseven modules also supports i.MX6 Quad Plus and i.MX6 Dual plus CPU configurations. Besides the main i.MX6 CPU portfolio, iWave Systems also launched the i.MX6UL SOM in very small SODIMM form factor with 67.6mmx29mm size for the power & cost constrained commercial & Industrial applications. Both the I.MX6 & i.MX6UL SODIMM SOMs are made pin compatible so that the customers can leverage scalability & software compatibility of the wide range of i.MX6 products. To enable quick prototyping of these different form factor SOMs, iWave Systems supports independent development kit variation for each form factor SOMs with Linux, Android and WEC7* BSP support. These development kits help customer to save up to 60% of new product development cycle so that the quick time to market can be achieved. iWave Systems also offers custom SOM & SBC development with turnkey manufacturing services based on its wide range of i.MX6 product development expertise. Please contact iWave Systems for additional details.

Introduction Currently there is not an easy procedure to build Qt 5.1 with hardware acceleration support for Freescale i.MX6 platform. This document describes the steps necessary to download all the prerequisite oftware, build Qt 5.1 code and examples, and verify the hardware acceleration support status. Required Software 1.     To start building, we need some development tools. This build is verified on LTIB (L3.0.35_4.0.0_130424_source.tar.gz downloaded from FreeScale website) and cross-compiled on a Ubuntu 12.04 64-bit PC. Verify that gpu-viv-bin-mx6q option is enabled in the LTIB configuration.                    $ mkdir -p ~/BSP                    $ cd ~/BSP                    $ tar -xzvf L3.0.35_4.0.0_130424_source.tar.gz   2.     Download Qt 5.1.1 source code from the Qt-project website. Create a build directory and extract the content in it.                    $ mkdir -p ~/Qt5                    $ cd ~/Qt5                    $ tar -xJvf qtbase-opensource-src-5.1.1.tar.xz Build procedure: 1.     Enter the Qt5 build directory and create a configuration script as follows:                   $ cd ~/Qt5/qt-everywhere-opensource-src-5.1.1/qtbase                   $ vi config.imx6                   #!/bin/sh                   ./configure -opensource -confirm-license -make libs -device imx6 \                   -device-option CROSS_COMPILE=\                   /opt/freescale/usr/local/gcc-4.6.2-glibc-2.13-linaro-multilib-2011.12/fsl-linaro-toolchain/bin/arm-fsl-linux-gnueabi- \                  -no-pch -no-opengl -no-icu                  -no-c++11 \                  -opengl es2 \                  -eglfs \                  -compile-examples \   2.     Edit the device configuration to specify the root file system of the BSP. Make sure the config file contains lines that match with what lists below                    $ cd ~/Qt5/qt-everywhere-opensource-src-5.1.1/qtbase/mkspecs/devices/linux-imx6-g++                    $ vi qmake.conf                    ROOTFS=/home/trainee/BSP/L3.0.35_4.0.0_130424_source/ltib/rootfs                    QMAKE_INCDIR           += $$ROOTFS/usr/include                    QMAKE_LIBDIR           += $$ROOTFS/usr/lib                    QMAKE_LFLAGS           += -Wl,-rpath-link,$$ROOTFS/usr/lib   3.     Run the configuration script and make sure that Qt5 has openGL ES 2.0 support when it is complete. Note that you must run 'make confclean' to remove the previous configuration when any hanges are made to the script.                 $ ./config.imx6                           This is the Qt Open Source Edition.                           You are licensed to use this software under the terms of  the Lesser GNU General Public License (LGPL) versions 2.1.                           You have already accepted the terms of the  license.                           Creating qmake...                            ….                            ….                            Support enabled for:                            Accessibility  .......... yes                            ….                            OpenGL .................. yes (OpenGL ES 2.x)                             ….                            Qt is now configured for building. Just run 'make'.             Once everything is built, you must run 'make install'.             Qt will be installed into             /home/trainee/BSP/L3.0.35_4.0.0_130424_source/ltib/rootfs/usr/local/Qt5.1.1             Prior to reconfiguration, make sure you remove any leftovers from             the previous build.   4.     Do a build. Note that all the libraries are copied to the appropriate directories in the root file system.                    $ make all -j8                    $INSTALL_ROOT=/home/trainee/BSP/L3.0.35_4.0.0_130424_source/ltib/rootfs/ sudo                    make install        5.     Build the examples                $ cd examples                $ make   6.     Copy an example (hellogl_es2) used to demonstrate openGL ES to the root file system.                $ sudo cp opengl/hellogl_es2/hellogl_es2                /home/trainee/BSP/L3.0.35_4.0.0_130424_source/ltib/rootfs/    Verify h/w acceleration support: 1.     Boot the board and verify that the galcore module is installed               $ cat /proc/devices | grep galcore               $ ls /dev/galcore   2.     Set up the required Qt environment               $ export QT_PLUGIN_PATH=/usr/local/Qt-5.1.1/plugins/        3.     Run the example. You shall see a rotating Qt logo on the display.               $ cd /               $ ./hellogl_es       4.     Run top command and it shows the application running with a very low (0 – 1 %) cpu usage.               $ top                 PID PPID USER     STAT   VSZ %VSZ CPU       %CPU COMMAND                                      2820 2809  root         S         188m 21.5   0              0.7       ./hellogl_es2 About Adeneo Embedded Adeneo Embedded provides system integration, design, support and training services to companies seeking world-class expertise in embedded solutions using high-performance architectures. For over 10 years, Adeneo Embedded has helped clients, in all stages of development; create profitable, feature-rich products that incorporate software and hardware solutions based on Android, Embedded Linux, Windows Embedded or Windows Mobile operating systems. Close working partnerships with industry-leading silicon and software vendors allow Adeneo Embedded to apply its experience to a wide range of embedded solutions for the automotive, industrial, medical,  multi-media, navigation,  networking, mobile and wireless markets. Adeneo Embedded has a global sales and support network backed by engineering offices in North America and Europe. Further information For more information about Adeneo Embedded competences, products and services around Windows Embedded technologies: Ä  visit Adeneo Embedded dedicated web site               www.adeneo-embedded.com Ä  Adeneo Embedded General sales contact                 sales@adeneo-embedded.com For a local contact in Ä  Europe, please contact Jeremy Delicato                   jdelicato@adeneo-embedded.com Ä  America, please contact Mike Ruiz                            mruiz@adeneo-embedded.com

iWave offers i.MX6 Qseven modules with latest 3.10.17 based Linux kernel with Yocto support. This official Yocto release is based on 3.10.17 kernel. The BSP will support for all the variants of i.MX6 CPU, i.e Quad, Dual, Dual Lite and Solo Qseven modules. The alpha release for the same is now available on request. This release supports the below features on our Qseven Development Platform: Freescale i.MX6 Q/D/DL/S CPU DDR3 SDRAM SPI Boot flash eMMC Flash Debug Console SD Ports USB Ports Ethernet PCIe HDMI 7”LVDS display For further information or enquiries please write to mktg@iwavesystems.com or visit our website www.iwavesystems.com

Hi, RAW is still often used in automotive applications. If you are doing bare metal code and if you use OS (QNX, GreenHills integrity), it is often a pain to boot from NAND. On SABRE AI, you have a NAND socket, this document will present you the basics command to reverse engineer the NAND boot setup of a SABRE AI. KOBS-NG What you can do first is understand kobs-ng application, and try to understand it...sources are available on freescale's GIT: http://sw-git.freescale.net/cgi-bin/gitweb.cgi?p=linux-kobs.git;a=summary Anyway, the sequencing is not obvious... Modified MFGtool (see enclosed archive) What you can do also it to program a NAND flash on a SABRE board for instance and read back the NAND flash. First configure your SABRE AI board: S2: 0001 S1: 0001100000  (I use 8 BBT and FCB to be more secure) BOOT_MODE: 0010 (if your NAND flash is not already programmed, otherwise 0100) Copy my mfgtool (Works only with i.MX6 Solo part), and unzip it. Plug  a micro USB cable and a RS232 cable, configure your hyperterminal as usual. Launch mfgtool and press start: Wait the end of programmation: Note: I did modify ucl2.xml file to have 8 BBT and FCB (see S1 configuration above, and "--search_exponent=3" --> 2^3=8 instead of default 2^2=4 ) and I did add the "-v" option in ucl2.xml file to have the verbose mode (thus memory addresses of FCB, BBT and more are displayed) ---> you have to go on the extreme right of the lines below... depending of the witdth of your screen): <!--burn the uboot to NAND: -->    <CMD   state = "Updater"   type = "push"   body = "send"   file = "files/u-boot-mx6solo-sabreauto-nand.bin" > Sending U-Boot </CMD>   <CMD   state = "Updater"   type = "push"   body = "$ kobs-ng init -v --search_exponent=3 --chip_0_device_path=/dev/mtd0 $FILE" > Flashing Bootloader </CMD> ‍‍‍‍‍‍‍‍‍‍‍ Set BOOT_MODE switches: 0010 and press reset. After u-boot startup press a key in the terminal to stop execution. Now you can explore your NAND! have a look in the enclosed "mx6Solo_RAW_NAND_SABRE_AI_programming_verbose.txt" file, you have all the adressses of BBT, FCB, etc...: Firmware: image #0 @ 0x400000 size 0x2a000 - available 0x600000 Firmware: image #1 @ 0xa00000 size 0x2a000 - available 0x600000 -------------- Start to write the [ FCB ] ----- mtd: erasing @0:0x0-0x80000 mtd: Writing FCB0 [ @0:0x0 ] (10e0) * mtd: Writing FCB1 [ @0:0x40000 ] (10e0) * mtd: erasing @0:0x80000-0x100000 mtd: Writing FCB2 [ @0:0x80000 ] (10e0) * mtd: Writing FCB3 [ @0:0xc0000 ] (10e0) * mtd: erasing @0:0x100000-0x180000 mtd: Writing FCB4 [ @0:0x100000 ] (10e0) * mtd: Writing FCB5 [ @0:0x140000 ] (10e0) * mtd: erasing @0:0x180000-0x200000 mtd: Writing FCB6 [ @0:0x180000 ] (10e0) * mtd: Writing FCB7 [ @0:0x1c0000 ] (10e0) * mtd_commit_bcb(FCB): status 0   -------------- Start to write the [ DBBT ] ----- mtd: erasing @0:0x200000-0x280000 mtd: Writing DBBT0 [ @0:0x200000 ] (1000) * mtd: Writing DBBT1 [ @0:0x240000 ] (1000) * mtd: erasing @0:0x280000-0x300000 mtd: Writing DBBT2 [ @0:0x280000 ] (1000) * mtd: Writing DBBT3 [ @0:0x2c0000 ] (1000) * mtd: erasing @0:0x300000-0x380000 mtd: Writing DBBT4 [ @0:0x300000 ] (1000) * mtd: Writing DBBT5 [ @0:0x340000 ] (1000) * mtd: erasing @0:0x380000-0x400000 mtd: Writing DBBT6 [ @0:0x380000 ] (1000) * mtd: Writing DBBT7 [ @0:0x3c0000 ] (1000) * mtd_commit_bcb(DBBT): status 0‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ to read the NAND, I read it in internal OCRAM ( address is 0x918000 for i.MX6DL and Solo) and then I display it): You can read the DCD of one of the boot image (first one is at address 0x400000 as you can see in the enclosed text file): Firmware: image #0 @ 0x400000 size 0x2a000 - available 0x600000 Firmware: image #1 @ 0xa00000 size 0x2a000 - available 0x600000‍‍‍‍‍‍ So, let's read the begenning of the image... at offset 0x400, you'll see the barker code of the DCD: 0x402000D1: MX6SOLO SABREAUTO U-Boot > nand read 0x918000 0x400000 0x800 NAND read: device 0 offset 0x400000, size 0x800 2048 bytes read: OK MX6SOLO SABREAUTO U-Boot > md 0x918000 0x500 00918000: ea000186 00000000 00000000 00000000 ................ 00918010: 00000000 00000000 00000000 00000000 ................ 00918020: 00000000 00000000 00000000 00000000 ................ 00918030: 00000000 00000000 00000000 00000000 ................ 00918040: 00000000 00000000 00000000 00000000 ................ 00918050: 00000000 00000000 00000000 00000000 ................ 00918060: 00000000 00000000 00000000 00000000 ................ 00918070: 00000000 00000000 00000000 00000000 ................ 00918080: 00000000 00000000 00000000 00000000 ................ 00918090: 00000000 00000000 00000000 00000000 ................ 009180a0: 00000000 00000000 00000000 00000000 ................ 009180b0: 00000000 00000000 00000000 00000000 ................ 009180c0: 00000000 00000000 00000000 00000000 ................ 009180d0: 00000000 00000000 00000000 00000000 ................ 009180e0: 00000000 00000000 00000000 00000000 ................ 009180f0: 00000000 00000000 00000000 00000000 ................ 00918100: 00000000 00000000 00000000 00000000 ................ 00918110: 00000000 00000000 00000000 00000000 ................ 00918120: 00000000 00000000 00000000 00000000 ................ 00918130: 00000000 00000000 00000000 00000000 ................ 00918140: 00000000 00000000 00000000 00000000 ................ 00918150: 00000000 00000000 00000000 00000000 ................ 00918160: 00000000 00000000 00000000 00000000 ................ 00918170: 00000000 00000000 00000000 00000000 ................ 00918180: 00000000 00000000 00000000 00000000 ................ 00918190: 00000000 00000000 00000000 00000000 ................ 009181a0: 00000000 00000000 00000000 00000000 ................ 009181b0: 00000000 00000000 00000000 00000000 ................ 009181c0: 00000000 00000000 00000000 00000000 ................ 009181d0: 00000000 00000000 00000000 00000000 ................ 009181e0: 00000000 00000000 00000000 00000000 ................ 009181f0: 00000000 00000000 00000000 00000000 ................ 00918200: 00000000 00000000 00000000 00000000 ................ 00918210: 00000000 00000000 00000000 00000000 ................ 00918220: 00000000 00000000 00000000 00000000 ................ 00918230: 00000000 00000000 00000000 00000000 ................ 00918240: 00000000 00000000 00000000 00000000 ................ 00918250: 00000000 00000000 00000000 00000000 ................ 00918260: 00000000 00000000 00000000 00000000 ................ 00918270: 00000000 00000000 00000000 00000000 ................ 00918280: 00000000 00000000 00000000 00000000 ................ 00918290: 00000000 00000000 00000000 00000000 ................ 009182a0: 00000000 00000000 00000000 00000000 ................ 009182b0: 00000000 00000000 00000000 00000000 ................ 009182c0: 00000000 00000000 00000000 00000000 ................ 009182d0: 00000000 00000000 00000000 00000000 ................ 009182e0: 00000000 00000000 00000000 00000000 ................ 009182f0: 00000000 00000000 00000000 00000000 ................ 00918300: 00000000 00000000 00000000 00000000 ................ 00918310: 00000000 00000000 00000000 00000000 ................ 00918320: 00000000 00000000 00000000 00000000 ................ 00918330: 00000000 00000000 00000000 00000000 ................ 00918340: 00000000 00000000 00000000 00000000 ................ 00918350: 00000000 00000000 00000000 00000000 ................ 00918360: 00000000 00000000 00000000 00000000 ................ 00918370: 00000000 00000000 00000000 00000000 ................ 00918380: 00000000 00000000 00000000 00000000 ................ 00918390: 00000000 00000000 00000000 00000000 ................ 009183a0: 00000000 00000000 00000000 00000000 ................ 009183b0: 00000000 00000000 00000000 00000000 ................ 009183c0: 00000000 00000000 00000000 00000000 ................ 009183d0: 00000000 00000000 00000000 00000000 ................ 009183e0: 00000000 00000000 00000000 00000000 ................ 009183f0: 00000000 00000000 00000000 00000000 ................ 00918400: 402000d1 27800620 00000000 2780042c .. @ ..'....,..' 00918410: 27800420 27800400 00000000 00000000 ..'...'........ 00918420: 27800000 0002a0a4 00000000 40e001d2 ...'...........@ 00918430: 04dc01cc 74070e02 00000c00 54070e02 .......t.......T 00918440: 00000000 ac040e02 30000000 b0040e02 ...........0.... 00918450: 30000000 64040e02 30000000 90040e02 ...0...d...0.... 00918460: 30000000 4c070e02 30000000 94040e02 ...0...L...0.... 00918470: 30000000 a0040e02 00000000 b4040e02 ...0............ 00918480: 30000000 b8040e02 30000000 6c070e02 ...0.......0...l 00918490: 30000000 50070e02 00000200 bc040e02 ...0...P........ 009184a0: 28000000 c0040e02 28000000 c4040e02 ...(.......(.... 009184b0: 28000000 c8040e02 28000000 60070e02 ...(.......(...` 009184c0: 00000200 64070e02 28000000 70070e02 .......d...(...p 009184d0: 28000000 78070e02 28000000 7c070e02 ...(...x...(...| 009184e0: 28000000 70040e02 28000000 74040e02 ...(...p...(...t 009184f0: 28000000 78040e02 28000000 7c040e02 ...(...x...(...| 00918500: 28000000 00081b02 030039a1 0c081b02 ...(.....9...... 00918510: 1f001f00 10081b02 1f001f00 3c081b02 ...............< 00918520: 16021c42 40081b02 7a017b01 48081b02 B......@.{.z...H 00918530: 4c4e4a4b 50081b02 34333f3f 1c081b02 KJNL...P??34.... 00918540: 33333333 20081b02 33333333 24081b02 3333... 3333...$ 00918550: 33333333 28081b02 33333333 b8081b02 3333...(3333.... 00918560: 00080000 04001b02 25000200 08001b02 ...........%.... 00918570: 30303300 0c001b02 13536b67 10001b02 .300....gkS..... 00918580: 638b6eb6 14001b02 db00ff01 18001b02 .n.c............ 00918590: 40170000 1c001b02 00800000 2c001b02 ...@..........., 009185a0: d2260000 30001b02 23106b00 40001b02 ..&....0.k.#...@ 009185b0: 27000000 00001b02 00001984 1c001b02 ...'............ 009185c0: 32800004 1c001b02 33800000 1c001b02 ...2.......3.... [ETC....] MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Let's check the persistent bit (i.MX6S or DL) PERSIST_SECONDARY_BOOT, reflecting from which image you boot: MX6SOLO SABREAUTO U-Boot > md 0x20D8044 1 020d8044: 40000000    ...@ MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍ Bit 30 is 0, meaning you boot from first image Let's erase one boot image to see it it still boot (you have 2 boot images) MX6SOLO SABREAUTO U-Boot > nand erase 0x400000 0x512 NAND erase: device 0 offset 0x400000, size 0x512 Warning: Erase size 0x00000512 smaller than one erase block 0x00080000 Erasing 0x00080000 instead Erasing at 0x400000 -- 100% complete. OK MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Presss the reset button of your board to see if the board still start. If you read the PERSIST_SECONDARY_BOOT persistent bit, you'll see you boot from the second image as bit 30 is active: MX6SOLO SABREAUTO U-Boot > md 0x20D8044 1 020d8044: 40000000    ...@ MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍ If you erase the second image (address 0xa00000, board will not boot as you only have 2 images). What you can do thenis read your FCB (flash configuration) with the following commands in u-boot prompt (sometimes the first read fails! so try again): WARNING: this was for a 2009 u-boot, in newer version (2016 for instance) you have to do a "nand dump" otherwise it will return an error (FAIL -74), see [Uboot] Nand read from offset xxx failed -74  MX6SOLO SABREAUTO U-Boot > nand read 0x918000 0x40000 0x800 NAND read: device 0 offset 0x40000, size 0x800 NAND read from offset 40000 failed -74 0 bytes read: ERROR MX6SOLO SABREAUTO U-Boot > nand read 0x918000 0x40000 0x800 NAND read: device 0 offset 0x40000, size 0x800 2048 bytes read: OK MX6SOLO SABREAUTO U-Boot > md 0x918000 0x100 00918000: fc000000 4346ffff 00002042 3c500100 ......FCB ....P< 00918010: 00000619 10000000 10e00000 00800000 ................ 00918020: 00000000 00000000 00000000 00080000 ................ 00918030: 02000000 02000000 00080000 000a0000 ................ 00918040: 00070000 00000000 00000000 00000000 ................ 00918050: 00000000 00000000 00000000 00000000 ................ 00918060: 00000000 00000000 04000000 0a000000 ................ 00918070: 002a0000 002a0000 02000000 0f400000 ..*...*.......@. 00918080: 00000000 10000000 00000000 00000000 ................ 00918090: 00000000 00000000 00000000 00000000 ................ 009180a0: 00000000 00000000 00000000 00000000 ................ 009180b0: 00000000 00000000 00000000 00000000 ................ 009180c0: 00000000 00000000 00000000 00000000 ................ 009180d0: 00000000 00000000 00000000 00000000 ................ 009180e0: 00000000 00000000 00000000 00000000 ................ 009180f0: 00000000 00000000 00000000 00000000 ................ 00918100: 00000000 00000000 00000000 00000000 ................ 00918110: 00000000 00000000 00000000 00000000 ................ 00918120: 00000000 00000000 00000000 00000000 ................ 00918130: 00000000 00000000 00000000 00000000 ................ 00918140: 00000000 00000000 00000000 00000000 ................ 00918150: 00000000 00000000 00000000 00000000 ................ 00918160: 00000000 00000000 00000000 00000000 ................ 00918170: 00000000 00000000 00000000 00000000 ................ 00918180: 00000000 00000000 00000000 00000000 ................ 00918190: 00000000 00000000 00000000 00000000 ................ 009181a0: 00000000 00000000 00000000 00000000 ................ 009181b0: 00000000 00000000 00000000 00000000 ................ 009181c0: 00000000 00000000 00000000 00000000 ................ 009181d0: 00000000 00000000 00000000 00000000 ................ 009181e0: 00000000 00000000 00000000 00000000 ................ 009181f0: 00000000 00000000 00000000 00000000 ................ 00918200: 00001a1c 0000000e 00000000 00000000 ................ 00918210: 00000000 00000019 00001600 00001600 ................ 00918220: 00000019 0000000f 00000019 00000000 ................ 00918230: 00000000 00000000 00000000 00000000 ................ 00918240: 00000000 00000000 00000000 00000000 ................ 00918250: 00001300 00000f00 00000008 00000008 ................ 00918260: 00001600 00000015 00000000 00001a00 ................ 00918270: 00000000 00000000 00000000 00000000 ................ 00918280: 00000000 00000000 00000000 00000000 ................ 00918290: 00000000 00000000 00000000 00000000 ................ 009182a0: 00000000 00000000 00000000 00000000 ................ 009182b0: 00000000 00000000 00000000 00000000 ................ 009182c0: 00000000 00000000 00000000 00000000 ................ 009182d0: 00000000 00000000 00000000 00000000 ................ 009182e0: 00000000 00000000 00000000 00000000 ................ 009182f0: 00000000 00000000 00000000 00000000 ................ 00918300: 00000000 00000000 00000000 00000000 ................ 00918310: 00000000 00000000 00000000 00000000 ................ 00918320: 00000000 00000000 00000000 00000000 ................ 00918330: 00000000 00000000 00000000 00000000 ................ 00918340: 00000000 00000000 00000000 00000000 ................ 00918350: 00000000 00000000 00000000 00000000 ................ 00918360: 00000000 00000000 00000000 00000000 ................ 00918370: 00000000 00000000 00000000 00000000 ................ 00918380: 00000000 00000000 00000000 00000000 ................ 00918390: 00000000 00000000 00000000 00000000 ................ 009183a0: 00000000 00000000 00000000 00000000 ................ 009183b0: 00000000 00000000 00000000 00000000 ................ 009183c0: 00000000 00000000 00000000 00000000 ................ 009183d0: 00000000 00000000 00000000 00000000 ................ 009183e0: 00000000 00000000 00000000 00000000 ................ 009183f0: 00000000 00000000 00000000 00000000 ................ MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ If you read the addresses 0x000000, 0x40000, 0x80000, 0xc0000, 0x100000, 0x140000 or 0x180000 or 0x1c0000 you'll have a copy of the FCB in OCRAM (internal RAM) and then read the OCRAM. You can now try that the replication is working. Thus try to erase FCBs (in my case, with Micron MT29F16G08ABABAWP the minimum I can erase is 2 FCBs due to sector size of 0x80000, check it on your side), for u-boot after 2009 use "nand dump", see https://community.nxp.com/message/885233  : MX6SOLO SABREAUTO U-Boot > nand erase 0x0 0x512 NAND erase: device 0 offset 0x0, size 0x512 Warning: Erase size 0x00000512 smaller than one erase block 0x00080000 Erasing 0x00080000 instead Erasing at 0x0 -- 100% complete. OK MX6SOLO SABREAUTO U-Boot > nand erase 0x80000 0x512 NAND erase: device 0 offset 0x80000, size 0x512 Warning: Erase size 0x00000512 smaller than one erase block 0x00080000 Erasing 0x00080000 instead Erasing at 0x80000 -- 100% complete. OK MX6SOLO SABREAUTO U-Boot > nand erase 0x100000 0x512 NAND erase: device 0 offset 0x100000, size 0x512 Warning: Erase size 0x00000512 smaller than one erase block 0x00080000 Erasing 0x00080000 instead Erasing at 0x100000 -- 100% complete. OK MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ You have erase 6 FCB. If you press reset, you normallystill can boot the device (checkswitch S1 is configured like that: 0001100000). You can also read the bad block table. In enclosed "mx6Solo_RAW_NAND_SABRE_AI_programming_verbose.txt" you have addresses of the DBBT: 0x200000, 0x240000, 0x280000, 0x2c0000, 0x300000, 0x340000, 0x380000 and 0x3c0000: -------------- Start to write the [ DBBT ] ----- mtd: erasing @0:0x200000-0x280000 mtd: Writing DBBT0 [ @0:0x200000 ] (1000) * mtd: Writing DBBT1 [ @0:0x240000 ] (1000) * mtd: erasing @0:0x280000-0x300000 mtd: Writing DBBT2 [ @0:0x280000 ] (1000) * mtd: Writing DBBT3 [ @0:0x2c0000 ] (1000) * mtd: erasing mtd: Writing DBBT4 [ @0:0x300000 ] (1000) * mtd: Writing DBBT5 [ @0:0x340000 ] (1000) * mtd: erasing @0:0x380000-0x400000 mtd: Writing DBBT6 [ @0:0x380000 ] (1000) * mtd: Writing DBBT7 [ @0:0x3c0000 ] (1000) * mtd_commit_bcb(DBBT): status 0‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ now read a DBBT in u-boot (as already mentionned, sometimes nand read failed, so try again!): MX6SOLO SABREAUTO U-Boot > nand read 0x918000 0x280000 0x800 NAND read: device 0 offset 0x280000, size 0x800 2048 bytes read: OK MX6SOLO SABREAUTO U-Boot > md 0x918000 0x80 00918000: 00000000 54424244 01000000 00000000 ....DBBT........ 00918010: 00000000 00000000 00000000 00000000 ................ 00918020: 00000000 00000000 00000000 00000000 ................ 00918030: 00000000 00000000 00000000 00000000 ................ 00918040: 00000000 00000000 00000000 00000000 ................ 00918050: 00000000 00000000 00000000 00000000 ................ 00918060: 00000000 00000000 00000000 00000000 ................ 00918070: 00000000 00000000 00000000 00000000 ................ 00918080: 00000000 00000000 00000000 00000000 ................ 00918090: 00000000 00000000 00000000 00000000 ................ 009180a0: 00000000 00000000 00000000 00000000 ................ 009180b0: 00000000 00000000 00000000 00000000 ................ 009180c0: 00000000 00000000 00000000 00000000 ................ 009180d0: 00000000 00000000 00000000 00000000 ................ 009180e0: 00000000 00000000 00000000 00000000 ................ 009180f0: 00000000 00000000 00000000 00000000 ................ 00918100: 00000000 00000000 00000000 00000000 ................ 00918110: 00000000 00000000 00000000 00000000 ................ 00918120: 00000000 00000000 00000000 00000000 ................ 00918130: 00000000 00000000 00000000 00000000 ................ 00918140: 00000000 00000000 00000000 00000000 ................ 00918150: 00000000 00000000 00000000 00000000 ................ 00918160: 00000000 00000000 00000000 00000000 ................ 00918170: 00000000 00000000 00000000 00000000 ................ 00918180: 00000000 00000000 00000000 00000000 ................ 00918190: 00000000 00000000 00000000 00000000 ................ 009181a0: 00000000 00000000 00000000 00000000 ................ 009181b0: 00000000 00000000 00000000 00000000 ................ 009181c0: 00000000 00000000 00000000 00000000 ................ 009181d0: 00000000 00000000 00000000 00000000 ................ 009181e0: 00000000 00000000 00000000 00000000 ................ 009181f0: 00000000 00000000 00000000 00000000 ................ MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Here I have no bad block (it is a SLC RAW NAND flash..). To be sure I have effectively erased 6 FCB, I will erase the 2 last one... thus I will not boot as all FCB tables will be erased(remove the usb cable otherwise mfgtool will restart): MX6SOLO SABREAUTO U-Boot > nand erase 0x180000 0x512 NAND erase: device 0 offset 0x180000, size 0x512 Warning: Erase size 0x00000512 smaller than one erase block 0x00080000 Erasing 0x00080000 instead Erasing at 0x180000 -- 100% complete. OK MX6SOLO SABREAUTO U-Boot >‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Reset the board... and it will not start as you have erased all the 8 FCB tables... you have to reprogram your board if you want to start again.

Hi nxp,      imx6q  mfgtools not work, can't open;      I download the mfgtools for android 7.1.2_2.0.0, but the size of mfgtools.zip only 4.28Mbytes, the sub dir is clean, no firmware and ucl;     the download from this: https://www.nxp.com/webapp/sps/download/preDownload.jsp  thanks

NXP i.MX7 processors, 1GHz Up to 2GB DDR3 and 32GB on-board eMMC LVDS, MIPI-DSI, Parallel RGB, up to 1920 x 1080 PCIe, 2x GbE, 5x USB2, 7x UART, 2x CAN, 124x GPIO Dual-band 802.11a/b/g/n WiFi and Bluetooth 4.1 BLE Yocto and Debian Linux, RTOS CL-SOM-iMX7 is a tiny System-on-Module (SoM) / Computer-on-Module (CoM) board designed to serve as a building block in embedded applications.   CL-SOM-iMX7 is built around the Freescale i.MX7 System-on-Chip featuring an advanced ARM Cortex-A7 CPU coupled with a dedicated real-time ARM Cortex-M4 MCU. The SoC is supplemented with up-to 2GB DDR3 and 32GB of on-board SLC NAND or eMMC storage.   Featuring a wide range of embedded interfaces, CL-SOM-iMX7 is a versatile platform for industrial automation and control systems. Dual Gbit Ethernet, 2x2 MIMO dual-band 802.11a/b/g/n WiFi and Bluetooth 4.1 make CL-SOM-iMX7 an excellent solution for networking, communications and IoT applications.   Low price makes CL-SOM-iMX7 an ideal selection for cost-sensitive systems, while its miniature size and low power consumption enable integration into portable and space-constrained designs.   CL-SOM-iMX7 is provided with a full Board Support Package and ready-to-run images for the Linux operating system. The CL-SOM-iMX7 BSP includes Linux kernel 3.14, Yocto Project file-system and U-Boot boot-loader. In addition, CompuLab will support CL-SOM-iMX7 with mainline Linux and upstream Yocto Project.   CL-SOM-iMX7 Detailed Spec CL-SOM-iMX7 Block Diagram CL-SOM-iMX7 Development Kit CL-SOM-iMX7 Online Pricing

Single Board Computers have always enjoyed serious attention in the field of Embedded Systems design. Ever since its introduction, its main intention was to devise a computer to inspire students to take up many new projects to explore the rich and wide world of Embedded Systems. With products like i.MX6 Pico ITX SBC, i.MX50 Quick Start Board, i.MX27 & PXA 270 SBCs, we at iWave Systems, are clearly a global competitor when it comes to promoting powerful ARM Cortex Single Board Computers. i.MX6 Pico ITX SBC: iWave's i.MX6 Dual Lite/Solo based Pico ITX SBC comes with all standard interfaces loaded into a single board with ultra-compact yet highly integrated platform that can be utilized across multiple embedded PC and industrial designs. It also provides an expansion header through which interfaces can be used according to their applications, measuring at just 100mm x 72mm. Pico ITX Advanced Learning Platform: As our product was aimed at inspiring young engineers to take up several projects in the field of Embedded Systems design iWave systems came up with a versatile and well equipped peripheral daughter board which can be plugged to the iWave’s i.MX6 Pico ITX SBC. This peripheral daughter board provides the extension to the I.MX6 Pico ITX board to evaluate several new display, sensor, communication & IO interfaces. The i.MX6 ARM Cortex A9 Pico ITX SBC with peripheral daughter board forms a powerful starter kit for the university students to plug & play several hardware & software components and make many new innovative concepts. The main interfaces supported by peripheral daughter board are as follows: Display Interfaces: A combination of a 7” TFT LCD display, 16x2 Character LCD and a 4 digit 7 segment display for display centric applications. Communication Interfaces: Additional RS232 & CAN ports for standard communication between external devices. Sensor module: Aimed specifically for engineering project works with various sensors like Ambient light sensors, Proximity sensors, Temperature sensor, Accelerometer and Magnetometer Motor Interface: A single driver that is capable of either driving two DC motors or a single Stepper motor Keypad Interface: Keypad scanner and a 4x4 keypad connector support External interfaces: The peripheral daughter board also following several interfaces CMOS camera interface support available on 17x2 row connector MIPI DSI interface support available on 10 pin MIPI connector SPI interface available on 6 pin SPI header Dual UART interface available on the 6 Pin UART header i.MX6 based Pico ITX Educational Kit For more information please contact: mktg@iwavesystems.com Website: www.iwavesystems.com

Windows Embedded Compact 7 Board Support Package for Freescale(R) Semiconductor’s Smart Applications Blueprint for Rapid Engineering (SABRE) Platform for Smart Devices based on the i.MX 6 Quad processor iWave Systems, a genuine embedded service provider, announces the official release of Windows Embedded Compact 7 Board Support Package (BSP) for Freescale(r) Semiconductor’s SABRE platform for smart devices based on the i.MX 6Quad applications processor. The BSP includes the advanced features which enable the Original Equipment Manufacturers (OEMs) to quickly prototype their solution around Freescale’s i.MX 6 series processor together with the flexibility and robustness offered by Windows Embedded Compact 7. With BSP support and customization offered by iWave, OEMs can build the advanced embedded devices with reduced cost and an early time to market approach. The BSP is targeted for Freescale’s SABRE platform for smart devices which is powered by the i.MX 6Quad applications processor and MMPF0100 Freescale PMIC. The BSP provides support for the advanced multimedia and connectivity options that can be used in high-performance and cost effective consumer, industrial and medical devices. The Windows Embedded Compact 7 BSP release for the SABRE platform supports the major features sets such as storage, networking, display and multimedia. Also the BSP can be quickly customized for the specific need of the customer, which results in quick time to market and lowers the overall development cost. BSP also includes the premium features such as Multimedia framework and OpenVG/OpenGL ES for graphics processing which utilizes the Video Processing Unit (VPU) and Graphics Processing Unit (GPU) capabilities of i.MX 6 series processors. These features make the BSP package ideal for rich multimedia and high-end 3D graphics-based devices such as consumer, industrial and medical tablets and IVI systems. The BSP supports SATA 3.0 and Standard SD/SDIO for storage, Ethernet for networking and LVDS/HDMI 1080p for display options. It also includes the driver for VPU to support the hardware based media compression and decompression (Codec) for industry standard media formats such as H.264, MPEG-4 and H.263 for multimedia applications. Windows Embedded Compact 7 brings in real-time computing capabilities along with support for multi-processing with Symmetric Multi-Processing (SMP), extended RAM support and rich user interface support with Microsoft Silverlight for Windows Embedded. Windows Embedded Compact 7 also provides the developers with rich tools for rapid application development and debugging, which creates a powerful software environment for the development of embedded applications. For more details please visit: http://www.iwavesystems.com/product/board-support-packages/wec7-on-i-mx6-sabre-sdp/wec7-on-i-mx6-sabre-sdp.html “We are pleased to launch Windows Embedded Compact 7 on Freescale’s SDP which supports the major feature sets such as Storage, Networking, Display & Multimedia” says M A Mohamed Saliya, Managing Director, iWave Systems. “Our solution enables faster and easier customization for optimising the product development cycle time, ensuring the best quality.” “We are excited to work with our Windows Embedded partner iWave Systems to help OEMs bring high performing, reliable and differentiated devices based on Windows Embedded Compact 7 to market more quickly”, said Steven Bridgeland, product manager for Windows Embedded at Microsoft. “Working together with iWave Systems continues to be at the forefront of innovation in specialized devices, creating new opportunities to develop innovative connected devices for intelligent systems across the enterprise and industrial applications.” “iWave’s feature rich WEC7 BSP for Freescale’s SABRE platform for smart devices based on i.MX 6Quad is highly helpful for quick prototyping and this BSP can be customized for any end product in very short possible time.   iWave has vast expertise in WinCE BSP and in-house technical support for various Freescale processors from  i.MX27, i.MX51, i.MX53 to i.MX 6 series, this has been beneficial to many of our product customers as iWave reference designs have helped streamline their cycle time”. Ken Obuszewski, Director of i.MX Product Marketing of Freescale’s Microcontroller Group About iWave Systems: iWave systems brings the expertise of building Windows Embedded based solutions on latest ARM platforms, with deep technical expertise in providing the Board Support Packages(BSP) for various ARM core platforms such as from Freescale and Texas Instruments. The BSP completely confronts to the Microsoft’s PQOAL (Production quality OEM Adaption layer) specification which follows layer based architecture for separating the OEM specific code from generic part of the code.

This is ITE MIPI to HDMI/IT6161 video bridge already merge/verified with i.Mx8 series processor. attached is IT6161 MINISAS card user manuel and reference circuits.@