Mirrors/avrdude
1
0
Fork 0
mirror of https://github.com/avrdudes/avrdude.git synced 2026-09-21 16:46:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1689 from dbuchwald/serialupdi_doc_update

Browse Source 
Updated section about NVM models support
This commit is contained in:
Stefan Rueger
2024-02-24 00:26:24 +13:00
committed by GitHub
parent 4b7da29cbe 565a7238f4
commit 2425ee98a6
1 changed files with 5 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/doc/avrdude.texi
View File

@@ -3722,15 +3722,11 @@ Tx---/\/\/\---Tx |----|<|---' .--------| Gnd 470 ohm
There are several limitations in current SerialUPDI/AVRDUDE integration, There are several limitations in current SerialUPDI/AVRDUDE integration,
listed below. listed below.
At the end of each run there are fuse values being presented to the user. Currently available devices support only UPDI NVM programming model 0, 2
For most of the UPDI-enabled devices these definitions (low fuse, high 3 and 5, but there is also experimental implementation of model 4 - it
fuse, extended fuse) have no meaning whatsoever, as they have been has been tested only on a single device, so issues with other devices are
simply replaced by array of fuses: fuse0..9. Therefore you can simply expected. Full NVM v4 mode support will be provided once the hardware is
ignore this particular line of AVRDUDE output. widely available.
Currently available devices support only UPDI NVM programming model 0
and 2, but there is also experimental implementation of model 3 - not
yet tested.
One of the core AVRDUDE features is verification of the connection by One of the core AVRDUDE features is verification of the connection by
reading device signature prior to any operation, but this operation reading device signature prior to any operation, but this operation