Pulse count timing impacted by Bluetooth GAP and A2DP
Posted: Thu Nov 22, 2018 2:58 pm
I am seeing erratic behavior with the pulse count on one of the pins when I startup the bluetooth stack and connect to a speaker via A2DP. Why is this happening? I am using the pcnt_get_counter_value function to get the count of a signal coming in on pin 4.