
This SDK has been patched by Embedded Artists for the iMXRT1064 Developer's Kit.
The SDK was released on 2024-03-25 and is based on NXP's 2.15.000 SDK (SDK_2_15_000_MIMXRT1064xxxxB.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
* 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
* SEMC projects - changed algorithm for memory test and now test entire 32MB instead of only 4KB
* Examples using a display 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)
* Changed the Wi-Fi examples to use the Embedded Artists 1XK M.2 Module (EAR00385) as default
* Many of the projects have been updated to use a more complete pin_mux.c file where all
  necessary pins have been initialized. The SDK examples used to only configure the pins
  that they use (and often not every pin) and most of the time the configuration was only
  for MUX:ing and not the PAD settings (pull up/down/none, drive strength and slew).
* 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

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


All CAN-related examples use either
* FLEXCAN2 on GPIO_AD_B0_14 and GPIO_AD_B0_15 or
* FLEXCAN3 on GPIO_AD_B0_14 and GPIO_AD_B0_15
So it is the same physical pins regardless of bus selection.

The uCOM Carrier Board rev C has two onboard CAN trancievers.
The examples only use one bus so it is up to personal
preference which of the two transcievers to use (channel A
or channel B).

The uCOM Carrier Boards older than rev C (rev PB2, PB3 and B)
have no CAN trancievers. However, using for example the
Adafruit CAN Pal (https://www.adafruit.com/product/5708)
makes it possible to run the CAN bus examples in the SDK.

On uCOM Carrier Board rev PB2 or PB3:

    J15-37 connects to TX on the Adafruit board
    J15-38 connects to RX on the Adafruit board
    J31-7  connects to VCC on the Adafruit board
    J31-8  connects to GND on the Adafruit board

On uCOM Carrier Board rev B:

    J15-29 connects to TX on the Adafruit board
    J15-30 connects to RX on the Adafruit board
    J31-7  connects to VCC on the Adafruit board
    J31-8  connects to GND on the Adafruit board

On uCOM Carrier Board rev C:

    Using CAN channel A:
        JP51-2 connects to JP48-1 for TX
        JP51-1 connects to JP48-2 for RX

        CAN-A_H is available on JP49-1
        CAN-A_L is available on JP49-2
        GND     is available on JP49-3

    Using CAN channel B:
        JP51-2 connects to JP48-4 for TX
        JP51-1 connects to JP48-5 for RX

        CAN-B_H is available on JP50-1
        CAN-B_L is available on JP50-2
        GND     is available on JP50-3


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



Hardware requirements
=====================
- Mini/micro USB cable
- MIMXRT1064-EVK board
- 3.3V CAN transceiver
- Supported CAN interface (IXXAT, Vector, Kvaser, etc.)
- Personal Computer
- FreeMASTER 2.5 or later installed on PC

Board settings
==============
CAN transceiver is available on board, at pins J11

Prepare the demo
===============
1.  Connect a USB cable between the host PC and the Debug USB port on the target board.
2.  Connect CAN transceiver to CAN interface on PC. Make sure the CAN bus is properly terminated.
3.  Compile and download the program to the target microcontroller.
4.  Run and resume application execution when debugger stops in the main() function.

Connect with FreeMASTER
=======================
5.  Run FreeMASTER, use the Connection Wizard or open Project Options.
6.  Select FreeMASTER-over-CAN communication plug-in at 500kbps.
7.  Start communication, FreeMASTER loads the initial TSA Active Content links in the Welcome page.
8.  Click the "FreeMASTER Demonstration Project (embedded in device)" in the Welcome page.
9.  The demo is now running, you should be able to watch variable values and graphs.

More information
================
Read more information about FreeMASTER tool at http://www.nxp.com/freemaster.
Feel free to ask questions and report issues at FreeMASTER's 
community page at https://community.nxp.com/community/freemaster
