While earlier versions of programming software were often buggy, translated poorly, or didn't support newer BIOS chips, became a legendary milestone in the community. It gained popularity because:
Because the CH341A programmer can operate in two distinct modes (Serial TTL/COM port mode or Parallel/SPI programmer mode), installing the correct driver is the most crucial step. Missing this will trigger the dreaded "Device not found" or "USB Error 43" in Windows. Step 1: Configure the Hardware Jumper
In the ever-evolving world of firmware development, BIOS repair, and EEPROM programming, having a reliable, versatile, and up-to-date software solution is non-negotiable. For years, the open-source community has relied on as a lightweight yet powerful alternative to proprietary bloated software suites. With the release of the ASProgrammer 21013 new version, a significant wave of improvements has arrived. asprogrammer 21013 new
ASProgrammer 2.1.0.13 remains a relevant, free, and powerful tool in 2026 for the electronics community. The focus on stability, bug fixes, and usability improvements makes it a reliable choice for firmware writing on a budget. The greatest strength of the platform lies in its open-source nature—new user contributions continually extend its chip list and its capabilities. For hardware tinkerers, laptop repair specialists, and embedded developers, ASProgrammer continues to lower the barrier to entry for professional-grade chip programming.
Read speeds were decent. I successfully dumped a 4MB BIOS file in about 15 seconds. Writing took a bit longer, but no errors verification passed 100%. While earlier versions of programming software were often
| | Specific Features & Improvements | Version / Source | | :--- | :--- | :--- | | Algorithm & Performance | Rewritten algorithms for reading, writing, and detection for improved safety and efficiency. | 2.1.0.13 | | | CH341A SPI writing speed increased by about 10%. | V4.15 Update | | | Optimized "busy check" setting to potentially improve programming efficiency. | Custom Builds | | User Interface (UI) | Improved interface with adjustable window size (min 450px / max 950px). | 2.1.0.13 | | | The software remembers the last window position and last used settings. | 2.1.0.13 | | | Added an option to not automatically fill buffers after selecting a component. | 2.1.0.13 | | | "AsProgrammer v2.0.4" introduced an interface specifically adapted for CH341A & FT232H users. | v2.0.4 | | Hardware Compatibility | Official support for CH341A and USBASP programmers. | 2.1.0.13 | | | Expanded hardware support includes Buzzpirat, Bus Pirate, CH347, UsbAsp, AVRISP, Arduino, and FT232H. | V4.15 Update | | New Component Support | Added support for Nuvoton N76E003 series microcontrollers. | 2.1.0.13 | | | Rewritten programming algorithm for special components like M35080. | 2.1.0.13 | | | Added support for various new flash memory ICs like MX25L6436F, MT25QU256, W25Q64JV, etc. | V4.15 Update | | Language & Localization | Added Traditional Chinese, Turkish, and Spanish translations. | V4.15 Update | | | Many modified versions and the NeoProgrammer branch now include built-in Chinese language support. | NeoProgrammer |
At its heart, ASProgrammer is a free, portable, and open-source graphical software designed to read, erase, and write data to common serial memory chips such as SPI Flash, EEPROM, and MicroWire memory. It acts as the essential bridge between a computer and a hardware programmer, allowing users to read, edit, and write firmware data. It is compatible with a wide range of low-cost programming hardware, including the USBasp and AVRISP-MKII, but its most widespread use is with the extremely popular CH341A programmer. This version is especially well-known for handling SPI Flash chips found in computer motherboards (containing the BIOS/UEFI), routers, graphics cards, and other electronic devices. Step 1: Configure the Hardware Jumper In the
Modern variants support expanded SPI chip lists (like the W25Q128JV or MX25U25673G) and fix old DPI interface scaling errors. Step-by-Step: Setting Up and Building the New Framework
: Always run the Verify command after a write operation to ensure the buffer matches the physical chip data.