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.

Storing fingerprint features to memory and accessing the extension board button inputs for fingerprint development kit

Hello, 

I am working with the provided code for the  FDK C5515 and would like to store the features extracted from the into a permanent memory location (turning off FDK will not erase the stored features). The user guides do not provide enough information in this area. If possible it would like to store these features in the same location that the installed program (program that the FDK comes packaged with) stores the 50 fingerprints.

Also, I am trying to access the buttons found on the extension board. From the schematics provided, it seems these input signals (labeled: match, enroll, and del_all) are connected to the extension board's 16-bit Ultra-Low-Power Microcontroller (msp430f2111IDW). I cannot determine where these are going

Thank you in advance for any assistance you can provide me.

  • Hi Huy,

    The FDK stores features in a SPI flash(W25X40A), you can find datasheet in the link. If they don't give out the driver source, you have to write it yourself. DSP uses SPI interface to communicate with the flash, you may need Ti's CSL on SPI.

    About the second question, the buttons do connect to  a msp430. It controls the button and  speaker directly. And the DSP communicates with the MSP430 via UART(TX and RX). If Ti doesn't give out the souce of the MSP430, we have to write the program ourselves. The programming of the MSP430 need the BSL(J7) interface on the extension board, which has not solder pins on it.

    I think it would be helpful if we,and those who have purchased C5515 FDK, could share some programming experiences.

    My email: sunoldman@foxmail.com

     

    Regards,

    Yang

  • Hello Yang,

    Thanks for commenting back so soon. I am new to DSP programming and having a hard time programming the FDK. I have gone as far as loading the demo program to the FDK through an XDS100v2. I did  modify the demo code to beep for 5 seconds and output a high on one of the GPIO ports at the same time. This is needed for my senior design project where the outputted high will trigger a lock to open. The only problems I have now are storing the features to SPI flash and interfacing with the buttons to set different modes.

    I thank you for sending me these documents. I am sure they shall be very helpful in completing my project. Have you been able to store the features in the SPI? I am having trouble understanding how to properly use it.