iWave now has released the official Yocto BSP for its i.MX 6 Qseven modules (iW-RainboW-G15M-Q7) and i.MX 6 development kit variants. The release is based on Linux 3.10.17 kernel and supports the following features; 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 (default boot) eMMC Flash (default OS storage) Data UART uSD slot Standard SD slot USB 2.0 Host USB 2.0 device 10/100/1000 Ethernet PCIex1 Port SATA Port CAN Port LVDS display port (Dual) PWM for backlight HDMI Port with Audio 7”TFT LCD with capacitive touch Hardware Codecs (Encode/Decode) 2D/3D Graphics CMOS CSI camera port MIPI CSI camera port AC97 Audio In/Out Console UART RTC (i.MX6 Internal) I2C Port Sensors Watchdog GPIOs This release supports single BSP, Binary image & MFG tool for all the four i.MX6 CPU version (Quad/Dual/Dual Lite/Solo) based Qseven SOMs. Besides the Linux Yocto BSP support, Android Jelly Bean and Windows Embedded Compact 7 (WEC7) board support packages are also supported for the i.MX6 Qseven modules (Rainbow G15M-Q7) by iWave. More details about the i.MX6 Qseven modules (Rainbow G15M-Q7) hardware & software features can be found in the i.MX6 Qseven SOM product page. For further information or enquiries please write to [email protected]

Freescales i.MX 6 family provides product developers with the computing power of consumer applications for use in the industrial and automotive sector. Rich Industrial Interfaces i.MX 6 processors offer a wide range of interfaces that render these devices suitable for industrial use. These include Gigabit Ethernet, PCI Express and SATA 2 that are integrated into the processor. The two Flex CAN interfaces make i.MX 6 processors specifically suitable for automotive as well as industrial applications. All interfaces provide an I/O voltage of 3.3 V. Accordingly, in most use cases there is no extensive signallevel adjustments are needed for design-in of the processor, thus simplifying peripheral circuitry design. The phyFLEX-i.MX 6 System on Module Highlights The i.MX 6 controller (Cortex-A9) can internally comprise one, two or four cores.This means that the computing power of the same controller is scalable i.MX6 Single, Dual, Quad core Up to 1,2 GHz / core VPU, IPUv3H, GPU2Dv2, OpenVG 1.2 Up to 4 GB DDR3 / 16 GB NAND SD/SDIO/MMC USB 2.0 OTG and Host PCIe, SATA II CAN, UART, SPI, I 2 C, I2S Camera interface Up to 4 displays + HDMI Linux and Compact 7 BSPs phyFLEX-i.MX6 interfaces are routed to our high-density PCB interconnects on the underside of the SOM. Design the mating connectors on your carrier board. HARDWARE-MANUAL    ---    LINUX QUICKSTART    ---    WINDOWS EMBEDDED COMPACT 7 QUICKSTART

我们目前用的是Eink的9.7寸屏幕，打上freeescale 提供的uboot的patch之后发现默认是6寸屏，于是修改了timing，如下： short lcd_cmap[256]; vidinfo_t panel_info = {         .vl_refresh = 85,         .vl_col = 1200,         .vl_row = 825,         .vl_pixclock = 32000000,         .vl_left_margin = 12,         .vl_right_margin = 128,         .vl_upper_margin = 4,         .vl_lower_margin = 10,         .vl_hsync = 20,         .vl_vsync = 4,         .vl_sync = 0,         .vl_mode = 0,         .vl_flag = 0,         .vl_bpix = 3,         .cmap = (void *)lcd_cmap, }; struct epdc_timing_params panel_timings = {         .vscan_holdoff = 8,         .sdoed_width = 10,         .sdoed_delay = 20,         .sdoez_width = 10,         .sdoez_delay = 20,         .gdclk_hp_offs = 632,         .gdsp_offs = 20,         .gdoe_offs = 0,         .gdclk_offs = 1,         .num_ce = 3, }; 现在屏幕要进行四次全刷之后黑屏，全刷过程中可以看到logo，刷完就没有了，不知道还有些什么地方需要修改，求指导

The BD-SL-i.MX6 formerly SABRE Lite board is a low cost i.MX6 development platform.  One of the best attributes of the board is the significant software support that is available.  This post introduces Qt5.4 from the QT Company.  The video below shows The Qt Company’s enterprise device creation offering, a Qt-optimized pre-built software stack that lets you immediately get started with prototyping on a real device for embedded Linux and Android development.  The demo is running Qt5.4 and the image is available for the BD-SL-i.MX6 as well as our Nitrogen family of products.  Here is a brief video showing some of the capabilities: The video above showed an image created for embedded Linux, and more specifically, built using tools from The Yocto Project and The Freescale Community BSP. Because of this, your products can leverage the packages provided by those projects, and you can use the Yocto build system to integrate your components and tailor your build. For more details, visit http://qt.io or http://boundarydevices.com/qt-for-device-creation/

Here is a video that shows the NFC feature integrated into our Android Lollipop 5.0.0 code base. It is running on our Nitrogen6x platform along with the NXP PN7120 development kit. The video shows that a NFC tag, programmed with Boundary's URL, is automatically read and starts the Browser accordingly. In order to read/write data from a NFC data, Android provides a fully documented API. If you seek an existing application to write tags, here are a couple of options: NXP TagWriter app StickyNotes sample code For more information, please visit http://boundarydevices.com/

Mar 13, 2020: imx_builder_03122020.tgz  --- change the i.MX8MN  configuration.  Dec 11, 2019: imx_builder_12112019.tgz --- add support  L4.19.35_1.1.0 August 28, 2019:  imx_builder_08282019.tgz   --- add i.MX8MM July 03, 2019:  imx_builder_07032019.tgz --- add i.MX8QM: build_i.MX8  Feb 26, 2020: imx_builder_02262020 --- add i.MX8MN, add spl m4 for build_i.MX8, build_i.MX8X with L4.14.98_2.0.0_ga, L4.14.98_2.2.0, L4.19.35_1.1.0 imx_builder_02262020: imx_builder |-- atf -> bsp/imx-atf |-- bsp -> REL/rel_imx_4.19.35_1.1.0 |-- build -> build_i.MX8X/L4.19.35_1.1.0 |-- build_i.MX6 |   |-- L3.0.x |   |-- L3.1x.xx |   |-- L4.14.xx |   |-- L4.19.xx |   `-- L4.1.xx |-- build_i.MX8 |   |-- before_L4.14.98_2.0.0_ga |   |-- L4.14.98_2.0.0_ga |   |-- L4.14.98_2.2.0 |   `-- L4.19.35_1.1.0 |-- build_i.MX8M |   |-- before.L4.19.35 |   `-- L4.19.35 |-- build_i.MX8MM |   |-- before.L4.19.35 |   `-- L4.19.35 |-- build_i.MX8MN |   `-- L4.19.35 |-- build_i.MX8X |   |-- before_L4.14.98_2.0.0_ga |   |-- L4.14.98_2.0.0_ga |   |-- L4.14.98_2.2.0 |   `-- L4.19.35_1.1.0 |-- dts -> linux/arch/arm/boot/dts |-- dts64 -> linux/arch/arm64/boot/dts/freescale |-- dts_uboot -> u-boot/arch/arm/dts |-- imx-mkimage -> bsp/imx-mkimage |-- linux -> bsp/linux-imx |-- m4_img |   |-- m4_1_image.bin -> rpmsg_lite_str_echo_rtos_imxcm4.bin |   |-- m4_image.bin -> power_mode_switch.bin |   `-- readme.txt |-- Makefile -> build/Makefile |-- Others |   |-- clk_module |   |-- cryptodev-linux-1.8 |   |-- helloworld_module |   |-- key_blob_module |   `-- spi |-- out |-- README -> build/README |-- REL |-- scfw -> bsp/scfw |-- SETTINGS.MK -> build/SETTINGS.MK |-- toolchains |   `-- scfw |-- u-boot -> bsp/uboot-imx `-- VERSION.MK imx_builder is a set of Makefile for build u-boot, Linux kernel, atf, scfw, imx-mkimage.  You can call it standalone build. here is the step to try it.  You can use  -n for make to get the detail build steps. ex:  make atf -n         make linux.Image -n L4.14.78_ga as example: 1. Untar  imx_builder_02282019.tgz 2. Read the  Standalone_Build_Preparation.pdf inside to prepare the bsp. 3. Prepare the toolchains(populate_sdk from yocto, get from linaro, get from buildroot, etc.) 4. Prepare scfw toolchains following the SCFW Porting Kit.  5. Follow the Standalone_Build_Preparation.pdf to check if the Build Structure is correct. Build Structure L4.14.78_1.0.0_ga as example. Prepare rel_imx_4.14.78_1.0.0_ga in REL Make symbol link to REL/rel_imx_4.14.78_1.0.0_ga Make symbol link to build_i.MX8X   imx_builder/ |-- atf -> bsp/imx-atf |-- bsp -> REL/rel_imx_4.14.78_1.0.0_ga |-- build -> build_i.MX8X |-- build_i.MX6 |-- build_i.MX8M |-- build_i.MX8X |   |-- Makefile -> Makefile.4.14.78_ga |   |-- Makefile.4.14.78_ga |   |-- README |   |-- SETTINGS_4.14.78_1.0.0_ga.MK |   |-- SETTINGS.MK -> SETTINGS_4.14.78_1.0.0_ga.MK |   `-- VERSION.MK |-- dts -> linux/arch/arm/boot/dts |-- imx-mkimage -> bsp/imx-mkimage |-- linux -> bsp/linux-imx |-- Makefile -> build/Makefile |-- Others |-- out |-- README -> build/README |-- REL |   `-- rel_imx_4.14.78_1.0.0_ga |       |-- firmware-imx-8.0.bin |       |-- imx-atf |       |-- imx-mkimage |       |-- imx-sc-firmware-1.1.bin(optional) |       |-- imx-scfw-porting-kit-1.1.tar.gz |       |-- linux-imx |       `-- uboot-imx |-- scfw -> bsp/scfw |-- SETTINGS.MK -> build/SETTINGS.MK |-- Standalone_Build_Preparation.pdf |-- toolchains |   `-- scfw |       `-- gcc-arm-none-eabi-6-2017-q2-update |-- u-boot -> bsp/uboot-imx `-- VERSION.MK -> build/VERSION.MK

The Nitrogen6X is a highly integrated development system based on the next generation ARM-Cortex A9 processor from Freescale, the i.MX6. Click here to visit Boundary Devices for full details   See Compatible Products Tab for: 7″ Display SATA Cable 5MP Camera Android Button Board WiFi ADD-ON LVDS Cable for Freescale 10.1″ PCIE DB Available through Arrow Electronics. Cost will be $199 in Production for non-WiFi (October 2012)  

Issue description: ZQ calibration issue with LPDDR2 memory with two chip selects    Micron has verified it on my customer's board with i.MX6Q. (ECT-SYT-1163 for FIC.pdf) The patch is made based on lp 5.1, see attachment.

Inverse Path is proud to announce the USB armory project, an open source hardware design, implementing a flash drive sized computer for security applications. The USB armory is a compact USB powered device that provides a platform for developing and running a variety of applications. The security features of the USB armory System on a Chip (SoC), combined with the openness of the board design, empower developers and users with a fully customizable USB trusted device for open and innovative personal security applications. The USB armory hardware is supported by standard software environments and requires very little customization effort. In fact vanilla Linux kernels and standard distributions run seamlessly on the tiny USB armory board. The capability of emulating arbitrary USB devices in combination with the SoC speed, the security features and the flexible and fully customizable operating environment, makes the USB armory the ideal platform for all kinds of personal security applications. The Inverse Path team, with the help of the open source community, will develop applications that fully explore the potential of the USB armory board. The USB armory will be available for pre-order soon. Delivery of the device before the end of 2014 is planned. Target applications: mass storage device with advanced features such as automatic encryption, virus scanning, host authentication and data self-destruct OpenSSH client and agent for untrusted hosts (kiosk) router for end-to-end VPN tunnelling, Tor password manager with integrated web server electronic wallet (e.g. pocket Bitcoin wallet) authentication token portable penetration testing platform low level USB security testing Key features: Freescale i.MX53 ARM® Cortex™-A8 800Mhz, 512MB DDR3 RAM USB host powered (<500 mA) device with compact form factor (65 x 19 x 6 mm) ARM® TrustZone®, secure boot + storage + RAM microSD card slot 5-pin breakout header with GPIOs and UART customizable LED, including secure mode detection excellent native support (Android, Debian, Ubuntu, FreeBSD) USB device emulation (CDC Ethernet, mass storage, HID, etc.) Open Hardware & Software http://inversepath.com/usbarmory

As i.MX6 empowers the Surveillance applications, iWave has developed a system that brings together video streams from four cameras on four i.MX6 Pico ITX SBCs placed in four different locations through Ethernet. The fifth Pico ITX captures the video streams from the Ethernet and displays on a single HDMI monitor as indicated in the following block diagram. The system requires five i.MX6 Dual Pico-ITX boards connected with LAN. Each of four boards are connected with cameras which capture the video, encode and streams it as RTP packets.  The fifth board receives four streams of RTP packets and displays to four slots in HDMI. Operating system used is Yocto of Dora Version. MIPI or CSI cameras can be used for the video capture (tested with 5MP MIPI camera). All the four cameras share the screen equally and the display resolution of each camera is 854x480. For ease of demonstration we have used one Pico-ITX per camera, however for real life scenario and to keep down costs there is a possiblity that each i.MX6 Pico-ITX SBC can be connected to two cameras. Each pico-itx with i.MX6 quad/dual core can capture video from two cameras simultaneously. The same streaming procedure needs to be followed for this scenario too with it appropriate IP and Port number. For more details please reach to [email protected]

Dear All, We used the MCIMX6X4EVM10AB CTBD1607 2N19K + L3.10.53 and there was no problem. However, MCIMX6X4EVM10AB CTBD1607 2N19K is discontinued. so, we replaced with MCIMX6X4EVM10AB CTBE1646 3N19K. we were replaced I.MX6 soloX 2N19K to 3N19K on same board and then we were faced to internal boot fail issue after download sucess using MFG tool. We used NAND Booting, so we using MFG tool to download. and download is always success. and then we changed the BOOT_MODE from '01' to '10' using the fuse switch. and system power on..... Internal Booting does not work and it goes directly to Serial Download and it is caught as USB Device on PC. BOOT_CFG uses '0000' In case MCIMX6X4EVM10AB CTBD1607 2N19K, both of L3.10.53 and L4.1.15 are successfully booted by Internal nand. MCIMX6X4EVM10AB CTBE1646 3N19K, both L3.10.53 and L4.1.15 were successfully downloaded using MFG but There is does not work Internal nand booting. I saw the document 'i.MX 6SoloX Application Processor Silicon Revision 1.2 to 1.3 Comparison' I could not find any part to change as software. I.MX6 Solo After changing from Rev1.2 to Rev1.3, is there any part that needs to be modified as S / W or H / W?