> For the complete documentation index, see [llms.txt](https://docs.petoi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.petoi.com/apis/raspberry-pi-serial-port-as-an-interfac/for-biboard-v1.md).
# For BiBoard V1
### Hardware Connection
You can solder a 5-pin socket on BiBoard V1 to plug in a Raspberry Pi.
The white [Pi standoff](https://github.com/PetoiCamp/NonCodeFiles/blob/master/stl/Bittle%20%26%20BittleX/RaspberryPiStandOff/Pi_StandOffRegular.stl) can be 3D printed.
You can 3D print a new [back cover](https://github.com/PetoiCamp/NonCodeFiles/blob/master/stl/Bittle%20%26%20BittleX/BittleCover/Bittle_Cover_with_hole_for_Pi.stl) that fits the Raspberry Pi socket, as follows:
After plug in the Raspberry Pi board , power on the BiBoard via USB data cable or Battery.
### Software Setup
Open the [serial monitor](https://docs.petoi.com/arduino-ide/serial-monitor#biboard), and send serial command **XS** to enable the [Serail 2](https://docs.petoi.com/arduino-ide/upload-sketch-for-biboard#id-2.9-swith-working-mode-via-the-serial-commands-optional) working mode.
{% hint style="info" %}
You can also modify the source code (***OpenCat.h***) and [upload the sketch for BiBoard](https://docs.petoi.com/arduino-ide/upload-sketch-for-biboard) to enable the Serail 2 working mode:
{% endhint %}
### Serial port name on Pi
{% hint style="info" %}
Generally, the serial port name on Raspberry **Pi 3 and 4** is "**/dev/ttyS0**," and the one on Raspberry **Pi 5** is "**/dev/ttyAMA0**." If the Pi can't open the serial port after it is connected to the mainboard, you can uncomment the line of code as follows to check all the serial ports on the Raspberry Pi in the terminal when the Python script(ardSerial.py) is running.
{% 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.petoi.com/apis/raspberry-pi-serial-port-as-an-interfac/for-biboard-v1.md?ask=&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.
