* FlexCAN not working
@ 2013-10-11 11:28 diego
2013-10-11 15:16 ` Eric Nelson
2013-10-18 11:33 ` FlexCAN not working diego
0 siblings, 2 replies; 10+ messages in thread
From: diego @ 2013-10-11 11:28 UTC (permalink / raw)
To: meta-freescale
Hello everybody,
I'm trying to test FlexCAN on Sabrelite imx6 board without success.
Those are the steps followed :
1) Comprobed that linux-imx has CAN drivers enable
2) Added on the image the packages:canutils,libsocketcan and iproute2
3) Tested the Flex can with canconfig and cantest.
Everything seems ok, even I can see transmitted frames incremented.
However there's not singnal on the oscilloscope.
I don't now why is not working. Any ideas or suggestions?
Thank you!
--
Diego González González
Dpto. de Control Industrial
diego.gonzalez@horus.es
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 11:28 FlexCAN not working diego
@ 2013-10-11 15:16 ` Eric Nelson
2013-10-11 18:15 ` Jose Mª Ferreiro
2013-10-18 11:33 ` FlexCAN not working diego
1 sibling, 1 reply; 10+ messages in thread
From: Eric Nelson @ 2013-10-11 15:16 UTC (permalink / raw)
To: diego, meta-freescale
Hi Diego,
On 10/11/2013 04:28 AM, diego wrote:
> Hello everybody,
>
> I'm trying to test FlexCAN on Sabrelite imx6 board without success.
> Those are the steps followed :
>
> 1) Comprobed that linux-imx has CAN drivers enable
> 2) Added on the image the packages:canutils,libsocketcan and iproute2
> 3) Tested the Flex can with canconfig and cantest.
>
> Everything seems ok, even I can see transmitted frames incremented.
> However there's not singnal on the oscilloscope.
>
> I don't now why is not working. Any ideas or suggestions?
>
Can you forward your kernel version (/proc/version) and output
of /proc/cpuinfo?
Some early versions of SABRE Lite used a discontinued Freescale
CAN PHY, and there's some code in board-mx6_nitrogen6x.c to
detect which is in use. If you're using the old board-mx6_sabrelite.c,
that detection code isn't present.
Checking dmesg will tell you:
dmesg | grep can
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L1377
Regards,
Eric
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 15:16 ` Eric Nelson
@ 2013-10-11 18:15 ` Jose Mª Ferreiro
2013-10-11 18:41 ` Eric Nelson
0 siblings, 1 reply; 10+ messages in thread
From: Jose Mª Ferreiro @ 2013-10-11 18:15 UTC (permalink / raw)
To: meta-freescale
El 11/10/2013 17:16, Eric Nelson escribió:
> Hi Diego,
>
> On 10/11/2013 04:28 AM, diego wrote:
>> Hello everybody,
>>
>> I'm trying to test FlexCAN on Sabrelite imx6 board without success.
>> Those are the steps followed :
>>
>> 1) Comprobed that linux-imx has CAN drivers enable
>> 2) Added on the image the packages:canutils,libsocketcan and iproute2
>> 3) Tested the Flex can with canconfig and cantest.
>>
>> Everything seems ok, even I can see transmitted frames incremented.
>> However there's not singnal on the oscilloscope.
>>
>> I don't now why is not working. Any ideas or suggestions?
>>
>
> Can you forward your kernel version (/proc/version) and output
> of /proc/cpuinfo?
>
> Some early versions of SABRE Lite used a discontinued Freescale
> CAN PHY, and there's some code in board-mx6_nitrogen6x.c to
> detect which is in use. If you're using the old board-mx6_sabrelite.c,
> that detection code isn't present.
Hi Eric
Below are the outputs you asked. But I compared board-...nitro to
board-..sabrelite sources. Certainly nitrogen is configured for two
transceivers while sabrelite is fixed to one of them. Our board, from
Farnell element 14, has the TJA1040 transceiver. I think Sabrelite code
is working like the other transceiver. However I am not finding the
transceiver detection code :( . I keep trying :)
Thanks
This is yocto master + linux-imx
root@imx6qsabrelite:~# cat /proc/version
Linux version 3.0.35-4.1.0+yocto-masterimxhorus+gbdde708 (horus@ubuntu)
(gcc version 4.8.1 (GCC) ) #4 SMP PREEMPT Thu Oct 10 10:41:48 CEST 2013
root@imx6qsabrelite:~# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 10 (v7l)
processor : 0
BogoMIPS : 790.52
processor : 1
BogoMIPS : 790.52
processor : 2
BogoMIPS : 790.52
processor : 3
BogoMIPS : 790.52
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10
Hardware : Freescale i.MX 6Quad Sabre-Lite Board
Revision : 63012
Serial : 0000000000000000
> Checking dmesg will tell you:
> dmesg | grep can
>
> https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L1377
>
>
> Regards,
>
>
> Eric
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 18:15 ` Jose Mª Ferreiro
@ 2013-10-11 18:41 ` Eric Nelson
2013-10-11 18:55 ` Jose Mª Ferreiro
0 siblings, 1 reply; 10+ messages in thread
From: Eric Nelson @ 2013-10-11 18:41 UTC (permalink / raw)
To: Jose Mª Ferreiro, meta-freescale
Hi Jose,
On 10/11/2013 11:15 AM, Jose Mª Ferreiro wrote:
>
> El 11/10/2013 17:16, Eric Nelson escribió:
>> Hi Diego,
>>
>> On 10/11/2013 04:28 AM, diego wrote:
>>> Hello everybody,
>>>
>>> I'm trying to test FlexCAN on Sabrelite imx6 board without success.
>>> Those are the steps followed :
>>>
>>> 1) Comprobed that linux-imx has CAN drivers enable
>>> 2) Added on the image the packages:canutils,libsocketcan and iproute2
>>> 3) Tested the Flex can with canconfig and cantest.
>>>
>>> Everything seems ok, even I can see transmitted frames incremented.
>>> However there's not singnal on the oscilloscope.
>>>
>>> I don't now why is not working. Any ideas or suggestions?
>>>
>>
>> Can you forward your kernel version (/proc/version) and output
>> of /proc/cpuinfo?
>>
>> Some early versions of SABRE Lite used a discontinued Freescale
>> CAN PHY, and there's some code in board-mx6_nitrogen6x.c to
>> detect which is in use. If you're using the old board-mx6_sabrelite.c,
>> that detection code isn't present.
> Hi Eric
>
> Below are the outputs you asked. But I compared board-...nitro to
> board-..sabrelite sources. Certainly nitrogen is configured for two
> transceivers while sabrelite is fixed to one of them. Our board, from
> Farnell element 14, has the TJA1040 transceiver. I think Sabrelite code
> is working like the other transceiver. However I am not finding the
> transceiver detection code :( . I keep trying :)
>
The detection code is defined in the link I forwarded earlier:
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L1382
This board file can be used for both SABRE Lite and Nitrogen6X
boards. I suspect this includes those produced by Farnell.
The board-mx6_sabrelite.c file is essentially un-maintained and
contains a reference to the old mc33902 PHY.
> Thanks
>
> This is yocto master + linux-imx
>
You'll really want to use linux-boundary.
Regards,
Eric
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 18:41 ` Eric Nelson
@ 2013-10-11 18:55 ` Jose Mª Ferreiro
2013-10-11 20:56 ` Wayne T. Schellekens
2013-10-11 22:11 ` Eric Nelson
0 siblings, 2 replies; 10+ messages in thread
From: Jose Mª Ferreiro @ 2013-10-11 18:55 UTC (permalink / raw)
To: meta-freescale
El 11/10/2013 20:41, Eric Nelson escribió:
> Hi Jose,
>
> On 10/11/2013 11:15 AM, Jose Mª Ferreiro wrote:
>>
>> El 11/10/2013 17:16, Eric Nelson escribió:
>>> Hi Diego,
>>>
>>> On 10/11/2013 04:28 AM, diego wrote:
>>>> Hello everybody,
>>>>
>>>> I'm trying to test FlexCAN on Sabrelite imx6 board without success.
>>>> Those are the steps followed :
>>>>
>>>> 1) Comprobed that linux-imx has CAN drivers enable
>>>> 2) Added on the image the packages:canutils,libsocketcan and iproute2
>>>> 3) Tested the Flex can with canconfig and cantest.
>>>>
>>>> Everything seems ok, even I can see transmitted frames incremented.
>>>> However there's not singnal on the oscilloscope.
>>>>
>>>> I don't now why is not working. Any ideas or suggestions?
>>>>
>>>
>>> Can you forward your kernel version (/proc/version) and output
>>> of /proc/cpuinfo?
>>>
>>> Some early versions of SABRE Lite used a discontinued Freescale
>>> CAN PHY, and there's some code in board-mx6_nitrogen6x.c to
>>> detect which is in use. If you're using the old board-mx6_sabrelite.c,
>>> that detection code isn't present.
>> Hi Eric
>>
>> Below are the outputs you asked. But I compared board-...nitro to
>> board-..sabrelite sources. Certainly nitrogen is configured for two
>> transceivers while sabrelite is fixed to one of them. Our board, from
>> Farnell element 14, has the TJA1040 transceiver. I think Sabrelite code
>> is working like the other transceiver. However I am not finding the
>> transceiver detection code :( . I keep trying :)
>>
>
> The detection code is defined in the link I forwarded earlier:
> https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L1382
>
>
> This board file can be used for both SABRE Lite and Nitrogen6X
> boards. I suspect this includes those produced by Farnell.
>
> The board-mx6_sabrelite.c file is essentially un-maintained and
> contains a reference to the old mc33902 PHY.
>
>> Thanks
>>
>> This is yocto master + linux-imx
>>
>
> You'll really want to use linux-boundary.
>
> Regards,
>
>
> Eric
Hi Eric
You are correct. I didn´t look well for it. It seems as it depends on a
third GPIO signal to select one transceiver or the other. We will test
it on monday.
I would like to use linux-boundary, wich was the default, but we have to
change to linux-imx due to video issues that did not work on
linux-boundary: something about mfw_isink i think.
I readed about the two linux branches, boundary and imx, being merged
for the board but we can not wait for it. So I suppose we will have to
test and merge them by ourselves .. with your help :) Any recomendation
are welcomed.
Thank you very much again
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 18:55 ` Jose Mª Ferreiro
@ 2013-10-11 20:56 ` Wayne T. Schellekens
2013-10-11 22:11 ` Eric Nelson
1 sibling, 0 replies; 10+ messages in thread
From: Wayne T. Schellekens @ 2013-10-11 20:56 UTC (permalink / raw)
To: meta-freescale@yoctoproject.org
Hi,
FlexCAN is also not working on SabreSDP board.
I normally follow this procedure (https://community.freescale.com/servlet/JiveServlet/previewBody/94887-102-1-6575/How%20to%20enable%20CAN%20bus%20on%20i.MX6Q%20SabreSD.pdf) , and it has worked in the past on my rev C SabreSDP board.
After I upgraded to dora branch, and applied my patch I now get an error in the ip link command:
root@imx6qsabresd:~# ip link set can0 up type can bitrate 1000000
ip: either "dev" is duplicate, or "type" is garbage
Any ideas what has changed?
Thanks,
Wayne
-----Original Message-----
From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-bounces@yoctoproject.org] On Behalf Of Jose Mª Ferreiro
Sent: Friday, October 11, 2013 1:56 PM
To: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] FlexCAN not working
El 11/10/2013 20:41, Eric Nelson escribió:
> Hi Jose,
>
> On 10/11/2013 11:15 AM, Jose Mª Ferreiro wrote:
>>
>> El 11/10/2013 17:16, Eric Nelson escribió:
>>> Hi Diego,
>>>
>>> On 10/11/2013 04:28 AM, diego wrote:
>>>> Hello everybody,
>>>>
>>>> I'm trying to test FlexCAN on Sabrelite imx6 board without success.
>>>> Those are the steps followed :
>>>>
>>>> 1) Comprobed that linux-imx has CAN drivers enable
>>>> 2) Added on the image the packages:canutils,libsocketcan and
>>>> iproute2
>>>> 3) Tested the Flex can with canconfig and cantest.
>>>>
>>>> Everything seems ok, even I can see transmitted frames incremented.
>>>> However there's not singnal on the oscilloscope.
>>>>
>>>> I don't now why is not working. Any ideas or suggestions?
>>>>
>>>
>>> Can you forward your kernel version (/proc/version) and output of
>>> /proc/cpuinfo?
>>>
>>> Some early versions of SABRE Lite used a discontinued Freescale CAN
>>> PHY, and there's some code in board-mx6_nitrogen6x.c to detect which
>>> is in use. If you're using the old board-mx6_sabrelite.c, that
>>> detection code isn't present.
>> Hi Eric
>>
>> Below are the outputs you asked. But I compared board-...nitro to
>> board-..sabrelite sources. Certainly nitrogen is configured for two
>> transceivers while sabrelite is fixed to one of them. Our board, from
>> Farnell element 14, has the TJA1040 transceiver. I think Sabrelite
>> code is working like the other transceiver. However I am not finding
>> the transceiver detection code :( . I keep trying :)
>>
>
> The detection code is defined in the link I forwarded earlier:
>
> https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35
> _4.1.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L1382
>
>
> This board file can be used for both SABRE Lite and Nitrogen6X boards.
> I suspect this includes those produced by Farnell.
>
> The board-mx6_sabrelite.c file is essentially un-maintained and
> contains a reference to the old mc33902 PHY.
>
>> Thanks
>>
>> This is yocto master + linux-imx
>>
>
> You'll really want to use linux-boundary.
>
> Regards,
>
>
> Eric
Hi Eric
You are correct. I didn´t look well for it. It seems as it depends on a third GPIO signal to select one transceiver or the other. We will test it on monday.
I would like to use linux-boundary, wich was the default, but we have to change to linux-imx due to video issues that did not work on
linux-boundary: something about mfw_isink i think.
I readed about the two linux branches, boundary and imx, being merged for the board but we can not wait for it. So I suppose we will have to test and merge them by ourselves .. with your help :) Any recomendation are welcomed.
Thank you very much again
_______________________________________________
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 18:55 ` Jose Mª Ferreiro
2013-10-11 20:56 ` Wayne T. Schellekens
@ 2013-10-11 22:11 ` Eric Nelson
2013-10-14 9:40 ` Jose Mª Ferreiro
1 sibling, 1 reply; 10+ messages in thread
From: Eric Nelson @ 2013-10-11 22:11 UTC (permalink / raw)
To: Jose Mª Ferreiro, meta-freescale
On 10/11/2013 11:55 AM, Jose Mª Ferreiro wrote:
<snip>
>
> You are correct. I didn´t look well for it. It seems as it depends on a
> third GPIO signal to select one transceiver or the other. We will test
> it on monday.
>
> I would like to use linux-boundary, wich was the default, but we have to
> change to linux-imx due to video issues that did not work on
> linux-boundary: something about mfw_isink i think.
>
Can you elaborate? I'm not aware of any board-specific code in
mfw_isink, and certainly not in the Nitrogen6x code.
> I readed about the two linux branches, boundary and imx, being merged
> for the board but we can not wait for it. So I suppose we will have to
> test and merge them by ourselves .. with your help :) Any recomendation
> are welcomed.
>
The current versions of meta-fsl-arm-extra have imx6qsabrelite pointed
at nitrogen6x:
https://github.com/Freescale/meta-fsl-arm-extra/blob/master/conf/machine/imx6qsabrelite.conf
Regards,
Eric
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 22:11 ` Eric Nelson
@ 2013-10-14 9:40 ` Jose Mª Ferreiro
2013-10-15 0:30 ` HDMI on SABRE Lite (was FlexCAN not working) Eric Nelson
0 siblings, 1 reply; 10+ messages in thread
From: Jose Mª Ferreiro @ 2013-10-14 9:40 UTC (permalink / raw)
To: meta-freescale
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
El 12/10/2013 0:11, Eric Nelson escribió:
> On 10/11/2013 11:55 AM, Jose Mª Ferreiro wrote:
> <snip>
>>
>> You are correct. I didn´t look well for it. It seems as it depends on a
>> third GPIO signal to select one transceiver or the other. We will test
>> it on monday.
>>
>> I would like to use linux-boundary, wich was the default, but we have to
>> change to linux-imx due to video issues that did not work on
>> linux-boundary: something about mfw_isink i think.
>>
>
> Can you elaborate? I'm not aware of any board-specific code in
> mfw_isink, and certainly not in the Nitrogen6x code.
Hi and sorry, Eric
I was wrong. We were testing several things at the time. The problem was
not with mfw_isink. The problem was with HDMI. We have a Samsung
S22B300H monitor connected to our Sabrelite board through HDMI.
When linux-boundary is starting it shows many hdmi messages until it
gets hanged when trying to start XServer. At both resolutions: 1920x1080
and 1280x720 (attached startup log). With linux-imx, it starts without
problems and the image is good.
If we connect a DVI monitor to the HDMI SabreLite output we can work
with linux-boundary at 1280x 720 but we have no image with 1920x1080.
Thank you
[-- Attachment #2: startup-linux-boundary.txt --]
[-- Type: text/plain, Size: 28620 bytes --]
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.0.35-4.1.0+yocto-horus2+g5809938 (horus@ubuntu) (gcc version 4.8.1 (GCC) ) #4 SMP PREEMPT Mon Oct 14 09:17:16 CEST 2013
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Boundary Devices Nitrogen6X/SABRE Lite Board
Memory policy: ECC disabled, Data cache writealloc
CPU identified as i.MX6Q, silicon rev 1.2
PERCPU: Embedded 7 pages/cpu @8c008000 s5440 r8192 d15040 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227328
Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk0p2 rootwait rw video=mxcfb0:dev=hdmi,1920x1080M@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: 640MB 256MB = 896MB total
Memory: 900748k/900748k available, 147828k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xf4600000 - 0xffe00000 ( 184 MB)
vmalloc : 0xc0800000 - 0xf2000000 ( 792 MB)
lowmem : 0x80000000 - 0xc0000000 (1024 MB)
pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)
modules : 0x7f000000 - 0x7fe00000 ( 14 MB)
.init : 0x80008000 - 0x8003a000 ( 200 kB)
.text : 0x8003a000 - 0x806d20b0 (6753 kB)
.data : 0x806d4000 - 0x8072b5c0 ( 350 kB)
.bss : 0x8072b5e4 - 0x8076f924 ( 273 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:624
MXC GPIO hardware
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
arm_max_freq=1GHz
MXC_Early serial console at MMIO 0x21e8000 (options '115200')
bootconsole [ttymxc1] enabled
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
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
CPU1: Booted secondary processor
CPU2: Booted secondary processor
CPU3: Booted secondary processor
Brought up 4 CPUs
SMP: Total of 4 processors activated (6324.22 BogoMIPS).
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
------------ Board type Sabre Lite
imx_add_mxc_pwm:pdata= (null)
imx_add_mxc_pwm:pdata= (null)
imx_add_mxc_pwm:pdata=806f71d8
imx_add_mxc_pwm:pdata= (null)
Flexcan NXP tja1040
hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
hw-breakpoint: maximum watchpoint size is 4 bytes.
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B
bio: create slab <bio-0> at 0
print_constraints: VDDA: 2500 mV
print_constraints: VDDIO: 3300 mV
machine_constraints_voltage: VDDD: unsupportable voltage constraints
reg-fixed-voltage reg-fixed-voltage.2: Failed to register regulator: -22
reg-fixed-voltage: probe of reg-fixed-voltage.2 failed with error -22
print_constraints: vmmc: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
spi_imx imx6q-ecspi.0: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Version 1.0.24.
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
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
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.
Static Power Management for Freescale i.MX6
wait mode is enabled for i.MX6
cpaddr = c0880000 suspend_iram_base=c0918000
PM driver module loaded
iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.
PCIE: imx_pcie_pltfm_probe start link up.
link up failed, DB_R0:0x00665e00, DB_R1:0x08200000!
IMX PCIe port: link down!
IMX usb wakeup probe
add wake up source irq 75
IMX usb wakeup probe
cpu regulator mode:ldo_enable
i.MXC CPU frequency driver
squashfs: version 4.0 (2009/01/31) Phillip Lougher
msgmni has been set to 1759
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
MIPI DSI driver module loaded
mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi
mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
fbcvt: 1920x1080@60: CVT Name - 2.073M9
ipu_init_sync_panel: disp=1, pixel_clk=148500000 148500000
imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
ipu_init_sync_panel: disp=1, pixel_clk=148500000 148500000
Console: switching to colour frame buffer device 240x67
mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver lcd
ipu_init_sync_panel: disp=0, pixel_clk=27000000 27000000
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver ldb
_regulator_get: get() with no identifier
ldb_disp_init: ret=3, 1280x800
ldb_disp_init:r=59, x=1280, y=800, p=14065, l=40, r=40, upper=10, lower=3, h=80, v=10
ldb_disp_init: 1024x768
ipu_init_sync_panel: disp=0, pixel_clk=71098000 71458646
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 24(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 25(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 26(VIC 31):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 27(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 28(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 29(VIC 3):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 30(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 31(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 32(VIC 3):
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
fbcvt: 1920x1080@60: CVT Name - 2.073M9
ipu_init_sync_panel: disp=1, pixel_clk=25175000 25142857
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x00800000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000
mxc_sdc_fb mxc_sdc_fb.3: register mxc display driver ldb
ldb_disp_init: ret=3, 1280x800
ldb_disp_init:r=59, x=1280, y=800, p=14065, l=40, r=40, upper=10, lower=3, h=80, v=10
ldb_disp_init: 1024x768
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x00800000
ipu_init_sync_panel: disp=1, pixel_clk=148500000 148500000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00080000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x10000000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
ipu_init_sync_panel: disp=1, pixel_clk=71098000 71458646
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
old_ufcr=a81 new_ufcr=b01, old_ucr2=4027 new_ucr2=4027, old_ubir=f num=1f7, old_ubmr=15b denom=c34
clk=80000000 div=7 num=504 denom=3125 baud=115200
console [ttymxc1] enabled, bootconsole disabled
console [ttymxc1] enabled, bootconsole disabled
loop: module loaded
No sata disk.
m25p80 spi0.0: sst25vf016b (2048 Kbytes)
Creating 3 MTD partitions on "m25p80":
0x000000000000-0x0000000c0000 : "bootloader"
0x0000000c0000-0x0000000c2000 : "ubparams"
0x0000000c2000-0x000000200000 : "unused"
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
flexcan imx6q-flexcan.0: device registered (reg_base=c09a8000, irq=142)
FEC Ethernet Driver
fec_enet_mii_bus: probed
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 72
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
USB Serial support registered for Qualcomm USB modem
usbcore: registered new interface driver qcserial
ARC USBOTG Device Controller driver (1 August 2005)
mousedev: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
tsc2004_prepare_for_reading: write_cmd -5
tsc2004: probe of 2-0048 failed with error -5
egalax_ts 2-0004: egalax_ts: 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: Oct 14 2013
check_alarm_past: alarm in the past
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video21
i2c-core: driver [mma8450] using legacy suspend method
i2c-core: driver [mma8450] using legacy resume method
add mma8450 i2c driver
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCILL protocol initialized
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
sdhci sdhci-esdhc-imx.3: no write-protect pin available!
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.3] using DMA
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
VPU initialized
mxc_asrc registered
Galcore version 4.6.9.6622
Thermal calibration data is 0x59c5007d
Thermal sensor with ratio = 186
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
sgtl5000 0-000a: Failed to get supply 'VDDD': -19
print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal
sgtl5000 0-000a: sgtl5000 revision 17
usb 2-1: new high speed USB device number 2 using fsl-ehci
mmc0: new high speed SDHC card at address 0007
mmcblk0: mmc0:0007 SD4GB 3.67 GiB
mmcblk0: p1 p2
asoc: sgtl5000 <-> imx-ssi.1 mapping ok
asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok
ALSA device list:
#0: sgtl5000-audio
#1: imx-hdmi-soc
NET: Registered protocol family 26
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 3 ports detected
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
usb 2-1.1: new low speed USB device number 3 using fsl-ehci
input: Dell Dell USB Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.1/2-1.1:1.0/input/input1
generic-usb 0003:413C:2003.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-fsl-ehci.1-1.1/input0
usb 2-1.2: new low speed USB device number 4 using fsl-ehci
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 200K
input: PIXART USB OPTICAL MOUSE as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2:1.0/input/input2
generic-usb 0003:093A:2510.0002: input,hidraw1: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-fsl-ehci.1-1.2/input0
INIT: version 2.88 booting
Starting udev
udevd[1424]: starting version 182
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
Starting Bootlog daemon: bootlogd.
Populating dev cache
ALSA: Restoring mixer settings...
No state is present for card sgtl5000audio
Found hardware: "sgtl5000-audio" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card sgtl5000audio
No state is present for card imxhdmisoc
Found hardware: "imx-hdmi-soc" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card imxhdmisoc
Configuring network interfaces... eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=1:06, irq=284)
udhcpc (v1.21.1) started
Sending discover...
PHY: 1:06 - Link is Up - 100/Full
Sending discover...
Sending select for 172.30.250.53...
Lease of 172.30.250.53 obtained, lease time 345600
/etc/udhcpc.d/50default: Adding DNS 172.30.250.122
done.
Starting rpcbind daemon...rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
done.
Mon Oct 14 08:15:00 UTC 2013
Running postinst /etc/rpm-postinsts/debianutils...
Running postinst /etc/rpm-postinsts/kernel-image-3.0.35-4.1.0+yocto-masterimxhorus+gbdde708...
Running postinst /etc/rpm-postinsts/kernel-image-3.11.1-fslc+ga318c1d...
Running postinst /etc/rpm-postinsts/kernel-module-binfmt-misc...
Running postinst /etc/rpm-postinsts/kernel-module-configfs...
Running postinst /etc/rpm-postinsts/kernel-module-crc-ccitt...
Running postinst /etc/rpm-postinsts/kernel-module-crc-itu-t...
Running postinst /etc/rpm-postinsts/kernel-module-crc7...
Running postinst /etc/rpm-postinsts/kernel-module-evbug...
Running postinst /etc/rpm-postinsts/kernel-module-g-ether...
Running postinst /etc/rpm-postinsts/kernel-module-g-file-storage...
Running postinst /etc/rpm-postinsts/kernel-module-g-serial...
Running postinst /etc/rpm-postinsts/kernel-module-i2c-algo-pca...
Running postinst /etc/rpm-postinsts/kernel-module-i2c-algo-pcf...
Running postinst /etc/rpm-postinsts/kernel-module-isofs...
Running postinst /etc/rpm-postinsts/kernel-module-libcrc32c...
Running postinst /etc/rpm-postinsts/kernel-module-msdos...
Running postinst /etc/rpm-postinsts/kernel-module-nls-iso8859-15...
Running postinst /etc/rpm-postinsts/kernel-module-nls-utf8...
Running postinst /etc/rpm-postinsts/kernel-module-psmouse...
Running postinst /etc/rpm-postinsts/kernel-module-serport...
Running postinst /etc/rpm-postinsts/kernel-module-udf...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
Removing any system startup links for run-postinsts ...
/etc/rcS.d/S99run-postinsts
INIT: Entering runlevel: 5
Starting Xserver
Starting system message bus: dbus.
Starting Connection Manager
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x10800000
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00180000
ipu_init_sync_panel: disp=1, pixel_clk=148500000 148500000
mxc_hdmi mxc_hdmi: same edid
mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 24(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 25(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 26(VIC 31):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 27(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 28(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 29(VIC 3):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 30(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 31(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 32(VIC 3):
mxc_hdmi mxc_hdmi: same edid
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 24(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 25(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 26(VIC 31):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 27(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 28(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 29(VIC 3):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 30(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 31(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 32(VIC 3):
eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=1:06, irq=284)
Starting OpenBSD Secure Shell server: sshd
generating ssh RSAimx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x00800000
key...
imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000
ipu_init_sync_panel: disp=1, pixel_clk=148500000 148500000
mxc_hdmi mxc_hdmi: same edid
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 0(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 1(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 2(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 3(VIC 1):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 4(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 5(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 6(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 7(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 8(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 9(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 10(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 11(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 12(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 13(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 14(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 15(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 16(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 17(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 18(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 19(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 20(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 21(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 22(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 23(VIC 0):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 24(VIC 16):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 25(VIC 4):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 26(VIC 31):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 27(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 28(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 29(VIC 3):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 30(VIC 19):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 31(VIC 18):
mxc_hdmi mxc_hdmi: mxc_hdmi_edid_rebuild_modelist: Added mode 32(VIC 3):
pwm_config: pwm freq = 32786, clk_select=2 clock_rate=22000000
pwm_config: pwm freq = 20000, clk_select=2 clock_rate=22000000
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: HDMI on SABRE Lite (was FlexCAN not working)
2013-10-14 9:40 ` Jose Mª Ferreiro
@ 2013-10-15 0:30 ` Eric Nelson
0 siblings, 0 replies; 10+ messages in thread
From: Eric Nelson @ 2013-10-15 0:30 UTC (permalink / raw)
To: Jose Mª Ferreiro, meta-freescale
Hi Jose,
On 10/14/2013 02:40 AM, Jose Mª Ferreiro wrote:
>
> El 12/10/2013 0:11, Eric Nelson escribió:
>> On 10/11/2013 11:55 AM, Jose Mª Ferreiro wrote:
>> <snip>
>>>
>>> You are correct. I didn´t look well for it. It seems as it depends on a
>>> third GPIO signal to select one transceiver or the other. We will test
>>> it on monday.
>>>
>>> I would like to use linux-boundary, wich was the default, but we have to
>>> change to linux-imx due to video issues that did not work on
>>> linux-boundary: something about mfw_isink i think.
>>>
>>
>> Can you elaborate? I'm not aware of any board-specific code in
>> mfw_isink, and certainly not in the Nitrogen6x code.
>
> Hi and sorry, Eric
>
> I was wrong. We were testing several things at the time. The problem was
> not with mfw_isink. The problem was with HDMI. We have a Samsung
> S22B300H monitor connected to our Sabrelite board through HDMI.
>
Okay, so we switched topics here.
> When linux-boundary is starting it shows many hdmi messages until it
> gets hanged when trying to start XServer. At both resolutions: 1920x1080
> and 1280x720 (attached startup log). With linux-imx, it starts without
> problems and the image is good.
>
From the log, it appears that the HDMI driver is detecting a disconnect
and re-connect.
If you're not seeing this with the fslc kernel, the problem must stem
from this patch, which added support for DVI monitors into the
HDMI driver:
https://github.com/boundarydevices/linux-imx6/commit/c0439e262bb6c23887d96466b2ab7916aa0488d9
> If we connect a DVI monitor to the HDMI SabreLite output we can work
> with linux-boundary at 1280x 720 but we have no image with 1920x1080.
>
That's odd. We put this patch in place to support DVI. On the older
fslc kernel, most DVI monitors would fail the detect logic as described
here:
http://boundarydevices.com/dvi-support-on-i-mx6-boards/
Are you in a position to revert the patch above?
Do you see the Linux penguins during the boot process?
If so, I've been wanting to test a patch to ignore disconnect
events and this may be a good time to do so. Since many of our
customers are operating signage apps and the like, it's useful
to simply force detection and be done with the process.
Please advise,
Eric
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: FlexCAN not working
2013-10-11 11:28 FlexCAN not working diego
2013-10-11 15:16 ` Eric Nelson
@ 2013-10-18 11:33 ` diego
1 sibling, 0 replies; 10+ messages in thread
From: diego @ 2013-10-18 11:33 UTC (permalink / raw)
To: meta-freescale
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
El 11/10/2013 13:28, diego escribió:
> Hello everybody,
>
> I'm trying to test FlexCAN on Sabrelite imx6 board without success.
> Those are the steps followed :
>
> 1) Comprobed that linux-imx has CAN drivers enable
> 2) Added on the image the packages:canutils,libsocketcan and iproute2
> 3) Tested the Flex can with canconfig and cantest.
>
> Everything seems ok, even I can see transmitted frames incremented.
> However there's not singnal on the oscilloscope.
>
> I don't now why is not working. Any ideas or suggestions?
>
> Thank you!
>
>
>
Hello,
we discovered why is not working. If you are using _*linux-imx*_ the
problem is on board-mx6q_sabrelite.c. This file is not ready to work
with TJA1040 transceiver. However, after reading the datasheet we found
the solution . Change this line :
https://github.com/imx6-dongle/linux-imx/blob/imx_3.0.35_1.1.0-hdmidongle/arch/arm/mach-mx6/board-mx6q_sabrelite.c?source=cc#L754
to
if (!enable)
bitbake and that's all. It's working now on my sabre lite with socketcan.
Regards
--
Diego González González
Dpto. de Control Industrial
HORUS HARDWARE S.A.
Pol Ind Europolis C/Berna nº4
28232 Las Rozas de Madrid
diego.gonzalez@horus.es
[-- Attachment #2: Type: text/html, Size: 2339 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2013-10-18 11:33 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-11 11:28 FlexCAN not working diego
2013-10-11 15:16 ` Eric Nelson
2013-10-11 18:15 ` Jose Mª Ferreiro
2013-10-11 18:41 ` Eric Nelson
2013-10-11 18:55 ` Jose Mª Ferreiro
2013-10-11 20:56 ` Wayne T. Schellekens
2013-10-11 22:11 ` Eric Nelson
2013-10-14 9:40 ` Jose Mª Ferreiro
2013-10-15 0:30 ` HDMI on SABRE Lite (was FlexCAN not working) Eric Nelson
2013-10-18 11:33 ` FlexCAN not working diego
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.