AM5728: AM572x evm - new default image - no display

Part Number: AM5728
Other Parts Discussed in Thread: BEAGLEBOARD-X15,

Tool/software:

The old image that came with the eval has a working boot screen, touch screen and program that load a screen. New image does not, was that removed or is there something wrong I need to look at?

  • Robert,

    Can you please be more explicit with the SDK versions you are referring to?

    -Josue

  • AM572X eval module

    https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-L1u0FxxpZf/09.03.06.05/tisdk-default-image-am57xx-evm.wic.xz

     new image///onboard display does not come up – downloaded from TI

    root@am57xx-evm:~# hostnamectl

    Static hostname: am57xx-evm

           Icon name: computer

          Machine ID: 07b5f4e2274549fbae6cbbb850b465ca

             Boot ID: 50ffa3086023472cb79f6b08c75de27b

    Operating System: Arago 2023.10

              Kernel: Linux 6.1.119-ti-ge4e8b16e66f5

        Architecture: arm

    /////////////////////////////////////

    image that came with AM752X evm board/// onboard display come up

     Linux version 4.1.13-g8dc6617

    (gtbldadm@ubuntu-12)

    (gcc version 4.9.3 20150413

    (prerelease) (Linaro GCC 4.9-2015.05 

  • Hello Robert,

    I am out of the office until 1/22. Please expect delays in reply.

    -Josue

  • Robert,

    On the new image, do you see at least a grey screen?

    Can you let me know what dtb you are using?

    I do not think the LCD is enabled by default in the newer images..  I am double-checking with our dev team.

    For sure the Matrix application is no longer supported.

    Please see the release notes here: https://software-dl.ti.com/processor-sdk-linux/esd/AM57X/09_03_06_05/exports/docs/devices/AM57X/linux/Release_Specific_Release_Notes.html#release-09-03-00

    -Josue

  • yes it is a light grey background..  I will review the release notes to see what was remove, but I would thing the boot screen would show but maybe that was removed. 

    U-Boot SPL 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)
    DRA752-GP ES2.0
    no pinctrl state for default mode
    Firmware loading failed for ipu2
    Trying to boot from MMC1
    Loading Environment from FAT... no pinctrl state for default mode
    *** Error - No Valid Environment Area found
    *** Warning - bad env area, using default environment

    Loading Environment from MMC... *** Warning - bad CRC, using default environment

    U-Boot 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)

    CPU : DRA752-GP ES2.0
    Model: TI AM5728 BeagleBoard-X15
    Board: AM572x EVM REV A.3A
    DRAM: 2 GiB
    ti_emmc_boardid_get failed -5
    Core: 70 devices, 24 uclasses, devicetree: separate
    MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
    Loading Environment from FAT... *** Error - No Valid Environment Area found
    *** Warning - bad env area, using default environment

    Loading Environment from MMC... *** Warning - bad CRC, using default environment

    Net: eth2: ethernet@48484000
    Hit any key to stop autoboot: 0
    switch to partitions #0, OK
    mmc0 is current device
    SD/MMC found on device 0
    This will not be a case any time
    This will not be a case any time
    7930368 bytes read in 373 ms (20.3 MiB/s)
    This will not be a case any time
    This will not be a case any time
    216953 bytes read in 39 ms (5.3 MiB/s)
    Working FDT set to 88000000
    This will not be a case any time
    This will not be a case any time
    Kernel image @ 0x82000000 [ 0x000000 - 0x790200 ]
    ## Flattened Device Tree blob at 88000000
    Booting using the fdt blob at 0x88000000
    Working FDT set to 88000000
    Loading Device Tree to 8fec8000, end 8fffffff ... OK
    Working FDT set to 8fec8000
    ft_fixup_clocks failed for DSP voltage domain: <valid offset/length>

    Starting kernel ...

    [ 0.000000] Booting Linux on physical CPU 0x0
    [ 0.000000] Linux version 6.1.119-ti-ge4e8b16e66f5 (oe-user@oe-host) (arm-oe-linux-gnueabi-gcc (GCC) 11.5.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Sat Dec 7 07:14:10 UTC 2024
    [ 0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=30c5387d
    [ 0.000000] CPU: div instructions available: patching division code
    [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
    [ 0.000000] OF: fdt: Machine model: TI AM5728 BeagleBoard-X15
    [ 0.000000] Memory policy: Data cache writealloc
    [ 0.000000] efi: UEFI not found.

    Here is the start of the boot seems like there is an issues with some warning/errors. Reimage a couple time same results. Note the model shows Beagleboard, seem wrong. the UENV.txt file has no defined variables in it - should it?

    Thanks for any help

    Rob

  • Robert, 

    If your screen looks like this one:

    This is the weston desktop and that's the expected behavior now that the GUI Matrix has been removed.

    If this is the case then your LCD is in working order.

    Yes, there are some kinks in the u-boot initialization that have not been taken care of and we can hopefully look into.

    Josue

  • ok, thanks, questions: it looks just like it does when power is just turned on, not the grey you are showing?

    I can stop/start weston but I see this  in the restarting - [13:36:10.000] BUG: layer list is not empty after shutdown. Calls to weston_layer_fini() are missing somwhere.

    below is the Weston /start after stop then restarting - seems fine except the above bug

    I do see weston task in the list of task though

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    [13:42:37.-1225405176] weston 10.0.2
    https://wayland.freedesktop.org
    Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
    Build: 10.0.2
    [13:42:37.-1096150020] Command line: weston /start
    [13:42:37.-1226533029] OS: Linux, 6.1.119-ti-ge4e8b16e66f5, #1 SMP PREEMPT Sat Dec 7 07:14:10 UTC 2024, armv7l
    [13:42:37.139272] Flight recorder: enabled
    [13:42:37.1679848297] Using config file '/etc/xdg/weston/weston.ini'
    [13:42:37.002] Output repaint window is 7 ms maximum.
    [13:42:37.-1225405176] Loading module '/usr/lib/libweston-10/wayland-backend.so'
    [13:42:37.-1225405176] Loading module '/usr/lib/libweston-10/gl-renderer.so'
    [13:42:37.000] EGL client extensions: EGL_EXT_client_extensions
    EGL_EXT_device_base EGL_EXT_device_enumeration
    EGL_EXT_device_query EGL_EXT_platform_base
    EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug
    EGL_EXT_platform_device EGL_EXT_platform_wayland
    EGL_KHR_platform_wayland EGL_MESA_platform_gbm
    EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless
    MESA: info: Loaded libpvr_dri_support.so
    [13:42:37.004] EGL device extensions: EGL_EXT_device_drm
    EGL_EXT_device_drm_render_node
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    is there something that I can run to see something on the display or driver code to use in the image to verify things (display)?

  • Robert,

    it looks just like it does when power is just turned on, not the grey you are showing?

    Can you clarify the above statement? you see the same screen or not? Do you see the date and the weston shell symbol?

    Can you see a mouse when you connect one via USB?

    Can you share the overlay you are using?

    you could run the GPU examples under /usr/share/qt5/examples/gui:

    Fullscreen
    1
    2
    3
    root@am57xx-evm:~# cd /usr/share/qt5/examples/gui
    root@am57xx-evm:/usr/share/qt5/examples/gui# ./openglwindow/openglwindow
    MESA: info: Loaded libpvr_dri_support.so
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    and you should see the following:

    -Josue

  • Screen is not the same as yours.

    Not sure overlay question means

    Ran program as stated and no display (see below) 

    root@am57xx-evm:/usr/share/qt5/examples/gui/openglwindow# ./openglwindow
    qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
    MESA: info: Loaded libpvr_dri_support.so

    mouse does show up that it was loaded in the termal (Putty) nothing on screen

    fyi..am57xx-evm-linux-rt-06.03.00.106.img.zip this image which was create in 2019 works fine

    Seems like the latest version has big issues around this area?

  • fyi..Test the 2019 image and the mouse work fine in this image

  • Robert,
    2019 image should be fine. I believe the default image for the newest SDK does not have the correct DTS loaded for enabling the LCD screen on the EVM.
    So my question is essentially what DT source is being used? 

    You might have to use a different DT source file in order to see the screen enabled, and I believe this is an overlay file or .dtbo file 

    Should be this one: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm/boot/dts/am57xx-evm.dtso?h=ti-linux-6.1.y

    I myself do not have the bandwidth to test right now but I can probably get around the end of next week or the week after.

    -Josue

  • Hi! thanks for the input I'll look at it, but traveling last couple of days should be back on it later today or tomorrow

  • Robert,

    No worries, safe travels!

  • Thanks, I trying to fine all the link for to get the file to build.. Seems more complicated then I would hope - any help with location image source files?

  • Robert,

    You can download the SDKs at https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-AM57X/09.03.06.05

    Or clone the Linux source https://git.ti.com/git/ti-linux-kernel/ti-linux-kernel.git. You could also do something to the extent of https://stackoverflow.com/questions/61587133/cloning-single-file-from-git-repository.

    The LCD overlays are already present in your root image.

    -Josue

  • Thanks, I need to get my Linux box up and look at it. From what I read it need to be built with Ubuntu 14, that really old?

  • Yes, SDK 6.3-8.2 is tested using Ubuntu 18.04 and the newer SDKs are all tested in Ubuntu 22.04.

    -Josue

  • cool, then 22.04 is closer to the newest - thanks..

  • BTW: have you have a change to look at it or is that another week or so out?