- 30 9月, 2020 34 次提交
-
-
由 ToXIc 提交于
-
由 lbernstone 提交于
* Update CaptivePortal.ino Illegal SSID used for SoftAP * Fixed ordering problem. Now actually works
-
由 chegewara 提交于
-
由 M. Betz 提交于
SPIFFS File object evaluates as true even if the file could not be opened.
-
由 cweinhofer 提交于
Co-authored-by: NMe No Dev <me-no-dev@users.noreply.github.com>
-
由 buxtronix 提交于
Co-authored-by: NMe No Dev <me-no-dev@users.noreply.github.com>
-
由 buxtronix 提交于
-
由 pulquero 提交于
Co-authored-by: NMark Hale <mark.hale@physics.org>
-
由 lewis he 提交于
Co-authored-by: Nlewis he <lewisxhe@outlook.com>
-
由 TANAKA Masayuki 提交于
-
由 Bascy 提交于
-
由 Ashwin K Whitchurch 提交于
Co-authored-by: NAshwin <ashwin@circuitects.com>
-
由 callifo 提交于
Update in accordance with Firebeetle's official firebeetle32 pins_arduino.h. Without it, digital pins weren't definable, and analogue pins didnt line up. Taken from http://download.dfrobot.top/FireBeetle/DFRobot_FireBeetle-ESP32-0.0.9.zip
-
由 lbernstone 提交于
-
由 robertpoll 提交于
Background The current implementation of Update() uses the spi_flash_* api to write and read from flash. These functions ignore the partition->encrypted flag and always write raw data to flash even if the partition is marked as encrypted. Changes in this PR Update() now uses the esp_partition_* api. Wrapper functions for esp_partition_* added to ESP.cpp. This was done to maintain a consistent approach to the way the spi_flash_* functions were used. I note though that not all of the esp-idf functions are used are wrapped, for example esp_ota_get_next_update_partition() so it may be that these should not be added? The current implementation of Update() changes the first (magic) byte of firmware to 0xFF on write, and then when the firmware is completely written changes it back to ESP_IMAGE_HEADER_MAGIC. This works without erasing the sector because flash bits can be changed from 1->0 (but not 0->1). If the flash is encrypted then the actual data written to flash will not be all ones, so this approach will not work. In addition, encrypted flash must be written in 16 byte blocks. So, instead of changing the first byte the changed code stashes the first 16 bytes, and starts writing at the 17th byte, leaving the first 16 bytes as 0xFF. Then, in _enablePartition() the stashed bytes can be successfully written. Benefits Whilst it's not possible to use encrypted flash directly from either the Arduino IDE or PIO it's reasonably straightforward to compile and flash a bootloader with the necessary support from a simple esp-idf project and then use ArduinoOTA for subsequent updates. This PR enables the use of this workflow until such time as encrypted flash is supported, and is a first (small) step toward adding support. Regardless of the above, the esp_partition_* api is recommended over the api_flash_* api. Application code should mostly use these esp_partition_* API functions instead of lower level spi_flash_* API functions. Partition table API functions do bounds checking and calculate correct offsets in flash, based on data stored in a partition table.
-
由 lbernstone 提交于
* Fixes UART detach. Fixes #3878 * 0 is not a good holder value for pins! * 0 is not a good holder value for pins!
-
由 Satyan Raj 提交于
* Added new board variant for Imbrios LogSens V1.1 Imbrios LogSens V1.1 new board variant * added new board Imbrios LogSens V1.1 Added new board details: Imbrios LogSens V1.1
-
由 sindney 提交于
By default the disconnect is broadcasted to every clients. So if you call disconnect on one connected client, they'll all be disconnected if we don't filter the event by conn_id.
-
由 Martijn Scheepers 提交于
* ESP.getChipModel() returns model of the chip * ESP.getChipCores() returns the core count. * Example gives chip model, revision and core count. * Read efuse for chipmodel Co-authored-by: NMartijn Scheepers <ms@SDNengineering.nl>
-
由 Admar Schoonen 提交于
Fixed bug where uartResizeRxBuffer() did not unlock mutex if creation of queue failed.
-
由 Bernd Giesecke 提交于
* Fix issue #3833, data parsing of Eddystone TLM data frame Add Beacon scanner example to show usage of BLEEddystoneTLM class and BLEEddystoneURL class Add EddystoneTLM beacon example Add EddystoneURL beacon example * Fix buffer size for .toString()
-
由 jgdent 提交于
BUGFIX: avoids assertion in xEventGroupWaitBits() (/home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/event_groups.c:350 (xEventGroupWaitBits)- assert failed!)
-
由 hznupeter 提交于
-
由 Mark D 提交于
-
由 Mauricio de Oliveira 提交于
Add support for the v1.8.6 compiler.libraries.ldflags: https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5:-Library-specification This fixes the issue reported here: https://community.bosch-sensortec.com/t5/MEMS-sensors-forum/BSEC-1-4-7-4-compilation-error-on-ESP32-1-0-3-rc1/td-p/9120
-
由 kliment 提交于
When connecting using transportTraits, the CA and client certificates are ignored after the initial _client->connect() is called. This is because on connect, WiFiClientSecure will call start_ssl_client with _CA_Cert and other cert options set to null unless setCACert, setCertificate etc. are called before connect. Running _transportTraits->verify after connect therefore does exactly nothing. It's easy to verify that this is the case by passing a CACert to HTTPClient with verbose logging enabled - the logs will say "WARNING: Use certificates for a more secure communication!" which is only present when both PSK and CA are null. This change fixes the issue.
-
由 puuu 提交于
-
由 Mark D 提交于
-
由 Andrzej Sierżęga 提交于
Real DNS resolving timeout used by lwip library is 14[s] (7[s] for DNS1 + 7[s] for DNS2). Function WiFiGenericClass::hostByName() has timeout set to lower value (only 4[s]), so callback function may be called after this low timeout and it may overlappe stack memory used now by other function. Fixes #3722
-
由 Me No Dev 提交于
-
由 Dirk O. Kaar 提交于
* Extend Print class for 64bit integers. modulo 32bit and 64bit tuned for code size. * Fix 32bit long used in long long printNumber.
-
由 Dirk O. Kaar 提交于
Greatly reduces error rate (half, or 0 zero errors, depends on in/out ranges) for round-trip mapping at the same performance. (#3655) (Based on "improved_map" from ESP8266's Servo.cpp)
-
由 crnchbng 提交于
-
由 ducalex 提交于
-
- 28 9月, 2020 1 次提交
-
-
由 Sean Kwok 提交于
fix some mistake
-
- 31 8月, 2020 1 次提交
-
-
由 Valerii Koval 提交于
-
- 25 8月, 2020 2 次提交
- 19 7月, 2020 1 次提交
-
-
- 01 6月, 2020 1 次提交
-
-
由 Nigel Mellor 提交于
They are all broadly similar, all being based on the ESP32-D0WD core, but have some subtle differences between variants around PSRAM inclusion and camera pin mappings. The ESP32CAM "unit" product (SKU: U007) has no PSRAM and maps the "Pixel Data 0" (Y2 GPIO/OV2640 D2) camera pin to IO17 rather than IO32 as is the case with most other M5Stack ESP32 camera devices. The ESP32CAM also requires the "hmirror" and "vflip" camera configuration bits setting in order to capture a true image. The relevant M5Stack pin configuration documentation can be found here: https://docs.m5stack.com/#/en/unit/esp32cam?id=pinmap
-