08:02 <ivmarkov[m]> <PeterKrull[m]> "No, its fine! I want to consider..." <- To share my (limited) experience (not sure that would help or bring more confusion, but oh well):... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/VeLwcrjatOABfDgaCPUWfVQu>)

10:33 <MariusKriegerows> Hey folks,

10:33 <MariusKriegerows> I tried optimizing for size as described in https://docs.rust-embedded.org/book/unsorted/speed-vs-size.html When I run cargo size --bin myapp -- -A as described, I'm getting error: Failed to parse crate metadata. What is can be causes for this error? How can I debug that?

10:33 <MariusKriegerows> Also asked here https://stackoverflow.com/questions/78959924/getting-size-of-binary-with-cargo-size-errors

11:05 <JamesMunns[m]> What does cargo build --bin myapp say? Does it build correctly?

11:06 <JamesMunns[m]> also, note that you also need to pass --release to size if you want it to be optimized, e.g. cargo size --bin myapp --release -- -A

15:39 <dav1d> Anyone know how I am supposed to set the internal pull up with esp-hal? https://docs.esp-rs.org/esp-hal/esp-hal/0.20.0/esp32s3/esp_hal/gpio/trait.OutputPin.html#tymethod.internal_pull_up - This used to just work, now it needs private::Internal ... which I assume is so I can't call it, but then how am I supposed to use it?

15:39 <JamesMunns[m]> Might be worth asking in #esp-rs:matrix.org if you don't get a response here

15:44 <dav1d> Thanks, gotta figure out the matrix stuff first, iirc it's not bridged to libera :(

15:45 <GrantM11235[m]> Are you trying to use it as an open drain output? I think this is what you want https://docs.esp-rs.org/esp-hal/esp-hal/0.20.0/esp32s3/esp_hal/gpio/struct.OutputOpenDrain.html#method.new

15:53 <dav1d> GrantM11235[m], thanks that could be it, there is also RtcPinWithResistors which seems to provide that

16:00 <dav1d> Seems like I have the same issue with `connect_input_to_peripheral_with_options` now. Trying to update this code https://github.com/jonored/esp-hal-rmt-onewire/blob/main/src/lib.rs#L47-L59

19:07 <danielb[m]> What are you trying to do?

19:09 <danielb[m]> Ah nevermind i see

19:16 <dav1d> By coincidence I saw the owner was active in the rust channel on liberal, they're gonna look into updating it \o/

19:43 <NiaLinaLunaStorm> I am writing firmware rn for a device of which I expect multiple to be connected at the same time so to make it clear which is which, I wanna give it its own PID and product name on the USB...... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/dNLVcVQhXDFMSsguVHOmBqTa>)

19:43 <NiaLinaLunaStorm> any idea what I'm doing wrong?

19:44 <K900> `serial_number` is _right there_

19:44 <K900> You probably want to vary that

19:44 <K900> And by probably I mean definitely

19:54 <GrantM11235[m]> <NiaLinaLunaStorm> "I am writing firmware rn for a..." <- > <@fly:asra.gr> I am writing firmware rn for a device of which I expect multiple to be connected at the same time so to make it clear which is which, I wanna give it its own PID and product name on the USB...... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/NGJZWVWXdFmtIxcNwRFehado>)

19:56 <nandnor[m]> Yea looks like the type of usb_dev is essentially () otherwise

20:00 <NiaLinaLunaStorm> <GrantM11235[m]> "> <@fly:asra.gr> I am writing..." <- thanks, that was it

20:07 <GrantM11235[m]> Most chips have some sort of built-in unique serial number or identifier, you could just use that for the usb serial number. That way you can use the same binary for every device