Open elCaxper opened 11 months ago
This happens when you try reading data before initializing the device. To fix it, you need to plug in the device into Windows machine, let the windows driver do its thing, and then plug it back into your linux box. Then, run
sudo ./ft9201_util /dev/fpreader0
and you should be able to capture the image.
However, even in the broken state, you should see one Data ready: 0x01
, followed by zeroes:
ft9201 5-2.2:1.0: Data ready: 0x01
ft9201 5-2.2:1.0: Read AFE at index 0x30: 0x00000000
ft9201 5-2.2:1.0: 0x30 translate data: 0x00
ft9201 5-2.2:1.0: Copied: 0, Filled: 0
ft9201 reading 0
ft9201 5-2.2:1.0: Data ready: 0x00
ft9201 5-2.2:1.0: Copied: 0, Filled: 0
ft9201 reading 0
ft9201 5-2.2:1.0: Data ready: 0x00
ft9201 5-2.2:1.0: Copied: 0, Filled: 0
The data is not streaming but is one-off instead so you should get data ready 0x01 immediately after you put your finger on the scanner, and zeroes until you remove your finger and put it again.
This is now tracked in #10
I have compiled the driver and loaded it but when I try to read data from the endpoint created in /dev/fpreader0 I don't get any data.
insmod ft9201.ko
[ 1688.853717] usbcore: registered new interface driver ft9201
When the device is connected:
./ft9201_util /dev/fpreader0
cat /dev/fpreader0
Uname -a
5.15.0-88-generic #98-Ubuntu
In the logs I see that all values read are zeros, why can this happen? Could it be a different firmware version of the device?