iWave Systems Technologies, successfully demonstrated the MIPI camera on its latest i.MX6 Qseven development kit. The Leopard’s 5M pixel MIPI CSI Camera module part LI-OV5640-MIPI-AF is integrated with the latest revision of iWave i.MX6 Q7 evaluation board and the sensor supports the following features. Sensor: OV5640 (CMOS image sensor) Active array Size: 2592x1944 Image transfer rates; 1080p@30fps, 720p@60fps Module Connector: AXK824145   The camera is interfaced with the i.MX6 processor through MIPI CSI interface. The Linux 3.0.35 and Android 4.0.4 BSP support is available for this display with iWave’s i.MX6 development kit. The i.MX6 development board integrated with this MIPI camera is available for shipping now. 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 i.MX6 Qseven System On Module (SOM): iW-RainboW-G15M is Freescale's i.MX6 based Qseven compatible CPU module for faster and multimedia focused applications. The module has on-board expandable 1GB DDR3 RAM, micro SD slot and optional eMMC flash. With the extreme peripheral integration, the module supports industry latest high performance interfaces such as, PCIe Gen2, Gigabit Ethernet, SATA 3.0, HDMI 1.4 and SDXC etc. 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: i.MX6 Q7 Development Kit | iWave Systems email: mktg@iwavesystems.com

The wait is over! Toradex announces the launch of its latest technical support feature, the Toradex Community, an online community that aims to provide customers a unique platform to stay connected with the Toradex engineers. Toradex, which has always provided extensive free and direct technical support from development engineers, recognizes that many of its customers often have similar queries. By providing an online community where anyone may post a query and by publicly listing down the engineers’ responses, Toradex anticipates that the entire community will stand to benefit from the collective knowledge available via the forum. “We invested a lot of time to understand what information our customers most wanted access to and how to deliver it in a simplified, user friendly and timely manner. With the launch of the Toradex Community platform, our aim is to create an even more connected and responsive support system for our customers, while enabling easy access to information. We invite you to be a part of this ever-growing community constituted by our embedded enthusiasts.” said Roman Schnarwiler, CTO, Toradex. The community will serve to provide its members with sustainable solutions and key insights from our experienced engineers who will be answering queries related to the usage of Toradex products in a wide variety of embedded applications. Furthermore, it will complement the exhaustive information available on the Toradex Developer Center, which is a resourceful website that brings all of Toradex’s developer resources together at one place. For an overview about all our available support channels, please check our support page. About Toradex: Toradex is a leading vendor of ARM based System on Modules (SOMs) that can be used for diverse embedded applications. Powered by Freescale® i.MX 6 & Vybrid™, NVIDIA® Tegra, and other leading processors, the SOM families offer a wide range of options in terms of price, performance, power consumption and interfaces. Complemented with the long-term availability of 10+ years for its products, Toradex stands out in the embedded computing market with free lifetime product maintenance, pin-compatible product families for scalable designs, direct premium technical support, and transparent pricing with direct online sales. Founded in 2003 and headquartered in Horw, Switzerland, the company’s network stretches across the globe with additional offices in the USA, Vietnam, China, India, Japan, and Brazil. For more information, visit https://www.toradex.com. For media queries, please contact: Lakshmi Naidu: lakshmi.naidu@toradex.com

The documentation has summerized some FAQs for development based on NXP's i.MX 6UL/6ULL ARM Cortex-A7 processors. MYIR provides a series of i.MX 6UL/6ULL based products including SoM, SBC, development board and HMI display panel. MYD-Y6ULX-CHMI | 7-inch HMI Display Solution based on NXP i.MX 6UL/6ULL-Welcome to MYIR  MYS-6ULX | NXP i.MX 6UL / 6ULL SBC Board for IoT and Industry Applications-Welcome to MYIR  MYC-Y6ULX CPU Module | NXP i.MX 6UL, i.MX 6ULL SOM | ARM Cortex-A7 Processor-Welcome to MYIR   MYD-Y6ULX | NXP i.MX 6UL, i.MX 6ULL Development Board / SOM, ARM Cortex-A7 Processor-Welcome to MYIR  MYD-Y6ULX-HMI Development Board | NXP i.MX 6UL/6ULL Board for HMI Applications-Welcome to MYIR  MYIR is pleased to share the experience with more developers. 

     The document will give a reference design for those i.MX6 users who wants to use GPIO to control relays. Actually, it is not difficult to reach the purpos on hardware design, But if hardware engineer doesn't notice the PAD status after Power On Reset, Relays will produce unexpected action, For example, if using those pins with "PU 100K"(Pull Up by 100K), or "keeper", After power on and before system booting, relays begin to be operated(unexpected close or open)     In recent days, one of imx6 user encoutered the similar issues when she debugged "GPIO control 32-channel relay output). So I drew a schematic on hwo to design Isolated GPIO, and how to use GPIO to contorl 24V-relay. In schematic, 8-channel GPIOs & Relays were supported.     From i.mx6 datasheet, we can find most of PADs' status are "PU 100K", so in schematic, 8 GPIOs are all those PADs with "PU 100K". The following is design requirement: (1) Turth table. GPIO output  1 -------Relay  Close GPIO output  0 -------Relay  Open GPIO default 0 ------ Relay  Open (2) GPIO should be Islated by optocoupler (3) 8-Channel ,24V digital signals output See attachment, please! Schematic is reference for i.mx6 users! If you have some questions or good advice on the design, you can submit case to me by our official website. NXP TIC Weidong Sun Email: weidong.sun@nxp.com

Hi, check out this video that demonstrates software making use of power savings capabilities on the i.MX28:  http://go.mentor.com/low-power

Hi NXP expert : Deaufult iMX8M apply 3GB DRAM density with the system, How to modify DRAM configration that could cutdowm density to 1GB DRAM ? 

With last LTIB - BSP release there was an interesting and very usefull document (attached here) """""""""""""""""""""""""""""""""""""""""""" i.MX 6Dual/6Quad BSP Porting Guide Document Number: IMX6DQBSPPG Rev. L3.0.35_1.1.0, 01/2013 """""""""""""""""""""""""""""""""""""""""""" In this document there were the most used needed steps to port the BSP from a reference board (i will take as example the IMX6q sabresd) to a Custom board. Infact the usual project path , is starting from a reference board , but a t the end i need to use a custom board (for costs , space and any other reason). So the Idea is o make a new document to do the same on the new Yocto enviroment. Infact the step and the stuff to change are ecxatly the same, but they are to be done in different way. When you want to make your custom board what can be different from a reference one: 1) DDR memory 2) IO usage 3) on board peripheral 4) boot source I think these are the main issue that could change from a board to another one (with the same processor Imx6q). Following the "Yocto Project best practice guide" we need to create a new "layer" where we can fit the customized thing: uboot, dts, drivers for pheriperal, maybe customized kernel .... So this document is intended to be a starting point where customer and freescale expert can work togheter to make this "aplication note " that is really the final step for every project based on imx6Q Yocto Project development. Omar *************************************************************************************************************************************************************************************************************************************** Following I will try to examine the single step that needs to be configured in every board. First a brief summary then each step will be detailed with files and paths , and example modification. I will use as example the board IMX6QsabreSD. So all the path will be referred to that board. *************************************************************************************************************************************************************************************************************************************** I)                                                                                                                Porting Bootloader *************************************************************************************************************************************************************************************************************************************** 1) They first program loaded and executed from your boot source (NAND, emmc, SD etc..) is the bootloader. In our case u-boot. this program perform some basic initialization, those intializations are related to the board. But the very first thing is DDR initialization, this mean to inizialize IOMUX and DDR controller registers (Timing geometry etcc...). This initialization is done in the DCD part of the uboot image. the once we initialized the DDR the bootloader can work, than it will have to configure the IOMUX to match the peripheral used on chip and on board. And then of course it will have to load the driver (at least one UART for consolle and ethernet driver) it needs. So FIRST thing to customize for your board is the bootloader. Using a base directory the git of u-boot the file that contain the DCD is: board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg the other important file is the board/freescale/mx6sabresd/mx6sabresd.c this second file contain several board related definition, first of all, the IOMUX configuration for the pins of IMX6Q used for soc peripheral a third important file is the include one here there are several important define such as mem size. include/configs/mx6sabresd.h include/configs/mx6sabre_common.h So you need to make a copy of those files (in the new board dir, or in the include/configs for .h files) renaming them of course with the name of your custom board. Then you need also to add the new board to the Makefiles and source tree , as described following: (take also as a reference he chapter 1.2 and 1.3 of the attached document and this link http://git.denx.de/?p=u-boot.git;a=blob_plain;f=README;hb=HEAD). 1. Add a new configuration option for your board to the toplevel  "boards.cfg" file, using the existing entries as examples.  Follow the instructions there to keep the boards in order. 2. Create a new directory to hold your board specific code. Add any files you need. In your board directory, you will need at least the "Makefile", a "<board>.c" 3. Create a new configuration file "include/configs/<board>.h" for  your board 4. Debug and solve any problems that might arise. At this point if we did all the modification we need to u-boot we have to create our fsl-myboard layer to add our "patch" to the u-boot tree. those patched u-boot will be compiled and deployed just for the new MACHINE (our custom board). *************************************************************************************************************************************************************************************************************************************** II)                                                                                                                Creating DTS tree for kernel *************************************************************************************************************************************************************************************************************************************** 1)Then you need to create the DTS files for your board as well, those files are a description of your board (including) SOC , mem etc etc... used by the kernel. those files are in the kernel tree in arch/arm/boot/dts. Take a look http://events.linuxfoundation.org/sites/events/files/slides/petazzoni-device-tree-dummies.pdf  this is a good starting point. Another good reference is: Device Tree - eLinux.org , here you can find a lot of link and reference to a more deep understanding. The official wiki:http://www.devicetree.org/Main_Page And interesting: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree In our example the reference dts will be of course the imx6q-sabresd.dts(in the kernel tree source path /arch/arm/boot/dts), this file include and refer other "dts" files that we will see . Well the starting point of this dts tree is, in this example, the imx6q-sabresd.dts, it recalls other files: imx6q-sabresd.dts ---------------> imx6qdl-sabresd.dtsi                           |----------------> imx6q.dtsi                                                            |--------------------> imx6q-pinfunc.h                                                            |--------------------> imx6qdl.dtsi                                                                                                   |-----------------------> skeleton.dtsi                                                                                                   |-----------------------> dt-bindings/gpio/gpio.h the file wiht the name that does not contain "sabresd" are not board related but Soc related so we can keep as is even for our custom board, so the only file we need to touch are imx6q-sabresd.dts and imx6qdl-sadresd.dtsi. As we did for u-boot porting, we will copy these files and create new ones with names as imx6q-cutomboard.dts and imx6qdl-customboard.dtsi in the same dir. Now we will examine them in detail.

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.

iWave Systems, Proven Partner of Freescale Semiconductor and a leading Embedded Hardware, FPGA and Software Turnkey Design Services and Solutions company, presents improved i.MX 6 Qseven Development Board RainboW-G15D that supports following  sensors: 3-Axis Accelerometer Digital e-Compass Ambient Light Sensor Altimeter/Barometer These sensors interfaced with the iMX6 processor using I2c interface for internal communication and data transfer and also possess INT (interrupt) signal to interrupt the processor about the data. The RainboW-G15D development kit with Linux 3.0.35 BSP supports these various sensors. 3-Axis Accelerometer: This Accelerometer sensor is used for Static orientation detection (Portrait/Landscape, Up/Down, Left/Right, Back/Front position identification). Motion detection for power saving (Auto-SLEEP and Auto-WAKE). Shock and vibration monitoring. Digital e-Compass: The digital e-compass sensor is used for measuring magnetic fields with an output date rates up to 80Hz (ODR). It acts as electronic Compass with accurate heading information. Location Based Services. Ambient Light Sensor: The ambient light sensor is used for measuring the light rays, it uses the photo detectors to convert the light energy into electrical energy. Altimeter/Barometer: This sensor is used for Measuring the pressure/altitude and temperature, it uses ADC to convert physical parameter into electrical. 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 i.MX6 Qseven System On Module (SOM): iW-RainboW-G15M is Freescale's i.MX6 based Qseven compatible CPU module for faster and multimedia focused applications. The module has on-board expandable 1GB DDR3 RAM, micro SD slot and optional eMMC flash. With the extreme peripheral integration, the module supports industry latest high performance interfaces such as, PCIe Gen2, Gigabit Ethernet, SATA 3.0, HDMI 1.4 and SDXC etc. 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: i.MX6 Q7 Development Kit | iWave Systems email: mktg@iwavesystems.com

iWave is upgrading Android KitKat 4.4 BSP for its all variants of i.MX6 Qseven SOMs. The KitKat BSP supports following features and will be available in end of Q2 2015: i.MX6 ARM Cortex A9 Quad, Dual, Dual Lite & Solo CPU 1GB DDR3 RAM (Quad, Dual, Dual Lite CPU version)/ 512MB DDR3 (Solo CPU version) Freescale PMIC SPI NOR Flash eMMC Flash uSD slot Standard SD slot USB 2.0 Host USB 2.0 device 10/100/1000 Ethernet PCIex1 Port CAN Port LVDS display port Capacitive multi-touch PWM for backlight HDMI Port with Audio SATA (Support available only in i.MX6Q/D) Hardware Codecs (Encode/Decode) 2D/3D Graphics MIPI CSI camera port AC97 Audio In/Out Console UART Besides the Android support, Linux and WEC7 board support packages are also available for the i.MX6 Qseven SOMs from iWave systems. More details about the i.MX6 Qseven SOM & software features can be found in the i.MX6 Qseven product page. Device drivers will be supported for specific interface chipsets, which are used in iWave's Qseven Carrier board. More details about iWave i.MX6 Qseven development kit can be found in the following webpage: http://www.iwavesystems.com/product/development-platform/i-mx6-q7-development-kit-54.html