Writing to ATtiny85 EEprom

I have a sketch I developed on a Pro Mini.
I now want to put the sketch on an ATtiny.

The first step I need to do is simply write some data to the ATtiny85 EEprom with a basic sketch.

My first problem is a soon as I include any library and try to compile for an ATtiny85, the compiler complains.

So my first thoughts are that I need to do some software updating.

I am using IDE 1.5.7 and have not updated by choice.
I added the ATtiny cores from HighLowTech about 8 or 9 months ago.

I am interested to hear from someone who has a working setup to use EEPROM with an ATtiny85 and would like to know which IDE version and ATtiny cores you are using.

Try this core instead.

With IDE version 1.6.1 or higher.

I haven't worked with the x5 series, but the x7 series and have been working with this core and contributing feedback to the point where I can't find any major errors. However, I believe the x5 series was more developed than the x7 before that point.

Thanks.
I have installed 1.6.5 and the cores you recommended.

@ApexMOEng " You might be interested in feeding back that there are some issues with the cores you recommended. The issues arise when trying to use the Manchester library. Apparently the cores are missing the definition of AVR_ATtinyX5. The problem is discussed in this StackExchange thread in more detail.

I would appreciate a heads-up if/when the x5 cores have been updated.

For now I will switch to the arduino-tiny cores since they apparently works with the Manchester library.

Yikes, glad I stumbled across this thread. The ATtiny core (the one for x4, x5, x61, x7, x8 and x313) that I'm maintaining for 1.6.x didn't have those defines. I just added them - it used ATTINYX5 instead of AVR_ATtinyX5 (it now has both defines)

If it wasn't obvious; ↑ this is the guy to talk to :stuck_out_tongue: .

...also: Heads up.

@DrAzzy : LOL - I was actually using the cores you are maintaining and they are the ones this thread is about. I just didn't realize you were the maintainer until ApexMOEng pointed it out.

Well I guess since you updated them, I will reinstall them and stick with them for now.