I'm using the UART similar to the examples in the DOCs. Our application uses below 500bps data rates. It seems that it takes a long time (many seconds) before read_bytes or data available values are filled. repeated calls to uart_get_buffered_data_len return 0 but all of a sudden you get 100+ bytes ...

Nice! Much thanks @ESP_Roland

So it looks like if modify tools.json and include the older cmake, it works fine. Not sure if there is a better way.

-a

Please Note: there never was support for Visual Studio Community or Professional. While there is IDF support for VSCode, which is NOT what this post is about. In prior IDF versions you could get it working well using this helpful post: https://esp32.com/viewtopic.php?t=18924 . With IDF 4.4, this doe...

Much thanks @WiFive. Owe you a drink.

The storage partition is a raw flash partition.

This is the confusing part. If flash encryption works fine for read and write (and it's hardware based), what's the advantage of using AES-XTS for NVS parts?

-a

Nvs data should not be encrypted by espsecure.py or marked as an encrypted partition. It is protected by AES-XTS, not by flash encryption. It would makes sense not to have to double encrypt. But the sample app marks theirs encrypted. I''ll try without encrypting the nvs data. https://github.com/esp...

[ESP32 IDF 4.4] Our set up has the following: - Host Generated Flash Encryption Keys - Host Generated NVS Encryption Keys - NVS Keys Partition, usual NVS Partition, an extra storage NVS type partition. - Manually encrypted files flashed off-site This means plain-text nvs data and app is never flashe...

[IDF 4.1.2] Prior to enabling flash encryption, we generated our factory settings data on a separate NVS subtype partition using mfg_gen.py and flashed it along with bootloader and app with esptool.py . The app loaded as expected, read the factory settings from the nvs partition all ok. With flash a...

The IDF 4.1.2 documentation refers to reflashable but I think that's only for V1.

Provided that we have host generated per device flash encryption keys and secure boot keys, what steps do we need to take allow for serial uploading of new firmware (signed and encrypted)?

thx

In my app, upgrading from IDF 4.0 to 4.3 fails to fit in the IRAM. I have tried to use the hints in optimizing IRAM https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/performance/ram-usage.html?highlight=ram%20usage#optimizing-iram-usage to make it fit, but it results in other is...

The flash_encrypted_project_args are only made in development mode.