<re_irc>
<yruama_lairba> directly passing multipliers/dividers is much nicer, but you may loose portability
<re_irc>
<yruama_lairba> i saw a "require" method on stm32f4xx that panics if the actual frequncy doesn't match
<re_irc>
<dirbaio> stm32-rs hals for different families are so different there's not much portability anyway 🤣
<re_irc>
<yruama_lairba> dibaio, you may have difference in clock setup across the same family
<re_irc>
<dirbaio> within a single familiy rcc is (almost) always the same
<re_irc>
<Lachlan Sneff> Require would be nice, better if that’s the default
<re_irc>
<yruama_lairba> on F4xx families, there is big difference for the I2s clock generation
<re_irc>
<yruama_lairba> for rcc clock, i always wonder if it is necessary to "freeze" clock
<re_irc>
<yruama_lairba> for example, for i2s again, it would be nice for some advanced application to "own" the i2s clock tree to have a wider choice of sampling frequency
<re_irc>
<yruama_lairba> but there not even yet a working hal for i2s :p
<re_irc>
<yruama_lairba> need to go, bye
Ekho has quit [Quit: CORE ERROR, SYSTEM HALTED.]
Socke has quit [Ping timeout: 272 seconds]
Socke has joined #rust-embedded
eigenform has quit [Ping timeout: 272 seconds]
eigenform has joined #rust-embedded
Socke has quit [Ping timeout: 272 seconds]
diagprov has quit [Ping timeout: 272 seconds]
xnor has quit [Ping timeout: 272 seconds]
limpkin has quit [Ping timeout: 272 seconds]
xnor has joined #rust-embedded
Socke has joined #rust-embedded
limpkin has joined #rust-embedded
diagprov has joined #rust-embedded
Ekho has joined #rust-embedded
nort has quit [Read error: Connection reset by peer]
explore has joined #rust-embedded
nort has joined #rust-embedded
fabic_ has quit [Ping timeout: 256 seconds]
emerent has joined #rust-embedded
eigenform has quit [Remote host closed the connection]
eigenform has joined #rust-embedded
gsalazar has joined #rust-embedded
fabic_ has joined #rust-embedded
explore has quit [Quit: Connection closed for inactivity]
<re_irc>
<thejpster> Had to cache the glyphs to get 60 FPS though. And I can't work out how to re-colour a texture on the fly, so I actually cache 16 copies of each glyph - one for each foreground colour.
fabic_ has joined #rust-embedded
<re_irc>
<James Munns> Hah! I think indirectly COVID has been a boon to Rust OS development
<re_irc>
<James Munns> MnemOS got imagined while I was actively sick, and written while I was recovering, and I know Eliza put in a bunch of work on Mycelium under the same conditions
wybpip[m] has joined #rust-embedded
wybpip[m] has left #rust-embedded [#rust-embedded]
Amadiro_ has quit [Ping timeout: 248 seconds]
stixp has joined #rust-embedded
stixp has quit [Ping timeout: 256 seconds]
stixp has joined #rust-embedded
ymwm has joined #rust-embedded
ymwm has quit [Ping timeout: 240 seconds]
stixp has quit [Quit: leaving]
ymwm has joined #rust-embedded
<re_irc>
<Radu> Hello, as Rust is good for system programming, what kind of personal projects can I make as a beginner? Do you have any ideeas/recomandations?
<re_irc>
<Radu> * ideeas/recommendations?
<re_irc>
<Radu> -kind of
<re_irc>
<K900> Blinking a LED is the usual starting point
<re_irc>
<K900> From there, really just look at what is available and seems fun to you
<re_irc>
<Radu> Thank you
<re_irc>
<ryan-summers> blinky LED is the hello world of embedded - highly recommended
<re_irc>
<Radu> Good to know it, fortunately, rust has a lot of books and resources to learn. I didn't enter very deep in embedded but as I understand, you can design your own boards, with your chip and components and then write code for it. Right?
<re_irc>
<marmrt> That's how it goes
<re_irc>
<newam> Radu: Yeah, there's nothing rust-specific about the hardware. Anything ARM Cortex-M or RISC-V based that runs C can run rust too.
gsalazar has quit [Ping timeout: 276 seconds]
fabic_ has quit [Ping timeout: 256 seconds]
<re_irc>
<Radu> Do you have any resources to learn about those types of chips: cortex,msp430, RISC-V
ymwm has quit [Ping timeout: 250 seconds]
<re_irc>
<Lachlan Sneff> The CAN bus is working, thank you everyone!
<re_irc>
<Lachlan Sneff> There's something weird going on with specifying the clock tree configuration directly though. The PLLMUL in the clock config gets 2 added to it within the HAL, so in mxcube you'd specify 9, but in stm32f1, you specify 7
<re_irc>
<burrbull> Lachlan Sneff: Open issue, please
<re_irc>
<Lachlan Sneff> Will do
ymwm has joined #rust-embedded
ymwm has quit [Remote host closed the connection]
ymwm_ has joined #rust-embedded
neceve has joined #rust-embedded
ymwm_ has quit [Remote host closed the connection]
ymwm_ has joined #rust-embedded
ymwm_ has quit [Remote host closed the connection]
ymwm_ has joined #rust-embedded
ymwm_ has quit [Remote host closed the connection]
ymwm_ has joined #rust-embedded
ymwm_ has quit [Ping timeout: 250 seconds]
richardeoin has quit [Ping timeout: 256 seconds]
richardeoin has joined #rust-embedded
neceve has quit [Ping timeout: 240 seconds]
hen6003 has quit [Remote host closed the connection]
hen6003 has joined #rust-embedded
hen6003 has quit [Remote host closed the connection]