ESP32-S2: Initialize touch in proper order #4021
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rework order of touch peripheral initialization code. 048ca2a changed it around slightly. This apparently made the calibration be wrong on pins with any length of trace or wire connected to them, causing the
TouchIn.raw_value
to be its max 65535, all the time.. Thanks to @microdev1 for help in debugging: the microS2 did not show this problem, which was a clue, because it's a very small board with short traces. When @microdev1 connected a wire to one pin, the problem did appear on that pin.Tested with
TouchIn
and alsoTouchAlarm
. Both work now.Note that
TouchAlarm
does not work on the MagTagD10
pin, probably because it has a protection Zener and resistor permanently attached.