boards: arm: nRF9160: avoid resizing sram0 for nRF9160_dk

sram0 node is needed to hold the size of the
total, physical SRAM available on nRF9160 SoC.
We use sram0_s to represent the Secure image
SRAM for nRF9160_dk builds.

Signed-off-by: Håkon Øye Amundsen <[email protected]>
Signed-off-by: Ioannis Glaropoulos <[email protected]>

Author: hakonfam

boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts

@@ -10,7 +10,7 @@
 
 / {
 	chosen {
-		zephyr,sram = &sram0;
+		zephyr,sram = &sram0_s;
 		zephyr,flash = &flash0;
 		zephyr,code-partition = &slot0_partition;
 	};

boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_common.dts

@@ -180,6 +180,11 @@
 };
 
 / {
+	/* SRAM allocated to the Secure image */
+	sram0_s: memory@20000000 {
+		label = "secure_sram_memory";
+	};
+
 	/* SRAM allocated and used by the BSD library */
 	sram0_bsd: memory@20010000 {
 		compatible = "mmio-sram";

boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_partition_conf.dts

@@ -39,13 +39,13 @@
 
 /* Default SRAM planning when building for nRF9160 with
  * ARM TrustZone-M support
- * - Lowest 64 kB SRAM allocated to Secure image (sram0).
+ * - Lowest 64 kB SRAM allocated to Secure image (sram0_s).
  * - 64 kB SRAM reserved for and used by the BSD socket
- *   library.
+ *   library (sram0_bsd).
  * - Upper 128 kB allocated to Non-Secure image (sram0_ns).
  */
 
-&sram0 {
+&sram0_s {
 	reg = <0x20000000 DT_SIZE_K(64)>;
 };