-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zariot new SIMs - retrieve atsign details #395
Comments
Thanks colin for your help yesterday with NoPorts all up and running on the remote RAK test environment. So what is happening? Well the device itself is obviously using the SIM at the same time i.e. reading the IMSI, updating ciphering keys, AKA etc. Close channel 1: AT+CSIM=10,"0070800100" Now the second thing I notice: Every so often the modem is unresponsive to AT+CSIM commands: AT+CSIM=10,"0070000001" I type AT again and retry the command: AT+CSIM=10,"0070000001" Then success? you may have to have this in your code? as an exception handler or such like ... Next to prove finally that I can read the @id here it is: OK OK OK But see I retried the command see in red above, and this is using a logical channel. So my advice is always to close the channel after a session and request one at the start i.e. Open Channel: Close Channel: If in doubt open another the terminals typically only ever use three at most. There are four, so make use of them. Final thing avoid busy times for SIMs i.e. boot strap. There is a huge amount of requests to the SIM and the SIM is really only a half duplex asynchronous device. Ther terminal will just reject requests during this period. It is probably why I didn't have the issues you saw, because by the time I used the device, I was well past the bootstrap. Oh yes Random challenge: AT+CSIM=10,"8184000000" A final note. Do I think this is a SIM problem? Any more problems ping me your code and I'll have a look, no problem 😉 Best Regards and thanks in advance for your attention. Jerry |
@cconstab should I move to backlog or is this still a priority? |
We need this to work so please prioritize |
We need to be able to grab the CRAM and then ask the SIM for a keypair and then for signing operatoons. So only the SIM has the private PKAM key |
No updates in PR71. carrying over |
Describe the bug
While trying to access the atsign details loaded in the SIM batch that Zariot shipped to Colin, getting an error while selecting the IoTSafe app.
+CSIM: 6,"019000"
OK
AT+CSIM=24,"01A4040007A0000005590010"
+CME ERROR: 0
Steps to reproduce
sshnp -f @scrapbookgemini -t @mwcpi -d raksign1 -h @rv_am
connect to minicom terminal
Run the below AT commands
+CSIM: 6,"019000"
OK
AT+CSIM=24,"01A4040007A0000005590010"
+CME ERROR: 0
Expected behavior
select IoT safe app command should return success without error code
Screenshots
No response
Smartphones
x
Were you using an atApplication when the bug was found?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: