Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    matrixbot
    @matrixbot
    flux you could get an external RTC, they are very energy-efficient
    uDude
    @uDude

    @Liriel > does anyone know if the so called RTC on the ESP8266 is actually backed by peripheral hardware? It seems to loose a few seconds here and there...

    a bit late, but I use sntp so you don't have to change your rtc code (external rtc is probably more energy efficient)

    manulari
    @manulari
    hey,
    I have an ESP32 board. I have some trouble figuring out if I should be building the Lua 5.3 or the Lua 5.1 variant of nodemcu, and which git branch I should be using for that, and what the correct make invocation is. (I'm on linux.)
    would be glad about any pointers. I think I tried to read the documentation that's up on readthedocs rather thoroughly.
    manulari
    @manulari
    the dev-esp32 branch seems to be drifting apart from dev and release, and one of the documents mentioned something about there at least being a plan of building all variants from the same git branch, so I was wondering which one is the correct one for me...
    Marcel Stör
    @marcelstoer
    You'll want the dev-esp32 branch. https://nodemcu.readthedocs.io/en/dev-esp32/build/ documents three options how to build for ESP32.
    manulari
    @manulari
    thank you! is the Lua 5.3-variant consumption ready on that branch?
    Thomas Jakober
    @tjakober
    Does ow (one-wire) on esp32 only work on pin 3? It seems to use a mux port.
    matrixbot
    @matrixbot
    ildar AFAIK NodeMCU owns the most advanced Lua on MCU implementation (thanks to Terry all you awesome devs :-))). Agree?
    matrixbot
    @matrixbot
    ildar Then it's very natural that other MCU-platform would want to have it.
    I just checked uPython and Espruino projects. They both have multiplatform source. I.e. building for different MCU patforms and adding new port is relatively easy. With NodeMCU we still aiming to join two targets in one tree.
    ildar Anyone looked at the above sources thinking if we could simply take that as a basis for the new united tree?
    matrixbot
    @matrixbot
    flux ildar: btw, there's a new gitter bridge coming up (and is already available for testing): #nodemcu_nodemcu-firmware:gitter.im - should provide a smoother experience on gitter side, where all matrix-originated communication from this room appear to come from a bot
    ildar
    @ildar:matrix.org
    [m]
    flux: ahh!! Yes, at last!!!
    ildar
    @ildar:matrix.org
    [m]
    summoning @TerryE
    225559
    @225559
    Hi NodeMCU developers,
    I'm curious if there's any interest in having a NodeMCU section on Lua forum?
    Marcel Stör
    @marcelstoer
    @225559 We send users to StackOverflow and esp8266.com for help: https://nodemcu.readthedocs.io/en/latest/support/. I can only speak for myself. I don't have the capacity to monitor another forum for support requests, sorry.
    Terry Ellison
    @TerryE
    Sorry @ildar:matrix.org I missed your poke. Wazzup?
    ildar
    @ildar:matrix.org
    [m]
    ))
    Nothin. Havin' a drink, watchin' a game
    😜
    Ok, seriously
    I see eLua is mostly dead
    No good reason to develop it
    NodeMCU is great but single platform
    Even ESP32 is out of the game
    ildar
    @ildar:matrix.org
    [m]
    Two tree merge is discussed for quite a time. But i doubt think it's a good way to go anymore
    *I don't think
    I want to know what you think
    Terry and others, for sure
    Terry Ellison
    @TerryE
    eLua hasn't had a commit for 18 months. We are still ticking along. I personally have had a house project going and then some health issues over the last few months so haven't been doing much on NodeMCU, but I am getting past those and now in catch up mode. I want to get the on-ESP version of LFS up and running, and then hope to switch to a common Lua core for ESP32 and ES8266. Hopefully Johnny will be able to support this.
    ildar
    @ildar:matrix.org
    [m]
    I see
    I'm quite sure the problem should be approached from the other end
    get a proper source tree that builds fine.
    then add core Lua
    and other core things
    then modules
    after that having other platforms added (ESP32)
    And proper source tree is a tree that is already multi-platform, I mean
    that's why looking at uPython, Espruino, whatnot
    1 reply
    Terry Ellison
    @TerryE
    NodeMCU allows you to run with ~ 256Kb code + constant in Flash and leaves ~44Kb for program data. uPython has the same RAM-only constraints and NodeMCU 1.x
    Read the LFS papers for discussions on this.
    Terri Prifti
    @tprifti
    Hello, recently I am working on building modules and it is working fine. I compile all modules into LFS image. By reading LFS Example I assume that I can access modules by LFS.{modulename}. I have also seen examples that executes LFS modules by using dofile method (by replacing the built in dofile to load module from LFS if present). My question is, which is the suggested way?
    Gregor Hartmann
    @HHHartmann
    In the end it depends on your preference. I tend to use the dofile (or require) method because they prefer SPIFFS over LFS, so that I can upload lua files for testing and development and don't have to flash the whole LFS on every dev cycle. It also allows to use the code without LFS (as long as memory allows). But others prefer to reflash on every cycle. So it's up to you.
    Terri Prifti
    @tprifti
    During development, I also use dofile which speeds up development process. When implementation in finished and let's say everything is working fine, both ways that I described, are modules being read from LFS and not from RAM?
    M.K.
    @mk-pmb
    @tprifti when you have the final version, flash it to LFS, remove modules from SPIFFS, and reboot. then LFS is the only possible source where they could be loaded from. and when they're loaded from LFS, they'll inflict minimal RAM cost.
    Terri Prifti
    @tprifti
    @mk-pmb That's really helpful, thank you!
    Thomas Jakober
    @tjakober
    Hello, since a while i get very rare error messages about bugs on my NodeMCU. First I thought ist a parameter in my firmware builds. So I made a cloud build but it‘s the same. Could it be somewhere in context with LFS handling? Is there some parameter which suppresses error messages? Its very annoying to find bugs in my programs without error messages.
    Thomas Jakober
    @tjakober
    edit: the errors just lead into a reboot without any message. Boot message is wdt reset.
    Thomas Jakober
    @tjakober
    edit: I found the cause: I „banned“ the LFS routines ex init.lua from the samples to the LFS itself. In turn I use node.LFS.get to load it. However this suppresses all error messages therafter. Perhaps you have a clue why this is the case?
    Thomas Jakober
    @tjakober
    edit again: problem solved. I had a global „debug = true“ statement to switch my own error logging on and off. This caused to suppress all error messages.