> For the complete documentation index, see [llms.txt](https://nxp.gitbook.io/navqplus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nxp.gitbook.io/navqplus/hardware/hardware-interfaces/usb-c.md). # USB-C ## Port configuration NavQPlus includes two USB 3.0 Type C ports that are capable of acting as PD devices. PD modes, Controller, Peripheral mode, USB Gadget Mode are configured at compile time, and may change depending on what image you are using. {% hint style="danger" %} It is VERY IMPORTANT to be aware of **PD mode** (power delivery mode) settings on your board. This is an embedded board with complete manual control. \ It is POSSIBLE to configure the settings and cables such that the powerfrom the POWER IN connector flows through to the USB C port without full negotiation. This is particularly problematic if you be using a USB C to USB type A cable/connector, USB A ports is only specified to 5V. USB C are protected to 20V \ PERMANENT DAMAGE TO THE CONNETED DEVICE could occur! {% endhint %} The default image as of the date shown here configures the USB ports as follows. (Last updated 10/13/2023 ) ## USB 1: USB-C port closest to the edge of the board. This port is used for *connecting* devices, such as USB-C hubs, cameras, sensors, and more. ## USB 2: USB-C port closest to the middle of the board. This port is used for *powering* the board, as seen in the Power page in the User Guide. This port accepts USB-C PD, and also allows data transfer. USB Gadget Ethernet is supported over this port with the interface `usb0`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://nxp.gitbook.io/navqplus/hardware/hardware-interfaces/usb-c.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.