ESP32-S2: get_security_info returns more bytes than expected (ESPTOOL-898) #65
Assignees
Comments
dobairoland
changed the title
DNedic
added a commit
to DNedic/esp-flasher-stub
that referenced
this issue
Oct 15, 2024
The ESP32-S2 ROM GET_SECURITY_INFO response does not contain chip_id and api_version fields. Currently, the flasher stub just returns 0 and 0 for these, however chip_id 0 is reserved for the ESP32. This makes the stub behavior in line with the ROM. Closes esp-rs#65
MabezDev
pushed a commit
that referenced
this issue
Oct 15, 2024
The ESP32-S2 ROM GET_SECURITY_INFO response does not contain chip_id and api_version fields. Currently, the flasher stub just returns 0 and 0 for these, however chip_id 0 is reserved for the ESP32. This makes the stub behavior in line with the ROM. Closes #65
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The ESP32-S2 supports the
get_security_infocmd, but returns a struct without thechip_idandapi_versionfields (returns 12 instead of 20 bytes).The legacy stub accounts for this with a variable
SECURITY_INFO_BYTESsize, but the rust flasher stub doesn't - returning 20 bytes with zeros instead of 12. This results in a wrongchip_idbeing detected (0).If the flasher stub is left running (
--after no_reset_stub) and you try to connect again, you get this:Detecting chip type.../dev/cu.usbserial-150 failed to connect: Unexpected chip ID value 0. Failed to autodetect chip type.
The security information report also shows this, which is wrong:
Chip ID: 0API Version: 0(Chip ID should be 2)
The text was updated successfully, but these errors were encountered: