You are reading a single comment by @Sacha and its replies. Click here to read the full conversation.
  • Hi Gordon,

    I don't want to hijack a thread. I create a new one with your statement:

    "One other thing that could be an issue is that if you have Espruino powered from a computer, the computer connects to it via USB but stops reading data after a few characters have been sent. This means that if you're using print/console.log then after a while Espruino will stop working as it's waiting for the computer to read the data it's printing. If you either run a terminal app, or connect Espruino to a USB power supply, it'll be fine though."

    Is this proven ? If yes that's very vey important to know and should be included in the documentation of console.log.

    Is this also true in general for all uarts? Lets say a serial device (LCD or transmission module) crashes or disconnects. Is it then a question of time that espruino crashes too, because of buffering and waiting?

    I do not know of such a behavior on the arduino side.

    For me it looks like a trap that should be considered as a bug.

    Sacha

About

Avatar for Sacha @Sacha started