-
Notifications
You must be signed in to change notification settings - Fork 91
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
UPDI on ATTiny814 #24
Comments
I have tried this on an Uno and got the same issue, I can reflash ATTiny412 easily but ATTiny814, the chip is locked once I programmed the blinky sketch and I can not unlock it. The chip is running normally since I power it and the LED blink as it should (I just simply toggle PA3 pin for blinking). Should I try this on another ATTiny814? |
Ok. I guess I'll have to get some tiny814 to investigate. Unfortunately I don't have any ATM. |
Thanks ElTangas for the great tool, do you need more verbose information to investigate? I will get the output tonight. |
Ok, post the verbose output, that is, add -vvvv to the avrdude command line. edit: this line
gives me hope that I may find the problem with the verbose output. edit 2: also, try to erase by using -e in the command line. I would like the verbose output of that, too. |
Thanks ElTangas, please see the output, hope it helps.
Hope this helps :) thanks |
State 0x00 shouldn't even be possible! |
Here is the test code: https://github.com/ElTangas/jtag2updi/tree/Debug Please repeat the erase processes and post the verbose output, hopefully it will have more clues. |
I've been able to reproduce the error on your first post:
I did this by putting a pull-down on the UPDI link, then removing it. Please check your connections and make sure there is no extra stuff connected to the UPDI link. edit: one more thing, did you change any fuses? |
Please find the output of debug version for your debug, hope this helps. I'm using an Uno as UPDI programmer.
No, I didn't change any fuse. I just tried to upload the simple blinky sketch and it works for the very first time (the blinky sketch is still running when I provide power to the chip via programmer / LED toggle on/off via PA3 pin).Tthen the chip is completely locked and I can not program or erase it anymore. I'm using this setup to program 412 again without any problem (tried 10 times with Tiny412 and 100% works).
Should I get another Tiny814 and try it again? I will buy some chips this weekend and give them a try. Thanks. |
That chip is definitely not behaving normally, but there is no need to risk new chips yet.
That is, the response to the reset command. Can you please repeat the avrdude -e several times and see if the response is always the same, i.e. 0xa5 0x88? |
Maybe you're correct, I have just tried to run avrdude to erase the chip and it works (I success only three times among 45-50 times, I think). I tried this method:
It erases the chip successfully 3 times only with these steps, and now I can not replicate again, it's quite hard to get it done. Please stay tuned, I will get some Tiny814 this weekend and give them a try. I soldered this Tiny814 on breakout board with heat gun + solder paste, maybe that I push too much hot air so the chip is damaged, maybe, just remembered it's nearly burnt because I'm too rush. |
Hi ElTangas, |
I'm having the same issue with attiny841, BUT, it has been used quite alot and is on a used DIYBMS board for a test bed. using avrdudess. |
@Tigeruno ATtiny841 doesn't have UPDI (reads on your log too). Do you have a typo (814 vs 841)? |
My bad then. I thought it would work on any attiny. |
I have tried this with ATTiny412 and ATTiny814, the 412 works well so far and I can re-program the 412 many times, however, I have problems with ATTiny814.
Regarding 814, I can program the chip once then I can not communicate with the chip anymore,
I run this command try to unlock the chip
avrdude -C UDPI.conf -c jtag2updi -PCOM10 -p t814 -t -F
Then....
avrdude: jtagmkII_reset(): bad response to reset command: RSP_ILLEGAL_MCU_STATE
avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x656570
avrdude: Expected signature for ATtiny814 is 1E 93 22
avrdude> erase
erase
avrdude: erasing chip
avrdude: jtagmkII_chip_erase(): timeout/error communicating with programmer (status -1)
avrdude>
I always receive the time out communicating with the chip then I can not perform erasing. Is there another way to unlock the chip? Once the chip was programmed, it will be locked even there's no fuse touch?
Thanks.
The text was updated successfully, but these errors were encountered: