Multi Source Translation Content

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Multi Source Translation Content

ディスカッション

ソート順:
[RTD600 IP] S32K312-EVB Lpuart 中断回显 这个简单的示例演示了如何在S32K312EVB-Q172和S32K312MINI-EVB上使用LPUART模块配置和处理UART中断。它设置UART回调函数,并以单字节模式启动接收。每接收一个字节,缓冲区都会使用  Lpuart_Uart_Ip_SetRxBuffer() 进行更新;如果检测到换行符( '\n' ),则将设置接收标志以通知主循环。 当发生  LPUART_UART_IP_EVENT_END_TRANSFER  事件时,将通过  Lpuart_Uart_Ip_AsyncReceive() 重新启用接收。 注意:只执行基本的事件处理操作;仅确认其他UART事件,但不会进行处理。 此示例使用 LPUART实例6,通过USB端口(EVB上的J40和MINI EVB上的J9)实现串行通信。 ------------------------------------------------------------------------------ *测试硬件:S32K312EVB-Q172和S32K312MINI-EVB *MCU:S32K312 *IDE:S32DS3.6.2 *RTD版本:6.0.0 *调试器:PE Micro *目标:internal_FLASH  ------------------------------------------------------------------------------ 运行示例: 1. 在PC上为串行设备打开串行终端,并设置以下参数:   波特率为115200 无校验  停止位为1 无流量控制  如果您使用TeraTerm,请确保发送设置配置为 LF(换行) ,以便在按下回车键时正确发送换行符。 2. 构建并运行示例。 测试结果:   NXP 提供的任何支持、信息和技术(“材料”)均按“现状”提供,不附带任何明示或暗示的保证,且 NXP 在适用法律允许的最大范围内,否认与材料相关的所有直接或间接责任和损害。NXP 对任何与应用或产品设计相关的协助不承担任何责任。材料仅可用于与 NXP 产品相关联。NXP 可以不受限制地使用您对材料提供的任何反馈。
記事全体を表示
示例 MPC5777C-eQADC_Simple GHS714 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * 初始化 eQADC 模块并循环转换所选通道,显示 * 将其放入终端窗口。 * 用户可以将 EVB 电位器的电位器连接到引脚接头 W(见下文)以查看有效 * 转换结果。 * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777C-512DS Rev.A + MPC57xx 主板 Rev.C * 微控制器: PPC5777CMM03 2N45H CTZZS1521A *系统频率:PLL1 = core_clk = 264MHz,PLL0 = 192MHz * 调试器:Lauterbach Trace32 * 目标:internal_FLASH * 终端:19200-8-无奇偶校验-1停止位-eSCI_A上无流量控制 * EVB 连接:对于 ADC:J53-1(EVB 电位器的电位器)--> PW7 - ANB16 * PW8 - ANB17 * PW9 - ANB18 * PW10 - ANB19 ******************************************************************************** <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * 初始化 eQADC 模块并循环转换所选通道,显示 * 将其放入终端窗口。 * 用户可以将 EVB 电位器的电位器连接到引脚接头 W(见下文)以查看有效 * 转换结果。 * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777C-512DS Rev.A + MPC57xx 主板 Rev.C * 微控制器: PPC5777CMM03 2N45H CTZZS1521A *系统频率:PLL1 = core_clk = 264MHz,PLL0 = 192MHz * 调试器:Lauterbach Trace32 * 目标:internal_FLASH * 终端:19200-8-无奇偶校验-1停止位-eSCI_A上无流量控制 * EVB 连接:对于 ADC:J53-1(EVB 电位器的电位器)--> PW7 - ANB16 * PW8 - ANB17 * PW9 - ANB18 * PW10 - ANB19 ********************************************************************************
記事全体を表示
wxWidgets based distributed information and control systems There developed the controller uses i.MX53 + Linux. Has developed a solution for building distributed information and control systems. Prototmpy been in operation for over a year. Examples: - Control Electromagnetic stirring (mixer) http://ontecom.com/en/catalog/ems / Rusal, Krasnoyarsk. - Moniroring and management of pumping stations. - Monitoring and control of climate control systems. You can create a smart home systems and iot. There is experience with PLC (Power Line Communication) Qualcomm/Atheros. In my spare time I develop a budget solution for PLC (Power Line Communication) control / monitoring components smart home. Based on the standard IEC 61131-3 developed software - distributed information management system. The solution is cross-platform. In a single system may be computers of different architectures and various operating systems. Such signals are synchronized controller ARM / Linux, and x86 server (Win, Linux, VMS, ...) Uses wxWidgets. Articles on this subject is, but in Russian.
記事全体を表示
Installing Ubuntu Rootfs on NXP i.MX6 boards This post describes the setup detail for installing Ubuntu based distro in any i.Mx6x NXP Boards. Details are described on: 1. Select your board, Setting the host, Download and compile uboot , dtb and and the Kernel version on your board. 2. Installing the Ubuntu core, Lubuntu graphics desktop version and/or Build your own Ubuntu rootfs with debootstrap. 3. Modify rootfs and Installing needed packages 4. Setting with SD image. 5. Setting Ubuntu on target 6. Adding GPU acceleration 1: Select your board, Setting the host, Download and compile uboot , dtb and and the Kernel version on your board. Supported NXP HW boards: i.MX 6QuadPlus SABRE-SD Board and Platform i.MX 6Quad SABRE-SD Board and Platform i.MX 6DualLite SABRE-SD Board i.MX 6Quad SABRE-AI Board i.MX 6DualLite SABRE-AI Board i.MX 6SoloX SABRE-SD Board i.MX 6SoloX SABRE-AI Board Install host dependences (version tested 14.04): $ sudo apt-get install gparted git build-essential libncurses5 wget u-boot-tools zlib1g-dev ncurses-dev \ cmake libc-dev-armhf-cross pkg-config-arm-linux-gnueabihf build-essential checkinstall cmake \ pkg-config lzop libc6 libstdc++6 debootstrap qemu-user-static binfmt-support Download the compiler toolchain and extract it: $ cd ~/ $ wget -c https://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz $ tar xf gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz Create general variable environments: $ export target=mx6q (e.g. processor: mx6sx, mx6d, mx6dl,etc) $ export board=sabresd (e.g. sabresd, sabreauto) $ export ARCH=arm $ export CROSS_COMPILE=../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- $ unset LDFLAGS Download u-boot At the release of this document, latest uboot version was imx_3.14.52, it should work with other version as well, so please check the proper version for your board: $ cd ~/ $ wget –c http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git/snapshot/uboot-imx-rel_imx_3.14.52_1.1.0_ga.tar.gz $ tar -xf uboot-imx-rel_imx_3.14.52_1.1.0_ga.tar.gz $ cd uboot-imx-rel_imx_3.14.52_1.1.0_ga $ make $targetboard_config    # e.g. mx6qsabresd_config $ make Linux Kernel, Firmware, headers, modules and DTS files $ cd ~/ $ wget –c http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/snapshot/linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga.tar.gz $ tar xf linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga.tar.gz $ cd linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga $ make imx_v7_defconfig $ make menuconfig $ make -j4 zImage modules dtbs $ cd ~/ move your image to binary folder: $ sudo cp –v uboot-imx-rel_imx_3.14.52_1.1.0_ga/u-boot.imx binary/ $ sudo cp –v linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga/arch/arm/boot/zImage binary/ $ sudo cp –v linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga/arch/arm/boot/dts/i$target-$board.dtb binary/ Now you have the bootloader, device tree and kernel image of your board ready, let’s create the rootfs. 2: Installing the Ubuntu core, Lubuntu graphics desktop version and/or Build your own Ubuntu rootfs with debootstrap. Installing ubuntu core: $ cd ~/ $ sudo mkdir –p core /media/rootfs /media/kernel $ wget –c http://cdimage.ubuntu.com/ubuntu-core/releases/14.04/release/ubuntu-core-14.04.4-core-armhf.tar.gz $ sudo tar –xf ubuntu-core-14.04.4-core-armhf.tar.gz –C core $ sudo cp -vr core/* /media/rootfs $ cd linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga $ sudo make modules_install firmware_install INSTALL_MOD_PATH=/media/rootfs/ ARCH=arm CROSS_COMPILE=../../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- $ sudo make ARCH=arm CROSS_COMPILE=../../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- headers_install INSTALL_HDR_PATH=/media/rootfs/usr Now you should have your ubuntu rootfs on /media/rootfs folder. and you can pass to part 3 of this post. Installing ubuntu Linaro LXDE: $ cd ~/ $ sudo mkdir –p core /media/rootfs /media/kernel $ wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz $ sudo tar -xf linaro-trusty-alip-20141024-684.tar.gz –C core $ sudo mv core/binary/* core/ $ sudo rm –rf core/binary $ sudo cp -vr core/* /media/rootfs $ cd linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga $ sudo make modules_install firmware_install INSTALL_MOD_PATH=/media/rootfs/ ARCH=arm CROSS_COMPILE=../../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- $ sudo make ARCH=arm CROSS_COMPILE=../../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- headers_install INSTALL_HDR_PATH=/media/rootfs/usr Now you should have your ubuntu rootfs on /media/rootfs folder. and you can pass to part 3 of this post. Installing with debootstrap $ cd ~/ $ target=rootfs $ distro=trusty $ sudo debootstrap --arch=armhf --foreign --include=ubuntu-keyring,apt-transport-https,ca-certificates,openssl $distro "$target" http://ports.ubuntu.com $ sudo cp /usr/bin/qemu-arm-static $target/usr/bin $ sudo cp /etc/resolv.conf $target/etc Now have a minimal Ubuntu rootfs - chroot to it and perform the 2nd stage install: $ sudo chroot $target  //Now we are in chroot # distro=trusty # export LC_ALL=C LANGUAGE=C LANG=C # /debootstrap/debootstrap --second-stage Edit the sources.list repositories # cat < /etc/apt/sources.list deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse EOT # apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 40976EAF437D05B5 # apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 3B4FE6ACC0B21F32 # apt-get update # apt -y -f install # apt-get upgrade # apt-get install nano Now you should be able to login without password, then use passwd command to set one. If you like to add custom users: # passwd root # adduser # usermod -a -G tty myuser # usermod -a -G dialout, adm, sudo, dip, plugdev myuser # visudo Under the line that looks like: root ALL=(ALL:ALL) ALL add the following (change user with your actual username) ALL=(ALL) ALL your rootfs is ready, exit chroot # exit $ sudo rm $target/etc/resolv.conf $ sudo rm $target/usr/bin/qemu-arm-static $ sudo mv rootfs/* /media/rootfs $ cd linux-2.6-imx-rel_imx_3.14.52_1.1.0_ga $ sudo make modules_install firmware_install INSTALL_MOD_PATH=/media/rootfs/ ARCH=arm CROSS_COMPILE=../../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- $ sudo make ARCH=arm CROSS_COMPILE=../../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf- headers_install INSTALL_HDR_PATH=/media/rootfs/usr Now you should have your ubuntu rootfs on /media/root. 3: Modify Rootfs and Install needed packages Edit and verify the sources.list repositories $ cd /media/rootfs $ sudo cat < etc/apt/sources.list deb http://ports.ubuntu.com/ubuntu-ports/ trusty main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports/ trusty-updates main restricted universe multiverse deb http://ports.ubuntu.com/ubuntu-ports/ trusty-security main restricted universe multiverse EOT Edit networks interfaces and append in the existing file: $ sudo nano etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp If you require Serial Console, remove and include an additional line at the end of the file for  ttymxc0 output as below, $ sudo nano etc/init/tty1.conf exec /sbin/getty -8 38400 tty1 exec /sbin/getty -L 115200 ttymxc0 If you like to change the localhostname: $ sudo nano etc/hostname and change to “your name” e.g. imx6Q. Set the date and time clock and update $ sudo nano /etc/rc.local  Add this: if [ `date +"%Y"` -eq "1970" ]; then                     date --set="2016-04-01" fi exit 0 (optional for Linaro rootfs) Edit passwd and remove the x in root and linaro lines $ sudo nano etc/passwd root:x:0:0:root:/root:/bin/bash linaro:x:0:0.. and change like this:                                   root::0:0:root:/root:/bin/bash linaro:::0:.. Now you are ready to program your sd image. 4: Setup microSD/SD card For these instructions, we are assuming: DISK=/dev/sdg on your HOST, cat /proc/partitions is very useful for determining the device id. $ cd ~/ $ export DISK=/dev/sdg Erase microSD/SD card: $ sudo dd if=/dev/zero of=${DISK} bs=1M count=10 Install Bootloader $ cd binary/ $ sudo dd if=u-boot.imx of=${DISK} bs=512 seek=2 $ sync Create Partition layout: $ cd ~/ $ sudo fdisk ${DISK} steps:        d ///delete all partitions currently on sd n // create new partition p // Primary partition 1 // partition number 1 2048 //default +1G // n // created 2d parition p 2 default default 1 // firts B // to be fat32 W // write partiotions $ sudo mkfs.vfat ${DISK}1 $ sudo mkfs.ext3  ${DISK}2 Mount ext3 SD partition to /media/rootfs: $ sudo mount ${DISK1} /media/kernel_target $ sudo mount ${DISK}2 /media/rootfs_target Copy Files on the SD. $ cd ~/ $ sudo cp –v binary/ i$target-$board.dtb /media/kernel_target $ sudo cp –v binary/zImage /media/kernel_target $ sudo mv /media/rootfs/* /media/rootfs_target Remove SD: $ sync $ sudo umount /media/kernel_target $ sudo umount /media/rootfs_target Boot the target, in console you should be login as root. root@imx6QSabreSD:~# 5: Setting Ubuntu on target Note: If you have issues with sudo on user UID, need to logout and log as root: imx6Q login: root Welcome to Ubuntu 14.04.4 LTS (GNU/Linux 3.14.52 armv7l) root@imx6Q:~# chown root:root /usr/bin/sudo root@imx6Q:~# chmod 4755 /usr/bin/sudo root@imx6Q:~# exit Login with or root # # apt-get update # apt-get –f install # apt-get install locales dialog wget # dpkg-reconfigure locales # apt-get upgrade Optional – install some useful packages: # apt-get install openssh-server can-utils usbutils build-essential automake autoconf libtool Get and Install the BSP packages (EULA required) # cd /home/user # mkdir –p vpu_pack # cd vpu_pack # wget http://www.nxp.com/lgfiles/NMG/MAD/YOCTO//firmware-imx-5.3.bin # wget http://www.nxp.com/lgfiles/NMG/MAD/YOCTO//imx-vpu-5.4.32.bin # wget http://www.nxp.com/lgfiles/NMG/MAD/YOCTO//libfslcodec-4.0.8.bin # wget http://www.nxp.com/lgfiles/NMG/MAD/YOCTO//imx-lib-5.1.tar.gz # chmod +x * # ./firmware-imx-5.3.bin --auto-accept --force # mkdir –p /lib/firmware/vpu # cp -ravf firmware-imx-5.3/firmware/* /lib/firmware/ # ./imx-vpu-5.4.32.bin --auto-accept --force # cd imx-vpu-* # make PLATFORM=IMX6Q all # make install # tar -xf imx-lib-5.1.tar.gz # cd  imx-lib-5.1/ # make -j1 PLATFORM="IMX6Q" # make PLATFORM="IMX6Q" install # cd .. # ./libfslcodec-4.0.8 --auto-accept –force # cd libfslcodec-* # ./autogent.sh --prefix=/usr --enable-fhw --enable-vpu # make # make install # mv /usr/lib/imx-mm/video-codec/* /usr/lib # mv /usr/lib/imx-mm/audio-codec/* /usr/lib # rm –rf /usr/lib/imx-mm/ # cd .. # mkdir –p gpu_pack # cd gpu_pack # wget http://www.nxp.com/lgfiles/NMG/MAD/YOCTO//imx-gpu-viv-5.0.11.p7.4-hfp.bin # wget http://www.nxp.com/lgfiles/NMG/MAD/YOCTO//xserver-xorg-video-imx-viv-5.0.11.p7.4.tar.gz # chmod +x * # ./imx-gpu-viv-5.0.11.p7.4-hfp –-auto-accept -–force # cd imx-gpu* # cp g2d/usr/include/* /usr/include/ # cp -d g2d/usr/lib/* /usr/lib/ # cp -Pr gpu-core/usr/* /usr # optional: install demos # cp -r gpu-demos/opt / # optional: install gpu tools # cp -axr gpu-tools/gmem-info/usr/bin/* /usr/bin/ # cd .. Installing gstreamer-imx, IPU, VPU and GPU support: Install build deps, gstreamer1.x, this step could take some time (~350MB): # apt-get install python pkg-config git gstreamer1.0-x gstreamer1.0-tools gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-alsa libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libgstreamer-plugins-good1.0-dev g++-multilib # git clone git://github.com/Freescale/gstreamer-imx.git # cd gstreamer-imx # ln –s /usr/lib/arm-linux-gnueabihf/gstreamer-1.0/ /usr/lib/gstreamer-1.0 # ./waf configure --prefix=/usr --kernel-headers=/include # ./waf # ./waf install # cd ../../ (optional) Install libimxvpuapi library: This library provides a community based open-source API to the NXP imx-vpu library (the low-level IMX6 VPU interface). # git clone git://github.com/Freescale/libimxvpuapi.git # cd libimxvpu* # ./waf configure –-prefix=/usr # ./waf # ./waf install # cd .. note './waf install' installs artifacts to its prefix + /lib/gstreamer-1.0 but they need to be installed to /usr/lib/arm-linux-gnueabihf/gstreamer-1.0 which is why we created a symlink above before installing note g2d lib required to build G2D note that x11 library is required to build EGL sink with Vivante direct textures (only needed for X11 support) note that libfslaudiocodec is required to build audio plugins Now you are ready to test gstreamer 6: Add GPU HW Acceleration for X11 NOTE: The original version of these build instructions can be found in the Gateworks wiki . Many thanks to them for writing this! IMX6 IPU, VPU, and GPU support via GStreamer and Gstreamer-imx plugins. Many of the pieces needed (firmware and source-code) are from NXP and not freely redistributable thus must be downloaded from their mirror and extracted from a shell script that forces you to read and agree to their End User License Agreement (EULA). The following instructions can be used on top of the debootstrap and should work on other sources of Ubuntu or other Linux distributions root filesystems as well You can easily add X11 support to a base image created with the debootstrap instructions above by adding a few package groups. You will need the following: X11 server - ie Xorg Display Manager - this controls the login to the X session Window Manager - manages window position, re-sizing, decorations, etc for X clients If in any case you have installed the Linaro LXDE rootfs, it includes the Xorg X11 server, the lxdm Display Manager, the openbox Window Manager, and others useful user applications including the Chromium browser, if you do not install linaro lxde and want to install it please do: this step could take some time (~650MB)   # apt-get install xinit lxde lxterminal lxappearance lxrandr lxshortcut lxinput xinit  xserver-xorg-dev mesa-utils mesa-utils-extra Notes: you will need to add a non-root user with adduser for Chromium browser to work. You may choose to set up auto-login for that user by editing /etc/lxdm/default.conf and setting the autologin property in the base section at the beginning of the config file. /etc/xdg/lubuntu/lxdm/lxdm.conf This document takes as based kernel version 3.14.52v, vivante 5.0.11p7.4 correspond to the kernel version used. you should check the BSP release notes in order to know which xserver and Vivante GPU files need to be downloaded from the NXP repos. $ sudo nano /etc/lxdm/default.conf    [base]    autologin=user To add hardware GPU acceleration to X11 you need to add some libraries and drivers provided by Freescale from the imx-gpu-viv package. This requires signing Freescales End User License Agreement (EULA). This package provides the following: libg2d - a documented low-level API to the GPU (used by things like libimxvpuapi for gstreamer-imx and the gpu-core drivers) gpu-core - provides all the various OpenGL libs (libGL, libGLESv1_CM, libGLESv1_CL, libGLESv2, libGLSLC, libCLC, libEGL, libGAL, libOpenCL, ls libOpenVG) typically provided by the mesa project. Note that several versions of libEGL/libGAL/libGLESv2/libVIVANTE are provided for different backend rendering systems: dfb, fb, wl, x11. # cd gpu_pack #cd imx-gpu-* # cp gpu-core/usr/lib/dri/vivante_dri.so /usr/lib/xorg/modules/drivers/ # chmod 644 /usr/lib/xorg/modules/drivers/vivante_dri.so # rm /usr/lib/arm-linux-gnueabihf/mesa/libGL.so* # rm /usr/lib/arm-linux-gnueabihf/mesa-egl/libEGL.so* # rm /usr/lib/arm-linux-gnueabihf/mesa-egl/libGLESv2.so* # rm /usr/lib/arm-linux-gnueabihf/mesa-egl/libOpenVG.so* # cd ../../ # cd gpu-pack # wget http://www.nxp.com/lgfiles/NMG/MAD/YOCTO//xserver-xorg-video-imx-viv-5.0.11.p7.4.tar.gz # tar –xf xserver* # cd xserver-org-video-imx* #looks lik have to made #git init # ./fastbuild.sh  BUILD_HARD_VFP=1 XSERVER_GREATER_THAN_13=1 # cd.. # cd kernel-modu* # make Switch to gpu-core x11 backend: # backend=x11 # ln -sf libEGL-${backend}.so /usr/lib/libEGL.so # ln -sf libEGL-${backend}.so /usr/lib/libEGL.so.1 # ln -sf libEGL-${backend}.so /usr/lib/libEGL.so.1.0 # ln -sf libGAL-${backend}.so /usr/lib/libGAL.so # ln -sf libGLESv2-${backend}.so /usr/lib/libGLESv2.so # ln -sf libGLESv2-${backend}.so /usr/lib/libGLESv2.so.2 # ln -sf libGLESv2-${backend}.so /usr/lib/libGLESv2.so.2.0.0 # ln -sf libVIVANTE-${backend}.so /usr/lib/libVIVANTE.so # ln -sf libGAL_egl.dri.so /usr/lib/libGAL_egl.so # for i in egl glesv1_cm glesv2 vg; do         cp /usr/lib/pkgconfig/${i}_${backend}.pc/usr/lib/pkgconfig/${i}.pc     done #rm /usr/lib/*-dfb.so /usr/lib/*-fb.so /usr/lib/*-wl.so (Optional in case you deploy your kernel version with GPU as module) make vivante kernel module (GPU kernel driver) load on boot: # echo vivante >> /etc/modules # nano /etc/udev/rules.d/10-imx.rules KERNEL=="galcore",  MODE="0660", GROUP="video" KERNEL=="mxc_asrc",  MODE="0666" Create an xorg.conf configured for the Vivante fbdev driver: # nano /etc/X11/xorg.conf Section "Device"     Identifier "i.MX Accelerated Framebuffer Device"     Driver "vivante"     Option "fbdev" "/dev/fb0"     Option "vivante_fbdev" "/dev/fb0"     Option "HWcursor" "false" EndSection Section "ServerFlags"     Option "BlankTime"  "0"     Option "StandbyTime"  "0"     Option "SuspendTime"  "0"     Option "OffTime"  "0" EndSection # cd .. Make sure the files copied into the correct places. If all compiled and copied, you should now see a bunch of new libraries in /usr/lib! Congratulations! After you finish you can reboot your system and start playing. Testing Gstreamer examples: show gstreamer-imx plugins: # gst-inspect-1.0 | grep imx imxvpu:  imxvpuenc_mjpeg: Freescale VPU motion JPEG video encoder imxvpu:  imxvpuenc_mpeg4: Freescale VPU MPEG-4 video encoder imxvpu:  imxvpuenc_h264: Freescale VPU h.264 video encoder imxvpu:  imxvpuenc_h263: Freescale VPU h.263 video encoder imxvpu:  imxvpudec: Freescale VPU video decoder imxv4l2videosrc:  imxv4l2videosrc: V4L2 CSI Video Source imxg2d:  imxg2dcompositor: Freescale G2D video compositor imxg2d:  imxg2dvideotransform: Freescale G2D video transform imxg2d:  imxg2dvideosink: Freescale G2D video sink imxipu:  imxipucompositor: Freescale IPU video compositor imxipu:  imxipuvideosink: Freescale IPU video sink imxipu:  imxipuvideotransform: Freescale IPU video transform imxpxp:  imxpxpvideotransform: Freescale PxP video transform imxpxp:  imxpxpvideosink: Freescale PxP video sink imxipuvideosink: # gst-launch-1.0 videotestsrc ! imxipuvideosink imxg2dvideosink: # gst-launch-1.0 videotestsrc ! imxg2dvideosink The imxeglvivsink allows hardware accelerated display to a window on the X11 host # export DISPLAY=:0.0 # gst-launch-1.0 videotestsrc ! imxeglvivsink To test if you have graphics support you can run any glmark2 and/or mesa-utils or can run example of the next route: # cd /opt/viv_samples/vdk/ # ./tutorial1                                                                      //any example root@imx6Q:~# glxgears -info GL_RENDERER   = Vivante GC2000 GL_VERSION    = 2.1 2.0.1 GL_VENDOR     = Vivante Corporation GL_EXTENSIONS = WGL_ARB_extensions_string WGL_EXT_extensions_string WGL_EXT_swap_control GL_EXT_texture_env_add GL_ARB_multitexture GL_ARB_multisample GL_ARB_texture_env_add GL_ARB_texture_compression GL_ARB_texture_env_combine GL_ARB_depth_texture GL_ARB_window_pos …. 1606 frames in 5.0 seconds = 321.130 FPS 1650 frames in 5.0 seconds = 329.834 FPS L_RENDERER   = Vivante GC2000 GL_VERSION    = 2.1 2.0.1 GL_VENDOR     = Vivante Corporation1629 frames in 5.0 seconds = 325.644 FPS 1621 frames in 5.0 seconds = 324.072 FPS 1650 frames in 5.0 seconds = 329.806 FPS 1651 frames in 5.0 seconds = 330.079 FPS Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Bio_TICFSL, Thank for your excellent doc. I'm working on imx6q sabreauto. successfully flashed uboot,zimage,*dtb and rootfs in sdcard and tried to bootup the board.but it stucks at one point my debug log is below. how can i fix it? U-Boot 2015.04-gb8837c4-dirty (Aug 13 2019 - 17:05:21) CPU: Freescale i.MX6Q rev1.2 at 792 MHz CPU: Temperature 41 C Reset cause: POR Board: MX6Q-Sabreauto revA I2C: ready DRAM: 2 GiB PMIC: PFUZE100 ID=0x10 NAND: 0 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 No panel detected: default to HDMI Display: HDMI (640x480) In: serial Out: serial Err: serial switch to partitions #0, OK mmc1 is current device Net: FEC [PRIME] Error: FEC address not set. Normal Boot Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device reading boot.scr ** Unable to read file boot.scr ** reading zImage 6022032 bytes read in 293 ms (19.6 MiB/s) Booting from mmc ... reading imx6q-sabreauto.dtb 41594 bytes read in 19 ms (2.1 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x5be390 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800d279 Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 3.14.52-g0e08af9-dirty (BspDeveloper2@BspDeveloper2) (gcc version 4.8.5 (Linaro GCC 4.8-2015.06) ) #9 SMP PREEMPT Tue Aug 13 16:58:40 IST 2019 CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine model: Freescale i.MX6 Quad SABRE Automotive Board cma: CMA: reserved 320 MiB at 6a000000 Memory policy: Data cache writealloc PERCPU: Embedded 8 pages/cpu @ee71e000 s8320 r8192 d16256 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520720 Kernel command line: console=ttymxc3,115200 root=/dev/mmcblk2p2 rootwait rw PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) Memory: 1739236K/2097152K available (7452K kernel code, 460K rwdata, 2596K rodata, 392K init, 433K bss, 357916K reserved, 270336K highmem) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) lowmem : 0x80000000 - 0xef800000 (1784 MB) pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) modules : 0x7f000000 - 0x7fe00000 ( 14 MB) .text : 0x80008000 - 0x809d828c (10049 kB) .init : 0x809d9000 - 0x80a3b080 ( 393 kB) .data : 0x80a3c000 - 0x80aaf340 ( 461 kB) .bss : 0x80aaf34c - 0x80b1b99c ( 434 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Preemptible hierarchical RCU implementation. NR_IRQS:16 nr_irqs:16 16 L310 cache controller enabled l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1024 kB Switching to timer-based delay loop sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682ns Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 4096 (order: 2, 16384 bytes) Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x10717d60 - 0x10717db8 CPU1: Booted secondary processor CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 CPU2: Booted secondary processor CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 CPU3: Booted secondary processor CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Brought up 4 CPUs SMP: Total of 4 processors activated (24.00 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 pinctrl core: initialized pinctrl subsystem regulator-dummy: no parameters NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor ladder cpuidle: using governor menu CPU identified as i.MX6Q, silicon rev 1.2 Use WDOG1 as reset source syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered vdd1p1: 800 <--> 1375 mV at 1100 mV vdd3p0: 2625 <--> 3400 mV at 3000 mV vdd2p5: 2000 <--> 2750 mV at 2400 mV vddarm: 725 <--> 1450 mV at 1150 mV vddpu: 725 <--> 1450 mV vddsoc: 725 <--> 1450 mV at 1175 mV syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. hw-breakpoint: maximum watchpoint size is 4 bytes. imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver bio: create slab at 0 mxs-dma 110000.dma-apbh: initialized cs42888_supply: 3300 mV 3P3V: 3300 mV vio1: 3300 mV vio2: 3300 mV vd: 3300 mV va: 5000 mV platform usb_h1_vbus.29: Driver reg-fixed-voltage requests probe deferral platform usb_otg_vbus.30: Driver reg-fixed-voltage requests probe deferral i2c-core: driver [max17135] using legacy suspend method i2c-core: driver [max17135] using legacy resume method SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb usbphy_nop1.12 supply vcc not found, using dummy regulator usbphy_nop2.13 supply vcc not found, using dummy regulator i2c i2c-1: IMX I2C adapter registered pca953x 2-0032: failed reading register pca953x: probe of 2-0032 failed with error -5 i2c i2c-2: IMX I2C adapter registered Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]> PTP clock support registered imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) MIPI CSI2 driver module loaded Advanced Linux Sound Architecture Driver Initialized. Bluetooth: Core ver 2.18 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized cfg80211: Calling CRDA to update world regulatory domain Switched to clocksource mxc_timer1 NET: Registered protocol family 2 TCP established hash table entries: 16384 (order: 4, 65536 bytes) TCP bind hash table entries: 16384 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP: reno registered UDP hash table entries: 1024 (order: 3, 32768 bytes) UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available imx rpmsg driver is registered. imx_busfreq busfreq.16: DDR medium rate not supported. Bus freq driver module loaded futex hash table entries: 1024 (order: 4, 65536 bytes) bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. fuse init (API version 7.22) msgmni has been set to 3508 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) imx-weim 21b8000.weim: Driver registered. backlight.17 supply power not found, using dummy regulator MIPI DSI driver module loaded MIPI DSI driver module loaded mxc_sdc_fb fb.22: registered mxc display driver ldb imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) Console: switching to colour frame buffer device 128x48 mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1 fbcvt: 1920x1080@60: CVT Name - 2.073M9 mxc_sdc_fb fb.23: registered mxc display driver hdmi mxc_sdc_fb fb.24: NO mxc display driver found! mxc_sdc_fb fb.25: registered mxc display driver ldb imx-sdma 20ec000.sdma: no iram assigned, using external mem imx-sdma 20ec000.sdma: no event needs to be remapped imx-sdma 20ec000.sdma: loaded firmware 3.2 imx-sdma 20ec000.sdma: initialized pfuze100-regulator 1-0008: Full layer: 2, Metal layer: 1 pfuze100-regulator 1-0008: FAB: 0, FIN: 0 pfuze100-regulator 1-0008: pfuze100 found. SW1AB: 300 <--> 1875 mV at 1375 mV SW1C: 300 <--> 1875 mV at 1375 mV SW2: 800 <--> 3300 mV at 3000 mV SW3A: 400 <--> 1975 mV at 1500 mV SW3B: 400 <--> 1975 mV at 1500 mV SW4: 800 <--> 1975 mV at 1800 mV SWBST: 5000 <--> 5150 mV at 5000 mV VSNVS: 1000 <--> 3000 mV at 3000 mV VREFDDR: 750 mV VGEN1: 800 <--> 1550 mV at 800 mV VGEN2: 800 <--> 1550 mV at 1500 mV VGEN3: 1800 <--> 3300 mV at 1800 mV VGEN4: 1800 <--> 3300 mV at 1800 mV VGEN5: 1800 <--> 3300 mV at 2500 mV VGEN6: 1800 <--> 3300 mV at 2800 mV Serial: IMX driver 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60, base_baud = 5000000) is a IMX 21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 61, base_baud = 5000000) is a IMX console [ttymxc3] enabled serial: Freescale lpuart driver imx sema4 driver is registered. [drm] Initialized drm 1.1.0 20060810 [drm] Initialized vivante 1.0.0 20120216 on minor 0 brd: module loaded loop: module loaded si476x-core 1-0063: Using default platform data. si476x-core 1-0063: No IRQ number specified, will use polling si476x-core 1-0063: Error while sending command 0x11 si476x-core 1-0063: The device in inconsistent power state ahci-imx 2200000.sata: fsl,transmit-level-mV not specified, using 00000024 ahci-imx 2200000.sata: fsl,transmit-boost-mdB not specified, using 00000480 ahci-imx 2200000.sata: fsl,transmit-atten-16ths not specified, using 00002000 ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000 ahci-imx 2200000.sata: failed to reset phy: -110 ahci-imx: probe of 2200000.sata failed with error -110 CAN device driver interface 2094000.can supply xceiver not found, using dummy regulator flexcan 2094000.can: device registered (reg_base=f01f0000, irq=143) ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-mxc: Freescale On-Chip EHCI Host driver usbcore: registered new interface driver usb-storage usbcore: registered new interface driver usb_ehset_test 2184800.usbmisc supply vbus-wakeup not found, using dummy regulator imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517 platform 2184000.usb: Driver imx_usb requests probe deferral imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517 platform 2184200.usb: Driver imx_usb requests probe deferral mousedev: PS/2 mouse device common for all mice egalax_ts 1-0004: Failed to read firmware version egalax_ts: probe of 1-0004 failed with error -5 2-0044 supply vdd not found, using dummy regulator i2c-core: driver [isl29023] using legacy suspend method i2c-core: driver [isl29023] using legacy resume method snvs_rtc 20cc034.snvs-rtc-lp: can't get snvs-rtc clock snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0 i2c /dev entries driver IR NEC protocol handler initialized IR RC5(x) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR RC5 (streamzap) protocol handler initialized IR SANYO protocol handler initialized IR MCE Keyboard/mouse protocol handler initialized mxc_v4l2_output v4l2_out.33: V4L2 device registered as video16 mxc_v4l2_output v4l2_out.33: V4L2 device registered as video17 mxc_v4l2_output v4l2_out.33: V4L2 device registered as video18 mxc_v4l2_output v4l2_out.33: V4L2 device registered as video19 mxc_v4l2_output v4l2_out.33: V4L2 device registered as video20 2-000e supply vdd not found, using dummy regulator 2-000e supply vddio not found, using dummy regulator mag3110 2-000e: check mag3110 chip ID mag3110 2-000e: read chip ID 0xfffffffb is not equal to 0xc4! mag3110: probe of 2-000e failed with error -22 i2c-core: driver [mag3110] using legacy suspend method i2c-core: driver [mag3110] using legacy resume method 2-001c supply vdd not found, using dummy regulator 2-001c supply vddio not found, using dummy regulator mma8451 2-001c: read chip ID 0x1 is not equal to 0x1a or 0x2a! mma8451: probe of 2-001c failed with error -22 imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0) Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized Bluetooth: HCI BCSP protocol initialized Bluetooth: HCIATH3K protocol initialized usbcore: registered new interface driver bcm203x usbcore: registered new interface driver btusb usbcore: registered new interface driver ath3k sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper mmc1: no vqmmc regulator found mmc1: no vmmc regulator found mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA mmc2: no vqmmc regulator found mmc2: no vmmc regulator found mmc2: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA Galcore version 5.0.11.33433 mmc1: new high speed DDR MMC card at address 0001 mmcblk1: mmc1:0001 VM010B 14.5 GiB mmcblk1boot0: mmc1:0001 VM010B partition 1 512 KiB mmcblk1boot1: mmc1:0001 VM010B partition 2 512 KiB mmcblk1rpmb: mmc1:0001 VM010B partition 3 512 KiB Alternate GPT is invalid, using primary GPT. mmcblk1: p1 p2 p3 p4 p5 p6 p7 mmcblk1boot1: unknown partition table mmcblk1boot0: unknown partition table mmc2: host does not support reading read-only switch. assuming write-enable. mmc2: new high speed SDHC card at address e624 mmcblk2: mmc2:e624 SS16G 14.8 GiB mmcblk2: p1 p2 mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed mxc_vpu 2040000.vpu: VPU initialized caam 2100000.caam: Instantiated RNG4 SH0 caam 2100000.caam: Instantiated RNG4 SH1 caam 2100000.caam: device ID = 0x0a160100 (Era 4) caam 2100000.caam: job rings = 2, qi = 0 caam algorithms registered in /proc/crypto caam_jr 2101000.jr0: registering rng-caam platform caam_sm: blkkey_ex: 4 keystore units available platform caam_sm: 64-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: 64-bit black key: platform caam_sm: [0000] 17 d4 14 e3 cd 14 99 3c platform caam_sm: [0008] 28 ac 13 da 4f 13 86 b9 platform caam_sm: 128-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: 128-bit black key: platform caam_sm: [0000] 47 20 d5 8a 08 2e c9 76 platform caam_sm: [0008] 21 a3 ab 86 72 eb e0 d7 platform caam_sm: 192-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: [0016] 10 11 12 13 14 15 16 17 platform caam_sm: 192-bit black key: platform caam_sm: [0000] a0 ab 18 b1 c0 86 52 c3 platform caam_sm: [0008] 26 02 62 70 a8 78 4c f2 platform caam_sm: [0016] 4e 6c e5 31 7e 6c d1 25 platform caam_sm: [0024] 48 62 78 86 93 70 62 ff platform caam_sm: 256-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: [0016] 10 11 12 13 14 15 16 17 platform caam_sm: [0024] 18 19 1a 1b 1c 1d 1e 1f platform caam_sm: 256-bit black key: platform caam_sm: [0000] 61 42 d7 cf 79 ad 81 5c platform caam_sm: [0008] cc 1b 9e 5c a0 20 0e 54 platform caam_sm: [0016] ed fa 74 03 08 e1 96 e2 platform caam_sm: [0024] 5c 85 e0 cc ab f4 9e 3b platform caam_sm: 64-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 128-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 196-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 256-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 64-bit black key in blob: platform caam_sm: [0000] fc e1 2d 2c 81 75 5e 99 platform caam_sm: [0008] 2d 93 9b b0 a6 5a 3d 49 platform caam_sm: [0016] 98 96 9d 0c 39 36 da 72 platform caam_sm: [0024] f9 1d 66 0c 78 24 20 9a platform caam_sm: [0032] 85 3c 92 1e a4 55 d2 4b platform caam_sm: [0040] e4 7a ed 19 af 70 2e f6 platform caam_sm: [0048] cf c9 07 0e 82 19 47 7f platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 128-bit black key in blob: platform caam_sm: [0000] c6 ae 04 56 f6 5e c2 1b platform caam_sm: [0008] d9 6c 07 89 9d 1e 20 0f platform caam_sm: [0016] 72 4c 63 e1 ed d2 fd 68 platform caam_sm: [0024] 99 81 17 32 33 39 2a 1c platform caam_sm: [0032] fb e4 bb db 0c 07 c0 f2 platform caam_sm: [0040] eb 23 cf 79 64 2a ca f3 platform caam_sm: [0048] d9 84 ac 22 0b 49 79 e9 platform caam_sm: [0056] 7d 8b 97 09 6a d4 72 0b platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 192-bit black key in blob: platform caam_sm: [0000] 9c ec 58 09 50 20 80 1d platform caam_sm: [0008] 21 b6 e3 64 41 ed 14 12 platform caam_sm: [0016] 16 e1 c7 d3 fe 54 40 ed platform caam_sm: [0024] bc 92 e0 0c 6b 0a ec 02 platform caam_sm: [0032] 3b 60 6f 18 20 26 e4 04 platform caam_sm: [0040] c2 94 5e 2f 1e e4 99 b1 platform caam_sm: [0048] 9c 05 65 95 9b 8d db 72 platform caam_sm: [0056] a8 50 b0 50 9d f8 67 66 platform caam_sm: [0064] 33 ae 46 e9 42 6c fb ab platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 256-bit black key in blob: platform caam_sm: [0000] 9b 50 6d 78 93 a8 08 84 platform caam_sm: [0008] e5 3b 26 18 1d 6a 42 80 platform caam_sm: [0016] 3f c9 7f 4d dd 1a b6 a3 platform caam_sm: [0024] 02 6a 4d 64 a6 cc c3 61 platform caam_sm: [0032] 15 9e c8 1f 75 72 01 af platform caam_sm: [0040] f5 87 b3 78 b0 78 3f 34 platform caam_sm: [0048] bf 19 80 05 72 32 c2 82 platform caam_sm: [0056] d1 fd 4c f7 c6 c9 98 85 platform caam_sm: [0064] 9d 02 55 75 35 d5 ef ca platform caam_sm: [0072] 80 f5 21 87 ef 6c cd 96 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: restored 64-bit black key: platform caam_sm: [0000] 47 9d fa 49 f0 cf c5 1c platform caam_sm: [0008] 90 4d 0a e3 a1 ee 72 5c platform caam_sm: restored 128-bit black key: platform caam_sm: [0000] 47 20 d5 8a 08 2e c9 76 platform caam_sm: [0008] 21 a3 ab 86 72 eb e0 d7 platform caam_sm: restored 192-bit black key: platform caam_sm: [0000] a0 ab 18 b1 c0 86 52 c3 platform caam_sm: [0008] 26 02 62 70 a8 78 4c f2 platform caam_sm: [0016] 8d 0d bc 2d 2c 90 67 0c platform caam_sm: [0024] 93 91 ea 59 81 df 52 df platform caam_sm: restored 256-bit black key: platform caam_sm: [0000] 61 42 d7 cf 79 ad 81 5c platform caam_sm: [0008] cc 1b 9e 5c a0 20 0e 54 platform caam_sm: [0016] ed fa 74 03 08 e1 96 e2 platform caam_sm: [0024] 5c 85 e0 cc ab f4 9e 3b snvs-secvio 20cc000.caam-snvs: can't get snvs clock snvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure state usbcore: registered new interface driver usbhid usbhid: USB HID core driver cs42xx8 1-0048: found device, revision 4 fsl-asrc 2034000.asrc: driver registered snd-soc-dummy snd-soc-dummy: ASoC: Failed to create platform debugfs directory imx-cs42888 sound-cs42888.26: cs42888 <-> 2024000.esai mapping ok imx-cs42888 sound-cs42888.26: snd-soc-dummy-dai <-> 2034000.asrc mapping ok imx-cs42888 sound-cs42888.26: cs42888 <-> 2024000.esai mapping ok imx-spdif sound-spdif.19: snd-soc-dummy-dai <-> 2004000.spdif mapping ok imx-audio-hdmi sound-hdmi.20: hdmi-hifi <-> hdmi_audio.3 mapping ok imx-tuner-si476x sound-fm.31: failed to find FM platform device imx-tuner-si476x: probe of sound-fm.31 failed with error -22 NET: Registered protocol family 26 TCP: cubic registered NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 can: controller area network core (rev 20120528 abi 9) NET: Registered protocol family 29 can: raw protocol (rev 20120528) can: broadcast manager protocol (rev 20120528 t) can: netlink gateway (rev 20130117) max_hops=1 Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP socket layer initialized Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Bluetooth: HIDP socket layer initialized 8021q: 802.1Q VLAN Support v1.8 Key type dns_resolver registered VGEN2: disabling SWBST: disabling SW4: disabling regulator-dummy: disabling imx mcc test is registered. platform usb_h1_vbus.29: Driver reg-fixed-voltage requests probe deferral usb_otg_vbus: 5000 mV imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517 platform 2184200.usb: Driver imx_usb requests probe deferral platform usb_h1_vbus.29: Driver reg-fixed-voltage requests probe deferral snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:02 UTC (2) imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517 ALSA device list: #0: cs42888-audio #1: imx-spdif #2: imx-hdmi-soc p�� �platform usb_h1_vbus.29: Driver reg-fixed-voltage requests probe deferral kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk2p2): using internal journal EXT3-fs (mmcblk2p2): recovery complete EXT3-fs (mmcblk2p2): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:34. devtmpfs: error mounting -2 Freeing unused kernel memory: 392K (809d9000 - 80a3b000) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. CPU2: stopping CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.14.52-g0e08af9-dirty #9 [<80014764>] (unwind_backtrace) from [<80011488>] (show_stack+0x10/0x14) [<80011488>] (show_stack) from [<807119b4>] (dump_stack+0x7c/0xbc) [<807119b4>] (dump_stack) from [<80013718>] (handle_IPI+0x144/0x158) [<80013718>] (handle_IPI) from [<800085b0>] (gic_handle_irq+0x58/0x5c) [<800085b0>] (gic_handle_irq) from [<80011f80>] (__irq_svc+0x40/0x70) Exception stack(0xd80adf50 to 0xd80adf98) df40: d80adf98 3b9aca00 e9b5de9d 00000000 df60: e882c038 00000000 ee72f0d0 80a4a814 00000001 ee72f0d4 d80ac000 d80ac000 df80: a6aaaaab d80adf98 00000009 804b64bc 60000113 ffffffff [<80011f80>] (__irq_svc) from [<804b64bc>] (cpuidle_enter_state+0x50/0xe0) [<804b64bc>] (cpuidle_enter_state) from [<804b6648>] (cpuidle_idle_call+0xfc/0x150) [<804b6648>] (cpuidle_idle_call) from [<8000edf0>] (arch_cpu_idle+0x8/0x44) [<8000edf0>] (arch_cpu_idle) from [<8006b140>] (cpu_startup_entry+0x104/0x150) [<8006b140>] (cpu_startup_entry) from [<10008644>] (0x10008644) CPU0: stopping CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.14.52-g0e08af9-dirty #9 [<80014764>] (unwind_backtrace) from [<80011488>] (show_stack+0x10/0x14) [<80011488>] (show_stack) from [<807119b4>] (dump_stack+0x7c/0xbc) [<807119b4>] (dump_stack) from [<80013718>] (handle_IPI+0x144/0x158) [<80013718>] (handle_IPI) from [<800085b0>] (gic_handle_irq+0x58/0x5c) [<800085b0>] (gic_handle_irq) from [<80011f80>] (__irq_svc+0x40/0x70) Exception stack(0x80a3df18 to 0x80a3df60) df00: 80a3df60 3b9aca00 df20: e9b5de9d 00000000 e883714d 00000000 ee71f0d0 80a4a814 00000001 ee71f0d4 df40: 80a3c000 80a3c000 a6aaaaab 80a3df60 00000009 804b64bc 60000113 ffffffff [<80011f80>] (__irq_svc) from [<804b64bc>] (cpuidle_enter_state+0x50/0xe0) [<804b64bc>] (cpuidle_enter_state) from [<804b6648>] (cpuidle_idle_call+0xfc/0x150) [<804b6648>] (cpuidle_idle_call) from [<8000edf0>] (arch_cpu_idle+0x8/0x44) [<8000edf0>] (arch_cpu_idle) from [<8006b140>] (cpu_startup_entry+0x104/0x150) [<8006b140>] (cpu_startup_entry) from [<809d9af0>] (start_kernel+0x350/0x35c) CPU3: stopping CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.14.52-g0e08af9-dirty #9 [<80014764>] (unwind_backtrace) from [<80011488>] (show_stack+0x10/0x14) [<80011488>] (show_stack) from [<807119b4>] (dump_stack+0x7c/0xbc) [<807119b4>] (dump_stack) from [<80013718>] (handle_IPI+0x144/0x158) [<80013718>] (handle_IPI) from [<800085b0>] (gic_handle_irq+0x58/0x5c) [<800085b0>] (gic_handle_irq) from [<80011f80>] (__irq_svc+0x40/0x70) Exception stack(0xd80aff50 to 0xd80aff98) ff40: d80aff98 3b9aca00 e9b5de9d 00000000 ff60: e882c2d3 00000000 ee7370d0 80a4a814 00000001 ee7370d4 d80ae000 d80ae000 ff80: a6aaaaab d80aff98 00000009 804b64bc 60000113 ffffffff [<80011f80>] (__irq_svc) from [<804b64bc>] (cpuidle_enter_state+0x50/0xe0) [<804b64bc>] (cpuidle_enter_state) from [<804b6648>] (cpuidle_idle_call+0xfc/0x150) [<804b6648>] (cpuidle_idle_call) from [<8000edf0>] (arch_cpu_idle+0x8/0x44) [<8000edf0>] (arch_cpu_idle) from [<8006b140>] (cpu_startup_entry+0x104/0x150) [<8006b140>] (cpu_startup_entry) from [<10008644>] (0x10008644) Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hello, Can same instrctions can be used with imx.8? Thanks Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi  in section "Download u-boot" I excuted the "make" instruction and seens like it doesnt work, show as below what's wrong with it?how can i fixed it? Thanks.. ../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc: 1: ../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc: Syntax error: "(" unexpected ../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc: 1: ../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc: Syntax error: "(" unexpected dirname: missing operand Try 'dirname --help' for more information. scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config.h GEN include/autoconf.mk ../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc: 1: ../gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc: Syntax error: "(" unexpected scripts/Makefile.autoconf:71: recipe for target 'include/autoconf.mk' failed make[1]: *** [include/autoconf.mk] Error 1 make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/uboot.release'. Stop. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Basically, I found the solution. To generate a zImage instead of Image, you have to enter make menuconfig and select this option Gzip is not the defaut choice.  Now I have a ubuntu 14.04 running on my I.MX6Q SABRESD board. Thanks for this essential post ! Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hello, Thanks for this great post ! My goal is to run an Ubuntu 14.04 or higher on my IMX6Q SABRE SD board from the mmc card. I am following the post.  The following link is not valid any more: https://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz  I replace it by the following one:  https://releases.linaro.org/archive/14.09/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz But it does not work, I get the following strange error: (same error described by wenming feng) /bin/sh: 1: /home/guillaume/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux/bin/arm-linux-gnueabihf-gcc: not found  If I select this toolchain, I can compile: gcc-linaro-4.8-2015.06-x86_64_arm-linux-xxxx But I am generating an Image file and NOT a zImage file. And u-boot does not take it (bad linux arm zimage magic error at u boot runtime). It seems that it exists uImage, Image and zImage. Image would correspond to a 64bit image if I understand correctly.   Question 1: Which toolchain or option I have to use/set to generate a zImage ? (and not an Image) Question 2: Would it be possible to update this post with up to date links ? Question 3: Is there somewhere an already builded .sdcard for SABRE SD with everything on it (u-boot, kernel, dtb, ubuntu 14.04 or higher ..) ? Best regards, Guillaume HUGUES Re: Installing Ubuntu Rootfs on NXP i.MX6 boards I am using imx6q-sabresd board. I am following steps from Installing Ubuntu Rootfs on NXP i.MX6 boards.  My kernel version is 3.14.52 and i am using ubuntu Rootfs 14.04. My Xorg xserver version is 1.15.1. I am observing that if i enable PCI bus support in the kernel, then i am not able to use x11 gpu hardware acceleration(glxgears and es2gears give segmentation faults). But if i disable PCI support , i could use x11 gpu hardware acceleration with above mentioned versions of xserver. What role is PCI drivers playing in x11 hardware acceleration? How to get x11 acceleration working with PCI bus support enabled. Has anyone faced similar issue? Is there any fix for this or patches for pci or drm drivers?? Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Wenming, I ignore the cd kernel-modu* too. My board is i.mx6q sabre sd and I use a LVDS display. Have you try the toolchain gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz as the doc discribed? You can search "Kane Jiang" in the Skype for Business. All the Best Kane Jiang Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Kane, I am used the linaro-trusty-alip-20141024-684.tar.gz , I can not start the desktop for my imx6dl customer board, I used an OSD-WVGA lcd to connect with ipu.di0/fb0. for the ubuntu core version I can not boot into console. about the kernel-modu* there is a link in the note:ventana/ubuntu – Gateworks  section 2, what I do just ignore the cd kernel-modu* make, I just cd /usr/lib to do the ln -sf . the fastbuild.sh only build the vivante_drv.so, the vivante_dri.so is copy from gpu_core. I can not find any folder name kernel-modu* maybe a mistake. BTW,  what is you video= line, Thanks! Wenming Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi @Bio_TICFSL, Thanks for your excellent doc!!  There's two questions I have get now. 1. I did not find the folder named kernel-modu* as the doc said, where is it? # ./fastbuild.sh  BUILD_HARD_VFP=1 XSERVER_GREATER_THAN_13=1   # cd..      # cd kernel-modu*   # make   Switch to gpu-core x11 backend:   # backend=x11     2. And when I use the rootfs named linaro-jessie-alip-20160428-22.tar.gz(debian based ubuntu 16.04), I can not successfully login to the console: [FAILED] Failed to start Login Service. See 'systemctl status systemd-logind.service' for details. [ OK ] Started Permit User Sessions. [FAILED] Failed to start LSB: Load kernel mo...eeded to enable cpufreq scaling. See 'systemctl status loadcpufreq.service' for details. [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started LSB: network benchmark. [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started Initialize hardware monitoring sensors. [ TIME ] Timed out waiting for device dev-ttymxc0.device. [DEPEND] Dependency failed for Serial Getty on ttymxc0. [FAILED] Failed to start Network Manager. See 'systemctl status NetworkManager.service' for details. So how to login to the console, any ideas? All the Best Kane Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Wenming, You may try command: apt-get install libxtst-dev to overcome the fatal error: X11/extensions/Xext.h: No such file or directory. All the Best Kane Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Wenming, Which rootfs did you choose? I think you may not choose the Linaro LXDE rootfs(E.g. linaro-trusty-alip-20141024-684.tar.gz) as mentioned in the doc above. The  vivid-preinstalled-core-armhf.tar.gz I mentioned didn't have a GUI desktop, it just have a console terminal. And it seems that did not support the commands like apt-get. But I also tried the rootfs linaro-trusty-alip-20141024-684.tar.gz as same as the doc. And I can succeed to bring up the desktop in i.MX6Q SABRE SD, but there's some issues about how to find the GPU Vivante and play tutorials. Besides, I did not find the folder named kernel-modu* as the doc said, have you? # ./fastbuild.sh  BUILD_HARD_VFP=1 XSERVER_GREATER_THAN_13=1   # cd..      # cd kernel-modu*   # make   Switch to gpu-core x11 backend:   # backend=x11   All the Best Kane Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Kane, I export the BUILD_HARD_VFP=1 and XSERVER_GREATER_THAN_13=1 it will not make for the DRI_1.10.4/src/, but I still got  fatal: bad default revision 'HEAD' fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git [ ...] -- [ ...]' fsl_pixmap_ext.c:31:33: fatal error: X11/extensions/Xext.h: No such file or directory #include Does me missed some installed package? BTW, as your mentioned vivid-preinstalled-core-armhf.tar.gz  are you tried and success to bring up the desktop for your imx6 board? thanks! Wenming Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, Prathamesh You can run the command: git init as the the doc said to have a try. You can open the ubuntu-core link in the Explorer and use another. E.g in the link: Index of /ubuntu-core/vivid/daily-preinstalled/current  You may select vivid-preinstalled-core-armhf.tar.gz . Kane Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Pratham, I got the same issue with you. Do you get it worked? Thanks! Wenming Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi erikraynolds‌ , I have the same question as yours. There seems no folder named kernel-modu*. Have you solved the problem now? Thanks! Kane Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi feng, the issue "Waiting for root device /dev/mmcblk0p2.." , seems to be related to sd card initialization failure, once kernel comes up. Try to boot from eMMc and see if you still get same issue. I am using toolchain mentioned above in this post. Thanks, Prathamesh  Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Pratham, Do you used any patches?  I can not boot into rootfs on my mx6dl customer board, I only can start uboot and kernel. Kenerl will stop at waiting "Waiting for root device /dev/mmcblk0p2... which version of toolchain are you used? Thanks! Wenming Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, I am using above steps to get ubuntu rootfs running on imx6q-sabrsd board. I am not able to build xserver-xorg-video-imx-viv-5.0.11.p7.4. I am getting below error with linaro rootfs: gcc -DCOMMIT="`git log -n 1 --format=%H``git diff-index --quiet HEAD || echo '-dirty'`" -DFIX_NO_MI_BACKINGSTORE -fvisibility=hidden -fPIC -DPIc fatal: Not a git repository (or any of the parent directories): .git fatal: Not a git repository (or any of the parent directories): .git gcc -shared -fPIC -o vivante_drv.so vivante_gal/vivante_gal_blit.o vivante_gal/vivante_gal_gpu.o vivante_gal/vivante_gal_surface.o vivante_fbde make: Leaving directory `/root/gpu/xserver-xorg-video-imx-viv-5.0.11.p7.4/EXA/src' make: *** DRI_1.10.4/src/: No such file or directory. Stop. has anybody able to solve this issue?? Also has anybody tried brnigup with ubuntu-core rootfs? Link for ubuntu-core rootfs seems dead. Thanks, Prathamesh Re: Installing Ubuntu Rootfs on NXP i.MX6 boards It seems now no way to build by this thread. I changed the gcc toolchain, still not compilable. But I can build one month ago, there should be some commits blocked the build. Does someone else encounter the same issue as me currently? Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, I installed ubuntu Linaro LXDE desktop but the touch panel doesn't work. I confirmed the touch panel driver is ok. It generates input events when I cat /dev/input/event0 and touch the panel. But the ubuntu desktop does not have response. Anyone has advice on it? Thanks! Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, I encounter a uboot compiler issue, when I try to build the wandboard_dl_defconfig. Anybody else encounter this? share your fix. LD examples/standalone/hello_world OBJCOPY examples/standalone/hello_world.srec OBJCOPY examples/standalone/hello_world.bin LDS u-boot.lds LD u-boot arch/arm/imx-common/built-in.o: In function `print_cpuinfo': /home/lucid/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga/arch/arm/imx-common/cpu.c:199: undefined reference to `uclass_get_device' /home/lucid/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga/arch/arm/imx-common/cpu.c:201: undefined reference to `thermal_get_temp' arch/arm/imx-common/built-in.o: In function `arch_preboot_os': /home/lucid/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga/arch/arm/imx-common/cpu.c:270: undefined reference to `ldo_mode_set' drivers/built-in.o: In function `read_cpu_temperature': /home/lucid/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga/drivers/thermal/imx_thermal.c:43: undefined reference to `dev_get_platdata' /home/lucid/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga/drivers/thermal/imx_thermal.c:45: undefined reference to `dev_get_priv' drivers/built-in.o: In function `imx_thermal_probe': /home/lucid/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga/drivers/thermal/imx_thermal.c:226: undefined reference to `dev_get_platdata' /home/lucid/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga/drivers/thermal/imx_thermal.c:227: undefined reference to `dev_get_priv' /home/lucid/toolchain/gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils) Linaro 2014.11-3-git 2.24.0.20141017 assertion fail /home/tcwg-buildslave/workspace/tcwg-make-release/label/tcwg-x86_64/target/arm-linux-gnueabihf/snapshots/binutils-gdb.git~linaro_binutils-2_24-branch@a93e252ee5250dba831e54f98336b40c7210dac7/bfd/elf32-arm.c:7710 /home/lucid/toolchain/gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils) Linaro 2014.11-3-git 2.24.0.20141017 assertion fail /home/tcwg-buildslave/workspace/tcwg-make-release/label/tcwg-x86_64/target/arm-linux-gnueabihf/snapshots/binutils-gdb.git~linaro_binutils-2_24-branch@a93e252ee5250dba831e54f98336b40c7210dac7/bfd/elf32-arm.c:7710 /home/lucid/toolchain/gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils) Linaro 2014.11-3-git 2.24.0.20141017 assertion fail /home/tcwg-buildslave/workspace/tcwg-make-release/label/tcwg-x86_64/target/arm-linux-gnueabihf/snapshots/binutils-gdb.git~linaro_binutils-2_24-branch@a93e252ee5250dba831e54f98336b40c7210dac7/bfd/elf32-arm.c:7710 /home/lucid/toolchain/gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils) Linaro 2014.11-3-git 2.24.0.20141017 assertion fail /home/tcwg-buildslave/workspace/tcwg-make-release/label/tcwg-x86_64/target/arm-linux-gnueabihf/snapshots/binutils-gdb.git~linaro_binutils-2_24-branch@a93e252ee5250dba831e54f98336b40c7210dac7/bfd/elf32-arm.c:7710 /home/lucid/toolchain/gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils) Linaro 2014.11-3-git 2.24.0.20141017 assertion fail /home/tcwg-buildslave/workspace/tcwg-make-release/label/tcwg-x86_64/target/arm-linux-gnueabihf/snapshots/binutils-gdb.git~linaro_binutils-2_24-branch@a93e252ee5250dba831e54f98336b40c7210dac7/bfd/elf32-arm.c:7710 /home/lucid/toolchain/gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld.bfd: error: required section '.rel.plt' not found in the linker script /home/lucid/toolchain/gcc-linaro-4.8-2015.06-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-ld.bfd: final link failed: Invalid operation make: *** [u-boot] Error 1 lucid@ubuntu:~/imx6dl/uboot-imx-rel_imx_3.14.52_1.1.0_ga$ Thanks! WF Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Dears, I'd like to continue with adding GPU HW Acceleration for X11 per instruction with that section and working within gpu_pack directory instructions say: # cd kernel-modu*   # make   Switch to gpu-core x11 backend:   # backend=x11   Where kernel-modu* is coming from? How kernel-modu* to create from? Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, Is there anyway to rotate LCD from landscape mode to portrait mode with ubuntu Linaro LXDE rootfs? Thanks! Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, I connected USB disk and USB mouse to the USB Host port, but the devices were not able to be detected. I can see following message during kernel booting up: usb_otg_vbus: disabling What could be the possible reasons? Thanks! Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi What error are you getting. I am still having the error messages I posted but my audio is working nonetheless so I stopped troubleshooting further on it until someone gives me an idea what should be done. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Cool. I had changed it to 'linaro' user which also doesnt have a password but still showed me login page. Anyways will try 'root.' But I was getting launched into desktop directly already so dont know if I should bother. Anyways thank for the info.  Re: Installing Ubuntu Rootfs on NXP i.MX6 boards I can login as root with no login screen automatically. this works for me /etc/lxdm$ lxdm.conf [base] ## uncomment and set autologin username to enable autologin autologin=root ## uncomment and set timeout to enable timeout autologin, ## the value should >=5 # timeout=10 ## default session or desktop used when no systemwide config session=/usr/bin/startlxde ## uncomment and set to set numlock on your keyboard # numlock=0 ## set this if you don't want to put xauth file at ~/.Xauthority # xauth_path=/tmp ## greeter used to welcome the user greeter=/usr/lib/lxdm/lxdm-greeter-gtk [server] ## arg used to start xserver, not fully function # arg=/usr/bin/X -background vt1 [display] ## gtk theme used by greeter gtk_theme=Clearlooks ## background of the greeter bg=/usr/share/backgrounds/default.png ## if show bottom pane bottom_pane=1 ## if show language select control lang=1 ## if show keyboard layout select control keyboard=0 ## the theme of greeter theme=Industrial [input] [userlist] ## if disable the user list control at greeter disable=0 ## whitelist user white= ## blacklist user black= Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Nice. Do let me know if you figure out how to remove the login page completely from 'startlxde'. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Have you fixed gstreamer-imx somehow? Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Finally I got login: After I got LXDE login screen which I needed to switch off the GUI and start in console mode via CTRL+ALT+F1 then I set passwd for root again and then switch back via CTRL+ALT+F7 and I did login as root. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Erik, Maybe you have not installed xorg and xinit. Try that. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Understand but on my side after install I can't run 'startx' command (command not found). I have my console on PC host side where I'm connected to the target via UART. On target itself I got Login screen which I can't go thru. I did changes as you suggested but no success. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Erik,    If you have also used Linaro LXDE then the default display manager is lxdm which is upstarted from /etc/init.d/. Lxdm uses /etc/lxdm/lxdm.conf for its configuration. I changed the default session to 'startx' to avoid the login page. Just a workaround for now. More info here : LXDM - ArchWiki  Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Jaffin, I'm in  pretty much the same situation: have you chance to resolve it? Thank you. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Erik Any idea how to boot into desktop rather than to the login window I am getting. When I execute startx from serial console, it starts desktop environment on the screen. But by default, startlxde is getting executed and that takes me to the login page from where I cant login with any user. By default I want startx to load. (later I would like to just boot into just one gui application) Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Erik, I am using iMX6 QP Sabre Board. Everything is working fine just that I am unable to login through the gui login manager. Also I am facing another issue today. I installed gstreamer-imx and its plugins but I am getting an error with the audio codec plugin which is not working. When I run 'gst-inspect-1.0 -b' I get. (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory (gst-plugin-scanner:8983): GStreamer-WARNING **: Failed to load plugin '/usr/lib/arm-linux-gnueabihf/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/gstreamer-1.0/libgstimxaudio.so': lib_mp3_enc_arm12_elinux.so.2: cannot open shared object file: No such file or directory Blacklisted files: libgstimxaudio.so Total count: 1 blacklisted file I dont understand why only audio plugin got blacklisted when I installed both fsl video and audio codec together. I have followed the links from this post. Also the error that it shows that it cannot open shared file, I checked the directory and the file is inside it. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards What imx board/chip do you use? Re: Installing Ubuntu Rootfs on NXP i.MX6 boards First of all, thanks for this amazing post. Helped a lot. I have used the Linaro LXDE rootfs(partly because the ubuntu core link didnt work). Now apart from few hiccups I faced here and there in the process, I am able to boot the hardware and login from the serial console to the shell. But on the HDMI display I am shown a login window. I tried typing username 'root' and 'linaro' without any password(since I had removed the password from the root and linaro user as per the process above) and I am still stuck on the same window. I am unable to move past the login window and enter the GUI. Did anyone else face this. Please advise if I have missed something. Or I could just remove this login window manager and install another. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Now I got Linaro, 14.10 image booting.. but still get into HDMI display and it's Serial console from PC. How can I enable and run it form within HDMI monitor? Secondly I followed  section 3: Modify Rootfs and Install needed packages  even though network, sources.list, hostname are not configured accordingly.. I change it on host PC and those setting are not reflected...       U-Boot 2016.03 (Nov 04 2016 - 11:24:24 +0100) CPU: Freescale i.MX6QP rev1.0 996 MHz (running at 792 MHz) CPU: Automotive temperature grade (-40C to 125C) at 31C Reset cause: POR Board: MX6Q-Sabreauto revA I2C: ready DRAM: 2 GiB PMIC: PFUZE100 ID=0x10 NAND: 0 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 No panel detected: default to Hannstar-XGA Display: Hannstar-XGA (1024x768) In: serial Out: serial Err: serial switch to partitions #0, OK mmc1 is current device Net: FEC [PRIME] Normal Boot Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device reading boot.scr ** Unable to read file boot.scr ** reading zImage 6637656 bytes read in 328 ms (19.3 MiB/s) Booting from mmc ... reading imx6qp-sabreauto.dtb 48853 bytes read in 20 ms (2.3 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x654858 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800eed4 Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 4.1.15 (r59400@Latitude) (gcc version 4.8.5 (Linaro GCC 4.8-2015.06) ) #1 SMP PREEMPT Fri Nov 4 11:53:43 CET 2016 CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine model: Freescale i.MX6 Quad Plus SABRE Automotive Board Reserved memory: created CMA memory pool at 0x6a000000, size 320 MiB Reserved memory: initialized node linux,cma, compatible id shared-dma-pool Memory policy: Data cache writealloc PERCPU: Embedded 12 pages/cpu @ee6fe000 s16960 r8192 d24000 u49152 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520720 Kernel command line: console=ttymxc3,115200 root=/dev/mmcblk2p2 rootwait rw PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) Memory: 1737928K/2097152K available (8295K kernel code, 435K rwdata, 2892K rodata, 432K init, 450K bss, 31544K reserved, 327680K cma-reserved, 270336K highmem) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) lowmem : 0x80000000 - 0xef800000 (1784 MB) pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) modules : 0x7f000000 - 0x7fe00000 ( 14 MB) .text : 0x80008000 - 0x80af51c8 (11189 kB) .init : 0x80af6000 - 0x80b62000 ( 432 kB) .data : 0x80b62000 - 0x80bcec40 ( 436 kB) .bss : 0x80bd1000 - 0x80c41a5c ( 451 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Preemptible hierarchical RCU implementation. Additional per-CPU info printed with stalls. NR_IRQS:16 nr_irqs:16 16 L2C-310 erratum 769419 enabled L2C-310 enabling early BRESP for Cortex-A9 L2C-310 full line of zeros enabled for Cortex-A9 L2C-310 ID prefetch enabled, offset 16 lines L2C-310 dynamic clock gating enabled, standby mode enabled L2C-310 cache controller enabled, 16 ways, 1024 kB L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76470001 mxc_clocksource_init 3000000 Switching to timer-based delay loop, resolution 333ns sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns clocksource mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 4096 (order: 2, 16384 bytes) Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x10008280 - 0x100082d8 CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Brought up 4 CPUs SMP: Total of 4 processors activated (24.00 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns pinctrl core: initialized pinctrl subsystem NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor ladder cpuidle: using governor menu CPU identified as i.MX6QP, silicon rev 1.0 hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. hw-breakpoint: maximum watchpoint size is 4 bytes. imx6q-pinctrl 20e0000.iomuxc: no groups defined in /soc/aips-bus@02000000/iomuxc@020e0000/hdmicecgrp imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver imx-gpc 20dc000.gpc: no fsl,ldo-bypass found! mxs-dma 110000.dma-apbh: initialized SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb 2000000.aips-bus:usbphy_nop1 supply vcc not found, using dummy regulator 2000000.aips-bus:usbphy_nop2 supply vcc not found, using dummy regulator i2c i2c-1: IMX I2C adapter registered i2c i2c-1: can't use DMA i2c i2c-2: IMX I2C adapter registered i2c i2c-2: can't use DMA Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]> PTP clock support registered imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) imx-prg 21cc000.prg: driver probed imx-prg 21cd000.prg: driver probed imx-pre 21c8000.pre: driver probed imx-pre 21c9000.pre: driver probed imx-pre 21ca000.pre: driver probed imx-pre 21cb000.pre: driver probed MIPI CSI2 driver module loaded Advanced Linux Sound Architecture Driver Initialized. Bluetooth: Core ver 2.20 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized Switched to clocksource mxc_timer1 NET: Registered protocol family 2 TCP established hash table entries: 16384 (order: 4, 65536 bytes) TCP bind hash table entries: 16384 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 16384) UDP hash table entries: 1024 (order: 3, 32768 bytes) UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. CPU PMU: Failed to parse /soc/pmu/interrupt-affinity[0] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available imx rpmsg driver is registered. Bus freq driver module loaded futex hash table entries: 1024 (order: 4, 65536 bytes) VFS: Disk quotas dquot_6.6.0 VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. fuse init (API version 7.23) bounce: pool size: 64 pages io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) backlight supply power not found, using dummy regulator MIPI DSI driver module loaded MIPI DSI driver module loaded mxc_sdc_fb fb@0: registered mxc display driver ldb imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) Console: switching to colour frame buffer device 128x48 mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1 fbcvt: 1920x1080@60: CVT Name - 2.073M9 mxc_sdc_fb fb@1: registered mxc display driver hdmi mxc_sdc_fb fb@2: NO mxc display driver found! mxc_sdc_fb fb@3: registered mxc display driver ldb mxc_hdmi 20e0000.hdmi_video: Read EDID again imx-sdma 20ec000.sdma: no iram assigned, using external mem imx-sdma 20ec000.sdma: no event needs to be remapped imx-sdma 20ec000.sdma: loaded firmware 3.3 imx-sdma 20ec000.sdma: initialized pfuze100-regulator 1-0008: Full layer: 2, Metal layer: 1 pfuze100-regulator 1-0008: FAB: 0, FIN: 0 pfuze100-regulator 1-0008: pfuze100 found. 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 298, base_baud = 5000000) is a IMX 21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 299, base_baud = 5000000) is a IMX mxc_hdmi 20e0000.hdmi_video: create default modelist console [ttymxc3] enabled imx sema4 driver is registered. [drm] Initialized drm 1.1.0 20060810 [drm] Initialized vivante 1.0.0 20120216 on minor 0 brd: module loaded loop: module loaded si476x-core 1-0063: Using default platform data. si476x-core 1-0063: No IRQ number specified, will use polling si476x-core 1-0063: Error while sending command 0x11 si476x-core 1-0063: The device in inconsistent power state ahci-imx 2200000.sata: fsl,transmit-level-mV not specified, using 00000024 ahci-imx 2200000.sata: fsl,transmit-boost-mdB not specified, using 00000480 ahci-imx 2200000.sata: fsl,transmit-atten-16ths not specified, using 00002000 ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000 ahci-imx 2200000.sata: SSS flag set, parallel bus scan disabled ahci-imx 2200000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode ahci-imx 2200000.sata: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst scsi host0: ahci-imx ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 313 CAN device driver interface 2188000.ethernet supply phy not found, using dummy regulator pps pps0: new PPS source ptp0 libphy: fec_enet_mii_bus: probed fec 2188000.ethernet eth0: registered PHC device 0 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-mxc: Freescale On-Chip EHCI Host driver usbcore: registered new interface driver usb-storage usbcore: registered new interface driver usb_ehset_test 2184800.usbmisc supply vbus-wakeup not found, using dummy regulator imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517 imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517 mousedev: PS/2 mouse device common for all mice egalax_ts 1-0004: Failed to read firmware version egalax_ts: probe of 1-0004 failed with error -5 2-0044 supply vdd not found, using dummy regulator input: isl29023 light sensor as /devices/virtual/input/input1 isl29023 2-0044: driver version 1.0 enabled snvs_rtc 20cc000.snvs:snvs-rtc-lp: rtc core: registered 20cc000.snvs:snvs-r as rtc0 i2c /dev entries driver IR NEC protocol handler initialized IR RC5(x/sz) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR SANYO protocol handler initialized IR Sharp protocol handler initialized IR MCE Keyboard/mouse protocol handler initialized IR XMP protocol handler initialized mxc_v4l2_output v4l2_out: V4L2 device registered as video16 mxc_v4l2_output v4l2_out: V4L2 device registered as video17 mxc_v4l2_output v4l2_out: V4L2 device registered as video18 mxc_v4l2_output v4l2_out: V4L2 device registered as video19 mxc_v4l2_output v4l2_out: V4L2 device registered as video20 2-000e supply vdd not found, using dummy regulator 2-000e supply vddio not found, using dummy regulator mag3110 2-000e: check mag3110 chip ID input: mag3110 as /devices/virtual/input/input2 mag3110 2-000e: mag3110 is probed 2-001c supply vdd not found, using dummy regulator 2-001c supply vddio not found, using dummy regulator input: mma845x as /devices/virtual/input/input3 imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0) Bluetooth: HCI UART driver ver 2.3 Bluetooth: HCI UART protocol H4 registered Bluetooth: HCI UART protocol BCSP registered Bluetooth: HCI UART protocol ATH3K registered ata1: SATA link down (SStatus 0 SControl 300) ahci-imx 2200000.sata: no device found, disabling link. usbcore: registered new interface driver bcm203x usbcore: registered new interface driver btusb usbcore: registered new interface driver ath3k ahci-imx 2200000.sata: pass ahci_imx..hotplug=1 to enable hotplug sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper /soc/aips-bus@02100000/usdhc@02190000: voltage-ranges unspecified sdhci-esdhc-imx 2190000.usdhc: Got CD GPIO sdhci-esdhc-imx 2190000.usdhc: No vmmc regulator found sdhci-esdhc-imx 2190000.usdhc: No vqmmc regulator found mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA /soc/aips-bus@02100000/usdhc@02198000: voltage-ranges unspecified sdhci-esdhc-imx 2198000.usdhc: Got CD GPIO sdhci-esdhc-imx 2198000.usdhc: Got WP GPIO sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found mmc2: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA 218c000.mlb supply reg_nvcc not found, using dummy regulator mxc_mlb150 218c000.mlb: enalbe regulator mxc_vpu 2040000.vpu_fsl: VPU initialized mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed imx6q-pinctrl 20e0000.iomuxc: unable to find group for node hdmicecgrp imx6q-pinctrl 20e0000.iomuxc: unable to find group for node hdmicecgrp mxc_hdmi_cec soc:hdmi_cec@00120000: can't get/select CEC pinctrl Galcore version 5.0.11.41671 mmc2: new ultra high speed SDR104 SDHC card at address 0007 mmcblk2: mmc2:0007 SD32G 28.9 GiB mmcblk2: p1 p2 caam 2100000.caam: Entropy delay = 3200 caam 2100000.caam: Instantiated RNG4 SH0 caam 2100000.caam: Instantiated RNG4 SH1 caam 2100000.caam: device ID = 0x0a16010000000000 (Era -524) caam 2100000.caam: job rings = 2, qi = 0 caam algorithms registered in /proc/crypto caam_jr 2101000.jr0: registering rng-caam platform caam_sm: blkkey_ex: 4 keystore units available platform caam_sm: 64-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: 64-bit black key: platform caam_sm: [0000] b1 20 7c 0a 8a 86 61 07 platform caam_sm: [0008] f0 19 01 46 38 76 bd 49 platform caam_sm: 128-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: 128-bit black key: platform caam_sm: [0000] 2f 06 82 1f cc b0 35 1f platform caam_sm: [0008] 72 03 b1 f3 aa e0 3e b0 platform caam_sm: 192-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: [0016] 10 11 12 13 14 15 16 17 platform caam_sm: 192-bit black key: platform caam_sm: [0000] 1b b3 ad 95 d0 24 81 9a platform caam_sm: [0008] fd b9 b8 4c 55 17 92 c4 platform caam_sm: [0016] ae af b5 6a ea 59 01 4f platform caam_sm: [0024] 1b be de e8 dd 5c 8b 10 platform caam_sm: 256-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: [0016] 10 11 12 13 14 15 16 17 platform caam_sm: [0024] 18 19 1a 1b 1c 1d 1e 1f platform caam_sm: 256-bit black key: platform caam_sm: [0000] cf f7 16 54 2e 7b 19 e0 platform caam_sm: [0008] fe 96 8c 8b 3e 1b b3 f0 platform caam_sm: [0016] 38 35 bc 80 67 35 ed 58 platform caam_sm: [0024] e1 dd 73 11 85 8b 10 1f platform caam_sm: 64-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 128-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 196-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 256-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 64-bit black key in blob: platform caam_sm: [0000] 7c 66 1b 86 2d 1c b7 2d platform caam_sm: [0008] 20 1f bb eb b4 00 1c 56 platform caam_sm: [0016] 8f b7 46 a6 40 58 28 49 platform caam_sm: [0024] 55 a0 50 1c 58 1d 43 a9 platform caam_sm: [0032] 06 3c 86 13 da 7d c1 6a platform caam_sm: [0040] 3b 09 77 ee 3a ee 3f e6 platform caam_sm: [0048] 7e be 58 92 f4 b9 1d 4a platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 128-bit black key in blob: platform caam_sm: [0000] 61 a7 fd 69 ac 06 3c 35 platform caam_sm: [0008] 55 aa 49 66 c1 d2 ee 49 platform caam_sm: [0016] 04 af 80 4a fe 33 92 ab platform caam_sm: [0024] 9c a7 c3 82 25 53 80 63 platform caam_sm: [0032] 22 3e 89 9a e6 d8 a6 54 platform caam_sm: [0040] c6 e6 f7 34 b6 1f 2c 9e platform caam_sm: [0048] 5e 96 89 5e a6 fc 7f 87 platform caam_sm: [0056] 20 5f 7a 16 11 3b e7 ce platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 192-bit black key in blob: platform caam_sm: [0000] 23 2c cb 1b 73 ab 7d 23 platform caam_sm: [0008] f4 b0 f7 92 b2 78 0d 4c platform caam_sm: [0016] b7 ba 1e 4d 05 6d 31 f5 platform caam_sm: [0024] ce c9 fd 0a ce 39 eb 94 platform caam_sm: [0032] cb b1 33 41 b7 f7 6b 26 platform caam_sm: [0040] 44 80 d7 26 36 25 ad 73 platform caam_sm: [0048] 87 a0 51 29 82 7f 9c d8 platform caam_sm: [0056] 2f 75 98 5f b7 50 f3 db platform caam_sm: [0064] b3 39 17 c7 c9 90 c8 26 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 256-bit black key in blob: platform caam_sm: [0000] 49 ff 5a d8 79 44 e7 67 platform caam_sm: [0008] 96 87 75 f6 5c 8a 2e df platform caam_sm: [0016] ae cc a1 b6 4a 31 f6 e8 platform caam_sm: [0024] 8d fd ad 8b 07 f3 e8 b0 platform caam_sm: [0032] c0 58 18 9b ae 02 bb ce platform caam_sm: [0040] 38 fb 44 db 04 67 1b c7 platform caam_sm: [0048] 2c 15 75 41 8d c1 77 cf platform caam_sm: [0056] a1 68 de 68 2d cd 24 e7 platform caam_sm: [0064] d5 7e e3 22 eb 7a 21 9d platform caam_sm: [0072] 63 67 cf 3b 32 19 e0 03 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: restored 64-bit black key: platform caam_sm: [0000] 95 c8 a2 bc ac 2e 8e d7 platform caam_sm: [0008] f7 cc fa 5b b6 a5 5b 4b platform caam_sm: restored 128-bit black key: platform caam_sm: [0000] 2f 06 82 1f cc b0 35 1f platform caam_sm: [0008] 72 03 b1 f3 aa e0 3e b0 platform caam_sm: restored 192-bit black key: platform caam_sm: [0000] 1b b3 ad 95 d0 24 81 9a platform caam_sm: [0008] fd b9 b8 4c 55 17 92 c4 platform caam_sm: [0016] 5f 82 48 34 d8 cb 15 a9 platform caam_sm: [0024] b0 6c fe c8 ee 8e cd 21 platform caam_sm: restored 256-bit black key: platform caam_sm: [0000] cf f7 16 54 2e 7b 19 e0 platform caam_sm: [0008] fe 96 8c 8b 3e 1b b3 f0 platform caam_sm: [0016] 38 35 bc 80 67 35 ed 58 platform caam_sm: [0024] e1 dd 73 11 85 8b 10 1f snvs-secvio 20cc000.caam-snvs: can't get snvs clock snvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure state usbcore: registered new interface driver usbhid usbhid: USB HID core driver cs42xx8 1-0048: found device, revision 4 fsl-asrc 2034000.asrc: driver registered imx-cs42888 sound-cs42888: cs42888 <-> 2024000.esai mapping ok imx-cs42888 sound-cs42888: snd-soc-dummy-dai <-> 2034000.asrc mapping ok imx-cs42888 sound-cs42888: cs42888 <-> 2024000.esai mapping ok imx-spdif sound-spdif: snd-soc-dummy-dai <-> 2004000.spdif mapping ok imx-tuner-si476x sound-fm: failed to find FM platform device imx-tuner-si476x: probe of sound-fm failed with error -22 imx-audio-hdmi sound-hdmi: hdmi-hifi <-> soc:hdmi_audio@00120000 mapping ok NET: Registered protocol family 26 NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 can: controller area network core (rev 20120528 abi 9) NET: Registered protocol family 29 can: raw protocol (rev 20120528) can: broadcast manager protocol (rev 20120528 t) can: netlink gateway (rev 20130117) max_hops=1 Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP socket layer initialized Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Bluetooth: HIDP socket layer initialized 8021q: 802.1Q VLAN Support v1.8 Key type dns_resolver registered can-stby: supplied by can-en flexcan 2094000.flexcan: device registered (reg_base=f0648000, irq=31) ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected ci_hdrc ci_hdrc.1: EHCI Host Controller ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2 ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00 hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected dhd_module_init in input: gpio-keys as /devices/soc0/gpio-keys/input/input4 snvs_rtc 20cc000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01 00:00:02 UTC (2) can-stby: disabling can-en: disabling VGEN2: disabling SWBST: disabling SW4: disabling ALSA device list: #0: cs42888-audio #1: imx-spdif #2: imx-hdmi-soc usb 1-1: new high-speed USB device number 2 using ci_hdrc hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.2: new low-speed USB device number 3 using ci_hdrc input: DELL DELL USB Laser Mouse as /devices/soc0/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C063.0001/input/input5 hid-generic 0003:046D:C063.0001: input: USB HID v1.10 Mouse [DELL DELL USB Laser Mouse] on usb-ci_hdrc.0-1.2/input0 usb 1-1.3: new low-speed USB device number 4 using ci_hdrc input: Dell Dell QuietKey Keyboard as /devices/soc0/soc/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:413C:2106.0002/input/input6 hid-generic 0003:413C:2106.0002: input: USB HID v1.10 Keyboard [Dell Dell QuietKey Keyboard] on usb-ci_hdrc.0-1.3/input0 kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk2p2): using internal journal EXT3-fs (mmcblk2p2): recovery complete EXT3-fs (mmcblk2p2): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:2. devtmpfs: mounted Freeing unused kernel memory: 432K (80af6000 - 80b62000) Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory random: init urandom read with 34 bits of entropy available init: plymouth-upstart-bridge main process (175) terminated with status 1 init: plymouth-upstart-bridge main process ended, respawning init: plymouth-upstart-bridge main process (185) terminated with status 1 init: plymouth-upstart-bridge main process ended, respawning init: plymouth-upstart-bridge main process (189) terminated with status 1 init: plymouth-upstart-bridge main process ended, respawning init: ureadahead main process (178) terminated with status 5 init: mounted-proc main process (204) terminated with status 1 DBG sensor data is at 7f010188 * Stopping Send an event to indicate plymouth is up [ OK ] * Starting Mount filesystems on boot [ OK ] * Starting Signal sysvinit that the rootfs is mounted [ OK ] * Starting Populate /dev filesystem [ OK ] * Stopping Populate /dev filesystem [ OK ] * Starting Clean /tmp directory [ OK ] * Starting Populate and link to /run filesystem [ OK ] * Stopping Clean /tmp directory [ OK ] * Stopping Populate and link to /run filesystem [ OK ] * Stopping Track if upstart is running in a container [ OK ] * Starting Initialize or finalize resolvconf [ OK ] * Starting set console keymap [ OK ] * Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * Starting Bridge udev events into upstart [ OK ] * Stopping set console keymap [ OK ] * Starting device node and kernel event manager [ OK ] * Starting Signal sysvinit that local filesystems are mounted [ OK ] * Starting Signal sysvinit that remote filesystems are mounted [ OK ] * Starting load modules from /etc/modules [ OK ] * Starting cold plug devices [ OK ] * Starting log initial device creation [ OK ] * Stopping load modules from /etc/modules [ OK ] * Starting flush early job output to logs [ OK ] * Stopping Mount filesystems on boot [ OK ] * Stopping flush early job output to logs [ OK ] * Starting D-Bus system message bus [ OK ] * Starting set console font [ OK ] * Starting SystemD login management service [ OK ] * Stopping set console font [ OK ] * Starting userspace bootsplash [ OK ] * Stopping userspace bootsplash [ OK ] * Starting Send an event to indicate plymouth is up [ OK ] * Starting bluetooth daemon [ OK ] * Stopping Send an event to indicate plymouth is up [ OK ] * Starting system logging daemon [ OK ] * Starting configure network device security [ OK ] * Starting mDNS/DNS-SD daemon [ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated * Starting configure network device [ OK ] * Starting Reload cups, upon starting avahi-daemon to make sure remote q[fail]are populated * Starting configure network device security [ OK ] * Starting configure network device [ OK ] * Starting configure network device security [ OK ] * Starting configure network device security [ OK ] * Starting configure network device [ OK ] * Starting Mount network filesystems [ OK ] * Starting Failsafe Boot Delay [ OK ] * Stopping Mount network filesystems [ OK ] * Starting configure network device [ OK ] * Stopping Failsafe Boot Delay [ OK ] * Starting System V initialisation compatibility [ OK ] * Setting up X socket directories... [ OK ] * Stopping System V initialisation compatibility [ OK ] Last login: Thu Jan 1 00:00:23 UTC 1970 on tty1 Welcome to Linaro 14.04 (GNU/Linux 4.1.15 armv7l) * Documentation: https://wiki.linaro.org/ root@linaro-alip:~# Re: Installing Ubuntu Rootfs on NXP i.MX6 boards I did compile for 4.1.15 kernel but I need to set (configure) proper board instead of Board: MX6Q-Sabreauto revA I need to have: MX6QP-Sabreauto Where and how to configure it? How can I redirect display to HDMI? U-Boot 2016.03 (Nov 03 2016 - 11:28:37 +0100) CPU: Freescale i.MX6QP rev1.0 996 MHz (running at 792 MHz) CPU: Automotive temperature grade (-40C to 125C) at 28C Reset cause: POR Board: MX6Q-Sabreauto revA I2C: ready DRAM: 2 GiB PMIC: PFUZE100 ID=0x10 NAND: 0 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment No panel detected: default to Hannstar-XGA Display: Hannstar-XGA (1024x768) In: serial Out: serial Err: serial switch to partitions #0, OK mmc1 is current device Net: FEC [PRIME] Normal Boot Hit any key to stop autoboot: 0 Re: Installing Ubuntu Rootfs on NXP i.MX6 boards How can I redirect output to HDMI monitor? I am trying to start the system but I got stuck at  * Stopping save kernel messages                                         [ OK ] U-Boot 2015.04 (Nov 02 2016 - 23:46:14) CPU: Freescale i.MX6QP rev1.0 at 792 MHz CPU: Temperature 33 C Reset cause: POR Board: MX6Q-Sabreauto revA I2C: ready DRAM: 2 GiB PMIC: PFUZE100 ID=0x10 NAND: 0 MiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment No panel detected: default to Hannstar-XGA Display: Hannstar-XGA (1024x768) In: serial Out: serial Err: serial switch to partitions #0, OK mmc1 is current device Net: FEC [PRIME] Normal Boot Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device reading boot.scr ** Unable to read file boot.scr ** reading zImage 6022776 bytes read in 309 ms (18.6 MiB/s) Booting from mmc ... reading imx6qp-sabreauto.dtb 46893 bytes read in 20 ms (2.2 MiB/s) Kernel image @ 0x12000000 [ 0x000000 - 0x5be678 ] ## Flattened Device Tree blob at 18000000 Booting using the fdt blob at 0x18000000 Using Device Tree in place at 18000000, end 1800e72c Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 3.14.52 (r59400@Latitude) (gcc version 4.8.5 (Linaro GCC 4.8-2015.06) ) #3 SMP PREEMPT Wed Nov 2 23:55:53 CET 2016 CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine model: Freescale i.MX6 Quad Plus SABRE Automotive Board cma: CMA: reserved 320 MiB at 6a000000 Memory policy: Data cache writealloc PERCPU: Embedded 8 pages/cpu @ee71d000 s8320 r8192 d16256 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520720 Kernel command line: console=ttymxc3,115200 root=/dev/mmcblk2p2 rootwait rw PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes) Inode-cache hash table entries: 131072 (order: 7, 524288 bytes) Memory: 1739228K/2097152K available (7452K kernel code, 460K rwdata, 2596K rodata, 392K init, 433K bss, 357924K reserved, 270336K highmem) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) lowmem : 0x80000000 - 0xef800000 (1784 MB) pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) modules : 0x7f000000 - 0x7fe00000 ( 14 MB) .text : 0x80008000 - 0x809d82d4 (10049 kB) .init : 0x809d9000 - 0x80a3b080 ( 393 kB) .data : 0x80a3c000 - 0x80aaf340 ( 461 kB) .bss : 0x80aaf34c - 0x80b1b99c ( 434 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Preemptible hierarchical RCU implementation. NR_IRQS:16 nr_irqs:16 16 L310 cache controller enabled l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32070000, Cache size: 1024 kB Switching to timer-based delay loop sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682ns Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 4096 (order: 2, 16384 bytes) Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Setting up static identity map for 0x10718008 - 0x10718060 CPU1: Booted secondary processor CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 CPU2: Booted secondary processor CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 CPU3: Booted secondary processor CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Brought up 4 CPUs SMP: Total of 4 processors activated (24.00 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 pinctrl core: initialized pinctrl subsystem regulator-dummy: no parameters NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor ladder cpuidle: using governor menu CPU identified as i.MX6QP, silicon rev 1.0 Use WDOG1 as reset source syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered vdd1p1: 800 <--> 1375 mV at 1100 mV vdd3p0: 2625 <--> 3400 mV at 3000 mV vdd2p5: 2000 <--> 2750 mV at 2400 mV vddarm: 725 <--> 1450 mV at 1150 mV vddpu: 725 <--> 1450 mV at 1150 mV vddsoc: 725 <--> 1450 mV at 1175 mV syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. hw-breakpoint: maximum watchpoint size is 4 bytes. imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver bio: create slab at 0 mxs-dma 110000.dma-apbh: initialized cs42888_supply: 3300 mV 3P3V: 3300 mV vio1: 3300 mV vio2: 3300 mV vd: 3300 mV va: 5000 mV platform usb_h1_vbus.30: Driver reg-fixed-voltage requests probe deferral platform usb_otg_vbus.31: Driver reg-fixed-voltage requests probe deferral P3V3_SDa_SWITCHED: 3300 mV i2c-core: driver [max17135] using legacy suspend method i2c-core: driver [max17135] using legacy resume method SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb usbphy_nop1.12 supply vcc not found, using dummy regulator usbphy_nop2.13 supply vcc not found, using dummy regulator i2c i2c-1: IMX I2C adapter registered i2c i2c-2: IMX I2C adapter registered Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]> PTP clock support registered imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7) imx-prg 21cc000.prg: driver probed imx-prg 21cd000.prg: driver probed imx-pre 21c8000.pre: driver probed imx-pre 21c9000.pre: driver probed imx-pre 21ca000.pre: driver probed imx-pre 21cb000.pre: driver probed MIPI CSI2 driver module loaded Advanced Linux Sound Architecture Driver Initialized. Bluetooth: Core ver 2.18 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized cfg80211: Calling CRDA to update world regulatory domain Switched to clocksource mxc_timer1 NET: Registered protocol family 2 TCP established hash table entries: 16384 (order: 4, 65536 bytes) TCP bind hash table entries: 16384 (order: 5, 131072 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP: reno registered UDP hash table entries: 1024 (order: 3, 32768 bytes) UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available imx rpmsg driver is registered. imx_busfreq busfreq.16: DDR medium rate not supported. Bus freq driver module loaded futex hash table entries: 1024 (order: 4, 65536 bytes) bounce pool size: 64 pages VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. fuse init (API version 7.22) msgmni has been set to 3508 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) backlight.17 supply power not found, using dummy regulator MIPI DSI driver module loaded MIPI DSI driver module loaded mxc_sdc_fb fb.23: registered mxc display driver ldb imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7) Console: switching to colour frame buffer device 128x48 mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1 fbcvt: 1920x1080@60: CVT Name - 2.073M9 mxc_sdc_fb fb.24: registered mxc display driver hdmi mxc_sdc_fb fb.25: NO mxc display driver found! mxc_sdc_fb fb.26: registered mxc display driver ldb imx-sdma 20ec000.sdma: no iram assigned, using external mem imx-sdma 20ec000.sdma: no event needs to be remapped imx-sdma 20ec000.sdma: loaded firmware 3.2 mxc_hdmi 20e0000.hdmi_video: Read EDID again imx-sdma 20ec000.sdma: initialized pfuze100-regulator 1-0008: Full layer: 2, Metal layer: 1 pfuze100-regulator 1-0008: FAB: 0, FIN: 0 pfuze100-regulator 1-0008: pfuze100 found. SW1AB: 300 <--> 1875 mV at 1375 mV SW1C: 300 <--> 1875 mV at 1375 mV SW2: 800 <--> 1975 mV at 1375 mV SW3A: 400 <--> 1975 mV at 1350 mV SW3B: 400 <--> 1975 mV at 1350 mV SW4: 800 <--> 1975 mV at 1825 mV SWBST: 5000 <--> 5150 mV at 5000 mV VSNVS: 1000 <--> 3000 mV at 3000 mV VREFDDR: 750 mV VGEN1: 800 <--> 1550 mV at 1200 mV VGEN2: 800 <--> 1550 mV at 1500 mV VGEN3: 1800 <--> 3300 mV at 1800 mV VGEN4: 1800 <--> 3300 mV at 3000 mV VGEN5: 1800 <--> 3300 mV at 2500 mV VGEN6: 1800 <--> 3300 mV at 2800 mV Serial: IMX driver 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60, base_baud = 5000000) is a IMX 21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 61, base_baud = 5000000) is a IMX mxc_hdmi 20e0000.hdmi_video: create default modelist console [ttymxc3] enabled serial: Freescale lpuart driver imx sema4 driver is registered. [drm] Initialized drm 1.1.0 20060810 [drm] Initialized vivante 1.0.0 20120216 on minor 0 brd: module loaded loop: module loaded si476x-core 1-0063: Using default platform data. si476x-core 1-0063: No IRQ number specified, will use polling si476x-core 1-0063: Error while sending command 0x11 si476x-core 1-0063: The device in inconsistent power state ahci-imx 2200000.sata: fsl,transmit-level-mV not specified, using 00000024 ahci-imx 2200000.sata: fsl,transmit-boost-mdB not specified, using 00000480 ahci-imx 2200000.sata: fsl,transmit-atten-16ths not specified, using 00002000 ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000 ahci-imx 2200000.sata: SSS flag set, parallel bus scan disabled ahci-imx 2200000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode ahci-imx 2200000.sata: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst scsi0 : ahci_platform ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71 CAN device driver interface 2094000.can supply xceiver not found, using dummy regulator flexcan 2094000.can: device registered (reg_base=f0238000, irq=143) 2188000.ethernet supply phy not found, using dummy regulator pps pps0: new PPS source ptp0 libphy: fec_enet_mii_bus: probed fec 2188000.ethernet eth0: registered PHC device 0 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-mxc: Freescale On-Chip EHCI Host driver usbcore: registered new interface driver usb-storage usbcore: registered new interface driver usb_ehset_test 2184800.usbmisc supply vbus-wakeup not found, using dummy regulator imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517 platform 2184000.usb: Driver imx_usb requests probe deferral imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517 platform 2184200.usb: Driver imx_usb requests probe deferral mousedev: PS/2 mouse device common for all mice egalax_ts 1-0004: Failed to read firmware version egalax_ts: probe of 1-0004 failed with error -5 2-0044 supply vdd not found, using dummy regulator input: isl29023 light sensor as /devices/virtual/input/input1 isl29023 2-0044: driver version 1.0 enabled i2c-core: driver [isl29023] using legacy suspend method i2c-core: driver [isl29023] using legacy resume method snvs_rtc 20cc034.snvs-rtc-lp: can't get snvs-rtc clock snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0 i2c /dev entries driver IR NEC protocol handler initialized IR RC5(x) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR RC5 (streamzap) protocol handler initialized IR SANYO protocol handler initialized IR MCE Keyboard/mouse protocol handler initialized mxc_v4l2_output v4l2_out.35: V4L2 device registered as video16 mxc_v4l2_output v4l2_out.35: V4L2 device registered as video17 mxc_v4l2_output v4l2_out.35: V4L2 device registered as video18 mxc_v4l2_output v4l2_out.35: V4L2 device registered as video19 mxc_v4l2_output v4l2_out.35: V4L2 device registered as video20 2-000e supply vdd not found, using dummy regulator 2-000e supply vddio not found, using dummy regulator mag3110 2-000e: check mag3110 chip ID input: mag3110 as /devices/virtual/input/input2 mag3110 2-000e: mag3110 is probed i2c-core: driver [mag3110] using legacy suspend method i2c-core: driver [mag3110] using legacy resume method 2-001c supply vdd not found, using dummy regulator 2-001c supply vddio not found, using dummy regulator ata1: SATA link down (SStatus 0 SControl 300) ahci-imx 2200000.sata: no device found, disabling link. ahci-imx 2200000.sata: pass ahci_imx..hotplug=1 to enable hotplug input: mma845x as /devices/virtual/input/input3 imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0) Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized Bluetooth: HCI BCSP protocol initialized Bluetooth: HCIATH3K protocol initialized usbcore: registered new interface driver bcm203x usbcore: registered new interface driver btusb usbcore: registered new interface driver ath3k sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper mmc0: no vqmmc regulator found mmc0: no vmmc regulator found mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA mmc2: no vqmmc regulator found mmc2: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA Warning: No contiguous memory is reserverd for gpu.! Warning: Will use default value(134217728) for the reserved memory! Galcore version 5.0.11.41671 mmc2: Problem setting current limit! mmc2: new ultra high speed DDR50 SDHC card at address aaaa mmcblk2: mmc2:aaaa SU08G 7.40 GiB mmcblk2: p1 p2 mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed mxc_vpu 2040000.vpu: VPU initialized caam 2100000.caam: Instantiated RNG4 SH0 caam 2100000.caam: Instantiated RNG4 SH1 caam 2100000.caam: device ID = 0x0a160100 (Era 4) caam 2100000.caam: job rings = 2, qi = 0 caam algorithms registered in /proc/crypto caam_jr 2101000.jr0: registering rng-caam platform caam_sm: blkkey_ex: 4 keystore units available platform caam_sm: 64-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: 64-bit black key: platform caam_sm: [0000] e5 67 1a 32 44 12 3e 71 platform caam_sm: [0008] 35 de 20 2e 43 ce ec 82 platform caam_sm: 128-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: 128-bit black key: platform caam_sm: [0000] d4 b2 d2 cd de 16 e3 b1 platform caam_sm: [0008] 13 7c 1e af 4c a4 40 14 platform caam_sm: 192-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: [0016] 10 11 12 13 14 15 16 17 platform caam_sm: 192-bit black key: platform caam_sm: [0000] 3d 4f 1d c9 83 84 b5 8a platform caam_sm: [0008] 50 8e de 15 8e 02 00 8d platform caam_sm: [0016] 67 cd 31 2d c6 9c 13 60 platform caam_sm: [0024] 35 2d b7 c2 10 76 36 e9 platform caam_sm: 256-bit clear key: platform caam_sm: [0000] 00 01 02 03 04 0f 06 07 platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f platform caam_sm: [0016] 10 11 12 13 14 15 16 17 platform caam_sm: [0024] 18 19 1a 1b 1c 1d 1e 1f platform caam_sm: 256-bit black key: platform caam_sm: [0000] c4 4e d7 b6 3e 43 2f 66 platform caam_sm: [0008] 36 df f3 c9 1c b4 d5 28 platform caam_sm: [0016] 4b 48 f0 e6 04 2e 87 2c platform caam_sm: [0024] 30 f4 10 8d c6 91 bd 77 platform caam_sm: 64-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 128-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 196-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 256-bit unwritten blob: platform caam_sm: [0000] 00 00 00 00 00 00 00 00 platform caam_sm: [0008] 00 00 00 00 00 00 00 00 platform caam_sm: [0016] 00 00 00 00 00 00 00 00 platform caam_sm: [0024] 00 00 00 00 00 00 00 00 platform caam_sm: [0032] 00 00 00 00 00 00 00 00 platform caam_sm: [0040] 00 00 00 00 00 00 00 00 platform caam_sm: [0048] 00 00 00 00 00 00 00 00 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 64-bit black key in blob: platform caam_sm: [0000] 9c 5f c6 a9 06 33 a5 a5 platform caam_sm: [0008] de 27 35 d8 15 e5 a1 4f platform caam_sm: [0016] f7 e1 e8 d0 74 23 fd a8 platform caam_sm: [0024] 68 81 69 46 49 13 17 3e platform caam_sm: [0032] 9c fc 15 f5 39 0a c6 3d platform caam_sm: [0040] d7 00 d0 49 9a bb 3f c3 platform caam_sm: [0048] e4 ef 05 f9 e5 38 da f8 platform caam_sm: [0056] 00 00 00 00 00 00 00 00 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 128-bit black key in blob: platform caam_sm: [0000] 84 6e 68 1d 03 6b f8 3b platform caam_sm: [0008] 09 da 7c 60 70 f4 df 65 platform caam_sm: [0016] 95 b5 48 9d 70 e4 47 ca platform caam_sm: [0024] e9 1f 5a e5 f0 43 26 a7 platform caam_sm: [0032] a9 90 65 92 42 ab fd 46 platform caam_sm: [0040] fb 3d e9 13 5c 24 f1 e9 platform caam_sm: [0048] 8b ca b4 c1 10 23 9d 66 platform caam_sm: [0056] 85 68 14 30 47 ce 43 c0 platform caam_sm: [0064] 00 00 00 00 00 00 00 00 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 192-bit black key in blob: platform caam_sm: [0000] 57 a6 97 3f 43 96 cf 87 platform caam_sm: [0008] 1f 72 89 a6 a0 ad 0e 48 platform caam_sm: [0016] 7a ad 5c e4 6e 37 04 3d platform caam_sm: [0024] e4 95 c9 09 aa c7 12 bb platform caam_sm: [0032] 56 3c d7 dc 03 6b 2f e1 platform caam_sm: [0040] 16 a8 c2 c3 78 7a 95 ce platform caam_sm: [0048] 05 75 fc d4 a6 84 be d3 platform caam_sm: [0056] c7 df 01 4f bc 17 fd 9d platform caam_sm: [0064] 98 25 68 26 f6 9b 5c 99 platform caam_sm: [0072] 00 00 00 00 00 00 00 00 platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: 256-bit black key in blob: platform caam_sm: [0000] fe a8 22 dd 34 d2 00 3e platform caam_sm: [0008] 7e e8 32 93 59 a4 96 72 platform caam_sm: [0016] 47 9a dd 3e fe 2a 83 27 platform caam_sm: [0024] 92 05 b2 c8 cc 3e fe 64 platform caam_sm: [0032] 9b 6b 2d 47 bc 58 ca 1c platform caam_sm: [0040] 8d c2 b4 94 81 b1 80 bf platform caam_sm: [0048] 0e 59 38 50 47 61 09 f4 platform caam_sm: [0056] 22 c2 fa 92 56 92 df 2e platform caam_sm: [0064] 62 84 43 56 69 3a 85 f1 platform caam_sm: [0072] c4 f4 f7 54 46 4c 0b ca platform caam_sm: [0080] 00 00 00 00 00 00 00 00 platform caam_sm: [0088] 00 00 00 00 00 00 00 00 platform caam_sm: restored 64-bit black key: platform caam_sm: [0000] c8 bd 51 12 0f 8c 3c 9b platform caam_sm: [0008] 94 ac 86 67 55 65 75 24 platform caam_sm: restored 128-bit black key: platform caam_sm: [0000] d4 b2 d2 cd de 16 e3 b1 platform caam_sm: [0008] 13 7c 1e af 4c a4 40 14 platform caam_sm: restored 192-bit black key: platform caam_sm: [0000] 3d 4f 1d c9 83 84 b5 8a platform caam_sm: [0008] 50 8e de 15 8e 02 00 8d platform caam_sm: [0016] 47 6b e3 e8 62 6f 89 8f platform caam_sm: [0024] 7c dc 6f eb cc 73 30 1c platform caam_sm: restored 256-bit black key: platform caam_sm: [0000] c4 4e d7 b6 3e 43 2f 66 platform caam_sm: [0008] 36 df f3 c9 1c b4 d5 28 platform caam_sm: [0016] 4b 48 f0 e6 04 2e 87 2c platform caam_sm: [0024] 30 f4 10 8d c6 91 bd 77 snvs-secvio 20cc000.caam-snvs: can't get snvs clock snvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure state usbcore: registered new interface driver usbhid usbhid: USB HID core driver cs42xx8 1-0048: found device, revision 4 fsl-asrc 2034000.asrc: driver registered snd-soc-dummy snd-soc-dummy: ASoC: Failed to create platform debugfs directory imx-cs42888 sound-cs42888.27: cs42888 <-> 2024000.esai mapping ok imx-cs42888 sound-cs42888.27: snd-soc-dummy-dai <-> 2034000.asrc mapping ok imx-cs42888 sound-cs42888.27: cs42888 <-> 2024000.esai mapping ok imx-spdif sound-spdif.20: snd-soc-dummy-dai <-> 2004000.spdif mapping ok imx-audio-hdmi sound-hdmi.21: hdmi-hifi <-> hdmi_audio.3 mapping ok imx-tuner-si476x sound-fm.33: failed to find FM platform device imx-tuner-si476x: probe of sound-fm.33 failed with error -22 NET: Registered protocol family 26 TCP: cubic registered NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 can: controller area network core (rev 20120528 abi 9) NET: Registered protocol family 29 can: raw protocol (rev 20120528) can: broadcast manager protocol (rev 20120528 t) can: netlink gateway (rev 20130117) max_hops=1 Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP socket layer initialized Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Bluetooth: HIDP socket layer initialized 8021q: 802.1Q VLAN Support v1.8 Key type dns_resolver registered VGEN2: disabling SWBST: disabling SW4: disabling regulator-dummy: disabling imx mcc test is registered. usb_h1_vbus: 5000 mV usb_otg_vbus: 5000 mV ci_hdrc ci_hdrc.0: EHCI Host Controller ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected ci_hdrc ci_hdrc.1: doesn't support gadget ci_hdrc ci_hdrc.1: EHCI Host Controller ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2 ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00 hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected input: gpio-keys.18 as /devices/soc0/gpio-keys.18/input/input4 snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:02 UTC (2) ALSA device list: #0: cs42888-audio #1: imx-spdif #2: imx-hdmi-soc usb 1-1: new high-speed USB device number 2 using ci_hdrc hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk2p2): using internal journal EXT3-fs (mmcblk2p2): recovery complete EXT3-fs (mmcblk2p2): mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) on device 179:2. devtmpfs: mounted Freeing unused kernel memory: 392K (809d9000 - 80a3b000) usb 1-1.2: new low-speed USB device number 3 using ci_hdrc Mount failed for selinuxfs on /sys/fs/selinux: No such file or directory random: init urandom read with 68 bits of entropy available input: DELL DELL USB Laser Mouse as /devices/soc0/soc.0/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C063.0001/input/input5 hid-generic 0003:046D:C063.0001: input: USB HID v1.10 Mouse [DELL DELL USB Laser Mouse] on usb-ci_hdrc.0-1.2/input0 usb 1-1.3: new low-speed USB device number 4 using ci_hdrc init: plymouth-upstart-bridge main process (177) terminated with status 1 init: plymouth-upstart-bridge main process ended, respawning init: plymouth-upstart-bridge main process (187) terminated with status 1 init: plymouth-upstart-bridge main process ended, respawning init: plymouth-upstart-bridge main process (190) terminated with status 1 init: plymouth-upstart-bridge main process ended, respawning input: Dell Dell QuietKey Keyboard as /devices/soc0/soc.0/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:413C:2106.0002/input/input6 hid-generic 0003:413C:2106.0002: input: USB HID v1.10 Keyboard [Dell Dell QuietKey Keyboard] on usb-ci_hdrc.0-1.3/input0 init: ureadahead main process (180) terminated with status 5 init: mounted-proc main process (204) terminated with status 1 DBG sensor data is at 7f010190 * Starting Mount filesystems on boot [ OK ] * Stopping Send an event to indicate plymouth is up [ OK ] * Starting Signal sysvinit that the rootfs is mounted [ OK ] * Starting Clean /tmp directory [ OK ] * Starting Populate and link to /run filesystem [ OK ] * Stopping Populate and link to /run filesystem [ OK ] * Stopping Clean /tmp directory [ OK ] * Stopping Track if upstart is running in a container [ OK ] * Starting Initialize or finalize resolvconf [ OK ] * Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * ERROR: v4l2 capture: slave not found! Starting Signal sysvinit that virtual filesystems are mounted [ OK ] * Starting Bridge udev events into upstart [ OK ] * Starting Signal sysvinit that local filesystems are mounted [ OK ] * Starting Signal sysvinit that remote filesystems are mounted [ OK ] * Stopping Mount filesystems on boot [ OK ] * Starting device node and kernel event manager [ OK ] * Starting flush early job output to logs [ OK ] * Starting load modules from /etc/modules [ OK ] * Starting cold plug devices [ OK ] * Starting log initial device creation [ OK ] * Stopping flush early job output to logs [ OK ] * Stopping load modules from /etc/modules [ OK ] * Starting set console font [ OK ] * Starting system logging daemon [ OK ] * Stopping set console font [ OK ] * Starting userspace bootsplash [ OK ] * Stopping userspace bootsplash [ OK ] * Starting Send an event to indicate plymouth is up [ OK ] * Stopping Send an event to indicate plymouth is up [ OK ] * Starting configure network device security [ OK ] * Starting configure network device [ OK ] * Starting configure network device security [ OK ] * Starting configure network device security [ OK ] * Starting configure network device security [ OK ] * Starting configure network device [ OK ] * Starting Mount network filesystems [ OK ] * Starting Failsafe Boot Delay [ OK ] * Stopping Mount network filesystems [ OK ] * Starting configure network device [ OK ] * Starting Bridge socket events into upstart [ OK ] * Starting Bridge file events into upstart [ OK ] * Starting Mount network filesystems [ OK ] * Starting configure network device [ OK ] * Stopping Failsafe Boot Delay [ OK ] * Starting System V initialisation compatibility [ OK ] * Stopping System V initialisation compatibility [ OK ] * Starting System V runlevel compatibility [ OK ] * Starting save kernel messages [ OK ] * Starting configure network device security [ OK ] * Starting regular background program processing daemon [ OK ] * Stopping System V runlevel compatibility [ OK ] * Stopping Mount network filesystems [ OK ] * Stopping save kernel messages [ OK ] Re: Installing Ubuntu Rootfs on NXP i.MX6 boards HI Erik, I do not have a i.mx 6 QuadPlus board to try. If you tried and share me the results. Thanks! Wenming Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Have you chance to test it for i.MX 6QuadPlus SABRE-AI Board? Can be used a newer BSP rel_imx_4.1.15_1.1.0_ga?  Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi , I build one following the guidance for my im53qsb reference board. But I got kernel panic at imx5_pm_init, I am using the imx_v7_defconfig, is anybody else has this issue or has fix for this issue or can I remove the pm configuration. U-Boot 2015.04 (Oct 04 2016 - 12:17:39) Board: MX53 LOCO I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: FEC Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device reading boot.scr ** Unable to read file boot.scr ** reading zImage 5997120 bytes read in 346 ms (16.5 MiB/s) Booting from mmc ... reading imx53-qsrb.dtb 24491 bytes read in 19 ms (1.2 MiB/s) Kernel image @ 0x72000000 [ 0x000000 - 0x5b8240 ] ## Flattened Device Tree blob at 71000000 Booting using the fdt blob at 0x71000000 Loading Device Tree to 8f552000, end 8f55afaa ... OK Starting kernel ... Booting Linux on physical CPU 0x0 Linux version 3.14.38 (lucid@ubuntu) (gcc version 4.8.5 (Linaro GCC 4.8-2015.06) ) #1 SMP PREEMPT Wed Oct 5 06:56:31 PDT 2016 CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Machine model: Freescale i.MX53 Quick Start Board cma: CMA: reserved 320 MiB at bc000000 Memory policy: Data cache writeback CPU: All CPU(s) started in SVC mode. PERCPU: Embedded 8 pages/cpu @cb33f000 s8320 r8192 d16256 u32768 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 259072 Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 rw rootwait PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 699820K/1048576K available (7423K kernel code, 456K rwdata, 2584K rodata, 384K init, 432K bss, 348756K reserved, 0K highmem) Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) lowmem : 0x80000000 - 0xe0000000 (1536 MB) pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) modules : 0x7f000000 - 0x7fe00000 ( 14 MB) .text : 0x80008000 - 0x809ce000 (10008 kB) .init : 0x809ce000 - 0x80a2e080 ( 385 kB) .data : 0x80a30000 - 0x80aa20c0 ( 457 kB) .bss : 0x80aa20cc - 0x80b0e25c ( 433 kB) SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Preemptible hierarchical RCU implementation. RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 NR_IRQS:16 nr_irqs:16 16 TrustZone Interrupt Controller (TZIC) initialized CPU identified as i.MX53, silicon rev 2.1 Switching to timer-based delay loop sched_clock: 32 bits at 33MHz, resolution 30ns, wraps every 128849019873ns clocksource_of_init: no matching clocksources found Console: colour dummy device 80x30 Calibrating delay loop (skipped), value calculated using timer frequency.. 66.66 BogoMIPS (lpj=333333) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) CPU: Testing write buffer coherency: ok CPU0: thread -1, cpu 0, socket -1, mpidr 0 Setting up static identity map for 0x70710420 - 0x70710478 Brought up 1 CPUs SMP: Total of 1 processors activated (66.66 BogoMIPS). CPU: All CPU(s) started in SVC mode. devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 pinctrl core: initialized pinctrl subsystem regulator-dummy: no parameters NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations cpuidle: using governor ladder cpuidle: using governor menu Use WDOG1 as reset source syscon 53fa8000.iomuxc-gpr: regmap [mem 0x53fa8000-0x53fa800b] registered hw-breakpoint: debug architecture 0x4 unsupported. imx53-pinctrl 53fa8000.iomuxc: initialized IMX pinctrl driver bio: create slab at 0 3P2V: 3200 mV usb_vbus: 5000 mV i2c-core: driver [max17135] using legacy suspend method i2c-core: driver [max17135] using legacy resume method SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb usbphy.1 supply vcc not found, using dummy regulator usbphy.2 supply vcc not found, using dummy regulator i2c i2c-1: IMX I2C adapter registered da9052: probe of 0-0048 failed with error -5 i2c i2c-0: IMX I2C adapter registered Linux video capture interface: v2.00 pps_core: LinuxPPS API ver. 1 registered pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]> PTP clock support registered imx-ipuv3: probe of 18000000.ipu failed with error -22 MIPI CSI2 driver module loaded Advanced Linux Sound Architecture Driver Initialized. Bluetooth: Core ver 2.18 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized Switched to clocksource mxc_timer1 cfg80211: Calling CRDA to update world regulatory domain NET: Registered protocol family 2 TCP established hash table entries: 8192 (order: 3, 32768 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP: reno registered UDP hash table entries: 512 (order: 2, 16384 bytes) UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. imx rpmsg driver is registered. Bus freq driver module loaded futex hash table entries: 256 (order: 2, 16384 bytes) VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. fuse init (API version 7.22) msgmni has been set to 2006 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) MIPI DSI driver module loaded imx-sdma 63fb0000.sdma: no iram assigned, using external mem imx-sdma 63fb0000.sdma: no event needs to be remapped imx-sdma 63fb0000.sdma: Direct firmware load failed with error -2 imx-sdma 63fb0000.sdma: Falling back to user helper imx-sdma 63fb0000.sdma: initialized Serial: IMX driver 53fbc000.serial: ttymxc0 at MMIO 0x53fbc000 (irq = 47, base_baud = 4166666) is a IMX console [ttymxc0] enabled serial: Freescale lpuart driver imx sema4 driver is registered. [drm] Initialized drm 1.1.0 20060810 [drm] Initialized vivante 1.0.0 20120216 on minor 0 brd: module loaded loop: module loaded CAN device driver interface 63fec000.ethernet supply phy not found, using dummy regulator libphy: fec_enet_mii_bus: probed ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-mxc: Freescale On-Chip EHCI Host driver usbcore: registered new interface driver usb-storage usbcore: registered new interface driver usb_ehset_test 53f80800.usbmisc supply vbus-wakeup not found, using dummy regulator ci_hdrc ci_hdrc.1: doesn't support gadget ci_hdrc ci_hdrc.1: EHCI Host Controller ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1 ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00 hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected mousedev: PS/2 mouse device common for all mice input: mma8450 as /devices/virtual/input/input0 i2c-core: driver [isl29023] using legacy suspend method i2c-core: driver [isl29023] using legacy resume method i2c /dev entries driver IR NEC protocol handler initialized IR RC5(x) protocol handler initialized IR RC6 protocol handler initialized IR JVC protocol handler initialized IR Sony protocol handler initialized IR RC5 (streamzap) protocol handler initialized IR SANYO protocol handler initialized IR MCE Keyboard/mouse protocol handler initialized coda 63ff4000.vpu: Direct firmware load failed with error -2 coda 63ff4000.vpu: Falling back to user helper i2c-core: driver [mag3110] using legacy suspend method i2c-core: driver [mag3110] using legacy resume method imx2-wdt 53f98000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0) Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized Bluetooth: HCI BCSP protocol initialized Bluetooth: HCIATH3K protocol initialized usbcore: registered new interface driver bcm203x usbcore: registered new interface driver btusb usbcore: registered new interface driver ath3k sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci-pltfm: SDHCI platform and OF driver helper mmc0: no vqmmc regulator found mmc0: no vmmc regulator found mmc0: SDHCI controller on 50004000.esdhc [50004000.esdhc] using ADMA mmc1: no vqmmc regulator found mmc1: no vmmc regulator found mmc0: host does not support reading read-only switch. assuming write-enable. mmc1: SDHCI controller on 50020000.esdhc [50020000.esdhc] using ADMA mmc0: new high speed SDHC card at address 0007 Job Ring Device allocation for transform failed mmcblk0: mmc0:0007 SD16G 14.5 GiB usbcore: registered new interface driver usbhid usbhid: USB HID core driver mmcblk0: p1 p2 sgtl5000 1-000a: sgtl5000 revision 0x11 imx-sgtl5000 sound.8: phandle missing or invalid imx-sgtl5000: probe of sound.8 failed with error -22 NET: Registered protocol family 26 TCP: cubic registered NET: Registered protocol family 10 sit: IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 can: controller area network core (rev 20120528 abi 9) NET: Registered protocol family 29 can: raw protocol (rev 20120528) can: broadcast manager protocol (rev 20120528 t) can: netlink gateway (rev 20130117) max_hops=1 Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: BNEP socket layer initialized Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Bluetooth: HIDP socket layer initialized 8021q: 802.1Q VLAN Support v1.8 Key type dns_resolver registered Unable to handle kernel paging request at virtual address f51a000c pgd = 80004000 [f51a000c] *pgd=00000000 Internal error: Oops: 5 [#1] PREEMPT SMP ARM Modules linked in: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.38 #1 task: c8068000 ti: c806c000 task.ti: c806c000 PC is at mx5_cpu_lp_set+0x10/0xfc LR is at imx5_pm_init+0x64/0x80 pc : [<8001d804>] lr : [<809da58c>] psr: 60000113 sp : c806dedc ip : 00000072 fp : 00000000 r10: c806c038 r9 : 80a1ee7c r8 : 809d1190 r7 : 80aa2100 r6 : 80aa2100 r5 : 00000007 r4 : c801b600 r3 : f51a0000 r2 : 8001d8f0 r1 : 00000002 r0 : 00000002 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 10c5387d Table: 70004019 DAC: 00000015 Process swapper/0 (pid: 1, stack limit = 0xc806c238) Stack: (0xc806dedc to 0xc806e000) dec0: c801b600 dee0: 00000007 809da58c 80a2b80c 809d11b0 00000000 800088bc c800ccc0 808c7d28 df00: c8096200 80714144 00000000 00000000 00000000 8012a57c 00000000 80a446b0 df20: 60000113 00000001 cbfffc2e 8073b938 0000010b 800498e0 80996644 00000007 df40: cbfffc36 00000007 80a446a0 80a2b80c 00000007 80aa2100 80aa2100 809ce50c df60: 80a1ee7c 0000010b 80a1ee74 809cec38 00000007 00000007 809ce50c 8070fbd8 df80: 00000000 00002100 80706164 00000000 00000000 00000000 00000000 00000000 dfa0: 00000000 80706170 00000000 8000e278 00000000 00000000 00000000 00000000 dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 dfe0: 00000000 00000000 00000000 00000000 00000013 00000000 80000220 08040010 [<8001d804>] (mx5_cpu_lp_set) from [<809da58c>] (imx5_pm_init+0x64/0x80) [<809da58c>] (imx5_pm_init) from [<809d11b0>] (init_machine_late+0x20/0x28) [<809d11b0>] (init_machine_late) from [<800088bc>] (do_one_initcall+0xf8/0x144) [<800088bc>] (do_one_initcall) from [<809cec38>] (kernel_init_freeable+0x13c/0x1dc) [<809cec38>] (kernel_init_freeable) from [<80706170>] (kernel_init+0xc/0xe8) [<80706170>] (kernel_init) from [<8000e278>] (ret_from_fork+0x14/0x3c) Code: e3a03000 e92d4030 e1a01000 e34f351a (e593c00c) ---[ end trace 65acb852349b9d5b ]--- Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b T Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, Please use the flashing procedure from our Ubuntu release blog post. Regards, Gary Re: Installing Ubuntu Rootfs on NXP i.MX6 boards My uboot print (couldn't find the document attachment option) baudrate=115200 board=sabrelite bootargs=console=ttymxc0,115200 root=/dev/mmcblk2p1 rootwait rw video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 bootargs_base=setenv bootargs console=ttymxc0,115200 bootargs_mmc=setenv bootargs ${bootargs} root=/dev/mmcblk2p1 rootwait rw bootcmd=run bootcmd_mmc bootcmd_mmc=run bootargs_base bootargs_mmc;mmc dev 1;mmc read ${loadaddr} 0x800 0x4000;mmc read ${fdt_addr} 0x5000 0x800;bootm ${loadaddr} - ${fdt_addr} bootdelay=3 bootdevs=sata mmc usb clearenv=if sf probe || sf probe || sf probe 1 ; then sf erase 0xc0000 0x2000 && echo restored environment to factory default ; fi cmd_hdmi=fdt set fb_hdmi status okay;fdt set fb_hdmi mode_str 1280x720M@60; cmd_lcd=fdt set fb_lcd status disabled cmd_lvds=fdt set fb_lvds status disabled console=ttymxc1 cpu=6Q dfu_alt_info=u-boot raw 0x0 0xc0000 ethact=FEC ethaddr=00:19:b8:02:79:6c ethprime=FEC fdt_addr=0x18000000 fdt_high=0xffffffff filesize=70c00 initrd_high=0xffffffff kernel=uImage loadaddr=0x80800000 loadsplash=if sf probe ; then sf read ${splashimage} c2000 ${splashsize} ; fi reset_cause=1 rundfu=dfu 0 sf 0:0:25000000:0 stdout=serial,vga uboot_defconfig=nitrogen6q umsdevs=sata mmc upgradeu=for dtype in ${bootdevs}; do for disk in 0 1 ; do ${dtype} dev ${disk};load ${dtype} ${disk}:1 10008000 /6x_upgrade && source 10008000 ; done ; done usbnet_devaddr=00:19:b8:00:00:02 usbnet_hostaddr=00:19:b8:00:00:01 usbrecover=setenv ethact usb_ether; setenv ipaddr 10.0.0.2; setenv netmask 255.255.255.0; setenv serverip 10.0.0.1; setenv bootargs console=ttymxc1,115200; tftp boot 10800000 10.0.0.1:uImage-${board}-recovery&& tftpboot 12800000 10.0.0.1:uramdisk-${board}-recovery.img && bootm 10800000 12800000 Environment size: 1701/8188 bytes => boot switch to partitions #0, OK mmc1 is current device MMC read: dev # 1, block # 2048, count 16384 ... 16384 blocks read: OK MMC read: dev # 1, block # 20480, count 2048 ... 2048 blocks read: OK Wrong Image Format for bootm command ERROR: can't get kernel image! Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Gary, thanks for your reply. Now the situation is like this : I want to interface an analog TV encoder (adv7343) to the RGB port of the imx6 (in BDSL). According to what I have researched, I need adding few modifications to the mxc_lcd.if of the linux kernel (3.14.52_1.1.0_ga) to use lcd driver in V_SYNC | H_SYNC mode to support this encoder. So I have no option (or do I?) rather than building a new kernel (as these drivers are builtin modules), and that's why I thought of building a bootable SD card myself.  I think the steps I followed in preparing SD should be okay, but to note what I've done in brief : ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ export DISK=/dev/sdg sudo dd if=/dev/zero of=${DISK} bs=1M count=10 cd binary/ sudo dd if=u-boot.imx of=${DISK} bs=512 seek=2 sync //------------create partition table sudo fdisk ${DISK} d       //delete all partitions currently on sd n       // create new partition p       // Primary partition 1       // partition number 1 2048 //default +1G    // n       // created 2d parition p 2 default default w sudo mkfs.vfat ${DISK}1 sudo mkfs.ext3 ${DISK}2 Mount ext3 SD partition to /media/rootfs: sudo mount ${DISK1} /media/kernel_target sudo mount ${DISK}2 /media/rootfs_target sudo cp –v binary/ i$target-$board.dtb /media/kernel_target    //dtb file sudo cp –v binary/uImage /media/kernel_target                        //uImage  sudo mv /media/rootfs/* /media/rootfs_target                             //root file sys ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- As you said the NAND flashed uboot already has required environment variables, and the uboot 'print' is attached to this comment. Now after the uboot prompt, I get the following message in console terminal : switch to partitions #0, OK mmc1 is current device MMC read: dev # 1, block # 2048, count 16384 ... 16384 blocks read: OK MMC read: dev # 1, block # 20480, count 2048 ... 2048 blocks read: OK Wrong Image Format for bootm command ERROR: can't get kernel image! So from this point, how should I proceed ? do these environment variables cause the issue or is SD card preparation wrong?  Thanks in advance ! Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Anuradha, Actually for SabreLite you don't need to follow the above instructions, we already provide an Ubuntu image ready to go: https://boundarydevices.com/ubuntu-xenial-mx67-boards-august-2016-kernel-4-1-15/  Or if you'd rather use Debian: https://boundarydevices.com/debian-8-3-jessie-for-i-mx6-boards-february-2016-kernel-3-14-28/  Note that in our case all the NXP components like the graphics library, VPU support, Chrome hw acceleration are packaged. That means that when a new graphics library version is out, you just need to do "apt update && apt upgrade" and you are up-to-date. Hope this helps. Regards, Gary Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi Anuradha, please refer to https://community.nxp.com/message/836641?commentID=836641&et=watches.email.thread#comment-836641  this doc, about old uboot with new kernel. Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi, thanks for this excellent doc, and I have a question on rootfs system. I am using imx6 sabrelite board and have exactly followed the guidelines in this doc. I cross compiled all the files on an Ubuntu platform, and after the unmount and inserted the SD card to my board. The kernel boot process requests 6x_bootscript file and it seems like the older uBoot is operating fron Nand Flash. How should I solve this issue by setting my own uBoot to prompt and load rootfs and zImage ? Thanks Re: Installing Ubuntu Rootfs on NXP i.MX6 boards Hi all, I find the gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz compiler not working on ubuntu14.04, I tried with gcc-linaro-4.8-2015.06-x86_64_arm-linux-xxxx works. Regards! Wenming Re: Installing Ubuntu Rootfs on NXP i.MX6 boards HI, Does somebody encounter /bin/sh 1: arm-linux-gnueabihf-gcc not found issue? this is a symlink to arm-linux-gnueabihf-gcc-4.9.4. any fix to it is highly appreciated. Thanks aheard. wenming Re: Installing Ubuntu Rootfs on NXP i.MX6 boards How to connect it to HDMI Display? Is there any additional changes or If I connect to HDMI it will show desktop??
記事全体を表示
Support Needed for Enabling OV5647 Camera on i.MX93 FRDM Hi, I am currently working on enabling the OV5647 camera module on the i.MX93 FRDM board. I have added the OV5647 node in the device tree and configured the appropriate clock source. The camera sensor is detected, and I am able to provide a 25 MHz clock on CCMSRCGPCMIX CLKO3. However, the /dev/video0 and media0 nodes are not appearing on the target board. Could you please assist me in identifying the possible cause of this issue or suggest steps to resolve it? DTS file and some required information snapshot attached in below Thank you for your support. Best regards, Bharath GC Re: Support Needed for Enabling OV5647 Camera on i.MX93 FRDM you can refer to the ov5640 dts file https://github.com/nxp-imx-support/meta-imx-frdm/blob/lf-6.6.36-2.1.0/meta-imx-bsp/recipes-kernel/linux/linux-imx/0009-arm64-dts-add-imx93-11x11-frdm-ov5640-dts.patch pls check if your camera need  PW pin or not Re: Support Needed for Enabling OV5647 Camera on i.MX93 FRDM Hello @joanxie , Thanks for your immediate response, As requested, I am sharing the OV5647 driver currently used in our build. The driver is taken from the kernel source in our Yocto build environment. Please find the attached driver ov5647.c file in the attachment  This is the driver being used for the camera integration on our system based on the i.MX93. driver is enabled for CONFIG_VIDEO_OV5647=y the kernel Version 6.6.36-lts-next-gb1d63f58897b-dirty Regards Bharath GC Re: Support Needed for Enabling OV5647 Camera on i.MX93 FRDM pls send the ov5647 driver you use, let me double check it Re: Support Needed for Enabling OV5647 Camera on i.MX93 FRDM Hello @joanxie , I also tried making some changes by referring to the OV5640 DTS file, but there is still no change on the target side. The same error is appearing. I have attached the updated DTS file, which I modified based on the OV5640 camera module DTS configuration. The power-domain pin is enabled by default, and I confirmed this by forcing it to active-low using a gpio-hog. If I add the below structure, the camera does not come up, which indicates that the power-domain is functioning. pcal6524:gpio@22 { ......        camera_pwdn {             gpio-hog;            gpios = <22 GPIO_ACTIVE_LOW>;            output-high;           line-name = "camera_pwdn";      }; }; Please find the modified DTS file attached for your reference. Kindly help in resolving this issue. Thank you.
記事全体を表示
MIMXRT700-EVK block diagram wrong part number reference I’m working with the RT700 evaluation board (MIMXRT700-EVK), and I’ve come across a discrepancy in the documentation. The block diagram mentions a Macronix flash memory part number as MX25UM51345GXDI00 , but this does not match the BOM file where it mentions MX25UW51345GXDI00. Additionally, the part number on the physical board itself differs from the block diagram     . This is causing confusion, especially when trying to reference documentation or locate the correct data sheet. Could you clarify the exact flash part number currently used on the RT700-EVK? Also, if possible, could NXP provide the data sheet for this specific flash IC? That would be extremely helpful for our development. Re: MIMXRT700-EVK block diagram wrong part number reference I only wanted to report this issue so that in the next errata or next revision of the RT700 EVK board manual NXP can take this into consideration. for the datasheet I'll contact macronix.   Re: MIMXRT700-EVK block diagram wrong part number reference Hi @prathamvora, Please follow the BOM for the memory part number. For the datasheet, please contact Macronix. Best Regards, Pablo Re: MIMXRT700-EVK block diagram wrong part number reference Hi, Thank you for bringing this to our attention. For future reference, you can also use the following link to submit technical documentation feedback. Technical Documentation Feedback | NXP Semiconductors Best Regards, Pablo
記事全体を表示
Physical connections for INT2 on MPL3115A2 and nRST on MPL115A2 Hi, I'd like to use interchangeably either a MPL115A2 or a MPL3115A2 in my circuit and I'm wondering if I can get away with not using a DNF/resistor on pin 5 and just connecting it to VDD. This is the RST line (active low) on the 115A2 but is INT2 on the 3115A2. What would the effect be if the INT2 line was internally pulling low and the pin is connected to VDD? Is the internal resistance enough that it wouldn't overheat/blow up? Would it be power hungry? Is this a CMOS type output? etc. etc. I'd be running them both from 3.3V on VDD/VDDIO. Any information appreciated - The only information I can find in the datasheets on this is VOH/VOL for INT1 and INT2 with a test condition I_o of 500uA. Pressure Sensors Re: Physical connections for INT2 on MPL3115A2 and nRST on MPL115A2 Thanks Tomas, your reply is very helpful. Re: Physical connections for INT2 on MPL3115A2 and nRST on MPL115A2 Timothy, By default all interrupts are disabled (CTRL_REG4 = 0x00), so the INT2 pin will be high all the time. If you want to use any of the internal interrupts (Data Ready, FIFO etc.), just set a corresponding bit in the CTRL_REG4 register and then route the interrupt to the INT1 pin by setting a corresponding bit in the CTRL_REG5 register. In both cases the INT2 pin can be connected directly to VDD without any problems. I hope it helps. Regards, Tomas
記事全体を表示
S32DS FOR ARM cannot be downloaded. S32DS software download is rejected, want to know the specific reasons and ways to deal with, I am a personal user without a company, the development board is the network to buy learning to use. The web page prompts the following: Our records indicate that you have previously requested an Evaluation version for this product. If you would like to purchase the full product please visit us at NXP or contact your sales representative . Note If you would like to extend your evaluation period please open a If you would like to extend your evaluation period please open a Service Request . Disabled creation of service requests Since we are unable to associate your email address with a company, you are not eligible to create a new service request on the Service Request Portal page. Please use your company email address to log in to the NXP website and submit a service request or submit your question via the NXP Technical Forum.   Re: S32DS FOR ARM 无法下载 Hi,  which version of S32DS do you like to download? 
記事全体を表示
PCA9698 のステータスをご存知ですか? こういうものが必要かもしれないと思いました。ステータスはどうですか?もっと新しい類似製品はありますか? ランディ Re: Do you know the status of PCA9698 ? こんにちは、ランディ。 PCA9698 は現在も生産中ですが、HVQFN56 バージョン (PCA9698BS) は製造が中止されます。TSSOP56 バージョン (PCA9698DGG) は引き続き完全にアクティブでサポートされており、新しいデザインに推奨される選択肢です。同じ 40 ビット GPIO 数と電流能力を単一チップで提供する新しい NXP デバイスは存在しないため、その機能が必要な場合、PCA9698DGG は依然として最適なソリューションです。 BRs、トーマス
記事全体を表示
RT1021 输入最大电流 您好,请问 GPIO 输入可以承受多大的电流?我使用的是 GPIO_AD_B1_02,通过该引脚的电流为 8mA。 在损坏引脚之前,输入端可承受的最大电流是多少? 如果我没理解错的话,该引脚是默认值,默认配置为带 100k 下拉电阻的输入引脚。 谢谢 Re: RT1021 input max current 你好,@jtrujillo、 一般来说,任何 RT1xxx GPIO 引脚的最大电流都应限制在 25mA,无论它是输出电流还是下沉电流。这是防止可靠性问题(如电迁移造成的潜在损坏)的技术安全极限,如果引脚需要,可以持续很长时间。 BR, Edwin.
記事全体を表示
MCX W71 Knowledge Hub MCX W71 无线微控制器采用 96 MHz Arm® Cortex®-M33 内核,搭配支持 Matter™、Thread®、Zigbee® 和 Bluetooth® 低功耗的多协议无线电子系统。独立的无线电子系统拥有专用内核和内存,可减轻主 CPU 的负担,使其专注于主要应用,并支持固件更新以适配未来的无线标准。MCX W71x 还通过集成的 EdgeLock® 安全飞地核心配置文件提供高级安全性,并将由 NXP 的 EdgeLock 2GO 云服务支持凭证共享。 MCX W71x 系列可作为单芯片解决方案支持工业和物联网设备,也可在托管架构中用作协处理器。   MCX W71 Block DiagramMCX W71 框图 文件 MCX W71 参考手册 MCX W71 数据表 Errata Secure Reference 手册** 认证 评估板 FRDM-MCXW71页面 FRDM-MCXW71 原理图 FRDM-MCXW71设计文件 FRDM-MCXW71 用户手册 FRDM-MCXW71 入门指南 应用笔记 AN14398:如何在 FRDM-MCXW71 上使用 RTC 本应用笔记介绍了如何在 BLE 演示中配置和使用 RTC 外设。 AN14416:在 FRDM-MCXW71 蓝牙低功耗连接协议栈上启用看门狗定时器模块 本应用笔记介绍了在连接协议栈演示中实现 WDOG 定时器的过程。 AN14396:MCX W71 将 OTAP 客户端服务集成到蓝牙低功耗外设设备中 本应用笔记提供了将空中编程客户端服务集成到 BLE 外设设备中的步骤和流程。 AN14391:MCX W71 负载牵引报告 本应用笔记介绍了负载牵引特性的测量方法和相关结果。 AN14394:使用 OTAP 工具为 MCX W71 创建固件更新镜像 本应用笔记提供了通过 OTAP 在 MCX W71 板上创建和升级镜像的步骤。  AN14389:MCXW71 蓝牙低功耗功耗分析 本应用笔记提供了有关 MCXW71 无线微控制器的功耗、硬件设计以及低功耗运行优化的信息。  AN14387:MCXW71 电源管理硬件 本应用笔记介绍了 MCXW71 微控制器中专门用于电源管理的不同模块的使用方法。 AN14399:MCXW71 针对 802.15.4 应用的连接测试本应用笔记介绍了如何使用连接测试工具执行 MCXW71 802.15.4 射频性能测试。 AN14374:用于蓝牙低功耗和 IEEE 802.15.4 应用的 FRDM-MCXW71 射频系统评估报告 本应用笔记提供了 FRDM-MCXW71 板在 BLE(2FSK 调制)和 IEEE 802.15.4(OQPSK 调制)应用中的射频评估测试结果,还介绍了可用于执行测试的设置和工具。  AN14427:MCXW71 在线编程工具 本应用笔记提供了将 MCXW71 微控制器引导至 ISP 模式并建立各种串行连接以与微控制器通信的步骤。 AN14397:量产期间通过串行线调试为应用程序和无线电固件编程 MCXW71 闪存本应用笔记介绍了在量产中通过 SWD 编写、烧录和编程所有必要设置的步骤。 Zigbee 协议 Zigbee 3.0 入门:本应用笔记为开发你自己的 Zigbee 3.0 设备固件提供了最佳起点指导。 Zigbee 3.0 基础设备模板:本应用笔记提供了示例应用程序,以演示采用恩智浦 DK006 Zigbee 3.0 微控制器的 Zigbee 3.0 网络中基础设备的特性和操作。 Zigbee 3.0 设备开发:本应用笔记介绍了如何以基础设备模板终端设备应用程序为起点开发 Zigbee 3.0 开关传感器。本应用笔记中描述的开关传感器基于 Zigbee 照明和占用(ZLO)设备规范中的 Zigbee 设备类型。 Zigbee 3.0 灯泡:本应用笔记为采用 NXP DK006 无线微控制器的 Zigbee 3.0 网络中的灯泡提供了示例应用程序。 Zigbee 3.0 物联网控制桥:本指南提供了允许用户使用图形用户界面(GUI)连接到控制桥的信息,该界面模拟主机来操作 Zigbee 网络。它还描述了用于与控制桥接口的串行协议,以及所有相关命令和响应的有效负载。 Zigbee 3.0 绿色功率设备:本应用笔记为开发你自己的 Zigbee 3.0 设备固件提供了最佳起点指导。 Zigbee 3.0 传感器:本应用笔记为采用恩智浦 DK006 Zigbee 3.0 无线微控制器的 Zigbee 3.0 网络中的传感器提供了示例应用程序。 Zigbee 3.0 控制器和开关:本应用笔记为采用恩智浦 DK006 无线微控制器的 Zigbee 3.0 网络中的控制器和开关提供了示例应用程序。本应用笔记还包括 Zigbee 3.0 网络中典型的 Zigbee 绿色功率 (GP) 能量收集开关的示例。 Zigbee 3.0 集群开发:本应用笔记介绍了如何以基础设备模板路由器设备应用程序为起点开发 Zigbee 3.0 窗帘设备。本应用笔记有两种使用方式: 作为使用最终步骤中创建的功能示例创建窗帘设备的起点。 作为创建 NXP ZCL 实现中未包含的设备和集群(包括制造商特定设备和集群)的指南。 支持 如果你有关于 MCX W71 的问题,请在我们的无线微控制器社区中提出你的问题!此处 有用链接 使用 KW45/KW47/MCXW71/MCXW72 的信号频率分析仪 (SFA) 模块进行时钟测量 - NXP 社区:该社区提供了如何使用信号频率分析仪的步骤 首次正确构建 KW45(汽车)或 K32W1/MCXW71(物联网 / 工业)PCB 的最佳方法 - NXP 社区:在该社区中提供了使用 KW45 或 K32W148 和 MCXW71 构建 PCB 的重要链接,以及所有与无线电性能、低功耗和无线电认证 (CE/FCC/ICC) 相关的内容。 如何在 Kinetis 系列产品上使用 HCI_bb 并进入 DTM 模式:本文分为两部分: 如何将HCI_bb二进制文件烧录到Kinetis产品中。 使用 R&S CMW270 进行射频测量 BLE HCI 应用程序设置发射机/接收机测试命令:本文提供了相关步骤,展示用户如何向设备发送串行命令。 Bluetooth LE HCI 黑盒快速入门指南:本文介绍了一个简单流程,能让用户通过串行命令控制无线电。 培训 MCX W71培训,安全MCU用于Matter、Zigbee、BLE MCX W系列培训 - NXP社区 设备 无线设备:本文提供了有助于项目开发的设备链接。 开发工具 NXP MCUXpresso:MCUXpresso IDE 提供高级编辑、编译和调试功能,此外还有针对微控制器的特定调试功能。支持与所有通用 Arm Cortex-M 的连接。 VSCode: MCUXpresso for Visual Studio Code (VS Code) 为嵌入式开发人员优化了代码编辑和开发体验。 Zephyr RTOs  NXP Application Code Hub:应用代码中心 (ACH) 存储库使工程师能够轻松找到由我们内部专家开发的微控制器软件示例、代码片段、应用软件包和演示。该平台提供了一种快速、简便且一致的方式来查找微控制器应用。 NXP SPSDK:是一个统一、可靠且易于使用的Python SDK库,适用于 NXP MCU 产品组合,为客户快速制作原型到生产部署提供坚实的基础。 NXP SEC工具: MCUXpresso安全配置工具是一款基于 GUI 的应用程序,用于简化在 NCP MCU 设备上生成和配置可启动的可执行文件。 NXP OTAP Tool: 是一款帮助用户对 NXP 开发板执行空中固件更新的应用程序。 ** 获取安全文件需要申请额外访问权限。 FRDM 培训 动手实践培训 协议:802.15.4 协议:BLE -> 连接性 协议:蓝牙 协议:Matter 协议:Thread 协议:Zigbee
記事全体を表示
使用 8x DPDMUX 加载静态 DPL 失败 嗨,社区、 成功使用动态创建 DPDMUX 和 DPNI,并通过以下命令生成 DPL: 8x ls-addni --fs-entries=8 --num-queues=8 -n source /usr/local/dpdk/dpaa2/dynamic_dpl.sh ... 8x restool dpdmux create 8x restool dprc connect dprc.1 --endpoint1= .n.0/1/2 --endpoint2= / /dpni.k> restool dprc generate-dpl dprc.1> dpl-8-dpdmux.dts 使用 dpl-8-dpdmux.dtb(由 dtc 工具生成)更新静态 DPL,以便 uboot 启动 MC 布局。 错误显示为 "吹": [E, mem_mng_get_phys_mem:655] 主内存。管理器内存分配失败 [E, mem_mng_get_phys_mem:658] Required size 0x000040000 alignment 0x000000100 exceeds available memory for partition ID 7 [E, init_bman_bp:399, DPDMUX] ID[6] - dpbp_allocate_buffers(),分配 dpbp 缓冲区失败 [E, init_infrastructure:3750, DPDMUX] swlib_init_bman_bp :-12 [E, dpdmux_init:4487, DPDMUX] init_infrastructure : -12 [E, mem_mng_get_phys_mem:655] MAJOR mem.管理器内存分配失败 [E, mem_mng_get_phys_mem:658] Required size 0x000040000 alignment 0x000000100 exceeds available memory for partition ID 7 [E, init_bman_bp:399, DPDMUX] ID[7] - dpbp_allocate_buffers(), 分配 dpbp 缓冲区失败 [E, init_infrastructure:3750, DPDMUX] swlib_init_bman_bp :-12 [E, dpdmux_init:4487, DPDMUX] init_infrastructure : -12 [E, resman_is_link_permitted:6375, RESMAN] Object wasn't found [E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@6 and dpmac@9 [E, subnode_process:155] Probing module 'connection' return error code -1.继续 dpl 处理... [E, resman_is_link_permitted:6375, RESMAN] 对象未找到 [E, linkman_probe_cb:205] 没有共同祖先 - 连接 dpdmux@6 和 dpni@15 失败 [E, subnode_process:155] 探测模块 'connection' 返回错误代码 -1.继续 dpl 处理... [E, resman_is_link_permitted:6375, RESMAN] Object wasn't found [E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@6 and dpni@7 [E, subnode_process:155] Probing module 'connection' return error code -1.继续 dpl 处理... [E, resman_is_link_permitted:6375, RESMAN] 对象未找到 [E, linkman_probe_cb:205] 没有共同祖先 - 连接 dpdmux@7 和 dpmac@10 失败 [E, subnode_process:155] 探测模块 'connection' 返回错误代码 -1.继续 dpl 处理... [E, resman_is_link_permitted:6375, RESMAN] 对象未找到 [E, linkman_probe_cb:205] 没有共同祖先 - 连接 dpdmux@7 和 dpni@16 失败 [E, subnode_process:155] 探测模块 'connection' 返回错误代码 -1.继续 dpl 处理... [E, resman_is_link_permitted:6375, RESMAN] 对象未找到 [E, linkman_probe_cb:205] 没有共同祖先 - 连接 dpdmux@7 和 dpni@8 失败 [E, subnode_process:155] 探测模块 'connection' 返回错误代码 -1.继续 dpl 处理... [E, dpl_process:527] 解析 "连接 "时出错。跳过处理 DPL 的其余部分。 [E, main:198] DPL 处理失败;继续... 静态 DPL 在支持与动态方式相同的布局方面是否有任何限制? QorIQ LS2 设备 Re: Failed to load static DPL with 8x DPDMUX 你好 yipingwang, 在动态创建布局时使用"--max-dmat-entries "不会改变 "restool dprc generate-dpl dprc.1 "的最终 dts。 因此,我尝试在 .dts 中添加以下元素 "mem-size "和"max-dmat-entries" 。手动 dpdmux@0 { 兼容 ="FSL,DPDMUX" ; options ="DPDMUX_OPT_CLS_MASK_SUPPORT","DPDMUX_OPT_AUTO_MAX_FRAME_LEN" ; method ="DPDMUX_METHOD_CUSTOM" ; manip ="DPDMUX_MANIP_NONE" ; num_ifs =<0x2> ; mem-size =<0x100>; // 这是我手动添加的 max-dmat-entries =<0x8>; // 这是我手动添加的 }; 遗憾的是,这并没有解决问题,MC 调试器中显示的错误信息还是一样。 还请检查随附的我的 dpl。 Re: Failed to load static DPL with 8x DPDMUX 请尝试以下方法是否可行。 创建 DPDMUX 时,请指定"--max-dmat-entries=8" 以减少资源分配。 -max-dmat-entries= DPDMUX 地址表的最大条目数。默认为 64。 如果问题仍然存在,请共享创建 DPDMUX 和生成 DPL 文件的整个控制台日志。 此外,您使用的是哪种处理器? Re: Failed to load static DPL with 8x DPDMUX 您好, 通过更正 DPL 参数名称,我设法解决了这个问题。
記事全体を表示
[ABUSE] Post By: @JohnKlug / Board: imx-processors / Reported by: ytuosk ytuosk has reported the post Could not invoke dnf for external kernel module in Yocto kirkstone posted by @JohnKlug for the following reasons: Reason: Harassment Details: http://polden.info/story/pharmacy-online-14"> https://www.jobwebby.ilovemarkso.com/33/pharmacy-online"> https://ruckup.org/caregivers-forum/topic/6379"> https://backend.dawahnigeria.com/audit/304767"> https://carros-usados.us/pharmacy-online-14"> https://mail.globalrealtor.co.in/node/4216"> https://direct.needshub.com/node/28221"> https://mail.globalrealtor.co.in/node/4216"> https://ufa-help.ru/content/pharmacy-online-10"> http://www.go4go.net/go/node/155292"> http://polden.info/story/pharmacy-online-14"> https://darkmetalmush.net/history/pharmacy-online-17"> https://obzorpoker.info/forum/pharmacy-online-10"> https://www.intimuscare.com/pharmacy-online-3"> http://www.alsongs.com.hk/node/15608"> https://mail.globalrealtor.co.in/node/4216"> https://darkmetalmush.net/history/pharmacy-online-17"> http://www.sccu.chula.ac.th/node/928"> https://slp.millingtonpubliclibrary.org/content/pharmacy-online-12"> http://kalyterizoi.gr/initiative/pharmacy-online-0"> http://ysrp.bnl.bm/review/pharmacy-online-13"> https://masters.adminskiracing.com/node/413289"> https://www.heilpraktikerausbildung24.de/node/124365"> https://obzorpoker.info/forum/pharmacy-online-10"> https://masters.adminskiracing.com/node/413289"> https://gglabs.us/node/5700"> https://neweddingday.com/your-couple-name-2367"> https://golemobuchino.com/content/2469/pharmacy-online"> https://lotteryobzor.com/forum/pharmacy-online-12"> http://old.jeunescathos.org/fr/content/pharmacy-online-59"> https://mnbride.com/your-couple-name-2372"> https://rahuldolas.com/forum/dummy-basic-course/topic/719/pharmacy-online"> https://wibride.com/your-couple-name-2375"> https://californiaweddingday.com/your-couple-name-2331"> http://onlyforsalebyowner.com/for-sale-by-owner-homes/dc/68"> http://polden.info/story/pharmacy-online-14"> https://www.intimus.pt/pharmacy-online-15"> https://openreviewhub.org/review/review-8412"> https://primfootball.com/pharmacy-online-10"> https://ruckup.org/caregivers-forum/topic/6379"> Post link: https://community.nxp.com/t5/i-MX-Processors/Could-not-invoke-dnf-for-external-kernel-module-in-Yocto/m-p/1627964#M203740 Post author: @JohnKlug | Email Author Reported by: ytuosk | Email Reporter The reported post has 2 replies.
記事全体を表示
Latest version of AN4581 Hi, There is a AN4581 (i.MX Secure Boot on HABv4 Supported Devices) Rev. 4 from 2020: https://de.scribd.com/document/811030804/AN4581 However If I search your website or the internet, I can only find outdated versions from 2012 or 2018. Can you tell me where I can find the latest revision of AN4581? Thanks Re: Latest version of AN4581 Thank you for your support. I was able to download the 2020 version here: https://www.readkong.com/page/an4581-i-mx-secure-boot-on-habv4-supported-devices-2622907 The old versions are available without NDA here: https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/imx-processors/225997/1/AN4581.pdf (2012) https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/imx-processors/194321/1/AN4581_2018.pdf (2018) Re: Latest version of AN4581 This AN for secure boot is confidential, you need to sign an NDA with NXP. It's better to create an internal ticket from https://support.nxp.com/s/?language=en_US
記事全体を表示
SMI-N2000 固态射频电源相对于真空管的优势 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自 20 世纪 20 年代初以来,微波能量的来源传统上一直是真空管和磁控管。尽管固态射频发电技术已经取得了许多进步,但当今的一些高功率射频应用仍然依赖真空管技术。本课程将介绍固态的技术优势,包括动态范围控制、光谱纯度、制造规模经济和产品寿命。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自 20 世纪 20 年代初以来,微波能量的来源传统上一直是真空管和磁控管。尽管固态射频发电技术已经取得了许多进步,但当今的一些高功率射频应用仍然依赖真空管技术。本课程将介绍固态的技术优势,包括动态范围控制、光谱纯度、制造规模经济和产品寿命。 智能机械和工业自动化 回复:SMI-N2000 固态射频电源相对于真空管的优势 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我看到了射频介电加热的应用。并想制作一个像RFEM24-250一样的用于加热的仪器。ISM频段为40MHz,晶体管采用MRFE6VP6300H或MRFE6VP5150N。 我想找到参考设计
記事全体を表示
FTF-ACC-F1259 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 同時マルチスレッド (SMT) は、独立した実行スレッドがスーパースカラー CPU パイプライン編成をより効果的に利用できるようにする高度なプロセッサ マイクロアーキテクチャ機能です。2ウェイ・スーパースカラー・パイプラインでのSMT実装は、動的消費電力の増加が比較的少ないデュアル・スレッドの同時実行性を最大化します。このセッションでは、次世代のPower Architecture e200z9プロセッサ・コアに含まれるSMT機能と、このマイクロアーキテクチャによって達成可能なパフォーマンス/パワー・メトリックの向上に焦点を当てます。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 同時マルチスレッド (SMT) は、独立した実行スレッドがスーパースカラー CPU パイプライン編成をより効果的に利用できるようにする高度なプロセッサ マイクロアーキテクチャ機能です。2ウェイ・スーパースカラー・パイプラインでのSMT実装は、動的消費電力の増加が比較的少ないデュアル・スレッドの同時実行性を最大化します。このセッションでは、次世代のPower Architecture e200z9プロセッサ・コアに含まれるSMT機能と、このマイクロアーキテクチャによって達成可能なパフォーマンス/パワー・メトリックの向上に焦点を当てます。 日時:FTF-ACC-F1259 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 新しいe200z9はいつ発売されますか?
記事全体を表示
BD-SL-i.MX6 (Qt Company の Qt 5.4 を実行) <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> BD-SL-i.MX6(旧SABRE Lite)ボードは、低コストのi.MX6開発プラットフォームです。このボードの最も優れた特性の1つは、利用可能な重要なソフトウェアサポートです。この記事では、QT CompanyのQt5.4についてご紹介します。以下のビデオは、 Qt Company のエンタープライズデバイス作成製品、つまりQtに最適化された事前構築済みソフトウェアスタックを示しています。これにより、組み込みLinuxおよびAndroid開発用の実際のデバイスでのプロトタイピングをすぐに開始できます。デモはQt5.4を実行しており、BD-SL-i.MX6とNitrogen製品ファミリーの画像が利用可能です。以下は、いくつかの機能を示す短いビデオです。 上のビデオは、組み込みLinux用に作成された画像を示しており、具体的には 、Yocto Project と The Freescale Community BSPのツールを使用して構築されています。このため、製品はこれらのプロジェクトによって提供されるパッケージを活用でき、Yocto ビルド システムを使用してコンポーネントを統合し、ビルドを調整できます。 詳細については、http://qt.io または http://boundarydevices.com/qt-for-device-creation/ をご覧ください 全般
記事全体を表示
Zephyr 的内存详情 如果您对这些资源有任何疑问或问题,请 提出新问题,恩智浦支持团队将为您解答。 在学习 Zephyr 时,存在许多与内存相关的问题。链接器会将代码和数据放置在何处?应用程序应如何配置以使用其他存储器? 链接器所使用的默认内存段是在设备树中进行配置的。通常,设备树会使用选定的节点来配置这些部分。以下是 MIMXRT1060-EVK 板上的一个示例: chosen { zephyr,flash = &is25wp064; zephyr,sram = &sdram0; }; 这些选定节点的名称可能会造成误导。 zephyr,flash 指向链接器用于所有代码(.text)和只读数据段的节点。通常,这指向物理闪存,例如,在这块板上,它被放置在外部 QSPI 闪存中,但它也可以位于非闪存的内存中。 zephyr,sram 指向链接器用于所有 .data和 .bss部分的节点。这应该位于 RAM 中,但不一定在 SRAM 中。在该板上,它位于外部 SDRAM 中。应用程序可以将这些节点指向最适合该应用程序的其他内存。其他常用的内存节点包括 &dtcm 、 &itcm 或 &ocram 。 通常,这些选定的节点在电路板设备树文件中进行设置。但是在学习 Zephyr 以及使用设备树时,最好在应用程序构建过程中生成的设备树文件中确认设备树设置,请参阅实验室指南:设备树和 VS Code 设备树查看器。 i.MX RT内存 大多数内存问题来自使用 i.MX RT 设备的用户。这些微控制器(MCU)是高性能无闪存设备,具备多种内部和外部存储选项,以最大化应用程序的性能和灵活性。以下是一些专门针对 i.MX RT 设备的有用资源: i.MX RT 应用说明: AN12437 i.MX RT系列性能优化 AN12077 使用 i.MX RT FlexRAM AN13970 Zephyr 中的 RT 系列内存重定位 ROM 中的引导加载程序在启动时需要 Flash 配置块(FCB),并且可以选择添加设备配置数据 (DCD) 或外部存储器配置数据 (XMCD),这些数据通常用于启用 SDRAM。这篇文章提供了更多关于在哪里可以找到这些结构,以及如何将它们包含在开发板中的详细信息。 不支持 SDRAM 的情况说明:Zephyr 对配备外部 SDRAM 的实时开发板的支持,通常会将数据存储在 SDRAM 中。ROM 引导加载程序会在 Zephyr 应用程序执行之前,通过 DCD 或 XMCD 配置 SDRAM 接口。这篇文章讨论了如何移除定制主板的 SDRAM。 如需配置 FlexRAM,调整 ITCM、DTCM 或 OCRAM 的大小,请参阅 AN13970 Zephyr 中的 RT 系列内存重定位 将代码重新定位到 RAM 中 将代码移至 RAM 是一个常见需求,例如,为了最大化性能或降低功耗。借助 Zephyr,应用程序可以将所有代码或部分代码迁移到 RAM 中。以下是一些有用的搬迁资源: AN13970 Zephyr 中的 RT 系列内存重定位 Zephyr代码和数据重定位API 重新定位代码的示例应用: 简单示例SDRAM_hello_world.zip将整个应用程序移动到 SDRAM,并在启动时使用 ROM 引导程序加载 RAM,然后再执行应用程序。 Zperf 示例:此 Zephyr 网络示例将网络堆栈和以太网驱动程序代码迁移至 ITCM,以提高在 MIMXRT1170-EVK 上构建时的性能。其余代码保留在默认的外部 QSPI 闪存中。 NXP SmartWatch 演示和网络研讨会:将大部分代码重新定位到内部 SRAM 以降低功耗,同时将图形资产保留在闪存中。 将数据加载到 RAM 在 Zephyr 中,所有数据、变量和堆栈的默认位置都位于 zephyr,sram 节点。然而,某些应用程序希望将特定数据放置在其他位置。例如,将数据放置在 DTCM 中以最大化性能,将 DMA 缓冲区放置在不可缓存的内存中,或将显示的大型帧缓冲区移动到外部 RAM。以下是一些有助于指定数据放置的资源: 静态变量的声明可以包含链接器段标签,以便将它们放置在特定段中。一个参考示例是dma_mcux_edma.c驱动程序,它将 dma_tcdpool 结构放置在 __dtcm_noinit_section 或 __nocache 部分。 静态变量的另一种选择是在变量声明中使用设备树节点,从而将其放置在特定的部分中。一个可以参考的例子是恩智浦的面部检测演示。此演示在设备树中添加选定的节点 zephyr,modelbuf ,该节点指向内存部分节点 sramx 。要使用此方法,内存段节点需要具备属性 zephyr,memory-region 。在源代码中, model_input_buf 缓冲区是用 zephyr_modelbuf 节点声明的。然后,链接程序将 model_input_buf 放置在 sramx 部分。 整个源文件或库中的 data 和 bss 部分可以重定位到其他 RAM,详情请参阅 Zephyr代码和数据重定位 API。 Zephyr 可以使用一个特殊的固定区域,将中断堆栈和主堆栈放置在不同的 RAM 区段中。简单示例pinned_hello_world.zip在 DTCM 中固定中断和主堆栈。   其他内存资源 示例调整内存节点大小,利用 NXP LPC5500 中的所有 SRAM 返回Zephyr知识中心
記事全体を表示
带有 S32K5xx RTD 的时钟 IP 发出的 S32DS 警告 0.8.0 使用 S32K5xx RTD 时 0.8.0编译时,我收到了来自时钟 IP 模块的许多警告。 有办法纠正它们吗? 这些警告是否可以忽略? 有计划把它们修好吗? Re: S32DS Warnings from Clock IP with S32K5xx RTD 0.8.0 你好@DirkEtzler、 谢谢您的提问。如前所述,S32K5 系列目前是 NPI(新产品推出)设备。因此,所有支持请求必须直接通过指定的恩智浦 FAE 处理。 或者,请通过以下网址创建支持票据: https://support.nxp.com/s/?language=en_US 系统会自动将您的请求转给相应的 FAE 团队,以便提供进一步帮助。 感谢您的理解。 顺祝商祺! 帕维尔
記事全体を表示
The benefits of choosing products with NXP security features (Japanese blog) Introduction NXP has long been developing products such as smart cards and secure elements for mobile devices. Based on these technologies, we offer a scalable range of embedded products, including MCUs/MPUs with built-in cryptographic accelerators, MCUs/MPUs with built-in EdgeLock ® secure enclaves, and dedicated security ICs (secure elements, secure authenticators), allowing for easy migration when products with different security strengths are required. We also offer a cloud service (EdgeLock 2GO) that securely writes confidential information to EdgeLock Secure Enclaves, Secure Elements, and Secure Authenticators. This article introduces the features and benefits of NXP's security-enabled products. NXP Hardware Security Product Features NXP offers products and services with the following security features, allowing users to select the optimal product based on the security level they require. Security features and services Feature Overview Cryptographic Accelerators Hardware-based encryption processing function implemented in MCU/MPU EdgeLock ® Secure Enclave A security block implemented within an MCU/MPU that integrates the above cryptographic accelerator as well as numerous other security functions. Secure Element/Authenticator An external IC specialized for security. EdgeLock 2GO A cloud service that supports key management and secure provisioning. In particular, products such as the EdgeLock ® Secure Enclave and Secure Element/Authenticator offer advanced security features not available in other companies' products. Even if you are not sure what level of security you need at the moment, by choosing NXP products, you can easily migrate to products with different security strengths if you need more advanced security features or if you no longer need them. NXP MCU/MPU without cryptographic accelerator or EdgeLock Secure Enclave MCU/MPU with built-in cryptographic accelerator or EdgeLock secure enclave External security IC (secure element/authenticator) The features when compared are shown below. Note: The actual features provided vary by product, so please check the product specifications for details.   1. MCU/MPU without cryptographic accelerator or EdgeLock Secure Enclave 2. MCU/MPU with built-in cryptographic accelerator or EdgeLock Secure Enclave 3. External security IC (secure element/authenticator) Product Examples MCX A(essential security), MCX C MCX A(advanced security), MCX L, MCX E, MCX N i.MX RT, i.MX 8, i.MX 9 SE05x, A5000, A30 Strong security ・Security software must run on the application CPU - Possibility of confidential information being leaked due to vulnerabilities in the application CPU and the software executed there. ・Application CPUs generally prioritize processing speed, and tamper resistance is a low priority (or is not considered at all) - Robust security with a dedicated security block that is physically independent from the application CPU ・Protection of confidential information from vulnerabilities in application CPU-side SW - Physical tamper resistance that also protects against some physical attacks ・In addition to 2., it also supports advanced physical attacks. Easier implementation of security software ・Security software (including key management and encryption algorithms) must be implemented and verified on the user software side. -Security processing has been implemented on the security function side In addition to 2., the following advantages are also provided: ・More advanced key management ・Product security can be strengthened without changing the MCU/MPU ・Security implementation can be standardized between systems using different host MCUs/MPUs Facilitating certification of final products ・If there is no security certification, it is necessary to extract information on compliance with cybersecurity standard requirements from product documentation or obtain it from customer support. -Third-party certification (SESIP/PSA) obtained - Evidence of conformance can be provided , and support is provided for obtaining cybersecurity standard certification for final products. - Meets the high-level hardware security requirements of various cybersecurity standards (depending on use cases) - In addition to 2, the more stringent Common Criteria (CC) certification has been obtained. Easier key writing (Provisioning) Customers must have PKI and manufacturing infrastructure for secure provisioning ・Initial investment and preparation period are required for new businesses ( EdgeLock Secure Enclave only) Flexible and secure key provisioning through the EdgeLock 2GO cloud service , enabling easy product launch. In addition to key provisioning with EdgeLock 2GO, factory-programmed credentials can be used for simple applications. While we've covered strong security and making security software easier to implement, we'll go into a bit more detail on third-party authentication and provisioning. Third-party certification Regardless of the security function used, the security processing behavior (output relative to input) will be the same, although there may be differences in processing speed. However, the security strength (tamper resistance, etc.) will differ depending on the security function implementation. Furthermore, even among products that are called the same secure element, the actual software/hardware implementation varies depending on the company. Security must also be considered in semiconductor suppliers' organizational structures and handling processes such as product development, manufacturing, and operation. The differences in security performance and processes of these semiconductor products from each company make it extremely difficult for users to compare them based on specifications or benchmarks. One way to solve these problems is to use third-party certification. Third-party certifications for ICs with security functions include SESIP, PSA, Common Criteria, and FIPS. A third-party organization evaluates the security implementation and operation of the security features declared by device manufacturers on a unified scale, verifying and certifying that they have been implemented correctly. In addition, we can provide documented evidence for products that have received third-party certification. This document allows customers to confirm how NXP products meet the requirements of cybersecurity standards, which is expected to reduce the effort required to ensure that end products incorporating NXP products comply with cybersecurity standards. NXP calls products that have received third-party certification under its EdgeLock ® Assurance program "Certified EdgeLock Assurance Products." A list of Certified EdgeLock Assurance products can be found here. You can also find product and certification evidence in the standards body's certified product lists. SESIP Certification List PSA Certification List Common Criteria (CC) Certified List The fact that components such as ICs/devices have already received third-party certification is expected to reduce the risk of non-compliance even when manufacturers obtain third-party certification for cybersecurity standards for their final products. For example, under the CRA (EU Cyber Resilience Act), products categorized as Default and Class 1 can be self-declared as well as third-party certified, but end users may still request third-party certification. About Secure Provisioning Service (EdgeLock 2GO) Products with security features require users to provision the confidential information they will use in their applications before they can actually be used. Provisioning must be done in a secure environment, and setting up a new secure environment on a user's production line requires a great deal of effort and expense. Additionally, if a user has multiple manufacturing bases, support will be required for each one. Furthermore, if manufacturing is outsourced, problems may arise such as it being difficult to exercise such control, or there being only a limited number of outsourcees that can exercise such control. NXP's secure elements/authenticators come pre-programmed with some identifying information at the NXP factory, and for simple use cases can be used without any provisioning during manufacturing. For complex use cases that cannot be covered by the identity information pre-programmed into the secure element/authenticator, or for MCU/MPU products with an integrated EdgeLock secure enclave that does not have pre-programmed identity information, NXP offers a cloud service ( EdgeLock 2GO ) that can be used in combination with NXP ICs. EdgeLock 2GO provides a means for secure provisioning during manufacturing and in the field by providing the ability to generate unique identities (key pairs and certificates) for each device and end-to-end encryption between EdgeLock 2GO and the device. In addition, EdgeLock 2GO's certificate authority is approved as a certificate authority that can issue certificates required by standards such as Matter and Qi. You can use it with confidence as a certificate authority that meets the requirements of these standards, not only when compliance with these standards is required, but also when it is not. In a separate article, we will take a closer look at the potential threats faced when handling confidential information on your production line and how EdgeLock 2GO addresses them. Software support for working with EdgeLock Secure Enclaves/Secure Elements We have mentioned that security can be strengthened by using products with security features. However, there are no set standards for APIs for using hardware security features, and each company has its own unique specifications. Doesn't this make it difficult to develop applications using these APIs? NXP provides middleware for host applications that not only provide device-specific APIs but also plugins for popular cryptographic libraries such as OpenSSL, PKCS#11, and Mbed-TLS. For example, by using a plugin for OpenSSL, applications that rely on OpenSSL (e.g., Eclipse Mosquitto ™ ) can use key protection using secure elements without any modifications. We will introduce practical use cases in a separate article. =========================​ We are currently unable to respond to comments in the " Comment " section of this post . We apologize for the inconvenience, but when making inquiries, please refer to " How to contact NXP with technical questions ( Japanese blog ) " . (If you are already an NXP distributor or have a relationship with NXP , you may ask the person in charge directly.) NXP has long been developing products such as smart cards and secure elements for mobile devices. Based on these technologies, we offer a scalable range of embedded products, including MCUs/MPUs with built-in cryptographic accelerators, MCUs/MPUs with built-in EdgeLock ® secure enclaves, and dedicated security ICs (secure elements, secure authenticators), allowing for easy migration when products with different security strengths are required. We also offer a cloud service (EdgeLock 2GO) that securely writes sensitive information to EdgeLock ® Secure Enclaves, Secure Elements, and Secure Authenticators. This article introduces the features and benefits of NXP's security-enabled products. Security Japanese Blog
記事全体を表示