Bureaucrats, dave_user, Administrators
8,184
edits
Changes
→XUELK 2.0.1/2.0.2/2.0.3
{{InfoBoxTop}}
{{AppliesToAXELULite}}
{{AppliesToSBCLynx}}
{{InfoBoxBottom}}
==Introduction==
[[File:TBDSBC Lynx-top.png|thumb|center|600px500px|captionSBC Lynx]]
SBC Lynx Embedded Linux Kit (XUELK for short) provides all the necessary components required to set up the developing environment to:
* build the bootloader (U-Boot)
* build and run Linux operating system on [[:Category:SBC Lynx|SBC Lynx board]]* build Linux and debug applications that will run be executed on top of Yocto-based Linux distribution running on the target.
The main kit components are:
* hardware platform composed of(SBC Lynx)** TBD* Development development host released in the form of [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]] containing:** Toolchain** U, tailored for [[Managed_Virtual_Machine_(MVM)#Yocto-based_Linux_distribution|Yocto-Boot bootloader sourcesbased distribution]]** Linux kernel sources** Root file systems* Technical technical documentation such (hardware manuals, mechanical drawings, reference schematics, application notes etc.) The documents related to the software issues help the user to quickly start configuring the bootloader and the operating system, by hiding most of the complexity of the underlying hardware. '''Reading of the [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine documentation]] is strongly recommended''', as it plays a '''major role''' in the XUELK organization.
==Kit Contents==
!Notes
|-
|style="text-align: center;" | [[File:TBDLynx.png|60px]]
|SBC Lynx<br>
CPU: Freescale NXP i.MX6MX6UL<br>SDRAM: 512 GB MB DDR3<br>
NOR: bootable SPI flash 32 MB<br>
NAND: 1GB
|Please refer to [[Hardware Manual Hardware_Manual_(AxelUltraSBC_Lynx) | Axel Ultra SBC Lynx Hardware Manual]]
|-
|style="text-align: center;" | [[File:Alimentatore.jpg|40px]]
|AC/DC Single Output Wall Mount adapter<br>
Output: +12V – 2.0 A
|
|-
|style="text-align: center;" | [[File:TBDTTL-232RG-VIP-WE.png|50px]]
|FTDI TTL/USB cable
|FTDI code: [http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm TTL-232RG-VIP-WE]
|-
|style="text-align: center;" | [[File:ProdSDC-MBLY-thumb.png|50px]]
|-
|}
==Additional documentation==
SBC Lynx documentation is provided on [[:Category:SBC_Lynx|Wiki]] product pages. The most important documents are listed below:
* [[XUELK Quick Start Guide]]
* [[Hardware_Manual_(SBC_Lynx)|Hardware Manual]]
* [[Mechanicals_(SBC_Lynx)|Mechanicals]]
== XUELK software components ==
{{ImportantMessage|text=From the software perspective, XUELK supports SBC Lynx and [[:Category:AXEL_ULite|AXEL ULite SOM]]. However, physical contents of the kit include SBC Lynx only.
}}
SBC Lynx Embedded Linux Kit is largely derived from the Yocto distributions released by NXP for the i.MX6 product family. For this reason most of the documentation provided by NXP remains valid for the XUELK development kit.
{| class="wikitable"
!
!colspan="16" | XUELK version
|-
|Release number
|0.9.0
|1.0.0
|1.1.0
|1.1.3
|1.2.0
|2.0.1/2.0.2/2.0.3
|-
|Release type
|Major
|Major
|Minor
|Minor
|Minor
|Major
|-
|Status
|Beta
|Released
|Released
|Released
|Released
|Released
|-
|Release date
|March 2016
|August 2016
|November 2016
|March 2017
|May 2017
|Sep 2017
|-
|Release notes
|[[#XUELK 0.9.0|0.9.0]]|[[#XUELK 1.0.0|1.0.0]]|[[#XUELK 1.1.0|1.1.0]]|[[#XUELK 1.1.3|1.1.3]]|[[#XUELK 1.2.0|1.2.0]]|[[#XUELK 2.0.1/2.0.2/2.0 .3| Ver 2.0.1/2.0.2/2.0.3]]
|-
|PCB version
|SBC Lynx CS214515|SBC Lynx CS214515A<br>(AXELULite CS184015) [1]|SBC Lynx CS214515A<br>(AXELULite CS184015) [1]|SBC Lynx CS214515A<br>SBC Lynx CS214515B<br>(AXELULite CS184015) [1]|SBC Lynx CS214515A<br>SBC Lynx CS214515B<br>(AXELULite CS184015)<br>(AXELULite CS184015A) [1]|SBC Lynx CS214515A<br>SBC Lynx CS214515B<br>(AXELULite CS184015)<br>(AXELULite CS184015A) [1]
|-
|[[ConfigID_and_UniqueIDConfigID_(XUELK)|ConfigIDs]] (core/interfaces)|TBD0x00000008/0x0000000E|0x00000008/0x0000000E<br>0x0000000C/NA<br>(0x0000000B/TBDNA) [1]|0x00000008/0x0000000E<br>0x0000000C/NA<br>(0x0000000B/NA) [1]|0x00000008/0x0000000E<br>0x0000000C/NA<br>0x00000013/NA [2]<br>(0x0000000B/0x00000010) [1]|0x00000008/0x0000000E<br>0x0000000C/NA<br>0x00000013/0x0000002D [3]<br>0x00000013/0x0000002E [3]<br>0x00000013/0x0000002F [3]<br>0x00000013/0x00000030 [3]<br>(0x0000000B/0x00000010) [1]<br>(0x00000014/0x00000010) [1]|0x00000008/0x0000000E<br>0x0000000C/NA<br>0x00000013/0x0000002D [3]<br>0x00000013/0x0000002E [3]<br>0x00000013/0x0000002F [3]<br>0x00000013/0x00000030 [3]<br>(0x0000000B/0x00000010) [1]<br>(0x00000014/0x00000010) [1]
|-
|[[Managed_Virtual_Machine_(MVM)|MVM]] version
|TBDxuelk-0.9.0, tested with:<br/>Virtual Box 5.0.14<br/>Vagrant 1.8.1|xuelk-1.0.0, tested with:<br/>Virtual Box 5.0.26<br/>Vagrant 1.8.1|xuelk-1.1.0, tested with:<br/>Virtual Box 5.1.10<br/>Vagrant 1.8.7|xuelk-1.1.3, tested with:<br/>Virtual Box 5.1.10<br/>Vagrant 1.8.7|xuelk-1.2.0, tested with:<br/>Virtual Box 5.1.10<br/>Vagrant 1.8.7|xuelk-2.0.0, tested with:<br/>Virtual Box 5.1.28<br/>Vagrant 2.0.0
|-
|U-Boot version/release
|TBDU-Boot 2015.04/TBDxuelk-0.9.0|U-Boot 2015.04/xuelk-1.0.0|U-Boot 2015.04/xuelk-1.1.0|U-Boot 2015.04/xuelk-1.1.3|U-Boot 2015.04/xuelk-1.2.1|U-Boot 2016.03/xuelk-2.0.3
|-
|Linux version/release
|TBDLinux 3.14.52/TBDxuelk-0.9.0|Linux 3.14.52/xuelk-1.0.0|Linux 3.14.52/xuelk-1.1.0|Linux 3.14.52/xuelk-1.1.3|Linux 3.14.52/xuelk-1.2.1|Linux 4.1.15/xuelk-2.0.3
|-
|Drivers
|valign="top" | TBDUART<br/>Ethernet<br/>SD/MMC<br/>USB Host<br/>USB Device<br/>NOR Flash<br/>NAND Flash<br/>ADC<br/>RTC<br/>|valign="top"|UART<br/>Ethernet<br/>SD/MMC<br/>USB Host<br/>USB Device<br/>NOR Flash<br/>NAND Flash<br/>ADC<br/>RTC<br/>CAN<br/>DWM<br/>LCD<br/>|valign="top"|UART<br/>Ethernet<br/>SD/MMC<br/>USB Host<br/>USB Device<br/>NOR Flash<br/>NAND Flash<br/>ADC<br/>RTC<br/>CAN<br/>DWM<br/>LCD<br/>|valign="top"|UART<br/>Ethernet<br/>SD/MMC<br/>USB Host<br/>USB Device<br/>NOR Flash<br/>NAND Flash<br/>ADC<br/>RTC<br/>CAN<br/>DWM<br/>LCD<br/>|valign="top"|UART<br/>Ethernet<br/>SD/MMC<br/>USB Host<br/>USB OTG<br/>NOR Flash<br/>NAND Flash<br/>ADC<br/>RTC<br/>CAN<br/>DWM (WLAN/BT)<br/>LCD<br/>|valign="top"|UART<br/>Ethernet<br/>SD/MMC<br/>USB Host<br/>USB OTG<br/>NOR Flash<br/>NAND Flash<br/>ADC<br/>RTC<br/>CAN<br/>DWM (WLAN/BT)<br/>LCD<br/>
|-
|Freescale NXP BSP version|TBD3.14.52_1.1.0_ga|3.14.52_1.1.0_ga|3.14.52_1.1.0_ga|3.14.52_1.1.0_ga|3.14.52_1.1.0_ga|4.1.15-2.0.0_ga|-|Xenomai version|||| 2.6.5| 2.6.5|
|-
|Build System
|TBDYocto Fido (1.8)|Yocto Fido (1.8)|Yocto Fido (1.8)|Yocto Fido (1.8)|Yocto Fido (1.8)|Yocto Krogoth (2.1)
|-
|}
=== XUELK microSD Layout ===
[[File:XUELK-uSD-partitioning.png|thumb|center|600px|microSD card partitioning]] Most of storage space is occupied by two partitions:*a <code>FAT32</code> partition (<code>mmcblk0p1</code>) containing:**U-Boot <code>bootscript</code>**Linux kernel and DTB binary images**XUELK virtual machine image in OFV format ([[Managed_Virtual_Machine_(MVM)|MVM]] basic version)**7-zip Windows executable file*an <code>ext3</code> partition (<code>mmcblk0p2</code>) containing the root file system for the target. <code>bootscript</code> and root file system are used to boot the target as described in [[#Target_setup_and_first_boot|this section]]. It is worth remembering that the microSD card is [[Booting_options_(SBC_Lynx)|bootable]], because U-Boot image is stored at address 0x400. However, even if U-Boot is run from the microSD card, '''the environment is retrieved from NOR flash'''.====How to create a bootable microSD card====Please refer to this [[How_to_create_a_bootable_microSD_card_(XUELK)|this page]]. === XUELK Updates updates ===TBD
{{ImportantMessage|text=It's recommended to use the latest available XUELK version. Please refer to [[#Release notes | Release notes]] for further information.}}
XUELK updating process consists of updating the [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]] it is based on. The procedure is described [[Managed_Virtual_Machine_(MVM)#Updating_MVM|here]].
Please note that this process '''implicitly updates git source code repositories of U-Boot and/or Linux kernel'''. Thus '''it is strongly recommended to create new local branches if you need to modify source code'''.
==== Updating git repositories ====
|Linux
|git@git.dave.eu:lynx/linux-2.6-imx.git
|/home/dvdk/lynx/linux-2.6-imx
|-
|U-Boot
|git@git.dave.eu:lynx/u-boot-imx.git
|/home/dvdk/lynx/u-boot-imx
|-
|Yocto BSP
|git@git.dave.eu:lynx/axellynx-bsp.git
|/home/dvdk/lynx/lynx-bsp
|-
This means that these components can be kept in sync and up to date with '''DAVE Embedded Systems''' repositories.
===Release notes = RSA == ==== XUELK 2.0.1/2.0.2/2.0.3 ==== ===== Notes 2.0.3 ===== * Add support for ISSI SPI NOR flash ===== Notes 2.0.2 ===== * Update Yocto BSP to latest Krogoth to fix WPA2 key generation replay security bug (for more details see [http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=krogoth&id=54e3f82bd77203c3d578e26c86506e6ef5c27000]) ===== Notes 2.0.1 =====Major update on XUELK 1.2.0:* BSP update to NXP 4.1.15-2.0.0_ga* Minor fixes for Wifi and BT ===== Known issues and limitations ===== The following table reports the known limitations of this XUELK release: {| class="wikitable" |-!Limitations!Description|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|Low Power Idle not supported|Low Power Idle is not supported in this release|} ==== XUELK 1.2.0 ==== ===== Notes ===== Minor update on XUELK 1.1.3:* add CPU temperature for thermal thresholds settings* add rf kill support for Bluetooth on device tree* add [[ConfigID and UniqueID|ConfigID]] support for different hardware configurations: SOM_ConfigID and CB_ConfigID* minor fixes and enhancement ===== Known issues and limitations ===== The following table reports the known limitations of this XUELK release:
{| class==== Synchronizing the repository ===="wikitable" |-!Issue!Description|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|Low Power Idle not supported|Low Power Idle is not supported in this release|}
{{ImportantMessage|textclass=After "wikitable" |-!Issue!Description|-|Rebooting in Linux may hang|Software reboot on Linux may hang (without rebooting the XUELK DVDK installation, please check for updates board) when root file system in on SD/MMC|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|Low Power Idle not supported|Low Power Idle is not supported in this release|-|Failing mount of root file system on microSD card|Some commercial microSD cards occasionally prevent the target from mounting the source tree repositories provided root file system stored on themselves. microSD cards delivered along with the kit, as described in XUELK do not exhibit this problem.|-|Missing firmware file for Bluetooth|In case [[Axel_Embedded_Linux_Kit_(XUELK)#XUELK_Updates -AN-001:_Using_WiFi-Bluetooth_combo_plugin_with_SBC_Lynx| XUELK UpdatesDWM wireless plugin]]is used, the following file need to be copied in <code>/lib/firmware/ti-connectivity/</code>:*<code>TIInit_7.6.15.}bts</code> (please click [https://github.com/TI-ECS/bt-firmware/blob/master/am335x/TIInit_7.6.15.bts here] to download it)|}
==== XUELK 1.0.0 ====
===== Notes =====
First stable release with support for SBC Lynx revision A and Axel ULite ===== Known issues and limitations =====TBDThe following table reports the known limitations of this XUELK release: {| class="wikitable" |-!Issue!Description|-|Rebooting in Linux may hang|Software reboot on Linux may hang (without rebooting the board) when root file system in on SD/MMC|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|Low Power Idle not supported|Low Power Idle is not supported in this release|-|XUELK environment fixup for SD boot<br/>on SBC Lynx|To boot with the XUELK SD card, user may need to execute the following commands at u-boot prompt<br/><pre>setenv mmcroot /dev/mmcblk0p2setenv mmc_loadfdt 'fatload mmc 0:1 ${fdtaddr} imx6ul-lynx-som000c.dtb'saveenv</pre>|-|Failing mount of root file system on microSD card|Some commercial microSD cards occasionally prevent the target from mounting the root file system stored on themselves. microSD cards delivered along with XUELK do not exhibit this problem.|-|System shutdown mode using the <code>shutdown -h now</code> command prevent the subsequent system's power-up|Issuing a system shutdown by the command <code>shutdown -h now</code> as described in [[Supported power mode transitions (SBC Lynx)]] will prevent the subsequent system's boot.|-|Missing 7-zip Windows executable in microSD card|Please download it from http://www.7-zip.org. |-|In the MVM, <code>network-manager</code> applet is not installed by default.| Please refer to [[VirtualBox_Network_Configuration#VBox_Bridged_configuration|this page]] to install it.|-|Missing firmware file for Bluetooth|In case [[XUELK-AN-001:_Using_WiFi-Bluetooth_combo_plugin_with_SBC_Lynx|DWM wireless plugin]] is used, the following file need to be copied in <code>/lib/firmware/ti-connectivity/</code>:*<code>TIInit_7.6.15.bts</code> (please click [https://github.com/TI-ECS/bt-firmware/blob/master/am335x/TIInit_7.6.15.bts here] to download it)|}
==== XUELK 0.9.0 ====
===== Notes =====
First beta release.
===== Known issues and limitations =====
The following table reports the known limitations of this XUELK release:
!Description
|-
|Rebooting in Linux may hang|Software reboot on Linux may hang (without rebooting the board) when root file system in on SD/MMC|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|LDO Mode not supported|LDO Mode is not supported in this SW release|-|Low Power Idle not supported|Low Power Idle is not supported in this release|-|DDR3 Frequency limited at 306 MHz|The DDR3 RAM frequency is limited at 306 MHz in this release
|-
|}
==Quick start guide==
This chapter describes how to quickly start working with the XUELK kit. The following paragraphs will guide you through the setup and installation procedures.
===UnboxingKit registration===TBD{{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. Registration grants access to reserved material such as source code and additional documentation.===Host setup===Please install To register the kit, please send an email to [mailto:support-lynx@dave.eu support-lynx@lynx.eu], [[Development_Kits_Identification_Codes|providing the kit P/N and configure XUELK MVM as S/N]]. If you also wish to access git repositories containing source code, please follow the procedure described [[Managed_Virtual_Machine_(MVM)#Installation_and_configurationAccessing_DAVE_Embedded_Systems_restricted_git_repositories|here]].}} ===Target setupand first boot===This section describes how to quick start an SBC Lynx board.delivered along with XUELK kit (see also the following image):
*connect a TTL/USB serial cable to J42 connector; J42 pinout is:
** 1: TX data
** 4: GND
*on host side start your favorite terminal that will be used to interact with the target's serial console; communication parameters are 115200-8-N-1
*optionally connect the system to Ethernet LAN by plugging cable into connector J16
*connect 12V power supply to J35 connector; J35 pinout is:
**1: GND
**2: VIN*insert microSD card in the slot J43. [[File:SBCLynx-XUELK.png|thumb|center|600px|Target setup for first boot]] Once power has been applied to the target, U-Boot bootloader will be fetched from the SPI NOR flash and executed. Boot messages will be printed out to the serial console. Redundant U-Boot environment is stored in the NOR flash as well, as depicted in the following image. [[File:Xub-nor.png|thumb|center|350px|NOR flash default partitioning]] By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the <code>mmcblk0p2</code> partition of the [[#XUELK microSD Layout|microSD card itself]]. At the end of boot process, Linux shell shall be available on the serial console. The following dump shows the typical messages printed out to the console during bootstrap process.<pre class="mw-collapsible mw-collapsed">U-Boot 2015.04 (Mar 31 2016 - 23:22:16)-xuelk-0.9.0 CPU: Freescale i.MX6UL rev1.0 at 396 MHzCPU: Temperature 30 CReset cause: PORBoard: MX6UL LYNXI2C: readyDRAM: 512 MiBPMIC: PFUZE300 DEV_ID=0x30 REV_ID=0x11NAND: 1024 MiBMMC: FSL_SDHC: 0SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiBIn: serialOut: serialErr: serialSOM ConfigID#: 00000008SOM UniqueID#: e317402a:1735b1d4CB ConfigID#: 0000000eCB UniqueID#: a0000011:0dcf672dBoard: MX6UL-LynxNet: FEC0Normal BootHit any key to stop autoboot: 0starting USB...USB0: Port not available.USB1: USB EHCI 1.00scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found USB device 0: unknown device** Bad device usb 0 **switch to partitions #0, OKmmc0 is current devicereading boot.scr228 bytes read in 12 ms (18.6 KiB/s)Running bootscript from mmc ...## Executing script at 80800000bootscript generated with command "mkimage -T script -C none -n SBC-Lynx -d bootscript.txt boot.scr"Booting SBC-Lynx via mmcbootreading uImage6033832 bytes read in 277 ms (20.8 MiB/s)reading imx6ul-lynx.dtb29394 bytes read in 22 ms (1.3 MiB/s)FDT: override 'som_configid' with '00000008'FDT: property cb_configid 0000000e matchFDT: override 'som_uniqueid' with 'e317402a:1735b1d4'FDT: override 'cb_uniqueid' with 'a0000011:0dcf672d'## Booting kernel from Legacy Image at 80800000 ... Image Name: Linux-3.14.52-xuelk-0.9.0 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 6033768 Bytes = 5.8 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK## Flattened Device Tree blob at 83000000 Booting using the fdt blob at 0x83000000EHCI failed to shut down host controller. Loading Kernel Image ... OK Using Device Tree in place at 83000000, end 8300a2d1switch to ldo_bypass mode! Starting kernel ... Booting Linux on physical CPU 0x0Linux version 3.14.52-xuelk-0.9.0 (amon@linuxserver2) (gcc version 4.9.2 (GCC) ) #2 SMP PREEMPT Thu Mar 31 22:53:29 CEST 2016CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7dCPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cacheMachine model: Freescale i.MX6 UltraLite LYNX Boardcma: CMA: reserved 320 MiB at 8c000000Memory policy: Data cache writeallocPERCPU: Embedded 8 pages/cpu @8bb41000 s8320 r8192 d16256 u32768Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048Kernel command line: root=/dev/mmcblk1p2 rootwait rw console=ttymxc0,115200 vmalloc=400M mtdparts=gpmi-nand:8M(nand-uboot),1M(nand-env1),1M(nand-env2),1M(nand-fdt),1M(nand-spare),8M(nand-kernel),4M(nand-splash),-(nand-ubi);spi0.0:1M(spi-uboot),256k(spi-env1),256k(spi-env2),512k(spi-dtb),6M(spi-kernel),4M(spi-splash),-(spi-free)PID hash table entries: 2048 (order: 1, 8192 bytes)Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)Memory: 179908K/524288K available (7511K kernel code, 461K rwdata, 2596K rodata, 392K init, 433K bss, 344380K reserved, 0K highmem)Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) vmalloc : 0xa0800000 - 0xff000000 (1512 MB) lowmem : 0x80000000 - 0xa0000000 ( 512 MB) pkmap : 0x7fe00000 - 0x80000000 ( 2 MB) modules : 0x7f000000 - 0x7fe00000 ( 14 MB) .text : 0x80008000 - 0x809e7134 (10109 kB) .init : 0x809e8000 - 0x80a4a080 ( 393 kB) .data : 0x80a4c000 - 0x80abf400 ( 461 kB) .bss : 0x80abf40c - 0x80b2ba5c ( 434 kB)SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1Preemptible 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=1NR_IRQS:16 nr_irqs:16 16Switching to timer-based delay loopsched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682nsclocksource_of_init: no matching clocksources foundConsole: colour dummy device 80x30Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000)pid_max: default: 32768 minimum: 301Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)CPU: Testing write buffer coherency: ok/cpus/cpu@0 missing clock-frequency propertyCPU0: thread -1, cpu 0, socket 0, mpidr 80000000Setting up static identity map for 0x807267c0 - 0x80726818Brought up 1 CPUsSMP: Total of 1 processors activated (6.00 BogoMIPS).CPU: All CPU(s) started in SVC mode.devtmpfs: initializedVFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5pinctrl core: initialized pinctrl subsystemregulator-dummy: no parametersNET: Registered protocol family 16DMA: preallocated 256 KiB pool for atomic coherent allocationscpuidle: using governor laddercpuidle: using governor menuUse WDOG1 as reset sourcesyscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registeredvdd3p0: 2625 <--> 3400 mV at 3000 mVcpu: 725 <--> 1450 mVvddsoc: 725 <--> 1450 mVsyscon 20e4000.iomuxc-gpr: regmap [mem 0x020e4000-0x020e7fff] registeredsyscon 21ac000.romcp: regmap [mem 0x021ac000-0x021affff] registeredsyscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registeredhw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.hw-breakpoint: maximum watchpoint size is 8 bytes.imx6ul-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver20dc000.gpc supply pu not found, using dummy regulatorbio: create slab <bio-0> at 0mxs-dma 1804000.dma-apbh: initializedvref-3v3: 3300 mVusb_otg1_vbus: 5000 mVusb_otg2_vbus: 5000 mVi2c-core: driver [max17135] using legacy suspend methodi2c-core: driver [max17135] using legacy resume methodSCSI subsystem initializedusbcore: registered new interface driver usbfsusbcore: registered new interface driver hubusbcore: registered new device driver usbi2c i2c-0: IMX I2C adapter registeredLinux video capture interface: v2.00pps_core: LinuxPPS API ver. 1 registeredpps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>PTP clock support registeredMIPI CSI2 driver module loadedAdvanced Linux Sound Architecture Driver Initialized.Bluetooth: Core ver 2.18NET: Registered protocol family 31Bluetooth: HCI device and connection manager initializedBluetooth: HCI socket layer initializedBluetooth: L2CAP socket layer initializedBluetooth: SCO socket layer initializedcfg80211: Calling CRDA to update world regulatory domainSwitched to clocksource mxc_timer1NET: Registered protocol family 2TCP established hash table entries: 4096 (order: 2, 16384 bytes)TCP bind hash table entries: 4096 (order: 3, 32768 bytes)TCP: Hash tables configured (established 4096 bind 4096)TCP: reno registeredUDP hash table entries: 256 (order: 1, 8192 bytes)UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)NET: Registered protocol family 1RPC: 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 loadedfutex hash table entries: 256 (order: 2, 16384 bytes)VFS: Disk quotas dquot_6.5.2Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)NFS: Registering the id_resolver key typeKey type id_resolver registeredKey type id_legacy registeredjffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.fuse init (API version 7.22)msgmni has been set to 991io scheduler noop registeredio scheduler deadline registeredio scheduler cfq registered (default)imx-weim 21b8000.weim: Driver registered.MIPI DSI driver module loadedMIPI DSI driver module loadedimx-sdma 20ec000.sdma: no event needs to be remappedimx-sdma 20ec000.sdma: loaded firmware 3.2imx-sdma 20ec000.sdma: initializedpfuze100-regulator 0-0008: Full layer: 1, Metal layer: 1pfuze100-regulator 0-0008: FAB: 0, FIN: 0pfuze100-regulator 0-0008: pfuze3000 found.SW1A: 700 <--> 3300 mV at 3300 mVSW1B: 700 <--> 1475 mV at 1175 mVSW2: 2500 <--> 3300 mV at 3300 mVSW3: 900 <--> 1650 mV at 1350 mVSWBST: 5000 <--> 5150 mV at 5000 mVVSNVS: 1000 <--> 3000 mV at 3000 mVVREFDDR: 750 mVVLDO1: 1800 <--> 3300 mV at 3300 mVVLDO2: 800 <--> 1550 mV at 1500 mVVCCSD: 2850 <--> 3300 mV at 3300 mVV33: 2850 <--> 3300 mV at 3300 mVVLDO3: 1800 <--> 3300 mV at 1800 mVVLDO4: 1800 <--> 3300 mV at 1800 mVSerial: IMX driver2018000.serial: ttymxc6 at MMIO 0x2018000 (irq = 71, base_baud = 5000000) is a IMX2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58, base_baud = 5000000) is a IMXconsole [ttymxc0] enabled21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60, base_baud = 5000000) is a IMXserial: Freescale lpuart driverimx sema4 driver is registered.[drm] Initialized drm 1.1.0 20060810[drm] Initialized vivante 1.0.0 20120216 on minor 0brd: module loadedloop: module loadednand: device found, Manufacturer ID: 0x01, Chip ID: 0xd3nand: AMD/Spansion S34ML08G1nand: 1024MiB, SLC, page size: 2048, OOB size: 64gpmi-nand 1806000.gpmi-nand: mode:4 ,failed in set feature.Scanning device for bad blocksrandom: nonblocking pool is initializedBad eraseblock 5903 at 0x00002e1e00008 cmdlinepart partitions found on MTD device gpmi-nandCreating 8 MTD partitions on "gpmi-nand":0x000000000000-0x000000800000 : "nand-uboot"0x000000800000-0x000000900000 : "nand-env1"0x000000900000-0x000000a00000 : "nand-env2"0x000000a00000-0x000000b00000 : "nand-fdt"0x000000b00000-0x000000c00000 : "nand-spare"0x000000c00000-0x000001400000 : "nand-kernel"0x000001400000-0x000001800000 : "nand-splash"0x000001800000-0x000040000000 : "nand-ubi"gpmi-nand 1806000.gpmi-nand: driver registered.m25p80 spi0.0: s25fl256s1 (32768 Kbytes)7 cmdlinepart partitions found on MTD device spi0.0Creating 7 MTD partitions on "spi0.0":0x000000000000-0x000000100000 : "spi-uboot"0x000000100000-0x000000140000 : "spi-env1"0x000000140000-0x000000180000 : "spi-env2"0x000000180000-0x000000200000 : "spi-dtb"0x000000200000-0x000000800000 : "spi-kernel"0x000000800000-0x000000c00000 : "spi-splash"0x000000c00000-0x000002000000 : "spi-free"spi_imx 2008000.ecspi: probedCAN device driver interface2188000.ethernet supply phy not found, using dummy regulatorpps pps0: new PPS source ptp0libphy: fec_enet_mii_bus: probedfec 2188000.ethernet eth0: registered PHC device 0ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driverehci-mxc: Freescale On-Chip EHCI Host driverusbcore: registered new interface driver usb-storageusbcore: registered new interface driver usb_ehset_test2184800.usbmisc supply vbus-wakeup not found, using dummy regulatorci_hdrc ci_hdrc.1: EHCI Host Controllerci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00hub 1-0:1.0: USB hub foundhub 1-0:1.0: 1 port detectedmousedev: PS/2 mouse device common for all micesnvs_pwrkey 20cc000.snvs-pwrkey: can't get snvs clockinput: 20cc000.snvs-pwrkey as /devices/soc0/soc.0/2000000.aips-bus/20cc000.snvs-pwrkey/input/input0snvs_pwrkey 20cc000.snvs-pwrkey: i.MX snvs powerkey probedi2c-core: driver [isl29023] using legacy suspend methodi2c-core: driver [isl29023] using legacy resume methodsnvs_rtc 20cc034.snvs-rtc-lp: can't get snvs-rtc clocksnvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0i2c /dev entries driverIR NEC protocol handler initializedIR RC5(x) protocol handler initializedIR RC6 protocol handler initializedIR JVC protocol handler initializedIR Sony protocol handler initializedIR RC5 (streamzap) protocol handler initializedIR SANYO protocol handler initializedIR MCE Keyboard/mouse protocol handler initializedi2c-core: driver [mag3110] using legacy suspend methodi2c-core: driver [mag3110] using legacy resume methodimx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)Bluetooth: HCI UART driver ver 2.2Bluetooth: HCI H4 protocol initializedBluetooth: HCI BCSP protocol initializedBluetooth: HCIATH3K protocol initializedusbcore: registered new interface driver bcm203xusbcore: registered new interface driver btusbusbcore: registered new interface driver ath3ksdhci: Secure Digital Host Controller Interface driversdhci: Copyright(c) Pierre Ossmansdhci-pltfm: SDHCI platform and OF driver helpermmc1: no vqmmc regulator foundmmc1: no vmmc regulator foundmmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMAcaam 2140000.caam: Instantiated RNG4 SH0mmc1: host does not support reading read-only switch. assuming write-enable.caam 2140000.caam: Instantiated RNG4 SH1caam 2140000.caam: device ID = 0x0a160300 (Era 8)caam 2140000.caam: job rings = 3, qi = 0mmc1: new high speed SDHC card at address 1234mmcblk1: mmc1:1234 SA16G 14.4 GiB mmcblk1: p1 p2caam algorithms registered in /proc/cryptocaam_jr 2141000.jr0: registering rng-caamplatform caam_sm: blkkey_ex: 8 keystore units availableplatform caam_sm: 64-bit clear key:platform caam_sm: [0000] 00 01 02 03 04 0f 06 07platform caam_sm: 64-bit black key:platform caam_sm: [0000] 5f 69 65 43 d8 01 d4 35platform caam_sm: [0008] 72 51 75 22 a5 33 93 cfplatform caam_sm: 128-bit clear key:platform caam_sm: [0000] 00 01 02 03 04 0f 06 07platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0fplatform caam_sm: 128-bit black key:platform caam_sm: [0000] 7e 83 f5 8e ed bd bf 4eplatform caam_sm: [0008] 6f 98 a2 68 c3 30 a3 81platform caam_sm: 192-bit clear key:platform caam_sm: [0000] 00 01 02 03 04 0f 06 07platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0fplatform caam_sm: [0016] 10 11 12 13 14 15 16 17platform caam_sm: 192-bit black key:platform caam_sm: [0000] 73 ba ab 08 93 75 f2 e3platform caam_sm: [0008] 66 73 d2 17 0c a7 f3 08platform caam_sm: [0016] 5b ee ee 28 37 82 c6 d6platform caam_sm: [0024] 75 3f 5e fc 50 be 9f c9platform caam_sm: 256-bit clear key:platform caam_sm: [0000] 00 01 02 03 04 0f 06 07platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0fplatform caam_sm: [0016] 10 11 12 13 14 15 16 17platform caam_sm: [0024] 18 19 1a 1b 1c 1d 1e 1fplatform caam_sm: 256-bit black key:platform caam_sm: [0000] da 35 27 8d 68 e2 e8 44platform caam_sm: [0008] 58 3a 7d 32 ea 54 dc 77platform caam_sm: [0016] 48 a1 28 bc a2 71 ad 8dplatform caam_sm: [0024] 6f 9a 59 ba 5c 35 63 56platform caam_sm: 64-bit unwritten blob:platform caam_sm: [0000] 00 00 00 00 00 00 00 00platform caam_sm: [0008] 00 00 00 00 00 00 00 00platform caam_sm: [0016] 00 00 00 00 00 00 00 00platform caam_sm: [0024] 00 00 00 00 00 00 00 00platform caam_sm: [0032] 00 00 00 00 00 00 00 00platform caam_sm: [0040] 00 00 00 00 00 00 00 00platform caam_sm: [0048] 00 00 00 00 00 00 00 00platform caam_sm: [0056] 00 00 00 00 00 00 00 00platform caam_sm: [0064] 00 00 00 00 00 00 00 00platform caam_sm: [0072] 00 00 00 00 00 00 00 00platform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: 128-bit unwritten blob:platform caam_sm: [0000] 00 00 00 00 00 00 00 00platform caam_sm: [0008] 00 00 00 00 00 00 00 00platform caam_sm: [0016] 00 00 00 00 00 00 00 00platform caam_sm: [0024] 00 00 00 00 00 00 00 00platform caam_sm: [0032] 00 00 00 00 00 00 00 00platform caam_sm: [0040] 00 00 00 00 00 00 00 00platform caam_sm: [0048] 00 00 00 00 00 00 00 00platform caam_sm: [0056] 00 00 00 00 00 00 00 00platform caam_sm: [0064] 00 00 00 00 00 00 00 00platform caam_sm: [0072] 00 00 00 00 00 00 00 00platform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: 196-bit unwritten blob:platform caam_sm: [0000] 00 00 00 00 00 00 00 00platform caam_sm: [0008] 00 00 00 00 00 00 00 00platform caam_sm: [0016] 00 00 00 00 00 00 00 00platform caam_sm: [0024] 00 00 00 00 00 00 00 00platform caam_sm: [0032] 00 00 00 00 00 00 00 00platform caam_sm: [0040] 00 00 00 00 00 00 00 00platform caam_sm: [0048] 00 00 00 00 00 00 00 00platform caam_sm: [0056] 00 00 00 00 00 00 00 00platform caam_sm: [0064] 00 00 00 00 00 00 00 00platform caam_sm: [0072] 00 00 00 00 00 00 00 00platform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: 256-bit unwritten blob:platform caam_sm: [0000] 00 00 00 00 00 00 00 00platform caam_sm: [0008] 00 00 00 00 00 00 00 00platform caam_sm: [0016] 00 00 00 00 00 00 00 00platform caam_sm: [0024] 00 00 00 00 00 00 00 00platform caam_sm: [0032] 00 00 00 00 00 00 00 00platform caam_sm: [0040] 00 00 00 00 00 00 00 00platform caam_sm: [0048] 00 00 00 00 00 00 00 00platform caam_sm: [0056] 00 00 00 00 00 00 00 00platform caam_sm: [0064] 00 00 00 00 00 00 00 00platform caam_sm: [0072] 00 00 00 00 00 00 00 00platform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: 64-bit black key in blob:platform caam_sm: [0000] 76 1a d3 a8 86 30 b4 a9platform caam_sm: [0008] 03 2d 01 ef dd 15 89 7cplatform caam_sm: [0016] d3 b3 14 03 ff 1d 6d efplatform caam_sm: [0024] b1 74 a7 d4 2e 7f 3a 65platform caam_sm: [0032] d5 b2 b6 56 e8 b0 82 cfplatform caam_sm: [0040] d4 59 c7 be 73 47 b9 dbplatform caam_sm: [0048] 6f 44 84 81 a1 04 13 d9platform caam_sm: [0056] 00 00 00 00 00 00 00 00platform caam_sm: [0064] 00 00 00 00 00 00 00 00platform caam_sm: [0072] 00 00 00 00 00 00 00 00platform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: 128-bit black key in blob:platform caam_sm: [0000] 50 a0 64 22 80 35 36 4eplatform caam_sm: [0008] 1c 6a 31 07 87 4c db f2platform caam_sm: [0016] 13 6a 4c 47 08 40 e3 87platform caam_sm: [0024] 98 52 fe 72 25 9f 91 ddplatform caam_sm: [0032] a6 e0 31 e1 72 50 ea 02platform caam_sm: [0040] 05 a9 62 d8 7e dd 91 48platform caam_sm: [0048] 58 94 2d bd 1c 84 9b 2eplatform caam_sm: [0056] 68 b7 16 05 6b 6c 4a 8aplatform caam_sm: [0064] 00 00 00 00 00 00 00 00platform caam_sm: [0072] 00 00 00 00 00 00 00 00platform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: 192-bit black key in blob:platform caam_sm: [0000] a5 d5 43 dc 3e a5 72 dcplatform caam_sm: [0008] 6a 8c 07 1a 3c 29 29 0dplatform caam_sm: [0016] af d9 84 13 68 5f 65 15platform caam_sm: [0024] 67 ae e9 5b 16 26 ab 2cplatform caam_sm: [0032] f3 ee 21 2f 51 ea f4 17platform caam_sm: [0040] 27 42 81 f3 ea a2 73 fbplatform caam_sm: [0048] 8e b9 45 dd c8 04 9b 67platform caam_sm: [0056] 6a 5f 9f c2 08 dc c7 73platform caam_sm: [0064] 0b a5 46 35 bb 65 ee d1platform caam_sm: [0072] 00 00 00 00 00 00 00 00platform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: 256-bit black key in blob:platform caam_sm: [0000] d6 36 a9 1b df 26 a2 7fplatform caam_sm: [0008] 1c 8b 99 8b 33 34 5a 92platform caam_sm: [0016] c4 00 dc dc 51 c4 2c f4platform caam_sm: [0024] c3 11 f6 c7 a2 7c c2 baplatform caam_sm: [0032] 7f 6f 4a d1 a7 7f 7b a0platform caam_sm: [0040] 2f cb f4 4a b8 b8 4d 54platform caam_sm: [0048] ae 10 ce 13 02 c5 09 daplatform caam_sm: [0056] ce 88 da 48 10 ee 20 e5platform caam_sm: [0064] 28 bb 0f 76 e4 8a 8e eeplatform caam_sm: [0072] 46 e2 69 6f ca d3 e4 baplatform caam_sm: [0080] 00 00 00 00 00 00 00 00platform caam_sm: [0088] 00 00 00 00 00 00 00 00platform caam_sm: restored 64-bit black key:platform caam_sm: [0000] 58 1c 8d b3 fa 93 6e 2cplatform caam_sm: [0008] f2 ae 66 67 b1 f4 e6 b9platform caam_sm: restored 128-bit black key:platform caam_sm: [0000] 7e 83 f5 8e ed bd bf 4eplatform caam_sm: [0008] 6f 98 a2 68 c3 30 a3 81platform caam_sm: restored 192-bit black key:platform caam_sm: [0000] 73 ba ab 08 93 75 f2 e3platform caam_sm: [0008] 66 73 d2 17 0c a7 f3 08platform caam_sm: [0016] ee 51 4c 4f 16 0a f2 9fplatform caam_sm: [0024] 9e c9 48 38 46 04 11 04platform caam_sm: restored 256-bit black key:platform caam_sm: [0000] da 35 27 8d 68 e2 e8 44platform caam_sm: [0008] 58 3a 7d 32 ea 54 dc 77platform caam_sm: [0016] 48 a1 28 bc a2 71 ad 8dplatform caam_sm: [0024] 6f 9a 59 ba 5c 35 63 56snvs-secvio 20cc000.caam-snvs: can't get snvs clocksnvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure stateusbcore: registered new interface driver usbhidusbhid: USB HID core driverfsl-asrc 2034000.asrc: driver registeredNET: Registered protocol family 26TCP: cubic registeredNET: Registered protocol family 10sit: IPv6 over IPv4 tunneling driverNET: Registered protocol family 17can: controller area network core (rev 20120528 abi 9)NET: Registered protocol family 29can: raw protocol (rev 20120528)can: broadcast manager protocol (rev 20120528 t)can: netlink gateway (rev 20130117) max_hops=1Bluetooth: RFCOMM TTY layer initializedBluetooth: RFCOMM socket layer initializedBluetooth: RFCOMM ver 1.11Bluetooth: BNEP (Ethernet Emulation) ver 1.3Bluetooth: BNEP filters: protocol multicastBluetooth: BNEP socket layer initializedBluetooth: HIDP (Human Interface Emulation) ver 1.2Bluetooth: HIDP socket layer initialized8021q: 802.1Q VLAN Support v1.8Key type dns_resolver registeredcpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)SWBST: disablingusb_otg1_vbus: disablingregulator-dummy: disablingimx mcc test is registered.snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 2016-04-01 08:34:36 UTC (1459499676)ALSA device list: No soundcards found.kjournald starting. Commit interval 5 secondsEXT3-fs (mmcblk1p2): using internal journalEXT3-fs (mmcblk1p2): recovery completeEXT3-fs (mmcblk1p2): mounted filesystem with ordered data modeVFS: Mounted root (ext3 filesystem) on device 179:2.devtmpfs: mountedFreeing unused kernel memory: 392K (809e8000 - 80a4a000)INIT: version 2.88 bootingError opening /dev/fb0: No such file or directoryStarting udevudevd[157]: starting version 182 udevadm settle - timeout of 3 seconds reached, the event queue contains: /sys/devices/soc0/soc.0/2100000.aips-bus/2188000.ethernet/net/eth0 (1225) /sys/devices/soc0/soc.0/2100000.aips-bus/2194000.usdhc/mmc_host/mmc1/mmc1:1234/block/mmcblk1 (1231) /sys/devices/soc0/soc.0/2100000.aips-bus/2194000.usdhc/mmc_host/mmc1/mmc1:1234/block/mmcblk1/mmcblk1p1 (1232) /sys/devices/soc0/soc.0/2100000.aips-bus/2194000.usdhc/mmc_host/mmc1/mmc1:1234/block/mmcblk1/mmcblk1p2 (1233) /sys/devices/virtual/block/loop0 (1313) /sys/devices/virtual/block/loop1 (1314) /sys/devices/virtual/block/loop4 (1317) /sys/devices/virtual/block/loop5 (1318) /sys/devices/virtual/block/loop6 (1319) /sys/devices/virtual/block/loop7 (1320) /sys/devices/virtual/block/ram0 (1321) /sys/devices/virtual/block/ram1 (1322) /sys/devices/virtual/block/ram10 (1323) /sys/devices/virtual/block/ram11 (1324) /sys/devices/virtual/block/ram12 (1325) /sys/devices/virtual/block/ram13 (1326) /sys/devices/virtual/block/ram14 (1327) /sys/devices/virtual/block/ram15 (1328) /sys/devices/virtual/block/ram2 (1329) /sys/devices/virtual/block/ram3 (1330) /sys/devices/virtual/block/ram4 (1331) /sys/devices/virtual/block/ram5 (1332) /sys/devices/virtual/block/ram6 (1333) /sys/devices/virtual/block/ram7 (1334) /sys/devices/virtual/block/ram8 (1335) /sys/devices/virtual/block/ram9 (1336) /sys/devices/virtual/mtd/mtd0/mtdblock0 (1340) /sys/devices/virtual/mtd/mtd1/mtdblock1 (1343) /sys/devices/virtual/mtd/mtd2/mtdblock2 (1346) /sys/devices/virtual/mtd/mtd3/mtdblock3 (1349) /sys/devices/virtual/mtd/mtd4/mtdblock4 (1352) /sys/devices/virtual/mtd/mtd5/mtdblock5 (1355) /sys/devices/virtual/mtd/mtd6/mtdblock6 (1358) /sys/devices/virtual/mtd/mtd7/mtdblock7 (1361) /sys/devices/virtual/net/lo (1363) /sys/devices/virtual/net/sit0 (1364)bootlogd: cannot allocate pseudo tty: No such file or directoryFAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.ALSA: Restoring mixer settings.../usr/sbin/alsactl: load_state:1729: No soundcards found...INIT: Entering runlevel: 5Configuring network interfaces... fec 2188000.ethernet eth0: Freescale FEC PHY driver [Micrel KSZ8081 or KSZ8091] (mii_bus:phy_addr=2188000.ethernet:00, irq=-1)IPv6: ADDRCONF(NETDEV_UP): eth0: link is not readydone.Starting Xserveropen /dev/fb0: No such file or directoryStarting system message bus: Unknown username "xuser" in message bus configuration filedbus.Starting Connection ManagerStarting Dropbear SSH server: dropbear.Starting rpcbind daemon...done.starting statd: doneStarting advanced power management daemon: No APM support in kernel(failed.)NFS daemon support not enabled in kernelStarting syslogd/klogd: done * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon ...done.Starting Telephony daemonStarting Linux NFC daemonStarting OProfileUI serverRunning local boot scripts (/etc/rc.local).Starting tcf-agent: OK Freescale i.MX Release Distro 3.14.52-1.1.0 sbc-lynx /dev/ttymxc0 sbc-lynx login: rootroot@sbc-lynx:~#</pre> [1] <code>bootscript</code> is used to do this task. ===Host setup===As stated previously, XUELK host tools are based on a [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]]. As indicated [[#XUELK microSD Layout|here]], microSD card delivered along with XUELK includes basic version of MVM that is the default option.
Either version you choose, please follow the procedure described [[Managed_Virtual_Machine_(MVM)#Installation_and_configuration|here]] to install the MVM.
It is also worth remembering that access to git repositories is required to download target source code. To enable it, please refer to [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|this page]].
{{ImportantMessage|text=Either version of MVM is installed, it provides the tools required to build [[Building_U-Boot_(XUELK)|U-boot]] and [[Building_Linux_kernel_(XUELK)|Linux kernel]]. It does not include the tools required to run Yocto build system instead.}}
===Target configuration for the development stage (<code>net_nfs</code>)===
During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:
*retrieve binary images (i.e. Linux kernel) via TFTP protocol
*mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]].
In DAVE Embedded Systems development kits, this configuration is generally denoted as <code>net_nfs</code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up. They are detailed [[Booting_Linux_Kernel#Configuration_net_nfs|here]].
For more details about TFTP and NFS servers on host side, please refer to this [[Setting_up_tftp_and_nfs|page]].
===Target configuration for standalone boot===
Please refer to [[Standalone_boot_(XUELK)|this page]].
===How to update root file system on SD card===
RFS update on SD card consists on expanding the new tarball compressed file on SD card ext3 partition.
It is possible, for example, to perform this operation using one of the following process:
* directly on the target
* using a Linux PC (or the XUELK VM)
The ext3 partition (mmcblk0p2) containing the root file system need to be:
* erased
* written with new rfs files
==== Update rfs on target====
* start SBC Lynx via nfs. See how to boot from nfs [[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#Target_configuration_for_the_development_stage_.28net_nfs.29|here]]
* change directory to the ext3 partition into the filesystem: typically <code>/run/media/mmcblk0p2</code>
<pre>
root@sbc-lynx:~# cd /run/media/mmcblk0p2
root@sbc-lynx:/run/media/mmcblk0p2#
</pre>
* delete all previous files
<pre>
root@sbc-lynx:/run/media/mmcblk0p2# rm -r *
</pre>
* extract new rfs files from tarball archive previously copied into nfs directory (the following command assumes that xuelk-1.1.0 rfs have been already copied into VM '''/home/dvdk/lynx/rfs/xuelk/home/root''' nfs directory
<pre>
root@sbc-lynx:/run/media/mmcblk0p2# tar jxvpf /home/dvdk/lynx/rfs/xuelk/home/root/xuelk-1.1.0_lynx-image-gui-sbc-lynx.tar.bz2
</pre>
==== Update rfs on a Linux PC====
* insert the SD card and check its mount point
* change dir to the ext3 SD card partition
* delete previous files and extract new files from tarball archive as described [[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#Update_rfs_on_target|here]]
===Developing the software for the target===
Please refer to [[Developing the software for the target (XUELK)|this page]].
==Physical devices mapping==
Please refer to [[Physical_devices_mapping_(XUELK)|this page]].
==Advanced topics==
===Debugging with Eclipse===
Please refer to [[Debugging with Eclipse (MVM)|this page]].
