Hi there,
I am trying to validate the SE050E chip interfaced in our custom IMX8MP based board using the middleware example se05x_GetInfo. I have built and deployed the middleware using the application note AN13027.pdf . Since the SE is interfaced with the i2c-4 so i have modified the
static char* default_axSmDevice_name = "/dev/i2c-1";
to static char* default_axSmDevice_name = "/dev/i2c-3"; in simw top/hostlib/hostLib/platform/linux/i2c_a7.c file.
Still I am facing the error:
root@imx8mp-lpddr4-evk:~# se05x_GetInfo
App :INFO :PlugAndTrust_v04.05.00_20231201
App :INFO :Running se05x_GetInfo
App :INFO :If you want to over-ride the selection, use ENV=EX_SSS_BOOT_SSS_PORT or pass in command line arguments.
smCom :ERROR:Failed writing data (nrWritten=-1).
smCom :ERROR: - Error in I2C Write.....
smCom :ERROR:phNxpEseProto7816_SendRawFrame Error phNxpEse_WriteFrame
smCom :ERROR:TransceiveProcess Transceive send failed, going to recovery!
smCom :ERROR:phNxpEseProto7816_Open failed
smCom :ERROR: Failed to Open session
sss :ERROR:SM_I2CConnect Failed. Status 7012
App :ERROR:sss_session_open failed
App :ERROR:ex_sss_session_open Failed
App :ERROR:!ERROR! ret != 0.
I have also attached the cmake-conf.txt for cmake configuration.
Can anyone suggest if any other changes are required in the source?
Hi @pratham_malaviya ,
Did you try the i2cdetect command like below to probe the SE device on /dev/i2c-3?
i2cdetect -y -a -q 3
and you don't need to change the source code at all, just use the following command before running any demo out of MW.
export EX_SSS_BOOT_SSS_PORT=/dev/i2c-3
Hope that helps,
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Hi @Kan_Li ,
I have tried with the given command and I am getting the output as below
root@imx8mp-lpddr4-evk:~# i2cdetect -y -a -q 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
10: 10 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- 21 -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- 55 -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 7f
root@imx8mp-lpddr4-evk:~# and by testing with Getinfo utility same error is there,
root@imx8mp-lpddr4-evk:~/simw-top_build/imx_native_se050_t1oi2c/bin# ./se05x_GetInfo
App :INFO :PlugAndTrust_v04.05.00_20231201
App :INFO :Running ./se05x_GetInfo
App :INFO :Using PortName='/dev/i2c-3' (ENV: EX_SSS_BOOT_SSS_PORT=/dev/i2c-3)
smCom :ERROR:Failed writing data (nrWritten=-1).
smCom :ERROR: - Error in I2C Write.....
smCom :ERROR:phNxpEseProto7816_SendRawFrame Error phNxpEse_WriteFrame
smCom :ERROR:TransceiveProcess Transceive send failed, going to recovery!
smCom :ERROR:phNxpEseProto7816_Open failed
smCom :ERROR: Failed to Open session
sss :ERROR:SM_I2CConnect Failed. Status 7012
App :ERROR:sss_session_open failed
App :ERROR:ex_sss_session_open Failed
App :ERROR:!ERROR! ret != 0.Can you please guide me to validate it?
Best Regards,
Pratham
Hi @pratham_malaviya ,
The default I2C address for SE050E is 0x48, so from your test, there is no such device on /dev/i2c-3, is there any connection issue between the host and SE050E on your board? Is it ok to have the schematics for a review?
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------