Document fix for avrftdi bit number should start with 0
This resolves https://github.com/avrdudes/avrdude/issues/369
This commit is contained in:
parent
6b95f9d181
commit
368bad5ca0
|
@ -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
|
programmers communicate through the USB, using @code{libusb} as a
|
||||||
platform abstraction layer.
|
platform abstraction layer.
|
||||||
The avrftdi adds support for the FT2232C/D, FT2232H, and FT4232H devices. These all use
|
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
|
the MPSSE mode, which has a specific pin mapping. Bit 0 (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
|
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
|
are only supported on interface A, but the H parts can be either A or B (specified by the
|
||||||
usbdev config parameter).
|
usbdev config parameter).
|
||||||
The STK500, STK600, JTAG ICE, and avr910 contain on-board logic to control the programming of the target
|
The STK500, STK600, JTAG ICE, and avr910 contain on-board logic to control the programming of the target
|
||||||
|
|
Loading…
Reference in New Issue