J721e: LPM example crashing before booting Linux

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: High
    • PDK
    • PDK-15176
    • PROCESSOR_SDK_10.00.00
    • PROCESSOR_SDK_10.01.00
    • j721e-evm

      The LPM demo for MCU_Only mode is crashing even before the LPM mode & booting Linux fails at the ATF stage.

      Crash:

      NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
      NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
      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: 4.2.0-dev (gcc version 13.3.0 (GCC)) #1 Fri Apr 12 09:51:21 UTC 2024 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 + 0x00070b10 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 + 0x00070b38 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 sa2ul_init:61 Failed to get SA2UL device
      E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x00070b40 failed
      E/TC:0 0 
      E/TC:0 0 Core data-abort at address 0x14 (translation fault)
      E/TC:0 0  esr 0x96000005  ttbr0 0x9e8a2000   ttbr1 0x00000000   cidr 0x0
      E/TC:0 0  cpu #0          cpsr 0x600003c4
      E/TC:0 0  x0  000000009e875000 x1  0000000000000000
      E/TC:0 0  x2  0000000000000000 x3  0000000000000000
      E/TC:0 0  x4  0000000000000050 x5  000000009e892d70
      E/TC:0 0  x6  ffffffffffffffb0 x7  0000000000010cb0
      E/TC:0 0  x8  0000000000010cb0 x9  000000009e892f80
      E/TC:0 0  x10 000000009e882070 x11 0000000000000008
      E/TC:0 0  x12 0000000000000000 x13 000000009e8a3e60
      E/TC:0 0  x14 0000000000000000 x15 0000000000000000
      E/TC:0 0  x16 000000009e81cc5c x17 0000000000000000
      E/TC:0 0  x18 0000000000000000 x19 000000009e8a41e0
      E/TC:0 0  x20 000000009e8a41e8 x21 000000009e875000
      E/TC:0 0  x22 000000009e875000 x23 000000009e875f00
      E/TC:0 0  x24 000000009e874dc0 x25 0000000000000000
      E/TC:0 0  x26 0000000000000000 x27 0000000000000000
      E/TC:0 0  x28 0000000000000000 x29 000000009e8a4170
      E/TC:0 0  x30 000000009e81741c elr 000000009e81742c
      E/TC:0 0  sp_el0 000000009e8a4170
      E/TC:0 0 TEE load address @ 0x9e800000
      E/TC:0 0 Call stack:
      E/TC:0 0  0x9e81742c
      E/TC:0 0  0x9e807ca0
      E/TC:0 0  0x9e8225fc
      E/TC:0 0  0x9e807e9c
      E/TC:0 0 Panic 'unhandled pageable abort' at /usr/src/debug/optee-os/4.2.0+git/core/arch/arm/kernel/abort.c:582 <abort_handler>
      E/TC:0 0 TEE load address @ 0x9e800000
      E/TC:0 0 Call stack:
      E/TC:0 0  0x9e80817c
      E/TC:0 0  0x9e81f0c0
      E/TC:0 0  0x9e807884
      E/TC:0 0  0x9e804a68

      Resolution:
      Create a separate task for
      sciserver with highest task priority

      Root Cause:
      Linux load fails with lpm_example_freertos because
      while booting linux kernel, tisci/sciclient calls
      are not processed by DM.
      This is because sciserver task running on DM doesn't
      process the task with high priority resulting in failure
      in linux side.

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Connection: Intermediate to External PROD System
                EXTSYNC-4898 - J721e: LPM example crashing before ...
                SYNCHRONIZED
                • Last Sync Date: