6/29/2026 at 8:57:05 AM
At $0.20 in 1k quantities, this is TI's answer to the CH32V003, Puya PY32, and the STM32C0 series. It's great to see tier-1 silicon vendors participating in the race to the bottom for jellybean microcontrollers.The 1KB of SRAM is admittedly very tight (even WCH's 10-cent RISC-V parts usually give you 2KB), so you are strictly in bare-metal, carefully-managing-your-stack territory.
by anonli
6/29/2026 at 11:21:35 AM
1KB isn't so bad unless you are making something complicated or need large buffers. You can do quite a bit of nontrivial stuff with it. Years ago I made universal remote with ATtiny13 + external EEPROM for storing remote data. It has only 64 bytes of RAM, that's what I would call very tight. Was still able to program it in C, 1KB flash and number of pins were bigger limiting factor than ram.Plenty of DIY projects used ATtiny2313 with V-USB. That's a pure software USB implementation bit banging the IO pins (not a USB stack on top of hardware USB support)+ your application logic squeezed into 2K of flash + 128 bytes of ram.
Chips like this are great for digital glue logic. Read a sensor, read a button press, blink some LEDs with simple state machine or control loop.
by Karliss
6/29/2026 at 3:03:31 PM
Yes, that's "bare metal" as opposed to programming in MicroPython, Javascript with Espruino, Lua/NodeMCU, Rust, or adding your C application on top of an off-the-shelf RTOS.C support is basically universal these days, very few chips require you to program in only assembly anymore.
by LeifCarrotson
6/29/2026 at 3:27:45 PM
I had no troubles targeting an ATTiny13A with Rust.(had to disable debug symbols, though)
Why should that be any harder than C?
by kawogi
6/29/2026 at 3:14:13 PM
Rust compiles to bare metal (assembly aka machine instruction code), just like C does.by daveguy
6/29/2026 at 6:36:10 PM
Bare metal refers to not using an rtos. I know that sounds weird but it is an industry convention. It does not refer to the language.by supertroop
6/29/2026 at 4:18:35 PM
It also supports running in freestanding setups without an OS, and quite a lot of the language's features still work.I was extremely surprised by how much functionality is packed into "core", and runs without an OS when using freestanding rust. Even stuff that requires an allocator can run provided you provide your own heap!
A cool example of this was implementing fmt::Write for a memory mapped uart console thing. Then implementing a kprintln! macro that supports all of the formatting machinery that you are use to. This worked without even a heap available.
by chlorion
6/29/2026 at 4:55:55 PM
Check out the video introducing Swift for Embedded. Seems like a really nice devX for this kind of thing.by kridsdale1