i.CORE M6UL Based on Freescale™ i.MX 6UltraLite processor, a high performance, ultra-efficient processor family featuring an advanced implementation of a single ARM™ Cortex™-A7 core, which operates at speeds up to 528 MHz. The new ENGICAM GEA M6UL module is suitable for cost effective HMI applications requiring high performance CPU. i.CORE M6UL Cores Cortex-A5 @ 528 MHz core, NEON MPE co-processor and VFPC  Memories 128MB 32bit DDR3-800 256MB SLC NAND Flash Graphics and Multimedia 1x Parallel LCD 18bit output Touch screen Peripherals 2x SD Card interface USB OTG HS, USB HS HOST, Uart, I2C, I2S 4x ADC inputs Up 2x Ethernet 10/100 Dimensions Standard SODIMM footprint 67,4x31.9 mm PCB size Very Low Profile Module EDIMM pin compatible ENGICAM - GEA M6UL

Hi all, Below is our press release for our i.MX6 solutions, i.e., kits and boards. emtrion GmbH, a company specialised in Embedded Systems design, hardware and software, Freescale Proven Partner, announces the availability of a new industrial processor module based on the multicore Cortex-A9 i.MX6 SoC family from Texas Instruments. This new module, called DIMM-MX6, extends the emtrion DIMM family and offers a full electrical and mechanical compatibility with the other modules of the emtrion DIMM series. emtrion guarantees the availability of its new module for at least 10 years. The DIMM-MX6 module from emtrion brings high computing capabilities with up to 10.000 DMIPS, multiple NEON SIMD and VPFU co-processors at a low power level, without requiring any active cooling system. The DIMM-MX6 module is available in several versions, with either i.MX6 Solo (1 core), Dual (2 cors) or Quad (4 cores) and on-board memories ranging from 512MB up to 8GB for the Flash (SLC NAND) and from 512MB up to 2GB RAM (DDR3). The new module is also qualified for an extended temperature range of -40°C to +85°C. In addition to boards and kits, emtrion offers support for a broad range of operating systems, board support packages (BSP) as well as engineering services. The DIMM-MX6 is available now with a BSP for Linux, that will be followed by additional BSP for Windows Embedded Compact 7 (WEC7), for QNX 6.5 and for Android 4.0. The BSP are available together with a developer kit. Each developer kit includes a DIMM-MX6 industrial module, a base board, a display and a development environment. All parts are mounted together and programmed by emtrion. The kits are shipped ready to use.

'Multi-core Processor Technology’ will be the key in the development of next generation of advanced computing devices. With major silicon vendor Freescale bringing multi-core application processors for the mainstream embedded devices, there is  need to have the multi-core processing support in the embedded operating systems. Windows Embedded Compact 7(WEC7) will enhance the performance of ARM based multi-core platforms with the addition of Symmetric Multi-Processing (SMP) support. iWave systems has done a SMP support verification on its Freescale’s i.MX6 Quad core processor running WEC7 platform. Symmetric Multi-Processing (SMP) support in WEC7: The most important update in the Windows Embedded Compact 7 is the support for Symmetric Multi-Processing (SMP) which takes the full advantage of multi-core systems providing a performance boost when the multithreaded applications are being used. The multi-core processor platforms such as Freescale’s i.MX6Q which has 4 identical CPU cores, can effectively take advantage of SMP support in WEC7. SMP enabled kernel can use several CPU cores simultaneously and distribute the execution of different processes and threads to them. The number of available cores can be determined by SMP API from the application – the processing and assignment of a thread to a specially selected core is also possible. Read More.. Windows Embedded Compact7 on i.MX6 RainboW-G15D Development Board: iWave Systems, profoundly known for its genuine embedded solution offerings spanning from SOMs to fully integrated systems, offers Windows Embedded Compact 7 (WEC7) reference BSP for iWave’s i.MX6 platform named RainboW G15D besides the existing Linux & Android BSP versions. All the latest features that WEC7 offers such as Silverlight 3.0, MPEG-4 HD, Expression Blend, Active Sync and also Adobe Flash10.1 are made available. About i.MX6 Qseven Development Board: The Development Platform incorporates Qseven compatible i.MX6x SOM which is based on Freescale's iMX 6 Series 1.2GHz multimedia focused processor and Generic Q7 compatible Evaluation Board. This platform can be used for quick prototyping of any high end applications in verticals like Automotive, Industrial & Medical. Being a nano ITX form factor with 120mmx120mm size, the board is highly packed with all necessary on-board connectors to validate complete iMX6 CPU features. About iWave Systems: iWave has been an innovator in the development of “Highly integrated, high-performance, low-power and low-cost i.MX6/i.MX50/i.MX53/i.MX51/i.MX27 SOMs”. iWave helps its customers reduce their time-to-market and development effort with its products ranging from System-On-Module to complete systems. The i.MX6 Pico ITX SBC is brought out by iWave in a record time of just 5 weeks. Furthermore, iWave’s i.MX6/i.MX50/i.MX53/i.MX51/i.MX27 SOMs have been engineered to meet the industry demanding requirements like various Embedded Computing Applications in Industrial, Medical & Automotive verticals. iWave provides full product design engineering and manufacturing services around the i.MX SOMs to help customers quickly develop innovative products and solutions. For more details: WEC7 on i.MX6 Rainbow G15D  | iWave Systems email: mktg@iwavesystems.com

