Skip to content
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

[nrf noup] samples: mgmt: mcumgr: smp_svr: Add nrf5340dk-optimised sample #2269

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nordicjm
Copy link
Contributor

Adds a configuration to this sample that is optimised for testing/usage with the nRF5340 which enables the Bluetooth transport, enables most management groups, has a static partition manager file with secondary partitions on QSPI flash, configures MCUboot in overwrite only mode with network core update support

Copy link
Contributor

@nvlsianpu nvlsianpu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multiple board configuration/overlay files was added in the sample's sysbuild/mcuboot/boards directory as well (not only nRF540dk).
I see that many of the can be involved into the build configuration as I'm recognizing them as their copies from MCUBoot's repository.

  1. What intention behind that?
  2. Why 3-rd party board files are added?
  3. Should we remove original files from MCUboot's repository?

@nordicjm
Copy link
Contributor Author

1. What intention behind that?

So that this sample can be used with any (nordic-based) board still, as the files in MCUboot will not be used

2. Why 3-rd party board files are added?

As above, only nordic-based boards are added

3. Should we remove original files from MCUboot's repository?

No

@nordicjm
Copy link
Contributor Author

Would add that this is only need due to, yet again, partition manager

Copy link
Contributor

@gchwier gchwier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: nrf54l15PDK can be removed, only DK is now supported
nit2: do we need pm_static files? Partition Manager should generate pm_static

and it is not fine that we need to copy all those configs from MCUboot repo when using sysbuild. As I remember, for child images those configs were taken as a default parameters, and overwritten by sample configs, now if we have any file/folder in sysbuild dir we must copy defaults to the project dir :(

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will we can avoid many of *.conf files copies If this file will be removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have reworked PR, all these files are now gone

@nvlsianpu
Copy link
Contributor

@nordicjm Can you rebase this?

@nvlsianpu
Copy link
Contributor

@nordicjm Can be merged.

@nvlsianpu
Copy link
Contributor

@nrfconnect/ncs-test-leads Please give tick.

@miha-nordic
Copy link

@nrfconnect/ncs-test-leads Please give tick.

CI is red. Please take a look on DFU tests.

…mple

Adds a configuration to this sample that is optimised for
testing/usage with the nRF5340 which enables the Bluetooth
transport, enables most management groups, has a static partition
manager file with secondary partitions on QSPI flash, configures
MCUboot in overwrite only mode with network core update support

Signed-off-by: Jamie McCrae <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants