Connect a Linux device
Securely connect a Linux device to Device Management over an IP connection.
Note: These instructions explain how to connect a generic Linux device. If you want to connect a Raspberry Pi 3, use the Raspberry Pi 3 tutorial.
This requires a Linux PC (64-bit Ubuntu/XUbuntu OS desktop environment).
Connecting the device
Open a terminal, and import the example repository to a convenient location on your development environment:
mbed import https://github.com/ARMmbed/mbed-cloud-client-example cd mbed-cloud-client-example
Download the developer certificates from the Device Management Portal:
- Log in to the portal with your credentials.
- Navigate to Device identity > Certificates.
- Click New certificate.
- Add a name and an optional description for the certificate, and click Create certificate.
- Go to Device identity > Certificates again.
- Click on your new certificate.
- Click Download developer C file to download the file
mbed_cloud_dev_credentials.cfile to the root folder of the Device Management example.
Navigate to the Device Management Client example folder, and run one of the following commands:
For a manually configured build for Release profile:
python pal-platform/pal-platform.py deploy --target=x86_x64_NativeLinux_mbedtls generate cd __x86_x64_NativeLinux_mbedtls cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE=./../pal-platform/Toolchain/GCC/GCC.cmake -DEXTERNAL_DEFINE_FILE=./../define.txt make mbedCloudClientExample.elf
For a manually configured build for Debug profile:
python pal-platform/pal-platform.py deploy --target=x86_x64_NativeLinux_mbedtls generate cd __x86_x64_NativeLinux_mbedtls cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=./../pal-platform/Toolchain/GCC/GCC.cmake -DEXTERNAL_DEFINE_FILE=./../define.txt make mbedCloudClientExample.elf
For more details on the manual build procedure, see the PAL platform utility documentation.
The manual build creates binaries under
mbed-cloud-client-example/__x86_x64_NativeLinux_mbedtls. In both cases, there are subdirectories ´Debug´ and ´Release´ respectively for the two profiles.
Note: If you experience build problems, refer to the Troubleshooting section for potential issues and workarounds.
Run the application (at the respective path, see above):
You see messages about connecting to Device Management Connect:
Client registered Endpoint Name: 013584750b3400000000000100100051 Device Id: 013584750b3400000000000100100051
Now that your device connects to Device Management, you can read information from it and control it.