-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
D500 DFU - cleaning d400 fw update code, avoid stucking of d500 w/o dfu monitoring #12964
Conversation
void ds_d500_update_device::dfu_manifest_phase(const platform::rs_usb_messenger& messenger, rs2_update_progress_callback_sptr update_progress_callback) const | ||
{ | ||
// measuring the progress of the writing to flash (when enabled by FW) | ||
if (!wait_for_manifest_completion(messenger, RS2_DFU_STATE_DFU_MANIFEST, std::chrono::seconds(200), update_progress_callback)) |
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.
Should we lower the timeout?
This will also be the timeout for D400 devices that only should take several seconds?
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.
The timeout is around 1.5 times the time it takes.
It is not related to the D400 devices, this code is only for D500 devices.
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 - consider the comments, your call..
41c47c6
into
IntelRealSense:development
Tracked by: RSDEV-1224 - second PR