OpenIPC Firmware

netblink is a minimal Linux command-line utility designed for embedded systems (like routers and IP cameras) to monitor network connectivity or traffic. It uses a GPIO-driven LED via the sysfs interface to indicate status through specific blink patterns.

It supports two primary modes:

• Ping mode: Periodically pings a host; the blink pattern reflects the Round Trip Time (RTT).
• Traffic mode: Monitors a network interface; the blink rate reflects the combined transmit (tx) and receive (rx) throughput.

gpiostep-openipc is an in-kernel GPIO half-step stepper driver and userspace CLI designed for PTZ (Pan/Tilt/Zoom) cameras. It is specifically intended for cameras using 4-wire stepper motors wired directly to GPIO pins (such as the Goke GK7205V510).

Compared to the userspace gpio-motors tool, gpiostep provides steadier timing and lower CPU usage because it executes gpio_set_value() directly within the kernel context rather than toggling /sys/class/gpio from userspace. It implements the same 8-phase half-step sequence and command signature as gpio-motors.

OpenIPC is an open-source alternative firmware for IP cameras, built on Buildroot. It is designed to provide a stable, flexible, and open IP Network Camera Framework.

Supported SoC (System on Chip) manufacturers include:

• HiSilicon
• Ambarella
• Anyka
• Fullhan
• Goke
• GrainMedia
• Ingenic
• MStar
• Novatek
• SigmaStar
• XiongMai

The OpenIPC Matter IP Camera Server is a minimal, self-contained Matter-compatible server written in C (POSIX / C99). It implements a subset of the Matter 1.2 specification, allowing IP cameras to be discoverable and controllable by Matter controllers like Apple Home, Google Home, and Amazon Alexa without requiring the official Matter SDK.

Key characteristics:

• Matter Interaction Model: Operates over TCP on port 5540.
• mDNS Announcement: Broadcasts _matter._tcp.local every 30 seconds on port 5353.
• RTSP Integration: Exposes the camera's RTSP stream URL as a Matter attribute.
• Zero Dependencies: Written in pure C99 / POSIX.
• Prototype Status: This is a prototype implementation where PASE/CASE cryptography (SPAKE2+) is stubbed out. It accepts commissioning requests but does not perform real cryptographic handshakes.

For security, mqtt-bot only executes commands explicitly defined in the whitelist using the -w flag. Each entry follows the format <command_name>:<path_to_executable>[:<arg1>[:<arg2>...]].

Constraints:

• You can define up to 64 whitelist entries.
• Each command can have up to 8 argv entries.
• Unknown commands are rejected and logged without execution.

Example: Basic command and arguments

# Basic command
# Triggering 'reboot' via MQTT topic will run /sbin/reboot
mqtt-bot -h mqtt.local -w reboot:/sbin/reboot

# Command with arguments
# Triggering 'snap_hq' will run ffmpeg with specific arguments
mqtt-bot -h mqtt.local -w snap_hq:/usr/bin/ffmpeg:-i:rtsp://cam/s:-frames:1:/tmp/snap.jpg

mqtt-bot -h mqtt.local -u admin -P secret -t cam/cmds \
         -w snap_hq:/usr/bin/ffmpeg:-i:rtsp://cam/s:-frames:1:/tmp/snap.jpg

The output format depends on whether you use the quiet flag -q.

Default (verbose)

Includes timestamp, topic, priority, and tags:

[2024-01-15 08:15:23] alerts [HIGH] Warning: CPU at 98%
  tags: warning,cpu
[2024-01-15 08:16:01] alerts Backup completed

Quiet (-q)

Outputs only the raw message body, ideal for shell pipes:

CPU at 98%
Backup completed

To support a 400W sensor (e.g., X50), follow the same procedure as the 200W sensor, but select the X50 sensor during configuration:

1. Navigate to mpp\isp\ispsample.
2. Run ./mkconfig.
3. In the interactive menu:
   • Select SOC: XMSDK
   • Select Sensor: X50
   • Confirm with OK.
4. Compile: make clean; make.
5. Replace the libraries in mpp\lib\isp with those from mpp\isp\ispsample\output.
6. Recompile the program in mpp\sample\venc using make clean; make.

Before configuring the camera, you must register in the Nabto Cloud Console to obtain the required identifiers:

• Product ID: pr-xxxxxxxx
• Device ID: de-xxxxxxxx

These IDs are necessary for the initial device configuration and to allow the device to attach to the Nabto Basestation.

To set up ZeroTier One on your camera, follow these steps:

1. Register an account at my.zerotier.com.
2. Create a network and obtain its Network ID. Ensure the network is configured as Private.
3. Access your camera's console (via web console or SSH) and join the network using the zerotier-cli join command with your Network ID: zerotier-cli join <network_id> A successful join will return the status: <200 join OK>.
4. Go to the my.zerotier.com web interface and authorize the newly connected camera by checking the box next to the corresponding peer.

Note: All configuration data is stored in /var/lib/zerotier-one.

The w1-ds18b20 application enables reading temperature from DS18B20 sensors using bitbang mode via direct GPIO memory access.

Requirements:

• A pull-up resistor must be connected to the sensor.
• Currently, only HiSilicon-style GPIO offsets are supported.
• You must identify the correct GPIO base address and GPIO number for your specific hardware (e.g., by consulting the datasheet or using ipctool).

Usage: Run the binary with the -base flag specifying the GPIO memory base address and the -gpio flag specifying the GPIO pin number.