logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

AsProgrammer software download: official GitHub links, dregmod fork, CH341A, CH347 support

Ask a question on the Forum

User question

Where to download asprogrammer software from

Artificial Intelligence Response

Direct answer to the question

• Download AsProgrammer only from the project’s own Git-Hub repositories (original or maintained forks).
• Primary URL (original project): https://github.com/nofeletru/UsbAsp-flash → “Releases” tab (latest v2.1.0).
• Most-actively-maintained fork (“dregmod”): https://github.com/therealdreg/asprogrammer-dregmod → “Releases” tab (currently v3.16).
• Any other site should be used only as a mirror after verifying checksums/signatures against the files published on Git-Hub.

Detailed problem analysis

  1. Why Git-Hub is the reference
    • AsProgrammer is open-source (MIT licence). The canonical repositories keep the entire commit history, signed tags, and published checksums, allowing you to verify integrity.
    • Git-Hub “Assets” files are uploaded by the maintainer’s account, which significantly reduces the chance of tampering compared with random download portals.

  2. Which repository to choose
    a) Original (“nofeletru/UsbAsp-flash”)
    – Last tagged release v2.1.0 (Apr 2019).
    – Stable, covers CH341A, USBasp, FT232, AVR ISP-MkII, etc.
    b) Active fork (“therealdreg/asprogrammer-dregmod”)
    – Ongoing development (Dec 2023: v3.16).
    – Adds CH347 support, higher-speed CH341A SPI writes, new flash IDs, UI localisation, bug fixes.
    – Preferred if you need newer device IDs or CH347T/CH347F adapters.
    c) Other forks (e.g., zapaka, openFPGALoader patch sets) exist but are niche; build from source if required.

  3. Release structure
    – Portable archive (ZIP/7z). Contains AsProgrammer.exe + DLLs + scripts + chip databases.
    – No installer; unpack into any writable directory.
    – For Linux/macOS: source only; build with Qt ≥ 5.12 and libusb-1.0.

  4. Driver prerequisite (Windows)
    – CH341/CH347: replace default “wchusbserial” with WinUSB/libusb-win32 via Zadig.
    – USBasp: use the libusb-win32 filter driver package.
    – FTDI-based adapters: FTDI D2XX or WinUSB driver.

  5. Checksum / signature verification
    – Every Git-Hub release lists SHA-256 (dregmod) or SHA-1 (legacy).
    – After download: 

     certutil -hashfile ASProgrammer_3.16.zip SHA256

    Compare with the value shown in the release notes.

Current information and trends

• Latest original tag v2.1.0 (2019) is stable but dormant.
• Fork “dregmod” is under active maintenance (v3.16, Dec 2023) – integrates new SPI opcodes, larger chip database, CH347, performance tuning (~10 % faster writes).
• Unofficial repackaged builds (e.g., “2.0.4 2024” seen on DisplayMonk/Khandish) usually re-zip an existing Git-Hub build; no verifiable code changes and occasionally modified executables. Use only for reference, not as a primary download.
• Growing interest in CH347’s high-speed mode; support appears first in dregmod.
• Alternatives gaining popularity: NeoProgrammer (proprietary, CH341A only) and Flashrom (CLI, cross-platform, huge device list, signed releases).

Supporting explanations and details

Example workflow (Windows 10 x64, CH341A black board):

  1. Download “ASProgrammer-3.16-win64.zip” from the dregmod release page.
  2. Extract to C:\Tools\AsProgrammer.
  3. Run Zadig → List All Devices → select “USB-EPP/I2C… CH341A” → choose “WinUSB (libusb-0.1)”.
  4. Start AsProgrammer.exe (Run as Administrator only if write-protect pins need toggling).
  5. Device → CH341A → detect chip → Read → Save backup → then Erase/Program/Verify.

Ethical and legal aspects

• Firmware flashing may void warranties or violate vendor licences—ensure you own the target hardware or have written consent.
• Do not redistribute proprietary firmware images.
• Avoid modified binaries from warez sites; they may embed malware or break GPL/MIT licensing terms.

Practical guidelines

Best practices
• Always read the flash first and keep two separate backups (hash-checked).
• Use a 3.3 V-tolerant clip/cable; over-voltage fries SPI flash.
• When updating BIOS chips in-circuit, power the board only from the programmer OR from the main PSU, never both simultaneously unless the programmer supports level-shifting.
Potential challenges
• “Chip not responding” → check driver, orientation, supply voltage, hold# pin pulled high.
• Corrupted verify → slow down SPI clock or power the flash externally.

Possible disclaimers or additional notes

• The original maintainer has not merged pull requests since 2020. Future security fixes may only appear in forks.
• macOS support is experimental; HID-based programmers (e.g., CH340E boards) are not recognised.
• GUI translations can introduce string-format bugs—stick to English interface if you hit crashes.

Suggestions for further research

• Compare write-speed and reliability of CH341A + AsProgrammer vs. CH347 + dregmod vs. FT232H + flashrom.
• Investigate automatic verification scripts using the AsProgrammer command-line interface (--script file.s).
• Explore using Sigrok/Logic-2 to monitor SPI traffic while flashing for educational purposes.
• Follow open-source EC/BIOS communities (e.g., coreboot, Libreboot) for new device-ID patches.

Brief summary

The safest, up-to-date way to obtain AsProgrammer is to download the portable ZIP archive from its Git-Hub “Releases” page—either the original repository (nofeletru/UsbAsp-flash) or the actively maintained fork (therealdreg/asprogrammer-dregmod). Verify the archive’s checksum, install the correct USB driver (WinUSB/libusb), then run the executable. Avoid unverified mirrors; treat any “new version” not traceable to Git-Hub with caution.

User question

how can i download

Artificial Intelligence Response

Direct answer to the question

Your question looks incomplete, so I will assume you mean “How can I download AsProgrammer?” If so, download it from the official GitHub Releases pages, not random mirror sites. As of April 20, 2026, the main upstream project nofeletru/UsbAsp-flash shows v2.1.2 as its latest release dated January 24, 2025, while the fork therealdreg/asprogrammer-dregmod shows v3.17 released December 28, 2024. Both repositories list support for CH341A/CH347-class programmers. (github.com)

Recommended choice:

  • Use nofeletru/UsbAsp-flash if you want the current upstream/original project. (github.com)
  • Use therealdreg/asprogrammer-dregmod if you specifically want that fork and its Bus Pirate/Buzzpirat-oriented additions. The fork itself tells users to report non-fork-specific issues to the official upstream project. (github.com)

Detailed problem analysis

Step-by-step download procedure

  1. Open the Releases page for either:

    • nofeletru/UsbAsp-flash, or
    • therealdreg/asprogrammer-dregmod. (github.com)

  2. Select the latest release and download the file under Assets. If the asset is a ZIP archive, extract it to a normal folder first, for example C:\Tools\AsProgrammer. The project documentation also recommends using the Release executable, not running from an IDE debug environment. (github.com)

  3. Run AsProgrammer.exe from the extracted folder. (github.com)

  4. If your programmer is not detected, install the USB driver with Zadig. The official Zadig site says it installs generic USB drivers such as WinUSB, libusb-win32, and libusbK for Windows devices. (zadig.akeo.ie)

Driver installation with Zadig

A practical sequence is:

  1. Plug in the programmer.
  2. Launch Zadig as administrator.
  3. If the device is not visible, use Options → List All Devices.
  4. Select your programmer from the dropdown.
  5. Choose WinUSB, libusb-win32/libusb0, or libusbK.
  6. Click Install Driver. The official Zadig guide documents this exact flow and notes that replacing an existing driver must be done carefully. (github.com)

Current information and trends

A correction to some older guides: the upstream/original project is not stuck at v2.1.0 anymore. The official upstream repository currently shows v2.1.2 released on January 24, 2025. Also, the upstream README now lists CH347 support, so statements saying the original build lacks CH347 support are outdated. (github.com)

The dregmod fork’s latest visible release is v3.17 from December 28, 2024, and its changelog says it pulled in upstream changes dated 2024-12-29, including updated files, drivers, and chip lists. (github.com)

Supporting explanations and details

From an electronics-engineering perspective, downloading the software is only the first step; driver binding and hardware voltage correctness are what usually determine success.

  • The fork documentation warns to keep USB cabling short and good quality, and recommends relatively conservative protocol speeds, around 100 kHz maximum, because cable length, adapters, and low-voltage targets can reduce signal integrity. (github.com)
  • For 1.8 V flash devices, the documentation explicitly warns not to connect 3.3 V or 5 V directly to the chip. (github.com)

In practical terms: if AsProgrammer opens but cannot read the chip ID, the problem is usually driver selection, wiring, clip contact quality, SPI speed, or incorrect target voltage, not the download itself. (github.com)

Ethical and legal aspects

  • Only read or write firmware on hardware you own or are authorized to service.
  • Be careful when replacing USB drivers with Zadig, because the official guide warns that replacing the wrong device driver can make that device unavailable to Windows in its normal role. (github.com)
  • For memory programming, avoid unsafe voltage application, especially with 1.8 V SPI flash, to prevent permanent damage. (github.com)

Practical guidelines

Best practice workflow:

  • Download from the official GitHub release page. (github.com)
  • Extract to a simple local folder.
  • Install the correct USB driver with Zadig if detection fails. (github.com)
  • Start by using Read ID or Read IC before attempting any write operation. The examples in the fork follow that pattern. (github.com)
  • If communication is unstable, reduce speed and shorten cables. (github.com)
  • If the target is a 1.8 V part, use the correct adapter/power arrangement. (github.com)

Possible disclaimers or additional notes

Because your original question was just “how can i download”, I inferred that you meant AsProgrammer from the provided sample context. If you meant a different application or file, the instructions will change.

Also, GitHub sometimes hides the exact asset names behind dynamic page loading, so the reliable rule is simply: open the release page, then download the file listed under Assets for the release you want. (github.com)

Suggestions for further research

If you continue after download, the next useful topics are:

  • choosing WinUSB vs libusb-win32 vs libusbK for your exact programmer, (github.com)
  • safe handling of 1.8 V vs 3.3 V SPI flash, (github.com)
  • supported programmer families such as CH341A, CH347, FT232H, USBasp, Arduino, AVRISP(LUFA). (github.com)

Brief summary

If you mean AsProgrammer, download it from the official GitHub Releases page for either nofeletru/UsbAsp-flash or therealdreg/asprogrammer-dregmod, extract it, run AsProgrammer.exe, and install the USB driver with Zadig if the hardware is not detected. As of April 20, 2026, the upstream repo shows v2.1.2 from January 24, 2025, and the dregmod fork shows v3.17 from December 28, 2024. (github.com)

If you want, I can give you the exact clicks for:

  • Windows
  • CH341A
  • CH347
  • or GitHub download steps with screenshots-style instructions

Ask additional question

Wait...(2min)
Disclaimer: The responses provided by artificial intelligence (language model) may be inaccurate and misleading. Elektroda is not responsible for the accuracy, reliability, or completeness of the presented information. All responses should be verified by the user.
Report illegal content (Article 16 DSA)