# Meeting notes

## 09.05.2024

### Agenda
- New probe-rs release (for real now)

## 02.05.2024

### Agenda
- New probe-rs release

### Notes
- We will release during next week's call
- Need to synch release with webpage docs as well as VSCode extension.

## 25.04.2024

### Agenda
- New probe-rs release

### Notes
- Hold release until next week - waiting for some PR's to merge.
- Approved and Merged #2411 (splitting binaries from lib), calling it `probe-rs-tools`

## 18.04.2024

### Agenda
- Last concerns regarding https://github.com/probe-rs/deprecated-placeholder
- License?
- Metadata?
- Cutting a new probe-rs release
- Binary/library split: https://github.com/probe-rs/probe-rs/pull/2364

### Notes

#### Binary / library split

- Motivation for split (tiwalun)
- Clearer in Cargo.toml (not 15 optional features)
- No duplicate compilation (with --features cli / without --features cli)
- subjective: rust-analyzer seems faster

- We should promote one single method of installation
- probe-rs-tools as crate name would be preferred, if we move binary to a new crate
- cargo-dist created installers should be preferred
- Keeping the binary in probe-rs crate would make the relation between binary and source clearer
- We should add a binary which fails to compile to probe-rs, so that users can be redirected to the right crate
- Mention cargo install for install from source
- cargo-dist has experimental support for updaters, might be worth looking into

- Should we publish to crate-io?
- allows usage of `cargo install probe-rs-tools`
- could be confusing

- name of the new binary crate
- probe-rs-tools
- probe-rs-bin(s?)

- for now, we are not planning on publishing to crates.io
- if we do, name should be discussed

#### place-holder crates

- same license as probe-rs ✅
- should we remove authors? ✅
- add crate for probe-rs-cli ✅
- add more people to the crate-owners team

## 11.04.2024

Meeting cancelled

## 04.04.2024

- Can everyone come or should we move it to Wednesday?

###

- Triaging

### Pre-meeting notes

- danielb questions/plans:
- Do we need the `rtt` feature?
- Not really
- Unify cargo flash and cargo embed

## 28.03.2024

Meeting cancelled

## 21.03.2024

### Agenda
- Objectives for this call
- Get to know each other
- Discuss big pain points, that might impact adoption?
- Issue triage?
- Integrating web page/docs with main repo?

- Financing
- bounties?
- purchasing chips to test?
- How do we get "boring" (noone has a personal/business stake/interest) issues done?

- Roadmap.

### Notes

#### What is everyone working on?

- tiwalun
- Debugger type handling
- RP2040 / CMSIS-DAP low-level
- low-level / high-level interface combination (https://github.com/probe-rs/probe-rs/issues/2285)
- danielb
- C debugging
- RTT code deduplicating
- trying to poke at various small bits and pieces I notice
- flashing perf
- dirbaio
- nothing actually WIP right now, I mostly hack on things that I personally find missing, I try to not leave them open forever
- nusb stuff, there's still a few issues left
- adam
- also nothing atm, generally cmsisdap related stuff
- jack
- Mostly debug related stuff
- Software breakpoints
- Unwind of (partially) optimized code
- More testing / test cases around current functionality
- Noah:
- Reviews
- Webpage
- Target Catalog
- debug probes
- autocompletion

#### What things still need doing in each section?

- cmsisdap
- improve batched/queued commands
- state of jtag support?
- rtt
- core section was merged for probe-rs run, but not added to other tools
- https://github.com/probe-rs/probe-rs/pull/2306
- what about rtthost?
- C debugging
- nested arrays are encoded differently
- several variables misdetected as something incorrect
- verifying probe max clocks (look at J-Link seemingly misbehaving), encode max clock freq for targets

#### Roadmap / new features

- network support? remote probe-rs or remote probes (AG)
- compressed custom flash algorithm for stm32s?
- unify `probe-rs run` and `cargo-embed`? (dirbaio, danielb)
- `probe-rs run <file> --probe-rs-args`
- `cargo probe-rs run --cargo-args -- --probe-rs-args`
- one runs the file, the other compiles and runs that, but both have the exact same functionality.
- what about rttui?
- both would have (optional probably) rttui. IMO RTTUI is nicer if you want to see multiple channels but is annoying if just one.
- rttui is also not very friendly to stderr output
- auto detect - run/configure (jack)
- target catalog (Noah)
- fix all bugs, merge all PRs!