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

Introduce delay in "sfputil firmware run" between running firmware and updating the cable firmware version info #51

Closed
wants to merge 2 commits into from

Conversation

stephenxs
Copy link
Owner

@stephenxs stephenxs commented Nov 2, 2024

What I did

Introduce a delay in "sfputil firmware run" between running firmware and updating the cable firmware version info.

The flow of "sfputil firmware run" is the following

  1. Issue CMIS CDB command "run cable firmware" (0x109) to the cable to switch to the inactive firmware.
  2. Fetch the version of the cable's running firmware

It takes time for the cable to get ready after switching firmware, which can cause an error message in step 2.
We introduce a CLI option to specify a delay between step 1 and 2 to avoid error message.

How I did it

How to verify it

Previous command output (if the output of a command-line utility has changed)

New command output (if the output of a command-line utility has changed)

Signed-off-by: Stephen Sun <stephens@nvidia.com>
@stephenxs stephenxs force-pushed the extend-delay-run-firmware branch from 22d73b5 to e48f1b7 Compare November 2, 2024 11:17
@stephenxs stephenxs changed the title Extend delay run firmware Introduce delay in "sfputil firmware run" between running firmware and updating the cable firmware version info Nov 4, 2024
Signed-off-by: Stephen Sun <stephens@nvidia.com>
@stephenxs
Copy link
Owner Author

ci 4638 passed

@stephenxs stephenxs closed this Nov 18, 2024
@stephenxs stephenxs deleted the extend-delay-run-firmware branch November 25, 2024 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants