feat: Add auto-detect ESP chip via security info and improve test coverage#12
Conversation
|
I was just able to do a little testing on my machine. With this PR, the auto-detection no longer works on |
|
@gandarez with this patch to your PR, I was able to flash esp3266 as well as esp32s3 boards: |
|
@gandarez did you see my proposed patch to this PR? What do you think? |
|
@deadprogram wdyt the proposed changes in this commit? Idea is to log when read security fails and fall though. |
Can you please add that to this PR so I can try it out? |
I just saw you already did that. Trying again now... |
|
@gandarez please see my small wording change. It does in fact appear to do what you were saying and worked on my esp8266 and esp32 boards, as well as esp32-s3. |
784c320 to
cdc2460
Compare
|
@deadprogram change made and commits squashed |
cdc2460 to
8c7d789
Compare
…erage Refactor chip detection from magic-register-only approach to use GET_SECURITY_INFO command with ChipID fallback via readReg. Add security_info.go for parsing security info responses (12/20 byte variants) and security flag decoding. Expand protocol layer with securityInfo command support and improve test coverage across flasher, protocol, and security_info packages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
8c7d789 to
1368642
Compare
|
Thank you very much for the additions @gandarez now merging... |
magic-register-onlyapproach to useGET_SECURITY_INFOcommand with ChipID fallback viareadReg.security_info.gofor parsing security info responses (12/20 byte variants) and security flag decoding.This PR is essential to get
esp32c6support in this PR