• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 2800 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/AM5728: IDK LCD display issue

Anthony Tzouris
Prodigy 220 points
Part Number: AM5728

Tool/software: Linux

Cannot seem to get any display output on the AM5728 IDK LCD (OSD101T2587-53TS) Display. Done the due diligence of investigation involving u-boot configuration setting the device tree appropriately (in u-boot) and checking all of the ribbon cable connections as well.  At this point either the hardware is bad or I'm doing something wrong.  Hoping the latter (doing something wrong) is my problem.  Would like some basic feedback if possible such as (it works for me, or my procedure looks okay, or seem to be missing something, etc.)  Using following configuration:

  • TI SDK is ... ti-processor-sdk-linux-rt-am57xx-evm-03.02.00.05

    • Using SDCard created from pre-built images from the SDK
  • AM5728 IDK platform

  • OSD101T2587-53T optional LCD display for the AM5728 IDK

  • Using USB Keyboard + USB Mouse

u-boot configuration

  • setenv idk_lcd osd101t2587
  • run findfdt
  • saveenv

snippet of u-boot console interaction below

--snip

=>  printenv fdtfile
fdtfile=am572x-idk-lcd-osd101t2587.dtb
=> printenv idk_lcd
idk_lcd=osd101t2587
=> setenv fdtfile
=> run findfdt
=> printenv fdtfile
fdtfile=am572x-idk-lcd-osd101t2587.dtb
=> printenv idk_lcd
idk_lcd=osd101t2587
=> saveenv

Saving Environment to FAT...
writing uboot.env
FAT: Misaligned buffer address (fef1d918)
done
=>

--snip

Also, tried an older SDK (ti-processor-sdk-linux-am57xx-evm-03.01.00.06) but get the same results.  Older SDKs than this older one do not contain the appropriate device tree dtb files for the LCD  OSD101T2587 device.

It's usually a rare occasion in which the hardware is bad.  I'm just about out of ideas as it seems fairly straightforward and should be supported out of the box from the SDK SDCard pre-built images with a u-boot modification for the idk_lcd environment variable.

As a side note, I have plugged in a 4.3" LCD Display (ELI43-CR) and I get the 'Please wait ..." message through the HDMI connector if I use the am572x-idk-lcd-osd101t2587.dtb and if I use the am572x-idk.dtb then I get the full matrox gui.  Note both of these "Please wait" and full matrox gui are only on the ELI43-CR LCD Display.  There is nothing on the OSD101T2587 LCD Display at all.

Please advise.

-- Anthony

  • 0
    TI__Guru**** 393215 points
    The IDK team have been notified. They will respond here.
  • 0
    TI__Mastermind 22386 points

    Hi Anthony,

    No need to play with dtb files settings. Right one gets picked at boot time.

    Most of the time issue is with LCD board ribbon connection. Please follow the LCD kit quick start guide for connecting the cables. I am attaching the document for your reference.

    AM57x_LCD_Kit_QSG_9-2-16.pdf

    Regards,

    Manisha

  • 0 in reply to Manisha Agrawal
    Prodigy 220 points

    Yes, you are correct, the dtb file gets chosen automatically at boot time.

    I tried one more time as you have suggested but with no success.

    I have already been through that document beforehand and at least on a few of times tried to reseat the ribbon cables already.  I would have liked to zoom in a little bit more but the resolution gets fuzzy in the referenced. I have attached three pics of my connections.

  • 0 in reply to Anthony Tzouris
    TI__Mastermind 22386 points
    I don't see any attachments in your post. Is you LCD panel itself not getting detected or is it touch screen not working? Can you connect the mouse to the board and check the behavior.

    Most common problem people face is the small ribbon cable they reversed on both sides
    [1] On the IDK board side: The contacts need to “face upwards”, i.e. away from the board.
    [2] On the LCD panel side: with the white/black flap side of the connector pointing away from the space between the boards
  • 0 in reply to Anthony Tzouris
    Prodigy 220 points

    Now that I reseated the ribbon cables again and I sent you the pics ... I know have "Please wait ..." on the display.  The orientation of the connectors had not changed but I reseated all of the connectors again and this time I had success.  I had always had a keyboard and mouse connected during my debugging here.

    Now to figure out how to get past the "Please wait ..." message to the weston (touch screen calibration) and matrox-gui.  If you have any ideas how I can get past the "Please wait ..." to calibration and the gui, it would be appreciated.

    -- Anthony Tzouris

  • 0 in reply to Anthony Tzouris
    TI__Mastermind 22386 points
    Hi Anthony,

    It seems like the touch screen is still not working. Since you have mouse connected, "Please wait" shouldn't have been shown. Can you share /var/log/weston.log file? If that's not generated, are you able to do #/etc/init.d/weston stop? If so, after stopping weston, can you run one of the qt demos like -
    #/usr/share/qt5/examples/opengl/2dpainting/2dpainting -platform eglfs
  • 0 in reply to Manisha Agrawal
    Prodigy 220 points

    weston.log file is attached.

    other stuff snippet below

    --snip

    root@am57xx-evm:~# /etc/init.d/weston stop

    Stopping Weston

    root@am57xx-evm:~# /usr/share/qt5/examples/opengl/2dpainting/2dpainting -platform eglfs

    PVR:(Error): OpenServices: PVRDRMOpenRender failed [0, ]

    PVR:(Error): PVRSRVConnect: Unable to open connection. [0, ]

    PVR:(Error): Couldn't connect to services [0, ]

    Could not initialize egl display

    Aborted (core dumped)

    weston.log 
    Date: 2017-02-23 UTC
[21:49:55.203] weston 1.9.0
               http://wayland.freedesktop.org
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.9.0
               Build: 1.8.93-2-gb05cdb8 configure.ac: bump to version 1.9.0 for the official release (2015-09-21 18:11:26 -0700)
[21:49:55.203] OS: Linux, 4.4.32-rt41-ge26c84b0ac, #1 SMP PREEMPT RT Wed Dec 14 19:34:32 EST 2016, armv7l
[21:49:55.204] Using config file '/etc//weston.ini'
[21:49:55.206] Loading module '/usr/lib/weston/drm-backend.so'
[21:49:55.236] Output repaint window is 7 ms maximum.
[21:49:55.236] initializing drm backend
[21:49:55.241] using /dev/dri/card0
[21:49:55.243] Loading module '/usr/lib/weston/gl-renderer.so'
failed to load module: /usr/lib/gbm/gbm_dri.so: cannot open shared object file: No such file or directory
failed to load module: /usr/lib/gbm/gbm_gallium_drm.so: cannot open shared object file: No such file or directory
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
[21:49:55.346] warning: either no EGL_EXT_platform_base support or specific platform support; falling back to eglGetDisplay.
[21:49:55.357] failed to initialize display
[21:49:55.357] EGL error state: EGL_BAD_ALLOC (0x3003)
[21:49:55.357] failed to initialize egl
[21:49:55.388] fatal: failed to create compositor backend
PVR:(Error): OpenServices: PVRDRMOpenRender failed [0, ]
PVR:(Error): PVRSRVConnect: Unable to open connection. [0, ]
PVR:(Error): Couldn't connect to services [0, ]
    root@am57xx-evm:~#

    --snip

  • 0 in reply to Anthony Tzouris
    TI__Mastermind 22386 points

    LCD bring-up procedure, including connecting the touch screen and LCD ribbon cables can be found in below training video -