Skip to content

Commit f8b51bc

Browse files
authored
Update how-to-connect-mxchip-iot-devkit.md
1 parent 4f1be26 commit f8b51bc

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

articles/iot-dps/how-to-connect-mxchip-iot-devkit.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,13 +68,13 @@ A typical unique device secret is a 64-character string, as seen in the followin
6868
```
6969
19e25a259d0c2be03a02d416c05c48ccd0cc7d1743458aae1cb488b074993eae
7070
```
71-
c
71+
7272
Each of two characters is used as the Hex value in the security calculation. The preceding sample UDS is resolved to: `0x19`, `0xe2`, `0x5a`, `0x25`, `0x9d`, `0x0c`, `0x2b`, `0xe0`, `0x3a`, `0x02`, `0xd4`, `0x16`, `0xc0`, `0x5c`, `0x48`, `0xcc`, `0xd0`, `0xcc`, `0x7d`, `0x17`, `0x43`, `0x45`, `0x8a`, `0xae`, `0x1c`, `0xb4`, `0x88`, `0xb0`, `0x74`, `0x99`, `0x3e`, `0xae`.
7373

7474
To save a unique device secret on the DevKit:
7575

7676
1. Open the serial monitor by using a tool such as Putty. See [Use configuration mode](https://microsoft.github.io/azure-iot-developer-kit/docs/use-configuration-mode/) for details.
77-
c
77+
7878
2. With the DevKit connected to your computer, hold down the **A** button, and then press and release the **Reset** button to enter configuration mode. The screen shows the DevKit ID and Configuration.
7979

8080
3. Take the sample UDS string and change one or more characters to other values between `0` and `f` for your own UDS.
@@ -121,7 +121,14 @@ c
121121
![Upload certificate](./media/how-to-connect-mxchip-iot-devkit/upload-cert.png)
122122

123123
> [!NOTE]
124-
> If you have an error with this message: {"message":"BadRequest:{\r\n \"errorCode\": 400004,\r\n \"trackingId\": \"1b82d826-ccb4-4e54-91d3-0b25daee8974\",\r\n \"message\": \"The certificate is not a valid base64 string value\",\r\n \"timestampUtc\": \"2018-05-09T13:52:42.7122256Z\"\r\n}"} you should open the certificate file **.pem** as text (open with Notepad or any text editor) and delete the lines "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----"
124+
> If you have an error with this message:
125+
>
126+
> `{"message":"BadRequest:{\r\n \"errorCode\": 400004,\r\n \"trackingId\": \"1b82d826-ccb4-4e54-91d3-0b25daee8974\",\r\n \"message\": \"The certificate is not a valid base64 string value\",\r\n \"timestampUtc\": \"2018-05-09T13:52:42.7122256Z\"\r\n}"}`
127+
>
128+
> Open the certificate file **.pem** as text (open with Notepad or any text editor), and delete the lines:
129+
>
130+
> `"-----BEGIN CERTIFICATE-----"` and `"-----END CERTIFICATE-----"`.
131+
>
125132
126133

127134
## Start the DevKit

0 commit comments

Comments
 (0)