FLASH and SRAM overflow error

[Sachin]

Hi,

 When I try to build a 'light_switch' project on SEGGER embedded studio for nRF connect SDK 1.9.1 for BMD-330-EVAL board. Running into the following error 

 arm-none-eabi/bin/ld.exe: zephyr\zephyr_pre0.elf section `text' will not fit in region `FLASH'
 v1.9.1/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: zephyr\zephyr_pre0.elf section `noinit' will not fit in region `SRAM'
 /v1.9.1/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: region `FLASH' overflowed by 69824 bytes
 v1.9.1/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: region `SRAM' overflowed by 25031 bytes

Not able to find flash_placement.xml to make any changes as suggested in a few threads. The 

[tesc]

Hi,

We have light switch examples for several protocols. I am most familiar with Bluetooth mesh, which is not supported on the nRF52810, mostly due to insufficient flash and RAM, which seems to be what you experience. The same is also true for some of the other protocols, such as Thread and Zigbee.

Bluetooth mesh is supported on nRF52832, nRF52833 and nRF52840.

Thread and Zigbee are supported on nRF52833 and nRF52840.

For Bluetooth mesh, if you want to experiment with building on devices with little space you could have a look at the microbit configuration files under \zephyr\samples\bluetooth\mesh, which contains configurations optimized for low flash and RAM usage.

Regards,
Terje