Hi there. There may be a more elegant solution, but I would replace EEPROM_check_if_busy() with a semaphore. Any task that wishes to perform a spi transaction must lock on the semaphore, and unlock it after the tranaction is complete.

Additionally, EEPROM_read_multiple_bytes() will not pass any ...

Fascinating. Thanks for the quick feedback

You might be able to call
/**
* @brief Wait until UART TX FIFO is empty.
*
* @param uart_num UART port number, the max port number is (UART_NUM_MAX -1).
* @param ticks_to_wait Timeout, count in RTOS ticks
*
* @return
* - ESP_OK Success
* - ESP_FAIL Parameter error
* - ESP_ERR_TIMEOUT ...

After reading the Flash Encryption and Secure Boot documents here https://docs.espressif.com/projects/esp-idf/en/latest/esp32/security/flash-encryption.html and https://docs.espressif.com/projects/esp-idf/en/latest/esp32/security/secure-boot-v1.html , I am rather confused on the benefits of secure ...

The documentation https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/unit-tests.html#multi-device-test-cases summarizes how to perform multi-device-test-cases and synchronize multiple devices using unity_send_signal() and unity_wait_for_signal()

Here is the provided sample multi ...

I am using an off-shore manufacturer for an esp32 product that can only be updated via OTA updates after the initial flash. For security reasons we are providing a limited firmware that we will subsequently use to load the proper firmware via an OTA update.

I believe the following files and ...