-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add Storage Operation Commands #374
Conversation
nanoFramework.Tools.DebugLibrary.Shared/WireProtocol/Commands.cs
Outdated
Show resolved
Hide resolved
- Add class to support the command in Wire Protocol.
- Add class to support the command in Wire Protocol.
- Also added/improve Intellisense comments.
- Add offset field to support memory access storage. - Add Intellisense comments.
- Logic simplification as all operations require sending the file name and operation code. - Add Intellisense comments.
- Aligning with changes in command. - Rename methods to add Storage for clarity. - AddStorageFile now instantiates a new Monitor_StorageOperation for each operation. - Add Intellisense comments to methods.
- Add new property to store file name as string. - PrepareForSend now assembles data buffer with file name and data.
fc273ee
to
e4ba0de
Compare
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.
LGTM!
The only thing missing here is the progress report, just like the other ones that are using during deployment to provide feedback to user. It's probably worth adding it now as each release of the debugger touches a lot of dependents... |
For this, the 2 new functions are either success either failure, I feel it's enough to have. You want something that shows progress on chunk upload? |
Depends on how large the files are, of course. But there will always by time involved and, just like we do with all the rest we should provide feedback to the user. |
- Add new parameters to allow report progress when executing operations. - Rework processing of reply to properly report errors. - Rework also about processing reply when target doesn't have access to storage, so this is reported properly.
All seems good to me. Thanks for moving forward the code! |
Thank YOU for getting all this started. |
Description
Motivation and Context
How Has This Been Tested?
On a real ESP32 device
Screenshots
Types of changes
Checklist: