27 Jan 2023 |
@slushee.:matrix.org | Do you know any way to stop probe-run without stopping the program from running on the pico? Often times I just Crtl+C the terminal but that crashes the program on the pico | 14:40:04 |
@slushee.:matrix.org | In reply to @slushee.:matrix.org if I needed precise time I could use the rtc RTC does give accurate time | 17:39:25 |
jannic | In reply to @slushee.:matrix.org Do you know any way to stop probe-run without stopping the program from running on the pico? Often times I just Crtl+C the terminal but that crashes the program on the pico I had a quick look at the source code. It looks like there is no way, probe-run will always do a core.halt() when you hit Ctrl+C. | 19:07:34 |
jannic | You should have better luck with cargo-embed or probe-rs-cli . | 19:18:56 |
@slushee.:matrix.org | Will try, thanks! | 19:44:14 |
@slushee.:matrix.org | * Will try, thanks! @jannic | 19:44:22 |
@slushee.:matrix.org | * Will try, thanks @jannic! | 19:44:32 |
| @slushee.:matrix.org left the room. | 22:08:58 |
| Slushee joined the room. | 22:15:03 |
28 Jan 2023 |
| playback2396 joined the room. | 09:42:40 |
Slushee | In reply to @jannic:matrix.org You should have better luck with cargo-embed or probe-rs-cli . I made it work with cargo embed! | 14:01:03 |
Slushee | I have one issue though: | 14:01:10 |
Slushee |  Download image.png | 14:01:13 |
Slushee | I can use the cargo embed just fine, but if I try to do it the regular way it doesn't want to work | 14:01:37 |
Slushee |  Download image.png | 14:02:10 |
Slushee | it seems like running cargo run runs cargo embed target/thumbv6m-none-eabi/debug/sevenseg_testing . Is there any way I can make it run cargo embed default instead? | 14:03:55 |
Slushee | also, I saw cargo-embed can do input, do you know by any chance how to use that? | 14:05:06 |
| Andelf changed their display name from Mono | Parami to Andelf. | 15:18:25 |
jannic | I don't have much experience with cargo-embed. If the docs at https://github.com/probe-rs/probe-rs/tree/master/cargo-embed#configuration don't help, l doubt l can add much to it. Regarding using rtt for providing inputs to the target device, I'd see if https://docs.rs/rtt-target/latest/rtt_target/ contains some hints. (Sorry if that's sounding like "RTFM", but l just don't know the answers myself) | 20:25:11 |
Slushee |
Sorry if it sounds like "RTFM"
No, not at all! Thank you for pointing me the right way :) I always read the docs before asking, but sometimes I don't know which docs to read :P | 22:00:35 |
29 Jan 2023 |
9names | i usually set up probe-rs-cli as my runner, and manually invoke cargo embed when i want that | 06:07:49 |
9names | don't see much benefit of setting embed as the runner, you're only saving 2 keystrokes and you can just alias it if you're concerned about that | 06:08:38 |
Slushee | In reply to @9names:matrix.org don't see much benefit of setting embed as the runner, you're only saving 2 keystrokes and you can just alias it if you're concerned about that 100% true, I use just so I was using aliases anyways. | 11:37:27 |
Slushee | In reply to @9names:matrix.org i usually set up probe-rs-cli as my runner, and manually invoke cargo embed when i want that I'll check out probe-rs-cli too then :) | 11:38:05 |
Slushee | Thanks for everything! | 11:38:13 |
ub|k | question about PIO: if I have two gpio pins: one set and one sideset, how should I set PINDIRS? SET PINDIRS only affects pins on SET_BASE? | 22:46:53 |
ub|k | i find this part really confusing | 22:47:02 |
ub|k | * question about PIO: if I have two gpio pins: one out and one sideset, how should I set PINDIRS? SET PINDIRS only affects pins on SET_BASE? | 22:54:10 |
30 Jan 2023 |
jannic | You can't set the direction of side set pins dynamically from within the PIO program. (Well, or you can, if the SIDE_PINDIR flag is set, but then you can only set pin direction, not the output value.) So what you usually do is calling set_pindirs before starting the state machine. | 20:32:28 |
jannic | BTW, why do the docs of that method say "The user has to make sure that they do not select any pins that are in use by any other state machines of the same PIO block."? AFAIK it's not forbidden to write to the same pin from multiple state machines? There's section 3.5.6.1. "Output Priority" in the datasheet that specifies what happens if multiple state machines use the same pin concurrently. Is there something that forbids such a concurrent use for side_set? | 20:36:38 |