What image should I build on the SabreLite?

What image should I build on the SabreLite?

[Philippe BALLEYDIER]

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

Hi everyone

I'm trying to stream the OV5642 parallel camera and a USB microphone over the network but i'm having some issues.
Previously, i was building fsl-image-multimedia (dizzi branch) on the SabreLite and I managed to make the video stream work. But i realized that USB ports were not working properly on this image (the USB microphone was detected but wouldn't appear in alsamixer)
To avoid this problem, i decided to switch to the image fsl-image-gui (dora branch) and now the OV5642 camera isn't detected (message showing up while booting: "Camera OV5642 is not found"). The mic is now properly showing up in alsamixer but i can't stream it since i get the error "cannot submit datapipe for urb 0, error -28: not enough bandwidth" when using my gstreamer commands.

I was previously building the image fsl-image-gui (dora) on the Sabre BOARD and i manage to stream both video and audio (but i was using a USB camera though, Mic remained the same)

So i don't really know what image and what board i should use to be able to stream 720p@30fps and audio from the USB Mic.
Due to USB throughput limitation, i can't stream a USB webcam at 720p@30fps on the sabre board (only 10fps possible) so i had to switch to the OV5642 on the Sabre Lite by using the parallel port J5
But what image will guaranty me that my USB Mic and the OV5642 will be detected and work properly?

Any pointers would be of great help
Best regards

PS1: Since the SabreLite is a boundary devices' product, maybe i should ask the question to them, but i can't find any forums. The "Community" tab on their website only links to other companies, but no actual community forum.

PS2: You can find in attachment my gstreamer commands, but i'm pretty sure the problem doesn't come from them, since when i use --gst-debug-level=2, it clearly appears that the camera is not detected. For the microphone, i have no idea why this is not working. It was working on the Sabre BOARD perfectly, and on the sabre Lite i have a bandwidth issue.


[-- Attachment #2: test ov.txt --]
[-- Type: text/plain, Size: 652 bytes --]

gst-launch --gst-debug-level=2 mfw_v4lsrc device=/dev/video0 capture-mode=4 rotate=3 fps-n=30 fps-d=1 ! ffmpegcolorspace ! vpuenc codec=6 ! rtph264pay ! udpsink host=192.168.20.31 port=5000 

gst-launch --gst-debug-level=2 udpsrc port=5000 caps="application/x-rtp, media=(string)video, clock-rate=(int)90000, payload=(int)96, encoding-name=(string)H264" ! rtph264depay ! ffdec_h264 ! xvimagesink

gst-launch --gst-debug-level=2 alsasrc device=hw:2 ! audioconvert ! audioresample  ! alawenc ! rtppcmapay ! udpsink host=192.168.20.31 port=5001

gst-launch --gst-debug-level=2 udpsrc port=5001 caps="application/x-rtp" ! rtppcmadepay ! alawdec ! alsasink

Re: What image should I build on the SabreLite?

[Eric Nelson]

[-- Attachment #1: Type: text/plain, Size: 2793 bytes --]

Hi Phillipe,

On Tuesday, November 4, 2014, Philippe BALLEYDIER <
PBalleydier@visionsystems.fr> wrote:

> Hi everyone
>
> I'm trying to stream the OV5642 parallel camera and a USB microphone over
> the network but i'm having some issues.
> Previously, i was building fsl-image-multimedia (dizzi branch) on the
> SabreLite and I managed to make the video stream work. But i realized that
> USB ports were not working properly on this image (the USB microphone was
> detected but wouldn't appear in alsamixer)


We don't normally include CONFIG_USB_AUDIO in our kernel defconfig, so
you'll need to add that.


> To avoid this problem, i decided to switch to the image fsl-image-gui
> (dora branch) and now the OV5642 camera isn't detected (message showing up
> while booting: "Camera OV5642 is not found"). The mic is now properly
> showing up in alsamixer but i can't stream it since i get the error "cannot
> submit datapipe for urb 0, error -28: not enough bandwidth" when using my
> gstreamer commands.


That branch is quite old. I'd recommend using dizzy.


>
> I was previously building the image fsl-image-gui (dora) on the Sabre
> BOARD and i manage to stream both video and audio (but i was using a USB
> camera though, Mic remained the same)
>
> So i don't really know what image and what board i should use to be able
> to stream 720p@30fps and audio from the USB Mic.
> Due to USB throughput limitation, i can't stream a USB webcam at 720p@30fps
> on the sabre board (only 10fps possible) so i had to switch to the OV5642
> on the Sabre Lite by using the parallel port J5

But what image will guaranty me that my USB Mic and the OV5642 will be
> detected and work properly?
>
> We configure things for included hardware (i.e. on board microphone
connection).

Deviation (USB microphone) will require some reconfiguration.


> Any pointers would be of great help
> Best regards
>
> PS1: Since the SabreLite is a boundary devices' product, maybe i should
> ask the question to them, but i can't find any forums. The "Community" tab
> on their website only links to other companies, but no actual community
> forum.
>
> This list wotks.

I also saw you question on i.mx Community, but haven't had a chance to
respond.

When all else fails, Info@boundarydevices.com should work for you.

PS2: You can find in attachment my gstreamer commands, but i'm pretty sure
> the problem doesn't come from them, since when i use --gst-debug-level=2,
> it clearly appears that the camera is not detected. For the microphone, i
> have no idea why this is not working. It was working on the Sabre BOARD
> perfectly, and on the sabre Lite i have a bandwidth issue.
>
>
The Sabre SD has a different defconfig.

Regards

Eric

[-- Attachment #2: Type: text/html, Size: 3902 bytes --]

Re: What image should I build on the SabreLite?

[Wally Yeh]

[-- Attachment #1: Type: text/plain, Size: 261 bytes --]

Hi, Eric:

>That branch is quite old. I'd recommend using dizzy.
since  FSL community BSP still use branch "daisy" for download example here:
http://freescale.github.io/#documentation

I'm not sure, would it be better using daisy instead dizzy?

Wally

[-- Attachment #2: Type: text/html, Size: 912 bytes --]

Re: What image should I build on the SabreLite?

[Otavio Salvador]

On Tue, Nov 4, 2014 at 1:16 PM, Wally Yeh <wally.yeh@atrustcorp.com> wrote:
> Hi, Eric:
>
>>That branch is quite old. I'd recommend using dizzy.
> since  FSL community BSP still use branch "daisy" for download example here:
> http://freescale.github.io/#documentation
>
> I'm not sure, would it be better using daisy instead dizzy?

My fault. I am adding Miguel on Cc so he can fix this for us.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: What image should I build on the SabreLite?

[Daiane Angolini]

On Tue, Nov 4, 2014 at 1:29 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
> On Tue, Nov 4, 2014 at 1:16 PM, Wally Yeh <wally.yeh@atrustcorp.com> wrote:
>> Hi, Eric:
>>
>>>That branch is quite old. I'd recommend using dizzy.
>> since  FSL community BSP still use branch "daisy" for download example here:
>> http://freescale.github.io/#documentation
>>
>> I'm not sure, would it be better using daisy instead dizzy?
>
> My fault. I am adding Miguel on Cc so he can fix this for us.

Why is it "your fault"? We haven´t formally released dizzy yet. The
page is supposed to point to daisy until we formally release dizzy.

I´m confused.

Daiane

Re: What image should I build on the SabreLite?

[Otavio Salvador]

On Tue, Nov 4, 2014 at 5:07 PM, Daiane Angolini <daiane.list@gmail.com> wrote:
> On Tue, Nov 4, 2014 at 1:29 PM, Otavio Salvador <otavio@ossystems.com.br> wrote:
>> On Tue, Nov 4, 2014 at 1:16 PM, Wally Yeh <wally.yeh@atrustcorp.com> wrote:
>>> Hi, Eric:
>>>
>>>>That branch is quite old. I'd recommend using dizzy.
>>> since  FSL community BSP still use branch "daisy" for download example here:
>>> http://freescale.github.io/#documentation
>>>
>>> I'm not sure, would it be better using daisy instead dizzy?
>>
>> My fault. I am adding Miguel on Cc so he can fix this for us.
>
> Why is it "your fault"? We haven´t formally released dizzy yet. The
> page is supposed to point to daisy until we formally release dizzy.
>
> I´m confused.

We are about it :-) But yes, Wally, Daiane is right. We didn't yet
formally released the 1.7 for FSL Community BSP however I strong
advise you focus on it as it is quite close and very stable.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: What image should I build on the SabreLite?

[Wally Yeh]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

Otavio Salvador <otavio@ossystems.com.br> wrote:
>We are about it :-) But yes, Wally, Daiane is right. We didn't yet
>formally released the 1.7 for FSL Community BSP however I strong
>advise you focus on it as it is quite close and very stable.

thanks, I'll try to change my branch from daisy(1.6) to dizzy(1.7).

Wally

[-- Attachment #2: Type: text/html, Size: 1258 bytes --]

Re: What image should I build on the SabreLite?

[Eric Nelson]

Hi Wally,

On 11/04/2014 07:16 AM, Wally Yeh wrote:
> Hi, Eric:
> 
>>That branch is quite old. I'd recommend using dizzy.
> since  FSL community BSP still use branch "daisy" for download example here:
> http://freescale.github.io/#documentation
> 
> I'm not sure, would it be better using daisy instead dizzy?
> 

If you're just getting started, I'd recommend starting off with
dizzy.

I'm not sure about the "official" release, but it's solid.

Regards,


Eric

Re: What image should I build on the SabreLite?

[Philippe BALLEYDIER]

[-- Attachment #1: Type: text/plain, Size: 3423 bytes --]

So i switched to the dizzy branch. I've build fsl-image-multimedia-full so i can have most of the gstreamer plugins i need.
How do i include CONFIG_USB_AUDIO to the kernel defconfig? I found multiple defconfig files, which one is the good one?

In attachment you can see the boot log, and it clearly appears that the OV5642 is not detected.
Any ideas why it doesn't show up?

Regards

________________________________________
De : Eric Nelson [eric.nelson@boundarydevices.com]
Envoyé : mardi 4 novembre 2014 16:04
À : Philippe BALLEYDIER
Cc : meta-freescale@yoctoproject.org
Objet : Re: [meta-freescale] What image should I build on the SabreLite?

Hi Phillipe,

On Tuesday, November 4, 2014, Philippe BALLEYDIER <PBalleydier@visionsystems.fr<mailto:PBalleydier@visionsystems.fr>> wrote:
Hi everyone

I'm trying to stream the OV5642 parallel camera and a USB microphone over the network but i'm having some issues.
Previously, i was building fsl-image-multimedia (dizzi branch) on the SabreLite and I managed to make the video stream work. But i realized that USB ports were not working properly on this image (the USB microphone was detected but wouldn't appear in alsamixer)

We don't normally include CONFIG_USB_AUDIO in our kernel defconfig, so you'll need to add that.

To avoid this problem, i decided to switch to the image fsl-image-gui (dora branch) and now the OV5642 camera isn't detected (message showing up while booting: "Camera OV5642 is not found"). The mic is now properly showing up in alsamixer but i can't stream it since i get the error "cannot submit datapipe for urb 0, error -28: not enough bandwidth" when using my gstreamer commands.

That branch is quite old. I'd recommend using dizzy.


I was previously building the image fsl-image-gui (dora) on the Sabre BOARD and i manage to stream both video and audio (but i was using a USB camera though, Mic remained the same)

So i don't really know what image and what board i should use to be able to stream 720p@30fps and audio from the USB Mic.
Due to USB throughput limitation, i can't stream a USB webcam at 720p@30fps on the sabre board (only 10fps possible) so i had to switch to the OV5642 on the Sabre Lite by using the parallel port J5
But what image will guaranty me that my USB Mic and the OV5642 will be detected and work properly?

We configure things for included hardware (i.e. on board microphone connection).

Deviation (USB microphone) will require some reconfiguration.

Any pointers would be of great help
Best regards

PS1: Since the SabreLite is a boundary devices' product, maybe i should ask the question to them, but i can't find any forums. The "Community" tab on their website only links to other companies, but no actual community forum.

This list wotks.

I also saw you question on i.mx<http://i.mx> Community, but haven't had a chance to respond.

When all else fails, Info@boundarydevices.com<mailto:Info@boundarydevices.com> should work for you.

PS2: You can find in attachment my gstreamer commands, but i'm pretty sure the problem doesn't come from them, since when i use --gst-debug-level=2, it clearly appears that the camera is not detected. For the microphone, i have no idea why this is not working. It was working on the Sabre BOARD perfectly, and on the sabre Lite i have a bandwidth issue.


The Sabre SD has a different defconfig.

Regards

Eric

[-- Attachment #2: boot log.txt --]
[-- Type: text/plain, Size: 21925 bytes --]

U-Boot 2014.04-00123-g63ae4a5 (May 14 2014 - 17:09:55)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: SABRE Lite
I2C:   ready
DRAM:  1 GiB
force_idle_bus: sda=0 scl=1 sda.gp=0x6d scl.gp=0x6c
force_idle_bus: failed to clear bus, sda=0 scl=1
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x50 retry=0
force_idle_bus: sda=0 scl=1 sda.gp=0x6d scl.gp=0x6c
force_idle_bus: failed to clear bus, sda=0 scl=1
i2c_init_transfer: give up i2c_regs=021a4000
No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6
FEC [PRIME], usb_ether
Hit any key to stop autoboot:  0 
mmc0 is current device
reading boot.scr
** Unable to read file boot.scr **
reading uImage
4595664 bytes read in 216 ms (20.3 MiB/s)
Booting from mmc ...
reading imx6q-sabrelite.dtb
49581 bytes read in 19 ms (2.5 MiB/s)
## Booting kernel from Legacy Image at 12000000 ...
   Image Name:   Linux-3.10.17-1.0.1_ga+yocto+g9f
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4595600 Bytes = 4.4 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 1800f1ac

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (philippe@philippe-HP-ProBook-4730s) (gcc version 4.9.1 (GCC) ) #1 SMP Tue Nov 4 18:56:30 CET 2014
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Freescale i.MX6 Quad SABRE Lite Board
cma: CMA: reserved 256 MiB at 2e000000
Memory policy: ECC disabled, Data cache writealloc
PERCPU: Embedded 8 pages/cpu @c10b7000 s8704 r8192 d15872 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260624
Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1024MB = 1024MB total
Memory: 767816k/767816k available, 280760k reserved, 270336K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc07b1024   (7845 kB)
      .init : 0xc07b2000 - 0xc07f8200   ( 281 kB)
      .data : 0xc07fa000 - 0xc0837ae0   ( 247 kB)
       .bss : 0xc0837ae0 - 0xc089d53c   ( 407 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:16 nr_irqs:16 16
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1048576 B
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
CPU identified as i.MX6Q, silicon rev 1.2
Console: colour dummy device 80x30
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0xc05e05d0 - 0xc05e0628
CPU1: Booted secondary processor
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
CPU2: Booted secondary processor
CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
CPU3: Booted secondary processor
CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Brought up 4 CPUs
SMP: Total of 4 processors activated (6324.22 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
pinctrl core: initialized pinctrl subsystem
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
Use WDOG1 as reset source
syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered
vdd1p1: 800 <--> 1375 mV at 1125 mV 
vdd3p0: 2800 <--> 3150 mV at 3000 mV 
vdd2p5: 2000 <--> 2750 mV at 2425 mV 
cpu: 725 <--> 1450 mV at 1100 mV 
vddpu: 725 <--> 1450 mV at 1100 mV 
vddsoc: 725 <--> 1450 mV at 1175 mV 
syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered
syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
bio: create slab <bio-0> at 0
1P8V: 1800 mV 
2P5V: 2500 mV 
3P3V: 3300 mV 
usb_otg_vbus: 5000 mV 
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c i2c-0: IMX I2C adapter registered
i2c i2c-1: IMX I2C adapter registered
i2c i2c-2: IMX I2C adapter registered
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed
mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Initialized.
Switching to clocksource mxc_timer1
imx6q-pcie 1ffc000.pcie: phy link never came up
imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x1000-0x10000]
pci_bus 0000:00: root bus resource [mem 0x01000000-0x01efffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
pci 0000:00:00.0: BAR 0: assigned [mem 0x01000000-0x010fffff]
pci 0000:00:00.0: BAR 6: assigned [mem 0x01100000-0x0110ffff pref]
pci 0000:00:00.0: PCI bridge to [bus 01]
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
pureg-dummy: no parameters
imx6_busfreq busfreq.15: DDR medium rate not supported.
Bus freq driver module loaded
bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
fuse init (API version 7.22)
msgmni has been set to 1483
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
imx-weim 21b8000.weim: WEIM driver registered.
i.MX PCIE endpoint device driver, version 0.1
MIPI DSI driver module loaded
mxc_sdc_fb fb.26: register mxc display driver hdmi
mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1
fbcvt: 1280x720@60: CVT Name - .921M9
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Console: switching to colour frame buffer device 160x45
mxc_sdc_fb fb.27: register mxc display driver hdmi
mxc_hdmi 20e0000.hdmi_video: Error only one HDMI output support now!
mxc_sdc_fb fb.27: NO mxc display driver found!
mxc_sdc_fb fb.28: register mxc display driver lcd
mxc_sdc_fb fb.28: NO mxc display driver found!
mxc_sdc_fb fb.29: register mxc display driver ldb
mxc_sdc_fb fb.29: 1024x768 h_sync,r,l: 60,40,220  v_sync,l,u: 10,7,21 pixclock=64998000 Hz
imx-ipuv3 2400000.ipu: use special clk parent
imx-ipuv3 2400000.ipu: disp=1, pixel_clk=64998000 64653061 parent=64653061 div=1
mxc_hdmi 20e0000.hdmi_video: Read EDID again
mxc_hdmi 20e0000.hdmi_video: No modes read from edid
mxc_hdmi 20e0000.hdmi_video: create default modelist
imx-sdma 20ec000.sdma: no iram assigned, using external mem
imx-sdma 20ec000.sdma: initialized
Serial: IMX driver
2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
imx-sdma 20ec000.sdma: loaded firmware 1.1
mxc_sdc_fb fb.26: 640x480 h_sync,r,l: 96,16,48  v_sync,l,u: 2,10,33 pixclock=25175000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=25175000 25142857 parent=264000000 div=10
console [ttymxc1] enabled
serial: Freescale lpuart driver
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized vivante 1.0.0 20120216 on minor 0
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
brd: module loaded
loop: module loaded
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Wait for CR ACK error!
sata phy RX_PLL is stable!
ahci: SSS flag set, parallel bus scan disabled
ahci ahci: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst 
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71
m25p80 spi32766.0: sst25vf016b (2048 Kbytes)
3 ofpart partitions found on MTD device spi32766.0
Creating 3 MTD partitions on "spi32766.0":
0x000000000000-0x0000000c0000 : "U-Boot"
0x0000000c0000-0x0000000c2000 : "env"
0x0000000c2000-0x000000200000 : "Kernel"
spi_imx 2008000.ecspi: probed
phyirq=188
libphy: fec_enet_mii_bus: probed
fec 2188000.ethernet eth0: registered PHC device 0
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver cp210x
usbserial: USB Serial support registered for cp210x
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver keyspan
usbserial: USB Serial support registered for Keyspan - (without firmware)
usbserial: USB Serial support registered for Keyspan 1 port adapter
usbserial: USB Serial support registered for Keyspan 2 port adapter
usbserial: USB Serial support registered for Keyspan 4 port adapter
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver pl2303
usbserial: USB Serial support registered for pl2303
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered for Qualcomm USB modem
setup_reset_gpios:-2
ci_hdrc ci_hdrc.0: EHCI Host Controller
ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
setup_reset_gpios:-2
ci_hdrc ci_hdrc.1: doesn't support gadget
ci_hdrc ci_hdrc.1: EHCI Host Controller
ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2
ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
egalax_ts 2-0004: Failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5
ft5x06-ts 2-0038: ft5x06: Could not detect touch screen.
ft5x06: Nov  4 2014
ili210x_i2c 2-0041: No platform data!
ili210x_i2c 2-0041: i2c transfer failed
ili210x_i2c 2-0041: Failed to get firmware version, err: -5
ili210x_i2c: probe of 2-0041 failed with error -5
tsc2004_prepare_for_reading: write_cmd -5
tsc2004: probe of 2-0048 failed with error -5
check_alarm_past: alarm in the past
snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
i2c /dev entries driver
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video16
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video17
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video18
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video19
i2c-core: driver [mag3110] using legacy suspend method
i2c-core: driver [mag3110] using legacy resume method
imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-esdhc-imx 2198000.usdhc: sdhci_esdhc_imx_probe_dt: power-gpio -2
sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode
mmc0: no vqmmc regulator found
mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
sdhci-esdhc-imx 219c000.usdhc: sdhci_esdhc_imx_probe_dt: power-gpio -2
sdhci-esdhc-imx 219c000.usdhc: could not get ultra high speed state, work on normal mode
mmc1: no vqmmc regulator found
mmc1: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA
ata1: SATA link down (SStatus 0 SControl 300)
usb 1-1: new full-speed USB device number 2 using ci_hdrc
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU08G 7.40 GiB 
 mmcblk0: p1 p2
usb 2-1: new high-speed USB device number 2 using ci_hdrc
Galcore version 4.6.9.9754
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 3 ports detected
mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
mxc_asrc 2034000.asrc: mxc_asrc registered
mxc_vpu 2040000.vpu: VPU initialized
caam 2100000.caam: device ID = 0x0a16010000000000 (Era -524)
caam 2100000.caam: job rings = 2, qi = 0
caam 2100000.caam: authenc-hmac-md5-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-md5-cbc-aes-caam
caam 2100000.caam: authenc-hmac-sha1-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-sha1-cbc-aes-caam
caam 2100000.caam: authenc-hmac-sha224-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-sha224-cbc-aes-caam
caam 2100000.caam: authenc-hmac-sha256-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-sha256-cbc-aes-caam
caam 2100000.caam: authenc-hmac-md5-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-md5-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-sha1-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-sha1-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-sha224-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-sha224-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-sha256-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-sha256-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-md5-cbc-des-caam
caam 2100000.caam: authencesn-hmac-md5-cbc-des-caam
caam 2100000.caam: authenc-hmac-sha1-cbc-des-caam
caam 2100000.caam: authencesn-hmac-sha1-cbc-des-caam
caam 2100000.caam: authenc-hmac-sha224-cbc-des-caam
caam 2100000.caam: authencesn-hmac-sha224-cbc-des-caam
caam 2100000.caam: authenc-hmac-sha256-cbc-des-caam
caam 2100000.caam: authencesn-hmac-sha256-cbc-des-caam
caam 2100000.caam: ecb-des-caam
caam 2100000.caam: ecb-arc4-caam
caam 2100000.caam: ecb-aes-caam
caam 2100000.caam: ctr-aes-caam
caam 2100000.caam: cbc-aes-caam
caam 2100000.caam: ecb-des3-caam
caam 2100000.caam: cbc-3des-caam
caam 2100000.caam: cbc-des-caam
caam 2100000.caam: fsl,sec-v4.0 algorithms registered in /proc/crypto
platform 2101000.jr0: registering rng-caam
platform caam_sm: caam_sm_test: 8-byte key test match OK
platform caam_sm: caam_sm_test: 16-byte key test match OK
platform caam_sm: caam_sm_test: 32-byte key test match OK
platform caam_secvio.37: security violation service handlers armed
input: Micronas UAC3556B as /devices/soc0/soc.1/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1:1.3/input/input0
hid-generic 0003:074D:3556.0001: input: USB HID v1.00 Device [Micronas UAC3556B] on usb-ci_hdrc.0-1/input3
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
sgtl5000 0-000a: sgtl5000 revision 0x11
sgtl5000 0-000a: Failed to get supply 'VDDD': -19
0-000a: 1200 mV normal 
sgtl5000 0-000a: Using internal LDO instead of VDDD
imx-sgtl5000 sound.24:  sgtl5000 <-> 2028000.ssi mapping ok
imx-audio-hdmi sound-hdmi.25:  hdmi-hifi <-> hdmi_audio.16 mapping ok
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Registering SWP/SWPB emulation handler
input: gpio-keys.23 as /devices/soc0/gpio-keys.23/input/input1
snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 2014-11-04 20:10:39 UTC (1415131839)
ALSA device list:
  #0: imx6q-sabrelite-sgtl5000
  #1: imx-hdmi-soc
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing unused kernel memory: 280K (c07b2000 - c07f8000)
INIT: version 2.88 booting
Starting udev
udevd[168]: starting version 182
CAN device driver interface
flexcan 2090000.can: device registered (reg_base=f0378000, irq=142)
bootlogd: cannot allocate pseudo tty: No such file or directory
adv7180 2-0020: adv7180_get_gpios: pwn-gpios flags(1 -> 0)
adv7180 2-0020: adv7180_get_gpios: rst-gpios flags(1 -> 0)
adv7180_gpio_state: active=0, rst-gpios(78)=0x1
adv7180_probe: cea861=0
adv7180_gpio_state: active=0, pwn-gpios(77)=0x1
adv7180 2-0020: get mclk failed
adv7180 2-0020: adv7180_read:read reg error: reg=11 ret=-5
adv7180: probe of 2-0020 failed with error -5
ov5640_mipi 1-003e: found pwm2, period=45
ov5640_read_reg:write reg error:reg=300a
camera ov5640 is not found
mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
mxc_v4l_open: Mxc Camera no sensor ipu1/csi1
mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
ALSA: Restoring mixer settings...FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

No state is present for card imx6qsabrelites
Found hardware: "imx6q-sabrelite" "" "" "" ""
Hardware is initialized using a generic method
INIT: Entering runlevel: 5
Configuring network interfaces... fec 2188000.ethernet eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=2188000.ethernet:0)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.22.1) started
update_device_addr: ov5640_mipi ret=-110
Sending discover...
ov5640_read_reg(mipi):reg=300a ret=-110
camera ov5640_mipi is not found
update_device_addr: ov5642 ret=-110
ov5642_read_reg:write reg error:reg=300a
camera ov5642 is not found
Sending discover...
Sending discover...
No lease, forking to background
done.
Starting Xserver
Starting system message bus: dbus.
Starting rpcbind daemon...done.
Starting advanced power management daemon: No APM support in kernel
(failed.)
Starting syslogd/klogd: done
 * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
   ...done.
Starting Telephony daemon
vgaarb: this pci device is not a vga device
Starting Linux NFC daemon
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
vgaarb: this pci device is not a vga device

Poky (Yocto Project Reference Distro) 1.7 imx6qsabrelite /dev/ttymxc1

imx6qsabrelite login: mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
libphy: 2188000.ethernet:06 - Link is Up - 1000/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Poky (Yocto Project Reference Distro) 1.7 imx6qsabrelite /dev/ttymxc1

imx6qsabrelite login:

Re: What image should I build on the SabreLite?

[Philippe BALLEYDIER]

[-- Attachment #1: Type: text/plain, Size: 3860 bytes --]

Hi

i'm still stuck with this problem.
Any ideas?

Best regards
________________________________________
De : meta-freescale-bounces@yoctoproject.org [meta-freescale-bounces@yoctoproject.org] de la part de Philippe BALLEYDIER [PBalleydier@visionsystems.fr]
Envoyé : mercredi 5 novembre 2014 09:42
À : Eric Nelson
Cc : meta-freescale@yoctoproject.org
Objet : Re: [meta-freescale] What image should I build on the SabreLite?

So i switched to the dizzy branch. I've build fsl-image-multimedia-full so i can have most of the gstreamer plugins i need.
How do i include CONFIG_USB_AUDIO to the kernel defconfig? I found multiple defconfig files, which one is the good one?

In attachment you can see the boot log, and it clearly appears that the OV5642 is not detected.
Any ideas why it doesn't show up?

Regards

________________________________________
De : Eric Nelson [eric.nelson@boundarydevices.com]
Envoyé : mardi 4 novembre 2014 16:04
À : Philippe BALLEYDIER
Cc : meta-freescale@yoctoproject.org
Objet : Re: [meta-freescale] What image should I build on the SabreLite?

Hi Phillipe,

On Tuesday, November 4, 2014, Philippe BALLEYDIER <PBalleydier@visionsystems.fr<mailto:PBalleydier@visionsystems.fr>> wrote:
Hi everyone

I'm trying to stream the OV5642 parallel camera and a USB microphone over the network but i'm having some issues.
Previously, i was building fsl-image-multimedia (dizzi branch) on the SabreLite and I managed to make the video stream work. But i realized that USB ports were not working properly on this image (the USB microphone was detected but wouldn't appear in alsamixer)

We don't normally include CONFIG_USB_AUDIO in our kernel defconfig, so you'll need to add that.

To avoid this problem, i decided to switch to the image fsl-image-gui (dora branch) and now the OV5642 camera isn't detected (message showing up while booting: "Camera OV5642 is not found"). The mic is now properly showing up in alsamixer but i can't stream it since i get the error "cannot submit datapipe for urb 0, error -28: not enough bandwidth" when using my gstreamer commands.

That branch is quite old. I'd recommend using dizzy.


I was previously building the image fsl-image-gui (dora) on the Sabre BOARD and i manage to stream both video and audio (but i was using a USB camera though, Mic remained the same)

So i don't really know what image and what board i should use to be able to stream 720p@30fps and audio from the USB Mic.
Due to USB throughput limitation, i can't stream a USB webcam at 720p@30fps on the sabre board (only 10fps possible) so i had to switch to the OV5642 on the Sabre Lite by using the parallel port J5
But what image will guaranty me that my USB Mic and the OV5642 will be detected and work properly?

We configure things for included hardware (i.e. on board microphone connection).

Deviation (USB microphone) will require some reconfiguration.

Any pointers would be of great help
Best regards

PS1: Since the SabreLite is a boundary devices' product, maybe i should ask the question to them, but i can't find any forums. The "Community" tab on their website only links to other companies, but no actual community forum.

This list wotks.

I also saw you question on i.mx<http://i.mx> Community, but haven't had a chance to respond.

When all else fails, Info@boundarydevices.com<mailto:Info@boundarydevices.com> should work for you.

PS2: You can find in attachment my gstreamer commands, but i'm pretty sure the problem doesn't come from them, since when i use --gst-debug-level=2, it clearly appears that the camera is not detected. For the microphone, i have no idea why this is not working. It was working on the Sabre BOARD perfectly, and on the sabre Lite i have a bandwidth issue.


The Sabre SD has a different defconfig.

Regards

Eric

[-- Attachment #2: boot log.txt --]
[-- Type: text/plain, Size: 21925 bytes --]

U-Boot 2014.04-00123-g63ae4a5 (May 14 2014 - 17:09:55)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: SABRE Lite
I2C:   ready
DRAM:  1 GiB
force_idle_bus: sda=0 scl=1 sda.gp=0x6d scl.gp=0x6c
force_idle_bus: failed to clear bus, sda=0 scl=1
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020
i2c_init_transfer: failed for chip 0x50 retry=0
force_idle_bus: sda=0 scl=1 sda.gp=0x6d scl.gp=0x6c
force_idle_bus: failed to clear bus, sda=0 scl=1
i2c_init_transfer: give up i2c_regs=021a4000
No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   using phy at 6
FEC [PRIME], usb_ether
Hit any key to stop autoboot:  0 
mmc0 is current device
reading boot.scr
** Unable to read file boot.scr **
reading uImage
4595664 bytes read in 216 ms (20.3 MiB/s)
Booting from mmc ...
reading imx6q-sabrelite.dtb
49581 bytes read in 19 ms (2.5 MiB/s)
## Booting kernel from Legacy Image at 12000000 ...
   Image Name:   Linux-3.10.17-1.0.1_ga+yocto+g9f
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4595600 Bytes = 4.4 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 1800f1ac

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (philippe@philippe-HP-ProBook-4730s) (gcc version 4.9.1 (GCC) ) #1 SMP Tue Nov 4 18:56:30 CET 2014
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Freescale i.MX6 Quad SABRE Lite Board
cma: CMA: reserved 256 MiB at 2e000000
Memory policy: ECC disabled, Data cache writealloc
PERCPU: Embedded 8 pages/cpu @c10b7000 s8704 r8192 d15872 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260624
Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1024MB = 1024MB total
Memory: 767816k/767816k available, 280760k reserved, 270336K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc07b1024   (7845 kB)
      .init : 0xc07b2000 - 0xc07f8200   ( 281 kB)
      .data : 0xc07fa000 - 0xc0837ae0   ( 247 kB)
       .bss : 0xc0837ae0 - 0xc089d53c   ( 407 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:16 nr_irqs:16 16
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1048576 B
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
CPU identified as i.MX6Q, silicon rev 1.2
Console: colour dummy device 80x30
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0xc05e05d0 - 0xc05e0628
CPU1: Booted secondary processor
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
CPU2: Booted secondary processor
CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
CPU3: Booted secondary processor
CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Brought up 4 CPUs
SMP: Total of 4 processors activated (6324.22 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
pinctrl core: initialized pinctrl subsystem
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
Use WDOG1 as reset source
syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered
vdd1p1: 800 <--> 1375 mV at 1125 mV 
vdd3p0: 2800 <--> 3150 mV at 3000 mV 
vdd2p5: 2000 <--> 2750 mV at 2425 mV 
cpu: 725 <--> 1450 mV at 1100 mV 
vddpu: 725 <--> 1450 mV at 1100 mV 
vddsoc: 725 <--> 1450 mV at 1175 mV 
syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered
syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
bio: create slab <bio-0> at 0
1P8V: 1800 mV 
2P5V: 2500 mV 
3P3V: 3300 mV 
usb_otg_vbus: 5000 mV 
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c i2c-0: IMX I2C adapter registered
i2c i2c-1: IMX I2C adapter registered
i2c i2c-2: IMX I2C adapter registered
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed
mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Initialized.
Switching to clocksource mxc_timer1
imx6q-pcie 1ffc000.pcie: phy link never came up
imx6q-pcie 1ffc000.pcie: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x1000-0x10000]
pci_bus 0000:00: root bus resource [mem 0x01000000-0x01efffff]
pci_bus 0000:00: root bus resource [bus 00-ff]
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
pci 0000:00:00.0: BAR 0: assigned [mem 0x01000000-0x010fffff]
pci 0000:00:00.0: BAR 6: assigned [mem 0x01100000-0x0110ffff pref]
pci 0000:00:00.0: PCI bridge to [bus 01]
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
pureg-dummy: no parameters
imx6_busfreq busfreq.15: DDR medium rate not supported.
Bus freq driver module loaded
bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
fuse init (API version 7.22)
msgmni has been set to 1483
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
imx-weim 21b8000.weim: WEIM driver registered.
i.MX PCIE endpoint device driver, version 0.1
MIPI DSI driver module loaded
mxc_sdc_fb fb.26: register mxc display driver hdmi
mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1
fbcvt: 1280x720@60: CVT Name - .921M9
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Console: switching to colour frame buffer device 160x45
mxc_sdc_fb fb.27: register mxc display driver hdmi
mxc_hdmi 20e0000.hdmi_video: Error only one HDMI output support now!
mxc_sdc_fb fb.27: NO mxc display driver found!
mxc_sdc_fb fb.28: register mxc display driver lcd
mxc_sdc_fb fb.28: NO mxc display driver found!
mxc_sdc_fb fb.29: register mxc display driver ldb
mxc_sdc_fb fb.29: 1024x768 h_sync,r,l: 60,40,220  v_sync,l,u: 10,7,21 pixclock=64998000 Hz
imx-ipuv3 2400000.ipu: use special clk parent
imx-ipuv3 2400000.ipu: disp=1, pixel_clk=64998000 64653061 parent=64653061 div=1
mxc_hdmi 20e0000.hdmi_video: Read EDID again
mxc_hdmi 20e0000.hdmi_video: No modes read from edid
mxc_hdmi 20e0000.hdmi_video: create default modelist
imx-sdma 20ec000.sdma: no iram assigned, using external mem
imx-sdma 20ec000.sdma: initialized
Serial: IMX driver
2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
imx-sdma 20ec000.sdma: loaded firmware 1.1
mxc_sdc_fb fb.26: 640x480 h_sync,r,l: 96,16,48  v_sync,l,u: 2,10,33 pixclock=25175000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=25175000 25142857 parent=264000000 div=10
console [ttymxc1] enabled
serial: Freescale lpuart driver
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized vivante 1.0.0 20120216 on minor 0
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
brd: module loaded
loop: module loaded
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Wait for CR ACK error!
sata phy RX_PLL is stable!
ahci: SSS flag set, parallel bus scan disabled
ahci ahci: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst 
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71
m25p80 spi32766.0: sst25vf016b (2048 Kbytes)
3 ofpart partitions found on MTD device spi32766.0
Creating 3 MTD partitions on "spi32766.0":
0x000000000000-0x0000000c0000 : "U-Boot"
0x0000000c0000-0x0000000c2000 : "env"
0x0000000c2000-0x000000200000 : "Kernel"
spi_imx 2008000.ecspi: probed
phyirq=188
libphy: fec_enet_mii_bus: probed
fec 2188000.ethernet eth0: registered PHC device 0
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver cp210x
usbserial: USB Serial support registered for cp210x
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver keyspan
usbserial: USB Serial support registered for Keyspan - (without firmware)
usbserial: USB Serial support registered for Keyspan 1 port adapter
usbserial: USB Serial support registered for Keyspan 2 port adapter
usbserial: USB Serial support registered for Keyspan 4 port adapter
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver pl2303
usbserial: USB Serial support registered for pl2303
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered for Qualcomm USB modem
setup_reset_gpios:-2
ci_hdrc ci_hdrc.0: EHCI Host Controller
ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
setup_reset_gpios:-2
ci_hdrc ci_hdrc.1: doesn't support gadget
ci_hdrc ci_hdrc.1: EHCI Host Controller
ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2
ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
egalax_ts 2-0004: Failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5
ft5x06-ts 2-0038: ft5x06: Could not detect touch screen.
ft5x06: Nov  4 2014
ili210x_i2c 2-0041: No platform data!
ili210x_i2c 2-0041: i2c transfer failed
ili210x_i2c 2-0041: Failed to get firmware version, err: -5
ili210x_i2c: probe of 2-0041 failed with error -5
tsc2004_prepare_for_reading: write_cmd -5
tsc2004: probe of 2-0048 failed with error -5
check_alarm_past: alarm in the past
snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
i2c /dev entries driver
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video16
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video17
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video18
mxc_v4l2_output v4l2_out.36: V4L2 device registered as video19
i2c-core: driver [mag3110] using legacy suspend method
i2c-core: driver [mag3110] using legacy resume method
imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-esdhc-imx 2198000.usdhc: sdhci_esdhc_imx_probe_dt: power-gpio -2
sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode
mmc0: no vqmmc regulator found
mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
sdhci-esdhc-imx 219c000.usdhc: sdhci_esdhc_imx_probe_dt: power-gpio -2
sdhci-esdhc-imx 219c000.usdhc: could not get ultra high speed state, work on normal mode
mmc1: no vqmmc regulator found
mmc1: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA
ata1: SATA link down (SStatus 0 SControl 300)
usb 1-1: new full-speed USB device number 2 using ci_hdrc
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU08G 7.40 GiB 
 mmcblk0: p1 p2
usb 2-1: new high-speed USB device number 2 using ci_hdrc
Galcore version 4.6.9.9754
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 3 ports detected
mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
mxc_asrc 2034000.asrc: mxc_asrc registered
mxc_vpu 2040000.vpu: VPU initialized
caam 2100000.caam: device ID = 0x0a16010000000000 (Era -524)
caam 2100000.caam: job rings = 2, qi = 0
caam 2100000.caam: authenc-hmac-md5-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-md5-cbc-aes-caam
caam 2100000.caam: authenc-hmac-sha1-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-sha1-cbc-aes-caam
caam 2100000.caam: authenc-hmac-sha224-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-sha224-cbc-aes-caam
caam 2100000.caam: authenc-hmac-sha256-cbc-aes-caam
caam 2100000.caam: authencesn-hmac-sha256-cbc-aes-caam
caam 2100000.caam: authenc-hmac-md5-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-md5-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-sha1-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-sha1-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-sha224-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-sha224-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-sha256-cbc-des3_ede-caam
caam 2100000.caam: authencesn-hmac-sha256-cbc-des3_ede-caam
caam 2100000.caam: authenc-hmac-md5-cbc-des-caam
caam 2100000.caam: authencesn-hmac-md5-cbc-des-caam
caam 2100000.caam: authenc-hmac-sha1-cbc-des-caam
caam 2100000.caam: authencesn-hmac-sha1-cbc-des-caam
caam 2100000.caam: authenc-hmac-sha224-cbc-des-caam
caam 2100000.caam: authencesn-hmac-sha224-cbc-des-caam
caam 2100000.caam: authenc-hmac-sha256-cbc-des-caam
caam 2100000.caam: authencesn-hmac-sha256-cbc-des-caam
caam 2100000.caam: ecb-des-caam
caam 2100000.caam: ecb-arc4-caam
caam 2100000.caam: ecb-aes-caam
caam 2100000.caam: ctr-aes-caam
caam 2100000.caam: cbc-aes-caam
caam 2100000.caam: ecb-des3-caam
caam 2100000.caam: cbc-3des-caam
caam 2100000.caam: cbc-des-caam
caam 2100000.caam: fsl,sec-v4.0 algorithms registered in /proc/crypto
platform 2101000.jr0: registering rng-caam
platform caam_sm: caam_sm_test: 8-byte key test match OK
platform caam_sm: caam_sm_test: 16-byte key test match OK
platform caam_sm: caam_sm_test: 32-byte key test match OK
platform caam_secvio.37: security violation service handlers armed
input: Micronas UAC3556B as /devices/soc0/soc.1/2100000.aips-bus/2184000.usb/ci_hdrc.0/usb1/1-1/1-1:1.3/input/input0
hid-generic 0003:074D:3556.0001: input: USB HID v1.00 Device [Micronas UAC3556B] on usb-ci_hdrc.0-1/input3
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
sgtl5000 0-000a: sgtl5000 revision 0x11
sgtl5000 0-000a: Failed to get supply 'VDDD': -19
0-000a: 1200 mV normal 
sgtl5000 0-000a: Using internal LDO instead of VDDD
imx-sgtl5000 sound.24:  sgtl5000 <-> 2028000.ssi mapping ok
imx-audio-hdmi sound-hdmi.25:  hdmi-hifi <-> hdmi_audio.16 mapping ok
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Registering SWP/SWPB emulation handler
input: gpio-keys.23 as /devices/soc0/gpio-keys.23/input/input1
snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 2014-11-04 20:10:39 UTC (1415131839)
ALSA device list:
  #0: imx6q-sabrelite-sgtl5000
  #1: imx-hdmi-soc
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing unused kernel memory: 280K (c07b2000 - c07f8000)
INIT: version 2.88 booting
Starting udev
udevd[168]: starting version 182
CAN device driver interface
flexcan 2090000.can: device registered (reg_base=f0378000, irq=142)
bootlogd: cannot allocate pseudo tty: No such file or directory
adv7180 2-0020: adv7180_get_gpios: pwn-gpios flags(1 -> 0)
adv7180 2-0020: adv7180_get_gpios: rst-gpios flags(1 -> 0)
adv7180_gpio_state: active=0, rst-gpios(78)=0x1
adv7180_probe: cea861=0
adv7180_gpio_state: active=0, pwn-gpios(77)=0x1
adv7180 2-0020: get mclk failed
adv7180 2-0020: adv7180_read:read reg error: reg=11 ret=-5
adv7180: probe of 2-0020 failed with error -5
ov5640_mipi 1-003e: found pwm2, period=45
ov5640_read_reg:write reg error:reg=300a
camera ov5640 is not found
mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
mxc_v4l_open: Mxc Camera no sensor ipu1/csi1
mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
ALSA: Restoring mixer settings...FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

No state is present for card imx6qsabrelites
Found hardware: "imx6q-sabrelite" "" "" "" ""
Hardware is initialized using a generic method
INIT: Entering runlevel: 5
Configuring network interfaces... fec 2188000.ethernet eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=2188000.ethernet:0)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.22.1) started
update_device_addr: ov5640_mipi ret=-110
Sending discover...
ov5640_read_reg(mipi):reg=300a ret=-110
camera ov5640_mipi is not found
update_device_addr: ov5642 ret=-110
ov5642_read_reg:write reg error:reg=300a
camera ov5642 is not found
Sending discover...
Sending discover...
No lease, forking to background
done.
Starting Xserver
Starting system message bus: dbus.
Starting rpcbind daemon...done.
Starting advanced power management daemon: No APM support in kernel
(failed.)
Starting syslogd/klogd: done
 * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
   ...done.
Starting Telephony daemon
vgaarb: this pci device is not a vga device
Starting Linux NFC daemon
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
vgaarb: this pci device is not a vga device

Poky (Yocto Project Reference Distro) 1.7 imx6qsabrelite /dev/ttymxc1

imx6qsabrelite login: mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
mxc_sdc_fb fb.26: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
libphy: 2188000.ethernet:06 - Link is Up - 1000/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Poky (Yocto Project Reference Distro) 1.7 imx6qsabrelite /dev/ttymxc1

imx6qsabrelite login:

Re: What image should I build on the SabreLite?

[Eric Nelson]

Hi Philippe,

Sorry for the delayed response.

On 11/06/2014 02:31 AM, Philippe BALLEYDIER wrote:
> Hi
> 
> i'm still stuck with this problem.
> Any ideas?
> 
> Best regards
> ________________________________________
> De : meta-freescale-bounces@yoctoproject.org [meta-freescale-bounces@yoctoproject.org] de la part de Philippe BALLEYDIER [PBalleydier@visionsystems.fr]
> Envoyé : mercredi 5 novembre 2014 09:42
> À : Eric Nelson
> Cc : meta-freescale@yoctoproject.org
> Objet : Re: [meta-freescale] What image should I build on the SabreLite?
> 
> So i switched to the dizzy branch. I've build fsl-image-multimedia-full so i can have most of the gstreamer plugins i need.
> How do i include CONFIG_USB_AUDIO to the kernel defconfig? I found multiple defconfig files, which one is the good one?
> 
> In attachment you can see the boot log, and it clearly appears that the OV5642 is not detected.
> Any ideas why it doesn't show up?
> 

No idea except perhaps cable connections. The log appears exactly
as it would if you had no camera connected.

This should **just work**.

I don't have a current dizzy/mm-full build handy, so I haven't had a
chance to reproduce.

I'll try to get that done later today.

Regards,


Eric

Re: What image should I build on the SabreLite?

[Eric Nelson]

Hi Philippe,

On 11/06/2014 08:55 AM, Eric Nelson wrote:
> Hi Philippe,
> 
> Sorry for the delayed response.
> 
> On 11/06/2014 02:31 AM, Philippe BALLEYDIER wrote:
>> Hi
>>
>> i'm still stuck with this problem.
>> Any ideas?
>>
>> Best regards
>> ________________________________________
>> De : meta-freescale-bounces@yoctoproject.org [meta-freescale-bounces@yoctoproject.org] de la part de Philippe BALLEYDIER [PBalleydier@visionsystems.fr]
>> Envoyé : mercredi 5 novembre 2014 09:42
>> À : Eric Nelson
>> Cc : meta-freescale@yoctoproject.org
>> Objet : Re: [meta-freescale] What image should I build on the SabreLite?
>>
>> So i switched to the dizzy branch. I've build fsl-image-multimedia-full so i can have most of the gstreamer plugins i need.
>> How do i include CONFIG_USB_AUDIO to the kernel defconfig? I found multiple defconfig files, which one is the good one?
>>
>> In attachment you can see the boot log, and it clearly appears that the OV5642 is not detected.
>> Any ideas why it doesn't show up?
>>
> 
> No idea except perhaps cable connections. The log appears exactly
> as it would if you had no camera connected.
> 
> This should **just work**.
> 
> I don't have a current dizzy/mm-full build handy, so I haven't had a
> chance to reproduce.
> 
> I'll try to get that done later today.
> 

While building from dizzy, I grabbed the latest 'fsl-machine-test'
from O.S.Systems CI server (master branch):

	http://ci.ossystems.com.br/public/fsl-community-bsp/master/389/x11/nitrogen6x/fsl-image-machine-test-nitrogen6x-20141102-389.rootfs.sdcard

This image has the same kernel version (g9f710da) as the head of
dizzy, and it came right up.

	root@nitrogen6x:~# cat /proc/version
	Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (jenkins@builder) (gcc
version 4.9.1 (GCC) ) #1 SMP Sun Nov 2 13:37:00 UTC 2014
	root@nitrogen6x:~# dmesg | grep ov5642
	mxc_v4l2_master_attach: ipu0:/csi0 parallel attached ov5642:mxc_v4l2_cap0
	ov5642 1-003d: created sysfs entry for reading regs
	camera ov5642 is found

I did see some weirdness in the mode setting of /dev/fb0, but the
camera was functional, and I tested with a minimal gst-launch
command-line:

	root@nitrogen6x:~# gst-launch mfw_v4lsrc ! mfw_v4lsink

Regards,


Eric

Re: What image should I build on the SabreLite?

[Eric Nelson]

Hi Philippe,

On 11/06/2014 11:11 AM, Eric Nelson wrote:
> Hi Philippe,
> 
> <snip>
> 
> While building from dizzy, I grabbed the latest 'fsl-machine-test'
> from O.S.Systems CI server (master branch):
> 
> 	http://ci.ossystems.com.br/public/fsl-community-bsp/master/389/x11/nitrogen6x/fsl-image-machine-test-nitrogen6x-20141102-389.rootfs.sdcard
> 
> This image has the same kernel version (g9f710da) as the head of
> dizzy, and it came right up.
> 
> 	root@nitrogen6x:~# cat /proc/version
> 	Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (jenkins@builder) (gcc
> version 4.9.1 (GCC) ) #1 SMP Sun Nov 2 13:37:00 UTC 2014
> 	root@nitrogen6x:~# dmesg | grep ov5642
> 	mxc_v4l2_master_attach: ipu0:/csi0 parallel attached ov5642:mxc_v4l2_cap0
> 	ov5642 1-003d: created sysfs entry for reading regs
> 	camera ov5642 is found
> 
> I did see some weirdness in the mode setting of /dev/fb0, but the
> camera was functional, and I tested with a minimal gst-launch
> command-line:
> 
> 	root@nitrogen6x:~# gst-launch mfw_v4lsrc ! mfw_v4lsink
> 

I just tested fsl-image-multimedia-full on the dizzy branch and
things look the same there (including the weirdness surrounding
the display resolution).

The camera was recognized and gst-launch functioned properly.

Regards,


Eric

Re: What image should I build on the SabreLite?

[Philippe BALLEYDIER]

Hi

I did the same as you on fsl-image-multimedia-full
Here's what i get:

root@nitrogen6x:~# cat /proc/version
Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (philippe@philippe-HP-ProBook-4730s) (gcc version 4.9.1 (GCC) ) #1 SMP Fri Nov 7 08:50:50 CET 2014
root@nitrogen6x:~# dmesg | grep ov5642
update_device_addr: ov5642 ret=-110
ov5642_read_reg:write reg error:reg=300a
camera ov5642 is not found
root@nitrogen6x:~# dmesg | grep ov5640
ov5640_mipi 1-003e: found pwm2, period=45
ov5640_read_reg:write reg error:reg=300a
camera ov5640 is not found
update_device_addr: ov5640_mipi ret=-110
ov5640_read_reg(mipi):reg=300a ret=-110
camera ov5640_mipi is not found
root@nitrogen6x:~# gst-launch --gst-debug-level=2 mfw_v4lsrc ! mfw_v4lsink
MFW_GST_V4LSRC_PLUGIN 3.0.11 build on Nov  7 2014 09:23:30.
mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
mxc_v4l_open: Mxc Camera no sensor ipu1/csi1
0:00:00.113605000   804  0x18aad20 WARN   xc_v4l_open: Mxc Camera no sensor ipu0/csi0
m          mfw_v4lsink /media/philippe/data/release/build/tmp/work/nitrogen6x-poky-linux-gnueabi/gst-fsl-plugin/3.0.11-r0/gst-fsl-plugins-3.0.11/src/misc/v4l_sink/src/mfw_gst_v4lsink.c:303:mfw_gst_v4l2sink_query_support_formats: unrecognized format:[Y444]YUV444
MFW_GST_V4LSINK_PLUGIN 3.0.11 build on Nov  7 2014 09:23:25.
Setting pipeline to PAUSED ...
0:00:00.123365000   804  0x18aad20 ERROR             mfw_v4lsrc /media/philippe/data/release/build/tmp/work/nitrogen6x-poky-linux-gnueabi/gst-fsl-plugin/3.0.11-r0/gst-fsl-plugins-3.0.11/src/misc/v4l_source/src/mfw_gst_v4lsrc.c:474:mfw_gst_v4lsrc_capture_setup: >>V4L_SRC: Unable to open /dev/video0
0:00:00.123428667   804  0x18aad20 ERROR             mfw_v4lsrc /media/philippe/data/release/build/tmp/work/nitrogen6x-poky-linux-gnueabi/gst-fsl-plugin/3.0.11-r0/gst-fsl-plugins-3.0.11/src/misc/v4l_source/src/mfw_gst_v4lsrc.c:1030:mfw_gst_v4lsrc_start: v4lsrc:error in opening the device
0:00:00.123483667   804  0x18aad20 WARN                 basesrc /media/philippe/data/release/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gstreamer/0.10.36-r2/gstreamer-0.10.36/libs/gst/base/gstbasesrc.c:3039:gst_base_src_activate_push:<mfwgstv4lsrc0> Failed to start in push mode
0:00:00.123538333   804  0x18aad20 WARN                GST_PADS /media/philippe/data/release/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/gstreamer/0.10.36-r2/gstreamer-0.10.36/gst/gstpad.c:737:gst_pad_set_active:<mfwgstv4lsrc0:src> Failed to activate pad
ERROR: Pipeline doesn't want to pause.
Setting pipeline to NULL ...
Total rendered:0
Freeing pipeline ...
[--->FINALIZE v4l_sink



Is it possible that my camera is dead? How can i make sure of that?
I managed to make it work once on fsl-image-gui (dora branch). I guess i will rebuild this one just to make sure the camera is still working fine.


I added the CONFIG_USB_AUDIO to the kernel and i now have a UAC2_Gadget appearing in alsamixer, but no element is showing up: This sound device does not have any controls.


________________________________________
De : Eric Nelson [eric.nelson@boundarydevices.com]
Envoyé : jeudi 6 novembre 2014 19:11
À : Philippe BALLEYDIER
Cc : meta-freescale@yoctoproject.org
Objet : Re: [meta-freescale] What image should I build on the SabreLite?

Hi Philippe,

On 11/06/2014 08:55 AM, Eric Nelson wrote:
> Hi Philippe,
>
> Sorry for the delayed response.
>
> On 11/06/2014 02:31 AM, Philippe BALLEYDIER wrote:
>> Hi
>>
>> i'm still stuck with this problem.
>> Any ideas?
>>
>> Best regards
>> ________________________________________
>> De : meta-freescale-bounces@yoctoproject.org [meta-freescale-bounces@yoctoproject.org] de la part de Philippe BALLEYDIER [PBalleydier@visionsystems.fr]
>> Envoyé : mercredi 5 novembre 2014 09:42
>> À : Eric Nelson
>> Cc : meta-freescale@yoctoproject.org
>> Objet : Re: [meta-freescale] What image should I build on the SabreLite?
>>
>> So i switched to the dizzy branch. I've build fsl-image-multimedia-full so i can have most of the gstreamer plugins i need.
>> How do i include CONFIG_USB_AUDIO to the kernel defconfig? I found multiple defconfig files, which one is the good one?
>>
>> In attachment you can see the boot log, and it clearly appears that the OV5642 is not detected.
>> Any ideas why it doesn't show up?
>>
>
> No idea except perhaps cable connections. The log appears exactly
> as it would if you had no camera connected.
>
> This should **just work**.
>
> I don't have a current dizzy/mm-full build handy, so I haven't had a
> chance to reproduce.
>
> I'll try to get that done later today.
>

While building from dizzy, I grabbed the latest 'fsl-machine-test'
from O.S.Systems CI server (master branch):

        http://ci.ossystems.com.br/public/fsl-community-bsp/master/389/x11/nitrogen6x/fsl-image-machine-test-nitrogen6x-20141102-389.rootfs.sdcard

This image has the same kernel version (g9f710da) as the head of
dizzy, and it came right up.

        root@nitrogen6x:~# cat /proc/version
        Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (jenkins@builder) (gcc
version 4.9.1 (GCC) ) #1 SMP Sun Nov 2 13:37:00 UTC 2014
        root@nitrogen6x:~# dmesg | grep ov5642
        mxc_v4l2_master_attach: ipu0:/csi0 parallel attached ov5642:mxc_v4l2_cap0
        ov5642 1-003d: created sysfs entry for reading regs
        camera ov5642 is found

I did see some weirdness in the mode setting of /dev/fb0, but the
camera was functional, and I tested with a minimal gst-launch
command-line:

        root@nitrogen6x:~# gst-launch mfw_v4lsrc ! mfw_v4lsink

Regards,


Eric

Re: What image should I build on the SabreLite?

[Eric Nelson]

Hi Philippe,

On 11/07/2014 03:00 AM, Philippe BALLEYDIER wrote:
> Hi
> 
> I did the same as you on fsl-image-multimedia-full
> Here's what i get:
> 
> root@nitrogen6x:~# cat /proc/version
> Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (philippe@philippe-HP-ProBook-4730s) (gcc version 4.9.1 (GCC) ) #1 SMP Fri Nov 7 08:50:50 CET 2014
> root@nitrogen6x:~# dmesg | grep ov5642
> update_device_addr: ov5642 ret=-110
> ov5642_read_reg:write reg error:reg=300a
> camera ov5642 is not found

This indicates a problem with the camera or cabling.

> root@nitrogen6x:~# dmesg | grep ov5640
> ov5640_mipi 1-003e: found pwm2, period=45
> ov5640_read_reg:write reg error:reg=300a
> camera ov5640 is not found
> update_device_addr: ov5640_mipi ret=-110
> ov5640_read_reg(mipi):reg=300a ret=-110
> camera ov5640_mipi is not found

You don't have one of these connected, right?

> root@nitrogen6x:~# gst-launch --gst-debug-level=2 mfw_v4lsrc ! mfw_v4lsink
> MFW_GST_V4LSRC_PLUGIN 3.0.11 build on Nov  7 2014 09:23:30.
> mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
> mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
> mxc_v4l_open: Mxc Camera no sensor ipu1/csi1

If the cameras were "not found", I think you knew what was going
to happen here!

> 
> <snip>
> 
> Is it possible that my camera is dead? How can i make sure of that?
>
It's most likely a cabling issue. It's quite easy for the flex cables
to become dislodged since there aren't any cable stays.

> I managed to make it work once on fsl-image-gui (dora branch). I
> guess i will rebuild this one just to make sure the camera is still working fine.
> 
I'd recommend using a pre-built image to shave some time.

There are quite a few on O.S. Systems CI server:
	http://ci.ossystems.com.br/public/fsl-community-bsp/master

This Ubuntu image also contains full camera support:
	http://boundarydevices.com/ubuntu-trusty-mx6-boards-september-2014/

> 
> I added the CONFIG_USB_AUDIO to the kernel and i now have a
> UAC2_Gadget appearing in alsamixer, but no element is showing up: This
> sound device does not have any controls.
> 
I'm not sure what you mean by "no element".

Can you clarify?

You mentioned that the SABRE SD board was able to operate with
your hardware. You might want to compare the defconfig files
between the two.  Perhaps something is missing.

Regards,


Eric

Re: What image should I build on the SabreLite?

[Philippe BALLEYDIER]

Hi everyone.

>________________________________________
>De : Eric Nelson [eric.nelson@boundarydevices.com]
>Envoyé : vendredi 7 novembre 2014 14:55
>À : Philippe BALLEYDIER
>Cc : meta-freescale@yoctoproject.org
>Objet : Re: [meta-freescale] What image should I build on the SabreLite?
>
>Hi Philippe,
>
>On 11/07/2014 03:00 AM, Philippe BALLEYDIER wrote:
>> Hi
>>
>> I did the same as you on fsl-image-multimedia-full
>> Here's what i get:
>>
>> root@nitrogen6x:~# cat /proc/version
>> Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (philippe@philippe-HP-ProBook-4730s) (gcc version 4.9.1 (GCC) ) #1 SMP Fri Nov 7 08:50:50 CET 2014
>> root@nitrogen6x:~# dmesg | grep ov5642
>> update_device_addr: ov5642 ret=-110
>> ov5642_read_reg:write reg error:reg=300a
>> camera ov5642 is not found

>This indicates a problem with the camera or cabling.



I verified the cabling, and it's still not working; So i believe one of the flex is broken, or it's the camera




>> root@nitrogen6x:~# dmesg | grep ov5640
>> ov5640_mipi 1-003e: found pwm2, period=45
>> ov5640_read_reg:write reg error:reg=300a
>> camera ov5640 is not found
>> update_device_addr: ov5640_mipi ret=-110
>> ov5640_read_reg(mipi):reg=300a ret=-110
>> camera ov5640_mipi is not found

>You don't have one of these connected, right?



No i don't. I just tried this command because i wanted to see if something different show up




>> root@nitrogen6x:~# gst-launch --gst-debug-level=2 mfw_v4lsrc ! mfw_v4lsink
>> MFW_GST_V4LSRC_PLUGIN 3.0.11 build on Nov  7 2014 09:23:30.
>> mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
>> mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
>> mxc_v4l_open: Mxc Camera no sensor ipu1/csi1

>If the cameras were "not found", I think you knew what was going
>to happen here!

>>
>> <snip>
>>
>> Is it possible that my camera is dead? How can i make sure of that?
>>
>It's most likely a cabling issue. It's quite easy for the flex cables
>to become dislodged since there aren't any cable stays.




As i said, i unplug/replug every flex, and it is still not working.




>> I managed to make it work once on fsl-image-gui (dora branch). I
>> guess i will rebuild this one just to make sure the camera is still working fine.
>>
>I'd recommend using a pre-built image to shave some time.

>There are quite a few on O.S. Systems CI server:
>        http://ci.ossystems.com.br/public/fsl-community-bsp/master

>This Ubuntu image also contains full camera support:
>        http://boundarydevices.com/ubuntu-trusty-mx6-boards-september-2014/



I used the fsl-image-gui (dora's branch, the one i used before and on which it was working before) and the fsl-image-test on OS Systems CI server.
In both case, the camera is not found. Since it used to work with the fsl-image-gui, it's either the flex or the camera not working.




>>
>> I added the CONFIG_USB_AUDIO to the kernel and i now have a
>> UAC2_Gadget appearing in alsamixer, but no element is showing up: This
>> sound device does not have any controls.
>>
>I'm not sure what you mean by "no element".

>Can you clarify?



When i open alsamixer and press F6 to see what card is available. I see a new sound card called "UAC2_Gadget". When i press enter to select it, there is no equalizer appearing (like MIC, Bass, Treble, Line, etc), just a message saying: "This sound device does not have any controls"



>You mentioned that the SABRE SD board was able to operate with
>your hardware. You might want to compare the defconfig files
>between the two.  Perhaps something is missing.



Yes, i'll try this later and keep you updated


Best regards

Philippe

Re: What image should I build on the SabreLite?

[Philippe BALLEYDIER]

Moreover, i just realized that there is a difference between the commands "dmesg | grep ov5642" when the camera is plugged in or not.
When plugged:
root@nitrogen6x:~# dmesg | grep ov5642                                          
update_device_addr: ov5642 ret=-110                                             
ov5642_read_reg:write reg error:reg=300a                                        
camera ov5642 is not found 

When not plugged:
root@nitrogen6x:~# dmesg | grep ov5642                                          
update_device_addr: ov5642 ret=-5                                               
ov5642_read_reg:write reg error:reg=300a                                        
camera ov5642 is not found 

So update_device_addr doesn't return the same thing. Maybe that means something, or not...

Best regards

________________________________________
De : meta-freescale-bounces@yoctoproject.org [meta-freescale-bounces@yoctoproject.org] de la part de Philippe BALLEYDIER [PBalleydier@visionsystems.fr]
Envoyé : jeudi 13 novembre 2014 12:09
À : meta-freescale@yoctoproject.org
Objet : Re: [meta-freescale] What image should I build on the SabreLite?

Hi everyone.

>________________________________________
>De : Eric Nelson [eric.nelson@boundarydevices.com]
>Envoyé : vendredi 7 novembre 2014 14:55
>À : Philippe BALLEYDIER
>Cc : meta-freescale@yoctoproject.org
>Objet : Re: [meta-freescale] What image should I build on the SabreLite?
>
>Hi Philippe,
>
>On 11/07/2014 03:00 AM, Philippe BALLEYDIER wrote:
>> Hi
>>
>> I did the same as you on fsl-image-multimedia-full
>> Here's what i get:
>>
>> root@nitrogen6x:~# cat /proc/version
>> Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (philippe@philippe-HP-ProBook-4730s) (gcc version 4.9.1 (GCC) ) #1 SMP Fri Nov 7 08:50:50 CET 2014
>> root@nitrogen6x:~# dmesg | grep ov5642
>> update_device_addr: ov5642 ret=-110
>> ov5642_read_reg:write reg error:reg=300a
>> camera ov5642 is not found

>This indicates a problem with the camera or cabling.



I verified the cabling, and it's still not working; So i believe one of the flex is broken, or it's the camera




>> root@nitrogen6x:~# dmesg | grep ov5640
>> ov5640_mipi 1-003e: found pwm2, period=45
>> ov5640_read_reg:write reg error:reg=300a
>> camera ov5640 is not found
>> update_device_addr: ov5640_mipi ret=-110
>> ov5640_read_reg(mipi):reg=300a ret=-110
>> camera ov5640_mipi is not found

>You don't have one of these connected, right?



No i don't. I just tried this command because i wanted to see if something different show up




>> root@nitrogen6x:~# gst-launch --gst-debug-level=2 mfw_v4lsrc ! mfw_v4lsink
>> MFW_GST_V4LSRC_PLUGIN 3.0.11 build on Nov  7 2014 09:23:30.
>> mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
>> mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
>> mxc_v4l_open: Mxc Camera no sensor ipu1/csi1

>If the cameras were "not found", I think you knew what was going
>to happen here!

>>
>> <snip>
>>
>> Is it possible that my camera is dead? How can i make sure of that?
>>
>It's most likely a cabling issue. It's quite easy for the flex cables
>to become dislodged since there aren't any cable stays.




As i said, i unplug/replug every flex, and it is still not working.




>> I managed to make it work once on fsl-image-gui (dora branch). I
>> guess i will rebuild this one just to make sure the camera is still working fine.
>>
>I'd recommend using a pre-built image to shave some time.

>There are quite a few on O.S. Systems CI server:
>        http://ci.ossystems.com.br/public/fsl-community-bsp/master

>This Ubuntu image also contains full camera support:
>        http://boundarydevices.com/ubuntu-trusty-mx6-boards-september-2014/



I used the fsl-image-gui (dora's branch, the one i used before and on which it was working before) and the fsl-image-test on OS Systems CI server.
In both case, the camera is not found. Since it used to work with the fsl-image-gui, it's either the flex or the camera not working.




>>
>> I added the CONFIG_USB_AUDIO to the kernel and i now have a
>> UAC2_Gadget appearing in alsamixer, but no element is showing up: This
>> sound device does not have any controls.
>>
>I'm not sure what you mean by "no element".

>Can you clarify?



When i open alsamixer and press F6 to see what card is available. I see a new sound card called "UAC2_Gadget". When i press enter to select it, there is no equalizer appearing (like MIC, Bass, Treble, Line, etc), just a message saying: "This sound device does not have any controls"



>You mentioned that the SABRE SD board was able to operate with
>your hardware. You might want to compare the defconfig files
>between the two.  Perhaps something is missing.



Yes, i'll try this later and keep you updated


Best regards

Philippe
--
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale

Re: What image should I build on the SabreLite?

[Eric Nelson]

Hi Philippe,

On 11/06/2014 08:55 AM, Eric Nelson wrote:
> Hi Philippe,
> 
> Sorry for the delayed response.
> 
> On 11/06/2014 02:31 AM, Philippe BALLEYDIER wrote:
>> Hi
>>
>> i'm still stuck with this problem.
>> Any ideas?
>>
>> Best regards
>> ________________________________________
>> De : meta-freescale-bounces@yoctoproject.org [meta-freescale-bounces@yoctoproject.org] de la part de Philippe BALLEYDIER [PBalleydier@visionsystems.fr]
>> Envoyé : mercredi 5 novembre 2014 09:42
>> À : Eric Nelson
>> Cc : meta-freescale@yoctoproject.org
>> Objet : Re: [meta-freescale] What image should I build on the SabreLite?
>>
>> So i switched to the dizzy branch. I've build fsl-image-multimedia-full so i can have most of the gstreamer plugins i need.
>> How do i include CONFIG_USB_AUDIO to the kernel defconfig? I found multiple defconfig files, which one is the good one?
>>

I think you can configure the kernel using "bitbake -c menuconfig":

	~/yocto/build$ bitbake -c menuconfig linux-boundary

	Device Drivers
		> Sound card support
			> Advanced Linux Sound Architecture
				> USB sound devices
					*  USB Audio/MIDI driver

You can also just add CONFIG_USB_AUDIO to the file
	sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary-3.10.17/nitrogen6x/defconfig

Regards,


Eric