-
Notifications
You must be signed in to change notification settings - Fork 24
feat(remote_debug): Add new RemoteDebug component for WiFi GPIO/ADC and logfile access
#589
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
Conversation
…ter handle input/output and lables for adc and io; update debug to use espp adc
|
✅Static analysis result - no issues found! ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 18 out of 18 changed files in this pull request and generated 20 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Description
Motivation and Context
Remote access and control over an esp32 device is often useful for debugging and monitoring. This component provides a way to remotely log data, monitor system status, and interact with the device over a network connection.
How has this been tested?
Build and run
remote_debug/exampleon QtPy ESP32-S3 and ensure that the remote debug server starts correctly, and that data can be sent and received as expected.Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):
remote-monitoring-2.mp4
Types of changes
Checklist:
Software
.github/workflows/build.ymlfile to add my new test to the automated cloud build github action.