PROCESSOR-SDK-J721S2: linux 8.5

xin lei

hello ti

when we debug A72, at the startup stage, serial gives us following error

NOTICE: BL31: v2.7(release):v2.7.0-359-g1309c6c80-dirty
NOTICE: BL31: Built : 13:08:29, Jun 29 2023
I/TC:
I/TC: OP-TEE version: 3.19.0-dev (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #16 Mon Jul 3 08:25:41 UTC 2023 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.3--v08.06.03 (Chill Capybar')
I/TC: HUK Initialized
I/TC: 1111111111111111111111111111111111 SA2UL_TI_SCI_DEV_ID = 297
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:60 Failed to get SA2UL device
E/TC:0 0 call_initcalls:43 Initcall __text_start + 0x0005c898 failed
I/TC: Primary CPU switching to normal world boot

According to our check, the control flow has reached following place

but it returns from smc.

so could you please tell me where control flow go, what code will execute when code executes smc #0 next. Thanks

over 2 years ago

0 Keerthy J over 2 years ago

TI__Guru**** 166510 points

Hi,

xin lei said:
so could you please tell me where control flow go, what code will execute when code executes smc #0 next.

Are you trying on a custom board? Does the boot hang after the above or the booting works post that?

- Keerthy

0 xin lei over 2 years ago in reply to Keerthy J

Prodigy 215 points

1.on custom board

2.process just hang at I/TC: Primary CPU switching to normal world boot, and no more print after.

0 Keerthy J over 2 years ago in reply to xin lei

TI__Guru**** 166510 points

Hi,

Can we try to remove OPTEE from the boot flow by building ATF to directly load the A72 SPL. This is just to move ahead.

cd $PSDK_Linux/board-support/trusted-firmware*
make CROSS_COMPILE=aarch64-linux-gnu- ARCH=aarch64 PLAT=k3 TARGET_BOARD=generic K3_USART=0x8

assuming you are using the MAIN_UART8 as console on your custom board as well.

This will bypass OPTEE and ATF will directly jump to A72 SPL.

- Keerthy

0 xin lei over 2 years ago in reply to Keerthy J

Prodigy 215 points

Hi Keerthy:

Thanks for your answering, i have passed tee. but I can still not jump to u-boot-spl. where is code in sdk instruct control flow to jump to uboot-spl. thanks!

0 xin lei over 2 years ago in reply to xin lei

Prodigy 215 points

I can see my code has gone to exception_return of el3_exit , but no more print show us after that. (I add print in uboot-spl).

0 Keerthy J over 2 years ago in reply to xin lei

TI__Guru**** 166510 points

Hi,

tiboot3.bin loads the tispl.bin which has the device manager binary: ipc_echo_testb_mcu1_0_release_strip.xer5f

Can you try with the default device manager binary under $PSDK_Linux/board-support/prebuilt-images/ipc_echo_testb_mcu1_0_release_strip.xer5f

Seems like that could be different here.

- Keerthy

0 xin lei over 2 years ago in reply to Keerthy J

Prodigy 215 points

hi keerthy

just as you said, If we change the dm part, our code can run, but why it can be this. I think after atf and tee, u-boot-spl should be executed but .xer5f.

And on the other hand, we do not have the source code of .xer5f, so we can not get the diff between our code and standard code.

thanks

0 Keerthy J over 2 years ago in reply to xin lei

TI__Guru**** 166510 points

Hi,

Thanks confirming this! DM --> Device manager is the server for all the device management. So that is executed by MCU1_0 after executing the R5 SPL.
So all the ATF/OPTEE/A72 SPL/U-Boot/Linux needs the DM services.

Closing this thread.

- Keerthy

0 xin lei over 2 years ago in reply to Keerthy J

Prodigy 215 points

sorry keerthy

How can we change our code to meet the need of startup? should we include .xer5f in our app code ?

thanks

0 Keerthy J over 2 years ago in reply to xin lei

TI__Guru**** 166510 points

xin lei said:
How can we change our code to meet the need of startup? should we include .xer5f in our app code ?

Please go through the device boot flow:

https://git.ti.com/gitweb?p=ti-u-boot/ti-u-boot.git;a=blob;f=board/ti/j721s2/README;h=a01c70a975811ad6c6eda89bacb3bbe95c843d30;hb=refs/heads/ti-u-boot-2021.01

Device manager is a must for all the boot flows. MCU1_0 core is dedicated for that.

- Keerthy

0 xin lei over 2 years ago in reply to Keerthy J

Prodigy 215 points

hi keerthy

I think we have some missunderstand about this problem. In my side, we need to run autosar on mcu, so we change the original .xer5f to our app(the dm part is not empty but our app code). under this situation, we can not start up our board. so could you please help to modify our code, so we can run our app on the mcu and startup our target.

actually , we open tee in our code which will use the DM server, and we can see there are answers from mcu.

thanks

0 Brijesh Jadav over 2 years ago in reply to xin lei

TI__Guru**** 486755 points

hi xin lei,

Have you integrated SciServer in Autosar code? Also if you have, have you checked loading this code using CCS and confirmed that it is starting SciServer correctly on mcu1_0 core?

Please refer to below Application note for more information on how to integrate SciServer.

https://www.ti.com/lit/an/spracy6/spracy6.pdf

Regards,

Brijesh

Processors

Processors forum

PROCESSOR-SDK-J721S2: linux 8.5