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
glitchy has quit [Remote host closed the connection]
glitchy has joined #rust-embedded
_whitelogger has joined #rust-embedded
lethalbit has quit [Server closed connection]
lethalbit has joined #rust-embedded
M9names[m] has quit [Quit: Idle timeout reached: 172800s]
danielb[m] has quit [Quit: Idle timeout reached: 172800s]
limpkin has quit [Server closed connection]
limpkin has joined #rust-embedded
Noah[m]1 has joined #rust-embedded
<Noah[m]1> Are there people here using M33/M55/M85 cores already? With Rust. Are they any good? 🤔
<diondokter[m]> Noah[m]1: nRF54 is M33
<diondokter[m]> Afaic, most impactful thing is trustzone
<diondokter[m]> Not even sure what other changes there are aside from having more instructions
<diondokter[m]> Ah, hardware stack limit. That's pretty cool
<Noah[m]1> oh wait M33 has ETM, sick!
<Noah[m]1> probe-rs needs support asap :P
rainingmessages has quit [Quit: bye]
rainingmessages has joined #rust-embedded
<JamesMunns[m]> <diondokter[m]> nRF54 is M33
<JamesMunns[m]> RP2350 too
glitchy has quit [Remote host closed the connection]
glitchy has joined #rust-embedded
<diondokter[m]> <JamesMunns[m]> RP2350 too
<diondokter[m]> Ah! I thought maybe it was an M23
jasperw has quit [Server closed connection]
jasperw has joined #rust-embedded
<wassasin[m]> NXP i.MX RT600 is also M33
<wassasin[m]> cortex-m-rt has the set-msplim feature to check the stack limit on v8-mainline
<wassasin[m]> * cortex-m-rt has the set-msplim feature to set the stack limit on v8-mainline
Mathias[m] has joined #rust-embedded
<Mathias[m]> NXP LPC55 has Cortex-M33 and has had Rust support for a while. Cortex-M33 are also in Nordic nRF5340/nRF91, ST STM32L5/STM32H5/STM32U5.
thenightmail has quit [Changing host]
thenightmail has joined #rust-embedded
MartinSivk[m] has quit [Quit: Idle timeout reached: 172800s]
TomB[m] has quit [Quit: Idle timeout reached: 172800s]
mkj[m] has quit [Quit: Idle timeout reached: 172800s]
thalesfragoso[m] has quit [Quit: Idle timeout reached: 172800s]
<thejpster[m]> <Noah[m]1> Are there people here using M33/M55/M85 cores already? With Rust. Are they any good? 🤔
<thejpster[m]> No M55 or M85 hardware but I did analyse the machine code Rust produces in order to write the platform support page. Helium is incredible. The new loop instructions too.
<thejpster[m]> I’ve seen one or two M55 parts - Renesas have one I think, but no M85 parts. There is also the Arm Fixed Virtual Platform (FVP) software - it emulates a whole virtual SoC using Arm’s own architecture models (the so called fast-models).
<thejpster[m]> Oh Renesas have an M85. Last time I tried a Renesas chip it bricked itself so not in a hurry to try again.
RobWells[m] has joined #rust-embedded
<RobWells[m]> Does anyone know of a common SPI device that does full duplex communication (write to MOSI and read from MISO simultaneously)? I'm looking for something to test an implementation of eh::spi::SpiDevice::transfer against.
<Noah[m]1> <wassasin[m]> cortex-m-rt has the set-msplim feature to check the stack limit on v8-mainline
<Noah[m]1> ohh cool
<Noah[m]1> <thejpster[m]> No M55 or M85 hardware but I did analyse the machine code Rust produces in order to write the platform support page. Helium is incredible. The new loop instructions too....
<Noah[m]1> Oh sick! Wait Rust supports Helium?
<Noah[m]1> Or rather LLVM
<Noah[m]1> * rather LLVM I guess which makes sense
<Noah[m]1> I was eyeing the STM32 one actually :) Infinion or rather cypress has a psoc M55 with M33 coprocessor :)
<Noah[m]1> But I guess to use any of the ML features you kinda need C again
<Noah[m]1> https://www.st.com/en/microcontrollers-microprocessors/stm32n6-series.html would be very cool if you can actually embedd the AI stuff with rust, which seems possible for sure. The question is how much pain it is :P
<diondokter[m]> <RobWells[m]> Does anyone know of a common SPI device that does full duplex communication (write to MOSI and read from MISO simultaneously)? I'm looking for something to test an implementation of eh::spi::SpiDevice::transfer against.
<diondokter[m]> [@tamme:matrix.org](https://matrix.to/#/@tamme:matrix.org) is there something you can share about the HAL testing project? Not sure if you've touched SPI yet
<RobWells[m]> Thanks. Every SPI part I have is sequential write-then-read it seems. I misread the contract for transfer() initially (and implemented it sequentially) so it's mostly just to check I've got it right this time.
<whitequark[cis]> <RobWells[m]> Does anyone know of a common SPI device that does full duplex communication (write to MOSI and read from MISO simultaneously)? I'm looking for something to test an implementation of eh::spi::SpiDevice::transfer against.
<whitequark[cis]> nrf24l01
<whitequark[cis]> as you shift in a command, it always shifts out status. and it's cheap
<RobWells[m]> Great, thank you!
adamgreig[m] has joined #rust-embedded
<adamgreig[m]> you could just short MISO and MOSI together I suppose
<adamgreig[m]> and always read exactly what you transmitted
<RobWells[m]> That's great, thanks Adam.
vollbrecht[m] has quit [Quit: Idle timeout reached: 172800s]
jason-kairos[m] has quit [Quit: Idle timeout reached: 172800s]
tk has quit [Server closed connection]
tk has joined #rust-embedded
<thejpster[m]> <Noah[m]1> Oh sick! Wait Rust supports Helium?
ello- has joined #rust-embedded
ello has quit [Read error: Connection reset by peer]
ello_ has quit [Read error: Connection reset by peer]
ello has joined #rust-embedded
limpkin has quit [Quit: No Ping reply in 180 seconds.]