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

[doc] Better explain HyperDebug flashing #26268

Merged
merged 1 commit into from
Feb 13, 2025
Merged

[doc] Better explain HyperDebug flashing #26268

merged 1 commit into from
Feb 13, 2025

Conversation

jesultra
Copy link
Contributor

At least two people have been understandably confused by error message Error: Firmware programming failed: Unable to establish connection after flashing. Possibly bad image. when using opentitantool to flash HyperDebug firmware for the first time. The cause being that with the jumper wire left in place, the board will not boot into the firmware just flashed, but instead boot into the DFU bootloaded again.

Adding an explicit step in the instructions calling for removing the jumper wire before running opentitantool should hopefully avoid this.

At least two people have been understandably confused by error message
`Error: Firmware programming failed: Unable to establish connection
after flashing.  Possibly bad image.` when using opentitantool to flash
HyperDebug firmware for the first time.  The cause being that with the
jumper wire left in place, the board will not boot into the firmware
just flashed, but instead boot into the DFU bootloaded again.

Adding an explicit step in the instructions calling for removing the
jumper wire _before_ running opentitantool should hopefully avoid this.

Change-Id: I2cdd333c12ebe566252482a1ba9eacf288a5eaec
Signed-off-by: Jes B. Klinke <[email protected]>
@jesultra jesultra marked this pull request as ready for review February 12, 2025 16:58
@jesultra jesultra requested a review from mundaym as a code owner February 12, 2025 16:58
Copy link
Member

@nasahlpa nasahlpa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I ran into the exact same issue, this is really helpful, thanks!

@jwnrt jwnrt merged commit a4eb67b into lowRISC:master Feb 13, 2025
42 checks passed
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.

3 participants