• State Resolved
  • Locked Locked
  • Replies 27 replies
  • Subscribers 42 subscribers
  • Views 11783 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Unable to use WL1837MOD with ConnMan

Fabio Emiliani
Intellectual 290 points

Other Parts Discussed in Thread: WL1837MOD, WL1837

Dear TI E2E Community,

I'm trying to setup a WL1837MOD with ConnMan but I've a strange problem. ConnMan doesn't want to interact with the wireless adapter.

Host platform: custom hardware based on i.MX6 processor

Operating system: Linux Yocto (kernel ver 3.14.281.0)

WiLink versions:

- wlcore: PHY firmware version: Rev 8.2.0.0.212
- wlcore: firmware booted (Rev 8.9.0.0.17)

The WL1837 is running, I can connect to a wifi network controlling the chip with ifdown/ifup and using wpa_supplicant. ConnMan is correctly configured, I can list the available wired interface and connect to a wired network.

Below the result of the "./connmanctl technologies" command:

/net/connman/technology/ethernet
  Name = Wired
  Type = ethernet
  Powered = True
  Connected = True
  Tethering = False
/net/connman/technology/gadget
  Name = Gadget
  Type = gadget
  Powered = False
  Connected = False
  Tethering = False

No wireless technology detected.

This is the log of ConnMan related to the wlan0 interface:

root@lam_icu:/# connmand -n
connmand[571]: Connection Manager version 1.28
connmand[571]: wlan0 {create} index 5 type 1 <ETHER>
connmand[571]: wlan0 {update} flags 4099 <UP>
connmand[571]: wlan0 {newlink} index 5 address DE:AD:BE:EF:00:00 mtu 1500
connmand[571]: wlan0 {newlink} index 5 operstate 2 <DOWN>
connmand[571]: Adding interface wlan0 [ wifi ]

Are there any known issues related to the intraction between WL1837MOD and ConnMan? What can be the cause of the problem?

Thanks in advance for your help

EDIT: in attachment a log of connmand launched in debug mode (connmand -n -d)connmand_debug.log

Regards,

Fabio

  • 0
    Guru 11260 points

    Hello Fabio,

    I have had no issues with connman-26/33.
    I assume you have enabled --enable-wifi while building connman ?

    connman doesn’t directly connect to wifi. Can you do the following steps and let me know it works.

    Run the command connmanctl, it will take you to the promp

    connmanctl> enable wifi
    Enabled wifi
    connmanctl> agent on
    Agent registered
    connmanctl> scan wifi
    connmanctl> services
    Testing_AP wifi_78a504234a52_526163656c6f6769635f4150_managed_psk
    XR12-24-6D-5E wifi_78a504234a52_585231322d32342d36442d3545_managed_none
    Scan completed for wifi
    connmanctl> services
    XR12-24-6D-5E wifi_78a504234a52_585231322d32342d36442d3545_managed_none
    wifi_78a504234a52_f09f98a5f09f94abf09f9887_managed_psk
    connmanctl> connect wifi_78a504234a52_526163656c6f6769635f4150_managed_psk
    <This asks for a pwd enter you pwd and the it says connected>


    enable wifi --->> This enable the wifi
    agent on ---->>> Turns on the agent wpa
    scan wifi ---->>> Scans for the wifi
    service ---->>> Lists out the wifi devices
    connect ---->>> Connect to a wifi

    Cheers,
    --Prabhakar Lad

  • 0 in reply to Prabhakar Lad
    TI__Mastermind 35795 points
    Prabhakar , thank you for posting !

    Fabio, let us know if it helps

    Saurabh
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points
    Hi Prabhakar,
    many thanks for your help. I've checked the build option of ConnMan and I confirm that the --enable-wifi is set.

    I've tried the enable wifi command but unfortunatly I've got:

    root@lam_icu:~# connmanctl
    connmanctl> enable wifi
    Error wifi: Method "SetProperty" with signature "sv" on interface "net.connman.Technology" doesn't exist

    connmanctl>

    The "/net/connman/technology/wireless" object path doesn not exists, so the enable fails.

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Guru 11260 points
    Hi Fabio,

    Can you attach the log when your board boots up (dmesg). along with the output of ip link show or ifconfig
    before starting the connman.

    Just to check have installed main.conf in your FS ?

    Cheers,
    --Prabhakar Lad
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points

    Hi Prabhakar,

    in attachment two logs with the info you have requested.

    Regarding the main.conf file I don't have it. I expect to found it under: /etc/connman/main.conf but the etc folder doesn't have a connman subfolder. As you can see in the logs I've just the /var/lib/connman folder. Do you think I need to create a main.conf file?

    Fullscreen 3201.boot_log.txt Download 
    root@lam_icu:~#

U-Boot 2015.041.0-tsu+g303e6a0 (Jun 30 2016 - 14:20:22)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
CPU:   Temperature 47 C
Reset cause: POR
Board: MX6Q-LAM_ICU rev 1
DRAM:  2 GiB
Flag read: 0x00
NAND:  2048 MiB
*** Warning - bad CRC, using default environment

No panel detected: default to HDMI
Display: HDMI (640x480)
In:    serial
Out:   serial
Err:   serial
Starting from Partition A
Normal Boot
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x6000000, size 0x800000
 8388608 bytes read: OK

NAND read: device 0 offset 0x5000000, size 0x100000
 1048576 bytes read: OK
## Booting kernel from Legacy Image at 12000000 ...
   Image Name:   Linux-3.14.281.0-icu+g0b8488d
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4683192 Bytes = 4.5 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 18000000, end 1800c9a7

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.14.281.0-icu+g0b8488d (user@user-VirtualBox) (gcc version 4.9.2 (GCC) ) #1 SMP PREEMPT Tue Jul 5 13:25:20 CEST 2016
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Freescale i.MX6 Quad Board
[    0.000000] cma: CMA: reserved 704 MiB at 52000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] PERCPU: Embedded 7 pages/cpu @ee660000 s7872 r8192 d12608 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 520720
[    0.000000] Kernel command line: console=ttymxc3,115200 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs mtdparts=gpmi-nand:64m(boot),16m(bootenv),16m(dtb),16m(kernel1),416m(rootfs1),16m(dtb2),16m(kernel2),416m(rootfs2),-(log)
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
[    0.000000] Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Memory: 1347736K/2097152K available (5991K kernel code, 309K rwdata, 1924K rodata, 267K init, 392K bss, 749416K reserved, 270336K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0x80000000 - 0xef800000   (1784 MB)
[    0.000000]     pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
[    0.000000]     modules : 0x7f000000 - 0x7fe00000   (  14 MB)
[    0.000000]       .text : 0x80008000 - 0x807c2f6c   (7916 kB)
[    0.000000]       .init : 0x807c3000 - 0x80805ec0   ( 268 kB)
[    0.000000]       .data : 0x80806000 - 0x808535e0   ( 310 kB)
[    0.000000]        .bss : 0x808535ec - 0x808b5700   ( 393 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L310 cache controller enabled
[    0.000000] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1024 kB
[    0.000000] clk: failed to reparent pll4_audio to pll4: -22
[    0.000000] VPU 352M is enabled!
[    0.000000] Switching to timer-based delay loop
[    0.000008] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682ns
[    0.000055] clk: failed to reparent pll4_audio to pll4: -22
[    0.000662] Console: colour dummy device 80x30
[    0.000689] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000)
[    0.000703] pid_max: default: 32768 minimum: 301
[    0.000877] Mount-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000889] Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.008249] CPU: Testing write buffer coherency: ok
[    0.008550] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.008624] Setting up static identity map for 0x105e02c8 - 0x105e0320
[    0.061143] CPU1: Booted secondary processor
[    0.061166] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.081135] CPU2: Booted secondary processor
[    0.081158] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.101126] CPU3: Booted secondary processor
[    0.101148] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.101261] Brought up 4 CPUs
[    0.101289] SMP: Total of 4 processors activated.
[    0.101298] CPU: All CPU(s) started in SVC mode.
[    0.101930] devtmpfs: initialized
[    0.105817] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.106164] pinctrl core: initialized pinctrl subsystem
[    0.106510] regulator-dummy: no parameters
[    0.144456] NET: Registered protocol family 16
[    0.153477] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.154103] CPU identified as i.MX6Q, silicon rev 1.5
[    0.154210] Use WDOG1 as reset source
[    0.164101] syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered
[    0.164429] vdd1p1: 800 <--> 1375 mV at 1100 mV
[    0.164769] vdd3p0: 2800 <--> 3150 mV at 3000 mV
[    0.165149] vdd2p5: 2000 <--> 2750 mV at 2400 mV
[    0.165518] vddarm: 725 <--> 1450 mV at 1150 mV
[    0.170404] vddpu: 725 <--> 1450 mV
[    0.170794] vddsoc: 725 <--> 1450 mV at 1175 mV
[    0.171272] 20c9000.usbphy supply phy-3p0 not found, using dummy regulator
[    0.171617] 20ca000.usbphy supply phy-3p0 not found, using dummy regulator
[    0.172821] syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered
[    0.175719] syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered
[    0.180059] imx6q_csi_mux_init :: platform
[    0.180154] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.180166] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.182713] imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
[    0.198775] bio: create slab <bio-0> at 0
[    0.201114] mxs-dma 110000.dma-apbh: initialized
[    0.280375] wlan-en-regulator: 3300 mV
[    0.280631] usb_h2_vbus: 3300 mV
[    0.281656] SCSI subsystem initialized
[    0.281940] usbcore: registered new interface driver usbfs
[    0.282010] usbcore: registered new interface driver hub
[    0.282135] usbcore: registered new device driver usb
[    0.282375] usbphy_nop1.10 supply vcc not found, using dummy regulator
[    0.284285] i2c i2c-0: IMX I2C adapter registered
[    0.284627] i2c i2c-1: IMX I2C adapter registered
[    0.285777] i2c i2c-2: IMX I2C adapter registered
[    0.285913] Linux video capture interface: v2.00
[    0.285963] pps_core: LinuxPPS API ver. 1 registered
[    0.285972] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.285996] PTP clock support registered
[    0.300446] imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
[    0.320442] imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
[    0.321277] Advanced Linux Sound Architecture Driver Initialized.
[    0.322625] Bluetooth: Core ver 2.18
[    0.322672] NET: Registered protocol family 31
[    0.322681] Bluetooth: HCI device and connection manager initialized
[    0.322701] Bluetooth: HCI socket layer initialized
[    0.322715] Bluetooth: L2CAP socket layer initialized
[    0.322753] Bluetooth: SCO socket layer initialized
[    0.322905] Switched to clocksource mxc_timer1
[    0.333493] NET: Registered protocol family 2
[    0.334364] TCP established hash table entries: 16384 (order: 4, 65536 bytes)
[    0.334522] TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
[    0.334784] TCP: Hash tables configured (established 16384 bind 16384)
[    0.334918] TCP: reno registered
[    0.334936] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[    0.335004] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[    0.335321] NET: Registered protocol family 1
[    0.335826] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.337400] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.338885] bounce pool size: 64 pages
[    0.345152] VFS: Disk quotas dquot_6.5.2
[    0.345434] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.347377] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.347630] NTFS driver 2.1.30 [Flags: R/O].
[    0.347923] ROMFS MTD (C) 2007 Red Hat, Inc.
[    0.348228] fuse init (API version 7.22)
[    0.348700] msgmni has been set to 3512
[    0.351872] io scheduler noop registered
[    0.351885] io scheduler deadline registered
[    0.351928] io scheduler cfq registered (default)
[    0.354227] mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1
[    0.354255] fbcvt: 1920x1200@60: CVT Name - 2.304MA-R
[    0.354376] mxc_sdc_fb fb.13: registered mxc display driver hdmi
[    0.412981] imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
[    0.418260] imx-sdma 20ec000.sdma: no iram assigned, using external mem
[    0.418812] imx-sdma 20ec000.sdma: no event needs to be remapped
[    0.419178] imx-sdma 20ec000.sdma: loaded firmware 3.1
[    0.422302] imx-sdma 20ec000.sdma: initialized
[    0.422764] Serial: IMX driver
[    0.423307] 21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 59, base_baud = 5000000) is a IMX
[    0.423752] 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60, base_baud = 5000000) is a IMX
[    0.424160] 21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 61, base_baud = 5000000) is a IMX
[    1.202601] console [ttymxc3] enabled
[    1.206709] 21f4000.serial: ttymxc4 at MMIO 0x21f4000 (irq = 62, base_baud = 5000000) is a IMX
[    1.215628] serial: Freescale lpuart driver
[    1.221057] imx sema4 driver is registered.
[    1.233290] brd: module loaded
[    1.240566] loop: module loaded
[    1.252928] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0x48
[    1.259296] nand: Micron MT29F16G08ABABAWP
[    1.263419] nand: 2048MiB, SLC, page size: 4096, OOB size: 224
[    1.269787] gpmi-nand 112000.gpmi-nand: enable the asynchronous EDO mode 4
[    1.277059] Bad block table found at page 524160, version 0x01
[    1.283154] Bad block table found at page 524032, version 0x01
[    1.289380] 9 cmdlinepart partitions found on MTD device gpmi-nand
[    1.295590] Creating 9 MTD partitions on "gpmi-nand":
[    1.300657] 0x000000000000-0x000004000000 : "boot"
[    1.306556] 0x000004000000-0x000005000000 : "bootenv"
[    1.312549] 0x000005000000-0x000006000000 : "dtb"
[    1.318246] 0x000006000000-0x000007000000 : "kernel1"
[    1.324264] 0x000007000000-0x000021000000 : "rootfs1"
[    1.330386] 0x000021000000-0x000022000000 : "dtb2"
[    1.336182] 0x000022000000-0x000023000000 : "kernel2"
[    1.342200] 0x000023000000-0x00003d000000 : "rootfs2"
[    1.348406] 0x00003d000000-0x000080000000 : "log"
[    1.354384] gpmi-nand 112000.gpmi-nand: driver registered.
[    1.362033] at25_probe :: at25 probe
[    1.365647] at25_probe :: Platform data not present -> using dev tree
[    1.372107] at25_probe :: gpio wren_n = 62
[    1.412997] at25_probe :: Sysfs created
[    1.416853] at25 spi1.0: 32 KByte at25 eeprom, pagesize 64
[    1.422347] at25_probe :: Probe completed created
[    1.427090] spi_imx 200c000.ecspi: probed
[    1.432488] spi_imx 2010000.ecspi: probed
[    1.437543] usbcore: registered new interface driver cdc_ether
[    1.443457] usbcore: registered new interface driver net1080
[    1.449176] usbcore: registered new interface driver cdc_subset
[    1.455207] usbcore: registered new interface driver cdc_ncm
[    1.460878] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.467432] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.473966] usbcore: registered new interface driver cdc_acm
[    1.479637] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    1.487736] usbcore: registered new interface driver usb-storage
[    1.494728] 2184800.usbmisc supply vbus-wakeup not found, using dummy regulator
[    1.502866] 2184000.usb supply vbus not found, using dummy regulator
[    1.513538] 2184200.usb supply vbus not found, using dummy regulator
[    1.522932] ci_hdrc ci_hdrc.1: EHCI Host Controller
[    1.527846] ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1
[    1.552933] ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
[    1.559130] hub 1-0:1.0: USB hub found
[    1.562964] hub 1-0:1.0: 1 port detected
[    1.567679] 2184400.usb supply vbus not found, using dummy regulator
[    1.595440] ci_hdrc ci_hdrc.2: doesn't support gadget
[    1.600511] ci_hdrc ci_hdrc.2: EHCI Host Controller
[    1.605437] ci_hdrc ci_hdrc.2: new USB bus registered, assigned bus number 2
[    1.632923] ci_hdrc ci_hdrc.2: USB 2.0 started, EHCI 1.00
[    1.639038] hub 2-0:1.0: USB hub found
[    1.642834] hub 2-0:1.0: 1 port detected
[    1.648438] snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
[    1.656852] i2c /dev entries driver
[    1.661170] In MVC:camera_init
[    1.664660] init_camera_struct :: ipu_id = 0, csi_id = 0, mclk_source = 0
[    1.671646]    Video device registered: Mxc Camera #0
[    1.676800] init_camera_struct :: ipu_id = 1, csi_id = 1, mclk_source = 0
[    1.683787]    Video device registered: Mxc Camera #1
[    1.688968] ov10635 0-0001: using csi 0
[    1.692817] ov10635 0-0001: requesting csi_mclk
[    1.697391] ov10635 0-0001: csi_mclk -1073616512
[    1.702029] In MVC: mxc_v4l2_master_attach
[    1.706146]    slave.name = ov10635-0
[    1.709817]    master.name = mxc_v4l2_cap0
[    1.713939] ov10635 0-0001: probed on csi 0
[    1.718176] ov10635 0-0002: using csi 1
[    1.722024] ov10635 0-0002: requesting csi_mclk
[    1.726588] ov10635 0-0002: csi_mclk -1073616512
[    1.731223] In MVC: mxc_v4l2_master_attach
[    1.735339]    slave.name = ov10635-1
[    1.739010]    master.name = mxc_v4l2_cap1
[    1.743251] ov10635 0-0002: probed on csi 1
[    1.748093] mxc_v4l2_output v4l2_out.22: V4L2 device registered as video16
[    1.755151] mxc_v4l2_output v4l2_out.22: V4L2 device registered as video17
[    1.762618] imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
[    1.770951] Bluetooth: HCI UART driver ver 2.2
[    1.775422] Bluetooth: HCI H4 protocol initialized
[    1.780549] sdhci: Secure Digital Host Controller Interface driver
[    1.786753] sdhci: Copyright(c) Pierre Ossman
[    1.791120] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.798497] mmc1: no vqmmc regulator found
[    1.843052] mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
[    1.851815] mmc2: no vqmmc regulator found
[    1.855720] sdhci-esdhc-imx 2194000.usdhc: card claims to support voltages below defined range
[    1.864567] mmc2: no vmmc regulator found
[    1.872361] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
[    1.879380] mmc1: new high speed SDIO card at address 0001
[    1.912920] mmc2: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
[    1.920838] Galcore version 5.0.11.33433
[    2.143142] usb 2-1: new high-speed USB device number 2 using ci_hdrc
[    2.305204] hub 2-1:1.0: USB hub found
[    2.309109] hub 2-1:1.0: 5 ports detected
[    2.488563] mmc2: BKOPS_EN bit is not set
[    2.499877] mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
[    2.506545] mmc2: new high speed DDR MMC card at address 0001
[    2.506984] mmcblk2: mmc2:0001 MMC64G 59.5 GiB
[    2.507109] mmcblk2boot0: mmc2:0001 MMC64G partition 1 16.0 MiB
[    2.507227] mmcblk2boot1: mmc2:0001 MMC64G partition 2 16.0 MiB
[    2.507339] mmcblk2rpmb: mmc2:0001 MMC64G partition 3 128 KiB
[    2.509118]  mmcblk2: p1 p2 p3 p4
[    2.512538]  mmcblk2boot1: unknown partition table
[    2.514976]  mmcblk2boot0: unknown partition table
[    2.549130] mxc_vpu 2040000.vpu: VPU initialized
[    2.593236] usb 2-1.1: new high-speed USB device number 3 using ci_hdrc
[    2.724832] cdc_acm 2-1.1:1.0: This device cannot do calls on its own. It is not a modem.
[    2.759139] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[    2.765837] cdc_acm 2-1.1:1.2: This device cannot do calls on its own. It is not a modem.
[    2.797182] cdc_acm 2-1.1:1.2: ttyACM1: USB ACM device
[    2.803876] caam 2100000.caam: Instantiated RNG4 SH0
[    3.043228] usb 2-1.3: new full-speed USB device number 4 using ci_hdrc
[    3.055783] caam 2100000.caam: Instantiated RNG4 SH1
[    3.060767] caam 2100000.caam: device ID = 0x0a160100 (Era 4)
[    3.066538] caam 2100000.caam: job rings = 2, qi = 0
[    3.076998] caam algorithms registered in /proc/crypto
[    3.086024] caam_jr 2101000.jr0: registering rng-caam
[    3.091864] platform caam_sm: blkkey_ex: 4 keystore units available
[    3.098382] platform caam_sm: 64-bit clear key:
[    3.102955] platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
[    3.108763] platform caam_sm: 64-bit black key:
[    3.113331] platform caam_sm: [0000] db d3 45 95 00 b4 da cd
[    3.119007] platform caam_sm: [0008] 78 e4 ba 30 96 48 48 b2
[    3.124693] platform caam_sm: 128-bit clear key:
[    3.129327] platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
[    3.135020] platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
[    3.140692] platform caam_sm: 128-bit black key:
[    3.145375] platform caam_sm: [0000] 52 29 d3 1a 2b f6 3c 1b
[    3.151101] platform caam_sm: [0008] d9 b7 42 2b ba e9 04 d1
[    3.156836] platform caam_sm: 192-bit clear key:
[    3.161490] platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
[    3.167201] platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
[    3.172884] platform caam_sm: [0016] 10 11 12 13 14 15 16 17
[    3.178574] platform caam_sm: 192-bit black key:
[    3.183259] platform caam_sm: [0000] 0b 5f 58 66 51 78 b3 92
[    3.189000] platform caam_sm: [0008] c4 d2 c8 35 ab cb 7c 79
[    3.194736] platform caam_sm: [0016] 21 98 46 88 4a e0 50 1e
[    3.200475] platform caam_sm: [0024] 80 a8 c2 c0 e9 e7 62 54
[    3.206207] platform caam_sm: 256-bit clear key:
[    3.210897] platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
[    3.217090] platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
[    3.228929] cdc_acm 2-1.3:1.0: ttyACM2: USB ACM device
[    3.234139] platform caam_sm: [0016] 10 11 12 13 14 15 16 17
[    3.239816] platform caam_sm: [0024] 18 19 1a 1b 1c 1d 1e 1f
[    3.245538] platform caam_sm: 256-bit black key:
[    3.250231] platform caam_sm: [0000] 2a d3 70 e6 d1 03 25 b2
[    3.256626] platform caam_sm: [0008] 01 20 41 15 d0 55 56 fc
[    3.262375] platform caam_sm: [0016] 76 29 fd 24 fb 96 64 0e
[    3.268101] platform caam_sm: [0024] 38 06 97 b1 d0 03 1b ae
[    3.273805] platform caam_sm: 64-bit unwritten blob:
[    3.278787] platform caam_sm: [0000] 00 00 00 00 00 00 00 00
[    3.284522] platform caam_sm: [0008] 00 00 00 00 00 00 00 00
[    3.290236] platform caam_sm: [0016] 00 00 00 00 00 00 00 00
[    3.295927] platform caam_sm: [0024] 00 00 00 00 00 00 00 00
[    3.301623] platform caam_sm: [0032] 00 00 00 00 00 00 00 00
[    3.307311] platform caam_sm: [0040] 00 00 00 00 00 00 00 00
[    3.313001] platform caam_sm: [0048] 00 00 00 00 00 00 00 00
[    3.318683] platform caam_sm: [0056] 00 00 00 00 00 00 00 00
[    3.324370] platform caam_sm: [0064] 00 00 00 00 00 00 00 00
[    3.330044] platform caam_sm: [0072] 00 00 00 00 00 00 00 00
[    3.335738] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.341413] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.347131] platform caam_sm: 128-bit unwritten blob:
[    3.352229] usb 2-1.5: new high-speed USB device number 5 using ci_hdrc
[    3.358918] platform caam_sm: [0000] 00 00 00 00 00 00 00 00
[    3.364657] platform caam_sm: [0008] 00 00 00 00 00 00 00 00
[    3.370365] platform caam_sm: [0016] 00 00 00 00 00 00 00 00
[    3.376068] platform caam_sm: [0024] 00 00 00 00 00 00 00 00
[    3.381747] platform caam_sm: [0032] 00 00 00 00 00 00 00 00
[    3.387482] platform caam_sm: [0040] 00 00 00 00 00 00 00 00
[    3.393208] platform caam_sm: [0048] 00 00 00 00 00 00 00 00
[    3.398884] platform caam_sm: [0056] 00 00 00 00 00 00 00 00
[    3.404591] platform caam_sm: [0064] 00 00 00 00 00 00 00 00
[    3.410290] platform caam_sm: [0072] 00 00 00 00 00 00 00 00
[    3.415983] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.421666] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.427349] platform caam_sm: 196-bit unwritten blob:
[    3.432416] platform caam_sm: [0000] 00 00 00 00 00 00 00 00
[    3.438103] platform caam_sm: [0008] 00 00 00 00 00 00 00 00
[    3.443789] platform caam_sm: [0016] 00 00 00 00 00 00 00 00
[    3.449471] platform caam_sm: [0024] 00 00 00 00 00 00 00 00
[    3.455189] platform caam_sm: [0032] 00 00 00 00 00 00 00 00
[    3.460910] platform caam_sm: [0040] 00 00 00 00 00 00 00 00
[    3.466646] platform caam_sm: [0048] 00 00 00 00 00 00 00 00
[    3.472343] platform caam_sm: [0056] 00 00 00 00 00 00 00 00
[    3.478050] platform caam_sm: [0064] 00 00 00 00 00 00 00 00
[    3.483744] platform caam_sm: [0072] 00 00 00 00 00 00 00 00
[    3.489426] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.495146] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.500875] platform caam_sm: 256-bit unwritten blob:
[    3.506005] platform caam_sm: [0000] 00 00 00 00 00 00 00 00
[    3.511740] platform caam_sm: [0008] 00 00 00 00 00 00 00 00
[    3.517478] platform caam_sm: [0016] 00 00 00 00 00 00 00 00
[    3.523587] platform caam_sm: [0024] 00 00 00 00 00 00 00 00
[    3.529589] platform caam_sm: [0032] 00 00 00 00 00 00 00 00
[    3.535410] platform caam_sm: [0040] 00 00 00 00 00 00 00 00
[    3.541087] platform caam_sm: [0048] 00 00 00 00 00 00 00 00
[    3.546797] platform caam_sm: [0056] 00 00 00 00 00 00 00 00
[    3.552472] platform caam_sm: [0064] 00 00 00 00 00 00 00 00
[    3.558178] platform caam_sm: [0072] 00 00 00 00 00 00 00 00
[    3.563867] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.569548] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.575461] platform caam_sm: 64-bit black key in blob:
[    3.580705] platform caam_sm: [0000] a8 e9 de 86 33 ab f7 58
[    3.586395] platform caam_sm: [0008] 6e e2 ab 9c e0 12 40 54
[    3.592086] platform caam_sm: [0016] fa 9b 85 62 1c af 1b 0f
[    3.597834] platform caam_sm: [0024] 53 3d 98 f3 0d 67 eb 48
[    3.603527] platform caam_sm: [0032] 73 ae 2b e6 b3 7b 3f 98
[    3.609202] platform caam_sm: [0040] 28 ad 85 fb 20 e0 84 ee
[    3.614889] platform caam_sm: [0048] 3c 99 d1 a8 f2 97 f8 fa
[    3.620563] platform caam_sm: [0056] 00 00 00 00 00 00 00 00
[    3.626249] platform caam_sm: [0064] 00 00 00 00 00 00 00 00
[    3.631923] platform caam_sm: [0072] 00 00 00 00 00 00 00 00
[    3.637609] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.643295] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.648965] platform caam_sm: 128-bit black key in blob:
[    3.654346] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    3.660841] platform caam_sm: [0000] 0a 13 6e 83 3d 38 81 3d
[    3.666598] platform caam_sm: [0008] 49 6a 29 3b 65 06 3a 6b
[    3.672275] platform caam_sm: [0016] c1 7f b4 87 ed 5d 1e 45
[    3.677982] platform caam_sm: [0024] 5e 28 5e 44 e5 4c 12 68
[    3.683671] platform caam_sm: [0032] 7d 93 80 e4 e3 b8 56 77
[    3.689352] platform caam_sm: [0040] 28 94 1e be 9d ac c7 59
[    3.695043] platform caam_sm: [0048] fb be 8d 9e c3 b9 bc 41
[    3.700718] platform caam_sm: [0056] 01 3b 94 cb 46 84 2c 11
[    3.706404] platform caam_sm: [0064] 00 00 00 00 00 00 00 00
[    3.712078] platform caam_sm: [0072] 00 00 00 00 00 00 00 00
[    3.717763] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.723508] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.729181] platform caam_sm: 192-bit black key in blob:
[    3.734525] platform caam_sm: [0000] ed 40 38 3b a3 55 f6 6e
[    3.740199] platform caam_sm: [0008] 84 ab 9c bf d1 95 d4 12
[    3.745886] platform caam_sm: [0016] c1 12 99 56 30 fc 72 5c
[    3.751560] platform caam_sm: [0024] 92 66 02 9a fb ac 82 d0
[    3.757246] platform caam_sm: [0032] 59 57 4e 9b 05 5a e8 3d
[    3.762940] platform caam_sm: [0040] 83 a9 7f c2 51 88 97 a2
[    3.768614] platform caam_sm: [0048] d5 ad 8b 32 db 0b 90 31
[    3.774300] platform caam_sm: [0056] a1 7e 6e 69 c9 bb 5a 99
[    3.779975] platform caam_sm: [0064] ee 65 a3 92 93 47 4b 42
[    3.785723] platform caam_sm: [0072] 00 00 00 00 00 00 00 00
[    3.791442] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.797158] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.802837] platform caam_sm: 256-bit black key in blob:
[    3.808179] platform caam_sm: [0000] 74 e7 92 3f 60 5e 1f a8
[    3.813903] platform caam_sm: [0008] 19 cc 99 90 bb cd 31 bf
[    3.819627] platform caam_sm: [0016] 1b d2 58 55 72 96 62 ca
[    3.825362] platform caam_sm: [0024] 98 50 7b 7d a4 ba 42 ec
[    3.831100] platform caam_sm: [0032] b5 4e 73 c0 f9 a1 c0 c7
[    3.836835] platform caam_sm: [0040] bc 83 ad 7e 39 eb a1 44
[    3.842922] platform caam_sm: [0048] 70 36 6c 55 08 bd 21 d0
[    3.848764] hub 1-1:1.0: USB hub found
[    3.852565] platform caam_sm: [0056] c4 6b ac 08 92 7b b6 b6
[    3.858292] hub 1-1:1.0: 5 ports detected
[    3.862348] platform caam_sm: [0064] ba f0 e6 88 a9 8e 87 bc
[    3.868171] platform caam_sm: [0072] fe 27 1e a4 10 ac e1 9f
[    3.873915] platform caam_sm: [0080] 00 00 00 00 00 00 00 00
[    3.879934] platform caam_sm: [0088] 00 00 00 00 00 00 00 00
[    3.886011] platform caam_sm: restored 64-bit black key:
[    3.891531] platform caam_sm: [0000] 00 c7 f8 fd 84 ca d8 f4
[    3.897230] platform caam_sm: [0008] 83 7a 24 4f 39 f0 f0 7f
[    3.902916] platform caam_sm: restored 128-bit black key:
[    3.908351] platform caam_sm: [0000] 52 29 d3 1a 2b f6 3c 1b
[    3.914040] platform caam_sm: [0008] d9 b7 42 2b ba e9 04 d1
[    3.919717] platform caam_sm: restored 192-bit black key:
[    3.925147] platform caam_sm: [0000] 0b 5f 58 66 51 78 b3 92
[    3.930822] platform caam_sm: [0008] c4 d2 c8 35 ab cb 7c 79
[    3.936509] platform caam_sm: [0016] 9e 7f 62 f5 72 31 e2 8c
[    3.942184] platform caam_sm: [0024] fe bd c0 8b 15 96 86 83
[    3.947866] platform caam_sm: restored 256-bit black key:
[    3.953293] platform caam_sm: [0000] 2a d3 70 e6 d1 03 25 b2
[    3.958967] platform caam_sm: [0008] 01 20 41 15 d0 55 56 fc
[    3.964653] platform caam_sm: [0016] 76 29 fd 24 fb 96 64 0e
[    3.970335] platform caam_sm: [0024] 38 06 97 b1 d0 03 1b ae
[    3.976289] snvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure state
[    3.984898] usbcore: registered new interface driver usbhid
[    3.990529] usbhid: USB HID core driver
[    3.996760] fsl-asrc 2034000.asrc: driver registered
[    4.007887] [AB] connecting 2 port with 6 port
[    4.014094] imx-bt sound.18: hifi <-> 2030000.ssi mapping ok
[    4.021505] imx_fda801b_probe :: get clock 393216000
[    4.028775] imx-fda801b sound.15: st,fda801 <-> 2024000.esai mapping ok
[    4.035439] imx_fda801b_late_probe :: setting dai with mclk = 393216000
[    4.042721] fda801b_set_dai_fmt :: fda801 is not i2c cmd ready... set IB14 now!
[    4.057682] tlv320aic23-codec 2-001b: codec clk_frequency = 12000000
[    4.069470] imx-tlv320 sound.16: tlv320aic23-hifi <-> 2028000.ssi mapping ok
[    4.076580] imx-tlv320 sound.16: ASoC: no source widget found for Mic Jack
[    4.083485] imx-tlv320 sound.16: ASoC: Failed to add route Mic Jack -> direct -> MICIN
[    4.091417] imx-tlv320 sound.16: ASoC: no sink widget found for Headphone Jack
[    4.098749] imx-tlv320 sound.16: ASoC: Failed to add route LHPOUT -> direct -> Headphone Jack
[    4.107375] imx-tlv320 sound.16: ASoC: no sink widget found for Headphone Jack
[    4.114673] imx-tlv320 sound.16: ASoC: Failed to add route RHPOUT -> direct -> Headphone Jack
[    4.125623] tlv320aic23-codec 2-001a: codec clk_frequency = 12000000
[    4.132014] imx-tlv320 sound.17: ASoC: Failed to create card debugfs directory
[    4.143128] fsl-ssi-dai 202c000.ssi: ASoC: Failed to create platform debugfs directory
[    4.152778] imx-tlv320 sound.17: tlv320aic23-hifi <-> 202c000.ssi mapping ok
[    4.159938] imx-tlv320 sound.17: ASoC: no source widget found for Mic Jack
[    4.166885] imx-tlv320 sound.17: ASoC: Failed to add route Mic Jack -> direct -> MICIN
[    4.174850] imx-tlv320 sound.17: ASoC: no sink widget found for Headphone Jack
[    4.182095] imx-tlv320 sound.17: ASoC: Failed to add route LHPOUT -> direct -> Headphone Jack
[    4.190651] imx-tlv320 sound.17: ASoC: no sink widget found for Headphone Jack
[    4.197899] imx-tlv320 sound.17: ASoC: Failed to add route RHPOUT -> direct -> Headphone Jack
[    4.208966] NET: Registered protocol family 26
[    4.213583] TCP: cubic registered
[    4.217418] NET: Registered protocol family 10
[    4.222634] sit: IPv6 over IPv4 tunneling driver
[    4.227620] usb 1-1.5: new high-speed USB device number 4 using ci_hdrc
[    4.234759] NET: Registered protocol family 17
[    4.239231] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    4.245241] Bluetooth: HIDP socket layer initialized
[    4.250255] 8021q: 802.1Q VLAN Support v1.8
[    4.254737] remove 396MHz OPP for VPU running at 352MHz!
[    4.260567] increase SOC/PU voltage for VPU352MHz
[    4.266983] regulator-dummy: disabling
[    4.271090] UBI: attaching mtd4 to ubi0
[    4.589242] random: nonblocking pool is initialized
[    4.629019] UBI: scanning is finished
[    4.637055] UBI: attached mtd4 (name "rootfs1", size 416 MiB) to ubi0
[    4.643548] UBI: PEB size: 524288 bytes (512 KiB), LEB size: 516096 bytes
[    4.650346] UBI: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
[    4.657067] UBI: VID header offset: 4096 (aligned 4096), data offset: 8192
[    4.663962] UBI: good PEBs: 832, bad PEBs: 0, corrupted PEBs: 0
[    4.669890] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
[    4.677079] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 611919292
[    4.686154] UBI: available PEBs: 0, total reserved PEBs: 832, PEBs reserved for bad PEB handling: 80
[    4.695350] UBI: background thread "ubi_bgt0d" started, PID 152
[    4.695522] using random self ethernet address
[    4.695530] using random host ethernet address
[    4.696091] usb0: HOST MAC f6:00:80:44:fa:9a
[    4.696168] usb0: MAC 96:a9:f1:7e:22:e3
[    4.696192] g_cdc gadget: Composite Gadget, version: 1.0
[    4.696196] g_cdc gadget: g_cdc ready
[    4.727627] snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:03 UTC (3)
[    4.746200] ALSA device list:
[    4.749203]   #0: imx-bt
[    4.751744]   #1: fda801b-audio
[    4.754917]   #2: imx-tlv320
[    4.757805]   #3: imx-tlv320
[    4.783116] usb 1-1.1: new high-speed USB device number 5 using ci_hdrc
[    4.815538] UBIFS: recovery needed
[    4.874435] UBIFS: recovery deferred
[    4.878120] UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode
[    4.885020] UBIFS: LEB size: 516096 bytes (504 KiB), min./max. I/O unit sizes: 4096 bytes/4096 bytes
[    4.894199] UBIFS: FS size: 380878848 bytes (363 MiB, 738 LEBs), journal size 19095552 bytes (18 MiB, 37 LEBs)
[    4.904249] UBIFS: reserved for root: 4952683 bytes (4836 KiB)
[    4.910103] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 9802ACCE-C6EF-4B16-ABD6-42FC59E7195C, small LPT model
[    4.921407] VFS: Mounted root (ubifs filesystem) readonly on device 0:13.
[    4.929193] devtmpfs: mounted
[    4.932732] Freeing unused kernel memory: 264K (807c3000 - 80805000)
INIT: version 2.88 booting
Splash Booting
using "DejaVu Sans Mono-16", pixelsize=16.67 file=/usr/share/fonts/truetype/DejaVuSansMono.ttf
Starting udev
[    6.109681] udevd[185]: starting version 182
[    6.331966] Loading modules backported from Linux version v4.3-0-g6a13feb
[    6.339489] Backport generated by backports.git v4.3-1-0-g2ba8fbc
[    6.443107] UBIFS: completing deferred recovery
[    6.596126] UBIFS: background thread "ubifs_bgt0_0" started, PID 255
[    6.611873] UBIFS: deferred recovery completed
bootlogd: cannot allocate pseudo tty: No such file or directory
[    6.715244] asix 1-1.1:1.0 eth0: register 'asix' at usb-ci_hdrc.1-1.1, ASIX AX88772B USB 2.0 Ethernet, 00:90:9a:9d:ac:b2
[    6.726540] usbcore: registered new interface driver asix
[    7.091351] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[    7.103679] wlcore: loaded
ALSA: Restoring mixer settings...
Mon Sep 26 13:08:44 UTC 2016
INIT: Entering runlevel: 5
Configuring network interfaces... Successfully initialized wpa_supplicant
rfkill: Cannot open RFKILL control device
[    7.974671] wlcore: PHY firmware version: Rev 8.2.0.0.212
[    8.026864] wlcore: firmware booted (Rev 8.9.0.0.17)
[    8.043458] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    8.995395] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
done.
Starting system message bus: Unknown username "xuser" in message bus configuration file
dbus.
UIM SYSFS Node Not Found
Starting Connection Manager
Starting OpenBSD Secure Shell server: sshd
done.
Starting ntpd: done
Starting syslogd/klogd: done
Starting internet superserver: xinetd.
Starting Telephony daemon
Mount MMC
[   10.326180] EXT4-fs (mmcblk2p1): recovery complete
[   10.330995] EXT4-fs (mmcblk2p1): mounted filesystem with ordered data mode. Opts: (null)
[   10.487834] EXT4-fs (mmcblk2p2): recovery complete
[   10.494291] EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)
[   10.596773] EXT4-fs (mmcblk2p3): recovery complete
[   10.601583] EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode. Opts: (null)
[   10.701269] EXT4-fs (mmcblk2p4): recovery complete
[   10.706163] EXT4-fs (mmcblk2p4): mounted filesystem with ordered data mode. Opts: (null)
[   10.708749] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Configure AUDIO Input
Configure FB1
open '/dev/fb1'
enable global alpha blending
key = 0x0
Configure FB
[   10.873957] Reconfiguring framebuffer
[   10.877643] virtfb_map_video_memory - fbi->fix.smem_len = 12288000 - fbi->var.yres_virtual = 2560 - fbi->fix.line_length = 4800allocated fb @ paddr=0x5B700000, size=12288000.
[   10.963930] Reconfiguring framebuffer
[   10.967603] virtfb_map_video_memory - fbi->fix.smem_len = 7372800 - fbi->var.yres_virtual = 1536 - fbi->fix.line_length = 4800allocated fb @ paddr=0x5C300000, size=7372800.
[   11.018543] Reconfiguring framebuffer
[   11.022234] virtfb_map_video_memory - fbi->fix.smem_len = 18432000 - fbi->var.yres_virtual = 3840 - fbi->fix.line_length = 4800
[   11.073441] usb 2-1.2: new high-speed USB device number 6 using ci_hdrc
[   11.109289] allocated fb @ paddr=0x5CB00000, size=18432000.
[   11.129642] Reconfiguring framebuffer
[   11.133343] virtfb_map_video_memory - fbi->fix.smem_len = 3840000 - fbi->var.yres_virtual = 1600 - fbi->fix.line_length = 2400allocated fb @ paddr=0x5DD00000, size=3840000.
[   11.173305] Reconfiguring framebuffer
[   11.176974] virtfb_map_video_memory - fbi->fix.smem_len = 18432000 - fbi->var.yres_virtual = 3840 - fbi->fix.line_length = 4800allocated fb @ paddr=0x5E100000, size=18432000.
[   11.279629] Reconfiguring framebuffer
[   11.283325] virtfb_map_video_memory - fbi->fix.smem_len = 5242880 - fbi->var.yres_virtual = 1280 - fbi->fix.line_length = 4096allocated fb @ paddr=0x5F300000, size=5242880.
[   11.330566] Virtual Cam major number = 245
[   11.335092] Virtual Camera Driver Module loaded
[   11.341624] Reconfiguring framebuffer
[   11.372868] allocated fb @ paddr=0x5F800000, size=7077888.
[   11.383989] GPU Frame buffer index: 0 addess: 0x5F800000
[   11.389306] GPU Frame buffer index: 1 addess: 0x5FA40000
[   11.394826] GPU Frame buffer index: 2 addess: 0x5FC80000
Configure NTP
ln: /usr/lib/libdns_sd.so: File exists
Application Start
*** ICU Start ***
Set touch for ICU app
mount: special device /dev/sda does not exist
umount: /media/touch: not mounted
*** Set lowmem for kernel ***
*** Set custom frame buffer ***
[   11.585614] Reconfiguring framebuffer
[   11.676782] virtfb_map_video_memory - fbi->fix.smem_len = 23040000 - fbi->var.yres_virtual = 4800 - fbi->fix.line_length = 4800allocated fb @ paddr=0x61100000, size=23040000.
[   11.716853] Reconfiguring framebuffer
[   11.765459] virtfb_map_video_memory - fbi->fix.smem_len = 12288000 - fbi->var.yres_virtual = 2560 - fbi->fix.line_length = 4800allocated fb @ paddr=0x5AE00000, size=12288000.
[   11.798092] Reconfiguring framebuffer
[   11.804951] Reconfiguring framebuffer
[   11.811606] Reconfiguring framebuffer
[   11.818334] Reconfiguring framebuffer
[   11.851052] virtfb_map_video_memory - fbi->fix.smem_len = 7864320 - fbi->var.yres_virtual = 1920 - fbi->fix.line_length = 4096allocated fb @ paddr=0x5BA00000, size=7864320.
Starting Apple Darwin Multicast DNS / DNS Service Discovery daemon: mdnsd.

