-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
EFR32: Add hex binary to build output #12809
Conversation
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.
Consider adding this to build_examples build_outputs so that flashbundle images contain the hex binary as well.
PR #12809: Size comparison from 5bb8377 to 2b991aa Full report (29 builds for esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
/rebase |
2b991aa
to
beb73d3
Compare
PR #12809: Size comparison from b210aa3 to beb73d3 Increases above 0.2%:
Increases (18 builds for esp32, linux, mbed, nrfconnect, p6, telink)
Decreases (23 builds for esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
Full report (29 builds for esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Add a gn action which provides a hex binary in addition to the s37. The hex binary can be flashed with jlink and doesn't require commander to be installed, and is therefore an easier format for use in test automation.
beb73d3
to
8f12562
Compare
Done |
PR #12809: Size comparison from 228bd4b to 8f12562 Full report (32 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Problem
Currently efr32 builds only output s37 binaries which require commander tool to flash.
Change overview
Add a gn action which provides a hex binary in addition to the s37.
The hex binary can be flashed with jlink, and is therefore an easier format for use in test automation.
Testing
Built efr32 lighting and locking examples and verified hex file was generated.