1. 25 10月, 2022 1 次提交
    • W
      Add New Board: Cytron Maker Feather AIoT S3. (#7348) · 007badbb
      Wai Weng 提交于
      * Added support for Cytron Maker Feather AIoT S3.
      
      * 1. Select OPI PSRAM by default.
      2. Fixed pin name error in variant.cpp.
      3. Added definition for RGB_BUILTIN.
      
      * Define the RGB_BUILTIN as shown in #6979.
      
      * Added pin definition for A12 (Vin Sense).
      007badbb
  2. 17 9月, 2022 1 次提交
  3. 14 9月, 2022 3 次提交
  4. 07 9月, 2022 3 次提交
  5. 29 8月, 2022 1 次提交
  6. 16 8月, 2022 1 次提交
  7. 11 8月, 2022 1 次提交
  8. 09 8月, 2022 1 次提交
  9. 08 8月, 2022 3 次提交
  10. 01 8月, 2022 1 次提交
  11. 27 7月, 2022 1 次提交
  12. 26 7月, 2022 3 次提交
  13. 18 7月, 2022 1 次提交
    • S
      Improve RGB driver in pull #6808; solves #6968 (#6979) · 05ae83a0
      santaimpersonator 提交于
      * Improve RGB LED Driver
      
      Replaces the use of the `LED_BUILTIN` variable by creating a new variable called `RGB_BUILTIN`. On boards with both a regular LED and RGB LED, this change provides functionality to control either LED.
      
      The `LED_BRIGHTNESS` variable is changed to `RGB_BRIGHTNESS`, which aligns more closely with the `RGB_BUILTIN` variable name.
      
      `BOARD_HAS_NEOPIXEL` is no longer necessary; it is replaced by `RGB_BUILTIN`.
      
      * Update BlinkRGB example
      
      Update example code for changes with the RGB driver:
      - Replace `LED_BUILTIN` and `BOARD_HAS_NEOPIXEL` with `RGB_BUILTIN`
      - Replace `LED_BRIGHTNESS` with `RGB_BRIGHTNESS`
      
      * Update board variants
      
      Update board variants for changes with the RGB driver:
      - Remove `BOARD_HAS_NEOPIXEL`
      - Define `RGB_BUILTIN` pin
      - Replace `LED_BRIGHTNESS` with `RGB_BRIGHTNESS` to align with `RGB_BUILTIN` name
      Co-authored-by: NRodrigo Garcia <rodrigo.garcia@espressif.com>
      Co-authored-by: NVojtěch Bartoška <76958047+VojtechBartoska@users.noreply.github.com>
      05ae83a0
  14. 06 7月, 2022 2 次提交
  15. 30 6月, 2022 1 次提交
  16. 27 6月, 2022 1 次提交
  17. 24 6月, 2022 1 次提交
    • T
      Implement simple RGB driver via digitalWrite; solving #6783 (#6808) · 097ff8b1
      Tomáš Pilný 提交于
      * Initial implementation of RGB driver via digitalWrite
      
      * Moved constants to pins_arduino.h
      
      * Changed pin definition + added example
      
      * Wrapped BlinkRGB in #ifdef BOARD_HAS_NEOPIXEL
      
      * Removed forgotten log from example
      
      * Moved RGBLedWrite to new file esp32-hal-rgb-led and created pinMode in variatn.cpp
      
      * Updated example - lowered single channel brightness to LED_BRIGHTNESS
      
      * Changed function name from RGBLedWrite to neopixelWrite + code polishing
      
      * Moved pinSetup portion related to RGB back to common file
      097ff8b1
  18. 13 6月, 2022 2 次提交
  19. 30 5月, 2022 2 次提交
  20. 11 5月, 2022 1 次提交
  21. 04 5月, 2022 1 次提交
    • U
      Added non-destructive TinyUF2 support for UM ESP32-S3 boards (#6668) · ba591fd9
      Unexpected Maker 提交于
      Implemented a new method for allowing folks to preserve their TinyUF2 bootloader setup when flashing their boards via Arduino IDE, without being locked out of not using it if they want to use a different partition.
      
      Adafruit had already added support for keeping (reflashing) the TinyUF2 bootloader when flashing via Arduino IDE (thanks @Ladyada ), but the issue with it is it doesn't allow users to not choose to use it. Even if they select a specific partition scheme from the partition drop down list, it ignores that selection and only does the TinyUF2 partitioning/bootloader thing.
      
      We wanted to let users choose between keeping their TinyUF2 partitioning and bootloader, or choose another partition scheme and have the TinyUF2 support disabled and just operate like they would expect.
      
      We've implemented this by adding the TinyUF2 support as a partition scheme option, and using these build options in platform.txt to choose to use teh UF2 path or use the standard path.
      ba591fd9
  22. 27 4月, 2022 1 次提交
  23. 26 4月, 2022 2 次提交
  24. 28 3月, 2022 2 次提交
  25. 14 3月, 2022 1 次提交
  26. 02 3月, 2022 1 次提交
  27. 28 2月, 2022 1 次提交