-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
west: runners: jlink: JLink.exe name collision #51825
Comments
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
@JordanYates FYI. Thanks for this. I ran into this as well. |
@JordanYates Also thanks. Same issue here. |
We need a different assignee. Does someone on this ticket want to take this on? |
I have also encountered this problem, and a temporary solution is: |
This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time. |
Describe the bug
The
jlink
binary runner uses the location ofJLink.exe
orJLinkExe
to determine the location of the JLink libraries,zephyr/scripts/west_commands/runners/jlink.py
Line 26 in 117039c
zephyr/scripts/west_commands/runners/jlink.py
Line 38 in 117039c
zephyr/scripts/west_commands/runners/jlink.py
Lines 177 to 178 in 117039c
Unfortunately the OpenJDK runtime also distributes an executable called
jlink.exe
: https://strontic.github.io/xcyclopedia/library/jlink.exe-15C86A7D8376EC476DD2AE27EAEE31D1.htmlTrying to run
west flash
with the runtime on the path results in errors like:Expected behavior
The jlink plugin should ideally be more resilient to finding a SEGGER executable, not any old executable called
jlink.exe
.Impact
Annoyance, the correct path can be selected with
west flash --commander /path/to/JLink.exe
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: