Opgui is the modern, cross-platform graphical user interface used to control the Open Programmer USB hardware, whereas OpenProg is the legacy Windows-only software application whose interface development has been officially terminated. Both applications share the same underlying chip-programming logic, but they differ significantly in their toolsets, framework dependencies, and long-term support.
The primary shift in recent project updates—culminating in version 0.12.4—focuses on migrating Opgui to modern UI toolkits, expanding microcontroller support, and consolidating codebases while leaving the old OpenProg client behind. Core Differences: Opgui vs. OpenProg Opgui (Modern UI) OpenProg (Legacy App) Operating Systems Windows and Linux Windows only (Legacy versions up to Windows 8) Interface Library GTK3 (recently migrated from GTK2) Native Win32 (originally compiled in Visual C++ 6) Dependency Requirement Requires external GTK runtime libraries No external libraries needed (standalone executable) Advanced Features Supports In-Circuit Debugging (ICD) and hardware testing Basic programming functions only Development Status Actively maintained and updated Terminated; interface is frozen What Changed in the New Updates? 1. Transition to GTK3 Framework
Older versions of Opgui relied heavily on outdated GTK2 libraries, which required a specific 64-bit GTK Runtime Environment on Windows. Recent updates migrated the codebase to GTK3. This structural change provides significantly better native compatibility for modern Windows (x64) and Linux installations, fixing long-standing window rendering bugs. 2. Codebase Consolidation
To optimize open-source maintenance, developers merged the separate source trees of the command-line interface (op) and the graphical software (opgui) into a single, unified repository. 3. Expanded Chip & Microcontroller Support
While old OpenProg binaries remain locked to historical algorithms, the updated Opgui software introduces massive compatibility fixes for newer PIC microcontrollers. In the latest v0.12.4 release, the following silicon updates were deployed via the Open Programmer SourceForge Files Page:
New Targets Added: Added full compatibility for 18F04, 18F05, 18F06, 18F14, 18F15, and 18F16Q20 microcontrollers.
Configuration Fixes: Resolved critical configuration word write errors on 18FXXQ10 series chips.
Erase/Write Optimizations: Repaired broken flash erase and write routines targeting the 16F131XX, 16F152XX, 16F171XX, and 16F18XXX families. 4. Linux Hardware Access Layer Adjustments
For users running Opgui on open-source distributions, the update refined how the application communicates with the hardware over USB. The pathing for hardware interactions was refactored to standard /dev/hidraw device handling, preventing permissions errors on newer Linux kernels.
Are you trying to update an existing physical Open Programmer board to flash a specific microcontroller chip? Opgui and OpenProg user’s guide v.1.2 Step 1
Leave a Reply