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.

TSC2004: Is /PINTDAV pin level set from "L" to "H" automatically when register data is read out via I2C interface?

Part Number: TSC2004

 Hello guys,

 One of my customers is evaluating TSC2004, a touch screen controller for their new products.

 They have several questions as the follows.

 Could you please give me your answers or comments?

 Q1. Is /PINTDAV pin level set from "L" to "H" automatically when register data is read out via I2C interface?

       Or does the host need to write any data to TSC2004 via I2C interface to set /PINTDAV to "H" level? 

 Q2. Is there any time limitation between /PINTDAV=H -> L and I2C data reading out?

 Your reply would be much appreciated.

 Best regards,

 Kazuya.

 

  • Hello Kazuya,

    Please find my answers below:

    Q1: Yes, the transition is does automatically. This pin is used as a flag/status pin and will transition HI/LOW depending on how the pin is configured.

    Q2: This is a good question and not one I have an answer for. There is no information in the Data Sheet regarding timing for HI --> LOW transition to I2C data read so I cannot really comment on this. 

    Regards,

    Aaron

  •  Hello Arron,

     Thank you very much for the prompt reply.

     The customer confirmed that /PINTDAV level was changed from L to H when register data was read out via I2C interface right away

     (0.5ms~1ms) after /PINTDAV was changed from H to L.

     But /PINTDAV level was not changed from L to H (=keep L) when register data was read out via I2C interface with about 60ms

    delay after /PINTDAV changed from H to L.

     They want to know whether this phenominon is a normal operation of TSC2004 or not.

     Could you please give me your comment?

     Thank you again and best regards,

     Kazuya. 

       

  • Hello Kazuya, 

    Was this delay intentionally added to check limits? If so, I am not for certain but would not expect that long of a delay to be normal.

    Regards,

    Aaron

  •  Hello Aaron,

     The delay was happened by processing time of other interrupt routine. The delay is not added intentionally and they can't remove the interrupt routin

    because the routime is higher priority than /PINTDAV falling signal.

     The customer wants to know whether this phenomenon (/PINTDAV level was not changed from L to H thogh data is read out via I2C) is

    normal operation of this device or not. Also they want to know any countermeasure to change /PINTDAV level from L to H level.

     Could you please give me your commet?

     Thank you very much and best regards,

     Kazuya.    

  •  Hello Aaron,

     Could you please give me your comment?

     Thank you and best regards,

     Kazuya.

  • Hello Kazuya,

    Apologies for the delayed response. Unfortunately, I cannot say for certain if that much of a delay time is too long. These devices were made some time ago and the original designers of the device are unfortunately no longer available. If the level transition works as expected with minimal delay, then I would go ahead and assume that the delay of 60ms is far too long. 

    Regards,

    Aaron