From: Yegor Yefremov
---
src/ftdi.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/src/ftdi.c b/src/ftdi.c
index 0a7fb27..3a51b26 100644
--- a/src/ftdi.c
+++ b/src/ftdi.c
@@ -83,7 +83,7 @@ static void ftdi_usb_close_internal (struct ftdi_context
*ftdi)
From: Yegor Yefremov
User area begins after the serial number string. Hence, use free_end
to specify the end of the necessary data like producer, serial number
strings as also PNP bits.
Treat both generated data area and strings area violations as errors.
---
src/ftdi.c | 15 +--
1
From: Yegor Yefremov
Handle user_data the same way as the main EEPROM buffer. Copy buffer
instead of assigning a pointer in ftdi_set_eeprom_user_data(). This
is required because if used from Python, the input buf is not
available as soon as the ftdi_set_eeprom_user_data() exits.
---
src/ftdi.c
On Tue, Aug 1, 2023 at 11:44 AM Yegor Yefremov
wrote:
>
> On Mon, Jul 31, 2023 at 1:53 PM Yegor Yefremov
> wrote:
> >
> > I want to write ca. 25 bytes as user data (my FTDI chips are FT2232,
> > FT4232 and FTX). What is my strategy to calculate the user_data_addr?
> >
> > If I set EEPROM defaults
From: Yegor Yefremov
User area begins after the serial number string. Hence, use free_end
to specify the end of the necessary data like producer, serial number
strings as also PNP bits.
---
src/ftdi.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/ftdi.c b/sr
From: Yegor Yefremov
Handle user_data the same way as the main EEPROM buffer. Copy buffer
instead of assigning a pointer in ftdi_set_eeprom_user_data(). This
is required because if used from Python, the input buf is not
available as soon as the ftdi_set_eeprom_user_data() exits.
---
src/ftdi.c