<firefrommoonligh>
I am in the initial investigation phase. I will probably prototype this using ESP-Hosted, as I already have the HCI interface working, so can focus on the business logic. Once that works, I will try to integrate it into nRF, maybe. If I want to do that, then I weigh how easy it would be to integrate one of the two libraries you listed, or anything else.
<firefrommoonligh>
I swear, I don't go into things trying to redo work! But sometimes it can be easier to do so than integrate something that doesn't fit
<firefrommoonligh>
At least once you have an HCI channel open, there is no integration trouble due to it being a universal standard
ska has joined #rust-embedded
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #rust-embedded
ska has quit [Ping timeout: 260 seconds]
_whitelogger has joined #rust-embedded
ksvr[m] has quit [Quit: Idle timeout reached: 172800s]
<Emkanea[m]>
<okhsunrog[m]> have you considered using device-driver crate in your driver?
<Emkanea[m]>
I havent at the time but I will look into it
Darius has quit [Read error: Connection reset by peer]
Darius has joined #rust-embedded
sroemer has joined #rust-embedded
sroemer has quit [Changing host]
sroemer has joined #rust-embedded
SosthneGudon[m] has quit [Quit: Idle timeout reached: 172800s]
M9names[m] has quit [Quit: Idle timeout reached: 172800s]
_whitelogger has joined #rust-embedded
Ralph[m] has quit [Quit: Idle timeout reached: 172800s]
zeenix[m] has quit [Quit: Idle timeout reached: 172800s]
Sonder has quit [Remote host closed the connection]
Sonder has joined #rust-embedded
ska has joined #rust-embedded
<thejpster[m]>
Sometimes I want to write about embedded topics, but not so badly that it's worth getting out an IDE and adding a blog post to my statically generated site.
<thejpster[m]>
it's literally empty right now, but expect pages about every major kind of microcontroller peripheral, every major SoC vendor/family, popular Rust Embedded crates, etc.
<firefrommoonligh>
Great stuff! I'm not sure which topics you favor, but one area stands out to me that I think the embedded community might benefit from: Seeing example projects. So, it might be interesting to hear about some of yours on that blog! This has the obvious challenge of public projects being the tip of the ice berg.
<firefrommoonligh>
For example, my latest projects are for work and are on a non-public subject, so I can't post details e.g. "Look at this cool rust project/here's how to do XYZ in rust embedded", but I think that sort of content is both very useful to anyone considering rust in this domain, and something I haven't seen much of
<firefrommoonligh>
(I'm aware of a few examples like Dirbaio's smart locks, and some sort of quantum processor (?) that (maybe you?) worked on)
<firefrommoonligh>
And I've Bluskied briefly about my UAS firmware and AHRS, but haven't written much
apirkle has joined #rust-embedded
<JamesMunns[m]>
<firefrommoonligh> (I'm aware of a few examples like Dirbaio's smart locks, and some sort of quantum processor (?) that (maybe you?) worked on)
<JamesMunns[m]>
Are you thinking of Stabilizer from the Quartiq folks?
<firefrommoonligh>
Yes
<firefrommoonligh>
I'm having a hard time getting my head around what that project does. An analog computer of some sort to solve differential equations?
jfsimon has quit [Ping timeout: 265 seconds]
jfsimon has joined #rust-embedded
jfsimon has quit [Remote host closed the connection]
<danielb[m]>
dngrs[m]: watch out before they rename their lineups cortex-arM, cortex-aRm, cortex-Arm
<dngrs[m]>
you can fit 3 bits into that side channel, that's not nothing
<thejpster[m]>
<whitequark[cis]> oh, this is a very useful wiki
<thejpster[m]>
I look forward to your answers to the account qualifying questions
<i509vcb[m]>
Wait until you have to describe the new branding lol
<thejpster[m]>
<dngrs[m]> you can fit 3 bits into that side channel, that's not nothing
<thejpster[m]>
At some point someone will have to work out what to call the Armv8-R AArch64 target (the Armv8-R AArch32 target is called `armv8r-none-eabihf`, but Armv8-R AArch64 does not use EABI and does not execute the same instructions as any other arm* target).
<whitequark[cis]>
ha
Pete[m]1 has quit [Quit: Idle timeout reached: 172800s]