-
Notifications
You must be signed in to change notification settings - Fork 3k
Reorganize SoftDevices for NRF52 series #6826
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
Conversation
@marcuschangarm How this breaks the current apps? Can it be made backward compatible ? |
Its not more breaking than the 5.9 stuff we've been doing! 😄 |
There sure are a bunch of new hex files and bootloaders. Would it be possible to comment in the commit message as to how they were generated? |
Shouldn't this be the default action for Nordic devices instead of needing to explicity add it to target_overrides? |
Added:
|
That would be a deviation from what we have done since the first NRF51. |
/morph build |
Build : FAILUREBuild number : 1950 |
/morph build |
Build : FAILUREBuild number : 1951 |
/morph build |
Build : FAILUREBuild number : 1953 |
Looks like something different went wrong with the CI. |
/morph build |
Build : FAILUREBuild number : 1967 |
/morph build |
Build : SUCCESSBuild number : 1973 Triggering tests/morph test |
Test : FAILUREBuild number : 1784 |
/morph test |
Exporter Build : FAILUREBuild number : 1624 |
Test : SUCCESSBuild number : 1785 |
/morph build |
Exporter Build : FAILUREBuild number : 1644 |
The failure for export is the same one as previous one. We have seen it on master, was fixed a week ago. Can you test locally on your branch, or shall it be rebased (however CI merges this with the destination branch) so should not be there at all. @theotherjimmy @studavekar Please look at this |
The fix #6713 for error looks like still the commandline is too long to handle. |
I'm undoing the nested folder structure and keeping the directories flat. The PR will be about adding the MBR and OTA binaries. |
Sure, I literally just copy pasted it in an intel hex editor. |
I can collect a list with changes. The major changes have been to things that didn't work correctly to begin or to people that for some reason have linked directly to files in the SDK. |
/morph build |
Build : SUCCESSBuild number : 2032 Triggering tests/morph test |
Test : FAILUREBuild number : 1838 |
Exporter Build : FAILUREBuild number : 1681 |
/morph test |
/morph test |
Exporter Build : SUCCESSBuild number : 1686 |
/morph test |
Test : SUCCESSBuild number : 1852 |
New directory structure: * TARGET_SOFTDEVICE_COMMON * TARGET_SOFTDEVICE_S112 * TARGET_SOFTDEVICE_S132_FULL (MBR + SoftDevice, default) * TARGET_SOFTDEVICE_S132_OTA (SoftDevice only, for firmware updates) * TARGET_SOFTDEVICE_S132_MBR (MBR only, for bootloader builds) * TARGET_SOFTDEVICE_S140_FULL (MBR + SoftDevice, default) * TARGET_SOFTDEVICE_S140_OTA (SoftDevice only, for firmware updates) * TARGET_SOFTDEVICE_S140_MBR (MBR only, for bootloader builds) * TARGET_SOFTDEVICE_NONE The X_OTA and X_MBR binaries are obtained from the original x_FULL SoftDevice by splitting it in an MBR part and a SoftDevice part. The MBR is needed for the bootloader and the SoftDevice for firmware updates. Build application without SoftDevice: "target_overrides": { "*": { "target.extra_labels_remove": ["SOFTDEVICE_COMMON", "SOFTDEVICE_X_FULL"], "target.extra_labels_add": ["SOFTDEVICE_NONE"] } } Build application for firmware update using SoftDevice X: "target_overrides": { "*": { "target.extra_labels_remove": ["SOFTDEVICE_X_FULL"], "target.extra_labels_add": ["SOFTDEVICE_X_OTA"] } } Build bootloader without SoftDevice X: "target_overrides": { "*": { "target.extra_labels_remove": ["SOFTDEVICE_COMMON", "SOFTDEVICE_X_FULL"], "target.extra_labels_add": ["SOFTDEVICE_X_MBR"] } }
/morph build |
Build : SUCCESSBuild number : 2058 Triggering tests/morph test |
/morph test |
Exporter Build : SUCCESSBuild number : 1700 |
Test : SUCCESSBuild number : 1868 |
Description
New directory structure:
The X_OTA and X_MBR binaries are obtained from the original x_FULL SoftDevice
by splitting it in an MBR part and a SoftDevice part. The MBR is needed for
the bootloader and the SoftDevice for firmware updates.
Build application without SoftDevice:
Build application for firmware update using SoftDevice X:
Build bootloader without SoftDevice X:
Pull request type