Today, technology goes forward and we get some new possibilities in the Online TV viewing. iWave’s i.MX6 Pico-ITX board with Jelly Bean Android provides one such solution. Today we can watch online TV in the Browser that will run in the i.MX6 Pico-ITX Single Board Computer. This uses Real Time Messaging Protocol (RTMP).  RTMP was initially a proprietary protocol developed by Macromedia. It is based on TCP and was specifically designed for streaming video, audio, and data between a media server and clients (Flash player). Currently applications like follows use this protocol: Online multi-player games Text and video chat applications Virtual meeting applications Synchronous and interactive e-learning applications (business simulation games, etc.) In the early days of web video delivery, users had to rely on progressive delivery of video, meaning that the bits of video were delivered to your player one packet at a time “in the blind,” with no communication between the server and player. When a reasonable percentage of the file was downloaded to disk, the player would begin playing the file. However too often the player caught up with the point at which the file was being delivered, and playback halted. As a result streaming was created—a mode through which the video is passed to the player, with increased communication and monitoring in place, and it happens in real time between the player and server. If bandwidth degrades on the player side, it signals the server and “buffers” until it can obtain a suitable amount of packets of video to resume playback. One benefit with RTMP worth mentioning here is its ability to provide multicast support. If you run an enterprise and want to take one stream inside your corporate network and deliver it to many users without initiating a new connection for each user, RTMP is the best technology. Using iMX6 PICO-ITX Android Jelly Bean, one can watch ‘online live iptv broadcasting’ and ‘video on demand’. As shown in the above block diagram, web browser through http requests the web server, then the web server will send the swf file to the web browser over http. Flash player then connects to the media server using RTMP. RTMP server will send the data via RTMP that will be played in the Flash Player. If your favourite online service (IP TV) uses the RTMP protocol for broadcasting, you have a good chance of being able to watch the video stream live using iWave’s i.MX6 SBC.  Its operating principle is simple: you input the address of the video server. It just connects to the server, consuming only the network traffic containing the video, and streams it to your display unit. Online Live IP TV: "Russia Today" is one of the IPTV broadcasting http://rt.com/on-air/rt-america-air/ we can watch this IPTV online in the Jelly Bean's Browser. We can choose the quality either HD, medium and low. Video On Demand: i.MX6 Pico ITX SBC also supports RTMP for Video on demand services. "Deutsche Welle" is one of the Video on demand service provider. We can watch this on demand video in the Android Browser.  http://www.dw-world.de/dw/0,,4756,00.html We can watch Discovery Germany Video By clicking on that. Finally iWave’s i.MX6 Single Board Computer is able to provide Video on demand services and Worldwide IPTV broadcasting over HDMI or LVDS display. For further information or enquiries please write to mktg@iwavesystems.com or visit www.iwavesystems.com. http://http://www.iwavesystems.com/onlinetv-videoondemand-imx6-android

This post is based on http://boundarydevices.com/using-the-cortex-m4-mcu-on-the-nit6_solox/ The i.MX6 SoloX processor is the first of a kind, coupling a Cortex-A9 with a Cortex-M4 core inside one chip to offer the best of both MPU and MCU worlds. The MCU is perfect for all the real-time tasks whereas the MPU can provide a great UI experience with non real-time OS such as GNU/Linux. This blog post will detail how to build and run source code on the MCU using our Nit6_SoloX. Terminology Before getting any further, here is a list of terms that will be used in this post: MCC: Multi-Core Communication: protocol offered by Freescale for the MCU and MPU to exchange data MCU: Microcontroller Unit such as the ARM Cortex-M series, here referring to the Cortex-M4 MPU: Microprocessor Unit such as the ARM Cortex-A series, here referring to the Cortex-A9 MQX: RTOS provided by Freescale to run their MCUs RTOS: Real-Time Operating System such as MQX or FreeRTOS For the impatient You can download a demo image from here: 20150814-buildroot-nitrogen6x-mcu-demo.img.gz for Nit6_SoloX. As usual, you’ll need to register on our site and agree to the EULA because it contains Freescale content. The image is a 1GB SD card image that can be restored using zcat and dd under Linux. ~$ zcat 20150814-buildroot*.img.gz | sudo dd of=/dev/sdX bs=1M For Windows users, please use Alex Page’s USB Image Tool. This image contains the following components: Linux kernel 3.14.38 from our repo https://github.com/boundarydevices/linux-imx6/tree/boundary-imx_3.14.38_6qp_beta U-Boot v2015.04 from our repo https://github.com/boundarydevices/u-boot-imx6/tree/boundary-imx6sx Development environment setup This section will detail how to set up a Linux machine to be able to build MCU source code. First you need to download the "MQX RTOS for i.MX 6SoloX v4.1.0 releases and patches" file from Freescale website: http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MQX Then you need to untar this archive and apply our patch to add support for the Nit6_SoloX board. ~$ cd && mkdir mqx && cd mqx ~/mqx$ tar xf ~/Downloads/Freescale\ MQX\ RTOS\ 4.1.0\ for\ i.MX\ 6SoloX\ Linux\ Base.tar.gz ~/mqx$ wget http://boundarydevices.com.commondatastorage.googleapis.com/0001-Add-Nit6_SoloX-board-support.patch ~/mqx$ patch -p1 < 0001-Add-Nit6_SoloX-board-support.patch ~/mqx$ find . -name "*.sh" -exec chmod +x {} \; Note that this package comes with a good set of documentation which we invite you to read: doc/Freescale_MQX_RTOS_4.1.0_i.MX_6SoloX_Release_Notes.pdf doc/Getting_Started_with_Freescale_MQX_RTOS_on_i.MX_6SoloX.pdf As specified in the documentation, you need to install a specific toolchain (CodeSourcery v2014q1) in order to build the BSP. ~$ cd && mkdir toolchains && cd toolchains ~/toolchains$ wget https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q1-update/+download/gcc-arm-none-eabi-4_8-2014q1-20140314-linux.tar.bz2 ~/toolchains$ tar xjf gcc-arm-none-eabi-4_8-2014q1-20140314-linux.tar.bz2 ~/toolchains$ rm gcc-arm-none-eabi-4_8-2014q1-20140314-linux.tar.bz2 Your machine is now ready to build applications for the MCU! Build instructions This section explains how to build the BSP as well as the applications for the MCU only. In order to build the BSP for the MPU, please refer to other blog posts on either Yocto or Buildroot. ~$ cd ~/mqx/ ~/mqx$ export TOP=$PWD ~/mqx$ export TOOLCHAIN_ROOTDIR=$HOME/toolchains/gcc-arm-none-eabi-4_8-2014q1/ ~/mqx$ cd $TOP/build/imx6sx_nit6sx_m4/make ~/mqx$ ./build_gcc_arm.sh As the BSP for our board is now built, we can build any example application provided in the MQX package. In order to have an interaction between the MPU and the MCU, you need to build a MCC application. Below are the instructions to build the pingpong application which sends data back and forth between the cores. ~/mqx$ cd $TOP/mcc/examples/pingpong/build/make/pingpong_example_imx6sx_nit6sx_m4/ ~/mqx$ ./build_gcc_arm.sh ~/mqx$ $TOOLCHAIN_ROOTDIR/bin/arm-none-eabi-objcopy \        ./gcc_arm/ram_release/pingpong_example_imx6sx_nit6sx_m4.elf \        -O binary m4_fw.bin That's it, the binary is ready to be used! Some might be interested in using an IDE to browse/modify/build the source code, note that Freescale provides instructions to use IAR Workbench (Windows only). It seems that there isn't any plan to support the SoloX MQX release inside the KSDK (Kinetis SDK) as explained in a community forum post. Run the demo First you need to copy the image (20150814-buildroot-nitrogen6x-mcu-demo.img.gz) provided at the beginning of this post to an SD Card. Then copy the m4_fw.bin binary to the root directory of the SD Card. The SD Card contains the U-Boot version that enables the use of the Cortex-M4, the bootloader inside your NOR must therefore be upgraded. U-Boot > setenv bootfile u-boot.imx U-Boot > run upgradeu Once the upgrade is complete and the board restarted, make sure to have a clean environment: U-Boot > env default -a ## Resetting to default environment U-Boot > saveenv By default, the M4 must be flashed in NOR memory, a U-Boot command has been added to look for the m4_fw.bin as the root of any external storage (SD, USB, SATA): U-Boot > run m4update This command will download the firmware from external storage to RAM and flash it at the offset 0x1E0000 of the NOR. While debugging on the MCU, you might wish not to write every firmware into NOR so we've added a command that loads the M4 firmware directly from external storage. U-Boot > setenv m4boot 'run m4boot_ext' Before going any further, make sure to hook up the second serial port to your machine as the one marked as "console" will be used for U-Boot and the other one will display data coming from the MCU. In order to start the MCU at boot up, we need to set a variable that will tell the 6x_bootscript to load the firmware into OCRAM. If you wish to start the MCU at every boot, make sure to save this variable. U-Boot > setenv m4enabled 1 U-Boot > boot While the kernel is booting, you should see the following prompt on the MCU serial output: ***** MCC PINGPONG EXAMPLE ***** Please wait :   1) A9 peer is ready   Then press "S" to start the demo ******************************** Press "S" to start the demo : Press the S key as requested above on the MCU serial console and then log into Buildroot on the MPU serial output (login is root, no password). You now need to enable the MPU side of the communication before starting the demo: # echo 1 > /sys/bus/platform/drivers/imx6sx-mcc-test/mcctest.15/pingpong_en & A9 mcc prepares run, MCC version is 002.000 test/mcctest.15/pingpong_en & # Main task received a msg from [1, 0, 2] endpoint Message: Size=0x00000004, data = 0x00000002 Main task received a msg from [1, 0, 2] endpoint Message: Size=0x00000004, data = 0x00000004 ... That's it, you've built a MCU application from scratch and can now start exploring all the examples provided inside the MQX SoloX release.

     See a connected Android demo on an i.MX53 in action -  http://www.youtube.com/watch?v=1R1kbya77eE   

In May of 2015, Forlinx Embedded Tech. Co., Ltd launched a new item based on i.MX6 serial microprocessor, both quad-core and dual lite-core are optional. Its features are as below: 1)i.MX6Q CPU module features i.MX6Q base board features: 2) i.MX6DL features: Both i.MX6Q and i.MX6DL share one CPU module and one base board. But SATA interface is only available for the quad-core board. They have excellent performance of OS Android, both multi-screen displaying and displayings are possible on it. Besides, as many companies are now engaged in EV Charger Billing Unit project or solution, i.MX6 will be a best backup option based on its advantages of LVDS and multi-screen For more details pls refer to our homepage www.forlinx.net or send emails to grace@forlinx.com Hardware Interface   S

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

PMIC PF3000/3001 + i.MX 6UL Resources: ========================================================================================================================= Upload the latest version D as enclosed, SCH-29105 KIT6UL_3000EVM Version D and SCH-29105 KIT6UL_3000EVM Version D. The attachment SCH-29105 KIT6UL-3000EVM Version C.zip includes i.MX 6UL 14x14 + PMIC PF3000(KIT6UL-3000EVM, SCH-29105 Rev.C) related files: No. Files in SCH-29105 KIT6UL-3000EVM Version C.zip 1 SPF-29105_C.pdf is the corresponding schematic PDF version. 2 SCH-29105_C.zip is the schematic. 3 LAY-29105_C.zip is the PCB layout. 4 750-29105_C BOM.xls is the BOM.   Its i.MX 6UL 14x14 + PMIC PF3000 BSP: Apply PF3000 driver patch in imx_3.14.52_1.1.0_ga http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/commit/?h=imx_3.14.52_1.1.0_ga&id=e5a7a72cd51a585b8f1a1e299bf88fff44b94440 Apply 0001-add-pf3000-on-imx6ul-evk-board.patch, see the attachment. Apply 0003-correct-arm-soc-regulator-for-pf300.patch, see the attachment. Apply 0001-u-boot-add-pf3000-support-on-imx6ul-14x14-evk-board.patch, see the attachment.        2.  Update customer board dts as the above 0001-add-pf3000-on-imx6ul-evk-board.patch.   ========================================================================================================================= The attachment SCH-29090 KIT6UL-3001EVM Version C.zip includes i.MX 6UL 14x14 + PMIC PF3001(KIT6UL-3001EVM, SCH-29090 Rev.C) related files: No. Files in SCH-29090 KIT6UL-3001EVM Version C.zip 1 SPF-29090_C.pdf is the corresponding schematic PDF version. 2 SCH-29090_C.zip is the schematic. 3 LAY-29090_C.zip is the PCB layout. 4 750-29090_C BOM.xls is the BOM.   Its i.MX 6UL 14x14 + PMIC PF3001 BSP: Apply PF3001 driver patch in imx_3.14.52_1.1.0_ga http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/commit/drivers/regulator/pfuze100-regulator.c?h=imx_3.14.52_1.1.0_ga&id=19708058f049be9a5dcc81943d1b9a14080367e8 Update PF3001 dts board file as customer board dts.   Thanks, PMIC team: Sean Liu

Вебинар по продукции TechNexion "Процессорные платы на базе iMX6 (ARM)" OK, maybe not everyone of you speak Russian. For example I don't speak. But I know there is a big Russian community out there, developing great stuff just like the rest of us by using ARM Processors. This Friday Ilya from IPC2U will hold a Webinar to give a Technical overview about the capabilities ARM processors have and how you can use them in today's world. I had a chat with Ilya and he told me he is planing to give a overview why ARM now is more suitable to be used in many different industrial areas due to increased capabilities and the increased usability of Linux. I had the luck that Ilya gave me an overview about what he will present, so even my Russian is limited (limited as in 'non existing') I still get some useful updates, even for me. The Link to register is here: http://ipc2u.ru/news/webinars/processornye-moduli-na-imx6-arm/ It's at 11:30 Moscow time (I guess, please check link above) and the Agenda is like this: Темы вебинара: Что такое ARM Семейство процессоров iMX6 на базе архитектуры ARM Cortex-A9 О компании TechNexion Обзор продукции компании TechNexion (встраиваемые системы, панельные компьютеры) Подробный обзор процессорных модулей формата PICO Talking with Ilya he told me this Agenda is roughly and he will cover like this: -ARM overview -ARM for industrial usage -NXP and it’s ARM i.MX6 Processors -TechNexion Product overview -TechNexion PICO Modules in detail -Q&A I don't know if there is a limit in maximum people to attend but 1h ago Ilya told me he is overwhelmed by the sign up rate of people... ..so you better hurry if you speak Russian and want join! Hey you are attending? Tell me here how it was after it, ok? Looking forward to hear from you Florian P.S.: I work for TechNexion. Thats the Company IPC2U is talking about in this Webinar, just to be clear about that. Me: florian12​​

Adeneo's entry for solution of the month in collaboration with Congatec