Conversation

I will be smart, he says! I will use I2C, for it uses less pins, he says! I will put three microcontrollers together, he says! Simple bring up, he says! (he weeps, trying to make an STM32 I2C peripheral and an nRF52 I2C controller to work together reliably without locking up)

190

rigorous consent flow

@runehog

Feb 28

Replying to

@bitshiftmask

oh I've been afraid of this conjunction

Replying to

Eh, it'll pass. I've been avoiding getting deeply familiar with the I2C peripheral on the STM32, and it likely has some error case I'm totally ignoring. Now that I (hopefully) have a much more reliable programming setup, it has been much easier to iterate :)

Replying to

and

i ditched the i2c on the stm32f103 and wrote a bitbanged impl. the hw is really buggy. hard lock that only reboot can solve. the newer ones (i2c v2?) are better i've read but i've never used them myself

2:08 AM · Feb 28, 2022Twitter Web App

rigorous consent flow

Replying to

and

that whole line of hardware looks really scary from the outside looking in but I'm sure there are some plusses, right?

Replying to

and

they used to be cheap :-)

Show replies

Replying to

and

Yeah, this is the v2 (STM32G030), so I was hopeful. tbh my driver is full of hope and naiivety (I wrote it on like one skim of the datasheet, a couple months ago), so it's very likely I'm not doing it entirely right yet The nRF52 side is a bit better, but I've had hiccups before

rigorous consent flow

Replying to

and

the nrf52 side is always slightly weird but at least predictable so far for me