This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

where to find materials of optical fingerprint sensor (Tooan OP-100N)

I am dealing with code of "TA_hal_sccb_write".But I don't know detail information of registers in the device which connected to the core board.For example ,I don't know what does the following parameters mean:  TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x18,431>>3); 

  • Hi,

    Which software and hardware platform ( processor, board ) being used?

    Please provide more information.

    Regards,

    Shankari.

  • The part number for the FDK is TMDXBDKFP5515.  1 core board (30 mm x 30 mm) based on C5515 low-power DSP

    & 1 extension board (78 mm x 30 mm) for power supply, communication and user interaction.Using CCS v4.The code is in FDK_demo project ,which is called in the function "TA_hal_gpio_read_cmos_image". Is it enough?

  • Hi,

    For help with the source code, you need to contact TooAn (FDK 3rd party). Please contact Weiqing Dong (dongweiqing@tooan.cn) or  Xiaohai Zhang (zhangxiaohai@tooan.cn).

    Regards,

    Rahul Nair

  • Hi,
    These emails seem not to exist. I have gotten 3 responses from Mail-Deamon for failed delivery.

    Please assist me obtain the correct materials for OP-100N. I purchased it a few months ago but am still stuck. The resources available on the forum are for HV7131R but the register descriptions in the data sheet do not match those used in the code provided in the CD.

    Hope to at least get a response
  • Where you purchase it from? Sorry but this has always been supported by TooAn.
    Regards.
  • I have forwarded your questions to zhaoxu@tooan.cn

    Refer to the register mapping in the HV7131R datasheet:
    http://html.alldatasheet.com/html-pdf/102699/ETC/HV7131R/654/11/HV7131R.html

    Around 2011 the optical sensor was revised and changed numbers from OP-100N to OP-100R. I wonder if you are seeing source code for one but have hardware for the other. However, I couldnt find out any differences in the optical sensor used - looks like HV7131R on both...

    Hope this helps,
    Mark
  • I purchased it from DigiKey mid 2014 and it came with OP-100N
  • the source code provided with the FDK has the following line inside the TA_hal_gpio_read_cmos_image function

    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x18,431>>3);//horizontal end MSB

    From the data sheet,  register 0x18 does not exist.

    Similarly, inside the TA_hal_sccb_Openfunction

    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x12,1<<7);//reset all register

    From the data sheet, register 0x12 is for column start address upper byte (CSAU)

    As you can see, the data sheet you suggested does not have the same register definitions as the code in the FDK. I have tried looking around at the other variants of MagnaChips but none has similar definitions. I bought this FDK from DigiKey mid 2014 so I expected it to be the latest one.

  • This older software does not write to reg 0x18 - and seems to match the datasheet.

    TA_hal_sccb.c replaced TA_demo_iic.c in the updated FDK software.

    So something must have changed with the sensor if it now accepts writes to 0x18.

    We should sync with Tooan to find the correct software for your hardware.

    Does this attached software work with your hardware version?

    demo_2.0_ccs4.zip

    Hope this helps,
    Mark

  • Hello,

     Thank you for your help. Unfortunately, when I try out the new code which you have given me I do not see any fingerprint image in it. Here is a screenshot:

    As  you can see the image does not look like okay. I setup the image analyzer earlier using the guide here

    I have tried contacting Tooan to at least get some assistance as other forums posts have suggest but I only get "Mail-Daemon" responses from the following emails:

    dongweiqing@tooan.cn

    zhangxiaohai@tooan.cn

    business@tooan.cn

    zhaoxu@tooan.cn

    As such I will really appreciate if you could sync with them. Just in case you need a copy of the FDK_Demo I received when I purchased my kit, here it is:

    FDK_Demo.zip

  • Hello,

    I got in touch with TooAn.

    The updated contact is zkai@tooan.cn with zhaoxu@tooan.cn CC'ed.

    Post a detailed summary in the email.

    Hope this helps,
    Mark
  • Hello,

    Thank you for your help. Again, I appreciate. I have since sent an email to them so I await a response an time.

    Thank you

  • Hi,

    They sent me the attached datasheet for the sensor. I see that there is information for address 0x18.


    coms datesheet.pdf

    Hope this helps,
    Mark

  • Hello,
    Sorry for the late response.
    Thank you for our help and for posting the datasheet here. I have never received any response from Tooan and I always get mail daemon responses. I should not be needing to contact them anymore.

    Now I am better placed to use the evaluation board I bought.

    I had noted about 2 weeks ago that the register definitions are very similar to OmviVision cameras. May be because is uses the SCCB interface. I had suspected that the internal camera module would have been OV2866 or OV6628 going by the values read from registers 0x0A and 0x0B. But none of which seemed to exist online.
  • Hi,

    Sorry to be back again.

    The datasheet you attached shows that the sensor array is 352 x 288. However, in the code given the Horizontal End (in registers 0x18 and 0x32) is set to 493 in one case as shown below

    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x18,493>>3);//horizontal end MSB
    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x17,141>>3);//horizontal start MSB
    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x32,(141&0x7)|((493&0x7)<<3));//horizontal LSB
    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x1a,150>>2);//vertical end MSB
    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x19,6>>2);//vertical start MSB
    TA_hal_sccb_write(SCCB_SENSOR_ADDR,0x03,(6&0x3)|((150&0x3)<<2));//vertical LSB
    

    How can the sensor be reading from 141 to 493 yet the sensor array is 352 pixels wide?

    Even if the code works, doesn't this violate the datasheet you gave?

    Kindly enlighten.