• State TI Thinks Resolved
  • Locked Locked
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 3864 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux: AM389x, HDMI - LCD panel blacked out.

Hodong Lee
Prodigy 80 points
Other Parts Discussed in Thread: PMP

Tool/software: Linux

Hello.

I have some questions about HDMI at AM389x.

Thank you for your patience. I'm not a english native speaker. But I hope that you may understand what i say very well.

 

1. Issue

I use the board based on AM392x. Some boards are blacked out at the LCD panel. So I want to figure out the reason and find the solving solution.

 

Turn on the board and keep on 2 ~ 6 hour over, The LCD panel turn to black screen(There is no display nothing).

That is not fixed occur time. Every time differ.

 

2. Environments

1) OS: Linux (kernel 2.6)

2) LCD program: nano-X (ver 20110730) & FLTK (ver 1.3.3)

3) Display output: HDMI

4) Connection

   - Board - Scaler board - LCD panel

   - Use HDMI and USB cable.

   - HDMI used for display screen, USB used to receive touch input from LCD.

 

3. Checked information

   1) Compared scoping sign data normal and un-normal state.

     - Scoping point: HDMI data line at scaler board.

     - In un-normal state, I checked the homogeneous sign. So expect that there is no data or received  “0” .

   2) Checked HDMI register value.

     - There is no differ.

     - For more detail information, check upload files.

   3) I reset HDMI by change the reset register. "No signal Input" displayed at LCD around 10 sec. But that string disappeared and show blacked out screen same.

   4) We found some log form "dmesg" and find out timeout.

  

Hdmi: first hpd register device crongfb_drv Ver 0.8.2.0 OK (major = 201)

CMEMK module: built on Jan 7 2013 at 17:27:04

Reference Linux version 2.6.37

File /home/v10528/workspace_svn/crong/eLinux/linuxutils_3_22_00_02/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c

Allocated heap buffer 0x98000000 of size 0x30000000

Cmemk initialized

Syslink-2_10_03_20 / packages / ti / syslink / utils / ti-syslink-2_10_03_20-r4j / ti-sysm-none-linux-gnueabi / Hlos / knl / Linux /../../../../../../ ti / syslink / ipc / hlos / knl / NameServerRemoteNotify.c: ((status == NameServer_S_SUCCESS) = NameServer_E_NOTFOUND)): failed

Syslink-2_10_03_20 / packages / ti / syslink / utils / ti-syslink-2_10_03_20-r4j / ti-sysm-none-linux-gnueabi / Hlos / knl / Linux /../../../../../../ ti / syslink / ipc / hlos / knl / NameServerRemoteNotify.c: ((status == NameServer_S_SUCCESS) = NameServer_E_NOTFOUND)): failed

Syslink-2_10_03_20 / packages / ti / syslink / utils / ti-syslink-2_10_03_20-r4j / ti-sysm-none-linux-gnueabi / Hlos / knl / Linux /../../../../../../ ti / syslink / ipc / hlos / knl / NameServerRemoteNotify.c: ((status == NameServer_S_SUCCESS) = NameServer_E_NOTFOUND)): failed

VPSS_FVID2: contrl event 0x6 timeout

Ti81xxfb ti81xxfb: failed to stop.

        

4. Questions

   1) Have you heard about this issue? Can you give me the answer?

   2) What is the reason that occur VPSS_FVID2 time out, How to solve the problem?

   3) What reason can occur VPSS_FVID2 timeout error?

   4) What HW parmeters can give affect to VPSSS output data?

   5) Is there register for checking VPSS output state?

   6) How to reset VPSS or VPSS output data?

