MikyZ72
commented
2 years ago Hello Espressif guys, no one respond here? We have a few thousand modules waiting to be sell and isn't possible that we must debug Espressif code! Problem is that esp_partition_write don't write in correct way the flash when is enabled the flash encryption, it broken bootloader code, partition table code, factory and ota in the flash.
Please help us...
What is the problem:
- frequency 80m flash and 40m RAM isnt ok?
- 16M flash?
- partition size?
- VFS and wear levelling don't work whit flash encrypted?
- some timeout not ok
mahavirj
Emill
moefear85
mythbuster5
Environment
Problem Description
Hello guys, If i flash all .bin system for production (ota, ota_data, factory, partition table, bootloader ecc) with efuses virtual enabled in partition emul_efuse, all work fine. If i disable virtual efuses for real burn efuses, start the problem, i think to see 2 problems:
esp_partition_get_sha256on ota return code 0x2002esp_vfs_fat_spiflash_mountformat the FAT like it lose the last formatted procedure on power offI have made many test, sdkconfig and different flash procedures and i have briked 10 module, till now i dont have found solution!
Project
I have 2 project in Espressif IDE (Eclipse):
The 2 project have the same sdkconfig and the same custom partition.csv file (they are ugual and i keep ugual)
In both there are enabled Flash encryption AES-256, Secure Boot V2 with sign binary during build with my generated key (openssl), ROM download mode is enabled (insecure for now). Sign key is the same for the loader project and firmware project I dont encrypt NVS data
SDKconfig image encryption
Bootloader of loader project is customized for run all the time at power on Factory partition and for run all the time ota partition from deep sleep wakeup. Bootloader of firmware project it's the original from Espressif, isn't customized, but i dont use it. When bootloader run my loader app from factory partition, after some check i launch deep sleep for hundred ms (100) and at wake up bootloader run ota partition (i use only 2 partition for update: 1 factory and 1 ota, this for don't lose flash space of 3 partition like 1 factory and 2 ota as a espressif default). Partition table offset is set to "0xb000" for enlarge bootloader space (because crypt and info logs) as a documentation explain.
Partitions
Write to flash
After build, i flash all binary with manual command from prompt:
esptool.py -p COM7 --chip esp32s3 erase_flashesptool.py -p COM7 --chip esp32s3 --before=default_reset --after=no_reset --no-stub write_flash --flash_mode dio --flash_freq 80m --flash_size 16MB 0x20000 loader.bin 0xb000 partition-table.bin 0x10000 ota_data_initial.bin 0x120000 firmware.binesptool.py -p COM7 --chip esp32s3 --before=default_reset --after=no_reset --no-stub write_flash --flash_mode dio --flash_freq 80m --flash_size 16MB 0x0 bootloader.binIn all command i dont reset after all bin file are flashed and Bootloader as the last as documentation mention because at restart it will start to burn the efuses if all crypt process is fine. It will reset when i start monitor:
idf.py -p COM7 monitorExpected Behavior
Firmware.bin file is signed at build and ota partition is crypted at first start of bootloader, i will expect that esp_partition_get_sha256 of ota is valid, but isn't. Storage partition isn't flashed and i think is empty (maybe is 0xFF) and i will expect at first start that is crypted and after formatted as a FAT when is mounted in automatic from API function, If i start to upload new ota firmware.bin with bluetooth and my protocol, file is saved in FAT and i run esp_reset(), then factory run check firmware.bin present in FAT and reflash ota partition with it.
Actual Behavior
Due to the ota is invalid my loader dont deep sleep and stay inside itself, wait for ota update via bluetooth with our protocol. At every power on i see that loader formatting every time the FAT, this is not correct. If i try to upload new ota firmware.bin with bluetooth and my protocol, function f_getfree on FAT error like the FAT is corrupted or not present
Debug Logs
Flash Log
Monitor Log
EFUSES LOG
Other items if possible