Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict of WiFi/Bluetooth and ADC2 #3

Open
IoTThinks opened this issue Sep 27, 2019 · 1 comment
Open

Conflict of WiFi/Bluetooth and ADC2 #3

IoTThinks opened this issue Sep 27, 2019 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@IoTThinks
Copy link
Owner

IoTThinks commented Sep 27, 2019

Suggested solution
Need to change GPIO2 and 4 into GPIO32 and 33 in ADC1 to resolve the conflict.
To test GPIO32 and 33 to confirm.

Reference:
The ADC driver API supports ADC1 (8 channels, attached to GPIOs 32 - 39), and ADC2 (10 channels, attached to GPIOs 0, 2, 4, 12 - 15 and 25 - 27). However, the usage of ADC2 has some restrictions for the application:

@IoTThinks IoTThinks added the bug Something isn't working label Sep 27, 2019
@IoTThinks IoTThinks added this to the v1.3 milestone Sep 27, 2019
@IoTThinks IoTThinks added enhancement New feature or request and removed bug Something isn't working labels Nov 19, 2019
@IoTThinks
Copy link
Owner Author

IoTThinks commented Nov 19, 2019

Target for next release of hardware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant