# wohdek21/project-roll architecture

> Architecture diagram of the GitHub repository wohdek21/project-roll, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-25). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/wohdek21/project-roll
- Repository: https://github.com/wohdek21/project-roll

## Overview

##### Main Components (Nodes)
a. Hardware Layer:
- Raspberry Pi 4 (central processing unit)
- Touchscreen display (connected via MIPI DSI)
- PN532 module (RFID/NFC operations)
- Radio CC1101 module (433MHz signal TX/RX)

b. Software / OS Layer:
- RollOS – a Linux-based operating system adapted for this project.
- RollUI – the customized user interface running on RollOS.
- Optional embedded services, such as those for pentesting functions (e.g., IR signal processing, RFID emulation, etc.).

##### Relationships and Interactions
- Touchscreen directly to the Pi via the MIPI DSI interface.
- PN532 module and Radio CC1101 module as peripheral extensions connected to the Pi (they can be drawn either as external modules linked via GPIO, SPI, or another appropriate bus).
- That RollOS runs on the Raspberry Pi and is the platform supporting the RollUI and other service applications.
- Hardware inputs from RFID, NFC, IR signals and radio are processed by the OS services.
- The RollUI provides an interface for users to interact with those functionalities.

##### Architectural Patterns and Design Principles
- Layered Architecture: Separate hardware, operating system, user interface, and specialized service modules.
- Modular Design: Each component (e.g., RollUI, RFID/NFC handling, radio communication) is designed to be potentially optional or replaceable, reflecting the highly customizable nature of the device.
- Integration of multiple communication protocols (e.g., MIPI DSI for display, possibly I2C/SPI/GPIO for other modules).

##### Incorporate Specific Technologies and Interfaces
- Physical connectivity for the peripherals: PN532 for RFID/NFC and Radio CC1101 for radio, showing their communication interfaces (e.g., SPI, I2C, or UART depending on the actual implementation).

## Diagram (Mermaid)

```mermaid
flowchart TD
    subgraph "Hardware Layer"
        A["Raspberry Pi 4"]:::hardware
        B["Touchscreen (MIPI DSI)"]:::hardware
        C["PN532 Module (RFID/NFC)"]:::hardware
        D["Radio CC1101 Module (433MHz)"]:::hardware
    end

    subgraph "Operating System Layer"
        E["RollOS (Linux-based OS)"]:::software
    end

    subgraph "Application Layer"
        F["RollUI (Custom UI)"]:::interface
        G["Pentesting Services"]:::interface
        H["UI Assets"]:::interface
    end

    A -->|"MIPI_DSI"| B
    A -->|"GPIO/SPI"| C
    A -->|"GPIO/SPI"| D
    A -->|"Runs_OS"| E
    E -->|"Provides_UI_support"| F
    E -->|"Handles_services"| G
    F -->|"Uses_images"| H

    click E "https://github.com/wohdek21/project-roll/blob/main/README.md"
    click F "https://github.com/wohdek21/project-roll/blob/main/README.md"
    click H "https://github.com/wohdek21/project-roll/tree/main/Assets/Img"

    classDef hardware fill:#f96,stroke:#333,stroke-width:2px;
    classDef software fill:#6cf,stroke:#333,stroke-width:2px;
    classDef interface fill:#9f6,stroke:#333,stroke-width:2px;
```
