> 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/navqplus-user-guide/quickstart/ethernet-over-usbc-gadget-mode.md).

# Wired Network connections

The NavQPlus has the ability to connect via ethernet in several different ways. 

{% hint style="danger" %}
NEVER use USB-C to USB-A cables without a hub or blocking device. In this embedded platform software has complete control over USB-PD and it is POSSIBLE to provide power >5V on the USB-C connector without handshaking. USB-A is only 5V tolerant and this can damage certain devices.
{% endhint %}

* Through the IX Industrial® Type A port. The provided IX to RJ45 adapter cable will allow connecting to RJ45  \*Preferred
* Using the USB-C port with "gadget bode" Ethernet over USB
* Through the 100 Base T1 automotive ethernet. A media converter such as RDDRONE-T1ADAPT, or a switch such as MR-T1ETH8 would allow connection to a typical RJ45 100Base-T port.
* Using a USB-C Ethernet adapter dongle

<figure><img src="/files/9s6jk4XAfZj7oegIdB2g" alt=""><figcaption></figcaption></figure>

### USB to Ethernet Adapter

Here is an example of how the NavQ+ can also be connected through the USB-C port. For this method, a separate adaptor is required to convert the USB-C to RJ45.&#x20;

<figure><img src="/files/yHBnjSPEZz609ORJaXIy" alt=""><figcaption><p>Example of the USB-C ethernet connection.</p></figcaption></figure>

To be able to connect to the board through SSH it must be connected to the same network. This is possible by using a router and connecting your network cable to it then the NavQ+ and your PC to it. With this connection SSH can be established between your PC and the NavQ+. Below is an example of how the router could be connected.

<figure><img src="/files/gU7sJeXiUcA7sT2fNFrS" alt=""><figcaption><p>The PC and the NavQ+ connected to the same router.</p></figcaption></figure>

{% hint style="warning" %}
Not all USB to Ethernet adapters are supported . In some cases you may also find that the board reboots when powering up with an unsupported adapter. While still sub-optimal, you can try circumventing the reboot by unplugging the ethernet and letting the board boot first. Once it is booted up you can retry attaching the adapter and connecting ethernet.
{% endhint %}

After everything is connected correctly a connection can be made through SSH. This is done with the following code, on your PC terminal:

```
ssh user@imx8mpnavq.local
```

or you can input the IP address of your NavQ+:

```
ssh user@<NavQ+'s IP address>
```

You will be asked to input the password.&#x20;

The default password is ***user***.

{% hint style="info" %}
You can also find your IP address using the command: *ifconfig*&#x20;
{% endhint %}

At this point you may want to consider following steps to connect the NavQPlus WiFi to a local network.&#x20;


---

# 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/navqplus-user-guide/quickstart/ethernet-over-usbc-gadget-mode.md?ask=<question>&goal=<endgoal>
```

`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.