Most recent activity
-
- 11 comments
- 2,843 views
-
-
Anytime i trie to use the debugger in any code i get this:
8 debugger; ^ debug> ets Jan 8 2013,rst cause:4, boot mode:(3,7) wdt reset load 0x40100000, len 2408, room 16 tail 8 chksum 0xe5 load 0x3ffe8000, len 776, room 0 tail 8 chksum 0x84 load 0x3ffe8310, len 632, room 0 tail 8 chksum 0xd8 csum 0xd8 2nd boot version : 1.6 SPI Speed : 80MHz SPI Mode : QIO SPI Flash Size & Map: 32Mbit(512KB+512KB) jump to run user1 @ 1000 Disconnected
Is it just some bug or am i doing something wrong?
-
-
I had a little trouble with the wifi connection of the ESP8244 4M (Firmware v1.93) lately.
Right now, i have this little bit of code:var wifi = require("Wifi"); var esp = require("ESP8266"); var WIFI_NAME = "DESKTOP-792U3CE 1298"; var WIFI_PASSWORD = "12345"; var sleepTime = 1000000; var cal = 4; function connect() { wifi.connect(WIFI_NAME, {password : WIFI_PASSWORD}, function(err) { if (err) { console.log("Connection error: "+err); return; } console.log("Connected!"); }); } function gn() { esp.deepSleep(sleepTime, cal); }
Basicly i tried to connect to wifi in various stages (directly after flashing, after saving and so on). It works fine up until after i sent the chip to deep sleep for the first time. In that case, when i try to connect, the blue system led will rapitly start blinking until i disconnect it. There's no error message or anything. Checking the wifi status it says "no_ap_found".
P.S. talking of deep sleep. i have a little issue with that to where it would exapt a number of microseconds that is far below what it should be able to take (only a few seconds in total). Unfortunatly a wasn't able to reconstruct the problem. it seems to happen quite random. It appears to be more likely with bigger scripts though
-
Hi,
i've already been asking this on a sidenote in another conversation but as it is becoming more critical right now i'll ask again specifically:
(copied from the other conversation)
P.S. talking of deep sleep. i have a little issue with that to where it would accept a number of microseconds that is far below what it should be able to take (only a few seconds in total). Unfortunatly a wasn't able to reconstruct the problem. it seems to happen quite random. It appears to be more likely with bigger scripts though