RTT logging, probe-run #358
Conversation
jordens
commented
May 13, 2021
jordens
commented
- use rtt logging
- remove rtt feature
- update hitl script
- README: streamline docs a bit, add probe-run
- CHANGELOG: update
- README: document lockin, cleanup instructions, use probe-run
- set target-cpu=cortex-m7, MSRV 1.52.0, use probe-run
github-actions
bot
added
the
changes-hitl
|
bors try |
1 similar comment
|
bors try |
|
bors try Bors doesn't look very cooperative today. HITL results are at https://github.com/quartiq/stabilizer/runs/2574636512?check_suite_focus=true |
| @@ -1,15 +1,10 @@ | |||
| [target.'cfg(all(target_arch = "arm", target_os = "none"))'] | |||
| runner = "gdb-multiarch -q -x openocd.gdb" | |||
| runner = "probe-run --chip STM32H743ZITx --speed 30000" | |||
There was a problem hiding this comment.
Does probe-run spin up a GDB server as well? Or is this just a command to program the chip?
There was a problem hiding this comment.
In general, I'd prefer if we kept around an easy way to spin up GDB, which was previously cargo run. The command-line way to flash was previously just cargo embed --bin dual-iir, and cargo run --bin dual-iir was meant for interactive debug
There was a problem hiding this comment.
There are still two ways to flash and while still getting gdb access as before. Just the command to start gdb changes.
- Start
cargo embedwith options to provide the gdb stub (https://github.com/probe-rs/cargo-embed/blob/master/src/config/default.toml#L71) or startopenocdas before. cargo build --release --bin app && gdb-multiarch -q -x openocd.gdb path/to/appto build and start gdb.
You can still use cargo embed to flash in the same way. That doesn't change. The command to start GDB becomes a bit longer.
The tooling for GDB+openocd is (a) significantly more complex to install (b) we don't test it, (c) doesn't provide usable logging, and (d) it isn't used as frequently compared to "just" flashing. Therefore I'd rather have a low entry barrier, streamlined runner that gives me backtraces and convenient logging for debugging.
There was a problem hiding this comment.
Ah, probe-run gives a logging interface. That's no issue - I can get gdb set up locally or see if I can make a custom cargo profile or something.
There was a problem hiding this comment.
A cargo profile might be nice for gdb.
* origin/master: remove unused dependencies remove unused dependencies
|
bors merge |
|
Build succeeded: |
