# Access Debug-logs

## Requirements

The following tools are required to get access to the debug logs:

* Linux based host system with minicom installed
  * use `sudo apt-get install minicom` to install
* USB to UART adapter
* UART cable to connect to the carrierboard

## Hardware connection

At first you have to connect your UART cable to the Jetson the following way

<table><thead><tr><th width="155.33333333333331">Signal Jetson</th><th width="195">Signal UART adapter</th><th>note</th></tr></thead><tbody><tr><td>VCC</td><td>VCC</td><td>its not recommended to connect this cable. The UART device (in this case the Jetson) should be powered externally </td></tr><tr><td>RX</td><td>TX</td><td></td></tr><tr><td>TX</td><td>RX</td><td></td></tr><tr><td>GRD</td><td>GRD</td><td></td></tr></tbody></table>

| Carrierboard                     | Connection                       |
| -------------------------------- | -------------------------------- |
| ![](/files/732BsXGaA1txT0oKWjmY) | ![](/files/UzqSvEXS0GdhPAYrtZdv) |

Now connect the cable to the USB to UART adapter und connect the USB to your Computer

## Software

{% hint style="info" %}
The following steps have to be done on your linux host system
{% endhint %}

### Install minicom

In case you do not have Minicom already installed use the following command to install it:&#x20;

{% code title="install minicom" overflow="wrap" lineNumbers="true" %}

```bash
sudo apt-get install minicom 
```

{% endcode %}

The following command makes sure that the USB to UART adapter is properly recognized by the linux system.&#x20;

### Check tty device

{% code title="check tty device" overflow="wrap" lineNumbers="true" %}

```bash
ls /dev | grep ttyUSB 
```

{% endcode %}

Please check your hardware connection to the USB to UART adapter, If the command does not print `ttyUSB0` back to the terminal.

### Open minicom

Now everything is set up get the debug logs, you just have to start minicom with the following parameters:&#x20;

{% code title="start minicom" overflow="wrap" lineNumbers="true" %}

```bash
sudo minicom -D /dev/ttyUSB0
```

{% endcode %}

Your terminal should now look like something like this

```log
Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys

```

### Start Jetson

Now connect your Jetson to the powersupply and start it properly. The minicom terminal should print a lot of messages during the boot of the Jetson system ending with a login window to the Linux system.

```log
Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyUSB0, 11:47:06

Press CTRL-A Z for help on special keys

��
[0000.025] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.034] I> MB1 (prd-version: 1.5.1.7-t194-41334769-98030a79)
[0000.039] I> Boot-mode: Coldboot
[0000.042] I> Chip revision : A02P
[0000.045] I> Bootrom patch version : 15 (correctly patched)
[0000.050] I> ATE fuse revision : 0x200
[0000.054] I> Ram repair fuse : 0x0
[0000.057] I> Ram Code : 0x1
[0000.059] I> rst_source : 0x0
[0000.062] I> rst_level : 0x0
[0000.065] I> Boot-device: QSPI
[0000.068] I> Qspi flash params source = brbct
[0000.072] I> Qspi using bpmp-dma
[0000.075] I> Qspi clock source : pllp
[0000.079] I> QSPI Flash Size = 64 MB
[0000.082] I> Qspi initialized successfully
[0000.086] W> No valid slot number is found in scratch register
[0000.092] W> Return default slot: _a
[0000.095] I> Active Boot chain : 0
[0000.098] I> Boot-device: QSPI
[0000.101] I> Qspi flash params source = brbct
[0000.107] W> MB1_PLATFORM_CONFIG: device prod data is empty in MB1 BCT.
[0000.114] I> Temperature = 23500
[0000.117] W> Skipping boost for clk: BPMP_CPU_NIC
[0000.122] W> Skipping boost for clk: BPMP_APB
[0000.126] W> Skipping boost for clk: AXI_CBB
[0000.130] W> Skipping boost for clk: AON_CPU_NIC
[0000.134] W> Skipping boost for clk: CAN1
[0000.138] W> Skipping boost for clk: CAN2
[0000.142] I> Boot-device: QSPI
[0000.145] I> Boot-device: QSPI
[0000.148] I> Qspi flash params source = mb1bct
[0000.152] I> Qspi using bpmp-dma
[0000.155] I> Qspi clock source : pllc_out0
[0000.158] I> Qspi reinitialized
[0000.161] I> Qspi flash params source = mb1bct
[0000.167] I> Qspi flash params source = mb1bct
[0000.172] I> ECC region[0]: Start:0x80000000, End:0x780000000
[0000.177] I> ECC region[1]: Start:0x0, End:0x0
...
```


---

# Agent Instructions: 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:

```
GET https://auvidea.gitbook.io/debug-log/guide/access-debug-logs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.