i509vcb[m] has quit [Quit: Idle timeout reached: 172800s]
richardeoin has quit [Remote host closed the connection]
richardeoin has joined #rust-embedded
sroemer has quit [Ping timeout: 252 seconds]
sroemer has joined #rust-embedded
sroemer has quit [Changing host]
sroemer has joined #rust-embedded
corecode[m] has quit [Quit: Idle timeout reached: 172800s]
chrysn[m] has quit [Quit: Idle timeout reached: 172800s]
EthanGardner[m] has joined #rust-embedded
<EthanGardner[m]>
If i have a bootloader application and i want to use rtt inside of the boot loader as well as the application that it loads how what would be the correct way to do that
<EthanGardner[m]>
SIngle RTT buffer it seems like the error comes from the following
<berkus[m]>
What if you enable disable-blocking-mode feature on defmt-rtt?
<EthanGardner[m]>
Looking at the repo now and don't see that flag available - and getting an error saying it doesn't have that feature
<berkus[m]>
hmm, I think every defmt-rtt you link into a binary will have its own rtt buffer
<berkus[m]>
so with two apps you look at two separate buffers
<berkus[m]>
and your host probably finds only one
<thejpster[m]>
You’d need to implement a new defmt transport that sent messages to your boot loader, I think.
<thejpster[m]>
Does anyone have any good USB Host examples, ideally on an RP2040?
Dlaw[m] has quit [Quit: Idle timeout reached: 172800s]
ben[m] has quit [Quit: Idle timeout reached: 172800s]
m5zs7k has quit [Ping timeout: 252 seconds]
m5zs7k has joined #rust-embedded
<JamesMunns[m]>
<thejpster[m]> "Does anyone have any good USB..." <- I think I've only seen usb host stack, it was the one for the 3d printer that used to be GPL, but they made the host stack MIT I think? I haven't seen anyone actually using it tho
<JamesMunns[m]>
btw, I know we've mentioned **Embedded World**, but I went ahead and put up a discussion topic if anyone else wants to sound off that they will be there, and want to arrange to meet up!
diondokter[m] has quit [Quit: Idle timeout reached: 172800s]
mabez[m] has quit [Quit: Idle timeout reached: 172800s]
kenny has quit [Quit: WeeChat 4.4.4]
kenny has joined #rust-embedded
dirbaio[m] has quit [Quit: Idle timeout reached: 172800s]
trreeaz[m] has quit [Quit: Idle timeout reached: 172800s]
n_vl[m] has quit [Quit: Idle timeout reached: 172800s]
sroemer has quit [Quit: WeeChat 4.4.2]
sroemer has joined #rust-embedded
sroemer has quit [Client Quit]
sroemer has joined #rust-embedded
bogdan[m] has quit [Quit: Idle timeout reached: 172800s]
ivmarkov[m] has quit [Quit: Idle timeout reached: 172800s]
<berkus[m]>
Hmmm, March
rafael[m] has joined #rust-embedded
<rafael[m]>
Is there any good no-std library for fusing sensor data? For my hobby-project tracked robot i implemented correction from data of motor encoders, as well as quaternion (using tilt and rotation mainly) for the drive task. As soon as i was done I realized that it will be not the brightest idea to have multiple independent corrections that will end up fighting each other. So I am looking to make a task that combines them and use only
<rafael[m]>
the fused data for correction. I have never done that before, but before I get my hands dirty: Do You know of any good library, that could be a good start? Either becauseit is ready to use or even if it is just a good thing to look at to get ideas. Thanks!
barafael[m] has quit [Quit: Idle timeout reached: 172800s]
<dngrs[m]>
the [main repo](https://github.com/pdh11/cotton/tree/main) links to quite a few examples (as opposed to the aforementioned docs.rs page which only mentions one crate), sadly they're all pretty much undocumented.
<sajattack[m]1>
hello friends. I am once again asking if there is any decent way to implement auto-instrumented timed-function-call performance tracing on mips
<sajattack[m]1>
I have gdb but not defmt
<sajattack[m]1>
nevermind I decided to just recompile for x86 and give up
Arne[m] has quit [Quit: Idle timeout reached: 172800s]
<berkus[m]>
on mips, jees, that thing probably doesn't even have perfcnt regs
jason-kairos[m] has joined #rust-embedded
<jason-kairos[m]>
Macros and a hardware timer
<jason-kairos[m]>
* Macros, some assembly and a hardware timer from your CPU