1. 13 May, 2017 1 commit
  2. 12 May, 2017 1 commit
  3. 07 May, 2017 1 commit
    • zelll's avatar
      ESP32: CAN module (#1958) · ff30f479
      zelll authored
      * can extension
      
      * can extension: bit timing and filter
      
      * can -> CAN
      
      * post CAN data callback
      
      * CAN docs
      
      * CAN: fixed receive, filter, extended frame
      
      * reorder fn in can.md, remove driver_can/Kconfig
      
      * fixed a leak when can.stop()
      ff30f479
  4. 06 May, 2017 1 commit
  5. 30 Apr, 2017 1 commit
  6. 27 Apr, 2017 1 commit
  7. 24 Apr, 2017 1 commit
  8. 23 Apr, 2017 1 commit
  9. 15 Apr, 2017 1 commit
  10. 14 Apr, 2017 3 commits
  11. 27 Mar, 2017 1 commit
  12. 24 Mar, 2017 1 commit
  13. 17 Mar, 2017 1 commit
  14. 08 Mar, 2017 2 commits
  15. 07 Mar, 2017 1 commit
  16. 02 Mar, 2017 3 commits
  17. 04 Feb, 2017 1 commit
  18. 02 Feb, 2017 1 commit
  19. 13 Jan, 2017 1 commit
  20. 03 Jan, 2017 1 commit
  21. 17 Nov, 2016 2 commits
  22. 05 Oct, 2016 1 commit
  23. 29 Sep, 2016 1 commit
  24. 22 Sep, 2016 3 commits
  25. 21 Sep, 2016 2 commits
  26. 02 Jun, 2016 1 commit
  27. 22 May, 2016 1 commit
  28. 18 May, 2016 2 commits
    • Marcel Stör's avatar
      ab6c2c39
    • Johny Mattsson's avatar
      Rework ADC mode setting approach (#1285) · 30d354c2
      Johny Mattsson authored
      - Stop fighting against the SDK in terms of owning/writing the init_data block.
        NodeMCU included a default init_data block because originally the SDK did
        not, but by now it's not needed.
      
      - Expose a way to reconfigure the ADC mode from Lua land. With most people
        using the cloud builder and not able to change the #define for byte 107
        this has been a pain point.
      
      - Less confusion about which init_data has been used. Lua code can now simply
        state what mode it wants the ADC to be in, and not worry about the rest of
        the init_data complexities such as the init_data changing location due to
        flashing with wrong flash_size setting, or doing/not doing a chip-erase
        before loading new NodeMCU firmware.
      30d354c2
  29. 16 May, 2016 1 commit
  30. 15 May, 2016 1 commit