> For the complete documentation index, see [llms.txt](https://docs.arkelectron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arkelectron.com/products/flight-controller/jetson-pabs/ark-jetson-pab-carrier/developer/micro-usb-console.md).

# Micro USB Console

Plugging a Micro USB cable into the Jetson carrier disconnects the flight controller from the Jetson's USB and puts the Jetson in USB device mode. It enumerates as one USB composite device (`0955:7020`) providing four functions:

| Function                   | Host sees                                             |
| -------------------------- | ----------------------------------------------------- |
| RNDIS + CDC-NCM networking | Two USB Ethernet interfaces; Jetson at `192.168.55.1` |
| CDC-ACM serial             | Virtual COM port with a login console                 |
| Mass storage               | `L4T-README` drive                                    |

{% hint style="warning" %}
After disconnecting the Micro USB cable, reboot the Jetson to reconnect the flight controller USB.
{% endhint %}

## Serial Console

Use the `by-id` path — the `ttyACM` number changes between sessions:

```bash
ls -l /dev/serial/by-id/
usb-NVIDIA_Linux_for_Tegra_1613223640377-if02 -> ../../ttyACM1
```

```bash
screen /dev/serial/by-id/usb-NVIDIA_Linux_for_Tegra_*-if02 115200
```

Log in with your username and password (default `jetson` / `jetson`). Your user must be in the `dialout` group.

On macOS the port is `/dev/tty.usbmodem*`; on Windows it is a `COMx` port in Device Manager.

{% hint style="info" %}
This is not a boot console. The gadget (`nv-l4t-usb-device-mode.service`) and login prompt (`serial-getty@ttyGS0.service`) start under `multi-user.target`, so there is no UEFI, bootloader, or early kernel output — and no port at all if boot hangs before that point. For boot-level debugging use the physical UART console.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arkelectron.com/products/flight-controller/jetson-pabs/ark-jetson-pab-carrier/developer/micro-usb-console.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.