Related Manuals for Avnet NXP RT1176
Summary of Contents for Avnet NXP RT1176
- Page 1 GHz Real-Time NXP RT1176 SBC board MaaXBoard RT Hardware User Guide v1.0 – Sept 21, 2021 Page 1...
-
Page 2: Document Control
1 Document Control Document Version: v1.0 Document Date: 09/21/2021 Document Author: Peter Fenn Document Classification: Public Document Distribution: Public 2 Version History Version Date Comment 09/21/2021 Release version (for Rev.3 production PCB) Page 2... -
Page 3: Table Of Contents
MIPI DSI 7-inch Capacitive Touch LCD Display (Optional) ......11 MIPI CSI 5 MP Camera (Optional) ............... 11 Other SBCs and SOMs from Avnet Boards (Optional) ......... 12 Hardware Setup for Application Development ..........13 MaaXBoard RT Architecture & Features ............14 Features ....................... - Page 4 6.7.2 BT/BLE UART Interface ....................30 6.7.3 BT PCM Audio Interface ....................30 6.7.4 Wi-Fi / BT antenna ......................30 Peripheral Devices and Interfaces ............... 31 6.8.1 USB 2.0 Host Interface ....................31 6.8.2 USB 2.0 Device Interface....................31 6.8.3 GbE Ethernet (with TSN time-sync.) ................
- Page 5 13 Known Issues ..................... 60 14 Cautionary Notes ....................60 15 Technical Support ....................61 15.1 NXP-hosted Technical Support Resources ..........61 15.2 Avnet-hosted Technical Support Resources ..........61 16 Sales Contact Info ....................61 17 Disclaimer ......................62 18 Safety Warnings ....................62...
- Page 6 Figure 2 – NXP MCU-LINK-PRO Debug/Programmer Probe ........10 Figure 3 – Typical hardware setup for software development ........13 Figure 4 – NXP RT1176 Processor Block Diagram ..........15 Figure 5 – MaaXBoard RT Block Diagram ..............16 Figure 6 – LEDs and Button Switches ..............18 Figure 7 –...
-
Page 7: Hardware Checklist
3 Hardware Checklist Hardware items recommended for application development are the following Item Description Computer (Windows / Linux / Mac) with installed development tools (see below) Avnet MaaXBoard RT board http://avnet.me/MaaXBoard-RT NXP MCU-LINK Debugger/Programmer Probe (plus USB type-A to MicroUSB cable) -
Page 8: Introduction
5 Introduction • 1GHz SBC with advanced real-time capabilities – Use as a processing sub-assembly in OEM products or as a versatile development board – Raspberry Pi-4B form-factor facilitates easier enclosure and cabling integration – 40-pin HAT compatible expansion header (ie. access Pi HAT ecosystem add-on boards) –... -
Page 9: Maaxboard Rt Info
MaaXBoard RT Schematic and BOM (available under NDA) NXP IMXRT1170RM MCU-LINK Debugger/Programmer Probe (Required Option) NXP MCU-LINK Debugger Probe configured for CMSIS-DAP protocol, is supported by multiple IDEs and is available for purchase separately from Avnet Standard MCU-Link features: High speed USB, SWD debug, ... -
Page 10: Mcu-Link-Pro Debugger/Programmer Probe (Optional)
MCU-LINK-PRO Debugger/Programmer Probe (Optional) The new NXP MCU-LINK-PRO Debugger Probe provides an alternative debugger probe option with several enhancements (available Sept 2021) Features in common with MCU-Link: High speed USB SWD debug SWO profiling VCOM (USB to UART bridge) Advanced MCU-Link-Pro features: ... -
Page 11: Mipi Dsi 7-Inch Capacitive Touch Lcd Display (Optional)
Compatible with all MaaXBoard SBC platforms. Connects to host via 2-lane MIPI-DSI interface Capacitive multi-touch display overlay Custom displays available via Avnet Embedded Part# (and link): AES-ACC-MAAX-DISP1 (MSRP = $78.95) MIPI CSI 5 MP Camera (Optional) ... -
Page 12: Other Sbcs And Soms From Avnet Boards (Optional)
Other SBCs and SOMs from Avnet Boards (Optional) The Avnet Products & Emerging Technology engineering team work in close partnership with key suppliers to develop advanced enablement solutions • Kits / Boards / SOMs / Modules • Reference Designs •... -
Page 13: Hardware Setup For Application Development
Hardware Setup for Application Development Figure 3 – Typical hardware setup for software development Page 13... -
Page 14: Maaxboard Rt Architecture & Features
6 MaaXBoard RT Architecture & Features Features Based on NXP i.MX RT1176 crossover dual-core MCU with advanced real-time capabilities Cortex-M7 @1GHz – Class-leading Cortex-M7 benchmarks (2434 DMIPS, 5070 Coremark) – Super-fast interrupts (12ns latency), up to 220 interrupts sources, 4 interrupt levels –... -
Page 15: Block Diagram - Nxp Rt1176 Processor
Block Diagram – NXP RT1176 Processor Figure 4 – NXP RT1176 Processor Block Diagram Page 15... -
Page 16: Block Diagram - Maaxboard Rt (Rev.3 Pcb)
Block Diagram – MaaXBoard RT (Rev.3 PCB) Figure 5 – MaaXBoard RT Block Diagram Page 16... -
Page 17: Location Of Components On Maaxboard Rt
Location of Components on MaaXBoard RT Component Description Component Description NXP RT1176DVMAA processor 1G Ethernet PHY Spansion HyperFlash memory 1G Ethernet MagJack RJ45 connector ISSI SDRAM memory PDM digital microphones (4) Boot Mode Selection Jumper (J19) Stereo audio output jack Dual-band Wi-Fi/BT combo module SWD / JTAG debug mini 10-pin header U.FL external antenna connector... -
Page 18: Jumpers, Leds, And Switches
Jumpers, LEDs, and Switches 6.5.1 Boot Mode Configuration Jumper (J19) Link M1 M0 Setting Pins State Description None Boot from Fuses Internal Boot / IDE-based Development Serial Downloader (using USB or UART) 6.5.2 Button Switches Two pushbuttons are located at board edge, between MIPI-DSI connector and 40-pin header Button Ref. -
Page 19: Memory Resources
Memory Resources The NXP RT1176 device is extremely flexible in what memory is utilized for application storage, application execution and data storage. Note: Significant differences in performance can be expected, when comparing code execution in the different types of memory. -
Page 20: Memory Maps For Application Development
6.6.1 Memory Maps for Application Development Tabled below are typical memory map settings for applications using RAM and SDRAM a) RAM-based Cortex-M7 low-latency/high-performance real-time application Memory Mem. Mem. Mem. Hex Start Hex Mem. Type Size Width Speed Address Size SRAM_ITC_cm7 256 KB 32 bit 0x40000... -
Page 21: Hyperflash Memory
2) Import an example project from the SDK 2.10.1 RT1170-SDK package (e.g., Hello World) 3) In the project’s XIP folder, delete evkmimxrt1170_flexspi_nor_config.c and replace this with the Avnet version file (of the same name), which specifies the HyperFlash parameters instead of the QSPI flash configuration parameters used in NXP’s SDK examples. - Page 22 Page 22...
-
Page 23: Hyperflash Programming Using Nxp Mcubootutility Application
6.6.4 HyperFlash Programming using NXP MCUBootUtility Application Besides normal programming via the debugger probe and the SWD interface, the hyperflash can also be programmed via the USB-C interface or a UART interface, using “Serial Download” boot mode. To select this mode, the J19 bootmode jumper needs to be moved to the “Serial Download” position. NXP-MCUBootUtility PC application is a user-friendly GUI based tool for flash erase and programming, using this mode, either via the board’s USB-C connector, or the debug UART 3-pin header. -
Page 24: Figure 8 - Nxp Mcu Boot Utility Settings For Erase Of Flashloader
Figure 8 – NXP MCU Boot Utility Settings for Erase of Flashloader Page 24... -
Page 25: Hyperflash Programming Using Mcuxpresso Secure Provisioning Tools
Figure 9 – Mass Erase / Reload of Default Flash Driver 6.6.5 HyperFlash Programming using MCUXpresso Secure Provisioning Tools Flash programming is also supported via the NXP MCUXpresso Secure Provisioning Tools standalone application. This is not however a suitable tool to use during program development. Page 25... -
Page 26: On-Chip Tcm Ram And Ocram
When building an application that uses SDRAM, it is of critical importance that the project’s dcd.c file be replaced by the version of this file that is supplied by Avnet. This is necessary as MaaXBoard RT has x16 width SDRAM interface, while the NXP RT1170-EVK board has a x32 width parallel data interface) Download the Avnet version dcd.c file from:... -
Page 27: Wireless Connectivity
MaaXBoard RT uses a Murata Type-1ZM Wi-Fi 5 and Bluetooth 5 combo module, which is based on the NXP 88W8987 device. Both 2.4 GHz and 5 GHz Wi-Fi operation is supported Interfaces between the NXP 88W8987 based module and the NXP RT1176 host processor include: ... -
Page 28: Table 5 - Wi-Fi/Bt Module Interface (Mapped To Sdk/Evk Signal Names)
1ZM Module RT Peripheral NXP RT1170-EVK NXP RT1170-EVK RT Peripheral Pin Name Resource SDK Signal Name M.2 Signal Name Resource and Pin# (on MaaXBoard) (on EVK) BOARD_InitUSDHCPins USDHC1 SD_CLK SD1_CLK WIFI_SD_CLK SDIO_CLK GPIO_SD_B1_01 [D15] [D15] SD1_CMD SD_CMD WIFI_SD_CMD SDIO_CMD GPIO_SD_B1_00 [B16] [B16] SD_DAT0... -
Page 29: Figure 11 - Schematic Detail Of Wi-Fi/Bt Implementation
Figure 11 – Schematic Detail of Wi-Fi/BT Implementation Page 29... -
Page 30: Wi-Fi Sdio Interface
6.7.1 Wi-Fi SDIO Interface USDHC1 interface is configured for 1.8V operation and is clocked at 200 MHz (This is the same SDIO interface as used on the RT1170-EVK) 6.7.2 BT/BLE UART Interface LPUART10 including hardware flow is routed from the RT1176 via a 3.3V to 1.8V level-shifter, to the 1ZM module’s Bluetooth UART interface. -
Page 31: Peripheral Devices And Interfaces
The antenna shipped with MaaXBoard RT (as used for regulatory certifications) is Molex p/n: 1461870050 Peripheral Devices and Interfaces 6.8.1 USB 2.0 Host Interface USB1 controller is assigned to the type-A connector USB Host interface 6.8.2 USB 2.0 Device Interface USB0 controller is assigned to the type-C connector USB Device interface 6.8.3 GbE Ethernet (with TSN time-sync.) -
Page 32: Mipi-Csi Camera
6.8.7 MIPI-CSI Camera 2-lane, the pinout is same as used on Raspberry-Pi boards. This optional 5 MP MIPI-CSI camera is based on same OV5640 image sensor as used with the NXP RT1170-EVK board. 6.8.8 Digital Microphones Four PDM digital microphones (ST p/n: MP34DT05-A) are located adjacent to the four mounting holes on MaaXBoard RT. -
Page 33: J1: Pi-Hat Compatible 40-Pin Header
Height of stacked boards is minimized as RT1176 does not require heatsink 6.8.13 MikroE Click Boards • Over 1000+ Click Boards available (orderable from Avnet) • Inexpensive Pi HAT adapters available (for 2 Click boards) • Parametric search tool on MikroE website •... -
Page 34: J15: Custom 18-Pin Expansion Header
6.8.14 J15: Custom 18-pin expansion header MaaXBoard RT MaaXBoard RT Even MaaXBoard RT MaaXBoard RT Port Name Signal Name Pin # Pin # Signal Name Port Name VDD_3V3 VDD_3V3 VDD_3V3 VDD_3V3 GPIO_LPSR_00 CAN3_TX GPIO_AD_01 CAN3_RX 1588_1G_EVENT1_OUT GPIO_LPSR_01 GPIO_AD_07 1588_1G_EVENT1_IN GPIO_AD_00 1588_EVENT1_OUT GPIO_EMC_B2_12 1588_EVENT1_IN... -
Page 35: J17: Uart1 Usb Serial Port 3-Pin Header
6.8.15 J17: UART1 USB Serial Port 3-pin header Label on Label on MCU-LINK MaaXBoard RT TX to Target RX to Target Table 9 – UART1 console debug VCOM 3-pin header (J17) Note: The TXD and RXD wire-order is crossed-over between MCU-LINK debugger and MaaXBoard RT ... -
Page 36: Power Input, Protection And Regulation
Power Input, Protection and Regulation 6.9.1 USB type-C Connector The USB type-C connector is used for 5V power and provides a USB-Device interface 6.9.2 ESD Protection All USB connectors have high-speed ESD protection on their power rails and data lines 6.9.3 Power Regulation A 5V to 3.3V dc/dc buck convertor regulates the Vcc rail voltage (rated @ 3A max) -
Page 37: Development Software Installation
Build MCUXpresso SDK_2.10.1 to download… To install, simply drag & drop the SDK zip file into the Installed SDKs panel of MCUXpresso IDE SDK_2.10.0_MIMXRT1170-EVK.zip Four files defined by Avnet also need to be downloaded from the following sharepoint page: http://avnet.me/MaaXBoard-RT-SDK MaaXBoard_S26KS256.cfx ... -
Page 38: Development Environment
8 Development Environment Follow the instructions from NXP to install the MCUXpresso IDE and SDK, the documentation to assist with setting up the development environment are provided in section 0. Importing a Project zip File Once the MCUXpresso IDE and SDK are installed, import the project zip file into a new workspace by clicking on the “Import project(s) from file system link”... -
Page 39: Building Projects
Building projects To build the selected project, simply press the Build button from the Quickstart panel. Setting up the debugger Before attempting to debug or flash the board the MaaXBoard_S26KS256.cfx file has to be added to the .mcuxpressoide_packages_support folder. To do this, locate the MaaXBoard_S26KS256.cfx file in the project directory xip folder. -
Page 40: Downloading And Running The Application
Downloading and running the application At this point, the application is ready for debugging. Press the Debug button from the Quickstart Panel Once the application is downloaded, press the resume button to run the application. Once the application is downloaded and running, press the terminate button to exit debugging. Power-cycling the board or pressing the reset button will restart the application since it is now located in flash. -
Page 41: Porting Nxp Rt1170-Evk Sdk Examples To Maaxboard Rt
I2C5 to I2C6. Remap the DSI_TS_nINT interrupt pin. MIPI Display Different display and MIPI controller, use Avnet-supplied driver (avt-ili9881c.c) controller driver plus related modifications. MIPI-DSI signals have same mapping as on EVK. DSI_EN and DSI_BL_PWM control signals require remapping. -
Page 42: Building And Running Sdk Rt1170-Evk Examples
4) Accommodating the subset of hardware differences between MaaXBoard RT and the RT1170-EVK, a broad range of RT1170-EVK SDK examples have already been adapted and tested on MaaXBoard RT. This material will be made available in due course via public Avnet Github pages Page 42... -
Page 43: Maaxboard Rt Example Applications
10 MaaXBoard RT Example Applications 10.1 Custom System-level Reference Designs Application Name Board functions exercised Repo / Location Ref.Design #1: MIPI DSI display, touchscreen, USB host, Wi-Fi scan and Not yet posted to Out of Box Demo connect, 100M & 1G Ethernet, PDM microphones, audio public repo output, RGB LED, CLI interface, HyperFlash, User button, CSI camera interface, I2C interface. -
Page 44: Customizing The Oob Test Suite (Ref. Design #1)
11 Customizing the OOB Test Suite (Ref. Design #1) 11.1 Overview of MaaXBoard-RT Reference Design #1 This reference design is the “out-of-box” application that is factory pre-programmed into the HyperFlash memory of new MaaXBoard RT boards. It provides a suite of board test functions that can be exercised using two different interfaces: ... - Page 45 The project source files are available for users to download, edit and repurpose for accelerated development of customized user applications (Avnet’s MaaXBoard RT “Factory Test” application is an example of how this codebase can be rapidly repurposed, in that case to interface with an automated C# test application running on a Windows computer) The Graphical UI screens are designed using NXP's free GUI Guider tool.
-
Page 46: Console Mode (Cli / Command-Line Interface)
--------- UTILITY -------------------- stats : RTOS Statistics : Clear the terminal q/ctrl+c : Abort the command ? / h : Menu Help ========= Avnet GUI Demo v1.0 [2021-06-25] Figure 14 – Default list of supported CLI Menu commands Page 46... -
Page 47: Gui Mode (Graphical Ui)
11.3 GUI mode (Graphical UI) To run in GUI mode, the optional 7inch MIPI display (720x1280) from Avnet is required. The Menu can be navigated using the touchscreen or mouse (attach via the USB type-A host connector). Depending on the required orientation, the user may want to rotate the screen by 180 degree. -
Page 48: Project Structure For Reference Design #1
11.4 Project Structure for Reference Design #1 The project contains several folders however, only a few are of interest for the purpose of this document. The folders of interest are the following: generated/ GUI Guider generated source files sources/ application source files ... -
Page 49: Figure 16 - Project Folders
Figure 16 – Project folders The main function int main(void) is located under source/littlevgl_guider.c and contains the initialization routines as well as the logic for creating the required FreeRTOS tasks. There are a total 10 FreeRTOS tasks running. lvgl_task Task handling all GUI object events and navigation ... -
Page 50: Adding A New Cli Command
USB_HostTask USB host task for enumerating HID devices (keyboard and mouse) USB_HostApplicationMouseTask Reads HID mouse data USB_HostApplicationKeyboardTask Reads HID keyboard data USB_logTask Responsible for processing the USB keyboard and mouse data and outputs to the serial port. -
Page 51: Customizing The Wi-Fi Webserver (Ref. Design #2)
12 Customizing the Wi-Fi Webserver (Ref. Design #2) 12.1 Overview of the MaaXBoard-RT Reference Design #2 FreeRTOS based dual-core application supports M7 based webserver and Wi-Fi network connectivity M4 based I2C sensor monitoring & output control Remote, headless operation UI access to board via any internet browser Websocket streaming of 6-axis IMU sensor data Network connection via 802.11ac Wi-Fi... -
Page 52: Modes Of Operation
This application utilizes the M7 and the M4 cores to demonstrate a headless webserver on the i.MXRT1170 MCU. Main features of this design include the following: Utilizing the HyperFlash for non-volatile configuration storage Wi-Fi softAP or Wi-Fi client ... -
Page 53: Soft Ap Mode
12.2.2 Soft AP mode MaaXBoard RT will run in soft AP mode if SSID and password have not been stored in the HyperFlash configuration partition. Alternatively, the user can pre-configure the board’s Wi-Fi network connection, by hard-coding the default SSID and password in webcongig.h #define WIFI_SSID "maaxboard_access_point"... -
Page 54: Project Structure For Reference Design #2
12.3 Project Structure for Reference Design #2 This reference design application is partitioned into two projects, one for each core, with each project running a set of FreeRTOS tasks. The M7 core project (MASTER) runs FreeRTOS with memory scheme 3 and runs 3 tasks. ... -
Page 55: M7 (Master) Wi-Fi Webserver Project
12.3.1 M7 (MASTER) Wi-Fi Webserver project This contains several folders, but only the following are of interest for purpose of this document. src/ web source files (.css .js .html) source/ application source files board/ board.c/h board specific definitions clock_config.c/h ... -
Page 56: Installing The Click Boards
12.4 Installing the Click Boards The LightRanger Click sensor board must installed in slot #1 on the click shield, and the IMU Click sensor board must be installed in slot #2. It is not possible to interchange the board locations due to physical pin routing. -
Page 57: Hyperflash As Runtime Storage
The log shown below is a sample output of the maaxboard_webserver_MASTER demo as displayed in the terminal window: Starting MaaXBoard Webserver DEMO [i] Trying to load data from mflash. [i] Saved SSID: ssid, Password: password [i] Initializing WiFi connection...d MAC Address: XX:XX:XX:XX:XX:XX [net] Initialized TCP/IP networking stack WLAN initialized WLAN FW Version: w8987o-V0, RF878X, FP91, 16.91.10.p200, WPA2_CVE_FIX 1,... -
Page 58: User Customization
12.7 User Customization 12.7.1 Frontend (Webserver UI) All front-end web resources can be found in src/wifi_common/webconfig/webui The LWIP stack provides a PERL script mkfs.pl which is used to convert entire web frontend sources into a single .c file. The generated .c file can then be added to a project and compiled. The mkfs.pl script is located here, src/wifi_common/webconfig/webui/mkfs.pl The mkfs.pl script requires only the folder location of the web resources as a parameter. -
Page 59: Webserver Access Via Smartphone
Example of a callback function: static int CGI_Example(HTTPSRV_CGI_REQ_STRUCT *param) char[] data = "OK"; // dummy text data HTTPSRV_CGI_RES_STRUCT response = {0}; response.ses_handle = param->ses_handle; response.status_code = HTTPSRV_CODE_OK; response.content_type = HTTPSRV_CONTENT_TYPE_PLAIN; response.data = data; response.data_length = strlen(data); response.content_length = response.data_length; HTTPSRV_cgi_write(&response); return (response.length);... -
Page 60: Known Issues
It is the user’s responsibility to be absolutely certain of their requirements before OTP programming and to not program the fuses by accident. Note that Avnet accepts no liability and will not replace boards that have been: ... -
Page 61: Technical Support
15.2 Avnet-hosted Technical Support Resources Avnet documents & reference designs will be available for download from MaaXBoard RT product page: http://avnet.me/MaaXBoard RT Avnet instructional tutorial blogs will also be linked to from: http://avnet.me/MaaXBoard RT... -
Page 62: Disclaimer
MaaXBoard RT is engineered for use as a development board (to facilitate product evaluation and system- level prototyping) as well as for use as a sub-assembly in custom OEM end-products. Avnet assumes no liability for modifications that a user chooses to make to MaaXBoard RT. 18 Safety Warnings... - Page 63 Page 63...
- Page 64 FCC Warning This device complies with part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any inte rference received, including interference that may cause undesired operation. Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
- Page 65 ISED Statement English: This device complies with Industry Canada license‐exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause interference, and (2) This d evice must accept any interference, including interference that may cause undesired operation of the device. The digital apparatus complies with Canadian CAN ICES‐3 (B)/NMB‐3(B).
Need help?
Do you have a question about the NXP RT1176 and is the answer not in the manual?
Questions and answers