boards: renesas: Add support MCUBoot for ek_ra8p1 and mck_ra8t2

[khoa-nguyen-18]

• Add depend on BOOTLOADER_MCUBOOT for SOC_RA_ENABLE_START_SECOND_CORE config
• Add support MCUBoot for ek_ra8p1 and mck_ra8t2
• Remove storage_partition definition for Renesas ek_ra8p1, mck_ra8t2 in the test flash/common

[github-actions]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
hal_renesas	zephyrproject-rtos/hal_renesas@3ce2bdc	zephyrproject-rtos/hal_renesas#159	zephyrproject-rtos/hal_renesas#159/files

⛔ DNM label due to: 1 project with PR revision

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[JarmouniA]

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

[khoa-nguyen-18]

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

Many thanks for your suggestion and the reference. I’ve added the board documentation for MCUboot. However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot. Instead, we guide users to build with the additional configuration option -DSB_CONFIG_BOOTLOADER_MCUBOOT=y.

[thenguyenyf]

LGTM. Will revisit after manifest is merged

[JarmouniA]

You still need to add Kconfig.sysbuild file. (Non-blocking)
Apply remarks to both boards.

[JarmouniA]

Suggested change

	With ``--sysbuild`` option, MCUboot will be re-build and re-flash
	With ``--sysbuild`` option, MCUboot will be re-built and re-flashed

[JarmouniA]

Suggested change

	To only flash the user application in the subsequent builds, Use:
	.. code-block:: console
	$ west flash --domain hello_world

[JarmouniA]

To be memory efficient, 2nd slot has to be 1 sector larger than the 1st.
https://docs.mcuboot.com/design.html#image-swap-offset-no-scratch

[JarmouniA]

However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot

Those should be the exception, not the general default. Also, you can create a dedicated board variant for those.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[duynguyenxa]

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

Many thanks for your suggestion and the reference. I’ve added the board documentation for MCUboot. However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot. Instead, we guide users to build with the additional configuration option -DSB_CONFIG_BOOTLOADER_MCUBOOT=y.

However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot

Those should be the exception, not the general default. Also, you can create a dedicated board variant for those.

Hi @nordicjm, @kartben — could we get your thoughts on this?
Should there be a Kconfig.sysbuild default here for MCUboot for the board, or should we leave it out to keep sysbuild generic for both MCUboot and non-MCUboot applications?

[nordicjm]

Can you add info about MCUboot usage to the board doc? Also, add Kconfig.sysbuild to board folder with the following

choice BOOTLOADER
	default BOOTLOADER_MCUBOOT
endchoice

Many thanks for your suggestion and the reference. I’ve added the board documentation for MCUboot. However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot. Instead, we guide users to build with the additional configuration option -DSB_CONFIG_BOOTLOADER_MCUBOOT=y.

However, I prefer not to include Kconfig.sysbuild in this case, as it’s specific to the user’s build setup. We also need sysbuild to support building other applications that don’t use or require MCUboot

Those should be the exception, not the general default. Also, you can create a dedicated board variant for those.

Hi @nordicjm, @kartben — could we get your thoughts on this? Should there be a Kconfig.sysbuild default here for MCUboot for the board, or should we leave it out to keep sysbuild generic for both MCUboot and non-MCUboot applications?

MCUboot is optional. You can build an application for the board without MCUboot and it builds, flashes and runs fine right? So having MCUboot disabled by default is perfectly fine