1. 30 May, 2016 2 commits
  2. 27 May, 2016 1 commit
  3. 26 May, 2016 4 commits
  4. 24 May, 2016 2 commits
    • Johny Mattsson's avatar
      Reimplemented the NodeMCU task interface on top of RTOS. · 5c39a1f6
      Johny Mattsson authored
      Not yet hooked up to an RTOS task, however.
      5c39a1f6
    • Johny Mattsson's avatar
      Initial pass at switching to RTOS SDK. · f3e2a3af
      Johny Mattsson authored
      This compiles, links, and starts the RTOS without crashing and burning.
      
      Lua environment does not yet start due to the different task architecture.
      
      Known pain points:
      
        - task implementation needs to be rewritten for RTOS (next up on my TODO)
      
        - secure espconn does not exist, all secure espconn stuff has been #if 0'd
      
        - lwip now built from within the RTOS SDK, but does not appear to include
          MDNS support. Investigation needed.
      
        - there is no access to FRC1 NMI, not sure if we ever actually used that
          however. Also #if 0'd out for now.
      
        - new timing constraints introduced by the RTOS, all use of ets_delay_us()
          and os_delay_us() needs to be reviewed (the tsl2561 driver in particular).
      
        - even more confusion with ets_ vs os_ vs c_ vs non-prefixed versions.
          In the long run everything should be switched to non-prefixed versions.
      
        - system_set_os_print() not available, needs to be reimplemented
      
        - all the RTOS rodata is loaded into RAM, as it ...
      f3e2a3af
  5. 22 May, 2016 1 commit
  6. 21 May, 2016 2 commits
  7. 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
  8. 16 May, 2016 1 commit
  9. 15 May, 2016 1 commit
  10. 14 May, 2016 2 commits
  11. 13 May, 2016 2 commits
  12. 12 May, 2016 1 commit
  13. 10 May, 2016 2 commits
  14. 09 May, 2016 1 commit
    • Thomas Soëte's avatar
      Finalize work on ws2812 module · 0577c8af
      Thomas Soëte authored
      * Fix bug on first write
      	Pin is 'HIGH' at reset, so we need to pull it down and generate a
      	reset.
      
      * Move init code to flash section, not needed to be in iram.
      
      * Remove pin choice in API
      
      * Remove lock in ws2812_buffer_write
      
      * Remove naked malloc
      
      * Drop ws2812_writergb
      
      * Drop support of ws2812.buffers to ws2812_writegrb should use ws2812.buffers:write
      
      * Add support for <>3 colors per leds strips (RGBW)
      
      * Remove ICACHE_FLASH_ATTR
      
      * Add static const on _uartData to avoid initialization penalty
      0577c8af
  15. 02 May, 2016 2 commits
  16. 01 May, 2016 1 commit
  17. 30 Apr, 2016 1 commit
  18. 29 Apr, 2016 2 commits
  19. 28 Apr, 2016 3 commits
  20. 26 Apr, 2016 3 commits
  21. 25 Apr, 2016 1 commit
  22. 24 Apr, 2016 1 commit
  23. 19 Apr, 2016 1 commit
  24. 18 Apr, 2016 1 commit