Closed uterator closed 1 year ago
Please re-test. I see several problems. The Chip submenu does not appear to have anything selected; I believe in this case it uses the first option, which is ATtiny1614 in the most recent release - though this may be an interface difference (a major downgrade if so). Be sure that all submenus have an option selected, particularly "chip". You list board as Arduino Uno; this is in direct conflict with everything else you say, because the board you are referencing otherwise is ATtiny3224/1624/(snip)/204. Please clarify what is meant here. You are using a pre-release 2.0.0 version of the IDE. We do not test with prereleases, and the RC versions have had a fairly large number of regressions. The latest 1.8.x release should work. I use 1.8.13 because of a bug in 1.8.14 and later (but fixed in 2.0.0) that makes development more troublesome, but the most recent releases have worked around that one. I have used 1.8.13 with mTC 2.6.5dev to upload to 1624's without issue.
@SpenceKonde Thank you for the answer, and yes you are right, chip setting was incorrect. And thank you for the IDE version notice, however the 2.0.0-rc9.2 worked as well and I like the editor there (built on theia) but I will continue with 1.8.13 as you recommend.
Regarding to chip selection, the 2.0.0-rc9.2's menu doesn't show the submenu selected values, should be a UI bug. I used to not see values there so I didn't pay attention on chip's value before reporting, not a something which I do every day. If not that bug, the reason of the reported issue would be very obvious.
The selected chip and other selected options are visible on 1.8.13's menu.
As for the board, I mentioned the device which is used only as a programmer for my tiny MCUs.
Now my setup is 1.8.13 with mTC 2.6.4 and it works.
Thank you.
Hi, Thank you for the all work done in megaTinyCore. I am using it for a long time, and now I faced an issue after switching from 1604 to 1624. At uploading a program on ATtiny1624 it fails with
Both mentioned signatures match the specs ATtiny1614 0x1E 0x94 0x22 ATtiny1624 0x1E 0x94 0x2A
It was working successfully for a long time with ATtiny1604 before moving to ATtiny1624. I just updated the megaTinyCore version to the latest one to have a support for 1624 (and replaced the board if that makes sense).
Environment Arduino IDE:
Version: 2.0.0-rc9.2, Date: 2022-08-10T13:01:55.702Z, CLI Version: 0.26.0-rc.1 [fc2ea723]
OS:Linux
megaTinyCore:Version 2.6.4
board:Arduino UNO
Config
command
As we see the
-pattiny1614
parameter is passed to theavrdude
command which is not correct as it had to be 1624. I manually changed it to-pattiny1624
and run theavrdude
command in terminal, it didn't fail but I am not sure if it was a correct thing to do as I kept all parameters for fuses the same from the old command with-pattiny1614
(I don't see even the program worked after that).Am I missing something in configuration or it can be corrected in the lib? Thanks
Full logs