ObviousInRetrospect
ObviousInRetrospect
Parameters I currently use via additional params are: vbv-maxrate=5000:vbv-bufsize=30000 (this constrains the stream rate on average to around 5mbps while allowing some bursting as needed up to a ~6 second...
Make the warnings a bit more precise. Given how responsive and helpful per1234 has been in getting these bugs fixed and releases cut including the fixes the prior language seemed...
this is a know bug with a trivial workaround that would get rid of the need to recommend against 1.8.19. I suspect the ratio of frustration saved to the indignity...
I'm not having much luck getting session save/restore to work. Multiple examples show that you need to implement NetSaveSessionInfo/NetSaveSessionState/NetGetSessionState. Based on issue #165 I also added GetAbpProvisioningInfo. When that wasn't...
Both of the SPI flash libraries need SPI.transfer16 which isn't defined.
$ git submodule update --init --recursive Submodule 'esp32/libraries/ESP32_AzureIoT_Arduino' (https://github.com/VSChina/ESP32_AzureIoT_Arduino.git) registered for path 'libraries/ESP32_AzureIoT_Arduino' Submodule 'esp8266/libraries/ESP8266SdFat' (https://github.com/earlephilhower/ESP8266SdFat.git) registered for path '../esp8266/libraries/ESP8266SdFat' Submodule 'esp8266/libraries/LittleFS/lib/littlefs' (https://github.com/esp8266/Arduino/libraries/LittleFS.git) registered for path '../esp8266/libraries/LittleFS/lib/littlefs' Submodule 'esp8266/libraries/SoftwareSerial' (https://github.com/PaulStoffregen/SoftwareSerial.git)...
I've noticed unreliable slave behavior in SLEEP_MODE_STANDBY (and SLEEP_MODE_POWER_DOWN). This seems to be more of an issue when transferring larger buffers. I thought guarding the sleep_cpu() call with !Wire.slaveTransactionOpen() was...
The prior description of Wire.slaveTransactionOpen() left out a bunch of pitfalls on correct use.
These are a first real cut for all chips. Interested in thoughts on whether square is even worth exploring. Happy to make changes as needed.
this is a know bug with a trivial workaround that would get rid of the need to recommend against 1.8.19. I suspect the ratio of frustration saved to the indignity...