[fprint] elan patch + poc 0x903 and 0x0C03

Sat Jan 27 15:38:48 UTC 2018

Hi,

Just for the case that the output of elanfp.c is still relevant:

                Device with vid 4f3 pid c1a found.

Config number is 1

CMD RESET sent

CMD Fuse Load sent

CMD VERSION sent

FP Bridge FW Version 1.66

CMD Get Image Size sent

Width x Height = 64x144

CMD Get Calibration Mean sent

calibration mean value: 7562 (0x1d8a)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 7562 (0x1d8a)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 7562 (0x1d8a)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 7562 (0x1d8a)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 7562 (0x1d8a)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 16383 (0x3fff)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 16383 (0x3fff)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 16383 (0x3fff)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 16383 (0x3fff)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 16383 (0x3fff)

CMD CALIBRATION sent

Calibration Status: 0x1

CMD STATUS sent

Status: 0xff

CMD Get Calibration Mean sent

calibration mean value: 2 (0x2)

CMD Wait For Finger sent

Received 0xa0

CMD Get Image sent

Received 18432

It’s true that I said that 4031 was called before 403F, which actually was the case - here are my notes regarding this:

-> 4031                                                  ?

-> 403F                                                  Get Pre-Scan

<- 55                      1.3.3                      Object

-> 4031                                                  ?

-> 0009                                                  Get Image Data

<- ?                         1.3.2                      Image Data

-> 0009                                                  Get Image Data

<- ?                         1.3.2                      Image Data

-> 0009

...

-> 4031

-> 403F

<- 55                      1.3.3

-> 4031

-> 0009

<- ?                         1.3.2

...

-> 4031

-> 403F

<- 55                      1.3.3

...

-> 4031

-> 0009

<- ?

-> 000b

-> 0009

<- ?

-> 4031

...

-> 0009

<- ?

-> 000b                                                 Stop

You say that it works – so haw exactly can I use it then? I guess it won’t do to simply install fprint from the package library, as it won’t have the newest driver for my device?

Regards

Timo

-----Original Message-----
From: Sebastien Bechet [mailto:sebastien.bechet at osinix.com] 
Sent: Saturday, 27 January 2018 15:43
To: Meta Colon <timo at teemze.de>; Igor Filatov <ia.filatov at gmail.com>
Cc: Hans de Goede <hdegoede at redhat.com>; konachan.700 at gmail.com; fprint at lists.freedesktop.org
Subject: Re: [fprint] elan patch + poc 0x903 and 0x0C03

Hello Timo,

Le samedi 27 janvier 2018 à 13:40 +0100, Meta Colon a écrit :

> fp:debug [find_supporting_driver] driver elan supports USB device

> > 04f3:0c1a

> > elan:debug [activate_run_state] FW ver 1.66 elan:debug 

> > [activate_run_state] sensor dimensions, WxH: 144x64

Ok, I record your informations in README.md.

> > elan:debug [elan_run_cmd] 4031

> > elan:debug [elan_run_cmd] skipping for this device

It seems to me you said 4031 was called before 403F in your windows usb trace?

> I guess this means that it works?

Yes.

> elanfp.c however had the output (after I properly installed / executed 

> it):

>     Device with vid 4f3 pid c1a found.

>     Error 5

> Which seems to mean, that the reader couldn't be opened?

You can run it with root account. But elanfp.c are not important now.

Thank you for your log with Igor driver.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fprint/attachments/20180127/c0df221c/attachment-0001.html>