SK-AM62B-P1: How to disable SYSFW log

Hello,

Koji Hirohashi said:

Sciserver Testapp Built On: Mar 15 2024 16:54:15

Sciserver Version: v2024.03.0.0-REL.MCUSDK.09.02.00.24+

RM_PM_HAL Version: v09.02.07a

Starting Sciserver..... PASSED

[IPC RPMSG ECHO] Version: REL.MCUSDK.09.02.00.24+ (Mar 15 2024 16:55:13):

[IPC RPMSG ECHO] Remote Core waiting for messages at end point 13 ... !!!

[IPC RPMSG ECHO] Remote Core waiting for messages at end point 14 ... !!!

I suppose these are the logs from wkup_uart0.

I would suggest you to go ahead and remove the wkup_uart0 instance. That will make sure you do not see the logs over wkup_uart0. I hope that clarifies. 

The sysconfig window should be your go to point to remove the wkup_uart0 instance.

Regards,

Vaibhav

Hi Vaibhav,

Thank you.

I understood that I should remove wkup_uart0 instance.

Please tell me whether the following my understanding is correct.

(1) The instance can be remover in MCU+ SDK and built as ipc_rpmsg_echo_linux.release.appimage.

(2) I would like to boot linux with SPL. For that, I should replace ipc_echo_testb_mcu1_0_release_strip.xer5f to the above appimage in u-boot-ti-staging.

If my understanding isn't correct, could you tell me what is correct?

Best Regards,

Koji

Hi Vaibhav,

I ask additionally question. 

Vaibhav Kumar said:

The sysconfig window should be your go to point to remove the wkup_uart0 instance.

Koji Hirohashi said:

(1) The instance can be remover in MCU+ SDK and built as ipc_rpmsg_echo_linux.release.appimage.

(2) I would like to boot linux with SPL. For that, I should replace ipc_echo_testb_mcu1_0_release_strip.xer5f to the above appimage in u-boot-ti-staging.

I tried their.

It seems that wkup_uart is already disabled, so I just only disabled "Enable UART Log".

At the result, wkup_uart console could be disabled.

But, the following log was output from uart0:

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 + 0x0006fae0 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 + 0x0006fb08 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 sa2ul_init:106 Could not change TRNG firewall owner
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x0006fb10 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 000000009e8a9050
E/TC:0 0 x14 0000000000000000 x15 0000000000000000
E/TC:0 0 x16 000000009e81c67c x17 0000000000000000
E/TC:0 0 x18 0000000000000000 x19 000000009e8a93d0
E/TC:0 0 x20 000000009e8a93d8 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 000000009e816fcc elr 000000009e816fdc
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 0x9e816fdc
E/TC:0 0 0x9e807d24
E/TC:0 0 0x9e822148
E/TC:0 0 0x9e807e94
E/TC:0 0 Panic 'unhandled pageable abort' at 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 0x9e80801c
E/TC:0 0 0x9e81eb88
E/TC:0 0 0x9e807920
E/TC:0 0 0x9e804a98

It seems that the log was output by OPTEE and linux couldn't boot.

What should I do for workaround this?

Best Regards,

Koji

Hello Koji,

Assigning this thread to another expert.

Thanks,

Vaibhav

I'm looking forward to the expert's update.

Koji

Do you have any update?

I would like to have a reply by tomorrow.

Koji

I have been waiting for your response for over 10 days.

Could you tell me current situation?

Vaibhav Kumar said:

Assigning this thread to another expert.

Is the expert already assigned?

Best Regards,

Koji

Koji Hirohashi said:

(2) I would like to boot linux with SPL. For that, I should replace ipc_echo_testb_mcu1_0_release_strip.xer5f to the above appimage in u-boot-ti-staging.

Hi Koji,

You need to replace the .out file, not the appimage.

From the logs looks like DM is not running.

Please check the below thread for the steps to build and replace the binary file correctly.
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1308171/sk-am62a-lp-running-the-mcu-application-through-the-sd-card-boot-mode/4972931#4972931

Regards,
Aparna