06:27 <ducks2788[m]> Good morning. Is the raspberry pi pico somehow restricted to two simultaneous socket connections? I have my network stack created like so:... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/mvCLbwDhKFwyQawPTHWAUaZB>)

06:28 <ducks2788[m]> Ups, sorry, wrong channel... 😅

14:16 <djdisodo[m]> can someone tell me what is 1530micros delay on https://docs.rs/lcd1602-rs/0.1.0/src/lcd1602_rs/lcd1602.rs.html?

14:16 <diondokter[m]> djdisodo[m]: My guess is that the datasheet says you need this

14:19 <djdisodo[m]> ok so it won't be a problem if i turn this into "make sure next call never happen in 1530micros" instead of "wait 1530 micros"

14:19 <djdisodo[m]> * 1530 micros"?

14:19 <diondokter[m]> Don't know how you want to uphold that, but yes

14:20 <djdisodo[m]> diondokter[m]: i set the timer after call and wait timer before executing call

14:20 <diondokter[m]> Sure, that'd work

14:20 <diondokter[m]> Even better would be to convert it all to async

14:20 <djdisodo[m]> yeah i'm planning async too

14:20 <diondokter[m]> Then you let the compiler an e.g. embassy figure it ouy

14:20 <diondokter[m]> s/ouy/out/

14:20 <diondokter[m]> s/an/and/, s/ouy/out/

16:28 <thejpster[m]> today I realised https://blog.rust-embedded.org still exists

16:31 <JamesMunns[m]> Very open to having it be used again, if someone is willing to do the writing

16:43 <thejpster[m]> speaking of blogs, today I wrote https://ferrous-systems.com/blog/rust-and-threadx/

20:08 <M9names[m]> According to the date on the blog you wrote it next year

20:12 <danielb[m]> M9names[m]: timezones are hard

20:30 <fuse117[m]> looking for some help understanding the following. I have never hit such an error. can someone provide general guidance on how to troubleshoot this?... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/wCNLUiPJQMSiPOBNNSmAyjiF>)

20:35 <dirbaio[m]> are you building with build-std-features=panic_immediate_abort?

20:35 <dirbaio[m]> that turns all panics into udf instructions, which trigger a hardfault

20:36 <fuse117[m]> yes. build-std-features=panic_immediate_abort is used for this project

20:37 <dirbaio[m]> then yep, it's a panic

21:02 <fuse117[m]> i can see the panic in a longer stack trace.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/SyGsvaWiYJTGuWyWMQCIegqQ>)

21:03 <fuse117[m]> * thanks! cool. i can see the panic in a longer stack trace now.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/qSMVsJcCohDXBydkGlqwDVWm>)