02:59 <i509vcb[m]> mspm0c1104 running Rust code. Seems like just toggling the LED pin appears to get to 3MHz but it does seem to work. Now for timers so I can see the blinking

13:19 <jduck[m]> <i509vcb[m]> "mspm0c1104 running Rust code..." <- > <@i509vcb:matrix.org> mspm0c1104 running Rust code. Seems like just toggling the LED pin appears to get to 3MHz but it does seem to work. Now for timers so I can see the blinking

13:19 <jduck[m]> >

13:19 <jduck[m]> I'm impressed!

18:15 <TomB[m]> <thejpster[m]1> "The Neotron BMC runs RTIC in 32K..." <- That's quite impressive tbh, zero string formatting involvement presumably?

18:20 <i509vcb[m]> I don't know why it is embedded which seems to just break rust-analyzer

18:20 <i509vcb[m]> Normally my laptop is cold but for some reason now it is very warm

18:34 <danielb[m]> rust-analyzer is a very hot piece of technology

18:37 <i509vcb[m]> I think it's probably the trying to have more than one workspace open at a time in a single window

18:39 <danielb[m]> it's more likely that your project has some slightly different configuration than what RA picks up, and it runs a lot more analysis than what you changed. You might want to try and tell it to use a different target folder

18:39 <vollbrecht[m]> RA should come with a system requirement label printed on startup like it was done on physical media.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/PlGFVsKVutybyWroDKJlFfIZ>)

18:40 <danielb[m]> Recommended RAM: not enough

18:40 <danielb[m]> * it's more likely that your project has some slightly different configuration than what RA picks up, and it runs a lot more analysis than what you changed. You might want to try and tell it to use a different target folder ("rust-analyzer.cargo.targetDir": "target/rust-analyzer",)

18:40 <vollbrecht[m]> also the classic is that RA builds against your host target

18:40 <vollbrecht[m]> and not your actual target

18:40 <vollbrecht[m]> well the ram is per process of RA. I mostly got more than one RA process running :D

18:41 <i509vcb[m]> Well it's too parts one part runs on the host (codegen) and the PAC/hal needs to be built for not the host

18:42 <danielb[m]> technically, it doesn't have to be :D you might get funky issues with inline assembly, or pointer width, but I've had pretty okay results with letting it do its thing with the host arch

19:12 <thejpster[m]1> <TomB[m]> "That's quite impressive tbh..." <- https://github.com/Neotron-Compute/Neotron-BMC/tree/main/neotron-bmc-pico