<dirbaio[m]>
> Read linker script from file. If multiple linker scripts are given, they are processed as if they were concatenated in the order they appeared on the command line.
<dirbaio[m]>
(yep, command line flags inside command line flags 💀)
<dirbaio[m]>
* -C link-arg=whatever passes whatever as a command line flag to the linker
<cgc17[m]>
And no space between -T and link.x bc something else is parsing that out?
<dirbaio[m]>
no, the linker accepts both -T link.x and -Tlink.x
<dirbaio[m]>
space is usually optional in options that are single dash + single letter
<cgc17[m]>
ah cool I didn’t realize that. I let this be magic for a while, but it kept nagging me so thanks for explaining the pieces and linking to docs!
starblue has quit [Ping timeout: 265 seconds]
starblue has joined #rust-embedded
ryan-summers[m] has joined #rust-embedded
<ryan-summers[m]>
<thejpster[m]> ":tada: https://ferrous-systems...." <- Oh hoh hoh do I have some clients to inform
<ryan-summers[m]>
<sourcebox[m]> "Not a topic for the meeting, but..." <- If no one has gotten to it after next week, please re ping me. I'm currently swamped onsite with a client and don't have much time until I fly back home
igiona[m] has joined #rust-embedded
<igiona[m]>
<thejpster[m]> ":tada: https://ferrous-systems...." <- Fantastic! I hope this is going to be another asset for finally bringing Rust in our embedded systems (real once, not Linux embedded 🙈 )
FrreJacques[m] has quit [Quit: Idle timeout reached: 172800s]
<thejpster[m]>
Finally?
<thejpster[m]>
<bartmassey[m]> "That would be good! Let me..." <- You have mail ;)
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #rust-embedded
limpkin has joined #rust-embedded
LiamKinne[m] has quit [Quit: Idle timeout reached: 172800s]
fooker has quit [Ping timeout: 272 seconds]
corecode[m] has joined #rust-embedded
<corecode[m]>
i'm getting a disallow references to static mut lint now, in my interrupt handler that calls a callback (if it is `Some`). The callback by itself is `Box<dyn FnMut() + Send>`. What would be a more idiomatic way of doing this?
fooker has joined #rust-embedded
Dlaw[m] has joined #rust-embedded
<Dlaw[m]>
<corecode[m]> "i'm getting a disallow reference..." <- As far as I understand it, you can either use a raw mut pointer instead of a mut reference, or else change to a type with interior mutability and take a non-mut static reference
<Dlaw[m]>
Dlaw[m]: If you don't have control over the callback type, I'm not sure
<corecode[m]>
<Dlaw[m]> "If you don't have control over..." <- but what interior mutability can work inside interrupt context?
<corecode[m]>
corecode[m]: atomic maybe?
jduck[m] has quit [Quit: Idle timeout reached: 172800s]
<thejpster[m]>
I got a reply from Renesas. They said, no, they will not RMA my board.
<dirbaio[m]>
no Rust for them 🤷
ilhanben[m] has joined #rust-embedded
<ilhanben[m]>
Good morning guys, i see three thousands of people here. Thanks for today and for future !🚀
<thejpster[m]>
I had to type out the interrupt enum by hand having read the PDF datasheet, because I couldn't find an SVD file and I didn't really want to bring a PAC into my example. So it's possible I typed it wrong.
AlexandrosLiarok has joined #rust-embedded
<AlexandrosLiarok>
how should one approach making PRs for projects in the rust-embedded-community repos ?
<AlexandrosLiarok>
I have one for serde-json-core, last PR merge / commit was done 5 months ago.
<thejpster[m]>
fixing the interrupt numbers didn't fix it. I suspect i need to poke the UART harder to actually enable the interrupt
<JamesMunns[m]>
ahh, it's thumbv8m, I wonder if you have to do Weird Things for the NS/S stuff
<thejpster[m]>
I hope not
<dirbaio[m]>
on all chips i've seen (stm32, nrf) you can run on S mode and pretend trustzone doesn't exist
<dirbaio[m]>
but it's just because all peripherals+RAM defaults to S, which is vendor-specific I think
<thejpster[m]>
oh I see what I did
<thejpster[m]>
I fill up the ring buffer, but I never actually do the first manual transmit. The IRQ won't fire until the TX buffer has something in it and then goes empty
<dirbaio[m]>
you can also the irq to kickstart it instead of doing a tx manually
<dirbaio[m]>
nicer because it centralizes tx in a single place
<thejpster[m]>
i feel race hazards coming on
<thejpster[m]>
hey, i got interrupts
vancz has quit [Quit: No Ping reply in 180 seconds.]
vancz has joined #rust-embedded
<thejpster[m]>
ok, I ripped it all apart and added simplicity. Now it seems to work.
<thejpster[m]>
I decided to use an spsc buffer inside a Mutex rather than using an mpsc buffer and a Uart inside a Mutex
<dngrs[m]>
also I highly recommend the #esp-rs:matrix.org room if you have specific questions, lots of very helpful folk there
<HeapUnderflow[m]>
ahhh nice, i will check those out (missed them before :D)... tho i have also found at least one of the issues ive encountered until now, which was a typo (sdkconfig.default instead of sdkconfig.defaults, which builds the esp stuff without ble 🤦)
<HeapUnderflow[m]>
petekubiak[m]: i have not. from a first glance this seems to be alright? ill definetly giving it a go seeing as nimble is being a bit finnicky....
<HeapUnderflow[m]>
i really am only looking for pure scanning, i dont need any kind of connecting or pairing so... (tho it looks like the "central" example has that covered somewhat?)
<petekubiak[m]>
I've personally mainly been focused on the peripheral side, but yes I believe the central example does cover scanning.
<petekubiak[m]>
We're actively developing it with a focus on being user friendly so please do let us know what you'd like to see improved!