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.

Framebuffer sometimes is set to wrong virtual resolution after bootup

Other Parts Discussed in Thread: TLC59108

I'm using DM8148 with EZSDK 5.05.02.00 with 800x480 LCD on dvo2. Sometimes (about 1 in 10 bootups), fb0 ends up set incorrectly resulting in a chopped up image. When the problem occurs, the framebuffer virtual resolution is set to 1920x1080 instead of the normal 800x1440, with the image resolution always being the correct 800x480.

How do I fix it so it always boots with the proper settings?

Here's an example of the problem. There should be a window on the right side. As you can see, the video from OMX works fine..
http://i.imgur.com/8y2YQBf.jpg


Normally fbset results in

mode "800x480-60"
    # D: 33.501 MHz, H: 31.515 kHz, V: 60.259 Hz
    geometry 800 480 800 1440 32
    timings 29850 89 164 23 10 10 10
    rgba 8/16,8/8,8/0,8/24
endmode

But on a boot where the problem occurs, it results in

mode "800x480-262"
    # D: 148.500 MHz, H: 137.500 kHz, V: 261.905 Hz
    geometry 800 480 1920 1080 32
    timings 6734 148 88 36 4 44 5
    rgba 8/16,8/8,8/0,8/24
endmode

When it's wrong, the following command fixes it

fbset -fb /dev/fb0 -xres 800 -yres 480 -vxres 800 -vyres 1440

My load-hd-firmware.sh is

...
configure_lcd()
{
    echo "Configuring fb0 to LCD"
    echo 1:dvo2 > /sys/devices/platform/vpss/graphics0/nodes
    echo 0 > /sys/devices/platform/vpss/display1/enabled
    echo 33500,800/164/89/10,480/10/23/10,1 > /sys/devices/platform/vpss/display1/timings
    echo triplediscrete,rgb888 > /sys/devices/platform/vpss/display1/output
    echo 1 > /sys/devices/platform/vpss/display1/enabled
    fbset -xres 800 -yres 480 -vxres 800 -vyres 480
}


case "$1" in
    start)
        echo "Loading HDVICP2 Firmware"
        prcm_config_app s
        modprobe syslink
        until [[ -e /dev/syslinkipc_ProcMgr && -e /dev/syslinkipc_ClientNotifyMgr ]]
        do                                                
            sleep 0.5
        done
        firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 start -i2c 0
        echo "Loading HDVPSS Firmware"
        firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 start -i2c 0
    modprobe vpss sbufaddr=0xBFB00000 mode=dvo2:800x480@60 i2c_mode=0

        modprobe ti81xxfb vram=0:24M,1:16M,2:6M
        configure_lcd
        modprobe ti81xxhdmi
