• State Resolved
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 143 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

AM62A7: DSS Pixel-clock cannot go below ~16MHz (small displays don't work)

AM625: DSS pixel clock can't set less than 15937500 Hz

Robert cnu
Prodigy 20 points
Part Number: AM625

Tool/software:

Hi,

My custom board has the same problem to https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1398125/am62a7-dss-pixel-clock-cannot-go-below-16mhz-small-displays-don-t-work?tisearch=e2e-sitesearch&keymatch=am62x%25252520dss%25252520clock%25252520can%25252527t%25252520set#

I use a DPI panel which supports frequency in range [8MHz, 12MHz] to operate properly.

Following is Uboot log for reference:

tidss_drv dss@30200000: vp1: new rate 15937500 Hz (requested 9000000 Hz)
tidss_drv dss@30200000: dss_vp_set_gamma: hw_videoport 1, lut len 0, hw len 256
tidss_drv dss@30200000: dss_vp_write_gamma_table: hw_videoport 1

Have the latest SDK firmware resolved this issue?

Thanks in advance!

  • 0
    TI__Expert 8300 points

    Which SDK version are you using? 
    I tried setting clock with k3conf set clock 186 2 <clock>, and I am able to set your requested values on SDK 11.01.
    Any value greater that 7MHz should be fine.

  • 0 in reply to Divyansh Mittal
    Prodigy 20 points

    Hi Divyansh,

    I'm using SDK https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tag/?h=09.02.00.009

    Kindly share to me the patches needed to port for this issue

  • 0 in reply to Robert cnu
    TI__Expert 8300 points

    9.02 is a very old SDK, would recommend you to port to the latest one.

  • 0 in reply to Divyansh Mittal
    Prodigy 20 points

    It would cost much effort to regression test if upgrading the SDK! It would be considered in near future.

    Is it possible to just patch necessary changes to resolve my problem?

  • 0 in reply to Robert cnu
    TI__Expert 8300 points

    Hi,
    This issue was resolved in SDK 10.1, can you try the following and let me know if it solves your issue:
    1. Copy the ipc_echo_testb_mcu1_0_release_strip* files from 10.1 SDK to 9.02 present at the location: ti-processor-sdk-linux-am62xx-evm-<version>/board-support/prebuilt-images/am62xx-evm/ti-dm/am62xx/.
    2. Run make u-boot and and install new binaries on your memory.

  • 0 in reply to Divyansh Mittal
    Prodigy 20 points

    Hi,

    After applied the file from https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/tree/ti-dm/am62xx?h=10.01.10, the board couldn't boot, please attached log for details

    U-Boot SPL 2023.04 (Sep 09 2025 - 10:38:44 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.7--v09.02.07 (Kool Koala)')
SPL initial stack usage: 13408 bytes
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):a755cfa8d-dirty
NOTICE:  BL31: Built : 10:29:55, Sep  9 2025
ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Timeout waiting for thread SP_RESPONSE to fill
ERROR:   Thread SP_RESPONSE verification failed (-60)
ERROR:   Message receive failed (-60)
ERROR:   Failed to get response (-60)
ERROR:   Transfer send failed (-60)
ERROR:   Unable to query firmware capabilities (-60)
I/TC: 
I/TC: OP-TEE version: a755cfa8d-dev (gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1)) #1 Tue Sep  9 01:30:07 UTC 2025 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 ti_sci_init:486 Unable to communicate with control firmware (-65523)
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x00070080 failed
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 tee_otp_get_hw_unique_key:97 Could not get HUK
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000700a8 failed
I/TC: Activated SA2UL device
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 k3_sec_proxy_verify_thread:108 Queue is busy
E/TC:0 0 k3_sec_proxy_recv:196 Thread SEC_PROXY_RESPONSE_THREAD verification failed. ret = -65523
E/TC:0 0 ti_sci_get_response:101 Message receive failed (-65523)
E/TC:0 0 ti_sci_do_xfer:150 Failed to get response (-65523)
E/TC:0 0 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x000700b0 failed
E/TC:0 0 
E/TC:0 0 Core data-abort at address 0x14 (translation fault)
E/TC:0 0  esr 0x96000005  ttbr0 0x9e8a1000   ttbr1 0x00000000   cidr 0x0
E/TC:0 0  cpu #0          cpsr 0x600003c4
E/TC:0 0  x0  000000009e874000 x1  0000000000000000
E/TC:0 0  x2  0000000000000000 x3  0000000000000000
E/TC:0 0  x4  00000000000003a0 x5  000000009e891d70
E/TC:0 0  x6  ffffffffffffffb0 x7  0000000000010cb0
E/TC:0 0  x8  000000009e891f80 x9  000000009e881070
E/TC:0 0  x10 0000000000000042 x11 0000000000000008
E/TC:0 0  x12 0000000000000000 x13 000000009e8a90b0
E/TC:0 0  x14 0000000000000000 x15 0000000000000000
E/TC:0 0  x16 000000009e81c8ec x17 0000000000000000
E/TC:0 0  x18 0000000000000000 x19 000000009e8a93f0
E/TC:0 0  x20 000000009e8a93f8 x21 000000009e874000
E/TC:0 0  x22 000000009e874000 x23 000000009e874ee0
E/TC:0 0  x24 000000009e873db0 x25 0000000000000000
E/TC:0 0  x26 0000000000000000 x27 0000000000000000
E/TC:0 0  x28 0000000000000000 x29 000000009e8a9360
E/TC:0 0  x30 000000009e817274 elr 000000009e817284
E/TC:0 0  sp_el0 000000009e8a9360
E/TC:0 0 TEE load address @ 0x9e800000
E/TC:0 0 Call stack:
E/TC:0 0  0x9e817284
E/TC:0 0  0x9e807ce4
E/TC:0 0  0x9e822334
E/TC:0 0  0x9e807ed4
E/TC:0 0 Panic 'unhandled pageable abort' at core/arch/arm/kernel/abort.c:582 <abort_handler>

  • +1 in reply to Robert cnu
    TI__Expert 8300 points

    Hi Robert,
    Thanks for sharing. 
    With slight modification to above setup, I have been able to replicate and validate a working setup at my end:
    1. Copy all files of ti-dm and ti-sysfw directories from 10.1 to 9.02.
    2. Run make-u-boot and install new binaries.

    With this, I am able to set lower frequencies on 9.02 as well.

  • 0 in reply to Divyansh Mittal
    Prodigy 20 points

    Perfect! Thanks Divyansh for great support