-
Notifications
You must be signed in to change notification settings - Fork 16
UART_DATE_REG_ADDR seems wrong for some chips in const.ts #46
Comments
UART_DATE_REG_ADDR values are correct for ESP8266 and ESP32. The value that you shared for ESP32 is actually for the ESP32-S3, not for the original ESP32. For the C3 you are correct, that DATE_REG_ADDRESS should be 0x6000007c, there is a function for retrieving the ADDRESS in const.ts given the chip family, and it is not ready for the C3 family, so it returns -1. However right now the esp-flasher never uses this register in any operation since it is only used in "writeRegister" when delayAfterUs is greater than 0, and no function currently makes use of this parameter. So while the value is incorrect, it cannot be the reason why flashing to C3 is not working for you. Can you share more information on your test? Log information to see what chip family is being detected, etc....I tested this with my C3 board when I submitted the PR and it worked, I'll try and re-test again though. |
@conradopoole Thx, for looking into!
Serial log messages during start when booting Tasmota
|
|
Fixed. Thx |
ESP8266: UART_DATE_REG_ADDR = 0x60000078
ESP32: UART_DATE_REG_ADDR = 0x60000080
ESP32C3: UART_DATE_REG_ADDR = 0x6000007c
Source latest dev version of esptool.py
The c3 support seems is never tested. It would be great to get it going!
The text was updated successfully, but these errors were encountered: