Sensor do not response when touched.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
AmRa_4297511
Level 1
Level 1

I would like to ask about software specification.

Currently I am facing a problems while using CY8CMBR3108.

Problem : sensors do not respond when touched.

Can some members give advice on how to use pin that have multiplex function like below 3pins.

  1. Pin 1 : CS0/PS0 want to use as CS0 -> OK.
  2. Pin 2 : CS1/PS1 want to use as CS1 -> OK.
  3. Pin12: CS2/GUARD want to use as CS2 -> OK.
  4. Pin 9 : CS5/GPO1 want to use as CS5 -> not response.
  5. Pin10: CS6/GPO2 want to use as CS6 -> not response.
  6. Pin11: CS7/GPO3 want to use as CS7 -> not response.

Below is the value of configuration settings for the related register in order to use pin 9,10,11 as CSx.

SENSOR_EN:0xE7 (Enable CS7, CS6, CS5, CS2, CS1, CS0)

GPO_CFG : 0x00

SPO_CFG : 0x14

Is there any register I miss to set?

I used register BUTTON_STAT, and LATCHED_BUTTON_STAT to read the button status touched/not touched.

Currently referring to below specification:

  1. CY8CMBR3xxx Programming Specification
  2. CY8CMBR3xxx Register TRM
  3. CY8CMBR3xxx CapSense Design Guide
0 Likes
1 Solution
BragadeeshV
Moderator
Moderator
Moderator
First question asked 1000 replies posted 750 replies posted

Hi AmRa_4297511​,

The configuration registers looks fine. There could be multiple reasons why your button is not responding to touch.

1. Cp of sensor exceeded acceptable range of 5 - 45 pF. We recommend you to perform a system diagnostics test on your device.

To do so:

a) Enable System diagnostic feature by enabling System diagnostics in DEVICE_CFG1  register (0x4E).

Note: Whenever a configuration register (0x00 - 0x7E) is modified, the CRC needs to be updated and a stored in the flash. Then the device has to be reset.

To do this refer to the section Custom commands entered in the BCP tool in Pg 69 of MBR3 CapSense design guide.

https://www.cypress.com/file/46366/download

b) Read the TOTAL_WORKING_SNS (0x97) register to see if any sensor has failed the test.

c)  Read the SNS_CP_HIGH (0x98) register to see if the sensors has a Cp greater than 45 pF

d) Read the SNS_VDD_SHORT (0x9a) and SNS_GND_SHORT (0x9c) register to see if the sensors are short to VDD or to GND.

2. If the system diagnostics test is passed, then there could be issue with the sensitivity. Try increasing the sensitivity and check the sensor performance.

3. There could be issues with the automatic threshold feature (if enabled) or the manual threshold values you have entered. Please use the Debug_Sensor_ID register to monitor the raw counts and difference counts of each of the sensors and check if you see any valid data in them.

For example , CS7 is not working:

a) Set DEBUG_SENSOR_ID (0xdc) to 7

b) Read the DEBUG_DIFFERENCE_COUNT0 and DEBUG_RAW_COUNT0 register and see if you see any valid data.

c) Set the finger threshold register according to the difference count you obtained.

4. Is it possible for you to send the configuration data (128 bytes)? We will try to check if there is anything is not correct if the above three suggestions didn't work.

5. Is it also possible for you to use EZ - Click software to generate the configuration data instead of you trying to manually enter the values.  Ez- Click if a very simple tool provided by Cypress to generate the config file (128 bytes) that can be added to your host program.

https://www.cypress.com/documentation/software-and-drivers/ez-click-20

6. If you have miniprog3 usb-i2c bridge, you can directly view the sensor data in the system diagnostics tab of Ez- Click

Regards,

Bragadeesh

Regards,
Bragadeesh

View solution in original post

0 Likes
3 Replies
BragadeeshV
Moderator
Moderator
Moderator
First question asked 1000 replies posted 750 replies posted

Hi AmRa_4297511​,

The configuration registers looks fine. There could be multiple reasons why your button is not responding to touch.

1. Cp of sensor exceeded acceptable range of 5 - 45 pF. We recommend you to perform a system diagnostics test on your device.

To do so:

a) Enable System diagnostic feature by enabling System diagnostics in DEVICE_CFG1  register (0x4E).

Note: Whenever a configuration register (0x00 - 0x7E) is modified, the CRC needs to be updated and a stored in the flash. Then the device has to be reset.

To do this refer to the section Custom commands entered in the BCP tool in Pg 69 of MBR3 CapSense design guide.

https://www.cypress.com/file/46366/download

b) Read the TOTAL_WORKING_SNS (0x97) register to see if any sensor has failed the test.

c)  Read the SNS_CP_HIGH (0x98) register to see if the sensors has a Cp greater than 45 pF

d) Read the SNS_VDD_SHORT (0x9a) and SNS_GND_SHORT (0x9c) register to see if the sensors are short to VDD or to GND.

2. If the system diagnostics test is passed, then there could be issue with the sensitivity. Try increasing the sensitivity and check the sensor performance.

3. There could be issues with the automatic threshold feature (if enabled) or the manual threshold values you have entered. Please use the Debug_Sensor_ID register to monitor the raw counts and difference counts of each of the sensors and check if you see any valid data in them.

For example , CS7 is not working:

a) Set DEBUG_SENSOR_ID (0xdc) to 7

b) Read the DEBUG_DIFFERENCE_COUNT0 and DEBUG_RAW_COUNT0 register and see if you see any valid data.

c) Set the finger threshold register according to the difference count you obtained.

4. Is it possible for you to send the configuration data (128 bytes)? We will try to check if there is anything is not correct if the above three suggestions didn't work.

5. Is it also possible for you to use EZ - Click software to generate the configuration data instead of you trying to manually enter the values.  Ez- Click if a very simple tool provided by Cypress to generate the config file (128 bytes) that can be added to your host program.

https://www.cypress.com/documentation/software-and-drivers/ez-click-20

6. If you have miniprog3 usb-i2c bridge, you can directly view the sensor data in the system diagnostics tab of Ez- Click

Regards,

Bragadeesh

Regards,
Bragadeesh
0 Likes

Hi BragadeeshV_41

Thank you for your suggestion.

I done trying no.1 and 3 regrading the System diagnostic.

Yes found error as below, currently checking our circuit diagram.

TOTAL_WORKING_SNS = 0x83 (SYSD_ERR: 1 error detected, SENSOR_COUNT:3 sensors passed the test)

SNS_GND_SHORT = 0x0008 ( sensor3 short to GND indicator, ---> is it ok to ignore this error because we are not using this CS3 and GND it?)

Here I share my configuration data.

>>4. Is it possible for you to send the configuration data (128 bytes)? We will try to check if there is anything is not correct if the above three suggestions didn't work.

const unsigned char CY8CMBR3108-LQXI_configuration[128] = {

    0xE7u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x80u, 0x80u, 0x80u, 0x7Fu,

    0x7Fu, 0x80u, 0x80u, 0x80u, 0x00u, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x05u, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x80u,

    0x05u, 0x00u, 0x00u, 0x02u, 0x00u, 0x02u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x1Eu, 0x1Eu, 0x00u,

    0x00u, 0x1Eu, 0x1Eu, 0x00u, 0x00u, 0x00u, 0x01u, 0x01u,

    0x00u, 0xFFu, 0xFFu, 0xFFu, 0xFFu, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x14u, 0x03u, 0x01u, 0x68u,

    0x00u, 0x37u, 0x01u, 0x00u, 0x00u, 0x0Au, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u,

    0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0x00u, 0xCEu, 0x90u

};

Thank you and best regards,

Amirah.

0 Likes

Hi AmRa_4297511​,

Have you not disabled CS3 button? Also is your Cp within limits?

If there are no errors, please use a data logger to plot Raw Counts, baselines and difference counts as suggested in point 3 and send us the log.

Regards,

Bragadeesh

Regards,
Bragadeesh
0 Likes