Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Abhijeet Bhatikar
    @abhatikar
    I am using arduino ide to program the Esp32
    jumjum123
    @jumjum123
    AFAIK there is no way to recognize the board. Only difference I know is to check heap with ESP32.getState() if freeheap is more than 1MB, the board has WROVER chip or similiar. In that case you should not use GPIO16/17
    sdellava
    @sdellava
    tnx!
    BeeMotors
    @BeeMotors
    Hello, friends! I need your help. I cannot connect sd card reader to NodeMCU (Espruino2.0). The library "fs" referenced by the textbooks is not on the site and not on github. Can you please tell me how to connect the module?
    seeya
    @seeya

    Hi, I'm using a ESP32-WROOM DOIT board and managed to flash Espruino 2v00.133 on it. I'm trying to test my serial connection.
    The GPIO pinouts is exactly like this image here (https://i1.wp.com/randomnerdtutorials.com/wp-content/uploads/2018/08/ESP32-DOIT-DEVKIT-V1-Board-Pinout-36-GPIOs-updated.jpg?ssl=1).

    I am using GPIO17(TX) and GPIO16(RX) to connect to my serial device (Reyax RYL896). So my connection is as follows:
    GPIO17(TX) -> (RX)
    GPIO16(RX) -> (TX)

    Then I tried running a serial loop-back to test if it works but I'm not getting anything.

    Serial1.setup(115200, {rx:D16, tx:D17});
    Serial1.on('data', function (data) { print("<Serial> "+data); });
    Serial1.print("Hello World");

    My question is am I intializing the Serial1.setup(115200, {rx:D16, tx:D17}); pins wrongly? How do I know which pin number rx and tx should use?

    seeya
    @seeya
    Has anyone manage to hook up serial devices on the esp32? I read that Serial1 and Serial2 are unavailable as one is for console and the other for SDIO flash chip. So my only option left is Serial3 which are pin D16 and D17. But I can’t seem to be able to establish a correct connection.

    I tried the codes and got back some weird response like this.

    >["AT\r\n"
    ] "\xFF\xFF\xFC\xE8"
    undefined
    Timeout

    The code that gave this output.

    var s = Serial3;
    s.setup(115200,{rx:D16, tx:D17});
    var at = require("AT").connect(s);  
    at.debug();
    at.cmd("AT\r\n", 1000, function(d) {
      if (d===undefined) {
        console.log(d);
         console.log("Timeout"); 
      }
      else {
        console.log(d);
      }
    });
    seeya
    @seeya
    I tried a loop back test by connecting pin 16 and 17 together and it works. But when I connect my serial device, the command sent became in hex like the one above
    Ernst Naezer
    @ernstnaezer
    Hi folks - initially posted this in the main channel but this might be a better place... I'm trying to get some TypeScript transpired to my ESP32 and I'm wondering how best to go about declaring a Pin. I noticed that both nodemcu and nucleo have a range of pins declared in a jswrap construct so you can reference to them directly through the namespace. This is missing for the ESP32 target and the TypeScript type definition only contains Pin as an interface.
    Ernst Naezer
    @ernstnaezer
    this seems to work declare var Pin: Pin;
    new Pin(25) now transpiles
    László Szirmai
    @lacmuch
    @seeya I'm in the same situation: the baud rate can not be changed. Its statically 4800 baud...
    Ákos Lukács
    @AkosLukacs
    Hi!, a question about EPS32 + I2C: If I do I2C1.setup({sda: D21, scl: D22});, I get the following warning in the console:
    (that's supposed to be the hardware I2C port of the ESP32, right?)
    jshI2CSetup: driver installed,sda: 21, dsl: 22, freq: 100000
    It does work, but why the warning?
    Rob Blanckaert
    @basicer
    its not even a warning
    just a thing it likes to print
    Ákos Lukács
    @AkosLukacs
    Hi, does the ESP32 support software serial? My code is runnign fine on Serial2 receiving on D16 (I only use rx)
    But does nothing with sw serial
    Even on the same pin. Or is there a restriction?
    @wildanimal
    Hi, I write the newest version firmware into esp32 wroom-32 board, but running error
    my write flash command is esptool.py --chip esp32 --port COM10 --baud 921600 --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0x1000 bootloader.bin 0x8000 partitions_espruino.bin 0x10000 espruino_esp32.bin
    Ákos Lukács
    @AkosLukacs
    Hi, what's the error? Did you try lower speed?
    @wildanimal
    i using another one esp32 board,the new type board is totally compatible, the old type board is not compatible。
    Mika
    @mhelander
    This might be stupid question, but has anybody created IoT setup using Espruino on Sonoff hardware? I'm looking forward custom setup to run GunDB (https://gun.eco/docs/Introduction) and possibly skipping altogether all MQTT and related broker issues...
    Target is to build truly P2P system, at least in local WLAN proximity including (computer) browsers and mobile devices.
    nardev
    @nardev
    hi guys, does the touch sensor work under soldermask?
    and, is it possible to make matrix keypad with 4x4 touch pins?
    Spence Konde (aka Dr. Azzy)
    @SpenceKonde
    capacitive touch sensors do work through solder mask
    I don't think you can matrix them, but check the datasheet for the touch controller.
    There exist 16-channel touch sensor ICs
    Ron B
    @RONTheCookie
    Hey, I'm installing espruino on my esp32 dev board and I just wanted to know if reinstalling the factory firmware, etc is documented and where
    Ron B
    @RONTheCookie
    ok, finished installing and im getting something weird, probably a boot loop as it constantly repeats:
    Brownout detector was triggered
    
    ets Jun  8 2016 00:22:57
    
    rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
    configsip: 0, SPIWP:0xee
    clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
    mode:DIO, clock div:2
    load:0x3fff0018,len:4
    load:0x3fff001c,len:2668
    load:0x40078000,len:7304
    load:0x40080000,len:5312
    entry 0x40080274
    E (536) spiram: SPI RAM enabled but initialization failed. Bailing out.
    Ron B
    @RONTheCookie
    Ok, turns out I just didn't have enough power for it to boot, now I have two power supplies connected to the esp
    iammikecohen
    @iammikecohen
    image.png
    Can anyone explain why my board keeps ending up in the broken state?
    I keep erasing the memory and reflashing espruino 2v03
    but not long after I get back in this state where the saved code runs but I can't communicate to modify the onInit function
    Ákos Lukács
    @AkosLukacs
    Just saw this on twitter https://m.aliexpress.com/item/33048962331.html ttgo esp32 with display thingy for ~1 usd
    Ákos Lukács
    @AkosLukacs
    @iammikecohen dunno, do you
    (argh, on mobile...)
    So, what do you have in your oninit? Maybe something long running, or something interferes with serial line?
    Kirill Ivanov
    @ApocalypseLinyx
    Hi. I gave a problem with DHT22 and low memory. http://forum.espruino.com/conversations/337313/ this post. Can anyone help?
    renegadeandy
    @renegadeandy

    Hi all. I am trying to flash an esp32-wroom (not on a dev board, am using this https://www.mouser.co.uk/ProductDetail/356-ESP-WROOM-32). I am finding that before I flash on a serial monitor I see:

    Jun  8 2016 00:22:57
    
    rst:0x1 (POWERON_RESET),boot:0x23 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
    waiting for download

    But when I try to flash I get:

    esptool.py v2.6
    Serial port COM3
    Connecting........_____....._____....._____....._____....._____....._____....._____
    
    A fatal error occurred: Failed to connect to ESP32: Invalid head of packet (0x00)
    A fatal error occurred: Failed to connect to ESP32: Invalid head of packet (0x00)

    Any ideas what might cause that?

    renegadeandy
    @renegadeandy
    If i keep the ground of the ft232 programmer joined to the ground of the ESP, i get a different error:
    esptool.py v2.6
    Serial port COM3
    Connecting.....
    Chip is ESP32D0WDQ6 (revision 1)
    Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
    MAC: cc:50:e3:be:c4:d4
    Uploading stub...
    Running stub...
    Stub running...
    Configuring flash size...
    Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
    Compressed 8192 bytes to 47...
    
    A fatal error occurred: Timed out waiting for packet content
    A fatal error occurred: Timed out waiting for packet content
    Green Protocol
    @green_protocol_twitter
    The first error is the COM3 port can't communicate with the ESP32
    I've seen this problem with my ESP32s
    The second issue seems to be a com problem too
    it connects then s loses connection "waiting for packet content"
    @HyGy I think your baudrate on your port is not set to the same speed as the ESP32