I am trying to flash some ESP-01 with a minimal integer build, but after flashing, the blue led is stuck flashing rapidly and I get a ton of garbage out the serial port. I don't know what else to tweak. I already tried different modules and erasing the flash. Any clues? @TerryE @marcelstoer ?
I haven't tested on ESP-01 for years. My entry level for testing it the Wemos-D1 mini
The lack of IOs on the 01 make it almost unusable, IMO. The nearest that I do use is the Sonoffs, but they have 2Mb flash.
@jpeletier minimal integer of what? We're keeping that frozen 1.5.4.1 branch around at https://github.com/nodemcu/nodemcu-firmware/tree/1.5.4.1-final because it's the last known-to-be working version on ESP-01. Later SDKs became so much larger that Espressif labeled them as unfit for ESP-01 IIRC.
@TerryE @marcelstoer Thanks, that's probably the problem. I was not taking into accoun the SDK upgrade and how it affects these modules. @TerryE The ESP-01 is almost unusable, right, but I had one of this laying around (https://www.banggood.com/5V-ESP8266-Dual-WiFi-Relay-Module-Internet-Of-Things-Smart-Home-Mobile-APP-Remote-Switch-p-1270421.html?cur_warehouse=CN) and wanted to use it to deal with the garage door. I ended up writing something in Arduino/C to be able to make use of it.
Out of curiosity, why doesn't it work? Everything seemed to flash just normally: 380-400kB in a 512kB flash. Why wouldn't it work?
@TerryE I use esp-01 black typically with 1MB flash. It works well for quite a few things e.g., I have a one at each outside faucet for turning on/off water solenoids (can't afford a centralized system,) I have a on/off only heater control using signed mqtt and polling for control, and other stuff.
I do build my own nodemcu/lua for it. An aside, on the 4MB modules I love LFS. Many thanks for your work.
Is there a readme or pinned post to read before I post a question?
ildar Does nobody like Busted over RPC ?
ildar π
I am wading through the issues related to getting our Lua 5.3 port from alpha to beta, and currently I am the only contributor actively working on the Lua core. I am using the Lua test suite in the
luac.cross -e environment as part of my test strategy (this runs the NodeMCU execution environment including ROTable support on the host). Part of these tests can run on a standard Lua VM, but part also require the core to be modified with the Test Suite patches. make LUA=53 TEST=1will build the firmware with the Lua 5.3 runtime and enable the T test module support in luac.cross -e
My intention is to run the subset of the test suite that doesn't require the
Tmodule on ESP, but delivered through one or more LFS images. I will also extend this to add test vectors for some of the core nodemcu modules.
If you've come from the world of have I got 4 Gb to work with or is 8 ... then getting your head around living within 44Kb is quite hard.
You can't assume that a reused infrastructure stack will be able to load, let alone run an effective application.
So whether we like Busted vs. RPC vs. some raw socket implementation really starts with "here is an example of my RPC-like system running this non-trivial application". This is with a git library containing this host end and this ESP client end. If you can't provide a decent example showing that you've addressed the RAM constraints for at least one realistic usecase, then the debate is purely academic.
ildar I'm sure using LFS would make it slim
ildar And definitely I don't intend to distance you from the important Lua platform change
ildar > <@ildar:matrix.org> And definitely I don't intend to distance you from the important Lua platform change
I mean distract
ildar Terry, as promised:https://johan-notes.blogspot.com/2019/10/ram-footprint-of-tango-rpc-on-nodemcu.html
@jpeletier Javier, it's because the work to port it was never done. The
file library was created as a stop-gap and has hung around ever since. See #2145 comment. Testing the file module comprehensively is a PITA. adding io is definitely a wish list item but it all comes down to priorities and time.
Δ° tried both ways but they did not work. I set NodeMcu ESP8266 12E on Arduino IDE then i used this libraries: https://github.com/adafruit/Adafruit-GFX-Library and https://github.com/adafruit/Adafruit_SSD1306 . Then i try ssd1306_128x64_i2c example in Adafruit_SSD1306 library. When i run the program i get this but there is nothing on the led.
@eliffakgunn
Δ° tried both ways but they did not work. I set NodeMcu ESP8266 12E on Arduino IDE then i used this libraries: https://github.com/adafruit/Adafruit-GFX-Library and https://github.com/adafruit/Adafruit_SSD1306 . Then i try ssd1306_128x64_i2c example in Adafruit_SSD1306 library. When i run the program i get this but there is nothing on the led.
When i run the progam i get this: *
esptool.py v2.6
2.6
esptool.py v2.6
Serial port COM4
Connecting....
Chip is ESP8266EX
Features: WiFi
MAC: a0:20:a6:1b:28:96
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 290176 bytes to 209656...
Writing at 0x00000000... (7 %)
Writing at 0x00004000... (15 %)
Writing at 0x00008000... (23 %)
Writing at 0x0000c000... (30 %)
Writing at 0x00010000... (38 %)
Writing at 0x00014000... (46 %)
Writing at 0x00018000... (53 %)
Writing at 0x0001c000... (61 %)
Writing at 0x00020000... (69 %)
Writing at 0x00024000... (76 %)
Writing at 0x00028000... (84 %)
Writing at 0x0002c000... (92 %)
Writing at 0x00030000... (100 %)
Wrote 290176 bytes (209656 compressed) at 0x00000000 in 18.6 seconds (effective 124.8 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
what is the meaning of
Leaving...
Hard resetting via RTS pin...
you need to use the rtcmem module and struct to pack your state into the memory block. Read the documentation. Use SPIFFS for low volatility config data. I just use
sjson to pack/unpack it and file.putcontents() and file.getcontents()to save/ restore. RTCmem is best for high volatility state data that you want to persist from boot to boot, but remember it gets trashed if you have a total powerfail.
ildar greetings! want to raise a little flame. You are warned )))API question: there are quite many platforms working with hardware directly (mainly targeting MCU): Arduino, Espruino, libopencm3, mPython, NodeMCU (in alphabetical order) and more. I think it really makes sense to have similar APIs instead inventing own.
We have different APIs for 8266 and 32. They must come to one API. Is it worth going closer to neighbor friends or not? just asking ))
Evolution doesn't work top down
We do intend to converge the two ESP architectures when we can resource it
ildar Hi, Terry,no, I'm not volunteering to do ALL of the leg work, sorry. Yet I believe that this work may be done (more or less) gradually, like in https://github.com/nodemcu/nodemcu-firmware/issues/1657#issuecomment-520635406
ildar so WHEN this to be done, what pattern is to be used?This is generally the topic of my question
I have a function that I wrote that converts BCD to decimal, and while it works in a console running Lua 5.1.5, it fails on the board... It's a arithmetic comparison, and it's probably me who's too tired as usual, or who doesn't know a peculiarity, but it says 9 > 9 = true... Like if I paste the file in a console running Lua 5.1.5, it runs OK; if I paste it in a terminal to my ESP12-E, the error gets triggered. Link: https://gist.github.com/poorandunlucky/7f0e29cf694ed37bb9e569752412ac09