Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamWhere to download asprogrammer software from
• 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.
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.
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.
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.
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.
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.
• 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).
Example workflow (Windows 10 x64, CH341A black board):
C:\Tools\AsProgrammer
. AsProgrammer.exe
(Run as Administrator only if write-protect pins need toggling). • 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.
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.
• 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.
• 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.
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.