02:12 <re_irc> < (@firefrommoonlight:matrix.org)> Check the DS?

02:12 <re_irc> < (@firefrommoonlight:matrix.org)> The TCXO I'm using is 1.8, which I believe is common

02:12 <re_irc> < (@firefrommoonlight:matrix.org)> Kinda bullshit I had to add a dedicated reg just for it

02:14 <re_irc> < (@firefrommoonlight:matrix.org)> The TCXO I'm using is 2.8, which I believe is common

02:14 <re_irc> < (@firefrommoonlight:matrix.org)> https://psion.agg.io/_matrix/media/r0/download/matrix.org/zcFwQIVhQFstfxQwTPwcbomw/image.png

02:15 <re_irc> < (@firefrommoonlight:matrix.org)> You're looking for something like this in the DS

02:15 <re_irc> < (@firefrommoonlight:matrix.org)> (That's for a RALTRON 52Mhz TCXO)

03:25 <Darius> definitely check the datasheet, it varies a lot

07:38 <re_irc> < (@thebutlah:matrix.org)> I have a feature flag that enables logging over uart, and a feature flag that controls which microcontroller I'm building for.

07:38 <re_irc> For the uart loggers, I have two libraries - one that only works on esp32, and one that works on nrf52.

07:38 <re_irc> I want to only enable the esp32 uart if _both_ the uart feature and the esp32 feature are enabled. Same with the nrf52.

07:38 <re_irc> But cargo doesn't have a way to specify an "&&" between features for enabling an optional dependency.

07:38 <re_irc> What should I do"

07:38 <re_irc> < (@thebutlah:matrix.org)> * do?

07:42 <re_irc> < (@thebutlah:matrix.org)> https://psion.agg.io/_matrix/media/r0/download/matrix.org/kAApybogLcbTOyTCmBDsAxUc/image.png

07:42 <re_irc> < (@thebutlah:matrix.org)> if "log-uart" AND "mcu-esp32c3", then enable "defmt_esp_println/uart"

07:53 <re_irc> < (@grantm11235:matrix.org)> I think you can make it work if you create a logging library that works with both esp and nrf

07:54 <re_irc> < (@grantm11235:matrix.org)> (Or just merge both your existing libraries into one)

07:59 <re_irc> < (@grantm11235:matrix.org)> Then you can do "mcu-esp32c3 = ["defmt_println?/esp"]" and "log-uart = ["defmt_println/uart"]"

08:06 <re_irc> < (@grantm11235:matrix.org)> You could implement the universal logging library as a thin shim around your existing libraries with something like this in the cargo toml of the new crate:

08:06 <re_irc> esp = ["defmt_esp_println"]

08:06 <re_irc> nrf = ["defmt_nrf_println"]

08:06 <re_irc> uart = ["defmt_esp_println?/uart", "defmt_nrf_println?/uart"]

10:37 <re_irc> < (@adamgreig:matrix.org)> Darius: I would love to check the datasheet but alas, seeed (who make the module that has the tcxo under the tin) don't say what it is or what voltage it needs 💀

10:38 <Darius> adamgreig: fuuuu

10:38 <re_irc> < (@adamgreig:matrix.org)> it's powered by the stm32wl which has a built in adjuatable ldo for powering tcxos that can be set in firmware to any voltage 1.6-3.3

10:38 <Darius> what is the modue?

10:38 <re_irc> < (@adamgreig:matrix.org)> which is cool for sur but would be better if they said what voltage it needs lol

10:38 <re_irc> < (@adamgreig:matrix.org)> lora-e5

10:40 <Darius> yeah

10:44 <Darius> tried emailing them?

10:44 <Darius> or their forums etc

11:38 <re_irc> <meteor> Hi, have anyone compiled rust code for Arduino Uno Rev3 before?

11:38 <re_irc> <meteor> I tried to follow https://github.com/avr-rust/blink

11:38 <re_irc> <meteor> For rev3 the correct mcu should be atmega16u2

11:40 <re_irc> <meteor> But it seems like the target avr-unknown-gnu-atmega328 assumes architecture avr5. But Arduino Uno uses avr35

11:40 <re_irc> <meteor> Which caused a link error.

11:41 <re_irc> <meteor> Am I out of luck here 😢

11:41 <re_irc> <meteor> * here?

11:45 <re_irc> < (@thejpster:matrix.org)> Are you sure?

11:45 <re_irc> https://store.arduino.cc/products/arduino-uno-rev3

11:46 <re_irc> < (@thejpster:matrix.org)> The AtMega16U2 is the USB-Serial and AVR-ISP device.

12:03 <re_irc> <meteor> Oh you are correct. Thank you.

12:59 <re_irc> <Ralph> i've now pushed my driver here: https://github.com/rursprung/tb6612fng-rs

12:59 <re_irc> i'm holding off with a first release until i get some feedback here (hopefully?) on whether it makes sense to keep this driver-specific or if it could be agnostic (which would basically just mean some renaming of the structs).

13:00 <re_irc> <Ralph> as a side-note: i've also had to add a "PwmPin" mock implementation to the "embedded-hal-mock" library, hopefully this is also useful to others: https://github.com/dbrgn/embedded-hal-mock/pull/52

14:42 <re_irc> <Ralph> : i'm trying to write a library for the Adafruit Bluefruit LE UART Friend (https://learn.adafruit.com/introducing-the-adafruit-bluefruit-le-uart-friend) module. i currently have two things in the crate:

14:42 <re_irc> - handling of the Controller Protocol (https://learn.adafruit.com/bluefruit-le-connect/controller) from Adafruit - this isn't device specific at all - i basically get some byte-array, parse it and extract the commands

14:42 <re_irc> - setting up the Rx/Tx pins, using these to set up a "Serial" and set up DMA for it (i realise more and more that this probably shouldn't/can't be in the crate at all because it's too device-specific; in the other drivers you e.g. also pass in the i2c instance and not the pins because it can't construct an i2c instance from them in a generic way)

14:42 <re_irc> what i currently have separately in the consuming code is the handling of the DMA buffer (every time i get a message / the buffer i read for which i have to use "next_transfer") and i wonder if i could put that into the library.

14:42 <re_irc> ... long message truncated: https://psion.agg.io/_matrix/media/r0/download/psion.agg.io/aKjRZUIAoeNLDvwK7kXeOCGnfWTlx54X (6 lines)

16:31 <re_irc> <Dlaw> Is there a good way to condition package dependencies on build profile? I'd like to use rtt-target and panic-rtt-target for my debug build, but strip out all the rtt stuff and use panic-abort or panic-halt on the release build. I'd like to use rprintln! calls throughout my code and have them magically turn into no-ops for the release build. My motivation here is shrinking the binary size of the release binary by making...

16:31 <re_irc> ... sure it doesn't include any string formatting.

16:34 <re_irc> <Dlaw> (I am aware of defmt-rtt as one possible solution to minimize the binary size impact from string formatting. I'm still interested in learning how to have some dependency used for debug but not release, whether it's defmt or rtt or something else.)

16:56 <re_irc> <elephantpie> If I've never done any embedded systems programming which book should I start with? Is it that difficult to just learn from the main Embedded Rust Book?

17:05 <re_irc> < (@k900:0upti.me)> The book is a good option

18:32 <re_irc> <Ralph> Dlaw: you can probably use conditional compilation (https://doc.rust-lang.org/reference/conditional-compilation.html) by checking on the used profile (https://doc.rust-lang.org/cargo/reference/profiles.html). i'd actually be interested in this as well as i probably want to select between "panic_probe" (debug) and "panic_halt" (release).

18:32 <re_irc> i guess it doesn't hurt to have the _dependency_ enabled if it's not actually "use"ed as it then won't end up in the compiled code? because i'm not aware of a way to select dependencies based on a profile (but i'm by no means an expert - i just briefly looked at the docs and checked the auto-complete in the IDE 😅)

18:42 <re_irc> <Ralph> for the moment i went with the first option and have published it here (not yet released to crates.io): https://github.com/rursprung/adafruit-bluefruit-protocol-rs

18:42 <re_irc> if anyone sees a good way to actually implement more of the device-specific stuff (UART, etc.) in the generic crate that'd be great!

18:47 <re_irc> <Dlaw> Ralph: Conditional compilation works for covering up rtt usage (even if it's slightly clunky for me to define my own wrapper around rprintln), but it doesn't give me a way to change out the panic handler library

18:47 <re_irc> <Dlaw> So panic-rtt-target is still there and it still pulls in all the string formatting stuff

18:56 <re_irc> <Dlaw> Oh, hmm, it looks like I can place a conditional compilation attribute on the "use" statement which pulls in each of the panic handlers. This surprises me because I thought "use" tweaks what's in the local namespace but doesn't actually alter what links with the program.

19:04 <re_irc> <Ralph> Dlaw: yes, you can put it on the "use". sorry, didn't mention that explicitly before.

19:04 <re_irc> that's why i think that this should work (i haven't tried it for the crates you mentioned, but i've now tried it on 1-2 other external crates which i had as optional dependencies and had to guard in the code)