From 368bad5ca0f7de612d484e661418dd44df8c7706 Mon Sep 17 00:00:00 2001
From: mcuee <xiaofanc@gmail.com>
Date: Wed, 11 Jan 2023 14:50:24 +0800
Subject: [PATCH] Document fix for avrftdi bit number should start with 0

This resolves https://github.com/avrdudes/avrdude/issues/369
---
 src/doc/avrdude.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/doc/avrdude.texi b/src/doc/avrdude.texi
index 9e2e3116..444bde23 100644
--- a/src/doc/avrdude.texi
+++ b/src/doc/avrdude.texi
@@ -223,8 +223,8 @@ The STK600, JTAG ICE mkII/3, AVRISP mkII, USBasp, avrftdi (and derivatives), and
 programmers communicate through the USB, using @code{libusb} as a
 platform abstraction layer.
 The avrftdi adds support for the FT2232C/D, FT2232H, and FT4232H devices. These all use 
-the MPSSE mode, which has a specific pin mapping. Bit 1 (the lsb of the byte in the config
-file) is SCK. Bit 2 is SDO, and Bit 3 is SDI. Bit 4 usually reset. The 2232C/D parts
+the MPSSE mode, which has a specific pin mapping. Bit 0 (the lsb of the byte in the config
+file) is SCK. Bit 1 is SDO, and Bit 2 is SDI. Bit 3 usually reset. The 2232C/D parts
 are only supported on interface A, but the H parts can be either A or B (specified by the
 usbdev config parameter).
 The STK500, STK600, JTAG ICE, and avr910 contain on-board logic to control the programming of the target