-
It looks like newer FTDI devices use 512 byte packets rather than 64. The FTDI Class currently assumes packets that have repeats of 2 bytes of status and 62 bytes of data. The newer FTDI devices go 2…
-
Hi,
When calling `close` (or `terminate` for I2cController) on an instance associated with a device that have been physically disconnect the following exceptions are thrown:
```
Traceback (most…
daoo updated
2 months ago
-
While looking into #201, I found a wrong serial number '5' reported for a FTDI 2232D which does not have a serial number (due to not having an external EEPROM fitted):
```
>cargo run --example lis…
-
Hi,
I was testing your code with the following setup and it did not work.
- raspbery PI 2B,
- vivado 2018.2
- arty35T FPGA with FTDI (Bus 001 Device 007: ID 0403:6010 Future Technology Devices I…
-
If you getting `EOVERFLOW` out of nowhere - be aware of this line:
https://github.com/bm16ton/ft2232-mpsse-i2c-spi-kern-drivers/blob/923b7059795bcba5d82a3ae0a9fc7de93c20df03/i2c-ftdi/i2c-ftdi.c#L45…
-
**Summary:**
I'd like to get nmea messages - and other types of logs supported by GPStest - over USB serial connection - for example FTDI connected to USB - to be able to analyze through external …
-
Hi, I am encountering a strange issue.
I have two discrete (separate) FT232H devices, here is the output of ftdi_urls.py -d -v:
```
Available interfaces:
ftdi://ftdi:232h:1/1 ()
…
-
It would be nice to have an optional cargo build feature to allow `Device` information and `Event` data to be easily serialized using serde.
If you're interested, I could do the work and put up a P…
-
I flashed it successfully [on a f042 dev board](github.com/brainstorm/bbtrackball-rs), but I wonder which interface config to use on OpenOCD given the USB VID:PID?:
```
$ lsusb
(...)
Bus 020 Dev…
-
This is just to state that I am able to use `pyftdi` as an ordinary user on my Arch Linux box without any `udev` tinkering.
This means (to illustrate what I mean by "I am able to use"):
1. That…