GitLab

typo

This PR fixes an issue of multiple device callbacks (one callback per device) were not getting registered and invoked.
Consider an example where I create two devices, a switch and a fan; each of them having their own write callbacks. On controlling either switch/fan through Rainmaker app, the callback that got registered at last gets invoked. This is also seen in the issue reported in #8231

* Added printQR function to library

* Upgraded example

* Upgraded README

* Safegueard for qrcode.h include

* Updated Safegueard for qrcode.h include

* Added Nebula s3 Board

* added nebulas3 board

* added variant

* added semicolons

* added pins details

* added secondary sda1 and scl1

* USB_CDC enabled by default

* Changed nebulas3.build.board to NebulaS3

* Changed NebulaS3 to NEBULAS3

* Add MatrixPortal ESP32-S3 (WIP)

* Update bootloader files, etc.

* Add MatrixPortal S3 PSRAM setup to boards.txt

* add dfrobot romeo esp32S3

* add dfrobot romeo esp32s3

* Update pins_arduino.h

* Update pins_arduino.h

* Update pins_arduino.h

* Update pins_arduino.h

* Fixes HWCDC::end()

There is a missing `tx_lock = NULL;`

* Update HWCDC.cpp

Initialize rx_data_buf[] with zeros.

* HardwareSerial: fix begin() lock issue on error path

If the user supplied a wrong UART number, the begin() method would
return without releasing the lock. Add missing unlock call.

* removing unsed Case test

---------
Co-authored-by: Rodrigo Garcia <rodrigo.garcia@espressif.com>

* Updated preferences.rst

* Added into FAQ info about SPIFFS failed mount

* Add M5CoreS3 boards.txt and pins definition

* Fix some pins definition

* Added link to external examples to the doc

* Fixed FunctionalInterrupt.ino + added introduction comment and few outputs

A new flexible and powerful "pluggable discovery" system was added to the Arduino boards platform framework. This system
makes it easy for Arduino boards platform authors to use any arbitrary communication channel between the board and
development tools.

Boards platform configurations that use the old property syntax are automatically translated to the new syntax by
Arduino CLI:

https://arduino.github.io/arduino-cli/latest/platform-specification/#sketch-upload-configuration

> For backward compatibility with IDE 1.8.15 and older the previous syntax is still supported

This translation is only done in platforms that use the old syntax exclusively. If `pluggable_discovery` properties are
defined for the platform then the new pluggable discovery-style `upload.tool.<protocol_name>` properties must be defined
for each board as well.

This platform was converted to use the new pluggable discovery platform properties syntax, so those properties are
required. Although such properties were added to board definitions at the time the syntax was changed, new board
definitions without the required properties were added later.

Those missing properties caused uploads to fail for users of the recent versions of Arduino IDE and Arduino CLI with an
error of the form:

Error during Upload: Property 'upload.tool.serial' is undefined

It is also important to provide compatibility with versions of Arduino development tools from before the introduction of
the modern pluggable discovery system. For this reason, the old style `<board ID>.upload.tool` properties are retained.
Old versions of the development tools will treat the `<board ID>.upload.tool.default` properties as an unused
arbitrary user defined property with no special significance and the new versions of the development tools will do the
same for the `upload.tool` properties.

Co-authored-by: Me No Dev <me-no-dev@users.noreply.github.com>

* Create allboards.yml for all boards test

* Clean workflow from unused stuff

* Use compile-sketch main

* Update find_all_boards.sh

* Update timer.rst

Changed text because of an inconsistence between title and text explaining the timerGetConfig function.
I don't know if the method timerSetConfig really exists.

* Update timer.rst

Add informations about timerSetConfig function.

Revert to previous definition of `FPSTR` and `F` macros.

Revert to previous definition of `FPSTR` and `F` macros.

Resolves deprecation warnings in CameraWebServer.ino. pin_sscb_sda -> pin_sccb_sda. pin_sscb_scl -> pin_sccb_scl.
The variables are in the same union and are identical.

* Added 2 new libs + removed unnecessary multiple examples

* Change example for WS2812FX lib

* Fixes analogWrite

* sets cnt_channel index

* fixes TAB alligment

* Fix the F_CPU frequency for the ESP32-S3

Hello, I was using the FastLED library and it was complaining about F_CPU not being defined. So, I just noticed that it is not defined for the ESP32-S3 module. So I made this change in the header file and it compiled. Therefore I wanted to propose this change to the HAL library to improve compatibility. Thank you for your time.

* Makes F_CPU generic based on the SoC frequency

Works for ESP32, ESP32C3, ESP32S2, ESP32S3

* Includes ESP32C3 in the F_CPU definition

Necessary for ESP32 Arduino Core 2.0.x based on IDF 4.4

---------
Co-authored-by: Ali Devrim OGUZ <11381547+devrim-oguz@users.noreply.github.com>

Co-authored-by: Me No Dev <me-no-dev@users.noreply.github.com>

it is planned to use the flash led but a normal led is configured instead