07:28 <re_irc> <raphi ⚡️> is it possible, to define an own arm-gcc to use for cross compilation? There are a lot of pages discriping how to set the linker or cc for a target. But none of this works on my machine (Windows 10, i tried a lot of arm targets)

08:22 <re_irc> <raphi ⚡️> * use own arm-gcc

08:50 <re_irc> <raphi ⚡️> http://blog.rust-embedded.org/2018-08-2x-psa-cortex-m-breakage/ => is Option A still possible?

09:30 <re_irc> < (@ryan-summers:matrix.org)> I don't see why this wouldn't be possible. flip-link does exactly this to accomplish its task

09:30 <re_irc> < (@ryan-summers:matrix.org)> Ref: https://github.com/knurling-rs/flip-link

12:51 <re_irc> < (@amanda:graven.dev)> The ESP32 dev boards I ordered finally showed up :D

12:53 <re_irc> < (@amanda:graven.dev)> https://psion.agg.io/_matrix/media/r0/download/graven.dev/ionjPBzRAYJuYttWqdnYtoOM/IMG_20221102_135154.jpg

12:54 <re_irc> < (@amanda:graven.dev)> It's been almost 5 years since I last messed with electronics/hardware stuff, I'm looking forward to getting back into it

12:54 <re_irc> < (@mabez:matrix.org)> : Come hang out in https://matrix.to/#/#esp-rs:matrix.org :)

12:54 <re_irc> < (@amanda:graven.dev)> Oh neat, hadn't seen that room, thanks for pointing it out :)

12:55 <re_irc> < (@amanda:graven.dev)> Ah, it's not in the space, that's probably why

12:56 <re_irc> < (@amanda:graven.dev)> Oh wait yes it is

12:57 <re_irc> < (@aktaboot:tchncs.de)> which space ? 🤔

12:58 <re_irc> < (@amanda:graven.dev)> #rust-embedded-space:matrix.org (https://matrix.to/#/#rust-embedded-space:matrix.org) this one

12:58 <re_irc> < (@amanda:graven.dev)> Which is a subspace of the main #rust-space:matrix.org (https://matrix.to/#/#rust-space:matrix.org) space

12:58 <re_irc> < (@aktaboot:tchncs.de)> thanks !

13:03 <re_irc> < (@mabez:matrix.org)> : TIL about spaces on matrix, thanks!

18:46 <re_irc> < (@firefrommoonlight:matrix.org)> I feel like I'm going to have to learn to program for ESP eventually, unless/until Nordic sorts out their WiFi plan

18:49 <re_irc> < (@orclev:matrix.org)> I've been thinking about it. I've got a nRF52840 I've been poking at, but so far I've been hesitant to start playing around with SoftDevice, and I'm not aware of a fully functioning pure rust BLE stack I could use on it instead. Another option I've thought about is trying to use one of the u-blox connextXpress modules which expose things over an AT command API.

18:52 <re_irc> < (@orclev:matrix.org)> Someone else was at least already leaning that way it looks like as I found this: https://github.com/BlackbirdHQ/ublox-short-range-rs

18:55 <re_irc> < (@dirbaio:matrix.org)> that's wifi, not BLE

18:56 <re_irc> < (@dirbaio:matrix.org)> for BLE from Rust the best supported way is nrf52 + nrf-softdevice

18:56 <re_irc> < (@orclev:matrix.org)> yeah, but I believe they also have BLE u-blox modules with a similar AT command interface

18:56 <re_irc> < (@dirbaio:matrix.org)> AT commands are a giant world of pain :D

18:57 <re_irc> < (@dirbaio:matrix.org)> > and I'm not aware of a fully functioning pure rust BLE stack

18:57 <re_irc> and yeah, this doesn't exist (yet?)

18:57 <re_irc> < (@orclev:matrix.org)> I did some brief research and it looked like there's a couple BLE crates already, but they're very alpha level

18:58 <re_irc> < (@orclev:matrix.org)> nrf-softdevice is the bit that I haven't gotten up the motivation to start poking around at yet. That's probably the next thing I'll do after I finish getting these PRs squared away for the sharp-memory-display crate

20:33 <re_irc> < (@chrysn:matrix.org)> the softdevice is ok-and-functional from rust. not greatly idiomatic,but then again it's pretty decent for a closed-source C API wrapped.

20:35 <re_irc> < (@chrysn:matrix.org)> i'd love to give wrapping the nimble library a more thorough try (all i've done so far was using it through its C API, which went OK), but currently I'm on softdevice for external reasons.

20:36 <re_irc> < (@chrysn:matrix.org)> orclev: ^

20:36 <re_irc> < (@chrysn:matrix.org)> orclev: ^

20:49 <re_irc> < (@orclev:matrix.org)> I'll probably play around with nrf-softdevice this weekend or maybe next weekend. I'm planning on using it with RTIC so I'll be interested to see how well those play together since it includes this warning in the readme:

20:49 <re_irc> > There's two common mistakes to avoid: (temporarily) disabling the softdevice's interrupts, and running your interrupts at too high priority.

20:49 <re_irc> > DO NOT disable the softdevice's interrupts. You MUST NOT use the widely-used cortex_m::interrupt::free for "disable all interrupts" critical sections.

20:49 <re_irc> and

20:49 <re_irc> and I can see in the generated code for RTIC that it uses "cortex_m::interrupt::free()"

20:53 <re_irc> < (@chrysn:matrix.org)> that's one of the reasons i don't like the softdevice too much (the other being the license). but RTIC doing critical sections surprises me: i thought it'd be its point not to do that, but rather to change the interrupt level (which, on softdevice, should just not happen up to its reserved level).

20:55 <re_irc> < (@orclev:matrix.org)> I think it _mostly_ does that in the initialization sections, I don't know that it uses it once everything is actually up and ticking along normally

20:58 <re_irc> < (@orclev:matrix.org)> hmm, looks like it does something or other with the software tasks. E.G. I'm using SWI_EGU0 as my dispatcher interrupt and I see this chunk of generated code:

20:58 <re_irc> match task {

20:58 <re_irc> SCHED_T::clear_display => {

20:58 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/Dw6QJQZZFSk9A7yj2IZ1D4XfPfKaTZDi (14 lines)

20:58 <re_irc> rtic::export::interrupt::free(|_| {

21:00 <re_irc> < (@orclev:matrix.org)> looks like that's inside of the generated handler for the timer task, which I guess makes sense

21:00 <re_irc> < (@orclev:matrix.org)> still, it does have several instances of using that function which it the readme is to be believed will cause problems

21:06 <re_irc> < (@orclev:matrix.org)> * if

22:54 <re_irc> < (@diondokter:matrix.org)> Give me money and I will make you all a BLE stack in async Rust 😉

23:26 <re_irc> < (@jamesmunns:beeper.com)> : How much money? Yes.