-
Notifications
You must be signed in to change notification settings - Fork 56
Fails to connect with K64F and ESP8266 #205
Comments
ARM Internal Ref: IOTCLT-1563 |
@sarahmarshy - do you think the linked issue is behind this or not? We have a CI run for this example which runs also over WiFi and it is working (with this exact combination). I also did a manual test myself as well, using the current top of the master.
built it with
outcome binary had these sizes:
and logs show this:
So, it was successfull. I can also see the device via connector.mbed.com. |
Hi, @sarahmarshy - you could also try to set on the client logs, modify the mbed_app.json - "mbed-trace.enable": 0 to 1, potentially also enabling the TLS logs as well. |
Hi @sarahmarshy, @JanneKiiskila This is a duplicated issue. I reported another one, please refer |
@sarahmarshy - can you confirm you were also using |
@JanneKiiskila Sorry, I have been out of office. I can confirm that is how this was compiled. Can you confirm your mbed-os hash? Mine is: Here is the full log with trace enabled:
|
My mbed-os.lib was pointing to: 305f5c491e34d86098e9da91b322017549c189ff |
Hi, Can you please specify the version of the compiler used here? |
Closing, it should work. |
Full log:
The text was updated successfully, but these errors were encountered: