FAQ
TL;DR: uProg writes AVR flash at 12.5 kB/s and reads at 14.5 kB/s; “The best results can be obtained with BIN files” [Elektroda, manekinen, post #9597772] Why it matters: those rates cut on-site firmware updates to under six seconds for a 64 kB image.
Quick Facts
• Foot-print: 44 × 39 × 5.5 mm, 5 mA menu current [Elektroda, manekinen, post #9597772]
• Peak write: 12.5 kB/s; verify read-back 14.5 kB/s [Elektroda, manekinen, post #9597772]
• Supported cards: 128 MB – 2 GB SD/MMC, FAT16/32 (SDHC in roadmap) [Elektroda, manekinen, post #9597772]
• Stand-by draw: 0.10 µA; boot surge ≤ 100 mA (card-dependent) [Elektroda, manekinen, post #9597772]
• Tested MCUs: ATtiny13 → ATmega2561; auto SCK 4 MHz-62.5 kHz [Elektroda, manekinen, post #9597772]
How do I power uProg and the target safely?
SD ERROR at start-up—what fixes it?
Which displays are plug-and-play?
Can I delete files directly on uProg?
How do I enter fusebits without a PC?
Why does verification fail after long cables?
Auto-speed starts at 4 MHz SCK and steps down on first error. A 30 cm ribbon may still pass the signature test but corrupt data. Limit length to ≤ 20 cm or set Max SCK=3 in config.ini (250 kHz)
[Elektroda, manekinen, post #9597772]
‘File too big’ when flashing ATtiny25—work-around?
How can I speed up the programmer itself?
What’s the typical failure after reverse-biasing C5?
Is Li-ion charging supported on-board?
PCB 1.2 exposes SO8 and SOT-223 pads so you can add MCP73831 charger and LDO. Factory firmware doesn’t monitor charge; add external LED or ADC mod as in user build
[Elektroda, MatygaD, post #9773466] A native charger is on the roadmap.
Quick How-To: update uProg firmware from SD
- Copy new BIN as 000.bin to card root. 2. Insert card and power-on; blank screen confirms bootloader mode. 3. Press RI to flash; after reboot the splash shows the new version [Elektroda, manekinen, post #9597772]
What statistic proves BIN is faster than HEX?
Edge-case: what if the LCD shows only a dash?
Generated by the language model.