-
```
What steps will reproduce the problem?
1. Open in I2C mode
2. Issue start condition (call Start() method)
I found a bug in Start() method.
See the attached patch file.
```
Original issue report…
-
```
What steps will reproduce the problem?
1. Open in I2C mode
2. Issue start condition (call Start() method)
I found a bug in Start() method.
See the attached patch file.
```
Original issue report…
-
```
What steps will reproduce the problem?
1. Open in I2C mode
2. Issue start condition (call Start() method)
I found a bug in Start() method.
See the attached patch file.
```
Original issue report…
-
```
What steps will reproduce the problem?
1. Open in I2C mode
2. Issue start condition (call Start() method)
I found a bug in Start() method.
See the attached patch file.
```
Original issue report…
-
```
What steps will reproduce the problem?
1. Open in I2C mode
2. Issue start condition (call Start() method)
I found a bug in Start() method.
See the attached patch file.
```
Original issue report…
-
```
What steps will reproduce the problem?
1. Open in I2C mode
2. Issue start condition (call Start() method)
I found a bug in Start() method.
See the attached patch file.
```
Original issue report…
-
```
What steps will reproduce the problem?
1. Open in I2C mode
2. Issue start condition (call Start() method)
I found a bug in Start() method.
See the attached patch file.
```
Original issue report…
-
in /pyftdi/pyftdi/ftdi.py the 'type' property does not support custom FTDI devices.
FTDI gave me a product ID number I can use with my board and pyftdi does not recognize it.
In order to fix it how …
-
-