topic Re: TEE logs are not available in DMESG in i.MX Processors

TEE logs are not available in DMESG

rnamburi — Fri, 04 Jul 2025 08:43:58 GMT

I am unable to see TEE logs in dmesg even after increasing the loglevel with

CFG_TEE_CORE_LOG_LEVEL=4
CFG_TEE_TA_LOG_LEVEL = 4

Could please let me know, where am i missing.

Re: TEE logs are not available in DMESG

yipingwang — Tue, 08 Jul 2025 08:25:46 GMT

I usually set the above two configurations, and when U-boot starts, I can see the Optee message.
First, confirm if the message can be seen in u-boot(atf) console log.

Re: TEE logs are not available in DMESG

rnamburi — Fri, 11 Jul 2025 10:14:04 GMT

i could not see config parameters in u-boot logs. i have enabled them in yacto build. But how to check those configs are enabled in target after flashing?

Re: TEE logs are not available in DMESG

yipingwang — Fri, 18 Jul 2025 09:34:47 GMT

$ bitbake optee-os -c cleansstate

$ bitbake imx-atf -c cleansstate

$ bitbake imx-boot -c cleansstate

$ bitbake optee-os -c patch

Go to folder build-xwayland/tmp/work/imx8mpevk-poky-linux/optee-os/4.6.0.imx/git, please modify mk/config.mk according to your debug level setting.

$ bitbake optee-os

$ bitbake imx-atf

$ bitbake imx-boot

Then check optee message in your Kernel console log.

Re: TEE logs are not available in DMESG

rnamburi — Sun, 10 Aug 2025 11:14:51 GMT

i have made the changes in mk/config.mk

I am not using yacto recipe for hartos compilation. Instead i use following commands to generate hartos image.

echo "<------------Building Hartos-------------------->"

echo "<============Exporting Toolchain Path and setting enviornment Variable=============>"
export CROSS_COMPILE=arm-elina-linux-gnueabi-
export ARCH=arm
export PLATFORM=imx
export COMPILE_NS_USER=32
LDFLAGS=

echo "<==========Compiling Hartos ==========>"
make clean
make all

after flashing the hartos image. i dont see any TA applicatoin logs in dmesg.

do you any suggestions on this?

Re: TEE logs are not available in DMESG

yipingwang — Mon, 11 Aug 2025 06:27:54 GMT

Did you build ATF image with optee enabled?

Please check Linux Kernel dmesg information, can you get "optee" related information?

Re: TEE logs are not available in DMESG

rnamburi — Wed, 13 Aug 2025 07:42:22 GMT

Did you build ATF image with optee enabled?

how to check this?

Please check Linux Kernel dmesg information, can you get "optee" related information?

this is the optee related information from dmesg.:

Line 104: [ 0.000000] L2C-310 optee cache controller enabled try to unlock

Line 244: [ 0.768908] optee soc:firmware:optee: probing for conduit method from DT.

Line 245: [ 0.769082] optee soc:firmware:optee: teetz outer mutex: ret=0 pa=0x8fa00000 va=0xf0376000

Line 246: [ 0.769558] optee soc:firmware:optee: initialized driver

Re: TEE logs are not available in DMESG

yipingwang — Wed, 13 Aug 2025 09:00:31 GMT

If you configure the following settings, you will get OPTEE related information in atf(u-boot) log.

CFG_TEE_CORE_LOG_LEVEL=4
CFG_TEE_TA_LOG_LEVEL = 4

If no, it seems that you didn't build atf image with optee enabled.

You need to build atf images with option "SPD=opteed BL32=<optee_binary>" enabled.

In addition, you need to perform TA operation, then you will get related log in dmesg.

Re: TEE logs are not available in DMESG

rnamburi — Wed, 13 Aug 2025 10:44:54 GMT

Did you build ATF image with optee enabled?

Yes

Please check Linux Kernel dmesg information, can you get "optee" related information?

these are the optee traces from dmesg

Line 53: [ 0.000000] L2C-310 optee cache controller enabled try to unlock

Line 193: [ 0.769007] optee soc:firmware:optee: probing for conduit method from DT.

Line 194: [ 0.769177] optee soc:firmware:optee: teetz outer mutex: ret=0 pa=0x8fa00000 va=0xf0376000

Line 195: [ 0.769652] optee soc:firmware:optee: initialized driver

Line 350: [ 1.590184] systemd[1]: Started tee-supplicant Service.

Line 738: [ 12.083898] BT_DOMAIN_ID KPI MARKER: 12s070912666ns CON_Bt_sendGcfMsg_BSS_GAP_SetBTStateEnable