Pulse count timing impacted by Bluetooth GAP and A2DP
Pulse count timing impacted by Bluetooth GAP and A2DP
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.
Who is online
Users browsing this forum: No registered users and 111 guests