
This SDK has been patched by Embedded Artists for the iMXRT1166 Developer's Kit.
The SDK was released on 2024-04-16 and is based on NXP's 2.15.0 SDK (SDK_2_15_000_MIMXRT1166xxxxx.zip).

This is what has been patched:
* LWIP projects - added reading of the MAC address from I2C EEPROM either on the 100Mbit adapter
  or on the uCOM board
* 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
* SDRAM size has been corrected to 32Mb (including linker files, MPU and DCD)
* The RTL8211F Ethernet PHY driver has been extended to also work with the AR8031DS PHY.
  The difference between the PHYs are minimal and extending the driver and letting the
  PHY ID decide which instructions to use makes switching PHYs seamless.
* SEMC projects - changed to correct settings for the SDRAM
* SEMC projects - changed algorithm for memory test and now test entire 32MB instead of only 4KB
* Examples using eLCDIF/LCDIFv2 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
* Touch: I2C bus and GPIOs have been changed for RST/INT
* Camera pins
* 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
* Corrected the ethernet PHY addresses
* Changed CORE clock depending on speed grading of MCU (528MHz for Industrial, 600MHz for Commercial)
* Changed SEMC clock to be within maximum speed for SDRAM (now 148.5MHz, was 198MHz)
* 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).
* Converted the AzureRTOS examples to use the BOARD_NETWORK_USE_100M_ENET_PORT (same as all
  other networking examples) instead of using the old EXAMPLE_USE_1G_ENET_PORT


This has been added:
* HDMI support to most GUI examples. The default is the 4.3" Parallel RGB
  display as it is a part of the iMXRT1166 Developer's Kit. The switch to HDMI
  can be made per project in display_support.h/elcdif_support.h/lcdifv2_support.h.
* I2C probe example
* EDID reader example

Important things to note:
* Read section "8 - Known Issues" in docs/MCUXpresso SDK Release Notes for MIMXRT1160-EVK.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
* GUI applications using Parallel RGB display and the LCDIFv2 interface require
  a carrier board supporting the 24 bit mapping (like the uCOM Carrier Board rev B and later).
  If you don't have that then switch the interface to eLCDIF in the project's
  display_support.h/elcdif_support.h/lcdifv2_support.h file.

Connectors:
* J29 (micro USB) is the default UART for the CM7 core and unless specified otherwise it is setup for 115200 8/N/1
* J30 (micro USB) is the default UART for the CM4 core and unless specified otherwise it is setup for 115200 8/N/1
* For 1Gbit Ethernet examples, use connector J25 on uCOM Carrier Board
* For 100Mbit Ethernet examples, use ethernet adapter connected between Connector "D" on
  uCOM Carrier Board and J37 on the adapter. These four connections are also needed:
    1) uCOM Carrier Board, JP38:1 -> adapter JP37:1
    2) uCOM Carrier Board, JP38:2 -> adapter JP37:2
    3) uCOM Carrier Board, JP27:1 -> adapter JP39:2
    4) uCOM Carrier Board, JP27:2 -> adapter JP39:1
* The two CSI examples can use either an OV5640 camera in connector J23 or a camera in connector J24
* The EIQ examples that use a camera expects the camera in connector J24 (J23 might work for some
  of the examples but runs much slower)
* Some GUI examples are configured for the RK055AHD091 display which should be in connector "C" on
  the uCOM Carrier Board. Ignore the readme text about connecting extra 5V power.
* The default for GUI examples is to use an HDMI adapter in connector "C" on
  the uCOM Carrier Board. Ignore the readme text about connecting extra 5V power.


All CAN-related examples use the FLEXCAN3 bus (even hardcoded
in the CANopen libraries).

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
- MIMXRT1160-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

Multi-core considerations
=========================
There are example applications prepared for both CM4 and CM7 cores of the RT116x target platform. 
The debugger is typically able to load and run the code on any of the cores, but only one core 
is default (CM7) and will run automatically after reset. This means that the flash-based targets 
(and both Debug and Release targets on MCUXpresso IDE) are only usable on the default core.

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
