DevLog[1] - “Early Beginnings”

Hi againnnnnn
In this devlog I kept working on the schematic, as well as did further research into the technologies that are going to be used (smarts)

I found a display that I would like to use and I wired it in! I also realized that I wired VDD and VSS wrong (power positive and negative, respectively) The last part of the schematic is going to be the bluetooth antenna and then we’ll be ready to move on to the next step!

(Caine Digital Circus’ voice)
Look at the rat’s nest! isn’t it beautiful
Have a nice day!

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:

1. 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.
2. 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
3. (bonus ) It’s not really expensive

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

1. Use the onboard USB on the MCU, knowing it’s slow af
2. 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