1. 07 Feb, 2024 1 commit
    • Christoph Thelen's avatar
      Update rmt translator (#3629) · 14cdff10
      Christoph Thelen authored
      * Choose the number of RMT buffers in the ws2812 module.
      
      The number of buffers required for optimal operation should be selected
      by the ws2812 module, not the caller.
      
      * Add parameters for RGB LED bit times.
      
      This patch adds compatibility for different RGB LEDS besides the WS2812.
      ESP evaluation boards like the ESP32-C3-DevKitM-1 use an SK68XXMINI-HS
      RGB LED which does not respond to the timings of this module.
      The patch adds optional parameters for the bit timings to the write
      function. If the new parameters are not supplied, the old values are used.
      An example for the SK68XXMINI-HS is provided in the documentation.
      
      * Remove restrictions from RTM translator.
      
      The old RMT translator was not able to split the bits of the source
      data into the size requested by the RMT transmitter. Either all 8 bits
      of an input byte were translated or none.
      The new routine removes the restriction by delivering exactly the
      requested amount of data to the transmitter, which results in a more
      balanced buffering of translated data under load.
      
      * Add a parameter for the RGB LED reset time.
      
      This patch introduces a new optional parameter for the reset time
      in the RGB LED communication. The default is 51.2 microseconds. A
      value of 0 sends no reset signal, which allows a small optimisation
      for consecutive write commands.
      
      Please note that the reset time of the old code should be 50
      microseconds, as the define WS2812_DURATION_RESET suggested. Due to the
      restrictions of the old RMT translator routine, it was slightly
      increased to 51.2 microseconds. This patch keeps the value of 51.2
      microseconds to be as compatible as possible.
      
      * Minimize the time drift between RMT channels.
      
      Place all RMT channels in a group to minimize the time drift between
      the signals. Please note that this feature is not available on all
      platforms.
      
      * Fix the description of the SK6812 LED in the example code.
      
      The SK6812 expects the data for the green LED first, then red and
      finally blue. It should be described as a GRB LED.
      14cdff10
  2. 30 Jan, 2024 1 commit
    • Johny Mattsson's avatar
      Initial migration to IDFv5.0 · f126b6fe
      Johny Mattsson authored
      Plenty of dependency adjustments, printf format specificier updates,
      FreeRTOS type and macro name modernisation, not to mention API changes.
      
      Still plenty of legacy/deprecated drivers in use which will need updating.
      
      The following features have been removed due to no longer being available
      from the IDF:
        - ADC hall effect sensor reading
        - Configuration of SD SPI host via sdmmc module (now must be done first
          via the spimaster module)
        - FAT partition selection on external SD cards; only the first FAT
          partition is supported by the IDF now
      
      On the other hand, the eth module now supports the following new chipsets:
        - KSZ8001
        - KSZ8021
        - KSZ8031
        - KSZ8051
        - KSZ8061
        - KSZ8091
        - Possibly additional models in the LAN87xx series (the IDF docs aren't
          clear on precisely which models are handled)
      
      Further, the sdmmc module is now available on the ESP32-S3 as well.
      f126b6fe
  3. 13 May, 2023 1 commit
    • Tom Sutcliffe's avatar
      Fix ws2812 on later esp32 variants · 1b38d8e6
      Tom Sutcliffe authored
      By not relying on the internal details of the RMT registers. For example
      on the esp32s2, the threshold event bits start at bit 12 not bit 24, and
      on the esp32s3 the memory buffers are only 48 words not 64. Also the
      esp-idf recommends against hooking the rmt ISR in the first place.
      
      Instead, use the published rmt APIs (specifically rmt_write_sample and
      rmt_translator_init) and the default rmt ISR, which should be much more
      resilient against future esp32 SoC changes.
      1b38d8e6
  4. 12 Oct, 2022 1 commit
    • Johny Mattsson's avatar
      Upgrade IDF to v4.4.2 · 38ccd7b2
      Johny Mattsson authored
      Slightly reworked embed_lfs.sh to better cope with attribute size changes
      in future compiler versions, without needing to be updated again.
      
      RMT register naming changed once again...
      38ccd7b2
  5. 04 Jun, 2022 1 commit
    • h2zero's avatar
      Explicitly set RMT config::flags. · b8ae6ca6
      h2zero authored
      If this variable is not set in the config it may contain random data and set the clock source to the REF_CLK
      resulting in timing errors, the DHTx, DS18B20 and ws2812 devices to not communicate.
      b8ae6ca6
  6. 07 Jan, 2022 1 commit
  7. 24 Aug, 2021 1 commit
  8. 22 Aug, 2021 1 commit
  9. 11 Aug, 2021 1 commit
    • Johny Mattsson's avatar
      Add ESP32C3 support/coexistence. · f123d462
      Johny Mattsson authored
      The uzlib and parts of Lua had to be switched over to use the
      C standard int types, as their custom typedefs conflicted with
      RISC-V toolchain provided typedefs.
      
      UART console driver updated to do less direct register meddling
      and use the IDF uart driver interface for setup. Still using our
      own ISR rather than the default driver ISR. Down the line we
      might want to investigate whether the IDF ISR would be a better
      fit.
      
      Lua C modules have been split into common and ESP32/ESP32-S
      specific ones. In the future there might also be ESP32-C3
      specific modules, which would go into components/modules-esp32c3
      at that point.
      
      Our old automatic fixup of flash size has been discarded as it
      interferes with the checksumming done by the ROM loader and
      results in unbootable systems. The IDF has already taken on
      this work via the ESPTOOL_FLASHSIZE_DETECT option, which handles
      this situation properly.
      f123d462
  10. 31 May, 2019 1 commit
  11. 12 Sep, 2017 1 commit
  12. 20 Jun, 2017 1 commit
  13. 27 Apr, 2017 1 commit
  14. 14 Apr, 2017 1 commit