00:39 <vollbrecht[m]> avr-hal-generic already supports i2c afaik, so you probably only need to create a specific attiny-hal i2c driver and get it automatically implemented against e-hal

00:39 <vollbrecht[m]> so its not about having an e-hal driver rather an i2c driver at all for that target

00:40 <vollbrecht[m]> * already supports embedded-hal i2c afaik,

01:02 <leonardvdj[m]> Hey y'all 👋 Was looking around the awesome-embedded-rust repo and couldn't quite see, is there any lib for the ST7796 SPI display driver? I got the esp32-3248S035C board

01:03 <leonardvdj[m]> * esp32-3248S035C board, on the shipped c++/ino examples the TFT_eSPI lib is used.

02:49 <vollbrecht[m]> you can use https://docs.rs/mipidsi/0.7.1/mipidsi/index.html

02:51 <vollbrecht[m]> ah wait its a 7796 i am not 7789, maybe it needs some adoption

03:42 <leonardvdj[m]> You mean in the sense of, I have to add support to mipidsi for it? Not really sure how to get started with that 😄

04:08 <vollbrecht[m]> <leonardvdj[m]> "You mean in the sense of, I have..." <- the right place for talking displays and stuff for embedded is https://matrix.to/#/#rust-embedded-graphics:matrix.org maybe you find something good there for it

04:09 <leonardvdj[m]> Ah, thank you :)

12:09 <Ralph[m]> <onkoe[m]> "hey there! does anyone know if..." <- > <@onkoe:matrix.org> hey there! does anyone know if there's an on-going effort to get `avr-hal` working with `embedded-hal@1.0.0-r3`? i have a small library crate that i just ported to the new `embedded-hal` (since it's releasing soon), but i'd really like to test with my Arduino before i even... (full message at

12:09 <Ralph[m]> <https://catircservices.org/_matrix/media/v3/download/catircservices.org/YzZVDqLGknMCyATcPNMeTpVi>)

14:31 <kriomant[m]> Hello. I have strange glitches which seems like memory is exhausted. It on Arduino Uno R3 with only 2kb sram. Is there any way to view stack consumption of each function? I've found cargo-call-stack, but it fails with «failed to parse LLVM IR». Any other solution?

14:44 <adamgreig[m]> try this fork of cargo-call-stack, if you haven't already, https://github.com/Dirbaio/cargo-call-stack

14:44 <adamgreig[m]> not sure how well it works on AVR though

14:44 <adamgreig[m]> watch out for functions that return large items, it's easy to end up with several copies and blow your stack that way

15:21 <kriomant[m]> <adamgreig[m]> "not sure how well it works on..." <- Unfortunately, it seems it relies on llvm linker, while avr-gcc is used: "avr-gcc: error: unrecognized command line option '-mllvm=-lto-embed-bitcode=optimized'"

16:34 <djdisodo[m]> <kriomant[m]> "Hello. I have strange glitches..." <- i've done such debugging once so i can be a help

16:35 <djdisodo[m]> getting stack address is relatively simple

16:35 <djdisodo[m]> you may want to use inline assembly because compiler might optimize it but i got one other method that doesn't use inline assembly

16:36 <djdisodo[m]> put volatilecell(u8) into variable and cast reference of it to raw pointer and u16, print

16:37 <djdisodo[m]> the stack address starts from 2048 + 255 and decreases

16:37 <djdisodo[m]> this means that 2048 + 255 - (current stack address) is amount of stack memory used

16:38 <djdisodo[m]> however available stack memory is likely smaller than 2048 bytes in the first place, it's because lot of things like static variable gets stored in sram

16:40 <djdisodo[m]> you can get how much of sram is used when program loaded by checking size of .data in compiled binary

16:41 <djdisodo[m]> compile in release profile and also check this

16:41 <djdisodo[m]> https://github.com/Rahix/avr-hal/discussions/463

16:56 <kriomant[m]> <djdisodo[m]> "compile in release profile and..." <- thank you, i'll give it a try

18:24 <TristramGrbener[> Hello, I’m an eterneal beginner with embended rust.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/kLMfcQJyjngwUpciODPYjNmX>)

18:25 <JamesMunns[m]> Nope! Not misunderstanding. You may want to use the embassy-nrf HAL, which might be more flexible

18:25 <JamesMunns[m]> but I also have code... somewhere? That (ab)uses the PWM peripheral to create a WS2812B bitstream

18:26 <dirbaio[m]> https://github.com/embassy-rs/embassy/blob/main/examples/nrf52840/src/bin/pwm_sequence_ws2812b.rs

18:27 <JamesMunns[m]> https://github.com/jamesmunns/nrf-smartled was mine :D

18:28 <TristramGrbener[> thank you for boths examples, I’ll try to wrap my head arround all that

19:35 <dirbaio[m]> 📣 smoltcp v0.11.0 released! [Changelog](https://github.com/smoltcp-rs/smoltcp/blob/v0.11.0/CHANGELOG.md)

19:55 <diondokter[m]> Ok, I've been fuzzing `sequential-storage` with unexpected shutdowns of the mock flash. It's running way better than expected.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/pcyHtBwLunfmiwCDtNUecTaS>)

19:55 <firefrommoonligh> Thanx homie. Would love to use it should I end up doing TCP over embedded

19:56 <firefrommoonligh> <TristramGrbener[> "Hello, I’m an eterneal beginner..." <- > <@tristramgr:matrix.org> Hello, I’m an eterneal beginner with embended rust.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/tyeFCXoQJVtrSwMmJsqaaLuI>)

19:56 <firefrommoonligh> Its timer module is a thin wrapper over the reg level API (which, thanks Nordic, is remarkably usable)

19:56 <firefrommoonligh> I ended up wrapping that with a more trad/high-level Timer struct etc, FWIW

19:57 <firefrommoonligh> Speaking of remarkably usable register APIs: Semtech's API and DS is remarkably good, at least for sx126x

19:57 <firefrommoonligh> s/remarkably good/great/

22:02 <TristramGrbener[> So I tried exploring a bit embassy. Sounds exiting (and overwhelming for someone only comfortable coding for a desktop with an OS).

22:02 <TristramGrbener[> Am I supposed for now to keep working in the embassy tree, or did I miss something ?

22:02 <TristramGrbener[> I tweaked the examples, and tried to extract it to a separate project. But it seems that the crates aren’t published (e.g. embassy_nrf) on crates.io.

22:11 <JamesMunns[m]> Docs here: https://embassy.dev/book/dev/basic_application.html

22:12 <JamesMunns[m]> Ah, https://embassy.dev/book/dev/new_project.html is what I was thinking of

22:18 <PeterHansen[m]> <diondokter[m]> "Ok, I've been fuzzing `sequentia..." <- How would you find other items if the CRC is bad? Is the CRC covering the length, or is there not a length, or is the length somehow validated separately from the CRC?

22:20 <TristramGrbener[> In those examples, in the Cargo.toml, we have things like : embassy-executor = { version = "0.4.0", path = "../../../../../embassy-executor" with a relative path to the crate, and not fetching it from crates.io, that is what surprises me

22:22 <TristramGrbener[> Sorry, I overlooked the https://embassy.dev/book/dev/new_project.html#_cargo_toml paragraph. Thank you for pointing the documentation, and sorry for the question that was actually answered in the doc

23:42 <JamesMunns[m]> Tristram Gräbener no worries! Those docs are relatively new, no need to apologize, it was a totally reasonable question :)