Skip to content
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

Closed
LordParsley opened this issue Jan 1, 2021 · 5 comments
Closed

Secure server connection attempt hangs on v2.1.1 #12

LordParsley opened this issue Jan 1, 2021 · 5 comments

Comments

@LordParsley
Copy link

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:

17:06:39.841 -> Starting connection to server...

To Reproduce

Steps to reproduce the behaviour:

  1. Set up the Wio Terminal's networking based on https://wiki.seeedstudio.com/Wio-Terminal-Network-Overview/.
  2. In the above, use the latest release of Seeed_Arduino_rpcUnified (v2.1.1).
  3. Run the demo programme.
  4. The Wio output remains on "Connecting to Server.." forever.

Bisecting previous versions, this behaviour seems to have started on commit 98cd4a07 which was merged into v2.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 commit ad514c73 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?).

@Pillar1989
Copy link
Member

@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.

@Pillar1989
Copy link
Member

@lakshanthad
Copy link
Contributor

lakshanthad commented Jan 4, 2021

Hi @LordParsley,

I have tested the following tutorial with rpcUnified v2.1.1 and worked perfectly:
https://wiki.seeedstudio.com/Wio-Terminal-Reading-Github/

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:
https://wiki.seeedstudio.com/Wio-Terminal-Network-Overview/

Please let me know the result

Best Regards,
Lakshantha

@LordParsley
Copy link
Author

Thanks very much @lakshanthad ! Appreciated. I see I was on 20201201-seeed-ambd-firmware-rpc-v2.0.3. I'll upgrade, retest & confirm.

@LordParsley
Copy link
Author

Thanks @lakshanthad – working 100% on v2.1.1 with the latest firmware 20201228-seeed-ambd-firmware-rpc-v2.1.0.

Sorry I missed that f/w update & thanks for the guidance! I've subscribed to releases now 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants