
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 discover Greengrass core and communicate with AWS IoT cloud through it.
You will need device (A Mac, Windows PC, or UNIX-like system) for running AWS Greengrass. Example will connect to Wi-Fi network, try to discover your AWS Greengrass device and send Hello World message to AWS IoT cloud through it.
This demo needs Wi-Fi network with internet access and opened 8883 and 8443 ports.


Prepare the AWS Greengrass and AWS IoT
Before running the demo it is needed to configure AWS IoT Console, AWS Greengrass:

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

2.  Create AWS Greengrass group, set up it's core and set up Hello World Lambda function (Module 1 to Module 3 Part 1): https://docs.aws.amazon.com/greengrass/latest/developerguide/gg-gs.html

    Note: If you are using Amazon EC2 service for running Greengrass Core, make sure that its public IP address (you can see when selecting your instance in AWS EC2 service administration) is set in Greengrass Core/Connectivity.

3.  Set up your device as part of your Greengrass group: https://docs.aws.amazon.com/greengrass/latest/developerguide/device-group.html

    In 2. step create one device named for example "HelloWorldDevice" (this will be your "Thing name") and save device certificates, you will need them later.

    Make note of "REST API endpoint" in Greengrass/Devices/<your device>/Interact

4.  Make sure that Greengrass core is running (e.g. on Linux you can check it with "ps aux | grep -e "greengrass"" command). If it is not running, start it with "sudo ./greengrassd start" in folder "/greengrass/ggc/packages/x.x.x/".

5.  Go to AWS IoT, find your Greengrass group and deploy it again. You should do new deployment after every configuration change.



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

Prepare the Demo
================

1.  Open file "aws_clientcredential.h" and fill in your "Thing name" and "REST API endpoint" which can be found in AWS IoT under "Greengrass/Devices/<your device>/Interact":

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

    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".

    keyCLIENT_CERTIFICATE_PEM is stored in <device id>.cert.pem file and keyCLIENT_PRIVATE_KEY_PEM is stored in <device id>.private.key file.

    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.

2.  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."

3.  Open example's project and build it.

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

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

6.  Download the program to the target board.

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

Running the demo
================

Demo is by default set to send message "Hello #0 from Amazon FreeRTOS to Greengrass Core." 3 times (can be changed with ggdDEMO_MAX_MQTT_MESSAGES).

You can check connection log in Greengrass device on path: /greengrass/ggc/var/log/system/connection_manager.log


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

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


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

MAC Address:  0:13:43:7F:9E:77 
[net] Initialized TCP/IP networking stack

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

4 37015 [wlcmgr] Connected to with IP = [192.168.199.188]

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

6 37060 [iot_thread] [INFO ][MQTT][37060] MQTT library successfully initialized.

7 37060 [iot_thread] [INFO ][DEMO][37060] Attempting automated selection of Greengrass device


8 40491 [iot_thread] JSON file retrieval completed

9 40491 [iot_thread] About to close socket.

10 40494 [iot_thread] Socket closed.

11 40494 [iot_thread] Stack high watermark for discovery helper task: 1530.

12 41456 [iot_thread] About to close socket.

13 41457 [iot_thread] Socket closed.

14 41460 [iot_thread] Stack high watermark for discovery helper task: 882.

15 41460 [iot_thread] [INFO ][DEMO][41460] Greengrass device discovered.

16 41460 [iot_thread] [INFO ][DEMO][41460] Attempting to establish MQTT connection to Greengrass.

17 42487 [iot_thread] [INFO ][MQTT][42487] Establishing new MQTT connection.

18 42491 [iot_thread] [INFO ][MQTT][42491] (MQTT connection 202144f0, CONNECT operation 202145b0) Waiting for operation completion.

19 42736 [NetRecv] [INFO] CONNACK session present bit not set.
20 42736 [NetRecv] [INFO] Connection accepted.
21 42737 [iot_thread] [INFO ][MQTT][42737] (MQTT connection 202144f0, CONNECT operation 202145b0) Wait complete with result SUCCESS.

22 42738 [iot_thread] [INFO ][MQTT][42738] New MQTT connection 2020bf20 established.

23 42740 [iot_thread] [INFO ][MQTT][42740] (MQTT connection 202144f0) MQTT PUBLISH operation queued.

24 44241 [iot_thread] [INFO ][MQTT][44241] (MQTT connection 202144f0) MQTT PUBLISH operation queued.

25 45742 [iot_thread] [INFO ][MQTT][45741] (MQTT connection 202144f0) MQTT PUBLISH operation queued.

26 47242 [iot_thread] [INFO ][DEMO][47242] Disconnecting from broker.

27 47242 [iot_thread] [INFO ][MQTT][47242] (MQTT connection 202144f0) Disconnecting connection.

28 47242 [iot_thread] [INFO] Disconnected from the broker.
29 47244 [iot_thread] [INFO ][MQTT][47244] (MQTT connection 202144f0) Network connection closed.

30 47477 [iot_thread] [INFO ][MQTT][47477] (MQTT connection 202144f0) Network connection destroyed.

31 47477 [iot_thread] [INFO ][DEMO][47477] Disconnected from the broker.

32 47477 [iot_thread] Heap low watermark: 14984. Stack high watermark: 882.

33 47477 [iot_thread] [INFO ][MQTT][47477] MQTT library cleanup done.

34 47477 [iot_thread] [INFO ][DEMO][47477] Cleaned up MQTT library.

35 47479 [iot_thread] [INFO ][DEMO][47479] memory_metrics::freertos_heap::before::bytes::87384

36 47479 [iot_thread] [INFO ][DEMO][47479] memory_metrics::freertos_heap::after::bytes::14984

37 47479 [iot_thread] [INFO ][DEMO][47479] memory_metrics::demo_task_stack::before::bytes::7856

38 47479 [iot_thread] [INFO ][DEMO][47479] memory_metrics::demo_task_stack::after::bytes::3528

39 48479 [iot_thread] [INFO ][DEMO][48479] Demo completed successfully.

40 48484 [wlcmgr] Dis-connected

41 48529 [iot_thread] [INFO ][INIT][48529] SDK cleanup done.

42 48529 [iot_thread] [INFO ][DEMO][48529] -------DEMO FINISHED-------

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