Poky (Yocto Project Reference Distro) 1.8 /dev/ttymxc3

lam_icu login: [   12.714254] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   12.722298] asix 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
[   15.441723] usb 2-1.2: USB disconnect, device number 6
[   18.233100] usb 2-1.2: new high-speed USB device number 7 using ci_hdrc
[   18.368308] cdc_ether 2-1.2:1.0 eth1: register 'cdc_ether' at usb-ci_hdrc.2-1.2, CDC Ethernet Device, 00:00:00:01:02:03
[   18.382862] cdc_acm 2-1.2:1.2: This device cannot do calls on its own. It is not a modem.
[   18.411476] cdc_acm 2-1.2:1.2: ttyACM3: USB ACM device
[   18.418213] cdc_acm 2-1.2:1.4: This device cannot do calls on its own. It is not a modem.
[   18.446094] cdc_acm 2-1.2:1.4: ttyACM4: USB ACM device
[   18.453117] cdc_acm 2-1.2:1.6: This device cannot do calls on its own. It is not a modem.
[   18.481173] cdc_acm 2-1.2:1.6: ttyACM5: USB ACM device
    Fullscreen misc.txt Download 
    // -------------//
// ip link show //
// -------------//
root@lam_icu:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0
3: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 1e:21:c2:e3:98:ad brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:90:9a:9d:ac:b2 brd ff:ff:ff:ff:ff:ff
5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 70:b3:d5:e7:ae:3e brd ff:ff:ff:ff:ff:ff
6: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:00:00:01:02:03 brd ff:ff:ff:ff:ff:ff

