Problem with E.toString in Espruino 1v95 on ESP8266-4MB #6005
Replies: 1 comment
-
Posted at 2018-02-03 by @MaBecker E.toString() is working perfect and is not the root cause. It is no a good idea to block the esp with large outputs, because this can cause a reboot :) Hint: use tdata.fill(0x30) Posted at 2018-02-03 by DrAzzy Is the issue that you got bitten by the watchdog as MaBe suggested? Or are you claiming the output of E.toString() is incorrect? (it's not, 0x30 is ascii code for "0" ) Posted at 2018-02-04 by ClearMemory041063 It were the watchdog timer doing the reset.
The emit and drain are simulating serving data to a socket. Gordon has addressed the problem shown by commenting out the process.memory, but his fix isn't in the published 1v95 code yet. Thanks for the tip about the watchdog. The ESP8266 Espruino is a different paradigm from the Pico. Is there a similar watchdog in the ESP32 Espruino? Posted at 2018-02-04 by @gfwilliams Have you tried this on the cutting edge builds yet to see if it's any different? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2018-02-03 by ClearMemory041063
Problem with E.toString in Espruino 1v95 on ESP8266-4MB
Erase flash
Flash the chip (uses DIO)
4 Here's the output
Skipping some output to save space
Beta Was this translation helpful? Give feedback.
All reactions