07:19 <ryan-summers[m]> <PhilMarkgraf[m]> "If no such driver is already..." <- I did a driver for a 4 channel ADC a while back, check out https://github.com/quartiq/booster/blob/main/ads7924/src/lib.rs for a reference design :)

07:20 <ryan-summers[m]> Many of the small, obscure ics don't really have drivers because they're small enough that spinning your own isn't hard

09:48 <eldruin[m]> <PhilMarkgraf[m]> "If no such driver is already..." <- You could also look at this driver I wrote a while back for a few ADC devices: https://crates.io/crates/ads1x1x

09:55 <sjm42[m]> Oh yeah, I have used that one myself for ads1115 with 8bit avr one day :D

09:55 <sjm42[m]> Fixed a stupid lab power supply that had broken V/A displays.

09:55 <sjm42[m]> https://photos.app.goo.gl/B8D3gWpy434fYNLY6

10:14 <eldruin[m]> <sjm42[m]> "Oh yeah, I have used that one..." <- > <@sjm42:matrix.org> Oh yeah, I have used that one myself for ads1115 with 8bit avr one day :D... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/VaMtSpxJgqbmIciKTQYXVdmT>)

11:02 <mfiumara[m]> how to sleep in rust

13:41 <mfiumara[m]> Hey all, since I asked a lot of questions the past weeks in here I figure I write a small article about some of the basic questions on how to set up a debugging environment when coding for embedded targets using rust.

13:41 <mfiumara[m]> Hope it can be of some help for others around here!

13:41 <mfiumara[m]> https://medium.com/better-programming/debugging-embedded-rust-e92ff0b8b8e5

14:02 <thejpster[m]> will you be revising the nested match loops or leaving-as is, as discussed on Linked In?

14:57 <mfiumara[m]> <thejpster[m]> "will you be revising the..." <- On GitHub yes, on medium I’m not sure I can still edit the article since it was published by Better Programming

15:35 <firefrommoonligh> <PhilMarkgraf[m]> "If no such driver is already..." <- I would go straight to the protocol section of the datasheet. A lot of these have a single register with a handful of bits to configure and command readings

15:35 <firefrommoonligh> > <@shakencodes:matrix.org> If no such driver is already available, is there an ADC driver you would recommend to use as an example? If I need to build this, I'd like to make the interface something that is expected and versatile (and ultimately, open source.)

15:35 <firefrommoonligh> * I would go straight to the protocol section of the datasheet. These often have have a single (or a few) register with a handful of bits to configure and command readings

15:36 <firefrommoonligh> Your interaction code is (after the appropriate bus is set up) likely to be a single function with a few lines

15:37 <firefrommoonligh> Possibly with some u8-repr config enums if you want to generalize it

16:33 <mfiumara[m]> thejpster Code samples updated

17:24 <d3zd3z[m]> Is anyone at RustConf2023?

17:28 <d3zd3z[m]> d3zd3z[m]: I've had them create a rust-embedded channel on the conference-specific Discord, for anyone present who may be interested in discussing.

18:00 <ilpalazzo-ojiis4> Is it possible to use The Compiler Explorer (aka “the Godbolt”) to see rustc's output for AVR targets?

18:02 <ilpalazzo-ojiis4> Thus far the options I've given are `-C opt-level=s -Z build-std=core --target=avr-unknown-gnu-atmega328 `, but it's telling me that... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/pDhVXFEMLWDlXAwRETtVTyHE>)

21:29 <mfiumara[m]> Anyone experience with compiling a C project inside of build.rs using make?

21:34 <JamesMunns[m]> <mfiumara[m]> "Anyone experience with compiling..." <- like, specifically just shelling out to make? Or interacting with it more thoroughly?

21:34 <JamesMunns[m]> ah

21:35 <JamesMunns[m]> by default Command swallows the output, you have the choice to redirect it somewhere, or pipe it to the caller's stdout, BUT stdout in build-rs scripts is actually output to cargo itself, so you might need to forward to stderr or a file

21:35 <mfiumara[m]> Just handing it over to make it's a big project and I don't want to recreate the build process using cc::

21:38 <JamesMunns[m]> https://doc.rust-lang.org/stable/std/process/struct.Command.html has some examples for getting the output, you'd call output() instead of status()

21:38 <JamesMunns[m]> Then Output can be used to obtain the status and all of the output to stdout/err: https://doc.rust-lang.org/stable/std/process/struct.Output.html

21:40 <mfiumara[m]> Ah that helps, then I can save the output to a file to see what's going on

21:40 <JamesMunns[m]> yep, or something like `panic!("{}", the_output);`

21:52 <mfiumara[m]> Yeah it's not doing anything it seems, make is just outputting `make[1]: Nothing to be done for `all'.

21:52 <mfiumara[m]> `

21:53 <mfiumara[m]> But when I go into the directory manually in a terminal it is definitely compiling. The path is correct

21:53 <JamesMunns[m]> I'd probably try making a small non-build-rs bin project, and mess with it there first, to make it easier to debug

21:53 <JamesMunns[m]> then when THAT works, move it over to a build-rs

21:55 <JamesMunns[m]> ah!

21:55 <JamesMunns[m]> > In addition to environment variables, the build script’s current directory is the source directory of the build script’s package.

21:56 <JamesMunns[m]> try printing your current dir, you might be in PROJECT/src instead of PROJECT

21:59 <JamesMunns[m]> hm, nope, actually:... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/pXFVJJWdiodOwbXyTujdDxbH>)

21:59 <mfiumara[m]> Yeah it works as a --bin

22:00 <mfiumara[m]> I'm printing the folder name but it's correct

22:04 <JamesMunns[m]> did you print stdout and stderr? like did make complain more on stderr?

22:06 <mfiumara[m]> no there's nothing on stderr

22:06 <mfiumara[m]> I think the C project has to be located inside of src

22:06 <mfiumara[m]> But the documentation is not very clear

22:06 <mfiumara[m]> It's just this one sentence you quoted

22:07 <mfiumara[m]> I'll give that a shot

22:13 <mfiumara[m]> no luck 🙃

22:41 <mfiumara[m]> Will try more tomorrow. I think I have to do something like copy the project into the OUT directory and then compile it from there