Search results for:

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

Is there any way to debug my code externally? Like some tool using a virtual machine or something like that?

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'm afraid it's offline again. Or does it even still work?

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

It's a 4m board. Also, as i said, it has already prooven to work (a number of times)

never done it anyway else ;)

I've tried to flash the firmware v1.93 on the ESP8266, which has worked just fine previously, and got this: see below

This is the second time this happens on an ESP8266. When trying to connect to the chip anyways, it just fires random bs constantly.

does anybody know how to solve this?

EDIT: Oh , and of course i've tried it multiple times

so i just made a short test and it seems that while save leaves the set boot code untouched E.setBootCode ereases everything that has been saved prior

But would a save() erease that? Because otherwise that would only work once.

Hey Folks,

so I'm working on a project, as part of which some code has to be executed on every wake up or power on but NOT after saving, mainly because a save can be the result of whats executed in onInit().

My first approach was to just check within the onInit function if the content should be executed via a boolean. It looks something like this.

var esp = require("ESP8266");
var runInit = true;
var sleepTime = 60000000;

function qsave() {
   runInit = false;
   save();
}

function stuffToDo() {
//Some code/changing variables
qsave();
esp.deepSleep(sleepTime, 1);
}

function onInit() {
   if (runInit) {
       stuffToDo();
   }
   else
      runInit = true;
}

So I think the problem here is pretty obvious. Once the runInit is set false it can effectively not be set back to true as it is not saved and thus lost as soon as the chip restarts.

Right now i can't really think of any way around this, so if anyone has got an idea, i'd be very thankful.

P.S. I already tried overwriting the reset reason propertie when saving so when reseting it would be set back to an actual reset reason. But it seems (and rightfully so, i guess) espruino doesn't allow the propertie to overwriten by the script.

EDIT: Oh by the way, please tell me if there's any way to store single values directly without the use of an additional module because always overwriting the whole flash evertime i have to save some variable changes is pretty inefective in the long run anyway and of cause that would solve my problem with onInit()