Attiny alternative with more pb pins

Hi,
I an designing a driver and need more pins.
Are there any recommended low power 3.7v MCUs with more than 8 pins.

(The extra pins are needed to control more LEDs separately)

THX
Yuval

Recently at the ‘FW3A FAQ’ thread Lexel referred to the Attiny1634 as a capable MCU for doing fancy stuff with LED control.
Though you will need to write the firmware yourself.



Thanks, I am planning to write the FW anyway :)

It seems like MikeC is also using this MCU model

Yup, the 1634 has been getting some love. If you can do QFN (or VQFN), that opens up plenty of more options.

I’ve been using the attinyX16/X17 lately (such as the ’816). They’re also QFN/VQFN with plenty more pins, but they use a newer architecture and programming/debugging style. That may or may not be a good thing depending on what you’re going for.

I’m currently using the 1634 but gchart has paved the way for the 1-series. I’ve successfully flashed 3217 for a specific project but I haven’t yet ported all my functionality over to it yet. I’ll be sticking to the 1634 for my “normal” drivers.

You might be interested in the 14 pin ATtiny84. I’ve used for some projects some time ago. If I remember correctly it has some register differences than the 85, but changing them is fairly easy, nothing compared to moving over to 1-series.

I’ve got question, where can i buy attiny 1634 uckr, because in attiny1634 mur Thermal stuff don’t work properly.

Never heard of 1634-UCKR and cannot find any information for that order code.

Native USB support (and an “Arduino-chip”) would be pretty amazing for the modding community :open_mouth: But perhaps it can also be confusing for some people (if any) charging there lights with a computer port. If I can get a (Sofirn?) light with a chip like that I’d be so in love!!

Confusing in the sense that some muggle (excuse the term) could plug it in and try to charge it while unexpectedly getting a pop-up trying to install drivers or something… But true I suppose that can be eliminated with good naming/addressing (I’m not really into USB so I don’t really know how everything works in the back-end).

First thing that comes to mind: Register as mass storage device and expose the configuration as a txt file. So if you plug it in, it shows up just as a USB mass storage device. This allows backups, easier configuration and installation of downloaded configs. Also you could upload the firmware update (just drag and drop in a file manager) and the bootloader flashes it.

Did not even think of this, great idea!!

Updated my post while you were writing your response. Updating the firmware just by dropping the file with a file manager…

Yeah I think this would be the “next step up” for flashlights! No idea if it’s been done before, I only recently started becoming active on this forum… Attiny’s with Anduril are very nice but putting a MCU in a flashlight with native USB could be a gamechanger!

But then I see the potential to “brick” devices if the connection is disconnected during a firmware upgrade?
(but this is going way off topic in this post I suppose…)

Usually the bootloader is unaffected by the update, so if it fails just update again.

MTP sounds also good, but isn’t mass storage also sequential? I didn’t mean to implement a full filesystem. It should be enough to provide a virtual file list and implement read and write operations to the config “file” and write to *.bin files for the firmware update.

There`s a whole Range of MCUs in Microchips PIC series as well (if you can`t find what you want in Atmel).