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
AdamHorden has quit [Ping timeout: 256 seconds]
AdamHorden has joined #rust-embedded
barnabyw[m] has quit [Quit: Idle timeout reached: 172800s]
IlPalazzo-ojiisa has quit [Remote host closed the connection]
dngrs[m] has quit [Quit: Idle timeout reached: 172800s]
NiaLinaLunaStorm has quit [Quit: Idle timeout reached: 172800s]
<f0rte[m]> does anyone else have alignment issues when using `tio` with `esp-println`? If so, how did you fix it? I'm experiencing something like this (only by the println code, the bootloader code formats fine)... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/CdjeoaxYsGaCpzuKeZUUGYJm>)
<M9names[m]> Please don't cross-post, this is pretty clearly an esp specific question. Anyone in here likely to answer it is also going to be in esp-rs.
Guest7282 has left #rust-embedded [Error from remote client]
Guest7282 has joined #rust-embedded
RoyBuitenhuis[m] has joined #rust-embedded
<RoyBuitenhuis[m]> mabez: About that riscv32ima target. I suppose they implicitly asked me not to open the MCP to get it to tier 2. Do you know how to help the stabilization of Cargo build-std?
<RoyBuitenhuis[m]> * Cargo build-std? Not sure if there's something in the list of blockers I could help with.
AdamHorden has quit [Ping timeout: 252 seconds]
marmrt[m] has quit [Quit: Idle timeout reached: 172800s]
AdamHorden has joined #rust-embedded
thejpster[m] has quit [Quit: Idle timeout reached: 172800s]
ithinuel[m] has joined #rust-embedded
<ithinuel[m]> thejpster Adam Hott James Munns : https://www.seeedstudio.com/Grove-Vision-AI-Module-V2-p-5851.html is another occurrence of M55 in the wild.
Noah[m]12 has quit [Quit: Idle timeout reached: 172800s]
<mabez[m]> <RoyBuitenhuis[m]> "mabez: About that riscv32ima..." <- I'm not really familiar with cargo, and tbh I don't have the time to get familiar with it. It's probably worth checking the issue list ehuss mentioned in your PR and seeing whether they can be solved easily, or if they truly block stabilization or can be punted down the line
marmrt[m] has joined #rust-embedded
<marmrt[m]> that is a tiny MCU package
<JamesMunns[m]> you aren't kidding, the MCU is the long rectangle in the center there
IlPalazzo-ojiisa has joined #rust-embedded
gauteh[m] has quit [Quit: Idle timeout reached: 172800s]
starblue has quit [Ping timeout: 255 seconds]
AdamHott[m] has joined #rust-embedded
<AdamHott[m]> <ithinuel[m]> "thejpster Adam Hott James Munns..." <- The price is definitely right on that one.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/BnOTCEkVFUjYPIzxqVUnTRWg>)
starblue has joined #rust-embedded
starblue has quit [Ping timeout: 264 seconds]
<AdamHott[m]> If I take a soldering iron to a cable on the positive terminal of a battery, will that complete the circuit and short the battery?
<AdamHott[m]> s/complete the circuit and//
<marmrt[m]> As long as you don't touch the negative terminal with the solder iron at the same time it should be fine
<AdamHott[m]> ok thanks!
starblue has joined #rust-embedded
<Ecco> Hi! Here's an embassy question: why is the stm32-metapac not providing any registers for the Touch-Sensing Controller? https://docs.embassy.dev/stm32-metapac/git/stm32wba52cg/constant.TSC.html#
<dirbaio[m]> because no one has added it
<Ecco> oh cool
<Ecco> Will try and do it then :)
<Ecco> So I guess maybe all I need is to tell embassy-stm33 what touch-sensing IP this specific chip uses
<dirbaio[m]> check if the registers are the same as any of the v1/v2/v3
<dirbaio[m]> if they're not then you'll have to add v4
<Ecco> perfect
<Ecco> thanks!
Foxyloxy has quit [Quit: Textual IRC Client: www.textualapp.com]
Foxyloxy has joined #rust-embedded
Guest7282 has left #rust-embedded [Error from remote client]
almindor[m] has joined #rust-embedded
<almindor[m]> embedded-hal::serial is embedded-io now?
<dirbaio[m]> yep
<almindor[m]> is there a changelog/migration doc somewhere between 0.27 -> 1.0 ? I'm trying to bump e310x-hal but it's kinda confusing for things I'm not used to (e.g. I never did anything with the i2c abstractions)
<dirbaio[m]> see https://blog.rust-embedded.org/embedded-hal-v1/ , it has some overview and links to the migration guide
rom4ik has joined #rust-embedded
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #rust-embedded
Guest7282 has joined #rust-embedded
Guest7282 has left #rust-embedded [Disconnected: Replaced by new connection]
cr1901 has quit [Quit: Leaving]
cr1901 has joined #rust-embedded
kenny has quit [Quit: WeeChat 4.2.1]
avery71[m] has quit [Quit: Idle timeout reached: 172800s]
<f0rte[m]> <M9names[m]> "Please don't cross-post, this is..." <- 9names: I understand that the spray-and-pray method may seem annoying, but you may notice I waited two hours before cross posting, and despite this received no replies (besides yours) in either group. I think that would indicate that it's logical to do so if I want hope of some traction. Not really sure what the "better" alternative would be.
<f0rte[m]> * would be. Not that anyone "owes" me help, but the membership between groups are different, and the issue I'm experiencing, while I am assuming _may_ be esp-specific, may also not be.