# BiBoard V1

### BiBoard V1 USB Driver to access the serial port

{% hint style="warning" %}
Some USB cables are only for charging and do not support data transfer. Using the original data cable in the kit is better for a successful upload.  
{% endhint %}

When you use a USB Type-C data cable to upload the firmware for the **mainboard.**

* In Windows, if there is **no** serial port in the port list of **Device Manager**:

<figure><img src="/files/OQ9sDgrC0Wgihg1niixC" alt=""><figcaption></figcaption></figure>

* In Mac, open the **Terminal** program under the **Applications**-**Utilities** folder and type the following commands. If no serial device name starting with "***tty.wchusbserial***" or "***cu.wchusbserial***" is found:

  <pre><code>cd /dev
  <strong>ls
  </strong></code></pre>

#### Please download and install the USB driver:

* Windows: <https://www.wch-ic.com/downloads/CH343SER_EXE.html>
* Mac: <https://www.wch-ic.com/downloads/CH34XSER_MAC_ZIP.html>

{% hint style="info" %}
For ChromeOS:

1. &#x20;Download the Arduino IDE(e.g. 1.8.19) for Linux from <https://github.com/arduino/Arduino/releases/download/1.8.19/arduino-1.8.19.tar.xz>
2. &#x20;Install it on the Chromebook. Please refer to the video at <https://www.youtube.com/watch?v=2cve6n4LZqI>
3. &#x20;Plug the Bittle USB type-C data cable into the robot and the Chromebook.
4. Set the Chromebook Linux VM to recognize the USB port

&#x20;      Settings => Advanced => Developers => Linux development environment => Manage USB devices => USB Serial (turn on)

NOTE: Step 4 must be repeated whenever the USB connection is reconnected/powered on.
{% endhint %}


---

# 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://guide.petoi.com/technical-support/useful-tools/biboard-v1.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.