braincode[m] has quit [Quit: Idle timeout reached: 172800s]
Pete[m]1 has joined #rust-embedded
<Pete[m]1>
Finally figured out the right magic flags to get the linker --print-memory-usage output I've come to expect from Zephyr builds... Just means accepting a crapton of other linking log messages.
starblue has quit [Ping timeout: 260 seconds]
starblue has joined #rust-embedded
hmw has quit [Quit: Bye.]
hmw has joined #rust-embedded
glitchy has quit [Remote host closed the connection]
glitchy has joined #rust-embedded
Ralith has quit [Quit: Idle timeout reached: 172800s]
sroemer has joined #rust-embedded
sroemer has quit [Changing host]
sroemer has joined #rust-embedded
ska has quit [Ping timeout: 245 seconds]
cr1901_ has quit [Read error: Connection reset by peer]
GuineaWheek[m] has joined #rust-embedded
<GuineaWheek[m]>
if you're using rust you're probably already a programmer invested though; it will never be the fastest thing to scrape something together arduino-style
Koen[m] has quit [Quit: Idle timeout reached: 172800s]
wassasin[m] has quit [Quit: Idle timeout reached: 172800s]
leftger[m] has quit [Quit: Idle timeout reached: 172800s]
mkj[m] has quit [Quit: Idle timeout reached: 172800s]
ska has joined #rust-embedded
LeandroMarceddu[ has quit [Quit: Idle timeout reached: 172800s]
jakzale has quit [Server closed connection]
jakzale has joined #rust-embedded
<JamesMunns[m]>
btw, did a Self Directed Research episodes for some of the intrusive linked list stuff I've been using in `pinlist`, `ergot`, and `cfg-noodle`: https://www.youtube.com/watch?v=ct10kgmcFmE
<JamesMunns[m]>
IMO it's a very useful pattern for a lot of things, as an alternative to a lot of const generics, or when you want to split "the storage" and "the background or i/o worker"
<dngrs[m]>
(the arduino hardware is something I'm deeply uninterested in, I think it's overpriced, annoying to handle re flashing, and pretty outdated)
ouilemur has quit [Quit: WeeChat 4.7.0]
<RobinMueller[m]>
At my workplace, arduinos are commonly used for quick tests of hardware, both by students and by engineers. it can be really good for that task. would definitely not do anything non-trivial with them though, and now that I'm more familiar with Rust, i would just write these test scripts with an stm32 / rpi pico and I recommend that to anyone who asks me as well. I think at the very least, arduinos can make the topic of
<RobinMueller[m]>
learning MCU programming more approachable for beginners. I wonder if the IDE is still as awful as I remember it to be (I transitioned to platform IO at some point).
<RobinMueller[m]>
* some point, and now that I use embedded-rust, I just use CLI/neovim..).
<RobinMueller[m]>
* rpi pico/, * esp and I, * some point, and now that I use embedded-rust, I just use CLI/neovim..).
<RobinMueller[m]>
* At my workplace, arduinos are commonly used for quick tests of hardware, both by students and by engineers. it can be really good for that task. would definitely not do anything non-trivial with them though, and now that I'm more familiar with Rust, i would just write these test scripts for stm32 / rpi pico/ esp and I recommend that to anyone who asks me as well. I think at the very least, arduinos can make the topic of
<RobinMueller[m]>
learning MCU programming more approachable for beginners. I wonder if the IDE is still as awful as I remember it to be (I transitioned to platform IO at some point, and now that I use embedded-rust, I just use CLI/neovim..).
<RobinMueller[m]>
* At my workplace, arduinos are commonly used for quick tests of hardware, both by students and by engineers. it can be really good for that task. would definitely not do anything non-trivial with them though, and now that I'm more familiar with Rust, i would just write these test scripts for stm32 / rpi pico/ esp and recommend that to anyone who asks me as well. I think at the very least, arduinos can make the topic of
<RobinMueller[m]>
learning MCU programming more approachable for beginners. I wonder if the IDE is still as awful as I remember it to be (I transitioned to platform IO at some point, and now that I use embedded-rust, I just use CLI/neovim..).
glitchy has quit [Ping timeout: 245 seconds]
Lumpio[m] has joined #rust-embedded
<Lumpio[m]>
From having had to subject myself to the IDE last week, can confirm it's still terribad, and the official hardware is also still priced 4x what they're worth.
<Lumpio[m]>
Arduino Uno is the TI-83 of microcontroller boards, it just refuses to die
Mihael[m] has quit [Quit: Idle timeout reached: 172800s]
jason-kairos[m] has quit [Quit: Idle timeout reached: 172800s]
<thejpster[m]>
> I wonder if the IDE is still as awful as I remember it
<thejpster[m]>
That was probably Arduino IDE v1.x. There's now an Arduino IDE v2.x, which is also available as a Cloud IDE (which suggests it's now written in Javascript and not Java)
starblue has quit [Quit: WeeChat 3.8]
<RobWells[m]>
<thejpster[m]> > I wonder if the IDE is still as awful as I remember it...
<RobWells[m]>
I believe it’s a VSCode fork. It’s slightly more helpful than I remember v1 being but it’s not hugely different.
glitchy has joined #rust-embedded
drainiard has joined #rust-embedded
drainiard has quit [Quit: drainiard]
glitchy has quit [Remote host closed the connection]
glitchy has joined #rust-embedded
barafael[m] has quit [Quit: Idle timeout reached: 172800s]
BentoMon has quit [Remote host closed the connection]
dne has quit [Remote host closed the connection]
dne has joined #rust-embedded
BentoMon has joined #rust-embedded
dirbaio[m] has quit [Quit: Idle timeout reached: 172800s]
LachlanIkeguchi4 has quit [Quit: Idle timeout reached: 172800s]