Search results for:

The issue here is this:

function writeFile() {
  global["writeFile0"](fileNum);
  if (++fileNum < maxFileNum) {
    setTimeout("writeFile()", 100);
  }
}

This is setting up 100 timeouts that will fire nealry at the same time. I think you are expecting them to queue up.

If you get rid of the setTimeout and just call writeFile() I think you will find it will run fine.

As you are writing to a new file and not closing the last file - you are running out of buffers. If you close the file when you are done with it - or write the same file I don't think you would have an issue.

Have a look at your free vars and also free heap. I would say you are running out of memory. The esp8266 is quite limited in ram.

Sorry, first I heard about it. Can you provide more information?

It it a new chip or a board?

This is normal behaviour for me. It seems the USB port gets in an odd state and physically disconnecting and reconnecting are nescessary.

This is why I usually connect WiFi and connect via IP address. I only use usb for flashing.

Is it a square wave you want or Is this testing?

You could use the pwm output and not use any loop code at all.

How long is a while?

It is possible that the USB port gets turned off for power saving after a period of inactivity.

here is the travis build with esp-idf 3.1:

https://www.espruino.com/binaries/travis/4f2b50f97887874339db5fae1f643fb6a6a47489/espruino_esp32.bin

@opichals
It seems the change you recently made force the PORT option to be used, and it wasn't in the past....
So I have removed that in a bleeding edge build - that used the esp-idf 3.1 binary:

https://www.espruino.com/binaries/travis/4f2b50f97887874339db5fae1f643fb6a6a47489/espruino_esp32.bin

When I connect the IDE I see a warning: setsockopt(SO_REUSPORT) failed. Is that expected?

@opichals made changes to this area recently
I have not personally tested the new build

I try to connect it to my router and see that the following is not working:

setHostname

This has not been implement at this stage. It requires using the mDNS library - and there was a move to do this in JS as a library rather than coding specifically for the ESP32 using esp-idf.
It could be added.

setConfig

I believe this is ESP8266 specific - I'm not sure other ports support it.

When the ESP32 was release there was not power mode options - there might be now - I have not looked recently.

In the ide I think you may get warnings, however the interpreter itself can handle the code.

From memory the acorn parser in the ide does not handle things like arrow functions.

It looks like you are using an esp8266 - and this has very limited memory - you could try the save on send option in the ide, and this might out put the code into flash, saving more ram space.

Ok. And I can do the same branch for build tools.

Do you want to raise an issue - or I can - and put in there the make file changes for the ESP-idf and then I can see if get that compiling as a first step?

How did you want to proceed?

Did you want to put this into the esp32 branch and then I can see if I can get a build?

https://github.com/espruino/EspruinoBuildTools/blob/master/esp32/build/app/partitions_espruino.csv

Looks like 1344k - pretty tight then!

The firmware size is not that important as it’s just flash space right?

What size did we make the partitions last time we changed?

At start up - why not create a 0-89 indexed float array and store the value of the sin at each index. Then when you want to use the value - it's just a simple lookup - no computation. You just need to do some manipulation of the index - so for 100deg look up the 80 degree value - and for > 180 flip the sign...

The compares might be slower so you could store the whole array - or 0-179.

You could even store fixed point values rather than floating point.

Push out the 5 secs - make it say 30 or 60 seconds.

I would guess that you are running out of sockets. You could tell by, on connect, print out the socket number. These should get reused - but I think you are re- connecting so quickly that they don't get a chance to get reused.

Go back and have a look at the sample: http://www.espruino.com/Writing+Modules

You need to add a constructor function and export the reference to that.

The bind your contants to that function. so if you called it myMod :

var myMod = function (options) {
  this.options = {}    || options;
};


myMod.C = {
  U : "up",
  D : "down",
  L : "left",
  R : "right",
  N : "north",
  E : "east",
  S : "south",
  W : "west",
  T : "top",
  M : "middle",
  B : "bottom"
};

exports = myMod;

my_mod=new myMod();
print my_mod.C.U;

Really need to see your code

Yes. Espruinobuildtools has the new bootlpoader.bin. The problem is that the Travis builds only save latest firmware.bin, not the zip of the complete set.

How are you loading code onto the board?

You seem to adding modules at run time loadModule('MQTT');'

If you use the web ide that is not necessary- and if connect with wifi and wifi.save() it will automatically reconnect when the board is powered up.

Oh - and it really needs to be fixed for the 3.0/3.1 ESP-idf version, so that it will work with the current releases.

@JumJum wrote the neopixel code on the esp32 using the ESP-idf rmt code. It's possible that a two channels might be using the same timers and that is what is screwing it up?

For the first time you need to flash all of the bin files - I suspect you only flashed the large firmware one.

The zip file for esp32 in the latest firmware release has all of the files.