Thingy91X nrf5340 flash usage configuration changes

[sd30]

Hello,  Have some experience with embedded development, but new to nRF Connect, sysbuild, Kconfig etc. 

Using Windows host VS code with nRF Connect extensions - current versions of all tools as of writing.

Thingy91x OOTB worked fine, build & flash simple examples working for '91 & '53 SOCs (via external segger SWD)

Looking to recover more of the 1M flash in the '53 app processor than provided by the default MCUboot configuration. e.g. similar to same sample apps running on the nRF5340DK board.

 nRF Kconfig GUI after creating a working build for thingy91x/nrf5340/cpuapp (not, some apps fail to build for the 'ns' option)

Tried the following;

 'Booloader support' = None (from MCUboot default)

then with MCUboot enabled again tried;

 'Pre-defined partition layout' - External flash and None (from factory default)

These cause the generate and build to fail in ways I don't yet understand how to fix.

Also tried defaults with just proj.conf:CONFIG_BOOTLOADER_MCUBOOT=n

A build after this still includes MCUBOOT.

I have much more to learn about the powerful features of sysbuild, overlays etc but would appreciate any tips re turning off MCUboot or changing its options to release more of the 1M flash in the SOC.

TIA. 

[Menon]

Hello,

Could you please share which SDK version you are using? If you are using sysbuild to build the sample application and want to disable MCUboot and recover flash, you can add SB_CONFIG_BOOTLOADER_MCUBOOT=n inside the sysbuild.conf file under the application directory. I believe you can also create a static partition file (pm_static) to define your own flash partition layout. See sysbuild partition manager.

Kind regards,
Abhijith

[sd30]

Thanks for the fast reply and info especially the link to an example with sysbuild.conf

"which SDK version you are using?" SDK 3.0.2

There is no sysbuild directory in the directories created by the SDK "Create a new application" (blinky & nrf multiple_adv_sets currently trying)

I read that sysbuild is the default when creating new applications with the current tools.  So I should actively select sysbuild when creating new applications in the SDK? 

I had tried a few early lessons from the devAcadamy ncs checkout but I see now its not till lesson 8 that the sysbuild/ directory is included.

I have been reading about partition manager, and expect to have to create a static partition layout later, esp. one that uses the external flash for storing DFU images, FS etc - to free up more of the internal flash for executable application code.  I understand that some boards don't have external flash so all partitions have to be crammed in internal flash of the SOCs, but when a board does have external flash like the Thingy91x - it would be nice to have the OOTB board configuration make use of that resource.  Is there by chance an example that does this?