1. 22 Aug, 2020 1 commit
  2. 03 Aug, 2020 1 commit
    • David Thornley's avatar
      Fix bthci compilation issue (#3201) · 7774b5fa
      David Thornley authored
      Manifests as multiple definition of esp_event_send during compilation, as bthci triggers inclusion of `event_loop.c`. Also improved lbth_init() to support BTDM or BLE_ONLY controller modes.
      7774b5fa
  3. 27 Jul, 2020 1 commit
  4. 08 Jul, 2020 1 commit
  5. 30 Jun, 2020 1 commit
  6. 20 Jun, 2020 2 commits
  7. 18 May, 2020 2 commits
  8. 02 May, 2020 1 commit
  9. 01 May, 2020 1 commit
  10. 30 Apr, 2020 1 commit
  11. 29 Apr, 2020 1 commit
    • David Thornley's avatar
      Address build error when path contains whitespace · 2a9bf13a
      David Thornley authored
      The path environment under Windows Subsystem for Linux typically 
      contains paths with spaces.
      
      Error Manifests as: -
      
      Setting IDF_PATH and re-invoking...
      /bin/sh: 1: Syntax error: "(" unexpected
      Makefile:21: recipe for target 'flash' failed
      
      Tested on Ubuntu 18.04 both on Linux proper and WSL.
      2a9bf13a
  12. 27 Apr, 2020 1 commit
  13. 26 Feb, 2020 1 commit
  14. 11 Feb, 2020 1 commit
  15. 09 Feb, 2020 1 commit
  16. 19 Jan, 2020 1 commit
  17. 06 Jan, 2020 3 commits
  18. 05 Jan, 2020 1 commit
  19. 29 Oct, 2019 1 commit
  20. 27 Oct, 2019 1 commit
    • John Lauer's avatar
      Add touch sensor module (#2863) · 9a5327ca
      John Lauer authored
      * Touch module 1st checkin
      * ESP32. Check-in 2 for Touch sensor module
      * ESP32: Touch module. Sample Lua code.
      * ESP32: Latest YouTube vid
      * ESP32: Touch docs update
      * Added opt_* methods for value retrieval
      9a5327ca
  21. 12 Oct, 2019 1 commit
    • Johny Mattsson's avatar
      Fix uart regressions & bugs (#2817) · b0558d5b
      Johny Mattsson authored
      * Fix uart regressions & bugs.
      
      Using `uart.on()` with a search character was broken in that it did
      not invoke the callback on a full UART buffer as documented. Logic reworked
      to match docs again.
      
      Fixed memory leak on `task_post()` failure (eep!).
      
      Improved logic to attempt to coalesce input bytes to reduce the number of
      `task_post()` slots used up by the platform uart.
      
      Finally, added a semaphore to prevent the platform uart from overrunning
      the `task_post()` slots all the time on high baud rates (e.g. 1mbit).
      With the semaphore in there, the LVM RTOS task gets a chance to actually
      process the received data and free up a `task_post()` slot or two.
      The above mentioned read coalescing then allows the platform uart to
      immediately catch up.
      
      Also added an error log message if the `task_post()` actually does fail.
      
      * Don't cache the uart delims.
      
      Doing so makes reconfiguring those settings from within the callback not
      take effect until the currently buffered bytes have been processed.
      b0558d5b
  22. 27 Sep, 2019 1 commit
  23. 12 Aug, 2019 1 commit
  24. 01 Aug, 2019 1 commit
  25. 23 Jul, 2019 1 commit
  26. 22 Jul, 2019 1 commit
  27. 20 Jul, 2019 1 commit
  28. 19 Jul, 2019 1 commit
  29. 14 Jul, 2019 1 commit
    • Johny Mattsson's avatar
      Fix net module data loss & RTOS task unsafety (#2829) · f44e6e96
      Johny Mattsson authored
      To avoid races between the lwIP callbacks (lwIP RTOS task) and the Lua
      handlers (LVM RTOS task), the data flow and ownership has been simplified
      and cleaned up.
      
      lwIP callbacks now have no visibility of the userdata struct. They are
      limited to creating small event objects and task_post()ing them over
      to the LVM "thread", passing ownership in doing so. The shared identifier
      then becomes the struct netconn*.
      
      On the LVM side, we keep a linked list of active userdata objects. This
      allows us to retrieve the correct userdata when we get an event with
      a netconn pointer. Because this list is only ever used within the LVM
      task, no locking is necessary.
      
      The old approach of stashing a userdata pointer into the 'socket' field
      on the netconn has been removed entirely, as this was both not
      thread/RTOS-task safe, and also interfered with the IDFs internal use
      of the socket field (even when using only the netconn layer). As an
      added benefit, this removed the need for all the SYS_ARCH_PROTECT()
      locking stuff.
      
      The need to track receive events before the corresponding userdata object
      has been established has been removed by virtue of not reordering the
      "accept" and the "recv" events any more (previously accepts were posted
      with medium priority, while the receives where high priority, leading
      to the observed reordering and associated headaches).
      
      The workaround for IDF issue 784 has been removed as it is now not needed
      and is in fact directly harmful as it results in a double-free. Yay for
      getting rid of old workarounds!
      
      DNS resolution code paths were merged for the two instances of "socket"
      initiated resolves (connect/dns functions).
      
      Also fixed an instance of using a stack variable for receiving the resolved
      IP address, with said variable going out of scope before the DNS resolution
      necessarily completed (hello, memory corruption!).
      
      Where possible, moved to use the Lua allocator rather than plain malloc.
      
      Finally, the NodeMCU task posting mechanism got a polish and an adjustment.
      Given all the Bad(tm) that tends to happen if something fails task posting,
      I went through a couple of iterations on how to avoid that. Alas, the
      preferred solution of blocking non-LVM RTOS tasks until a slot is free
      turned out to not be viable, as this easily resulted in deadlocks with the
      lwIP stack. After much deliberation I settled on increasing the number of
      available queue slots for the task_post() mechanism, but in the interest
      of user control also now made it user configurable via Kconfig.
      f44e6e96
  30. 11 Jul, 2019 1 commit
    • Johny Mattsson's avatar
      Fix net module losing TCP data. (#2825) · c0145e03
      Johny Mattsson authored
      The netbuf_data() function only returns data from the first pbuf in the
      chain. We need to use netbuf_first() and netbuf_next() to walk the
      pbuf chain and act on each in turn.
      c0145e03
  31. 10 Jul, 2019 1 commit
  32. 06 Jul, 2019 2 commits
  33. 04 Jul, 2019 1 commit
    • Johny Mattsson's avatar
      Improved crypto module for ESP32, now with HMAC (#2815) · e11087bf
      Johny Mattsson authored
      * Leaner, meaner crypto module; now with HMAC
      
      Based on my testing, mbedtls pulls in all its algorithm regardless of
      whether the NodeMCU crypto module was using them or not. As such, the
      space savings from omitting algorithms were only in the tens of bytes.
      
      By switching to using the mbedtls generic message digest interface, the
      crypto module itself could be shrunk in size and complexity. Despite
      adding support for HMAC on all algorithms (plus including RIPEMD160),
      this version is 330 bytes smaller.
      
      * Updated crypto module docs.
      
      * Removed superfluous brackets in crypto docs.
      
      Copy-paste considered harmful... >.>
      e11087bf
  34. 03 Jul, 2019 1 commit
  35. 22 Jun, 2019 1 commit
    • Johny Mattsson's avatar
      Reworked linker magic to work with IDF 3.3 (#2805) · 51912d55
      Johny Mattsson authored
      With the IDF asserting full control over the linker scripts and insisting on
      the application description being the first entry in the .flash.rodata
      section, or previous method of doing link-time arrays stopped working.
      Why? Because the build patched in a SHA256 digest straight into our arrays.
      
      With the limited language of the gcc linker scripts I could find no other
      way of getting it in cleanly.
      
      The IDF "linker fragments" support can not be made to work for our needs:
        - no support for setting alignment before including objects
        - no support for declaring symbols
        - no support for adding our terminating zeros
        - insists on grouping objects by lib rather than by declared grouping,
          which means we could at most have a single link-time-array using
          the IDF mechanism
        - also does not like underscores in section names, but that's just an
          annoyance
      
      So, the least bad option that I could come up with was to use a project-wide
      makefile snippet to add a target in-between the IDF's generation of the
      esp32.project.ld file, and the linking of our NodeMCU.elf. In this target
      we read in the esp32.project.ld linker script, check whether we have our
      arrays in there, and if not rewrites the linker script.
      
      Oh, and the esp32.project.ld file only came into existence on the IDF 3.3
      branch, so I had to change up the IDF to the latest release/3.3 as well.
      I would've preferred a stable tag, but the v3.3-beta3 had a really nasty
      regression for us (can't add partition entry), so that was a no-go.
      51912d55