How to make custom core work on 1.6.2

Okay, so everyone who had any interest in my new Attiny841 core immediately asked about 1.6.x support.

So I got it working on 1.6.0 pretty easy. Figured I should drop 1.0.6 since it doesn't seem possible to make one core that works with both due to changes in boards.txt.

Trying to keep up with the times, I removed 1.60, deleted Arduino user folder, installed 1.6.2, and tried to reinstall my core. And nothing works.

My custom core used to work on 1.6.0.

On 1.6.2, I get:

Cannot run program "C:\Arduino/hardware/tools/avr/bin/avr-g++": CreateProcess error=2, The system cannot find the file specified

Sure enough - the compiler toolchain is GONE!

Where the hell is it now, and how do I get my core to work again?

The core migration guide makes no mention of this!

Core is this one - https://github.com/SpenceKonde/arduino-tiny-841 - this used to work (at least for the 841 - didn't yet test the 1634 - that was one of the things I was about to do, when I discoverd that the toolchain was no longer accessible.

DrAzzy: Sure enough - the compiler toolchain is GONE!

Moved (assuming you are using Windows)... http://forum.arduino.cc/index.php?topic=312561.msg2166454#msg2166454

On 1.6.2, I get: Cannot run program "C:\Arduino/hardware/tools/avr/bin/avr-g++": CreateProcess error=2, The system cannot find the file specified

You will have to update platforms.txt. This is what I use. A few things are dropped from the official version so Tools / Burn Bootloader just changes the fuses... https://github.com/Coding-Badly/TinyCore1/blob/master/avr/platform.txt

The core migration guide makes no mention of this!

On the Developers List, Federico apologized for the lack of documentation. He had to deal with an emergency that prevented him updating the documentation with the release.

Thanks

Does that mean that there's no way to make a single core that works in both 1.6.1 and 1.6.2?

And, are you saying it is no longer possible to burn a bootloader from the IDE on a custom core, only change the fuses? That is a huge step backwards if that's true....

DrAzzy: Does that mean that there's no way to make a single core that works in both 1.6.1 and 1.6.2?

The only difference is platform.txt, the entire file is about 30 lines, and the differences are minor. If you are using any sort of version control system, the "old" / 1.6.1 version will essentially always be available. You will have to decide if that means "no way".

And, are you saying it is no longer possible to burn a bootloader from the IDE on a custom core, only change the fuses?

No. I am saying my version of platform.txt only changes the fuses. I apologize for the confusion. That earlier post was poorly written.

Sigh - thanks.

Your version of platform.txt looks like it still burns the bootloader?

Fixes are in - until 1.6.3.

No.

Unlock is removed from the erase pattern... https://github.com/Coding-Badly/TinyCore1/blob/master/avr/platform.txt#L92 ..versus... https://github.com/arduino/Arduino/blob/master/hardware/arduino/avr/platform.txt#L92

Flash and lock are removed from bootloader pattern... https://github.com/Coding-Badly/TinyCore1/blob/master/avr/platform.txt#L96 ..versus... https://github.com/arduino/Arduino/blob/master/hardware/arduino/avr/platform.txt#L96

DrAzzy:
Okay, so everyone who had any interest in my new Attiny841 core immediately asked about 1.6.x support.

So I got it working on 1.6.0 pretty easy. Figured I should drop 1.0.6 since it doesn’t seem possible to make one core that works with both due to changes in boards.txt.

I have not looked into 1.7.x from the “other” Arduino IDE provider, have you? Personally, I think this is the kiss of death for the brand. I use professional tools from various manufactures; Arduino, once easy for weekend play, is doing everything to piss me off. I’m seriously thinking about leaving and moving to another IDE.

What I would like to see is both parties moving the GUI to a 3rd party for support & maintenance as a single open source project.

Ray