diff --git a/genpack/NXPSDK_overview.png b/genpack/NXPSDK_overview.png deleted file mode 100644 index e5f6566..0000000 Binary files a/genpack/NXPSDK_overview.png and /dev/null differ diff --git a/genpack/armkeil_white_h.png b/genpack/armkeil_white_h.png deleted file mode 100644 index 7818384..0000000 Binary files a/genpack/armkeil_white_h.png and /dev/null differ diff --git a/genpack/bc_s.png b/genpack/bc_s.png deleted file mode 100644 index 224b29a..0000000 Binary files a/genpack/bc_s.png and /dev/null differ diff --git a/genpack/bc_sd.png b/genpack/bc_sd.png deleted file mode 100644 index 31ca888..0000000 Binary files a/genpack/bc_sd.png and /dev/null differ diff --git a/genpack/bdwn.png b/genpack/bdwn.png deleted file mode 100644 index 940a0b9..0000000 Binary files a/genpack/bdwn.png and /dev/null differ diff --git a/genpack/closed.png b/genpack/closed.png deleted file mode 100644 index 98cc2c9..0000000 Binary files a/genpack/closed.png and /dev/null differ diff --git a/genpack/config_drivers.html b/genpack/config_drivers.html deleted file mode 100644 index dfdf5ba..0000000 --- a/genpack/config_drivers.html +++ /dev/null @@ -1,141 +0,0 @@ - - - -
- - - -For each CMSIS-Driver, the required configuration is explained in depth below:
Continue by adding user code.
-The NXP SDK is an NXP-specific software abstraction layer that provides interfaces to the device-specific peripherals. The steps to create a microcontroller application that uses MDK-Middleware and the NXP SDK are:
The instructions assume the following:
<selected_device>
, for example MIMXRT1052DVL6B
<PACK_root>
, typically C:\>Keil_v5\ARM\PACK\Keil\iMXRT105x_MWP\2.0.0
<project_dir>
The EVK board might be initially pre-loaded with an application which disables debug. In such case it is necessary to erase the Flash before using the board. Follow this procedure:
Most of the drivers require pin and clock configuration that is done with NXP's MCUXpresso Config Tools.
-The following steps are required to create the configuration (enter the values that are marked bold):
-Update the code and close MCUXpresso Config Tools when you are done.
-Continue by configuring CMSIS-Drivers.
-Go to Project - Options for Target... and do the following:
6314
in the disable Warnings box.\RTE\Device\<selected_device>\MIMXRT1052xxxxx_flexspi_nor.scf
in case you want to download the program to the target's external Flash memory 0x00008000
If you are using the Event Recorder, you need to place this software component in uninitialized memory. To do so, overwrite the default linker scripts in the project directory <project_dir>\RTE\Device\<selected_device>
with the updated linker scripts that are located in <PACK_root>\Scripts\Linker
.
To build your project:
Once you have successfully built the project, download it to Flash and start debugging:
-Directories | |
directory | Driver |
CMSIS-Driver for CAN Interface Setup
-The CMSIS-Driver for CAN Interface requires:
Valid pin settings for CAN peripheral on EVKB-IMXRT1050 evaluation board are listed in the table below:
-# | Peripheral | Signal | Route to | Direction | Software Input On | Speed |
---|---|---|---|---|---|---|
H14 | CAN2 | TX | GPIO_AD_B0_14 | Output | Enabled | low(50MHz) |
L10 | CAN2 | RX | GPIO_AD_B0_15 | Input | Enabled | low(50MHz) |
The rest of the settings can be at the default (reset) value.
-For other boards or custom hardware, refer to the hardware schematics to reflect correct setup values.
-In the MCUXpresso Config Tools, make sure that the following pin and clock settings are made (enter the values that are shown in italics):
-CMSIS-Driver for EMAC Interface Setup
-The CMSIS-Driver for EMAC Interface requires:
Valid pin settings for ENET peripheral on EVKB-IMXRT1050 evaluation board are listed in the table below:
-# | Peripheral | Signal | Route to | Direction | Software Input On | Pull/Keeper enable | Slew rate |
---|---|---|---|---|---|---|---|
A7 | ENET | MDC | GPIO_EMC_40 | Output | Disabled | Disabled | Fast |
C7 | ENET | MDIO | GPIO_EMC_41 | Input/Output | Disabled | Disabled | Fast |
B13 | ENET | REF_CLK | GPIO_B1_10 | Output | Enabled | Disabled | Fast |
E12 | ENET | RX_DATA,0 | GPIO_B1_04 | Input | Disabled | Disabled | Fast |
D12 | ENET | RX_DATA,1 | GPIO_B1_05 | Input | Disabled | Disabled | Fast |
C12 | ENET | RX_EN | GPIO_B1_06 | Input | Disabled | Disabled | Fast |
C13 | ENET | RX_ER | GPIO_B1_11 | Input | Disabled | Disabled | Fast |
B12 | ENET | TX_DATA,0 | GPIO_B1_07 | Output | Disabled | Disabled | Fast |
A12 | ENET | TX_DATA,1 | GPIO_B1_08 | Output | Disabled | Disabled | Fast |
A13 | ENET | TX_EN | GPIO_B1_09 | Output | Disabled | Disabled | Fast |
G13 | GPIO1 | goio_io,10 | GPIO_AD_B0_10 | Output | Disabled | Disabled | Fast |
F14 | GPIO1 | gpio_io, 9 | GPIO_AD_B0_09 | Not specified | Disabled | Enabled | Slow |
The rest of the settings can be at the default (reset) value.
-For other boards or custom hardware, refer to the hardware schematics to reflect correct setup values.
-This driver uses special signal identifiers in order to properly detect Media Interface mode (MII or RMII). These identifiers are required when using MII mode and must be assigned to signals as follows:
-Signal | Identifier |
---|---|
RX_DATA,2 | ENET_RXD2 |
RX_DATA,3 | ENET_RXD3 |
TX_DATA,2 | ENET_TXD2 |
TX_DATA,3 | ENET_TXD3 |
In the MCUXpresso Config Tools, make sure that the following pin and clock settings are made (enter the values that are shown in italics):
-CMSIS-Driver for USB Device Interface Setup
-The CMSIS-Driver for USB Device Interface enables necessary clocks and uses dedicated USB pins so no additional configuration in the MCUXpresso Config Tools is necessary.
-Note: If USB buffers and descriptors have to be located in specific memory then variables qh_buffer and s_UsbDeviceEhciDtd from usb_device_ehci.c module have to be positioned in that memory. The mentioned USB buffers and descriptors on this microcontroller must be located in the internal SRAM memory.
-CMSIS-Driver for USB Host Interface Setup
-The CMSIS-Driver for USB Host Interface enables necessary clocks and uses dedicated USB pins so no additional configuration in the MCUXpresso Config Tools is necessary.
-The CMSIS-Driver for USB Host Interface uses CMSIS-Driver for EHCI which is provided in the Keil::CMSIS-Driver pack.
-The procedure of configuring EHCI driver for usage:
Note: If USB Communication Area has to be located in specific memory then enable Relocate EHCI Communication Area by setting USBHn_EHCI_COM_AREA_RELOC define value to 1 and use name specified as value of USBHn_EHCI_COM_AREA_SECTION_NAME define in your linker script. The Communication Area on this microcontroller must be located in the internal SRAM memory.
-The USBH_EHCI_HW_iMXRT10xx.c file provides hardware-specific interface to EHCI driver.
-CMSIS-Driver for MCI Interface Setup
-The CMSIS-Driver for MCI Interface requires:
Valid pin settings for USDHC1 peripheral on EVKB-IMXRT1050 evaluation board are listed in the table below:
-# | Peripheral | Signal | Route to | Identifier | Direction | Pull Up/Down Config | Pull/Keeper select | Pull/Keeper enable | Drive strength | Slew rate |
---|---|---|---|---|---|---|---|---|---|---|
J2 | USDHC1 | DATA,3 | GPIO_SD_B0_05 | SD1_D3 | Input/Output | 47k Ohm Pull Up | Pull | Enabled | R0 | Fast |
H2 | USDHC1 | DATA,2 | GPIO_SD_B0_04 | SD1_D2 | Input/Output | 47k Ohm Pull Up | Pull | Enabled | R0 | Fast |
K1 | USDHC1 | DATA,1 | GPIO_SD_B0_03 | SD1_D1 | Input/Output | 47k Ohm Pull Up | Pull | Enabled | R0 | Fast |
J1 | USDHC1 | DATA,0 | GPIO_SD_B0_02 | SD1_D0 | Input/Output | 47k Ohm Pull Up | Pull | Enabled | R0 | Fast |
J4 | USDHC1 | CMD | GPIO_SD_B0_00 | SD1_CMD | Input/Output | 47k Ohm Pull Up | Pull | Enabled | R0 | Fast |
J3 | USDHC1 | CLK | GPIO_SD_B0_01 | SD1_CLK | Output | 100k Ohm Pull Down | Keeper | Disabled | R0 | Fast |
D13 | GPIO2 | goio_io,28 | GPIO_B1_12 | SD1_CD | Not specified | 100k Ohm Pull Down | Keeper | Enabled | R0/6 | Slow |
The rest of the settings can be at the default (reset) value.
-For other boards or custom hardware, refer to the hardware schematics to reflect correct setup values.
-This driver uses special signal identifiers in order to enable SD Card Detect and Write Protect pin functionality. These identifiers can be optionally used and must be assigned to signal connected to card detect or write protect pin on SD card socket. Each MCI driver instance uses its own identifiers which can be assigned to signals as follows:
-MCI instance | Peripheral | Identifier | Functionality |
---|---|---|---|
0 | USDHC1 | SD1_CD | Card Detect |
0 | USDHC1 | SD1_WP | Write Protect |
1 | USDHC2 | SD2_CD | Card Detect |
1 | USDHC2 | SD2_WP | Write Protect |
In the MCUXpresso Config Tools, make sure that the following pin and clock settings are made (enter the values that are shown in italics):
-In main.c
, edit the app_main
function to suit the needs of your application.
Continue by building and debugging the project or add software components for printf debugging.
-This manual explains how to create MDK-Middleware projects for NXP's i.MXRT105x series. NXP provides device family packs (DFP) and a comprehensive SDK that contain CMSIS-Drivers for I2C, SPI, and USART. This software pack adds CMSIS-Drivers for Ethernet MAC, GPIO, FLEXCAN, MCI, USB Host and USB Device for the above mentioned device series, based on the original NXP peripheral drivers (fsl) and USB middleware drivers.
-The diagram below is an overview of the complete software stack:
-The following software packs are required:
-Software pack | Description |
---|---|
ARM.CMSIS.6.0.0 (or higher) | Arm CMSIS |
ARM.CMSIS-Driver.2.9.0 (or higher) | Arm CMSIS Drivers for external devices |
NXP.MIMXRT1051_DFP.18.0.0 | Device family pack for NXP i.MXRT1051 |
NXP.MIMXRT1052_DFP.18.0.0 | Device family pack for NXP i.MXRT1052 |
For pin and clock configuration of the i.MXRT devices, the NXP MCUXpresso Config Tools are required. The corresponding user's guide can be downloaded from: MCUXpresso Config Tools User's Guide
-It is assumed that you are familiar with MDK. Refer to MDK - Getting Started for additional setup information.
-Please make sure that you have setup your board correctly. The section Important notes explains how to enable debugging by removing the pre-programmed image in Flash that disables debugging.
-This manual contains the chapters:
Directory or File | Description |
---|---|
.\CMSIS | CMSIS-Drivers for Ethernet MAC, FLEXCAN, MCI, USB Host and Device |
.\Documentation | This documentation |
.\Scripts | Updated linker scripts for using Event Recorder and debugger scripts |
.\SDK | NXP USB Middleware sources necessary for CMSIS USB Device Driver and extended GPIO headers |
.\Templates | Various source code templates |
Version | Description |
---|---|
V2.0.0 | Updated CMSIS Drivers to align with NXP.MIMXRT1052_DFP.18.0.0 pack -Updated documentation to reflect the latest state of MCUXpresso Config Tools -CMSIS-Driver:
Removed EVKB-IMXRT1050 board examples - |
V1.6.0 | Updated CMSIS Drivers and examples to align with NXP.MIMXRT1052_DFP.17.0.0 pack -Updated documentation to reflect the latest state of MCUXpresso Config Tools -CMSIS-Driver:
Examples:
|
V1.5.1 | Updated CMSIS Drivers and examples to align with NXP.MIMXRT1052_DFP.15.1.0 pack -Updated documentation to reflect the latest state of MCUXpresso Config Tools -CMSIS-Driver:
Examples:
|
V1.5.0 | Updated CMSIS Drivers and examples to align with NXP.MIMXRT1052_DFP.15.0.0 pack -Updated documentation to reflect the latest state of MCUXpresso Config Tools -CMSIS-Driver:
Examples:
|
V1.4.0 | Updated CMSIS Drivers and examples to align with NXP.MIMXRT1052_DFP.13.1.0 pack -Updated SDK package to version 2.10.0(2021-07-15) -PDSC file: Changed schemaVersion (1.7.2) -Examples:
|
V1.3.0 | Updated CMSIS Drivers and examples to align with NXP.MIMXRT1052_DFP.12.3.0 pack -Updated SDK package to version 2.9.1(2021-01-20) -PDSC file: Changed schemaVersion (1.7.1) -Examples:
|
V1.2.1 | Examples:
|
V1.2.0 | Updated CMSIS Drivers and examples to align with NXP.MIMXRT1052_DFP.12.1.0 pack -Updated SDK package to version 2.7.0(2019-12-19) -Examples:
|
V1.1.0 | Updated CMSIS Driver and examples to align with NXP.MIMXRT1052_DFP.12.0.0 -CMSIS-Driver:
SDK:
SDK_Patch:
Scripts:
Examples:
|
V1.0.0 | Initial release of i.MX RT MDK-Middleware examples and CMSIS-Drivers Pack. |