-
Notifications
You must be signed in to change notification settings - Fork 90
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
Can't unlock ATTiny1624 #63
Comments
Well, I think I never actually tested jtag2updi with a Tiny AVR-2 series chip. The UPDI unit seems identical to series 0 and 1 so it should work but I need to be sure now that you report a problem. Anyway, another possible problem is that the UPDI pin is disabled (in reset or I(O mode). It should come in UPDI mode from the factory, but in this time of chip shortages there are some "strange" units being sold... In this case all I can do is redirect you to https://github.com/Dlloydev/jtag2updi/wiki/DIY-ATtiny-HV-UPDI-Programmer Sorry if can't be more helpful right now, I might need to get some Tiny AVR-2 samples for testing to make sure there isn't a bug with jtag2updi. |
Update Tried a new chip and everything worked just fine. It was unlocked and the upload works as it should. So I guess that the first one is either damaged or locked. So I am gonna try the HV programmer, but don't know when I'll have time. |
Ok, good to know tiny AVR-2 can be programmed or I would have to go bug hunting... |
Well, I have no idea where else to go. I bought a brand new ATTiny from Mouser and it seemed to come locked. So I tried to unlock it by erasing it (
-e
or-e -F
), which just gave me the error here:I then tried to use the interactive terminal. So I uncommented the
#define DISABLE_HOST_TIMEOUT
and#define DISABLE_TARGET_TIMEOUT
(tried it with and without the second define). I was then able to get into the terminal. But when I tried to erase the chip from here, I just got another error:Looks to be the same error as here #24, which makes me guess, that my ATTiny is broken.
So, is my ATTiny actually broken or is there anything I can try? Thanks in advance for any help
Here is the verbose log when using
-e
only:The text was updated successfully, but these errors were encountered: