Softprober Plugins

Scenario 1: You are referring to the Software/Hardware Inventory Tool (Linux)

If you are a system administrator or a Linux user using the softprober tool (often used for system health, DMI decoding, or hardware inventory), "plugins" usually refer to the modules or extensions used to gather specific data.

How SoftProber Plugins Work: In this context, the tool likely uses a modular architecture to probe different hardware components without taxing the system.

1. Where to find them:

   • Check the installation directory (usually /usr/lib/softprober/plugins or /usr/share/softprober depending on your distro).
   • Plugins are often shared objects (.so) or executable scripts.

2. Common Plugin Categories:

   • CPU Plugins: Probe clock speeds, cache sizes, and temperature.
   • Storage Plugins: Interact with smartctl to check hard drive health.
   • Memory Plugins: Read EDID data or check RAM slot usage.
   • Network Plugins: Check interface speeds and driver status.

3. Troubleshooting Plugins:

   • Permission Errors: Hardware probing plugins often require root privileges. If a plugin fails to load, try running the main command with sudo.
   • Missing Data: If a specific plugin returns "N/A", ensure the relevant kernel modules are loaded (e.g., modprobe eeprom for memory data).

Step 4: Develop the Plugin Functionality

Develop the plugin functionality by implementing the plugin's specific logic.

Scenario 2: You are referring to "SoftProber" as a Typo for SoftMaker or similar Software

There is a popular office suite called SoftMaker Office (and previously "SoftMaker FreeOffice"), and users sometimes confuse the name. softprober plugins

If you meant SoftMaker Office:

• Plugins: SoftMaker does not use a traditional "plugin" system like Chrome or WordPress. Instead, it supports Add-ins and Macros.
• How to add functionality:
  • You can write Basic scripts or Python scripts to automate tasks.
  • You can install dictionaries (spell check plugins) via the Tools > Options menu.

Introduction

Softprober is a powerful tool for software development and testing. One of its key features is the ability to extend its functionality through plugins. In this guide, we will walk you through the process of developing plugins for Softprober.

2. Stimulus & Fault Injection

Verification isn't just about watching; it’s about breaking things safely. Scenario 1: You are referring to the Software/Hardware

• Signal Forcing: Override internal states directly from your testbench (SV/Python/C++) to test error-handling routines.
• Fault Injection Plugins: Systematically flip bits or delay signals to test fault-tolerant architectures without adding clutter to your design files.

Step 3: Implement the Plugin Interface

Each plugin must implement the SoftproberPlugin interface. This interface defines the following methods:

• init(): called when the plugin is loaded.
• shutdown(): called when the plugin is unloaded.
• getPluginInfo(): returns information about the plugin.

Design patterns for effective SoftProber plugins

• Declarative probe specs: define where/how to probe using high-level rules (paths, annotations, conditions) rather than scattered imperative code.
• Context propagation: maintain trace and request context so probes correlate across async boundaries.
• Pluggable exporters: separate capture from storage/export to let teams route signals to traces, logs, SIEMs, or local debugging tools.
• Safe execution sandbox: run complex analysis in isolated contexts (threads, pooled workers, or separate processes) to avoid destabilizing the host.
• Policy-first probes: enable configurable rules for data capture, retention, and redaction to meet legal and security constraints.
• Feature-flagged probing: gate probes behind flags for gradual rollout and quick disable.
• Probe templates and libraries: reusable patterns for common needs (DB calls, HTTP handlers, serialization).

Troubleshooting Common Plugin Errors

Even seasoned users encounter plugin issues. Here is a quick diagnostic table:

| Error Message | Likely Cause | Solution | | :--- | :--- | :--- | | "Plugin failed to load (0x8007007E)" | Missing VC++ Redistributable | Install Microsoft Visual C++ 2015-2022 x64 | | "Access violation at address..." | Antivirus blocking DLL injection | Add SoftProber folder to Defender exclusions | | "No sensors found for device" | Incorrect plugin version for your hardware | Check if the plugin supports your specific chipset (Z790 vs X670) | | "Timeout on MQTT publish" | Firewall blocking port 1883 | Allow SoftProber.exe through Windows Firewall (Inbound rules) | Where to find them:

Pro Tip: Always run SoftProber with administrator privileges. Many plugins, especially the Hardware Bridge and USB HID plugins, require Ring 0 access to read hardware registers.