ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
starblue1 has quit [Ping timeout: 252 seconds]
starblue1 has joined #rust-embedded
konkers[m] has joined #rust-embedded
<konkers[m]> I'm writing a crate that I want to be ergonomic in std and no_std environments. Are there best practices for supporting both defmt and log logging?
i509vcb[m] has joined #rust-embedded
<i509vcb[m]> Define a set of internal log macros and select which one to use based on the presence of features?
<i509vcb[m]> I'm definitely having fun looking at the preliminary stuff for another rust device port (the CC1352 because I find it interesting having concurrent sub-1GHz and 2.4GHz radios on the same device).
<i509vcb[m]> However TI decided we needed another layer of conversion (I take the SVDs normally and move those to chiptool) so they needed to also throw a custom XML format to describe their chips as well.
<i509vcb[m]> Always a bit more fun where I didn't expect it...
jasperw- has quit [Read error: Connection reset by peer]
RockBoynton[m] has joined #rust-embedded
<RockBoynton[m]> <i509vcb[m]> "I'm definitely having fun..." <- > <@i509vcb:matrix.org> I'm definitely having fun looking at the preliminary stuff for another rust device port (the CC1352 because I find it interesting having concurrent sub-... (full message at
jasperw has joined #rust-embedded
<RockBoynton[m]> <konkers[m]> "I'm writing a crate that I..." <- you're in luck! https://github.com/t-moe/defmt-or-log
<i509vcb[m]> Never a good sign when your best option for data is parsing vendor PDF datasheets...
<i509vcb[m]> Well for some data
<i509vcb[m]> For very good reason I don't trust myself manually copying pin assignments for 6 packages
<RockBoynton[m]> i509vcb[m]: https://github.com/dhoove/tixml2svd
<i509vcb[m]> RockBoynton[m]: Yeah I did see that
<i509vcb[m]> And really I only need to do it once since it will then immediately get chiptool'd
sugoi has quit [Ping timeout: 246 seconds]
diondokter[m] has joined #rust-embedded
<diondokter[m]> <JamesMunns[m]> "Hey diondokter, if I wanted to..." <- Oh hey, didn't catch your message yesterday.... (full message at <https://catircservices.org/_irc/v1/media/download/AS6ODCh1Yl7qOP3yr5bsgX1mFbjP_rHPCkKzzVr8TC-kC37VZCYjWK_QwzK93dmpPj4pTN46jVQxMrNfJFl3f8xCeSFAj4AQAGNhdGlyY3NlcnZpY2VzLm9yZy9kaGZCR0poR2hTamFnYlprWGZsVXJrRnU>)
<diondokter[m]> Statime ultimately boils down to getting these Port Actions and then executing them on your system: https://docs.rs/statime/0.2.2/statime/port/enum.PortAction.html
sugoi has joined #rust-embedded
sugoi has quit [Ping timeout: 252 seconds]
sknebel has quit [Ping timeout: 248 seconds]
sknebel has joined #rust-embedded
mabez[m] has quit [Quit: Idle timeout reached: 172800s]
ivmarkov[m] has quit [Quit: Idle timeout reached: 172800s]
sugoi has joined #rust-embedded
sugoi has quit [Ping timeout: 244 seconds]
bpye has quit [Ping timeout: 252 seconds]
bpye has joined #rust-embedded
NiaLinaLunaStorm has joined #rust-embedded
<NiaLinaLunaStorm> I'm working on the firmware for my latest PCBs. While most pins work, I get the following error when trying to use pin pa15 and pb4 of the STM32F103 MCU.... (full message at <https://catircservices.org/_irc/v1/media/download/AaVdX7tN9ECuzmzv1TMjnIwMtYdQ1eSsK_xTOulgTVovFO89LoTzeuIGu7gGojC0SKi_ezHybBFBhWX3EMOJVPtCeSFY8VRAAGNhdGlyY3NlcnZpY2VzLm9yZy9HSlRyTXJ1UHRxR2hpZGhNaHlrTGhkdnU>)
<NiaLinaLunaStorm> how do I get it to let me use those pins?
starblue1 has quit [Ping timeout: 252 seconds]
M762spr[m] has quit [Quit: Idle timeout reached: 172800s]
sugoi has joined #rust-embedded
sugoi has quit [Ping timeout: 248 seconds]
starblue1 has joined #rust-embedded
sugoi has joined #rust-embedded
GrantM11235[m] has joined #rust-embedded
AtleoS has quit [Ping timeout: 260 seconds]
AtleoS has joined #rust-embedded
<NiaLinaLunaStorm> thanks
<NiaLinaLunaStorm> I still struggle to make use of the pin
<NiaLinaLunaStorm> with a similarily confusing error message
<NiaLinaLunaStorm> I can use it as normal IO pin but trying to make it a PWM pin fails
<GrantM11235[m]> I'm not sure that the hardware supports using PA15 as a pwm output
s1syph0s[m] has quit [Quit: Idle timeout reached: 172800s]
AtleoS has quit [Ping timeout: 252 seconds]
AtleoS has joined #rust-embedded
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #rust-embedded
<NiaLinaLunaStorm> it does, eventually figured it out that it has to do with remapping of stuff
pbsds3 has quit [Quit: The Lounge - https://thelounge.chat]
starblue1 has quit [Ping timeout: 246 seconds]
pbsds3 has joined #rust-embedded
sleepy_cat has joined #rust-embedded
starblue1 has joined #rust-embedded
sleepy_cat has quit [Quit: Client closed]
catsrule has joined #rust-embedded