mirror of
https://github.com/avrdudes/avrdude.git
synced 2026-07-24 02:12:28 +03:00
Add dryboot programmer
This commit is contained in:
@@ -851,6 +851,29 @@ programmer # dryrun
|
||||
prog_modes = PM_TPI | PM_ISP | PM_PDI | PM_UPDI | PM_HVSP | PM_HVPP | PM_aWire;
|
||||
;
|
||||
|
||||
#------------------------------------------------------------
|
||||
# dryboot
|
||||
#------------------------------------------------------------
|
||||
|
||||
# Like -c dryrun the -c dryboot programmer only emulates programming,
|
||||
# albeit for communicating to bootloaders, ie, without a physical
|
||||
# programmer between the host and the target AVR part. AVRDUDE behaves
|
||||
# slightly different when talking to a bootloader: Whilst for most classic
|
||||
# parts the flash memory looks like NOR-memory, ie, cleared bits cannot be
|
||||
# set and therefore programming requires a chip erase first, bootloaders
|
||||
# do have the power of erasing a flash page (setting it to all 0xff)
|
||||
# before writing a page. This requires AVRDUDE to behave differently when
|
||||
# talking to a bootloader, which it recognises by the prog_modes = PM_SPM
|
||||
# setting below. -c dryboot allows exploring these differences at an
|
||||
# emulation level.
|
||||
|
||||
programmer # dryboot
|
||||
id = "dryboot";
|
||||
desc = "Emulates bootloader programming without a programmer";
|
||||
type = "dryrun";
|
||||
prog_modes = PM_SPM;
|
||||
;
|
||||
|
||||
#------------------------------------------------------------
|
||||
# wiring
|
||||
#------------------------------------------------------------
|
||||
|
||||
Reference in New Issue
Block a user