Tyler Holmes
Tyler Holmes
@ahcm both seeing the top and having y start at 0 should now be possible with #33 merged
My bet is the qemu model has just implemented the `calib` register wrong. Could you check `is_precise`? perhaps qemu agrees that the value returned by `calib` is wrong
some context: https://github.com/rust-embedded/cortex-m/pull/235#issuecomment-662046920 / #235
I tested the cycle count comparison functionality on HW to make sure this all worked as expected. I'm not sure how to test the address compare functionality on HW so...
Thoughts @tmplt ?
I made all of the `DWT::has_*` implementation feature checks associated functions instead of methods (they no longer take `&self`) per [this comment](https://github.com/rust-embedded/cortex-m/issues/183#issuecomment-579430492) as it allows me to check `has_cycle_counter` in...
I also tried to be fancy by wrapping these two slightly different comparators in a unified struct which then vended the right one by implementing the `Index` trait, however it...
Actually.. I suppose I could still implement `Index` where I return the type `Result` where `ComparatorTypes` is an enum: ```rust enum ComparatorTypes { NoCycleCount(Comparator), WithCycleCount(Comparator), ``` thoughts?
In that case this should be ready to review and merge