Avatar for CrashingDutchman


Member since Apr 2015 • Last active Mar 2020
  • 9 conversations

Gadget freak

Most recent activity

  • in Porting to new Devices
    Avatar for CrashingDutchman

    Did you ever get around this?

    I am looking at the PineTime that is also equiped with a nRF52832

  • in Projects
    Avatar for CrashingDutchman

    A story on Hackaday with regard to flashing Arduino on watches: https://hackaday.com/2019/08/23/ota-flas­h-tool-makes-fitness-tracker-hacking-mor­e-accessible/

  • in ESP8266
    Avatar for CrashingDutchman

    You are probably correct about that... although, it can give some satisfaction if you solve an issue like this.

    Thanks again!

  • in ESP8266
    Avatar for CrashingDutchman

    Oh, @Gordon do you happen to know which capacitor I should look at?

  • in ESP8266
    Avatar for CrashingDutchman

    Baudrate is set to 115200. I always do a power cycle after flashing, so that should qualify as a reset, correct?

    Tonight I will try to power it from an external supply and see if I can connect.

    Thank you for the hints @Gordon

  • in ESP8266
    Avatar for CrashingDutchman

    I am having a similar problem with a NodeMCU. I tried the line in (post 8) that helped the topic starter, but to no avail.

    1. Flashing seems to go fine (see bottom of this post)
    2. I can sometimes access the Espruino prompt in Putty (1 out of 3 or 4 tries)
    3. I never see a prompt in Espruino

    When I click the connect button in Espruino and choose the COM port, then I see the following in the IDE:

    • an orange box with text "Disconnected"
    • a line with some garbage text "0 űÁ"
    • a red box with text "Unable to retrieve board information. Connection error?"
    • a green box with text "Connected to CO4 (no response from board)"

    Here is my line that I use for flashing:

    esptool.py.exe --port COM4 --baud 115200 write_flash --flash_size=detect -fm dio 0 .\espruino_1v99_esp8266_4mb_combined_409­6.bin

    And here are the flash results:

    esptool.py v2.5.1
    Serial port COM4
    Detecting chip type... ESP8266
    Chip is ESP8266EX
    Features: WiFi
    MAC: 18:fe:34:e1:a4:16
    Uploading stub...
    Running stub...
    Stub running...
    Configuring flash size...
    Auto-detected Flash size: 4MB
    Flash params set to 0x0240
    Compressed 4194304 bytes to 353773...
    Wrote 4194304 bytes (353773 compressed) at 0x00000000 in 31.7 seconds (effective 1058.0 kbit/s)...
    Hash of data verified.
    Hard resetting via RTS pin...

    I can upload any Arduino sketch that I have to this module (NodeMCU from Amica), and they all work as expected. So, I think the module is fine. I don't have any others to try right now.

    Any help is appreciated

  • in ESP32
    Avatar for CrashingDutchman

    When I get this error in the IDE, connecting with Putty results in an: Putty Fatal Error: Error reading from serial device.

    In the putty dialog I see this:
    ets Jun 8 2016 00:22:57
    rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    configsip: 0, SPIWP:0xee
    mode:DIO, clock div:2
    entry 0x40078c4c

  • in ESP32
    Avatar for CrashingDutchman

    I tested the following:

    1. Start Espruino IDE
    2. Connect ESP32
    3. Connect to COM port (which worked)
    4. Close the IDE
    5. Start the IDE
    6. Connect to COM port (I get the "Connected to COM7 (No response from board)" message)
  • in ESP32
    Avatar for CrashingDutchman

    I am not yet sure how long a while is. I connected the ESP32 probably on Thursday and left the IDE open, computer was powered on at all times. When I wanted to connect the IDE to the port yesterday (Tuesday) evening (around 8 pm) I got the messages.

    I disconnected and reconnected the device yesterday and was able to connect through the IDE. This morning I found that my computer had rebooted. I tried to connect again from the IDE and saw the same messages. It seems that only a power cycle of the ESP32 allows me to connect successfully.

    I will keep an eye on this and report back when I have more information.

    Thank you @Wilberforce