cmorganBE

@pablogs9 are there plans to support zephyr 3.2 in the near future? Was hoping we could get this PR merged in.

I was actually trying to test against 3.3 (the latest stable release) and was running into boatloads of warnings as the old headers are nearing removal. Was planning at least...

@eliaskanelis wow, august 2022, time flies... I'd like to take a crack at this during the next break I have, likely during a holiday but I'd also gladly use it...

Using sht4x driver here (with the default of 1MHz). Seeing similar issues with periodic failures during configuration (retries resolve), and periodically during run-time where the write to start a measurement...

Modified the sht4x driver code to slow from 1MHz down to 100khz, and changed i2c bus pullups from 4.6k down to 2.6k. Signals on the scope look very clean vs....

I was able to catch the issue here. In the good case: - write to start measurement (0xFD) - Longer delay (~1ms) - data response from part bad case: -...

Alright, root cause identified for my case, opening a PR today to resolve. The issue was that for the SH4Tx driver pdMS_TO_TICKS() was being used. ticks on my system (and...

@FeOAr I'm guessing you have a different issue than I have. I wouldn't have posted here but it looked like the same issue initially. PR is #632

I'm seeing similar behavior here with extended advertisements on esp32-s3 with a very close copy of bleprph example. Sometimes it will retry and join, other times it looks like the...

Also pinging on this feature. It would bump performance up a bunch having the larger mtu.