// ----------------//
// ifconfig output //
// ----------------//
root@lam_icu:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:90:9A:9D:AC:B2
          inet addr:10.0.30.114  Bcast:10.0.255.255  Mask:255.255.0.0
          inet6 addr: fe80::290:9aff:fe9d:acb2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:344 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:34490 (33.6 KiB)  TX bytes:5236 (5.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:256 errors:0 dropped:0 overruns:0 frame:0
          TX packets:256 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:20736 (20.2 KiB)  TX bytes:20736 (20.2 KiB)

// -------------------------- //
// ifup/ifdown configuration  //
// -------------------------- //
root@lam_icu:~# cat /etc/network/interfaces
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

# The loopback interface
auto lo
iface lo inet loopback

# Wireless interfaces
auto wlan0
iface wlan0 inet dhcp
        wireless_mode managed
        wireless_essid any
        wpa-driver wext
        wpa-conf /etc/wpa_supplicant.conf


# Wired or wireless interfaces
auto eth0
#iface eth0 inet dhcp
iface eth0 inet static
    address 10.0.30.114
    netmask 255.255.0.0
    gateway 10.0.0.254

#auto eth1
iface eth1 inet dhcp

// --------------------------- //
// ConnMan configuration files //
// --------------------------- //
root@lam_icu:/var/lib/connman# ls
ethernet_000000010203_cable  settings
ethernet_00909a9dacb2_cable
root@lam_icu:/var/lib/connman# ls -la
drwxr-xr-x    4 root     root           408 Sep 26 13:08 .
drwxr-xr-x    9 root     root           608 Sep 23 12:56 ..
drwx------    2 root     root           296 Sep 26  2016 ethernet_000000010203_cable
drwx------    2 root     root           296 Sep 26 13:08 ethernet_00909a9dacb2_cable
-rw-------    1 root     root           103 Sep 26 13:08 settings
root@lam_icu:/var/lib/connman# cat settings
[global]
OfflineMode=false

[Gadget]
Enable=false
Tethering=false

[Wired]
Enable=true
Tethering=false

  • 0 in reply to Fabio Emiliani
    Guru 11260 points
    Hello,

    1: Have you enabled the following while building wpa_supplicant ?

    CONFIG_DRIVER_NL80211
    CONFIG_CTRL_IFACE_DBUS_NEW
    CONFIG_CTRL_IFACE_DBUS_INTRO
    CONFIG_CTRL_IFACE

    2: Do you have wpa_supplicant.conf in you fs (/etc/wpa_supplicant.conf) ?
    Example file:

    # WPA configuration

    ctrl_interface=/var/run/wpa_supplicant
    update_config=1
    fast_reauth=1

    3: Did you run the wpa_supplicant before starting connman (you should)
    example:
    wpa_supplicant -c /etc/wpa_supplicant.conf -u

    4: Have you enabled rfkill while building the kernel (CONFIG_RFKILL=y)?

    5: copy the main.conf from [1] to etc/connman/main.conf

    [1] github.com/.../main.conf

    Cheers,
    --Prabhakar Lad
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points
    Hello Prabhakar,
    the answer to questions 1, 2, 3, 5 is: yes. Everything fine regarding this aspects.

    About question 4, RFKILL support was disabled, I'm currently rebuilding all with CONFIG_RFKILL=y. I'll let you know as soon as I've done.

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Intellectual 290 points

    Hello Prabhakar,

    big steps ahead! After the configuration of RFKILL ConnMan has started to show the wifi technology:

    root@lam_icu:~# connmanctl technologies
    /net/connman/technology/ethernet
      Name = Wired
      Type = ethernet
      Powered = True
      Connected = True
      Tethering = False
    /net/connman/technology/gadget
      Name = Gadget
      Type = gadget
      Powered = False
      Connected = False
      Tethering = False
    /net/connman/technology/wifi
      Name = WiFi
      Type = wifi
      Powered = True
      Connected = False
      Tethering = False


    Unfortunatly there is still something to configure. When executing the "scan wifi" command I've got:

    root@lam_icu:~# connmanctl
    connmanctl> enable wifi
    Error wifi: Already enabled
    connmanctl> agent on
    Agent registered
    connmanctl> scan wifi
    Error /net/connman/technology/wifi: Not supported

    I've searched with Google and found that the error is related to wpa_supplicant. See: https://wiki.archlinux.org/index.php/Connman#Error_.2Fnet.2Fconnman.2Ftechnology.2Fwifi:_Not_supported

    I've checked wpa_supplicant, it starts with the "networking" init script. The script is executed before the launch of connman:

    S01networking -> ../init.d/networking

    S05connman -> ../init.d/connman

    The boot log confirms that connman is started after the start of wpa_supplicant. The supplicant configuration file is:

    root@lam_icu:/etc/rc5.d# cat /etc/wpa_supplicant.conf
    ctrl_interface=/var/run/wpa_supplicant
    ctrl_interface_group=0
    update_config=1

    network={
            key_mgmt=NONE
    }

    It has been autogenerated.


    What can be the problem?

    Regards,

    Fabio

  • 0 in reply to Fabio Emiliani
    Guru 11260 points
    Hello,

    Just to check do you have systemd in your FS or init scripts ?
    Also do you have dbus ?

    Cheers,
    --Prabhakar Lad
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points
    Hi Prabhakar,
    we are still using init scripts. Yes, we use D-Bus for a lot of user space applications.

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Guru 11260 points
    Hello,

    connman depends on d-bus you need to have in you FS. It would be tricky to do with just scripts.
    Do you have your linux source online (github) ?, I could build a FS for you with dbus in it.

    Cheers,
    --Prabhakar Lad
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points
    Hi Prabhakar,
    I think D-Bus is correctly configured. I have checked the connman configuration file and:

    root@lam_icu:/etc/dbus-1/system.d# cat connman.conf
    <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
    "www.freedesktop.org/.../busconfig.dtd">
    <busconfig>
    <policy user="root">
    <allow own="net.connman"/>
    <allow send_destination="net.connman"/>
    <allow send_interface="net.connman.Agent"/>
    <allow send_interface="net.connman.Counter"/>
    <allow send_interface="net.connman.Notification"/>
    </policy>
    <policy user="xuser">
    <allow send_destination="net.connman"/>
    </policy>
    <policy at_console="true">
    <allow send_destination="net.connman"/>
    </policy>
    <policy context="default">
    <allow send_destination="net.connman"/>
    </policy>
    </busconfig>

    ConnMan can talk and receive messages on the bus. Plus I've requested the introspection of the net.connman service with dbus-send and everything is fine.

    dbus-send --system --dest=net.connman --type=method_call --print-reply / org.freedesktop.DBus.Introspectable.Introspect

    I can send D-Bus commands to ConnMan, I can receive signals from ConnMan.

    Is it possible that the "Error /net/connman/technology/wifi: Not supported" is caused by some strange interactions with wpa_supplicant? Does wpa_supplicant need some ConnMan specific configuration options? Does ConnMan dependes on some other system daemons (e.g. hostapd)?

    P.S. unfortunatly the linux source is not online, I can't share it :-(

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Intellectual 290 points

    Uhmmmm, reading my last post I've noticed a strange thing. The connman D-Bus configuration files refer to a <policy user="xuser">. I've already seen the "xuser" name, it's in the boot log:

    [    7.021644] wlcore: loaded

    Tue Sep 27 20:33:05 UTC 2016

    INIT: Entering runlevel: 5

    Configuring network interfaces... Successfully initialized wpa_supplicant

    [    7.835274] wlcore: PHY firmware version: Rev 8.2.0.0.212

    [    7.937027] wlcore: firmware booted (Rev 8.9.0.0.17)

    [    7.953514] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

    [    8.925556] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

    done.

    Starting system message bus: Unknown username "xuser" in message bus configuration file

    dbus.

    UIM SYSFS Node Not Found

    Starting Connection Manager

    Starting OpenBSD Secure Shell server: sshd

    done.

    Starting ntpd: done

    Starting syslogd/klogd: done

    Starting internet superserver: xinetd.

    Starting Telephony daemon

    Mount MMC

    [   10.242545] EXT4-fs (mmcblk2p1): recovery complete

    [   10.247631] EXT4-fs (mmcblk2p1): mounted filesystem with ordered data mode. Opts: (null)

    Is it possible that there is something wrong with the D-Bus configuration of ConnMan? What is "xuser"?

    Regards,

    Fabio

  • 0 in reply to Fabio Emiliani
    Guru 11260 points
    Hello,

    xuser is the user name, IF you have user xuser that should be fine. OR you can change it to root if you are logging as root. Here is my conf

    # cat connman.conf
    <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
    "www.freedesktop.org/.../busconfig.dtd">
    <busconfig>
    <policy user="root">
    <allow own="net.connman"/>
    <allow send_destination="net.connman"/>
    <allow send_interface="net.connman.Agent"/>
    <allow send_interface="net.connman.Counter"/>
    <allow send_interface="net.connman.Notification"/>
    </policy>
    <policy at_console="true">
    <allow send_destination="net.connman"/>
    </policy>
    <policy context="default">
    <deny send_destination="net.connman"/>
    </policy>
    </busconfig>



    # cat dbus-wpa_supplicant.conf
    <!DOCTYPE busconfig PUBLIC
    "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
    "www.freedesktop.org/.../busconfig.dtd">
    <busconfig>
    <policy user="root">
    <allow own="fi.epitest.hostap.WPASupplicant"/>

    <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
    <allow send_interface="fi.epitest.hostap.WPASupplicant"/>

    <allow own="fi.w1.wpa_supplicant1"/>

    <allow send_destination="fi.w1.wpa_supplicant1"/>
    <allow send_interface="fi.w1.wpa_supplicant1"/>
    <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
    </policy>
    <policy context="default">
    <deny own="fi.epitest.hostap.WPASupplicant"/>
    <deny send_destination="fi.epitest.hostap.WPASupplicant"/>
    <deny send_interface="fi.epitest.hostap.WPASupplicant"/>

    <deny own="fi.w1.wpa_supplicant1"/>
    <deny send_destination="fi.w1.wpa_supplicant1"/>
    <deny send_interface="fi.w1.wpa_supplicant1"/>
    <deny receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
    </policy>
    </busconfig>

    can you check if wpa is working with dbus ?

    Cheers,
    --Prabhakar Lad
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points
    Hi Prabhakar,
    damn! I forgot to enable the wpa_supplicant D-Bus interface. Well, I've copied your conf and enabled the interface (-u option), below my wpa_supplicant invocation (script: /etc/network/if-pre-up.d/wpa-supplicant):

    wpa_supplicant -u -B -P /var/run/wpa_supplicant.wlan0.pid -i wlan0

    In the boot log I see:
    dbus: Could not acquire the system bus: org.freedesktop.DBus.Error.FileNotFound - Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
    Failed to initialize wpa_supplicant

    Anyway wpa_supplicant is running :
    root@lam_icu:~# ps | grep wpa
    404 root 6376 S /usr/sbin/wpa_supplicant -u
    484 root 2660 S grep wpa

    and the D-Bus services seems to be ok:
    root@lam_icu:~#dbus-send --system --dest=org.freedesktop.DBus --type=method_call --print-reply /org/freedesktop/DBus org.freedesktop.DBus.ListNames
    method return sender=org.freedesktop.DBus -> dest=:1.4 reply_serial=2
    array [
    string "org.freedesktop.DBus"
    string ":1.4"
    string "fi.epitest.hostap.WPASupplicant"
    string "net.connman"
    string ":1.0"
    string "fi.w1.wpa_supplicant1"
    string ":1.1"
    string "org.ofono"
    string ":1.2"
    ]

    Finally I tried a wifi scan with ConnMan, the error disappeared but no networks are found (I'm under the coverage of several wifi AP).

    root@lam_icu:~# connmanctl
    connmanctl> enable wifi
    Error wifi: Already enabled
    connmanctl> agent on
    Agent registered
    connmanctl> scan wifi
    Scan completed for wifi

    I think that the cause of the problem can be found in the error at wpa_supplicant inizialization time.

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Intellectual 290 points
    HEY!

    I've checked the boot order of D-Bus and wpa_supplicant, D-Bus was AFTER wpa_supplicant. I changed my /etc/rc.5 folder from:
    root@lam_icu:/etc/rc5.d# ls -la
    drwxr-xr-x 2 root root 1520 Sep 28 10:22 .
    drwxr-xr-x 34 root root 6848 Sep 27 20:33 ..
    lrwxrwxrwx 1 root root 16 Sep 27 20:29 S02dbus-1 -> ../init.d/dbus-1
    lrwxrwxrwx 1 root root 20 Sep 27 20:29 S01networking -> ../init.d/networking

    into:
    root@lam_icu:/etc/rc5.d# ls -la
    drwxr-xr-x 2 root root 1520 Sep 28 10:22 .
    drwxr-xr-x 34 root root 6848 Sep 27 20:33 ..
    lrwxrwxrwx 1 root root 16 Sep 27 20:29 S01dbus-1 -> ../init.d/dbus-1
    lrwxrwxrwx 1 root root 20 Sep 27 20:29 S02networking -> ../init.d/networking

    in the boot log I see:
    Successfully initialized wpa_supplicant

    I've tried a scan and...

    connmanctl> scan wifi
    Scan completed for wifi
    connmanctl> services
    *AO Wired ethernet_00909a9dacb2_cable
    *A Wired ethernet_000000010203_cable
    MOTOGNET wifi_deadbeef0000_4d4f544f474e4554_managed_psk
    ARTWIFY3 wifi_deadbeef0000_4152545749465933_managed_wep

    IT WORKS!
  • 0 in reply to Fabio Emiliani
    Intellectual 290 points
    I'm testing the connection to several wifis, the agent let the user to insert the passphrase. ConnMan stores known wifis into /var/lib/connman. If executing disable/enable wifi the re-connection is automatically.

    Summarizing the macro problems were:
    - the enable of the RFKILL (kernel CONFIG)
    - the enable and configuration of wpa_supplicant D-Bus interface

    Prabhakar, you help was unvaluable, I don't know how to thank you.

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Intellectual 290 points

    Hi Prabhakar,

    these days I'm facing an important step: the migration from init to systemd.

    After the installation and configuration of systemd, I've tried to setup connman. When executing the command: connmanctl enable wifi, I've got the old, well known, error:

    Error wifi: Method "SetProperty" with signature "sv" on interface "net.connman.Technology" doesn't exist

    When I was using init, I resolved the error updating the kernel configuration with CONFIG_RFKILL=y. Now, under systemd, RFKILL is correctly running. See:

    root@lam_icu:~# rfkill list
    0: phy0: Wireless LAN
            Soft blocked: no
            Hard blocked: no

    After RFKILL I've checked the boot order of connmand and wpa_supplicant. It was wrong, I have changed the /lib/systemd/system/connman.service file adding the following dependency:

    [Unit]
    Description=Connection service
    Requires=dbus.socket
    After=dbus.socket wpa_supplicant.service
    Before=remote-fs.target

    [Service]
    Type=dbus
    BusName=net.connman
    Restart=on-failure
    ExecStartPre=-/usr/lib/connman/wired-setup
    ExecStart=/usr/sbin/connmand -n -c /etc/connman/main.conf
    StandardOutput=null

    [Install]
    WantedBy=multi-user.target

    The wpa_supplicant.service file content is:

    [Unit]
    Description=WPA supplicant

    [Service]
    Type=dbus
    BusName=fi.epitest.hostap.WPASupplicant
    ExecStart=/usr/sbin/wpa_supplicant -u -c /etc/wpa_supplicant.conf

    [Install]
    WantedBy=multi-user.target
    Alias=dbus-fi.epitest.hostap.WPASupplicant.service

    I've used the systemd-analyze tool to check the boot order. I can confirm that wpa_supplicant starts before connman.

    What can be the cause of the problem above? Why the "wireless" technology is missing? Is this a problem of interaction between RFKILL and Connman?

    Thanks in advance for your time

    Regards,

    Fabio

  • 0 in reply to Fabio Emiliani
    Intellectual 290 points

    Hi Prabhakar,

    another bit of info, I've tried to check the units related to RFKILL with the command: systemctl list-units | grep rfkill. Can you please check the attachment? Is everything ok?

    Fullscreen rfkill_list_units.txt Download 
    sys-devices-soc0-soc.0-2100000.aips\x2dbus-2194000.usdhc-mmc_host-mmc1-mmc1:0001-mmc1:0001:2-wl18xx.0.auto-ieee80211-phy0-rfkill0.device loaded active plugged   /sys/devices/soc0/soc.0/2100000.aips-bus/2194000.usdhc/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl18xx.0.auto/ieee80211/phy0/rfkill0
sys-subsystem-rfkill-devices-rfkill0.device                                                                                              loaded active plugged   /sys/subsystem/rfkill/devices/rfkill0
systemd-rfkill@rfkill0.service                                                                                                           loaded active exited    Load/Save RF Kill Switch Status of rfkill0
system-systemd\x2drfkill.slice                                                                                                           loaded active active    system-systemd\x2drfkill.slice

wpa_supplicant.service                                                                                                                   loaded active running   WPA supplicant

connman.service                                                                                                                          loaded active running   Connection service

    Then, looking into the connman.service file, I've found the following ExecStartPre:

    ExecStartPre=/usr/lib/connman/wired-setup

    The exec of wired-setup fails with code 203. There is no wired-setup bin in /usr/lib/connman. Do you think that this fail can cause the problem?

    Regards,

    Fabio

  • 0 in reply to Fabio Emiliani
    Guru 11260 points
    Hello,

    Not sure what version of connman are you using I am using the latest one with following service file:

    [Unit]
    Description=Connection Service
    After=dbus.service network-pre.target systemd-sysusers.service
    Before=network.target multi-user.target shutdown.target
    Wants=network.target

    [Service]
    Type=dbus
    BusName=net.connman
    Restart=on-failure
    ExecStart=/usr/sbin/connmand -n
    StandardOutput=null

    [Install]
    WantedBy=multi-user.target

    And wpa service as following:

    # cat /etc/systemd/system/wpa_supplicant.service
    [Unit]
    Description=Wi-Fi Security Service

    [Service]
    Type=dbus
    BusName=fi.w1.wpa_supplicant1
    ExecStart=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant.conf -u

    [Install]
    WantedBy=multi-user.target


    Note you still need CONFIG_RFKILL=y

    You dont need a rfkill service ideally.

    Cheers,
    --Prabhakar Lad
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points

    Hello Prabhakar,

    first of all thanks for your support. I'm using connman ver. 1.28, wpa_supplicant ver. 2.3, rfkill 0.5.

    This morning I've found an important clue. When launching connmand in foreground (-n), with debug logs enabled (-d), I see:

    connmand[1769]: /home/user/Project/ICU/BUILD_YOCTO/build_lam_icu_systemd/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/connman/1.28-r0/connman-1.28/src/technology.c:technology_get() No matching drivers found for wifi.

    That's strange because the driver is installed and the chip is correctly running (I can launch a scan, I can connect to a network using wpa_supplicant manually).

    The location of the driver is:

    /lib/modules/3.14.281.0-icu+g0b8488d/extra/drivers/net/wireless/ti/wlcore/wlcore.ko

    while the firmware and the config are located into:

    /lib/firmware/ti-connectivity

    Why connman can't found wifi drivers?

    In attachment the log output of connmand with debug logs enabled.

    connmand.log

    Again, many thanks

    --

    Fabio

  • 0 in reply to Fabio Emiliani
    Guru 11260 points
    Hello,

    Just to confirm have you built the wpa with following options ?
    CONFIG_READLINE=y
    CONFIG_DRIVER_NL80211=y
    CONFIG_CTRL_IFACE_DBUS_NEW=y
    CONFIG_CTRL_IFACE_DBUS_INTRO=y
    CONFIG_CTRL_IFACE=y
    CONFIG_LIBNL32=y
    CONFIG_AP=y
    CONFIG_P2P=y
    CONFIG_WPS=y
    CONFIG_EAP_GTC=y
    CONFIG_EAP_LEAP=y
    CONFIG_EAP_MD5=y
    CONFIG_EAP_MSCHAPV2=y
    CONFIG_EAP_OTP=y
    CONFIG_EAP_PEAP=y
    CONFIG_EAP_TLS=y
    CONFIG_EAP_TTLS=y
    CONFIG_PEERKEY=y

    Cheers,
    --Prabhakar Lad
  • 0 in reply to Prabhakar Lad
    Intellectual 290 points
    Hi Prabhakar,
    these are the CONFIGS of my supplicant build:

    #CONFIG_READLINE=y
    CONFIG_DRIVER_NL80211=y
    CONFIG_CTRL_IFACE_DBUS_NEW=y
    #CONFIG_CTRL_IFACE_DBUS_INTRO=y
    CONFIG_CTRL_IFACE=y
    CONFIG_LIBNL32=y
    CONFIG_AP=y
    #CONFIG_P2P=y
    CONFIG_WPS=y
    CONFIG_EAP_GTC=y
    CONFIG_EAP_LEAP=y
    CONFIG_EAP_MD5=y
    CONFIG_EAP_MSCHAPV2=y
    CONFIG_EAP_OTP=y
    CONFIG_EAP_PEAP=y
    CONFIG_EAP_TLS=y
    CONFIG_EAP_TTLS=y
    CONFIG_PEERKEY=y

    some are commented out:

    # Include support for GNU Readline and History Libraries in wpa_cli.
    # When building a wpa_cli binary for distribution, please note that these
    # libraries are licensed under GPL and as such, BSD license may not apply for
    # the resulting binary.
    #CONFIG_READLINE=y

    # Add introspection support for new DBus control interface
    #CONFIG_CTRL_IFACE_DBUS_INTRO=y

    # P2P (Wi-Fi Direct)
    # This can be used to enable P2P support in wpa_supplicant. See README-P2P for
    # more information on P2P operations.
    #CONFIG_P2P=y

    do you think I need to rebuild it?

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Intellectual 290 points

    Hi Prabhakar,

    I think I've found the problem. I don't know why but... after the switch from init to systemd some build options have changed.

    This is the command line invocation of the connman configure script:

     $ /home/user/Project/ICU/BUILD_YOCTO/build_lam_icu_systemd/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/connman/1.28-r0/connman-1.28/configure --build=x86_64-linux --host=arm-poky-linux-gnueabi --target=arm-poky-linux-gnueabi --prefix=/usr --exec_prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --libexecdir=/usr/lib/connman --datadir=/usr/share --sysconfdir=/etc --sharedstatedir=/com --localstatedir=/var --libdir=/usr/lib --includedir=/usr/include --oldincludedir=/usr/include --infodir=/usr/share/info --mandir=/usr/share/man --disable-silent-rules --disable-dependency-tracking --with-libtool-sysroot=/home/user/Project/ICU/BUILD_YOCTO/build_lam_icu_systemd/tmp/sysroots/lam_icu ac_cv_path_WPASUPPLICANT=/usr/sbin/wpa_supplicant ac_cv_path_PPPD=/usr/sbin/pppd --enable-debug --enable-loopback --enable-ethernet --enable-tools --enable-test --disable-polkit --enable-client --disable-ofono --disable-bluetooth --disable-l2tp --disable-openvpn --disable-pptp --with-systemdunitdir=/lib/systemd/system/ --disable-tist --disable-vpnc --disable-wifi --enable-wispr

    The wifi plugin is disabled. I'm currently rebuilding connman. I'll let you know asap.

    Regards,

    Fabio

  • 0 in reply to Fabio Emiliani
    Intellectual 290 points
    Hi Prabhakar,
    SOLVED! I added the following option in the Yocto local.conf:
    DISTRO_FEATURES_append += "wifi"

    Now connman has wifi plugin enabled. All technologies are correctly recognized:
    root@lam_icu:~# connmanctl technologies
    /net/connman/technology/p2p
    Name = P2P
    Type = p2p
    Powered = False
    Connected = False
    Tethering = False
    /net/connman/technology/wifi
    Name = WiFi
    Type = wifi
    Powered = True
    Connected = False
    Tethering = False
    /net/connman/technology/ethernet
    Name = Wired
    Type = ethernet
    Powered = True
    Connected = True
    Tethering = False
    /net/connman/technology/gadget
    Name = Gadget
    Type = gadget
    Powered = True
    Connected = False
    Tethering = False

    Thanks for your support!

    Regards,
    Fabio
  • 0 in reply to Fabio Emiliani
    Prodigy 10 points
    Hi Did you ever find a solution to this problem? I have an almost identical problem using a variscite IMX6 module with WL183xMOD
  • 0 in reply to Peter Hall
    Intellectual 290 points

    Hi Peter,

    yes, I solved the problem thanks to Prabhakar. Please refer to posts above


    Regards,

    Fabio Emiliani