Error flashing bootloader to 1604 because version with the fix was (2.6.6) was not released.

[ssarna1]

I've made a UPDI programmer like this one: ATtiny1604 UPDI HV Programmer

And now i'm on programming it, everything is set up as described there DIY ATtiny HV UPDI Programmer

and this is what i got:(fuses beforehand are verified correctly) `avrdude: reading input file "/home/XXX/.arduino15/packages/megaTinyCore/hardware/megaavr/2.6.5/bootloaders/hex/optiboot_txyz{bootloader.entrycond}.hex"

avrdude: can't open input file /home/XXX/.arduino15/packages/megaTinyCore/hardware/megaavr/2.6.5/bootloaders/hex/optiboot_txyz{bootloader.entrycond}.hex: No such file or directory

avrdude: read from file '/home/XXX/.arduino15/packages/megaTinyCore/hardware/megaavr/2.6.5/bootloaders/hex/optiboot_txyz{bootloader.entrycond}.hex' failed`

I assume something is not set correctly within Arduino and instead of some part of filename, a variable name "{bootloader.entrycond}"is displayed? It is installed from tarball, i'm on Ubuntu. IDE version is 1.8.19.

[SpenceKonde]

What does the Arduino tools menu look like?

[ssarna1]

[SpenceKonde]

You're not using the most recent release of the core, or are running some mixed up combination of two releases. Latest released version should have a bootloader entry condition menu and a reset/updi pin config menu for optiboot boards

IIRC while adding that to 2.6.6, I found a few places where the bootloader filename didn't resolve correcty.

So this should be fixed in 2,6,6.

Don't use github/2.6.7 version, I busted pwm completely the other night and am still trying to get that sorted out (part of the issue is that not only were users demanding it, I had suddenly come into a use case where I needed buffered pwm, so i figured time to implement the pwm pin selection menu. Which is in, except no matter what you select, no pins have PWM.

[ssarna1]

How do i get this 2.6.6? It's neither in board manager nor in releases on github.

[SpenceKonde]

Oh fuck!

Okay, well, apparently I failed to actually release it before I rendered the core non-useable in the development version, thinking I'd released a working version.

[nlCortana]

Similar issue yesterday while burning bootloader for the ATtiny3226. Fresh install of 1.8.13 with Megatinycore 2.6.5. Downgrade to MegaTinyCore 2.6.4 WORKS!

FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Users\\Asus\\AppData\\Local\\Arduino15\\packages\\megaTinyCore\\hardware\\megaavr\\2.6.5/bootloaders/hex/optiboot_tx2z{bootloader.entrycond}.hex'

[SpenceKonde]

Well yeah it would.

As long as you didn't care about the new features, I mean.

There are only 22 bootloader binaries supplied with 2.6.4. 2.6.6 would have shipped with 80, adding the same functionality that DxCore has.

[SpenceKonde]

I mean 2.6.5 shipped with all 80 too. We just substituted in "entrycond" but the menu sent "entrycondition" or something silly like that. Though I think as I was looking at it i fixed a bunch of bunk bootloaders. Or maybe that was DxCore. I know one one occasion I was in there for one simple bug, and wound up finding a huge number of bad binaries in one of the previous few versions of one of the cores. Would have been either 2.6.6 if it was mTC, since the new entry conditions were in when I started.

[SpenceKonde]

Closed - fixed by 2.6.7