iMX6 SabreLite board Android issue : surfaceFlinger service crash when HDMI is not connected

[harsh_shah]

I m running Android 4.3 on BD-SL-i.MX6 ( http://boundarydevices.com/product/sabre-lite-imx6-sbc/ )

It is working properly when HDMI monitor is connected, but if I boot without HDMI connected then surfaceFlinger crashes during bootup and board reboots on it own (probably by watchdog)

How to prevent this crash ? Why is surfaceFlinger service dependent of HDMI ? I have to develop a Camera video streaming project based on Android without any display.

PS : Android version I'm using is http://boundarydevices.com/jb-4-3-ga-mx6/

[saurabh206]

Hi,

Harsh

Can you share you bootargs and crash log?

Saurabh

[harsh_shah]

Please find attached crash log and these are the bootargs :

U-Boot > printenv

baudrate=115200

board=sabrelite

bootcmd=for dtype in $; do if itest.s "xusb" == "x$" ; then usb start ;fi; for disk in 0 1 ; do $ dev $ ;for fs in fat ext2 ; do $load $ $:1 10008000 /6x_bootscript&& source 10008000 ; done ; done ; done; setenv stdout serial,vga ; echo ; ec ho 6x_bootscript not found ; echo ; echo serial console at 115200, 8N1 ; echo ; echo details at http://boundarydevices.com/6q_bootscript ; seten v stdin serial,usbkbd bootdelay=1 bootdevs=sata mmc usb clearenv=if sf probe || sf probe || sf probe 1 ; then sf erase 0xc0000 0x2000 && echo restored environment to factory default ; fi console=ttymxc1 cpu=6Q ethact=FEC ethaddr=00:19:b8:01:5e:26 ethprime=FEC fdt_addr=0x11000000 fdt_high=0xffffffff loadaddr=0x12000000 loadsplash=if sf probe ; then sf read $ c2000 $ ; fi upgradeu=for dtype in $; do for disk in 0 1 ; do $ dev $ ;for fs in fat ext2 ; do $load $ $:1 10008000 /

6x_upgrade && source 10008000 ; done ; done ; done

usbnet_devaddr=00:19:b8:00:00:02

usbnet_hostaddr=00:19:b8:00:00:01

usbrecover=setenv ethact usb_ether; setenv ipaddr 10.0.0.2; setenv

netmask 255.255.255.0; setenv serverip 10.0.0.1; setenv bootargs

console=ttym

xc1,115200; tftpboot 10800000 10.0.0.1:uImage-$-recovery&& tftpboot 12800000 10.0.0.1:uramdisk-$-recovery.img && bootm

10800000 12

800000

[EricNelson]

I think you'll need a display in order to run Android without some pretty major hacking.

You can probably define a small(ish) display using the LVDS or RGB ports in the interim by hacking the boot script.