Like C_K said, same clip, same programmer, same software, but the code is not directly compatible, and it isn't quite as simple as just switching the register names, etc.
There are no code examples available for a 25/45/85 flashlight driver that I'm aware of, so you're probably on your own for now. The datasheet and Google will be your friends if you choose to embark on this adventure.
Yes definitely wasnt meaning to imply all it took was some register changes, I was getting at even with all the other work it needs right off the bat it isnt compatible at the most basic level. The language is the same but they are totally different chip’s, not simply “just a bigger 13A”. It will be a LOT of work to port it over and unless you already know how to code and have a good grasp of what all’s needed to do this you’ll probably be better off starting new. It would be about the same amount of work as starting new and if you’re new to coding in general it would be more helpful in the long run just to start fresh and learn.
Pretty much what I’m getting at is this- [OP] if you are brand new to coding and are gonna be following a tutorial along as you go start fresh, you’ll learn more in general doing that than trying to struggle threw porting it from a totally different chip.
I guess that was what I was getting at: it isn't something that someone that doesn't have an understanding of the chip and how to code for it can do; it isn't a simple "find and replace" port. I don't think you have to start from scratch, but you do need to have read the datasheet and understand what is going on with it. I tried to do it and couldn't make it work on my own, but it was a halfhearted effort.
It’s not a wider body, the 25 is available in both 150mil and 208mil (208mil is the larger size you are referring to - that’s what the 45/85 use).
JonnyC is planning to port STAR to the ATtiny25. Other capable minds are also on the matter even if they are not currently working on it (ToyKeeper for one).
I think it would be safe to pick up an ATtiny25 or two and be ready for new firmwares when they arrive.
To answer your question more directly: not really - microcontrollers all have the obstacles which RMM described. The only other MCUs I’m aware of which have publicly demonstrated flashlight code would be the handful of PIC MCU’s tterev3 discusses over here: tterev3’s PIC quickstart guide
I have code for an LED dimmer that runs on both the tiny13 and tiny85. The only place I had to change was the register setup for selecting the ADC bandgap reference voltage. Depending upon what you are doing, more changes might be needed…
I wouldn’t mind seeing the code either, but I think TP’s point was that fewer changes are necessary than has been implied. He’s clearly got to setup several registers for his LED dimmer, but the only ones he had to change were those for setting up the Vref.
Unfortunately the code for that dimmer is not mine and can’t be shared. It would not be usable in a flashlight anyway. The only change was in the register bits that select the 1.1V bandgap reference for the ADC.
just last night, after trying to somehow squeeze more code to fit into tiny13’s 1k, I realized I want the same thing, more memory -> tiny25a. I’d be willing to contribute few hours a week to have some flashlight code running on tiny25.
I’m also planning on getting some stuff from the Swedish Farnell site. If you’re going to order we could share the shipping cost. I think shipping is 70 or 80 sek.
I’ve had a look at the data-sheet, it doesn’t look like much work, but maybe some of it has already been done. In the zip from the Star download link (Blf-firmware) there is a ATtiny25 folder. I haven’t tried it yet though.