I am working with a provisioned secure element se050 and I am suddenly getting error messages instead of the id list.
I use these commands and I would normally get an output of a bunch of key ids.
ssscli connect se05x t1oi2c non
ssscli se05x readidlist
But suddenly I am seeing these two error messages on two different chips:
ERROR:cli.cli:invalid load key, '\x00'.
ERROR:cli.cli:'Context' object has no attribute 'session'
ERROR:cli.cli:Ran out of input
ERROR:cli.cli:'Context' object has no attribute 'session'
A power cycle doesn't help.
Does anyone know what's going on?
The devices these chips have been installed on have been undergoing stress and environmental testing -40C to +65C.
Thanks.
Hi @Jamier ,
Which variant of SE05x was used in your test? Have you tried to rebuild sssapisw within the MW with the verbose log level? It would be very helpful to have the log during this issue.
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.
-------------------------------------------------------------------------------
Thanks for the suggestion.
I ended up getting it working by reprogramming my BSP. I didn't try the verbose log as I didn't have the time to do the setup for that. I suspect the problem was caused by corrupted files and not by anything to do with the chip or the i2c communication.