Connection issue to portal.mbedcloud.com from STM32F769I-DISC1 board with Pelion example

Pelion Device Management [forum moved]
, ,
1

I am trying to bring up the Pelion example on a STM32F769I-DISC1 board.

I have tried pelion-example-common(pelion-example-common - Mbed OS Device Management example for various ST … | Mbed)
and pelion-ready-example (https://os.mbed.com/teams/mbed-os-examples/code/pelion-ready-example/ )
Both of the programs fails to register with portal.mbedcloud.com.

I have followed the the steps correctly from this site.
https://os.mbed.com/guides/connect-device-to-pelion/1/?board=ST-Discovery-F769NI

<< serial log >>
[BOOT] Mbed Bootloader
[BOOT] ARM: 00000000000000000000
[BOOT] OEM: 00000000000000000000
[BOOT] Layout: 0 8009328
[BOOT] Active firmware integrity check:
[BOOT] SHA256: 87C10F94E43F5F3BBC6E1CF10E76468103D61A01D65C0482F501F15A69062E2B
[BOOT] Version: 1560524045
[BOOT] Slot 0 is empty
[BOOT] Active firmware up-to-date
[BOOT] Application’s start address: 0x8010400
[BOOT] Application’s jump address: 0x80110A9
[BOOT] Application’s stack address: 0x20080000
[BOOT] Forwarding to application…
p@@
Starting Simple Pelion Device Management Client example
You can hold the user button during boot to format the storage and change the device identity.
Connecting to the network using the default network interface…
Connected to the network successfully. IP address: 10.122.16.108
Initializing Pelion Device Management Client…
Initialized Pelion Device Management Client. Registering…
Press the user button to increment the LwM2M resource value…
ADC temp: 23.2234 C, vref: 0.3665 %
Button clicked 1 times
Button clicked 2 times
[SMCC] Error occurred : MbedCloudClient::ConnectNetworkError
[SMCC] Error code : 6
[SMCC] Error details : Client in reconnection mode NetworkError

<< above error happens every 30 seconds and no device
listed here. Izuma Device Management
What could be the root cause ?
My connection credentials as below from the mbed_cloud_dev_credentials.c file .

const char MBED_CLOUD_DEV_BOOTSTRAP_ENDPOINT_NAME = “016b5222ff847a6af473872f03c00000”;
const char MBED_CLOUD_DEV_ACCOUNT_ID = “016b2914a5fc762d28a836d200000000”;
const char MBED_CLOUD_DEV_BOOTSTRAP_SERVER_URI = “coaps://bootstrap.us-east-1.mbedcloud.com:5684?aid=016b2914a5fc762d28a836d200000000”;

I am on corporate network and I able to ping the target. This proves that network stack is alive.
vgeorge@CI0700000000653:~$ ping 10.122.16.108
PING 10.122.16.108 (10.122.16.108) 56(84) bytes of data.
64 bytes from 10.122.16.108: icmp_seq=1 ttl=254 time=0.318 ms
64 bytes from 10.122.16.108: icmp_seq=2 ttl=254 time=0.384 ms

Is it possible my corporate policy blocking the port 5684 ?

Any small help to debug this issue is greatly appreciated.

Varughese George

2

You can verify your connection with netcat aka nc;

$ nc -zv bootstrap.us-east-1.mbedcloud.com 5684
Connection to bootstrap.us-east-1.mbedcloud.com 5684 port [tcp/*] succeeded!

Please try it out.

Corporate networks can and quite often will firewall traffic.

Best Regards,

Janne Kiiskilä

3

This happened to me in my Institution, I requested the IT department to open the port 5684, but they replied that it is not possible due the servers have dynamic IPs. Now I am working from home while I find a solution!

4

The issue root caused to corporate network blocking the communication.

I am able to resolve by creating a access point using raspberryPI.

Did the installations mentioned here. Just switched the configurations for eth0 and wlan0.

You need the wlan0 to act as your Internet connection, and eth0 to act as the access connection

(which is the opposite of what’s here). You can ignore step 5 and step 8.