BE-IIS Installer Repository

On this page

BE-IIS Installer Repository

The BE-IIS installer repository contains scripts, overlays, tools, tests and examples for preparing BE-IIS HAT++ boards on Raspberry Pi systems.

The goal is simple:

Manual setup for understanding.
Installer-based setup for deployment.

The repository is open and traceable. It does not contain marketing media, images or binary presentation material.

It is mainly:

ASCII files
Markdown documentation
Shell scripts
Python test scripts
Device Tree overlays
Build files
Configuration files

1. What Is This Repository For?

The repository is used to prepare supported BE-IIS HAT++ boards on Raspberry Pi OS.

It helps with:

  • installing required kernel modules
  • installing Device Tree overlays
  • applying udev rules
  • preparing serial device names
  • configuring supported industrial interfaces
  • testing the installed hardware
  • providing example setups

The installer is intended to reduce manual setup work.

2. Repository Structure

The repository is organized into clear sections:

common/
docs/
examples/
platform/
products/
scripts/
tools/

Each section has a specific purpose.

3. common

The common directory contains shared helper code.

common/lib.sh

This file is used by installer scripts to avoid duplicated shell code.

4. docs

The docs directory contains general documentation.

Example:

docs/be-iis_raspberry-pi-os-flashing-guide.md

This section is used for basic setup information, such as preparing Raspberry Pi OS.

5. examples

The examples directory contains practical setup examples.

One example is:

examples/beiis_field_switch/

This example shows how BE-IIS boards can be used to build a field switch or gateway setup.

It contains setup notes for different Raspberry Pi systems and bridge configurations.

6. platform

The platform directory contains platform-specific integration files.

For Raspberry Pi OS this includes:

platform/raspberry-pi-os/

This section contains:

  • overlay handling
  • systemd service files
  • udev rules
  • helper scripts

The goal is to integrate BE-IIS HAT++ boards cleanly into the operating system.

7. products

The products directory contains the product-specific files.

Examples:

BE-IIS-HPP-T1L-REVB
BE-IIS-HPP-T1S-REVB
BE-IIS-HPP-CAN-FD-SIC-REVB
BE-IIS-HPP-MODBUS-REVB
BE-IIS-HPP-UART-REVB
BE-IIS-HPP-LAN-REVB
BE-IIS-PoSPE

Each product directory can contain:

  • documentation
  • examples
  • files
  • overlays
  • scripts
  • tests
  • udev information

This keeps every board cleanly separated.

8. Device Tree Overlays

Many BE-IIS boards need a Raspberry Pi Device Tree overlay.

The repository contains both source files and built overlay files.

Example structure:

overlays/src/rpi/
overlays/build/rpi/

The source files are stored as:

*.dts

The compiled overlay files are stored as:

*.dtbo

For HAT++ stacking, several overlay variants are provided.

Example:

BE-IIS-HPP-T1S-I.dtbo
BE-IIS-HPP-T1S-II.dtbo
BE-IIS-HPP-T1S-III.dtbo

This allows multiple boards to be used in defined positions.

9. scripts

The scripts directory contains the main installer logic.

Important installer scripts are located in:

scripts/install/

The main entry point is:

scripts/install/install-all.sh

The installer steps include:

01_install_eepdump.sh
02_install-mods.sh
03_install-overlays.sh
04_install_hatpp_service.sh
05_install-udev-rules.sh
06_I2C_VC_ena.sh

This makes the installation process readable and easy to debug.

10. tools

The tools directory contains helper tools for development and deployment.

It includes tools for:

  • EEPROM handling
  • ethtool builds
  • kernel module builds
  • overlay handling

Example:

tools/kernel/

This directory contains scripts for building required kernel modules, for example:

adin1110_mod_build.sh
lan865x_mod_build.sh
mcp251xfd_mod_build.sh
sc16is7xx_mod_build.sh

11. Test Scripts

Several products include test scripts.

Examples:

test.sh
test_target1.sh
test_target2.sh
test_uart.py
beiis_uart_test.py
canperf.py

These scripts are intended to check whether the installed hardware and drivers work as expected.

The tests are not hidden inside a binary tool.

They are plain scripts and can be read, changed and executed manually.

12. Why No Images or Media?

The repository is intentionally technical.

It does not try to be a product brochure.

It contains mostly:

ASCII
Markdown
Shell
Python
Device Tree source
Makefiles
udev rules
systemd files

This makes the repository easy to inspect with normal Linux tools.

Example:

tree
grep
cat
vim
git diff

Everything should be visible and understandable.

13. Summary

The BE-IIS installer repository is the technical foundation for preparing supported BE-IIS HAT++ boards on Raspberry Pi systems.

It contains:

  • installer scripts
  • product-specific overlays
  • kernel module build helpers
  • udev rules
  • systemd integration
  • tests
  • examples
  • documentation

The goal is not to hide the setup process.

The goal is to make it reproducible.

For normal deployment, the installer prepares the system automatically. For development and debugging, every step can still be inspected manually.

Open.
Traceable.
Script-based.
Linux-friendly.

Repository

https://github.com/be-iis/be-iis-installer

© 2026 Brechel Electronic

Imprint (Impressum)
Hugo Universal Theme