Where are fuse settings in esptool command?

[zliudr]

I was wondering if fuse settings such as the cpu frequency etc. are separately stored from program code or with the app .bin file. Because the command that flashes firmware doesn't include anything that looks like fuse settings:

Code: Select all

python /home/user/esp/esp-idf/components/esptool_py/esptool/esptool.py --chip esp32 --port COM32 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x10000 /home/user/esp/Projects/test/build/test.bin

I never thought about this till today I know now that partition table and bootloader both can be flashed if I make with flash option or just app if I do app-flash.

Thanks!

[chegewara]

https://docs.espressif.com/projects/esp ... efuse.html
https://github.com/espressif/esptool/wiki/espefuse

[zliudr]

Thanks chegewara. So I read the list of commands/fuse bits and I think that the efuse has nothing to do with what I'm concerned with such as CPU speed etc.

[ESP_Angus]

Thanks chegewara. So I read the list of commands/fuse bits and I think that the efuse has nothing to do with what I'm concerned with such as CPU speed etc.

That's correct. Almost all the project settings are compiled into the firmware binary file which is written to flash, nothing else needs to be done. Efuses are write-once settings related to low-level chip configuration, security features, or persistent storage inside the chip.

[zliudr]

Thanks chegewara. So I read the list of commands/fuse bits and I think that the efuse has nothing to do with what I'm concerned with such as CPU speed etc.

That's correct. Almost all the project settings are compiled into the firmware binary file which is written to flash, nothing else needs to be done. Efuses are write-once settings related to low-level chip configuration, security features, or persistent storage inside the chip.

That clarified everything! I'll worry about efuses towards the final stage of my project then. Thanks.