Thank you.

  • 0
    TI__Guru**** 170625 points
    Hi Hodong,

    Do you use AM389x EZSDK?
    www.ti.com/.../linuxezsdk-sitara

    From what I understand, you are using AM389x custom board with both HDMI display and LCD display, and you have problems with LCD display?

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Prodigy 80 points
    Hello Pavel.

    I'm sorry to late.

    1. Checking EZSDK
    I can't check the EZSDK details because the person in charge was leave.
    Can you give me some advice how to check EZSDK version or installation?

    2. Relation HDMI, LCD
    In my opinion, I feel that I said about HDMI and LCD obscurely.
    I use only LCD for display, HDMI used for sending screen data from board to LCD.
    Not use two item HDMI display and LCD display.

    Regards,
    Hodong
  • 0 in reply to Hodong Lee
    TI__Guru**** 170625 points

    Hodong,

    Hodong Lee said:
    1. Checking EZSDK
    I can't check the EZSDK details because the person in charge was leave.
    Can you give me some advice how to check EZSDK version or installation?

    Can you provide me full boot up console log (u-boot, kernel, user space)?

    Hodong Lee said:
    HDMI used for sending screen data from board to LCD

    I am not sure how to understand this. Could you please provide more details how exactly you are sending data from HDMI to LCD?

    In AM389x device, we have HDVPSS subsystem.

    In HDVPSS subsystem we have HDMI (DVO1/VOUT1) transmitter which is used to send data to external HDMI monitor through the HDMI pins (TMDSCLKP/N, TMDSDN/P2/1/0, etc).  Do you have problems with the external HDMI monitor?

    In HDVPSS subsystem we have DVO2/VOUT0 interface which is used to send data to external LCD monitor through the DVO2/VOUT0 pins (VOUT[0]_CLK, VOUT[0]_VSYNC, VOUT[0]_HSYNC, etc). Do you have problems with the external LCD monitor?


    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 80 points

    1. Boot log

       The following log is "dmesg" log. i will give you to u-boot and user space log later.

    2. I'm sorry, but I have not used the TI board or have been involved in embedded tasks. So it is very difficult to give a detailed description of what you want. Thank you for your understanding.

       As far as I know, I made GUI program by nano-X & FLTK(the version were told before). Nano-X will use frame buffer.

       and I found vpss.ko file in build folder and Makefile included vpss.ko and other files. This is what I found out.

    3. I used LCD monitor and checked pins as you said. these are normal(CLK, VSYNC, HSYNC, Power). and I cross checked board and LCD.

      I think that this issue is depend on board.

    Nomal board Un-normal board
    LCD o x

    root@crong_m:~# dmesg
    Linux version 2.6.37 (v10528@v10528-5) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Mar 15 17:10:11 KST 2017
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: ti8168evm
    reserved size = 52428800 at 0x0
    FB: Reserving 52428800 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP chip is TI8168 2.0
    On node 0 totalpages: 52736
    free_area_init_node: node 0, pgdat 804f7fe4, node_mem_map 80532000
      Normal zone: 512 pages used for memmap
      Normal zone: 0 pages reserved
      Normal zone: 52224 pages, LIFO batch:15
    pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
    pcpu-alloc: [0] 0
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 52224
    Kernel command line: console=ttyO2,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M notifyk.vpssm3_sva=0xBF900000 ip=off noinitrd
    PID hash table entries: 1024 (order: 0, 4096 bytes)
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Memory: 206MB = 206MB total
    Memory: 203336k/203336k available, 58808k reserved, 0K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
        vmalloc : 0x90800000 - 0xf8000000   (1656 MB)
        lowmem  : 0x80000000 - 0x90000000   ( 256 MB)
        pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
        modules : 0x7f000000 - 0x7fe00000   (  14 MB)
          .init : 0x80008000 - 0x8003a000   ( 200 kB)
          .text : 0x8003a000 - 0x804b3000   (4580 kB)
          .data : 0x804b4000 - 0x804f8c00   ( 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 27000000 Hz
    Console: colour dummy device 80x30
    Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
    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_mux_init: Add partition: #1: core, flags: 0
    _omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
    _omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
    GPMC CS0: cs_on     :   0 ticks,   0 ns (was   0 ticks)   0 ns
    GPMC CS0: cs_rd_off :   5 ticks,  40 ns (was  30 ticks)  40 ns
    GPMC CS0: cs_wr_off :   5 ticks,  40 ns (was  30 ticks)  40 ns
    GPMC CS0: adv_on    :   1 ticks,   8 ns (was   0 ticks)   8 ns
    GPMC CS0: adv_rd_off:   3 ticks,  24 ns (was  30 ticks)  24 ns
    GPMC CS0: adv_wr_off:   5 ticks,  40 ns (was  30 ticks)  40 ns
    GPMC CS0: oe_on     :   1 ticks,   8 ns (was   7 ticks)   8 ns
    GPMC CS0: oe_off    :   6 ticks,  48 ns (was  24 ticks)  48 ns
    GPMC CS0: we_on     :   1 ticks,   8 ns (was   5 ticks)   8 ns
    GPMC CS0: we_off    :   4 ticks,  32 ns (was  22 ticks)  32 ns
    GPMC CS0: rd_cycle  :   9 ticks,  72 ns (was  30 ticks)  72 ns
    GPMC CS0: wr_cycle  :   9 ticks,  72 ns (was  30 ticks)  72 ns
    GPMC CS0: access    :   7 ticks,  56 ns (was  21 ticks)  56 ns
    GPMC CS0: page_burst_access:   0 ticks,   0 ns (was   0 ticks)   0 ns
    NOR: Can't request GPMC CS
    registered ti816x_gpio_vr device
    registered ti816x_sr device
    pm_dbg_init: only OMAP3 supported
    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
    regulator: VFB: 800 <--> 1025 mV at 830 mV
    SCSI subsystem initialized
    libata version 3.00 loaded.
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    USBSS revision 4ea20809
    registerd cppi-dma Intr @ IRQ 17
    Cppi41 Init Done
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 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
    TxFifo Empty intr disabled
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    musb-hdrc: 28/31 max ep, 16384/16384 memory
    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 9081e000 using DMA, IRQ 18
    Registered /proc/driver/musb_hdrc.0
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    MUSB controller-1 revision 4ea20800
    TxFifo Empty intr disabled
    musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
    musb-hdrc: MHDRC RTL version 2.0
    musb-hdrc: setup fifo_mode 4
    musb-hdrc: 28/31 max ep, 16384/16384 memory
    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 90828800 using DMA, IRQ 19
    Registered /proc/driver/musb_hdrc.1
    NET: Registered protocol family 2
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    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
    JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    msgmni has been set to 397
    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
    console [ttyO2] enabled
    brd: module loaded
    loop: module loaded
    ahci ahci.0: forcing PORTS_IMPL to 0x3
    ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
    scsi0 : ahci_platform
    scsi1 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
    ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16
    m25p80 spi1.0: found m25p05-nonjedec, expected m25p80
    m25p80 spi1.0: m25p05-nonjedec (64 Kbytes)
    Creating 4 MTD partitions on "spi_flash":
    0x000000000000-0x000000040000 : "U-Boot"
    mtd: partition "U-Boot" extends beyond the end of device "spi_flash" -- size truncated to 0x10000
    0x000000010000-0x000000012000 : "U-Boot Env"
    mtd: partition "U-Boot Env" is out of reach -- disabled
    0x000000000000-0x000000280000 : "Kernel"
    mtd: partition "Kernel" extends beyond the end of device "spi_flash" -- size truncated to 0x10000
    0x000000010000-0x000000010000 : "File System"
    mtd: partition "File System" is out of reach -- disabled
    omap2-nand driver initializing
    No NAND device found.
    No NAND device found.
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    davinci_mdio davinci_mdio.0: detected phy mask fffffffd
    mmc0: new high speed SD card at address b368
    mmcblk0: mmc0:b368 00000 1.83 GiB
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver dm9601
    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
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    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
     mmcblk0: p1 p2
    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
    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.
    smartreflex smartreflex: Driver initialized
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
    usb 2-1: new full speed USB device using musb-hdrc and address 2
    ata2: SATA link down (SStatus 0 SControl 300)
    ata1: SATA link down (SStatus 0 SControl 300)
    EXT3-fs: barriers not enabled
    kjournald starting.  Commit interval 5 seconds
    usb 2-1: New USB device found, idVendor=04d8, idProduct=0c03
    usb 2-1: New USB device strings: Mfr=1, Product=4, SerialNumber=0
    usb 2-1: Product: AR1100 HID-DIGITIZER
    usb 2-1: Manufacturer: Microchip Technology Inc.
    input: Microchip Technology Inc. AR1100 HID-DIGITIZER as /devices/platform/omap/ti81xx-usbss/musb-hdrc.1/usb2/2-1/2-1:1.0/input/input0
    generic-usb 0003:04D8:0C03.0001: input: USB HID v1.11 Device [Microchip Technology Inc. AR1100 HID-DIGITIZER] on usb-musb-hdrc.1-1/input0
    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
    udevd (68): /proc/68/oom_adj is deprecated, please use /proc/68/oom_score_adj instead.
    NET: Registered protocol family 10
    davinci_mdio davinci_mdio.0: resetting idled controller
    net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    SysLink version : 2.10.03.20
    SysLink module created on Date:Apr 29 2012 Time:20:45:11
    HDMI W1 rev 2.0
    hdmi: Enter HDMI_W1_StopVideoFrame()
    E-EDID checksum failed!!
    hdmi: Enter HDMI_W1_GlobalInitVars()
    hdmi: Enter HDMI_Core_GlobalInitVars()
    hdmi: Enter HDMI_W1_ConfigVideoResolutionTiming()
    hdmi: Enter HDMI_W1_ConfigVideoInterface()
    hdmi: HDMI_WP_AUDIO_CFG = 0x1030006
    hdmi: HDMI_WP_AUDIO_CFG2 = 0x20c0
    hdmi: HDMI_WP_AUDIO_CTRL = 0x20
    hdmi: Enter DSS_HDMI_CORE_SW_RESET_ASSERT ()
    hdmi: Enter DSS_HDMI_CORE_POWER_DOWN_DISABLE()
    hdmi: Enter DSS_HDMI_CORE_SW_RESET_RELEASE()
    hdmi: Enter HDMI_W1_StartVideoFrame  ()
    hdmi: Irqenable 60000011
    hdmi: 40 hpd
    hdmi: -------------DEBUG-------------------
    hdmi: 1 hdmi_wp_irqstatus
    hdmi: 1 hdmi_core_intr_state
    hdmi: 60 hdmi_core_intr1
    hdmi: 3 hdmi_core_intr2
    hdmi: f hdmi_core_intr3
    hdmi: 87 hdmi_core_sys_sys_stat
    hdmi: -------------DEBUG-------------------
    hdmi: first hpd register device crongfb_drv Ver 0.8.2.0 OK (major=201)
    root@crong_m:~#
  • 0 in reply to Hodong Lee
    TI__Guru**** 170625 points

    Hodong Lee said:
    2. I'm sorry, but I have not used the TI board or have been involved in embedded tasks. So it is very difficult to give a detailed description of what you want. Thank you for your understanding.

    I can provide you limited help in this case. Thank you for your understanding.

    Hodong Lee said:
    As far as I know, I made GUI program by nano-X & FLTK(the version were told before). Nano-X will use frame buffer.

    So you made your own user space application and you observe the display issue after starting your application? Is your application based on some of the demos available in the EZSDK package?

    Hodong Lee said:

    I used LCD monitor and checked pins as you said. these are normal(CLK, VSYNC, HSYNC, Power). and I cross checked board and LCD.

      I think that this issue is depend on board.

    Nomal board Un-normal board

    Do you mean that on some of your custom boards you do not have any issues and these are working fine?

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 80 points
    Dear Pavel

    1.
    I'm sorry that I gave to you wrong information.
    I used HDMI (DV01/VOUT1) to send data. Scaler board that we made receive HDMI data and change data for LCD.
    It is not connected between HDMI port LCD monitor.

    Board <-(HDMI)-> Scaler board <-> LCD

    This issue not occurred every board, it is occurred only a few boards.

    2.
    As i said at first time, I checked the board i could.(Scoping data, HDMI register checking)
    I think that this is hard to figure out it.
    So, I will give data my owns to you to find solution.
    Please tell me what you want data.

    3
    Could you give me answer for my questions that were i mentioned at first time.
    Even if you don't have solutions for it, Could you give me general information.(for example, the reason why occur 0x6 timeout in normal case.)

    Thank you.

    Regards,
    Hodong
  • 0 in reply to Hodong Lee
    TI__Guru**** 170625 points

    Hodong Lee said:
    I'm sorry that I gave to you wrong information.
    I used HDMI (DV01/VOUT1) to send data. Scaler board that we made receive HDMI data and change data for LCD.
    It is not connected between HDMI port LCD monitor.

    Board <-(HDMI)-> Scaler board <-> LCD

    Per mine understanding you have: AM389x board (HDMI pins) --> Scaler board ---> LCD screen, is that correct? Can you provide more info regarding this Scaler board, does it contain TI processor? And the issue is in HDMI pins or in LCD screen?

    Hodong Lee said:
    This issue not occurred every board, it is occurred only a few boards.

    When one software run fine on one board, and the same software fail on another board, this is most often indication of a hardware malfunction of the failing board.

    Hodong Lee said:
    Please tell me what you want data.

    I do this in each of my posts.

    Hodong Lee said:
    Could you give me answer for my questions that were i mentioned at first time.

    I will

    Regards,
    Pavel

  • 0
    TI__Guru**** 170625 points

    Hodong Lee said:
       1) Have you heard about this issue? Can you give me the answer?

    We had something similar in the past. The root cause was the PLL jitter. Check the PLL settings of the failing board, and compare with working board.

    Hodong Lee said:
       2) What is the reason that occur VPSS_FVID2 time out, How to solve the problem?

    This might be SW bug or incorrect sequence. See if the below e2e threads will be in help:

    Hodong Lee said:
       3) What reason can occur VPSS_FVID2 timeout error?

    This is the same question as in 2). The same answer apply here.

    Hodong Lee said:
    4) What HW parmeters can give affect to VPSSS output data?

    The HW parameters are described in the AM389x datasheet.

    Hodong Lee said:
      5) Is there register for checking VPSS output state?

    VPSS registers are described in TRM

    Hodong Lee said:
       6) How to reset VPSS or VPSS output data?

    This is described in the TRM

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 80 points

    Hi, Pavel

    1.
    I searched "18.5 Reset Management" in TRM but I could not find exactly the way to reset VPSS or VPSS data in TRM document(Literature Number: SPRUGX7C, March 2015).
    Could you give me more inforamtion like check point or the way to reset "VPSS"?

    2.
    and I found some information about my custom board.
    it used linux-2.6.37 and psp 04.04.00.11.

    3.

    I have a question.
    I used HDMI resolution 800x480 and it works well. But 800x480 is not defined in TRM document.
    is this resolution were officially support or not?

    Regards,
    Hodong

  • 0 in reply to Hodong Lee
    TI__Guru**** 170625 points

    Hi Hodong,

    Hodong Lee said:
    I searched "18.5 Reset Management" in TRM but I could not find exactly the way to reset VPSS or VPSS data in TRM document(Literature Number: SPRUGX7C, March 2015).
    Could you give me more inforamtion like check point or the way to reset "VPSS"?

    In TRM ch 18.5 is described how to reset the Cortex-M3 core that is controlling the HDVPSS, search for DSS_M3_PWRN_RST, DSS_M3_RST1/2/3, RM_DEFAULT_RSTCTRL Register

    See also:

    Regarding HDVPSS reset, you can also check DM816x HDVPSS Users Guide and Advisory 2.0.58, Advisory 2.1.32, Advisory 2.1.46


    Hodong Lee said:
    and I found some information about my custom board.
    it used linux-2.6.37 and psp 04.04.00.11.






    Do you mean psp 04.04.00.01?

    Hodong Lee said:
    I have a question.
    I used HDMI resolution 800x480 and it works well. But 800x480 is not defined in TRM document.
    is this resolution were officially support or not?

    I will check and come back to you.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 80 points
    Hi, Pavel

    Yes, I used psp 04.04.00.01

    Thank you.

    Regards,
    Hodong
  • 0 in reply to Pavel Botev
    Prodigy 80 points
    Dear, Pavel

    As i asked a question last before, HDMI resolution 800x480 is not defined in TRM docs.
    Is this resolution were officially support?
    And, Were The AM389x Users open use HDMI800x480 resolutions? I just wonder that how many user use this not defined resolution .

    regards,
    Hodong
  • 0 in reply to Hodong Lee
    TI__Guru**** 170625 points

    Hodong Lee said:
    Yes, I used psp 04.04.00.01

    You might explore the below set of patches and check which are missing in your code base. Look for HDMI, VPSS, DVO2, display, LCD, etc

  • 0 in reply to Hodong Lee
    TI__Guru**** 170625 points

    Hodong Lee said:
    As i asked a question last before, HDMI resolution 800x480 is not defined in TRM docs.
    Is this resolution were officially support?

    Yes. 480P (800x480) is a supported resolution for HDMI. This is supported in PSP04.04.00.01 onwards and you can  use timing or mode sysfs entry to program 480P resolution. You can refer to video driver useguide for same

     

    The below sequence has been validated in DM816x TI EVM

    root@dm816x-evm:~# /etc/init.d/matrix-gui-e stop
    Stopping Matrix GUI application.
    root@dm816x-evm:~# /etc/init.d/pvr-init stop
    Stopping PVR
    root@dm816x-evm:~# echo 0 > /sys/devices/platform/vpss/display0/enabled
    root@dm816x-evm:~# echo 33500,800/164/89/10,480/10/23/10,1 > /sys/devices/platform/vpss/display0/timings
    root@dm816x-evm:~# echo 1 > /sys/devices/platform/vpss/display0/enabled
    root@dm816x-evm:~# fbset -xres 800 -yres 480 -vxres 800 -vyres 480
    root@dm816x-evm:~# /etc/init.d/matrix-gui-e start
    Starting Matrix GUI application.
    root@dm816x-evm:~# cat /sys/devices/platform/vpss/display0/mode
    800x480@60

    See also the below e2e threads:

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    TI__Guru**** 170625 points
    Note that 800x480 mode is supported only for Video (display) (ti81xx_mode_dvi), there will be no audio in this mode. See the below e2e thread for more details:

    e2e.ti.com/.../478643
  • 0 in reply to Pavel Botev
    Prodigy 80 points

    Hi. Pavel Botev.

    I'm still looking for right answer about this issue(LCD blacked out).

    1.

    As you mentioned, i have been get new os files from arago-git by snapshot. I have compiled this source and got uImage.

    But it is failed to board-boot because of sysylink inserting error. probably old external module is not matched with new uImage.

    Hardware is initialized using a generic method
    No state is present for card EVM
    davinci_mdio davinci_mdio.0: resetting idled controller
    net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    done.
    Setting up IP spoofing protection: rp_filter.
    Sun Apr 29 22:50:00 UTC 2012
    INIT: Entering runlevel: 5
    Loading HDVICP2 Firmware
    syslink: disagrees about version of symbol clk_set_rate
    syslink: Unknown symbol clk_set_rate (err -22)
    syslink: disagrees about version of symbol clk_get_rate
    syslink: Unknown symbol clk_get_rate (err -22)
    syslink: disagrees about version of symbol clk_disable
    syslink: Unknown symbol clk_disable (err -22)
    syslink: disagrees about version of symbol clk_enable
    syslink: Unknown symbol clk_enable (err -22)
    FATAL: Error inserting syslink (/lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko): Invalid argument
    PHY: 0:01 - Link is Up - 1000/Full
    ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

    Could you tell me where can I find lastest syslink and other external modules data and files?

    I wiil apply lastest or new source to my board.

    2.

    I activated ti81xxfb, vpss modules debug mode(by attaching debug=1 at modprobe).

    When blacked out is occurred, I stopped the UI program(this is made by FLTK and nano-X). I got the log message below.

    [Mon Jul 03 17:53:25.309 2017] TI81XXFB  : Opening fb0
    [Mon Jul 03 17:53:25.309 2017] VPSS_GRPX : create grpx0
    [Mon Jul 03 17:53:25.309 2017] VPSS_DCTRL: enter set node
    [Mon Jul 03 17:53:25.309 2017] VPSS_FVID2: send control with cmd 0x10040018
    [Mon Jul 03 17:53:25.324 2017] VPSS_FVID2: control event 0x10040018 return 0 within 0 ms.
    [Mon Jul 03 17:53:25.324 2017] VPSS_FVID2: send control with cmd 0x10040017
    [Mon Jul 03 17:53:25.324 2017] VPSS_FVID2: control event 0x10040017 return 0 within 0 ms.
    [Mon Jul 03 17:53:25.324 2017] VPSS_SHRBUF: FOUND 0xbfb13000, end 0xbfd00000, map vir 0x97013000 size 4096
    [Mon Jul 03 17:53:25.340 2017] VPSS_FVID2: Fvid2 handle 0x9f1caca4 with notifyno 12 within 0 ms
    [Mon Jul 03 17:53:25.340 2017] VPSS_GRPX : (0)- add buffer 0x8ce00000
    [Mon Jul 03 17:53:25.340 2017] VPSS_GRPX : start grpx0
    [Mon Jul 03 17:53:25.356 2017] VPSS_GRPX : (0)- get resolution.
    [Mon Jul 03 17:53:25.356 2017] VPSS_DCTRL: enter get output format
    [Mon Jul 03 17:53:25.356 2017] VPSS_FVID2: send control with cmd 0x1004001a
    [Mon Jul 03 17:53:25.356 2017] VPSS_FVID2: control event 0x1004001a return 0 within 0 ms.
    [Mon Jul 03 17:53:25.371 2017] VPSS_FVID2: send control with cmd 0x00000003
    [Mon Jul 03 17:53:25.371 2017] VPSS_FVID2: control event 0x3 return 0 within 0 ms.
    [Mon Jul 03 17:53:25.371 2017] VPSS_FVID2: send control with cmd 0x10000002
    [Mon Jul 03 17:53:25.371 2017] VPSS_FVID2: control event 0x10000002 return 0 within 0 ms.
    [Mon Jul 03 17:53:25.387 2017] VPSS_FVID2: queue event return 0 within 0 ms.
    [Mon Jul 03 17:53:25.387 2017] VPSS_FVID2: send control with cmd 0x00000005
    [Mon Jul 03 17:53:25.387 2017] VPSS_FVID2: control event 0x5 return 0 within 38 ms.
    [Mon Jul 03 17:53:25.402 2017] TI81XXFB  : vram end 2aec7000 start 2ad50000, offset 0
    [Mon Jul 03 17:53:25.402 2017] TI81XXFB  : user mmap regions start 8ce00000, len 25165824
    [Mon Jul 03 17:53:25.402 2017] TI81XXFB  : setcamp(0)
    [Mon Jul 03 17:53:25.402 2017] TI81XXFB  : clut not same ,set
    [Mon Jul 03 17:53:25.418 2017] VPSS_GRPX : (0)- set clut 0x8a43a000
    [Mon Jul 03 17:53:25.418 2017] VPSS_GRPX : (0)- apply changes into FVID2_FRAME.
    [Mon Jul 03 17:53:25.418 2017] VPSS_FVID2: queue event return 0 within 0 ms.
    [Mon Jul 03 17:53:25.418 2017] eth0: no IPv6 routers present
    [Mon Jul 03 17:53:25.418 2017] TI81XXFB  : setcamp(0)  <-- UI program quit.
    [Mon Jul 03 17:53:25.434 2017] TI81XXFB  : Closing fb0
    [Mon Jul 03 17:53:25.434 2017] VPSS_GRPX : stop grpx0
    [Mon Jul 03 17:53:25.434 2017] VPSS_FVID2: send control with cmd 0x00000006
    [Mon Jul 03 17:53:25.434 2017] VPSS_FVID2: contrl event 0x6 timeout
    [Mon Jul 03 17:53:25.434 2017] ti81xxfb ti81xxfb: failed to stop.
    [Mon Jul 03 17:53:25.449 2017] root@crong_m:~#

    I want to reduce search range.

    Still not found that reason why, but I think ti81xxfb and vpss has been malfunctioned.

    If I'm right, i will check these modules at source level.

    please give me your advises.

  • 0 in reply to Hodong Lee
    TI__Guru**** 170625 points

    Hodong Lee said:
    But it is failed to board-boot because of sysylink inserting error. probably old external module is not matched with new uImage.

    Hodong Lee said:
    Could you tell me where can I find lastest syslink and other external modules data and files?

    You do not need latest syslink. You can use the one coming with latest EZSDK 5.05.02.00. You just need to build new syslink.ko file against new kernel source, then place that new syslink.ko file in rootfs

    Hodong Lee said:
    Still not found that reason why, but I think ti81xxfb and vpss has been malfunctioned.

    Try first with the latest linux kernel version (fix 1 above) before starting to debug linux kernel drivers

    Regards,
    Pavel