DevLog[0] - Patient learning

Hiiiiiiiii
This project might be a bit harder than I thought (very hard)
But worry not! my ego won’t let me leave it even if I tried

What I did:

The main decisions - I decided to use an STM32WBA65RIV6 (I think I spelt that right ) over a USB 2.0 connection.
“But isn’t that MCU way over-the-top?” yes
“And isn’t USB 2.0 super slow” indeed

So what’s up?

The MCU - I decided to use this MCU for two main reasons:

it has a LOT of memory: I am writing the firmware myself and if there’s one thing I can’t do (there are many) it’s work properly under hard restrictions.
it has a TON of GPIOs: I don’t yet fully know what this will do, my intention is that it would be an actually usable open-source (and hackable!) device, so any extra pin helps
(bonus ) It’s not really expensive

Bad USB - This one actually hurt. After some research I realized that my options were either:

Use the onboard USB on the MCU, knowing it’s slow af
write a whole USB driver, which would require a fundamental understanding of concepts I don’t have almost any grasp on, just to attempt to understand the amount of datasheets I would need to read through, all for a side project.

If anyone knows of a better way to do this, I would really love to know.
Have a nice dayy :33 <3