Skip to content

run_5503.py stuck on the second mcu_switch_to_fdt_up #43

@wanywhn

Description

@wanywhn

UPDATE:
driver should work and can capture&generate correct image, but it seems always mismatch when verify.

hi, i have a 27c6:5503 device.
i run with run_5503.py and stuck on mcu_switch_to_fdt_up like bellow( and ctrl + c can't stop the program)

Please remove your finger from the sensor mcu_switch_to_fdt_up(b'\x0e\x01\x8b\x00\x84\x00\x8c\x00\x88\x00\x80\x95\x80\x89\x80\x99\x80\x8a\x80\x8d\x80\x8d') mcu_switch_to_fdt_up(b'\x0e\x01\x8b\x00\x84\x00\x8c\x00\x88\x00\x80\x9b\x80\x8e\x80\xa2\x80\x90\x80\x9f\x80\xa8')

but i can see fingerprint-0.pgm and clear-*.pmg generate ok, it show my fingerprint.

i try to comment mcu_switch_to_fdt_up(b'\x0e\x01\x8b\x00\x84\x00\x8c\x00\x88\x00\x80\x9b\x80\x8e\x80\xa2\x80\x90\x80\x9f\x80\xa8') and it seems work fine and exit normally as bellow
Please remove your finger from the sensor mcu_switch_to_fdt_up(b'\x0e\x01\x8b\x00\x84\x00\x8c\x00\x88\x00\x80\x95\x80\x89\x80\x99\x80\x8a\x80\x8d\x80\x8d') mcu_switch_to_fdt_down(b'\x0c\x01\x8b\x00\x84\x00\x8c\x00\x88\x00\x80\xba\x80\xaf\x80\xba\x80\xb0\x80\xb6\x80\xab', False) query_mcu_state(b'\x01\x002', True)

so
what does the second mcu_switch_to_fdt_up which send byte ending with \x80\xa8 mean?
is this nessary?
and since it works fine ,whta the next step should i do to let the fprintd work(use) with this divece?

thinks for the great works!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions