-
Notifications
You must be signed in to change notification settings - Fork 10
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
Secure server connection attempt hangs on v2.1.1 #12
Comments
@lakshanthad @matsujirushi We need to confirm as soon as possible whether this is a problem with the RTL SDK or with our communication protocol itself. Preferably it is a problem with the RTL SDK and I can contact the RTL FAE to resolve the issue. |
Hi @LordParsley, I have tested the following tutorial with Make sure to update your RTL firmware as well. Currently the RTL firmware is at v2.1.0 Please follow the wiki below to burn the latest RTL firmware: Please let me know the result Best Regards, |
Thanks very much @lakshanthad ! Appreciated. I see I was on |
Thanks @lakshanthad – working 100% on Sorry I missed that f/w update & thanks for the guidance! I've subscribed to releases now 😉 |
Describe the bug
In the tutorial, Accessing to GitHub using Wio Terminal, a secure connection is made to https://api.github.com/repos/micropython/micropython using a CA certificate &
WiFiClientSecure
.Instead of connecting to the server, the example programme hangs on:
To Reproduce
Steps to reproduce the behaviour:
Seeed_Arduino_rpcUnified
(v2.1.1
).Bisecting previous versions, this behaviour seems to have started on commit
98cd4a07
which was merged intov2.1.0
.❌ commit
f8935b82
:v2.1.1
❌ commit
c0be4e91
:v2.1.0
❌ ... commit
98cd4a07
: reduce delay✅ commit
ad514c73
: add null pointer check in pbuf erpc functions✅ commit
4fd46b11
:v2.0.2
Expected behaviour
A successful connection to Github should be followed by parsing the JSON response & displaying the number of stars, etc. on the repo.
The tutorial runs as expected when using
Seeed_Arduino_rpcUnified
v2.0.2
& the last commitad514c73
before merging in "reduce delay" related work.Additional context
I'm not really sure how to see debug output for RPC (or really how it works), but since the normal behaviour of
WifiSecureClient
is to time out – & it never does – it seems like the underlying client is never getting the message intended for it (or else the RPC response is not returned?).The text was updated successfully, but these errors were encountered: