> For the complete documentation index, see [llms.txt](https://auvidea.gitbook.io/b101-and-b102/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://auvidea.gitbook.io/b101-and-b102/manual/b101-and-b102-overview.md).

# B101 & B102 Overview

<figure><img src="https://1086285270-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZL3dWTIQHiemrAM3rk7F%2Fuploads%2Fv6vpsc80Wk65qLBMEIg0%2F38126-4%20B101%20(5)-freigestellt-cropped.png?alt=media&amp;token=84d986dd-1283-47e6-866b-0c10aa31734c" alt="" width="563"><figcaption></figcaption></figure>

## Product SKU

<table><thead><tr><th width="173">SKU</th><th>Description</th></tr></thead><tbody><tr><td>70501</td><td>B101</td></tr><tr><td>70502</td><td>B102</td></tr></tbody></table>

## Document versions and changes

<table><thead><tr><th width="118">Version</th><th>Changes</th></tr></thead><tbody><tr><td>1.0</td><td>Initial release</td></tr><tr><td>1.1</td><td>Ported Manual to Gitbook</td></tr><tr><td>1.2</td><td>Complete rework of manual</td></tr></tbody></table>

{% hint style="warning" %}
Auvidea can take no responsibility for the accuracy or completeness of any information presented in an exported PDF document as the export feature is developed, managed and maintained by GitBook. Those export mechanisms are subject to change without interaction by Auvidea. Please note that Auvidea includes this version table to identify the document and reference changes.
{% endhint %}

## Product revisions and changes <a href="#toc112747284" id="toc112747284"></a>

{% tabs %}
{% tab title="B101" %}

<table><thead><tr><th width="140.5">Version</th><th>Changes</th></tr></thead><tbody><tr><td>38126-1</td><td>Internal release</td></tr><tr><td>38126-2</td><td>Bug fixes</td></tr><tr><td>38126-3</td><td>added 2nd cam LED</td></tr><tr><td>38126-4</td><td>Added I2S Connector</td></tr></tbody></table>
{% endtab %}

{% tab title="B102" %}

<table><thead><tr><th width="134.5">Version</th><th>Changes</th></tr></thead><tbody><tr><td>38127-1</td><td>Production release</td></tr><tr><td>38127-2</td><td>Added I2S connector</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## What is the B101/B102?

The B101/B102 is a HDMI to CSI bridge with I2S Audio Interface designed for the Raspberry PI/HummingBoard. The difference between the B101 and the B102 is the data rate that can be sent over CSI-2. The B102 features 22-pin FFC-Connector with 4 lanes. The B101 only supports a 15-pin FFC-Connector with 2 data lanes.

## **Compatible systems**

* Nvidia Jetson (Prefered platform)
* Raspberry Pi models A, B, B+, 3
* HummingBoard

{% hint style="info" %}
Keep in mind that your choice of platform will require a proper Devicetree and driver implementation to work with the B101/B102. For further informations please contact <support@auvidea.eu>
{% endhint %}

## Product features

* HDMI input: 1080p25 only on the RPi (software limitation of the RPi at this time)
* HDMI to CSI-2 bridge chip: Toshiba TC358743XBG
* size: 27 x 42 mm (PCB size)
* MIPI CSI-2 4 lanes (B102) / 2 lanes (B101)
* mounting: 3x M2.5 mounting holes (do not use M3 screws)
* mount hole spacing: 22 mm x 21 mm
* power: 3.3V


---

# 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://auvidea.gitbook.io/b101-and-b102/manual/b101-and-b102-overview.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.