10:32 <re_irc> <barafael> calling for volunteers who own stm32l0/stm32l4 devices :) if you have some time, could you test if https://github.com/barafael/rtic-examples/tree/master/rtic_v1/stm32l0_monotonic and https://github.com/barafael/rtic-examples/tree/master/rtic_v1/stm32l4_heartbeat work and do the right thing? I ported them to RTIC v1 but cannot test as I don't have the hardware.

10:35 <re_irc> <burrbull> barafael: It would be much more better if you add those implementations to HALs directly.

10:36 <re_irc> <barafael> burrbull: they are all living inside rtic-examples repo and I just took them from v0.5 to v1. I'm just random contributor. Maybe the examples should be in the HALs, I don't know

10:37 <re_irc> <barafael> but I think may be good to have one place with some RTIC examples on different targets

10:39 <re_irc> <burrbull> usage examples yes, but they should not content monotonic implementations which must be in hals

10:49 <re_irc> <barafael> ok, good point. So the monotonic impls should go in the HALs behind some feature gate, which makes sense

14:25 <re_irc> <chmanie> James Munns, dirbaio: Here's my preliminary approach for the MAX11300 driver using typestate. I'm making having use of seq_macro for the port mode structs and the trait implementations that are very repetitive. For the SPI bus I'm using a simple RefCell holding the shared struct. The only thing I'm not super happy with is the code repetition of the individual port configurations after the fact ("configure_xxx"). I...

14:25 <re_irc> ... refrained from implementing the typestate transitions for now as that's something that in practise rarely happens. Here's the code: https://gist.github.com/chmanie/abe818ba291609dacbd8d0a4f9775969

14:27 <re_irc> <chmanie> Let me know what you think!

14:29 <re_irc> <James Munns> Oh neat! I hadn't seen that seq! Macro before!

14:30 <re_irc> <chmanie> Maybe there's a better way but it did seem appropriate

14:32 <re_irc> <chmanie> James Munns, dirbaio: Here's my preliminary approach for the MAX11300 driver using typestate. I'm making heavy use of "seq_macro" for the port mode structs and the trait implementations that are very repetitive. For the SPI bus I'm using a simple RefCell holding the shared struct. The only thing I'm not super happy with is the code repetition of the individual port configurations after the fact ("configure_xxx"). I...

14:32 <re_irc> ... refrained from implementing the typestate transitions for now as that's something that in practise rarely happens. Here's the code: https://gist.github.com/chmanie/abe818ba291609dacbd8d0a4f9775969

16:24 <re_irc> <James Munns> Gunna stream some more Splitpea development (with "pretty HAL machine"!), today at 18:00 CET (a bit over 30m from now): https://youtu.be/EughbCeVVxw, come hang out and say hi :D

16:25 <re_irc> <James Munns> (pretty HAL machine is a tool for proxying "embedded-hal" commands to an attached USB device, instead of flashing/reflashing a firmware while developing a driver. More info here: https://github.com/jamesmunns/pretty-hal-machine)

17:16 <re_irc> <James Munns> Starting the stream now :D

20:19 <re_irc> <henrik_alser> James Munns: Catching up on the stream now :D

21:08 <re_irc> Whatever I do with the DWT peripheral, I always get 1073741824 when I call get_cycle_count(), which is 0x4000_0000

21:08 <re_irc> <Mehmet Ali> I am trying to count how many cycles a function takes.

21:09 <re_irc> <Mehmet Ali> I tried the core peripheral from nrf52840_pac like this:

21:09 <re_irc> use nrf52840_hal:: {

21:09 <re_irc> #...

21:09 <re_irc> };

21:09 <re_irc> pac::DWT,

21:09 <re_irc> <Mehmet Ali> I tried the core peripheral from nrf52840_pac like this:

21:09 <re_irc> use nrf52840_hal:: {

21:09 <re_irc> pac::DWT,

21:09 <re_irc> #...

21:09 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/181ad4924c14eadbe7dabaa9eb738791f45d193af72b1fd2f701dfe7bb5c16ed (9 lines)

21:10 <re_irc> <Mehmet Ali> I tried the core peripheral from nrf52840_pac like this:

21:10 <re_irc> use nrf52840_hal:: {

21:10 <re_irc> #...

21:10 <re_irc> pac::DWT,

21:10 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/c8d69593cd9a918648900b09a64dc8ab09ff224213b9c8e8ace5871b23fb5f4f (14 lines)

21:10 <re_irc> <Mehmet Ali> I tried the equivalent with the cortex_m crate.

21:12 <re_irc> <Mehmet Ali> Am I missing sth obvious? Is it the belgian ale?

21:40 <re_irc> <adamgreig> Check the docs for enable_cycle_counter, iirc you have to enable_trace also

23:16 <re_irc> <vdkj> With your help I have made most of the changes that were suggested in the initial review of the code here: https://github.com/jvanderk/syd-siderial_tracker/blob/main/src/bin/syd.rs .

23:16 <re_irc> One remark was to split the code into modules. I've made an initial attempt at that but ran into a number of issues, mostly scope related. I started in https://doc.rust-lang.org/book/ch07-00-managing-growing-projects-with-packages-crates-and-modules.html but would really like to see an example setup...

23:52 <re_irc> <vdkj> With your help I have made most of the changes that were suggested in the initial review of the code here: https://github.com/jvanderk/syd-siderial_tracker/blob/main/src/bin/syd.rs .

23:52 <re_irc> One remark was to split the code into modules. I've made an initial attempt at that but ran into a number of issues, mostly scope related. I started in https://doc.rust-lang.org/book/ch07-00-managing-growing-projects-with-packages-crates-and-modules.html but would really like to see an example setup...

23:52 <re_irc> One example:

23:52 <re_irc> mod rate {

23:52 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/81c969a6dc3d52079c6913bb0fe45f6eb58bffe6b44aea18690de8039fd16c47 (12 lines)