When user selected HSPI with SPIClass name(HSPI) ESP was, by default,
still using VSPI ports (the ones defined in pins_arduino.h).
With this change when user selects HSPI then HSPI default ports will be
used.
If user won't specify HSPI then VSPI default ports will be used.
If user will specify SCLK, MOSI, MISO and SS with SPI.begin() then user
defined ports will be used no matter if VSPI or HSPI is selected.
With this change fe. SD library can use default HSPI ports. It was
possible to
pass HSPI SPI instance to SD lib, however even then it was using VSPI
ports which were (probably) GPIO matrixed to HSPI.
The .build.board=xx proptery is used for generating a macro named "ARDUINO_xxx".
C macro names should never have a "-" sign.
* current: ARDUINO_NodeMCU-32S
* should be: ARDUINO_=NodeMCU_32S
* fix NodeMCU-32S .build.board property
The .build.board=xx proptery is used for generating a macro named "ARDUINO_xxx".
C macro names should never have a "-" sign.
* current: ARDUINO_NodeMCU-32S
* should be: ARDUINO_=NodeMCU_32S
* fix compiler flags to be compatible to ESP8622/Arduino
see also "fix NodeMCU-32S .build.board property" #812 (https://github.com/espressif/arduino-esp32/pull/812#issuecomment-341990261)
`-DARDUINO_BOARD={build.board}` **is missing**
* Revert "fix NodeMCU-32S .build.board property"
This reverts commit ea57b1496a2e87d3977a31a29a4cf7d63216f008.
* ArduinoOTA would stop receiving any packets if the port received a zero-length UDP packet, commonly sent by network scanners like nmap. Fixed to flush() after every call to parsePacket(), even if read length is 0.
Additionally, added length checking to fix a potential buffer overflow in parseInt().
Finally, added an end() method that stops the OTA listener and releases resources.
* Only end MDNS in end() if mdns mode is enabled.
The existing code did not follow protocol with 10bit addressed devices. Per _Philps/NXP Semiconductors UM10204 I2C-bus specification and user manual Rev. 6 4April2014_ pg.15 3.1.11 10-bit addressing:
~The first seven bits of the first byte are the combination of 1111 0xx of which the last two bits (xx) are the two Most-Significant Bits (MSB) of the 10-bit address; the eighth bit of the first byte is the R/!W! bit the determines the direction of the message~
The i2cWrite() function was returning to the app before the i2c transaction had completed. This caused the next Wire() call to return a I2C_ERROR_BUSY.
