Dániel Buga comments

Results 578 comments of


                                            Dániel Buga

Analyze and improve public APIs for most common peripheral drivers

I'm picking up GPIO

HIL tests fail on H2 with probe-rs 0.24.0

Please retry with https://github.com/probe-rs/probe-rs/pull/2547

HIL tests fail on H2 with probe-rs 0.24.0

Interesting, I'm not aware of relevant changes, but I'll take it :D

When using cmsis-dap + jtag + riscv, probe-rs reports `The selected probe does not support the 'RISC-V' interface.`

What probe are you trying to use? This error sounds like the probe itself does not report JTAG compatibility.

When using cmsis-dap + jtag + riscv, probe-rs reports `The selected probe does not support the 'RISC-V' interface.`

But which cmsis-dap? What is the exact model?

When using cmsis-dap + jtag + riscv, probe-rs reports `The selected probe does not support the 'RISC-V' interface.`

Okay nevermind, looks like `JTAGAccess` needs to be implemented for cmsis_dap, and also the `try_get_XX` functions at least.

When using cmsis-dap + jtag + riscv, probe-rs reports `The selected probe does not support the 'RISC-V' interface.`

Yes (well there are two functions, `has_riscv_interface` and `try_get_riscv_interface_builder`) and if you'd do that I'd ask you to add the xtensa bits as well, it should be fairly easy once...

Validate that flash algos can be constructed

The test fails because `stm32l4r9i_eval` is at least 29K, and uses 4K pages, which is more than what the target has in a single region. This failure can be fixed...

Upgrade to defmt-decoder v0.4.0

Why does this need a changelog entry (besides the mindless workflow that complains)? Does this have any user-facing changes, or does it break wire protocol compatibility?

Generic riscv chip via JTAG uses ARM driver

I'm inclined to remove or rename `probe-rs info`. It's just not useful for anything non-ARM currently (even if some other chips may have coresight compatible components). `info` is very brute-force,...