This thread has been locked.

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

Green Background in Qt fancybrowser

Hi,

 I tried to launch Qt Fancybrowser in DM814x EVM and the browser window launches wih the green background behind. Please help me on what could be the reason for this green background?


  • Hello,

    I have tried it on EVM with EZSDK and I am not seeing the green screen.
    Probably you are seeing it because somewhere it is set to green.
    You could try to search in the code.

    Best Regards,
    Margarita
  • Can you please try launching it in /dev/fb1
  • Hi Margarita,

      This is an issue in ezsdk. I took a fresh ezsdk  and booted up the EVM. The browser launched from MatrixGUI is fine. But when we try to launch Qt fancybrowser in LCD as well as in HDMI, we get the green background as shown in the picture

    This happens for all graphics pipeline. either it is /dev/fb0 or /dev/fb1

    root@dm814x-evm:/usr/bin/qtopia/examples/webkit/fancybrowser# ./fancybrowser -qws http://www.google.co.in

    Please find the logs below

    RCM Initialization completed
    SysLink version : 2.20.02.20
    SysLink module created on Date:Dec 26 2012 Time:18:39:49
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    Firmware Loader debugging not configured
    Default FL_DEBUG: warning
    Allowed FL_DEBUG levels: error, warning, info, debug, log
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    davinci_mdio davinci_mdio.0: timed out waiting for user access
    FIRMWARE: 1 start Successful
    Loading HDVPSS Firmware
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    Firmware Loader debugging not configured
    Default FL_DEBUG: warning
    Allowed FL_DEBUG levels: error, warning, info, debug, log
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    FIRMWARE: 2 start Successful
    VPSS_FVID2: M3 firmware version 0x1000145 is newer,driver may not work properly.
    HDMI W1 rev 4.0
    HDMI CEC Spec version 1.2
    Starting system message bus: dbus.
    Starting Dropbear SSH server: dropbear.
    Starting telnet daemon.
    Starting network benchmark server: netserver.
    Starting syslogd/klogd: done
    Starting thttpd.
    Starting PVR
    /dev/mem opened.
    Memory mapped at address 0x402b9000.
    Read at address 0x48180F04 (0x402b9f04): 0x00000001
    Write at address 0x48180F04 (0x402b9f04): 0x00000000, readback 0x00000000
    /dev/mem opened.
    Memory mapped at address 0x4030f000.
    Read at address 0x48180900 (0x4030f900): 0x00000102
    Write at address 0x48180900 (0x4030f900): 0x00000002, readback 0x00000002
    /dev/mem opened.
    Memory mapped at address 0x40272000.
    Read at address 0x48180920 (0x40272920): 0x00040002
    Write at address 0x48180920 (0x40272920): 0x00000002, readback 0x00000002
    Starting Matrix GUI application.

    _____ _____ _ _
    | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
    | | _| .'| . | . | | __| _| . | | | -_| _| _|
    |__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
    |___| |___|

    Arago Project http://arago-project.org dm814x-evm ttyO0

    Arago 2011.09 dm814x-evm ttyO0

    dm814x-evm login: root
    root@dm814x-evm:~#
    root@dm814x-evm:~#
    root@dm814x-evm:~#
    root@dm814x-evm:~# cd /usroot@dm814x-evm:~# cd /usr/[J
    root@dm814x-evm:/usr# cd bin/qtopia/examples/webkit/fancybrowser
    root@dm814x-evm:/usr/bin/qtopia/examples/webkit/fancybrowser# ./fancybrowser -qw
    s http://www.google.co.in

    root@dm814x-evm:/usr/bin/qtopia/examples/webkit/fancybrowser#

    Thanks and Regards,

    Subha.V

  • Hello,

    I have ran it on the EVM with LCD, I still doesn't see any green issue.

    Best Regards,
    Margarita
  • Hi,

    If you launch browser from Matrix GUI we do not get it. But when you launch browser standalone not with Matrix GUI, we get the green background.
    I had upgraded QT also to check whether this issue is with Qt. But the green background persists

    Can you please run fancybrowser standalone as mentioned below

    root@dm814x-evm:/usr# cd bin/qtopia/examples/webkit/fancybrowser
    root@dm814x-evm:/usr/bin/qtopia/examples/webkit/fancybrowser# ./fancybrowser -qw
    s http://www.google.co.in

    Please provide me suggestions on how this can be avoided.

    Thanks and Regards,
    Subha.V
  • Hello,

    I am able to reproduce it when the MATRIX GUI is stopped.
    I will check and I will let you know.

    Best Regards,
    Margarita
  • Thanks Margarita. it would be very helpful