1. 22 Jul, 2019 1 commit
  2. 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
  3. 30 Dec, 2016 1 commit
    • Johny Mattsson's avatar
      Updated to latest IDF. · 7abda5c9
      Johny Mattsson authored
      - Switched hardcoded interrupts to new IDF interrupt allocation
      framework.
      
      - gpio module switched to the IDF's per-pin interrupt callback service.
      
      - Improved NodeMCU linker script since it broke with the IDF upgrade.
      
      - Various compatibility updates.
      7abda5c9
  4. 27 Sep, 2016 1 commit
  5. 22 Sep, 2016 1 commit
  6. 20 Sep, 2016 1 commit
    • Johny Mattsson's avatar
      Successfully boot barebones NodeMCU on ESP32 (only). · 9bbf8f43
      Johny Mattsson authored
      RTOS driver evicted as it did not play nice with stdio etc.
      
      Implemented a minimal driver to fully support Lua console on UART0. Output
      on UART0 done via stdout (provided by the IDF). Input and setup handled
      via driver_console/console.c. In addition to the direct input function
      console_getc(), the driver also registers in the syscall tables to enable
      regular stdio input functions to work (yay!). The Lua VM is still using the
      direct interface since it's less overhead, but does also work when going
      through stdin/fd 0.
      
      Auto-bauding on the console is not yet functional; revisit when the UART docs
      are available.
      
      Module registration/linking/enabling moved over to be Kconfig based. See
      updates to base_nodemcu/include/module.h and base_nodemcu/Kconfig for
      details.
      
      The sdk-overrides directory/approach is no longer used. The IDF is simply
      too different to the old RTOS SDK - we need to adapt our code directly instead.
      
      Everything in app/ is now unused, and will need to be gradually migrated
      into components/ though it is probably better to migrate straight from the
      latest dev branch.
      9bbf8f43