ildar
Does nobody like Busted over RPC ?
ildar
π
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=1
will build the firmware with the Lua 5.3 runtime and enable the T
test module support in luac.cross -e
T
module 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.
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: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.
@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...
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 )))ildar
Hi, Terry,ildar
so WHEN this to be done, what pattern is to be used?btw:
Which is faster?
A. if (x >> 14 > 0) {}
B. if (x > 16384) {}
and
I heard that Strings suck.
Is there a way I can avoid using it (in a way that makes sense, performance-wise), here?
String s = "";
int i, n;
for(i=0; i<lenght; i++) {
s += (char)payload[i];
}
n = s.toInt();
(using Arduino language)
@poorandunlucky Patrick, I know perhaps 2 dozen languages and assembler variants, but have only used half of these professionally. In my view one of the essentials of coming to new language is to ask yourself
It is a mistake to attempt write in language Y as if it were language X, simply because you happened to learn language Y first.