# Power Up your RB

This section will demonstrate you the board bring up activity.

{% tabs %}
{% tab title="Windows Host" %}
Connect the USB to micro-USB cable to a windows PC and ruggedBOARD-A5D2x respectively.

Note: Once the cable is connected, you will be prompted with a USB connected sound. But at this point you will not see any mass storage symbol in task-bar/File Manager.

Next goto start menu and type:

`device manager`

Launch device manager. Device manger shows all the device and interfaces on a particular PC.

Look for COM port as shown in the image below. Mostly you should look for *`Port (COM & LPT)`*. Your device will be displayed as *`USB Serial Port (COMx)`*. Here x means the COM port number. In my case its *COM8*

![Device Manager](/files/-Lc6Wb3AooZlnwHz7eDi)

Now open `Putty.exe.` Click on Serial and replace the COM port with your COM port shown from device manager and click *"Open"*.

![](/files/-Lc6XtHS4_caocGkYNnv)

{% endtab %}

{% tab title="Linux Host" %}
Connect the micro USB cable to PC and the board. Check if the light in the board glows up. If the LED is glowing in the board then proceed to test the serial Console on Linux Host.

To confirm USB device is detected, enter the following command

`dmesg`

Look for  *`/dev/ttyUSBx`* where `x`means the connected port number.\
Example: If the device is connected in USB0, you will get message as `/dev/ttyUSB0`

**Install minicom Serial Monitor on your host PC:**

`Ubuntu@pc:~$ sudo apt-get install minicom`

**Setting Serial Console (Minicom):**

`Ubuntu@pc:~$ sudo minicom –s`

Select the option “serial port setup” from menu on terminal and press 'Enter

![](/files/-Lc0tDeTgoD3twegfiSs)

For ex: Serial device - /dev/ttyUSB0, first press ‘A’ the cursor blinks at the particular line then change the device name to /dev/ttyUSB0 and press ‘ENTER’

![](/files/-Lc0tPeg9kPGASqXyVp9)

Note: Serial device name will vary based on your serial device. `dev/ttyS0,` if you are suing Serial cable and `/dev/ttyUSB0,` if you are using USB to Serial converter.

After making all changes like baud rate "115200", hardware flow control "NO" by pressing the keyword ‘F’ etc. that are required press ‘ENTER’ to come out from the screen, 

Simply follow the further screens from the menu list and select **“Save setup as default”** by Press Enter key and Exit from the minicom setup process. It will take into ‘minicom’ the serial terminal.

Finally, you will get Board Console on the terminal after board boot-up ...what Next?

Note: In this stage if the board does not show the boot-logs/Board terminal, then just restart the board by switching power "OFF" and "ON".

Now will have two terminals:

* PC - Terminal.\
  PC terminal will have the following annotation:

  `gopal@phytec:~$`                               
* Board Terminal.

  PC terminal will have the following annotation:`root@ruggedBOARD-A5D2x:~#`                     

**Congratulations!!! Now you are ready to play around with ruggedBOARD-A5D2x SBC.**

![Terminal windows of Board and HOST PC](/files/-LeQbqc8_dEb8he0nzTJ)

Terminal on the left side of the image is Board's terminal and the one on the right side of the image is HOST PC's terminal. 

Upcoming Sections will show how to set up **SD card** to boot the board from SD card. Also **"tftp"** server and client communication to transfer files from host PC to 
{% endtab %}
{% endtabs %}


---

# 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://ruggedboard.gitbook.io/ruggedboard/quick-start-with-rb/powering-your-ruggedboard.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.