nrf53_bsim doc: Add paragraph about using sysbuild

And a link to an example sample and its sysbuild.cmake file Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
zephyrproject-rtos · Oct 20, 2023 · 08fcc3c · 08fcc3c
1 parent e742362
commit 08fcc3c
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/boards/posix/nrf_bsim/doc/nrf5340bsim.rst b/boards/posix/nrf_bsim/doc/nrf5340bsim.rst
@@ -96,6 +96,11 @@ built with either Zephyr's build system or another native simulator compatible b
 you can provide that image to the Zephyr build of the second image using
 :kconfig:option:`CONFIG_NATIVE_SIMULATOR_EXTRA_IMAGE_PATHS`.
 
+You can also use :ref:`System build (sysbuild) <sysbuild>` to build your dual MCU executable.
+The best way to understand how, may be to look into how this is done in one of the examples
+in the tree. For example, for :ref:`the nrf53_sync_rtc sample <nrf53_sync_rtc_sample_build_bsim>`,
+:zephyr_file:`samples/boards/nrf/nrf53_sync_rtc/sysbuild.cmake`.
+
 
 .. note::
 

diff --git a/samples/boards/nrf/nrf53_sync_rtc/README.rst b/samples/boards/nrf/nrf53_sync_rtc/README.rst
@@ -75,6 +75,8 @@ Observe that initially logging timestamps for the corresponding events on both c
 do not match. Same with local and remote timestamps reported on network core. After
 RTC synchronization is completed they start to match.
 
+.. _nrf53_sync_rtc_sample_build_bsim:
+
 Building the application for the simulated nrf5340bsim
 ******************************************************