jlink: get flash and debug files from cli#10528
Conversation
Get BINFILE and ELFFILE from command line instead of environment variable. Rename 'HEXFILE' to 'BINFILE' in the script as the binary file is used. The documentation was already talking about 'BINFILE' but 'BINFILE' was never exported by the build system and it was using 'HEXFILE' in the implementation.
|
@cladmi, thanks for trying to cleanup this kind of things. The changes proposed this PR make sense but doesn't work in all cases: I tried to flash several applications with nRF52dk, most of them can be flashed except the ones that embed the Nordic Softdevice blob. |
|
@aabadie There should not be any issues with the way it was handled but I may be missing something. Could you print both output from |
|
@cladmi, I compared with master (and the 3 previous release branches) and I get the same issue with Nordic softdevice. So that may be a problem on my side, or a more general issue. To answer your request:
|
|
The diff between both looks the same as my example without I think the I found another way of comparing with master by checking the content of |
It was indeed this. Reinstalling jlink fixed the problem... And this PR works like a charm: I tried using |
|
Thanks for the review ! :) |
Contribution description
Get BINFILE and ELFFILE from command line instead of environment variable.
Rename 'HEXFILE' to 'BINFILE' in the script as the binary file is used.
The documentation was already talking about 'BINFILE' but 'BINFILE'
was never exported by the build system and it was using 'HEXFILE' in the
implementation.
Testing procedure
I cannot test flashing as I do not have boards or a Jlink flasher.
A real verification would also be great.
A partial test is to compare the content of
burn.segthat should be the same:My test is to check the executed command:
The difference with master is the following, which has nothing related to the actual flashing command but show
binfiletaken from argument.Same check for
debug:And the output diff with master also has nothing related to the executed debug commands but show
elffiletaken from argument:Issues/PRs references
#8838