hello
Customer ABB is using SE050C1 via nRF5340 + Zephyr, he in integrating our nano-package MW.
It is needed to communicate in SCP03
I suppose that first step is to compile the nanopackage library accordingly, and I believe there is a unique define involved at that stage which is CONFIG_PLUGANDTRUST_SCP03
Can I ask you how to configure it / define it ? Is it a preprocessor define that need to be passed to CMake ?
Also I see that there is another define whici is PLUGANDTRUST_SE05X_AUTH that need to be set to PlatformSCP03
How does this one relate to CONFIG_PLUGANDTRUST_SCP03 ?
Thank you,
Mehdi
thank you Michael
Would the right compilation flow be like ?
step1 - on the one hand, use CMake to build the mw library (with CONFIG_PLUGANDTRUST_SCP03 being defined in the Cmake option)
step 2 - compile the Zephyr exemple with CONFIG_PLUGANDTRUST_SCP03=y in the .proj file
I understand that only CONFIG_PLUGANDTRUST_SCP3 need to be declared in the proj file, while CONFIG_PLUGANDTRUST_SCP03 is rather a Cmake option is that correct ?
Mehdi
Hello Mehdi,
for the defines:
CONFIG_PLUGANDTRUST_SCP03: Enables the SCP03 code/libraries in the build (includes SCP03 source files, crypto dependencies)PLUGANDTRUST_SE05X_AUTH=PlatformSCP03: Tells the runtime code to actually USE SCP03 authentication when communicating with the SE050Both must be set for SCP03 to work properly.
For zephyr compilation the defines can be set in the zephyr prj.conf file, by default all is off:
Hello Mehdi,
only thing need to be done for using platform scp is:
in prj.conf file set this: CONFIG_PLUGANDTRUST_SCP03=y
I tested nano package with zephyr:
1. in prj.conf file inside the example folder (example : ..\workspace\modules\crypto\nxp-plugandtrust\examples\se05x_GetInfo\zephyr\prj.conf) , only set this: CONFIG_PLUGANDTRUST_SCP03=y
2. build example: >west build -b frdm_k64f modules/crypto/nxp-plugandtrust/examples/se05x_GetInfo/zephyr --pristine
3. flash binary : C:\nxp\workspace\build\zephyr\zephyr.bin to k64
and it works.
kind regards,
Parth