SE050ARD-E with Raspberry Pi - SCP03

[psvz]

Following https://www.nxp.com/docs/en/application-note/AN12570.pdf

Para 5.3: with ccmake . I have out of the box:

PTMW_SCP SCP03_SSS
PTMW_SE05X_Auth None

It won't let me change None -> PlatfSCP03 saying:

accessManager is not copied to default binary directory upon install

What do I do to make it work?

Following paragraph 5.2.2 this seems false:

EdgeLock SE Plug & Trust Middleware will first look for the default path
/tmp/SE05X/plain_scp.txt, if it is not able to find the file, it will try to use the
environment variable EX_SSS_BOOT_SCP03_PATH, and lastly, it will fall back to pre-compiled keys.

I exported EX_SSS_BOOT_SCP03_PATH and Figure 29 won't appear - instead, it still says

sss :WARN :Communication channel is Plain.

Is this expected?

[michaelsalfer · Accepted solution]

Hello,

this (accessManager is not copied to default binary directory upon install) is only a message to make you aware that the binary will not be copied. 

Did you after the "c"onfigure step as well do the "g"enerate step?

If PTMW_SE05X_Auth is set to any authentication value then the common example startup code will always execute the authentication - if it fails, then the example will not be started (sss_entry() will not be called). 

Kind regards,
Michael

[psvz]

@michaelsalfer Although se05x_Minimal now behaves as expected i.e.,

App :INFO :Using default PlatfSCP03 keys.

I have similar problem with ssscli still:

ssscli se05x uid

sss :WARN :Communication channel is Plain.

I have built ssscli in letter with para 9.3.1.3 of the docs. How do I make ssscli use SCP03, please?

[psvz]

@michaelsalfer I think I have figured it out. Sorry - I never used ccmak before. I expected option list when I pressed "c" - and "Enter" is actually what making the change. All Sorted!

[psvz]

Hi Michael
I didn't do 'g' step because I do not know how to change None -> PlatfSCP03 in ccmake before the 'g' step. What do I miss?