-
Notifications
You must be signed in to change notification settings - Fork 149
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
New attiny404 unprogrammable (RSP_ILLEGAL_MCU_STATE) #1660
Comments
ElTangas/jtag2updi#66 (comment)
|
Thanks, I missed that before. I've modified the make.bat file and built the latest version of jtag2updi with DISABLE_HOST_TIMEOUT defined. Unfortunately, after updating the arduino UPDI programmer I get the same response as before. As a sanity check I tried re-programming a known working attiny404 and there were no issues. Is it weird that I get the same error regardless of the commands entered? (programming, erasing, terminal, etc.) |
Problem solving tips
For JTAG2UPDI, this error and an additional status 0x00 pair are output from:
This system_status is obtained directly from ATtiny404 at the beginning of the "JTAG2::enter_progmode" function.
Under normal circumstances, this value will never be zero. There are several possible reasons for this.
|
I can only think that the chip is fried. But you can try the HV UPDI method mentioned by @askn37. If still not working, then the chip is probably damaged. I will close this issue now. Please re-open if you find that there is an issue with avrdude later. BTW, other than jtag2updi, you can also try serialupdi. |
Brilliant analysis @askn37 - Thank you |
Thank you for such a thorough answer. Since I've already tried the high voltage option I'm going to assume it's simply broken. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I have a new attiny404 which I've tried programming with both a HV UPDI programmer and a DIY/arduino version, but both encounter the same error message:
avrdude error: bad response to read memory command: RSP_ILLEGAL_MCU_STATE
I've been able to program attiny404s in the past, so my suspicion is that this particular one is in some way broken. On the PCB 5V is shared with the MCU and two low power LEDs, so I doubt that's relevant.
I've tried
-e
and-t -F
, but the output looks the same.Are there any additional debug steps that I can try, or is it a lost-cause?
avrdude -c jtag2updi -P COM4 -b 115200 -p t404 -e -vvvv
The text was updated successfully, but these errors were encountered: