Linux freezes when connected to HDMI

hi cristian,

I guess you have downloaded from here : https://www.dropbox.com/sh/nuhzba8uqpijenb/AAAt8l9g6u6T6-DOqJHozyKca/fsl-image-fb-riotboard.sdcard?dl=1

If I connect the HDMI after Linux starts running it also freezes.

The HDMI screen freezes or Riotboard booting ??

it only boots if HDMI is not connected.

The HDMI GUI support is not yet enabled in kernel.

on display devices it will show a terminal with Yocto signature as shown below.

If I stop the boot it displays the Freescale logo

if possible, plz share a snapsort  .

Hi,

Just to clarify, I don't want a GUI, my application uses GStreamer to output straight to the framebuffer.

I have tried both the downloaded file and also one that I build with Yocto (fsl-image-fb),  with the same result.

If I have the HDMI cable connected the kernel would not start. Here is the console output:

---------------------------------------------------------------------------------------------------------

U-Boot 2013.04-04988-gd2e8066-dirty (Jul 04 2014 - 09:18:53)

CPU:   Freescale i.MX6SOLO rev1.1 at 792 MHz

CPU:   Temperature 35 C, calibration data: 0x5915165f

Reset cause: POR

Board: MX6SOLO RIoTboard

I2C:   ready

DRAM:  1 GiB

MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2

*** Warning - bad CRC, using default environment

No panel detected: default to HDMI

Display: HDMI (640x480)

In:    serial

Out:   serial

Err:   serial

mmc2(part 0) is current device

Net:   FEC [PRIME]

Warning: failed to set MAC address

Normal Boot

Hit any key to stop autoboot:  0

mmc2(part 0) is current device

reading boot.scr

** Unable to read file boot.scr **

reading uImage

5275824 bytes read in 274 ms (18.4 MiB/s)

Booting from mmc ...

reading imx6solo_RIoTboard.dtb

43553 bytes read in 21 ms (2 MiB/s)

## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.10.17_1.0.0_RIoTboard+g9

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    5275760 Bytes = 5 MiB

   Load Address: 10008000

   Entry Point:  10008000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 18000000

   Booting using the fdt blob at 0x18000000

   Loading Kernel Image ... OK

OK

   Using Device Tree in place at 18000000, end 1800da20

Starting kernel ...

--------------------------------------------------------------------------------------------

If I have the cable initially disconnected it works OK. As soon as I connect the cable Linux freezes. No serial console and the LED stops blinking.

The strange thing is that I have a board that works with no problems at all and another four that behave like I described.

I currently don't have the working board with me to see if there is a hardware difference (however unlikely that is). I should get it back next week.

The software is exactly the same on all.

I have the same problem.  I have 6 boards all flashed with the same u-boot, 3.10 kernel and ubuntu 14.04.

4 of them work great.  Both the serial console and the hdmi work well.

On 1 the serial console does not display anything but the hdmi works.

The last 1 has the same problem described here.  If I plug the hdmi cable it freezes.  From the serial console I am able to see u-boot go but it gets stuck at "Starting kernel ..." just like yours:

U-Boot 2013.04-04992-g002bd44 (Oct 10 2014 - 16:41:48)

CPU:   Freescale i.MX6SOLO rev1.1 at 792 MHz

CPU:   Temperature 41 C, calibration data: 0x5935125f

Reset cause: POR

Board: MX6SOLO RIoTboard

I2C:   ready

DRAM:  1 GiB

MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2

*** Warning - bad CRC, using default environment

No panel detected: default to HDMI

Display: HDMI (640x480)

In:    serial

Out:   serial

Err:   serial

mmc2(part 0) is current device

Net:   FEC [PRIME]

Warning: failed to set MAC address

Normal Boot

Hit any key to stop autoboot:  0

mmc2(part 0) is current device

reading boot.scr

** Unable to read file boot.scr **

reading uImage

5580480 bytes read in 352 ms (15.1 MiB/s)

Booting from mmc ...

reading imx6solo_RIoTboard.dtb

46379 bytes read in 20 ms (2.2 MiB/s)

## Booting kernel from Legacy Image at 12000000 ...

   Image Name:   Linux-3.10.17_1.0.0_RIoTboard-80

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    5580416 Bytes = 5.3 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

OK

   Using Device Tree in place at 18000000, end 1800e52a

Starting kernel ...

About the time I posted my first message I have also contacted Embest via their web site. I got a couple of replies asking for more info, but I haven't heard from them since. I can only assume they don't have an answer or simply don't care.

Since I am developing a commercial product and have no time to muck around  I had to go back to kernel 3.0.35 (using the good old LTIB).

So far, so good. All my boards seem to work OK.

same u-boot, 3.10 kernel and ubuntu 14.04.

I don't think we have a official release for  3.10 kernel with ubuntu 14.04 bsp.

I had to go back to kernel 3.0.35 (using the good old LTIB).

So far, so good. All my boards seem to work OK.

I am unable to generate the HDMI freeze issue.

does this occur after any changes made to bsp or its a custom bsp .

which BSP version you are using ??

tushar panda wrote:

 

I don't think we have a official release for  3.10 kernel with ubuntu 14.04 bsp.

This is the u-boot and linux-img I am using:

git clone https://github.com/embest-tech/u-boot-imx.git -b embest_imx_v2013.04_3.10.17_1.0.0_ga

git clone https://github.com/embest-tech/linux-imx.git -b embest_imx_3.10.17_1.0.0_ga

Since it is getting stuck at loading the kernel I am not sure it is an Ubuntu issue but I may be wrong.

The ubuntu distribution I am using is from the bottom of this page: http://www.armhf.com/download/ I like that it is a bare minimal install without the GUI desktop.

As mentioned above, 5 of my boards do not show this problem at all.  Only 1 and they all have the exact same u-boot, kernel, dtb and rootfs.

Hey guys!

With the help of panda's little tutorial for building a yocto-linux, I managed to build an own linux for riotboard - thanks for that!

Unfortunately I have the same problem as the thread-starter. Linux starts fine without hdmi and is accessible via the debug-uart-tty.

After uboot the following output is given:

Starting kernel ...

 

Booting Linux on physical CPU 0x0

Linux version 3.10.17_1.0.0_RIoTboard+g084d5c3 (flo@thinkpad.localdomain) (gcc version 4.8.1 (GCC) ) #1 SMP PREEMPT Tue Nov 25 14:28:33 CET 2014

CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d

CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Freescale i.MX6 Solo RIoTboard

cma: CMA: reserved 320 MiB at 3c000000

Memory policy: ECC disabled, Data cache writealloc

PERCPU: Embedded 8 pages/cpu @8156f000 s8896 r8192 d15680 u32768

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260096

Kernel command line: console=ttymxc1,115200 nosmp video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32 video=mxcfb1:off fbmem=10M root=/dev/mmcblk1p2 rootwait rw consoleblank=0

... (and so on) ...

As soon I stick in the hdmi cable during boot, the uart-tty freezes. If the cable is mountet at boot, the last I see in minicom is "Starting kernel ..."

The above posts sound like a hardware error to be the cause, not?

Do you maybe have a way out of this problem now? If someone has an idea to be tried by me please mention it !

Thanks!

Cheers

Flo

Hello Tushar

Greetings

From your post I understand that the kernel does not have HDMI support enabled. Could you confirm if BSP Linux Yocto v3.10.17 available at RIoTboard BSP Images and Tools Download - Android and Linux has the same issue too. The booting freezes at "starting kernel" when the HDMI cable is connected.

Regards

Karthik