14:43 <re_irc> <@moerk:matrix.org> What is the preffered way to do state machine?

14:44 <re_irc> <@newam:matrix.org> If you don't need performance just a giant `match`

14:45 <re_irc> <@newam:matrix.org> You can make an enum with custom `next` methods or whatever to make the transitions clear.

16:21 <re_irc> <@ryan-summers:matrix.org> Use a crate like smlang

16:22 <re_irc> <@ryan-summers:matrix.org> It allows you to quickly define the state and all necessary events + transitions and makes it a hell of a lot cleaner than a giant match

18:44 <re_irc> <@sourcebox:matrix.org> So I got RTT working via rtt_target. Initially I wanted to use the existing rtt_logger quote, but this doesn't work and is obviously unmaintained. No repo also. So I put together my own version of it. Of course, I have to find a different name for it now. Any ideas?

19:18 <re_irc> <@dirbaio:matrix.org> rtt_logger does work..

19:21 <re_irc> <@sourcebox:matrix.org> But it's already taken at crates.io. Or does rtt-logger refer to a different crate?

19:22 <re_irc> <@sourcebox:matrix.org> Because the hyphen is normally replaced by underscore.

19:27 <re_irc> <@sourcebox:matrix.org> Can shorten it to rtt_log

19:36 <Lumpio-> Maybe I should just add log support to rtt-target directly finally

19:36 <re_irc> <@sourcebox:matrix.org> That would be the best option.

19:37 <re_irc> <@sourcebox:matrix.org> Do you want to have a look at my code? It's not very much.

19:38 <re_irc> <@ryan-summers:matrix.org> We definitely use rtt-logger all the time

19:39 <re_irc> <@sourcebox:matrix.org> The existing one?

19:39 <re_irc> <@ryan-summers:matrix.org> Hmm, never mind, we use `rtt-target` directly because we have to wrap our own logger for interrupt context stuff

19:40 <re_irc> <@sourcebox:matrix.org> rtt-target works well.

19:43 <re_irc> <@sourcebox:matrix.org> Having a working logger crate or direct support within rtt-target would make switching between different loggers very simple - just one line of code has to be changed to init the desired logger.

20:00 <re_irc> <@sourcebox:matrix.org> Ok. I've put this on GitHub if anyone is interested: https://github.com/sourcebox/rtt_log-rs

20:14 <Lumpio-> I always talk about I should do this should do that but never get around to it heh

20:20 <re_irc> <@sourcebox:matrix.org> Should I publish this on crates.io?

20:21 <re_irc> <@sourcebox:matrix.org> Because when you're going to implement it directly, it is rather pointless.

20:22 <re_irc> <@ryan-summers:matrix.org> Why not just PR it into `rtt-target` instead?

20:23 <re_irc> <@newam:matrix.org> Maybe with `log = { version = "0.4", optional = true }`?

20:23 <re_irc> <@newam:matrix.org> Log does add a bit to compile times if I recall correctly.

20:23 <re_irc> <@ryan-summers:matrix.org> Yeah, seems like a feature would be easy

20:25 <re_irc> <@ryan-summers:matrix.org> But ultimately it's your code :)

20:26 <re_irc> <@sourcebox:matrix.org> I would like to leave it up to Lumpio-, I'm sure he has some ideas own his own to integrate it.

20:26 <re_irc> <@ryan-summers:matrix.org> I think he was pointing out that he's probably too busy to get around to it, and I empathize with him :P

20:26 <re_irc> <@ryan-summers:matrix.org> But again, your choice

20:27 <Lumpio-> Busy? Lazy!

20:27 <re_irc> <@ryan-summers:matrix.org> Fair enough

20:28 <re_irc> <@sourcebox:matrix.org> Lumpio-: my crate is just one file. You take the lib.rs, change it to logger.rs or similar and adapt it to your like.

20:39 <re_irc> <@ryan-summers:matrix.org> I think you'd be much more persuasive with a PR where he can say ök";)

21:13 <Lumpio-> I had weird ideas about channels and auto init and whatnot but

21:14 <Lumpio-> I guess really most people just want rprintln

21:14 <Lumpio-> (via log or not)

21:24 <re_irc> <@sourcebox:matrix.org> Another thing. I get the RTT messages via probe-run on the console, but VS Code with cortex-debug complains about symbol _SEGGER_RTT not found.

21:26 <re_irc> <@sourcebox:matrix.org> Workaround is to specify the address manually. Where do I get this information?

21:41 <re_irc> <@newam:matrix.org> sourcebox:matrix.org: I think the magic is `nm --demangle --numeric-sort path/to/your/elf`

21:42 <re_irc> <@sourcebox:matrix.org> Will the symbol always have the same address?

21:42 <re_irc> <@newam:matrix.org> no

21:44 <re_irc> <@newam:matrix.org> Generally you do something like this to find the symbol:

21:44 <re_irc> <@newam:matrix.org> ```rs

21:44 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/4e4a5f4550a73faad6c100a57876e2814f4cef67d1e9c926330b93e6eabcd378 (20 lines)

21:44 <re_irc> <@newam:matrix.org> use object::{Object, ObjectSymbol};

21:44 <re_irc> <@newam:matrix.org> fn rtt_region() -> anyhow::Result<probe_rs_rtt::ScanRegion> {

21:45 <re_irc> <@sourcebox:matrix.org> The symbol exists in the ELF file.

21:46 <re_irc> <@sourcebox:matrix.org> I don't want to deal with this, it's the job of the VS Code extension.

21:47 <re_irc> <@newam:matrix.org> Yeah, that above code finds the symbol from the ELF

21:47 <re_irc> <@sourcebox:matrix.org> If probe-run can do it, the extension should also.

21:47 <re_irc> <@newam:matrix.org> if the extension is broke it shouldn't be hard to fix, it's just iterating over symbols