...

  • Hello,

    Are you using EVM or custom board?
    Could you provide the steps how can be reproduced since on EVM I have not seen such problem.

    Best Regards,
    Margarita
  • Hello,

    This is the default script in EZSDK for loading the firmwares and lcd config:

    PATH=$PATH:/usr/share/ti/ti-media-controller-utils
    HDVICP2_ID=1
    HDVPSS_ID=2

    configure_lcd()
    {
    echo "Configuring fb0 to LCD"
    echo 1:dvo2 > /sys/devices/platform/vpss/graphics0/nodes
    echo 0 > /sys/devices/platform/vpss/display1/enabled
    echo 33500,800/164/89/10,480/10/23/10,1 > /sys/devices/platform/vpss/display1/timings
    echo triplediscrete,rgb888 > /sys/devices/platform/vpss/display1/output
    echo 1 > /sys/devices/platform/vpss/display1/enabled
    fbset -xres 800 -yres 480 -vxres 800 -vyres 480
    }


    case "$1" in
    start)
    echo "Loading HDVICP2 Firmware"
    prcm_config_app s
    modprobe syslink
    until [[ -e /dev/syslinkipc_ProcMgr && -e /dev/syslinkipc_ClientNotifyMgr ]]
    do
    sleep 0.5
    done
    firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 start
    echo "Loading HDVPSS Firmware"
    firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 start
    modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-60 i2c_mode=1
    modprobe ti81xxfb vram=0:24M,1:16M,2:6M
    configure_lcd
    modprobe ti81xxhdmi
    modprobe tlc59108
    ;;
    stop)
    echo "Unloading HDVICP2 Firmware"
    firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 stop
    echo "Unloading HDVPSS Firmware"
    rmmod tlc59108
    rmmod ti81xxhdmi
    rmmod ti81xxfb
    rmmod vpss
    firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 stop
    rm /tmp/firmware.$HDVPSS_ID
    rmmod syslink
    ;;
    *)
    echo "Usage: /etc/init.d/load-hd-firmware.sh {start|stop}"
    exit 1
    ;;
    esac

    exit 0

    Regards,
    Margarita
  • Hi Margarita,

    This is on a custom board. It's very difficult to reproduce, it occurs infrequently and seemingly at random. Rebooting your board 20 or 30 times should reproduce it if the problem exists on your board.

    That was the exact script I was using initially, I didn't paste the bottom (stop) half in my post. I have changed it from mode=hdmi:1080p-60 to mode=dvo2:800x480@60, thinking this may have been affecting the framebuffer, but it made no difference. The problem still occurred when I had the completely stock file as you posted.

    Do you think the problem is some sort of race condition between two startup init processes finishing, or perhaps something to do with pvr_init which also uses fbset? I'm not using PVR but there is a problem with the pvr_init script not finding the kernel modules, could that have anything to do with it?

    I'm getting the following error:

    Starting PVR
    Usage: insmod filename [args]
    FATAL: Module omaplfb not found.
    FATAL: Module bufferclass_ti not found.
    BusyBox v1.13.2 (2012-12-26 15:45:54 IST) multi-call binary


    My boot console log is shown below:

    Starting kernel ...
    
    Uncompressing Linux... done, booting the kernel.
    Linux version 2.6.37 (david@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #58 Fri Feb 20 19:56:34 PST 2015
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: ti8148evm
    bootconsole [earlycon0] enabled
    reserved size = 52428800 at 0x0
    FB: Reserving 52428800 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP chip is TI8148 2.1
    SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 160648
    Kernel command line: console=ttyO4,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=364M@0x80000000 mem=320M@0x9FC00000 vmalloc=500M earlyprintk notifyk.vpssm3_sva=0xBF900000 root=/dev/nfs nfsroot=192.168.0.103:/home/david/targetfs ip=dhcp
    PID hash table entries: 2048 (order: 1, 8192 bytes)
    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    Memory: 364MB 270MB = 634MB total
    Memory: 637524k/637524k available, 62892k reserved, 276480K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
        vmalloc : 0xd7000000 - 0xf8000000   ( 528 MB)
        lowmem  : 0xc0000000 - 0xd6c00000   ( 364 MB)
        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
        modules : 0xbf000000 - 0xbfe00000   (  14 MB)
          .init : 0xc0008000 - 0xc003b000   ( 204 kB)
          .text : 0xc003b000 - 0xc0522000   (5020 kB)
          .data : 0xc0522000 - 0xc05668c0   ( 275 kB)
    SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    NR_IRQS:375
    IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
    Total of 128 interrupts on 1 active controller
    GPMC revision 6.0
    Trying to install interrupt handler for IRQ368
    Trying to install interrupt handler for IRQ369
    Trying to install interrupt handler for IRQ370
    Trying to install interrupt handler for IRQ371
    Trying to install interrupt handler for IRQ372
    Trying to install interrupt handler for IRQ373
    Trying to install interrupt handler for IRQ374
    Trying to install type control for IRQ375
    Trying to set irq flags for IRQ375
    OMAP clockevent source: GPTIMER1 at 20000000 Hz
    Console: colour dummy device 80x30
    Calibrating delay loop... 719.25 BogoMIPS (lpj=3596288)
    pid_max: default: 32768 minimum: 301
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    devtmpfs: initialized
    omap_voltage_early_init: voltage driver support not added
    regulator: core version 0.5
    regulator: dummy:
    NET: Registered protocol family 16
    omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
    omap_voltage_add_dev: VDD specified does not exist!
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    omap_mux_init: Add partition: #1: core, flags: 4
    TSC IRQ Init
    Attempting to mux I2C bus 3
    _omap_mux_init_gpio: Could not set gpio14
    _omap_mux_init_gpio: Could not set gpio13
    omap_hsmmc_reset
    omap_init_camera
    omap_init_mbox
    omap_init_mcspi
    omap_init_elm
    omap_init_pmu
    omap_hdq_init
    omap_init_sti
    omap_init_sham
    omap_init_aes
    omap_init_vout
    ti814x_sata_pllcfg
    ti81xx_ethernet_init
    ti81xx_init_pcie
    ti81xx_register_edma
    ti81xx_init_pcm
    ti816x_sr_init
    ti81xx_video_mux
    ti814x_enable_i2c2
    omap_init_ahci
    ti81xx_rtc_init
    Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
    registered ti81xx_vpss device
    registered ti81xx_vidout device
    registered ti81xx on-chip HDMI device
    registered ti81xx_fb device
    registered ti81xx_vin device
    bio: create slab <bio-0> at 0
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    USBSS revision 4ea2080b
    registerd cppi-dma Intr @ IRQ 17
    Cppi41 Init Done
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    pcf857x: probe of 1-0021 failed with error -121
    tps65910 1-002d: No interrupt support, no core IRQ
    omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz
    Advanced Linux Sound Architecture Driver Version 1.0.23.
    Switching to clocksource gp timer
    musb-hdrc: version 6.0, host, debug=0
    musb-hdrc musb-hdrc.0: dma type: dma-cppi41
    MUSB controller-0 revision 4ea20800
    musb-hdrc musb-hdrc.0: MUSB HDRC host driver
    musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb1: Product: MUSB HDRC host driver
    usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
    usb usb1: SerialNumber: musb-hdrc.0
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    musb-hdrc musb-hdrc.0: USB Host mode controller at d701e000 using DMA, IRQ 18
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    MUSB controller-1 revision 4ea20800
    musb-hdrc musb-hdrc.1: MUSB HDRC host driver
    musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
    usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb2: Product: MUSB HDRC host driver
    usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
    usb usb2: SerialNumber: musb-hdrc.1
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    musb-hdrc musb-hdrc.1: USB Host mode controller at d7028800 using DMA, IRQ 19
    NET: Registered protocol family 2
    IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
    TCP established hash table entries: 65536 (order: 7, 524288 bytes)
    TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
    TCP: Hash tables configured (established 65536 bind 65536)
    TCP reno registered
    UDP hash table entries: 256 (order: 0, 4096 bytes)
    UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    NET: Registered protocol family 1
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    NetWinder Floating Point Emulator V0.97 (double precision)
    PMU: registered new PMU device of type 0
    omap-iommu omap-iommu.0: ducati registered
    omap-iommu omap-iommu.1: sys registered
    highmem bounce pool size: 64 pages
    NTFS driver 2.1.29 [Flags: R/W].
    JFFS2 version 2.2. (NAND) c 2001-2006 Red Hat, Inc.
    msgmni has been set to 705
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
    omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
    omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
    omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
    omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
    console [ttyO4] enabled, bootconsole disabled
    console [ttyO4] enabled, bootconsole disabled
    omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
    brd: module loaded
    loop: module loaded
    ahci ahci.0: forcing PORTS_IMPL to 0x1
    ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
    scsi0 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    davinci_mdio davinci_mdio.0: detected phy mask fffffffe
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
    CAN device driver interface
    CAN bus driver for Bosch D_CAN controller 1.0
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver dm9601
    usbcore: registered new interface driver cdc_acm
    cdc_acm: v0.26: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.
    mice: PS/2 mouse device common for all mice
    usb 2-1: new high speed USB device using musb-hdrc and address 2
    input: st1232-touchscreen as /devices/platform/omap/omap_i2c.3/i2c-3/3-0055/input/input0
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    rtc-s35390a 1-0030: rtc core: registered rtc-s35390a as rtc1
    i2c /dev entries driver
    Linux video capture interface: v2.00
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v1.0.0)
    OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbf900000
    usbcore: registered new interface driver snd-usb-audio
    asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
    ALSA device list:
      #0: TI81XX EVM
    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)
    Registering the dns_resolver key type
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    omap_voltage_late_init: Voltage driver support not added
    Power Management for TI81XX.
    Detected MACID=50:56:63:b8:cf:ae
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    mmc0: new high speed SDHC card at address 1234
    mmcblk0: mmc0:1234 SA04G 3.67 GiB
     mmcblk0: p1 p2
    usb 2-1: New USB device found, idVendor=0409, idProduct=0058
    usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    usb 2-1: Product: USB2.0 Hub Controller
    usb 2-1: Manufacturer: NEC Corporation
    hub 2-1:1.0: USB hub found
    hub 2-1:1.0: 4 ports detected
    ata1: SATA link down (SStatus 0 SControl 300)
    mmc1: new high speed SDHC card at address 59b4
    mmcblk1: mmc1:59b4 SD    58.9 GiB
     mmcblk1: p1
    usb 2-1.1: new high speed USB device using musb-hdrc and address 3
    usb 2-1.1: New USB device found, idVendor=058f, idProduct=6387
    usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 2-1.1: Product: Mass Storage Device
    usb 2-1.1: Manufacturer: Generic
    usb 2-1.1: SerialNumber: GYS0MGWP
    
    CPSW phy found : id is : 0x70421
    PHY 0:01 not found
    usb-storage 2-1.1:1.0: Quirks match for vid 058f pid 6387: 400
    scsi1 : usb-storage 2-1.1:1.0
    Sending DHCP requests .
    scsi 1:0:0:0: Direct-Access     JetFlash TS1GJF110        8.07 PQ: 0 ANSI: 2
    sd 1:0:0:0: Attached scsi generic sg0 type 0
    sd 1:0:0:0: [sda] 2007038 512-byte logical blocks: (1.02 GB/979 MiB)
    sd 1:0:0:0: [sda] Write Protect is off
    sd 1:0:0:0: [sda] Assuming drive cache: write through
    sd 1:0:0:0: [sda] Assuming drive cache: write through
     sda: sda1
    sd 1:0:0:0: [sda] Assuming drive cache: write through
    sd 1:0:0:0: [sda] Attached SCSI removable disk
    ..
    PHY: 0:00 - Link is Up - 1000/Full
    ., OK
    IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.0.54
    IP-Config: Complete:
         device=eth0, addr=192.168.0.54, mask=255.255.255.0, gw=192.168.0.254,
         host=192.168.0.54, domain=local, nis-domain=(none),
         bootserver=0.0.0.0, rootserver=192.168.0.103, rootpath=
    VFS: Mounted root (nfs filesystem) on device 0:15.
    devtmpfs: mounted
    Freeing init memory: 204K
    INIT: version 2.86 booting
    Please wait: booting...
    Starting udev
    udevd (71): /proc/71/oom_adj is deprecated, please use /proc/71/oom_score_adj instead.
    FAT: bogus number of reserved sectors
    VFS: Can't find a valid FAT filesystem on dev mmcblk1.
    FAT: bogus number of reserved sectors
    VFS: Can't find a valid FAT filesystem on dev mmcblk0.
    FAT: invalid media value (0x00)
    VFS: Can't find a valid FAT filesystem on dev sda.
    EXT3-fs: barriers not enabled
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): recovery complete
    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    Root filesystem already rw, not remounting
    Caching udev devnodes
    NET: Registered protocol family 10
    ALSA: Restoring mixer settings...
    NOT configuring network interfaces: / is an NFS mount
    INIT: Entering runlevel: 5
    Loading HDVICP2 Firmware
    DM814X prcm_config_app version: 2.0.0.1
    Doing PRCM settings...
            PRCM for IVHD0 is in Progress, Please wait.....
                            BW Phy Addr : 0x48180600 Data : 0x00000001
                            AW Phy Addr : 0x48180600 Data : 0x00000002
                            Phy Addr : 0x48180c04 Data : 0x00000037
                            BW Phy Addr : 0x48180620 Data : 0x00070000
                            AW Phy Addr : 0x48180620 Data : 0x00050002
                            BW Phy Addr : 0x48180624 Data : 0x00030000
                            AW Phy Addr : 0x48180624 Data : 0x00010002
                            Phy Addr : 0x48180600 Data : 0x00000102
                            BW Phy Addr : 0x48180c10 Data : 0x00000007
                            AW Phy Addr : 0x48180c10 Data : 0x00000003
                            Phy Addr : 0x48180c14 Data : 0x00000004
                            BW Phy Addr : 0x58088000 Data : 0xeafffffe
                            AW Phy Addr : 0x58088000 Data : 0xeafffffe
                            BW Phy Addr : 0x58098000 Data : 0xeafffffe
                            AW Phy Addr : 0x58098000 Data : 0xeafffffe
                            BW Phy Addr : 0x48180c10 Data : 0x00000003
                            AW Phy Addr : 0x48180c10 Data : 0x00000000
                            Phy Addr : 0x48180c14 Data : 0x00000007
            PRCM for IVHD0 is Done Successfully
    PRCM Initialization completed
    SysLink version : 2.20.02.20
    SysLink module created on Date:Oct 24 2014 Time:03:34:11
    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: 0
    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: 1 start Successful
    Loading HDVPSS Firmware
    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: 0
    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.
    Configuring fb0 to LCD
    HDMI W1 rev 4.0
    HDMI CEC Spec version 1.2
    I2C No Ack
    
    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
    Usage: insmod filename [args]
    FATAL: Module omaplfb not found.
    FATAL: Module bufferclass_ti not found.
    BusyBox v1.13.2 (2012-12-26 15:45:54 IST) multi-call binary
    
    Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR
    
    Create a special file (block, character, or pipe)
    
    Options:
            -m      Create the special file using the specified mode (default a=rw)
    TYPEs include:
            b:      Make a block device
            c or u: Make a character device
            p:      Make a named pipe (MAJOR and MINOR are ignored)
    
    chmod: /dev/pvrsrvkm: No such file or directory
    /dev/mem opened.
    Memory mapped at address 0x40187000.
    Read at address  0x48180F04 (0x40187f04): 0x00000001
    Write at address 0x48180F04 (0x40187f04): 0x00000000, readback 0x00000000
    /dev/mem opened.
    Memory mapped at address 0x4033d000.
    Read at address  0x48180900 (0x4033d900): 0x00000001
    Write at address 0x48180900 (0x4033d900): 0x00000002, readback 0x00000002
    /dev/mem opened.
    Memory mapped at address 0x400f9000.
    Read at address  0x48180920 (0x400f9920): 0x00070000
    Write at address 0x48180920 (0x400f9920): 0x00000002, readback 0x00000002
    Starting power monitor.
    
     _____                    _____           _         _
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
                  |___|                    |___|
    
    Arago Project http://arago-project.org dm814x-evm ttyO4
    
    Arago 2011.09 dm814x-evm ttyO4

  • Hello,

    Have you checked this page:

    processors.wiki.ti.com/.../TI81XX_PSP_VPSS_Video_Driver_User_Guide
    Configure Application Output to LCD Display

    Best Regards,
    Margarita
  • Hi Margarita,

    The steps listed under "Configure Application Output to LCD Display" are already being done by the load_hd_firmware script, albiet in a different order. Are the steps in the load_hd_firmware script wrong, or should they be executed at another place or time?

    I will try changing the order to match that in the document.

    David
  • Hello David,

    Let me know if this will helps.

    If it fail again I will try to reproduce it on my side:

    Your steps was :

    changing the mode to mode=dvo2:800x480@60 and I shall reboot the board few time, right?

    BR
    Margarita

  • Yes, that's the change I made, although it occurs without that change as well.
  • Hello David,

    David Kronstein said:
    although it occurs without that change as well.

    Since you said that this issue occurs even without your change, I tried on the EVM but I can not reproduce it or may be I just get "lucky" since this is happen only sometimes. I will give a try with your change as well.

    Best Regards,

    Margarita