Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange Attiny424 HV programming issue #48

Open
lsellens opened this issue Jul 6, 2024 · 1 comment
Open

Strange Attiny424 HV programming issue #48

lsellens opened this issue Jul 6, 2024 · 1 comment

Comments

@lsellens
Copy link

lsellens commented Jul 6, 2024

I grabbed a HV Programmer to play around with some fuse settings and I'm having an issue with one particular chip. It's a attiny424. It will not program with pymcuprog in HV mode. I can read/write fuses and upload code with avrdude using this same HV programmer but anytime I try to use pymcuprog I get this error

raise PymcuprogError("Unexpected number of bytes in response: "
pymcuprog.pymcuprog_errors.PymcuprogError: Unexpected number of bytes in response: 0 byte(s) expected 1 byte(s)
Failed programming: uploading error: exit status 1

I can read/write other chips with this same HV programmer and pymcuprog just fine. I can also read/write to this chip with pymcuprog with a non HV programmer with no issues. It's just something particular about the combination of this chip with pymcuprog and HV programming. I'm thoroughly confused.

@xedbg
Copy link
Contributor

xedbg commented Jul 16, 2024

@lsellens - using SerialUPDI with HV activation is tricky. It looks like the device is not responding to a LDCS request, in other words UPDI is probably not enabled.
Although these tiny devices are very similar, there have been changes to the UPDI activation (check errata / datasheet clarifications) which might be affecting timing. AvrDude could have a plausible advantage with timing constraints over Python solutions like pymcuprog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants