Remix.run Logo
▲ serious_angel 6 hours ago

    > Update 2014-01-07:
    > It actually works on a ATtiny 10 now, yay!...
    > 
    > Update 2014-03-19:
    > I published a more detailed write-up...
    > 
    > Source: https://github.com/cpldcpu/u-wire

    ---

    > Flash: 988 of 1024 bytes used (96.4%)
    > SRAM: 28 (variables)+2 (stack) of 32 bytes used (93.8%)
    > 
    > This is most likely the most complex firmware ever loaded into an ATtiny10!
    > 
    > Source: https://cpldcpu.com/2014/03/19/%c2%b5-wire-usb-on-an-attiny-10
It felt like it was devalued by a sorrowful LLM/AI, but no… The person achieved the whole code manually.

Considering recent times… This is an authentic, real achievement that may inspire and support someone else and is to be kept treasured in the history with genuine glory, honor, and dignity.

Thank you… Thank you heartfelt for being an actual engineer, developer with authentic experience to be actually proud of, and held up as an example!

▲ignilux 2 hours ago | parent [-]

Doubly impressive considering the ATtiny 10 has no on-chip debugger peripheral!

▲05 2 hours ago | parent [-]

I don't think it makes a big difference - the mcu has a subset of AVR RISC instruction set so just running firmware on a beefier mcu of that family would allow you at least printf based debugging to uart, which should be enough here. It's not like stopping in debugger would help you with a timing sensitive protocol anyhoo, you would use logging either way.