suit: Do not erase on IPUC write setup

Erasing of the IPUC took about 500ms of time, which
led to many issues.

The erasing was removed, instead different security
measures were introduced, erasing parts when the
seek offset is greater than the write peek offset.

Signed-off-by: Artur Hadasz <artur.hadasz@nordicsemi.no>

Author: ahasztag

subsys/suit/ipuc/src/suit_ipuc_sdfw.c

@@ -297,15 +297,6 @@ suit_plat_err_t suit_ipuc_sdfw_write_setup(int ipc_client_id, struct zcbor_strin
 		suit_plat_digest_cache_remove(component_id);
 #endif /* CONFIG_SUIT_DIGEST_CACHE */
 
-		if (ipuc_sink.erase == NULL ||
-		    ipuc_sink.erase(ipuc_sink.ctx) != SUIT_PLAT_SUCCESS) {
-			LOG_ERR("Erase operation not supported or failed");
-			if (ipuc_sink.release) {
-				ipuc_sink.release(ipuc_sink.ctx);
-			}
-			k_mutex_unlock(&ipuc_mutex);
-			return SUIT_PLAT_ERR_IO;
-		}
 
 		if (ipuc_sink.release) {
 			ipuc_sink.release(ipuc_sink.ctx);
@@ -371,6 +362,21 @@ suit_plat_err_t suit_ipuc_sdfw_write(int ipc_client_id, struct zcbor_string *com
 			return SUIT_PLAT_ERR_IO;
 		}
 
+		if ((ipuc_sink.write != NULL) && (offset > ipuc_entry->write_peek_offset)) {
+			/* Erasing if necessary
+			 */
+			uint8_t erase_buffer[READ_CHUNK_MAX_SIZE] = {
+					[0 ... READ_CHUNK_MAX_SIZE - 1] = 0xFF
+			};
+
+			ipuc_sink.seek(ipuc_sink.ctx, ipuc_entry->write_peek_offset);
+			for (size_t i = ipuc_entry->write_peek_offset; i < offset;
+			     i += READ_CHUNK_MAX_SIZE) {
+				ipuc_sink.write(ipuc_sink.ctx, (uint8_t *)erase_buffer,
+				MIN(sizeof(erase_buffer), slot_size - i));
+			}
+		}
+
 		if (ipuc_sink.seek == NULL ||
 		    ipuc_sink.seek(ipuc_sink.ctx, offset) != SUIT_PLAT_SUCCESS) {
 			LOG_ERR("Seek operation not supported or failed");