periodic update 10/02/2020 13:15 PDT

Author: robhath

doc_source/portingguide/afr-echo-server.md

@@ -13,24 +13,32 @@ To run the TLS echo server, you must install the following:
 After you finish the prerequisites, you must enter the following commands to create your credentials\.
 
 **Server**  
-The following `openssl` command generates a self\-signed server certificate\.  
+The following `openssl` command generates a self\-signed server certificate\.    
+**RSA**  
 
 ```
 openssl req -newkey rsa:2048 -nodes -x509 -sha256 -out certs/server.pem -keyout certs/server.key -days 365 -subj "/C=US/ST=WA/L=Place/O=YourCompany/OU=IT/CN=www.your-company-website.com/emailAddress=yourEmail@your-company-website.com"
+```  
+**EC**  
+
+```
+openssl req -new -x509 -nodes -newkey ec:<(openssl ecparam -name prime256v1) -keyout certs/server.key -out certs/server.pem -days 365 -subj "/C=US/ST=WA/L=Place/O=YourCompany/OU=IT/CN=www.your-company-website.com/emailAddress=yourEmail@your-company-website.com"
 ```
 
 **Client**  
-The following `openssl` commands generate a client certificate\.  
+The following `openssl` commands generate a client certificate\.    
+**RSA**  
 
 ```
 openssl genrsa -out certs/client.key 2048
-```
-
-```
 openssl req -new -key certs/client.key -out certs/client.csr -subj "/C=US/ST=WA/L=Place/O=YourCompany/OU=IT/CN=www.your-company-website.com/emailAddress=yourEmail@your-company-website.com"
-```
+openssl x509 -req -in certs/client.csr -CA certs/server.pem -CAkey certs/server.key -CAcreateserial -out certs/client.pem -days 365 -sha256
+```  
+**EC**  
 
 ```
+ecparam -genkey -name prime256v1 -out certs/client.key 
+openssl req -new -key certs/client.key -out certs/client.csr -subj "/C=US/ST=WA/L=Place/O=YourCompany/OU=IT/CN=www.your-company-website.com/emailAddress=yourEmail@your-company-website.com"
 openssl x509 -req -in certs/client.csr -CA certs/server.pem -CAkey certs/server.key -CAcreateserial -out certs/client.pem -days 365 -sha256
 ```
 
@@ -100,10 +108,10 @@ Before you run the TCP tests on your device, we recommend that you read [Getting
 After you complete the steps in [Create credentials](#afr-echo-server-credentials), you should have the following files:
 + `certs/server.pem`
 + `certs/server.key`
++ `certs/server.srl`
 + `certs/client.pem`
 + `certs/client.key`
 + `certs/client.csr`
-+ `certs/server.srl`
 
 Make the following changes to these files:
 
@@ -116,7 +124,7 @@ Make the following changes to these files:
 + Set `keyCLIENT_CERTIFICATE_PEM` to the contents of `certs/client.pem`\.
 + Leave `keyJITR_DEVICE_CERTIFICATE_AUTHORITY_PEM` as `NULL`\.
 + Set `keyCLIENT_PRIVATE_KEY_PEM` to the contents of `certs/client.key`\.
-+ For more information, see [ Configuring the FreeRTOS demos](https://docs.aws.amazon.com/freertos/latest/userguide/freertos-configure.html)\.
++ For more information, see [ Configuring the FreeRTOS demos](https://docs.aws.amazon.com/freertos/latest/userguide/freertos-prereqs.html#freertos-configure)\.
 
  `freertos/tests/include/aws_test_tcp.h`   
 + Set `tcptestECHO_HOST_ROOT_CA` to the contents of `certs/server.pem`\.

doc_source/portingguide/afr-porting-ble.md

@@ -161,6 +161,8 @@ The `CMakeLists.txt` template list file under `freertos/vendors/vendor/boards/bo
 
 1. Execute the `runPI.sh` script\.
 
+1. Clear any existing BLE bonds stored in the device\.
+
 1. Build the test project, and then flash it to your device for execution\.
 
 1. Check the test results in the UART console\.

doc_source/portingguide/afr-porting-mqtt.md

@@ -2,7 +2,7 @@
 
 Devices on the edge can use the MQTT protocol to communicate with the AWS Cloud\. AWS IoT hosts an MQTT broker that sends and receives messages to and from connected devices at the edge\.
 
-The MQTT library implements the MQTT protocol for devices running FreeRTOS\. The MQTT library does not need to be ported, but your device's test project must pass all MQTT tests for qualification\. For more information, see [FreeRTOS MQTT Library](https://docs.aws.amazon.com/freertos/latest/userguide/freertos-lib-cloud-mqtt.html.html) in the FreeRTOS User Guide\.
+The MQTT library implements the MQTT protocol for devices running FreeRTOS\. The MQTT library does not need to be ported, but your device's test project must pass all MQTT tests for qualification\. For more information, see [FreeRTOS MQTT Library](https://docs.aws.amazon.com/freertos/latest/userguide/freertos-lib-cloud-mqtt.html) in the FreeRTOS User Guide\.
 
 ## Prerequisites<a name="testing-prereqs-mqtt"></a>
 

doc_source/portingguide/cmake-template.md

@@ -36,6 +36,7 @@ The first section of the template file defines the metadata that is used to disp
 | SUPPORTED\_IDE | A semicolon\-delimited list of IDs for the IDEs that the board supports\. | 
 | IDE\_ID\_NAME | The name of the supported IDE\. Replace ID with the ID listed for the IDE in the SUPPORTED\_IDE field\. | 
 | IDE\_ID\_COMPILER | A semicolon\-delimited list of names of supported compilers for the supported IDE\. Replace ID with the ID listed for the IDE in the SUPPORTED\_IDE field\. | 
+| KEY\_IMPORT\_PROVISIONING |  Set to TRUE if the board demo project imports the credentials from the pre\-provisioned `aws_clientcredential_keys.h` header file; in this case, **Quick Connect** will be enabled in the FreeRTOS console\. Set to FALSE if the intended board provisioning mechanism is JITR/JITP or multi\-account registration; in this case, **Quick Connect** will be disabled in the FreeRTOS console\.  | 
 
 ## Compiler settings<a name="cmake-compiler"></a>
 

doc_source/qualificationguide/cmake-template.md

@@ -36,6 +36,7 @@ The first section of the template file defines the metadata that is used to disp
 | SUPPORTED\_IDE | A semicolon\-delimited list of IDs for the IDEs that the board supports\. | 
 | IDE\_ID\_NAME | The name of the supported IDE\. Replace ID with the ID listed for the IDE in the SUPPORTED\_IDE field\. | 
 | IDE\_ID\_COMPILER | A semicolon\-delimited list of names of supported compilers for the supported IDE\. Replace ID with the ID listed for the IDE in the SUPPORTED\_IDE field\. | 
+| KEY\_IMPORT\_PROVISIONING |  Set to TRUE if the board demo project imports the credentials from the pre\-provisioned `aws_clientcredential_keys.h` header file; in this case, **Quick Connect** will be enabled in the FreeRTOS console\. Set to FALSE if the intended board provisioning mechanism is JITR/JITP or multi\-account registration; in this case, **Quick Connect** will be disabled in the FreeRTOS console\.  | 
 
 ## Compiler settings<a name="cmake-compiler"></a>
 

doc_source/userguide/afr-bridgekeeper-dt-bt.md

@@ -99,20 +99,36 @@ The `ssh-copy-id` command assumes the public key is named `id_rsa.pub`\. On macO
                          "id": "ble-test-raspberry-pi-1",
                          "connectivity": {
                              "protocol": "ssh",
-                             "ip": "rasp-pi-id-address"
+                             "ip": "rasp-pi-ip-address"
                          }
                      }
                  ]
              }
          ]
          ```
 
+      1. If you didn't choose to use public key authentication for SSH, add the following to the `connectivity` section of the `resource.json` file\.
+
+         ```
+         "connectivity": {
+             "protocol": "ssh",
+             "ip": "rasp-pi-ip-address",
+             "auth": {
+                 "method": "password",
+                 "credentials": {
+                     "user": "root",
+                     "password": "idtafr"
+                 }
+             }
+         }
+         ```
+
       1. \(Optional\) If you chose to use public key authentication for SSH, add the following to the `connectivity` section of the `resource.json` file\.
 
          ```
          "connectivity": {
              "protocol": "ssh",
-             "ip": "rasp-pi-id-address",
+             "ip": "rasp-pi-ip-address",
              "auth": {
                  "method": "pki",
                  "credentials": {

doc_source/userguide/ble-demo.md

@@ -4,15 +4,15 @@
 
 FreeRTOS Bluetooth Low Energy includes three demo applications:
 
-### [MQTT over Bluetooth Low Energy](#ble-demo-mqtt) demo<a name="w14aac11c11b3b5"></a>
+### [MQTT over Bluetooth Low Energy](#ble-demo-mqtt) demo<a name="w15aac19c11b3b5"></a>
 
 This application demonstrates how to use the MQTT over Bluetooth Low Energy service\.
 
-### [Wi\-Fi provisioning](#ble-demo-wifi) demo<a name="w14aac11c11b3b7"></a>
+### [Wi\-Fi provisioning](#ble-demo-wifi) demo<a name="w15aac19c11b3b7"></a>
 
 This application demonstrates how to use the Bluetooth Low Energy Wi\-Fi Provisioning service\.
 
-### [Generic Attributes Server](#ble-demo-server) demo<a name="w14aac11c11b3b9"></a>
+### [Generic Attributes Server](#ble-demo-server) demo<a name="w15aac19c11b3b9"></a>
 
 This application demonstrates how to use the FreeRTOS Bluetooth Low Energy middleware APIs to create a simple GATT server\.
 
@@ -287,7 +287,7 @@ This policy is different from the IAM policy created for the cognito authenticat
 
 **To discover and establish secure connections with your microcontroller over Bluetooth Low Energy**
 
-1. In order to pair your microcontroller and mobile device securely \(step 6\), you need a serial terminal emulator with both input and output capabilities \(such as TeraTerm\)\. Configure the terminal to connect to your board by a serial connection as instructed in [Installing a terminal emulator](uart-term.md)\.
+1. In order to pair your microcontroller and mobile device securely \(step 6\), you need a serial terminal emulator with both input and output capabilities \(such as TeraTerm\)\. Configure the terminal to connect to your board by a serial connection as instructed in [Installing a terminal emulator](gsg-troubleshooting.md#uart-term)\.
 
 1. Run the Bluetooth Low Energy demo project on your microcontroller\.