-
Notifications
You must be signed in to change notification settings - Fork 2k
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
makefiles/tools/jlink.inc.mk: use FLASHFILE #11130
Conversation
Updated the testing procedure, with and without board. |
Update to use FLASHFILE as file to be flashed on the board.
JLink flasher used by the only supported board `nrf52dk` has been updated. FLASHFILE must now be defined by the board to use this in case a new one wants to be supported.
55b4c31
to
4c860f3
Compare
Rebased now that #11112 was merged |
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.
looks straight forward to me,
@smlng Do you want any other boards tested before merging this ? |
I see no issue with this PR. The boards I have are already tested so I can't do more testing. |
@cladmi can you test in a remote? |
@kYc0o I just checked and the remote boards are using a different JLink script
EDIT: and it is the same for |
Works on STK3700, I'd say everything is fine. Merge when Murdock succeeds. |
Thank you for the review. |
Contribution description
Update to use FLASHFILE as file to be flashed on the board.
Testing procedure
We need to test that boards using
Jlink
would still work with this.I will come up with a testing procedure without board.
Boards using JLink:
I listed all the boards using Jlink by using
git grep jlink.inc.mk
and checking also the boards usingcommon
.Test flashing normal examples with the board:
Test without board
I replaced FLASHER by 'true' to only show the FFLAGS and get the same output with master and this pull request:
mcuboot test
Test flashing
tests/mcuboot
fornrf52dk
(only one supported):One
make term
and runmake -C tests/mcuboot/ clean mcuboot-flash
.You should get:
Issues/PRs references
Split out of #8838
Depends on
#11112It would be useful to prevent extend the hack to Jlink for #11126