
This SDK has been patched by Embedded Artists for the iMXRT1064 Developer's Kit.
The SDK was released on 2021-12-01 and is based on NXP's 2.10.0 SDK (SDK_2_10_0_MIMXRT1064xxxxA.zip).

This is what has been patched:
* Set CPU speed according to Commercial/Industrial CPU
* Correction of the VDD_SOC_IN voltage.
* LWIP projects - added reading of the MAC address from the onboard I2C EEPROM
* Wi-Fi and Bluetooth projects
* Added an I2C driver for the gpio expander (PCA6416) and code to use it
* Added an I2C driver for the PWM gpio expander (PCA9530) and code to use it
* Modified pin muxing
* SEMC projects - changed algorithm for memory test and now test entire 32MB instead of only 4KB
* Examples using a disaplay have been updated to use PCA6416/PCA9530 for
  RST/PWR/BL signals
* BOARD_USER_BUTTON has been redirected to SW5/WAKEUP button on the uCOM Carrier Board
* USER_LED has been changed to the blue RGB LED using PCA6416
* Adjusted the USB interface number (it is different for host and device examples)
* Added support for Embedded Artists 2DS M.2 Module (EAR00386) in the NXP Wi-Fi examples
* Added support for Embedded Artists 1ZM M.2 Module (EAR00364) in the NXP Wi-Fi examples
* Added support for Embedded Artists 1XK M.2 Module (EAR00385) in the NXP Wi-Fi examples
* Changed reset pin for SD card examples

This has been added:
* LWIP projects - option to use 100/10Mbps Ethernet-PHY Adapter
* AWS projects - option to use 100/10Mbps Ethernet-PHY Adapter
* AzureRTOS projects - option to use 100/10Mbps Ethernet-PHY Adapter
* I2C probe example
* Wi-Fi (serial) examples for the CMWC1ZZABR-107-EVB (a.k.a ABR Module)

This has been removed:
* All projects for the expansion board AGM01

Important things to note:
* Read section "8 - Known Issues" in docs/MCUXpresso SDK Release Notes for EVK-MIMXRT1064.pdf
  to see known issues with the current version of the SDK.
* For Iperf examples, set compiler optimization to -O3 or similar to improve performance.
* If the hardware seems unresponsive and the debugger cannot connect/flash/erase the current program
  then the most likely cause is the running program preventing the access. To stop the currently
  running program and regain control:
  1) Press and hold down the ISP_ENABLE button (SW1)
  2) Press and hold down the RESET button (SW3)
  3) Let go of the RESET button
  4) Wait an extra second or two
  5) Release the ISP_ENABLE button
  6) The hardware is now in a mode where programming/erasing it should work



Connectors:
* J29 (micro USB) is the default UART and unless specified otherwise it is setup for 115200 8/N/1


This example has been configured to use the 1XK (IW416 or 88W8978) M.2 module. To change
which module to use, replace WIFI_BOARD_EA_1XK_M2_88W8978_IW416 in the app_config.h file
with one of the following and then rebuild the project:

    WIFI_BOARD_EA_1XK_M2_88W8978_IW416   - To use the 1XK M.2 module
    WIFI_BOARD_EA_2DS_M2_88W8801         - To use the 2DS M.2 module
    WIFI_BOARD_EA_1ZM_M2_88W8987         - To use the 1ZM M.2 module

This example requires an M.2 Module and a uSD-M2 Adapter (LBEE0ZZ1WE-TEMP)
from Murata inserted in uSD connector J34. The M.2 socket (J33) on the uCOM Carrier Board
is not used.

The uSD-M2 Adapter must be configured with:
J1  shorted in 1-2 position
J12 shorted in 2-3 position
J13 shorted in 1-2 position
J9 pin 3 must be connected to J32 pin 2 (INT) on the uCOM Carrier Board with a cable.

Due to high current consumption peaks of the M.2 module, especially during startup calibration,
you must power the uSD-M2 Adapter from an external source. The power supply from the uSD
interface is not enough. Connect a USB cable to the micro-B USB connector on the uSD-M2 Adapter,
in one end, and a PC, USB Hub or USB charger in the other end.

The BLUE LED on the uSD-M2 Adapter should be on if the adapter is configured correctly.

More information about the M.2 Modules can be found here: https://www.embeddedartists.com/m2/.
More information about the uSD-M2 Adapter can be found here: https://wireless.murata.com/usd-m2.html.

It could be possible to use the other modules as shown in the original
readme text below, however that is untested and unsupported.

Everything below this line is the original content of the readme file.
=======================================================================



Overview
========
This example demonstrates how the board can be controlled by Android mobile application with usage the AWS IoT.
User LEDs on the board can be controlled and also an action can be invoked to read data from accelerometer and report it to AWS IoT device shadow.
Please take look into section "Board settings" if there are some board limitations to control LEDs or read data from accelerometer.


Toolchain supported
===================
- IAR embedded Workbench  9.10.2
- Keil MDK  5.34
- GCC ARM Embedded  10.2.1
- MCUXpresso  11.4.0

Hardware requirements
=====================
- Micro USB cable
- EVK-MIMXRT1064 board
- Personal Computer
- One of the following Wi-Fi modules:
  - Panasonic PAN9026 SDIO ADAPTER + SD to uSD adapter
  - AzureWave AW-NM191NF-uSD
  - AzureWave AW-AM457-uSD
  - AzureWave AW-CM358-uSD

Board settings
==============
This example, by default, is built to work with the AzureWave AW-AM457-uSD. It is configured by the macro definition in file app_config.h (#define WIFI_BOARD_AW_AM457).
If you want use the AzureWave AW-NM191NF-uSD, please change the macro to WIFI_BOARD_AW_NM191.
If you want use the Panasonic PAN9026 SDIO ADAPTER, please change the macro to WIFI_BOARD_PAN9026_SDIO.
If you want use the AzureWave AW-CM358-uSD, please change the macro to WIFI_BOARD_AW_CM358.

Jumper settings for AzureWave AW-NM191NF-uSD Module:
  - J11 1-2: VIO_SD 1.8V (Voltage level of SDIO pins is 1.8V)
  - J2  1-2: 3.3V VIO_uSD (Power Supply from uSD connector)

Jumper settings for AzureWave AW-AM457-uSD Module:
  - J11 1-2: VIO_SD 1.8V (Voltage level of SDIO pins is 1.8V)
  - J2  1-2: 3.3V VIO_uSD (Power Supply from uSD connector)

Jumper settings for AzureWave AW-CM358-uSD Module:
  - J4 1-2: VIO 1.8V (Voltage level of SDIO pins is 1.8V)
  - J2 1-2: 3.3V VIO_uSD (Power Supply from uSD connector)
  - The pin 1 of J4 is not marked on the board. Please note that pin numbering of J4 is opposite to J2 (pin 1 is close to the "J4" label):
         3 2 1
         o o=o J4
      J2 o=o o
         1 2 3

Accelerometer is not used on this board.

Prepare the Demo
================
Before running the demo it is need to configure AWS IoT Console and update some of project files:

1.  Create AWS Account: https://console.aws.amazon.com/console/home

2.  Configure device in the AWS IoT Console base on this guide: https://docs.aws.amazon.com/iot/latest/developerguide/iot-sdk-setup.html

    Make note of example's "Thing name" and "REST API endpoint". These strings need to be set in the "aws_clientcredential.h".

    Example:
        static const char clientcredentialMQTT_BROKER_ENDPOINT[] = "abcdefgh123456.iot.us-west-2.amazonaws.com";
        #define clientcredentialIOT_THING_NAME "MyExample"

    In the next step you will get the "device certificate" and the "primary key". The device certificate and private key needs to be opened in text editor and its content copied into the "aws_clientcredential_keys.h".
    Or you can use the CertificateConfigurator.html (mcu-sdk-2.0\rtos\freertos\tools\certificate_configuration) to generate the "aws_clientcredential_keys.h".

    Example:
        #define keyCLIENT_CERTIFICATE_PEM "Paste client certificate here."

        Needs to be changed to:

        #define keyCLIENT_CERTIFICATE_PEM "-----BEGIN CERTIFICATE-----\n"\
        "MIIDWTCCAkGgAwIBAgIUfmv3zA+JULlMOxmz+upkAzhEkQ0wDQYJKoZIhvcNAQEL\n"\
        .
        .
        .
        "mepuT3lKmD0jZupsQ9vLQOA09rMjVMd0YPmI9ozvvWqLpjVvNTKVhsf/3slM\n"\
        "-----END CERTIFICATE-----\n"

    In the same way update the private key array.

3.  This demo needs Wi-Fi network with internet access.
    Update these macros in "aws_clientcredential.h" based on your Wi-Fi network configuration:
        #define clientcredentialWIFI_SSID       "Paste Wi-Fi SSID here."
        #define clientcredentialWIFI_PASSWORD   "Paste Wi-Fi password here."

4.  Open example's project and build it.

5.  Connect a USB cable between the PC host and the OpenSDA USB port on the target board.

6.  Open a serial terminal on PC for OpenSDA serial device with these settings:
    - 115200 baud rate
    - 8 data bits
    - No parity
    - One stop bit
    - No flow control

7.  Download the program to the target board.

8.  Either press the reset button on your board or launch the debugger in your IDE to begin running the demo.


Prepare the Android application
The Android application requires Cognito service to authorize to AWS IoT in order to access device shadows. Use Amazon Cognito to create a new identity pool:

1.  In the Amazon Cognito Console https://console.aws.amazon.com/cognito/ select "Manage Federated Identities" and "Create new identity pool".

2.  Name your pool and ensure "Enable access to unauthenticated identities" is checked. This allows the sample application to assume the unauthenticated role associated with this identity pool.
    Note: to keep this example simple it makes use of unauthenticated users in the identity pool. This can be used for getting started and prototypes but unauthenticated users should typically only be given read-only permissions in production applications. More information on Cognito identity pools including the Cognito developer guide can be found here: http://aws.amazon.com/cognito/.

3.  To obtain the Pool ID constant, select "Edit identity pool" and copy Identity pool ID (it will look like <REGION>:<ID>). This Identity pool ID (<COGNITO POOL ID>) will be used in the application (policy and configuration file).

4.  To obtain Account ID, select account name in webpage menu bar and select "My account" from drop down menu. Make note of "Account ID" under "Account Settings".

5. As part of creating the identity pool Cognito will setup two roles in Identity and Access Management (IAM) https://console.aws.amazon.com/iam/home#roles. These will be named something similar to: "Cognito_PoolNameAuth_Role" and "Cognito_PoolNameUnauth_Role".
Create policy to be attached into "Cognito_PoolNameUnauth_Role" though "Policies" menu, selecting "Create policy", "Create Your Own Policy" and copying example policy below into "Policy Document" field and naming it for example "<THING NAME>Policy". Replace <REGION>, <ACCOUNT ID> and <THING NAME> with your respective values. This policy allows the application to get and update the two thing shadows used in this sample.

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "iot:Connect"
                ],
                "Resource": [
                    "*"
                ]
            },
            {
                "Effect": "Allow",
                "Action": [
                    "iot:Publish"
                ],
                "Resource": [
                    "arn:aws:iot:<REGION>:<ACCOUNT ID>:topic/$aws/things/<THING NAME>/shadow/update",
                    "arn:aws:iot:<REGION>:<ACCOUNT ID>:topic/$aws/things/<THING NAME>/shadow/get"
                ]
            },
            {
                "Effect": "Allow",
                "Action": [
                    "iot:Subscribe",
                    "iot:Receive"
                ],
                "Resource": [
                    "*"
                ]
            }
        ]
    }

6.  Newly created policy now needs to be attached to the unauthenticated role which has permissions to access the required AWS IoT APIs by opening "Cognito_PoolNameUnauth_Role" under "Roles" menu. Then in "Permissions" tab select "Attach policy" to view list of all AWS policies where example's policy "<THING NAME>Policy" needs to be selected though checking its checkbox and clicking on "Attach policy" button.

    More information on AWS IAM roles and policies can be found here: http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_manage.html
    More information on AWS IoT policies can be found here: http://docs.aws.amazon.com/iot/latest/developerguide/authorization.html

7.  Prepare "AwsRemoteControlPreferences.properties" file with yours AWS credentials. It's structure looks like this:

    customer_specific_endpoint=<REST API ENDPOINT>
    cognito_pool_id=<COGNITO POOL ID>
    thing_name=<THING NAME>
    region=<REGION>

    Then move properties file into your Android device (application will ask for properties file though file browser dialog during first run).

8.  To run Android application do either:
    a) install and run pre-build apk on Android device (<SDK_Repository>\boards\<board_name>\aws_examples\remote_control\android\AwsRemoteControl.apk)
    b) open project in Android Studio, build it, attach Android device and Run application

    Application requires at least Android version 5.1 (Android SDK 22).

    Then in both cases when asked select AwsRemoteControlPreferences.properties file with AWS IoT preferences. Then application will establish MQTT connection to AWS server, download last state of thing's shadow and will be ready for user input.


Running the demo
================
The log below shows the output of the demo in the terminal window. The log can be different based on your Wi-Fi network configuration and based on the actions, which you have done in the Android application.

Android application displays Accelerometer data for all three axis and status of LEDs which is split into Desired and Reported section. Desired value is value wanted by user and Reported value is actual value of LEDs on device.

- When you turn on/off some of RGB LED in the Android application, the change should be visible on RGB LED on the board.
- When you refresh accelerometer data on Android application, you should see changes in the accelerometer data.

Every mentioned action takes approximately 1-3 seconds.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0 114 [Tmr Svc] Write certificate...

1 130 [iot_thread] [INFO ][DEMO][130] ---------STARTING DEMO---------


2 132 [iot_thread] [INFO ][INIT][132] SDK successfully initialized.

MAC Address:  0:13:43:91:8C:9D 
[net] Initialized TCP/IP networking stack

3 3443 [iot_thread] Connecting to nxp .....

4 12155 [wlcmgr] Connected to with IP = [192.168.1.107]

5 12193 [iot_thread] [INFO ][DEMO][12193] Successfully initialized the demo. Network type for the demo: 1

6 12193 [iot_thread] [INFO] Create a TCP connection to a2zcot8a2tqh6c-ats.iot.us-east-2.amazonaws.com:8883.
7 13297 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
8 13299 [iot_thread] [INFO] CONNACK session present bit not set.
9 13299 [iot_thread] [INFO] Connection accepted.
10 13299 [iot_thread] [INFO] Received MQTT CONNACK successfully from broker.
11 13299 [iot_thread] [INFO] MQTT connection established with the broker.
12 13299 [iot_thread] [INFO] MQTT connection successfully established with broker.


13 13299 [iot_thread] [INFO] A clean MQTT connection is established. Cleaning up all the stored outgoing publishes.


14 13300 [iot_thread] [INFO] SUBSCRIBE topic $aws/things/aws_demo/shadow/delete/accepted to broker.


15 13445 [iot_thread] [INFO] Packet received. ReceivedBytes=3.
16 13445 [iot_thread] [INFO] MQTT_PACKET_TYPE_SUBACK.


17 15455 [iot_thread] [INFO] SUBSCRIBE topic $aws/things/aws_demo/shadow/delete/rejected to broker.


18 15630 [iot_thread] [INFO] Packet received. ReceivedBytes=3.
19 15630 [iot_thread] [INFO] MQTT_PACKET_TYPE_SUBACK.


20 17640 [iot_thread] [INFO] the published payload: 
 
21 17641 [iot_thread] [INFO] PUBLISH sent for topic $aws/things/aws_demo/shadow/delete to broker with packet ID 3.


22 17857 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
23 17857 [iot_thread] [INFO] Ack packet deserialized with result: MQTTSuccess.
24 17857 [iot_thread] [INFO] State record updated. New state=MQTTPublishDone.
25 17857 [iot_thread] [INFO] PUBACK received for packet id 3.


26 17857 [iot_thread] [INFO] Cleaned up outgoing publish packet with packet id 3.


27 17895 [iot_thread] [INFO] Packet received. ReceivedBytes=92.
28 17895 [iot_thread] [INFO] De-serialized incoming PUBLISH packet: DeserializerResult=MQTTSuccess.
29 17895 [iot_thread] [INFO] State record updated. New state=MQTTPubAckSend.
30 17895 [iot_thread] [INFO] pPublishInfo->pTopicName:$aws/things/aws_demo/shadow/delete/accepted.
31 17895 [iot_thread] [INFO] Received an MQTT incoming publish on /delete/accepted topic.
32 19705 [iot_thread] [INFO] UNSUBSCRIBE sent topic $aws/things/aws_demo/shadow/delete/accepted to broker.


33 19850 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
34 19850 [iot_thread] [INFO] MQTT_PACKET_TYPE_UNSUBACK.


35 21860 [iot_thread] [INFO] UNSUBSCRIBE sent topic $aws/things/aws_demo/shadow/delete/rejected to broker.


36 22035 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
37 22035 [iot_thread] [INFO] MQTT_PACKET_TYPE_UNSUBACK.


38 24045 [iot_thread] [INFO] SUBSCRIBE topic $aws/things/aws_demo/shadow/update/delta to broker.


39 24195 [iot_thread] [INFO] Packet received. ReceivedBytes=3.
40 24195 [iot_thread] [INFO] MQTT_PACKET_TYPE_SUBACK.


41 26205 [iot_thread] [INFO] the published payload:{"state":{"desired":{"LEDstate":0},"reported":{"LEDstate":0,"accel":{"x":0,"y":0,"z":0},"LEDinfo":{"isRgbLed":false,"colors":["green"]}}},"clientToken": "token-26205"} 
 
42 26206 [iot_thread] [INFO] PUBLISH sent for topic $aws/things/aws_demo/shadow/update to broker with packet ID 7.


43 26509 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
44 26509 [iot_thread] [INFO] Ack packet deserialized with result: MQTTSuccess.
45 26509 [iot_thread] [INFO] State record updated. New state=MQTTPublishDone.
46 26509 [iot_thread] [INFO] PUBACK received for packet id 7.


47 26509 [iot_thread] [INFO] Cleaned up outgoing publish packet with packet id 7.


48 28318 [iot_thread] [INFO] AWS Remote Control Demo initialized.
49 28318 [iot_thread] [INFO] Use mobile application to control the remote device.
.
.
.
50 45680 [iot_thread] [INFO] Packet received. ReceivedBytes=161.
51 45680 [iot_thread] [INFO] De-serialized incoming PUBLISH packet: DeserializerResult=MQTTSuccess.
52 45680 [iot_thread] [INFO] State record updated. New state=MQTTPubAckSend.
53 45680 [iot_thread] [INFO] pPublishInfo->pTopicName:$aws/things/aws_demo/shadow/update/delta.
54 45680 [iot_thread] [INFO] /update/delta json payload:{"version":1051,"timestamp":1623426921,"state":{"LEDstate":1},"metadata":{"LEDstate":{"timestamp":1623426921}}}.
55 45680 [iot_thread] [INFO] version: 1051
56 45680 [iot_thread] [INFO] version:1051, ulCurrentVersion:0 

57 45884 [iot_thread] [INFO] Turn on LED
58 45884 [iot_thread] [INFO] the published payload:{"state":{"reported":{"LEDstate":1}},"clientToken": "token-45884"} 
 
59 45885 [iot_thread] [INFO] PUBLISH sent for topic $aws/things/aws_demo/shadow/update to broker with packet ID 8.


60 46144 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
61 46144 [iot_thread] [INFO] Ack packet deserialized with result: MQTTSuccess.
62 46144 [iot_thread] [INFO] State record updated. New state=MQTTPublishDone.
63 46144 [iot_thread] [INFO] PUBACK received for packet id 8.


64 46144 [iot_thread] [INFO] Cleaned up outgoing publish packet with packet id 8.


65 47953 [iot_thread] [INFO] Successfully performed update.
.
.
.
66 49423 [iot_thread] [INFO] Packet received. ReceivedBytes=161.
67 49423 [iot_thread] [INFO] De-serialized incoming PUBLISH packet: DeserializerResult=MQTTSuccess.
68 49423 [iot_thread] [INFO] State record updated. New state=MQTTPubAckSend.
69 49423 [iot_thread] [INFO] pPublishInfo->pTopicName:$aws/things/aws_demo/shadow/update/delta.
70 49423 [iot_thread] [INFO] /update/delta json payload:{"version":1053,"timestamp":1623426925,"state":{"LEDstate":0},"metadata":{"LEDstate":{"timestamp":1623426925}}}.
71 49423 [iot_thread] [INFO] version: 1053
72 49423 [iot_thread] [INFO] version:1053, ulCurrentVersion:1051 

73 49625 [iot_thread] [INFO] Turn off LED
74 49625 [iot_thread] [INFO] the published payload:{"state":{"reported":{"LEDstate":0}},"clientToken": "token-49625"} 
 
75 49626 [iot_thread] [INFO] PUBLISH sent for topic $aws/things/aws_demo/shadow/update to broker with packet ID 9.


76 49875 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
77 49875 [iot_thread] [INFO] Ack packet deserialized with result: MQTTSuccess.
78 49875 [iot_thread] [INFO] State record updated. New state=MQTTPublishDone.
79 49875 [iot_thread] [INFO] PUBACK received for packet id 9.


80 49875 [iot_thread] [INFO] Cleaned up outgoing publish packet with packet id 9.


81 51684 [iot_thread] [INFO] Successfully performed update.
.
.
.
82 54021 [iot_thread] [INFO] Packet received. ReceivedBytes=167.
83 54021 [iot_thread] [INFO] De-serialized incoming PUBLISH packet: DeserializerResult=MQTTSuccess.
84 54021 [iot_thread] [INFO] State record updated. New state=MQTTPubAckSend.
85 54021 [iot_thread] [INFO] pPublishInfo->pTopicName:$aws/things/aws_demo/shadow/update/delta.
86 54021 [iot_thread] [INFO] /update/delta json payload:{"version":1055,"timestamp":1623426930,"state":{"accelUpdate":1},"metadata":{"accelUpdate":{"timestamp":1623426930}}}.
87 54021 [iot_thread] [INFO] version: 1055
88 54021 [iot_thread] [INFO] version:1055, ulCurrentVersion:1053 

89 54022 [iot_thread] [INFO] Update accelerometer.
90 54024 [iot_thread] [INFO] the published payload:{"state":{"desired":{"accelUpdate":null},"reported":{"accel":{"x":-5,"y":-15,"z":1001}}},"clientToken": "token-54024"} 
 
91 54024 [iot_thread] [INFO] PUBLISH sent for topic $aws/things/aws_demo/shadow/update to broker with packet ID 10.


92 54301 [iot_thread] [INFO] Packet received. ReceivedBytes=2.
93 54301 [iot_thread] [INFO] Ack packet deserialized with result: MQTTSuccess.
94 54301 [iot_thread] [INFO] State record updated. New state=MQTTPublishDone.
95 54301 [iot_thread] [INFO] PUBACK received for packet id 10.


96 54301 [iot_thread] [INFO] Cleaned up outgoing publish packet with packet id 10.


97 56110 [iot_thread] [INFO] Successfully performed update.
.
.
.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
