ESP32-WROVER-V4 won't recieve commands over uart

Geocheats2
Posts: 3
Joined: Fri May 04, 2018 8:10 pm

ESP32-WROVER-V4 won't recieve commands over uart

Postby Geocheats2 » Fri May 04, 2018 8:41 pm

I am pretty sure i have burned somthing but i would like a second opinion, if you can point me at anywhere i would be gratefull

Here is a photo of my setup

Image

The arduino on the left is one of those cheap ones with the CH340 instead of the FTDI chip but it seems like it is working.

When i bridge TX+RX i get my message sent back as a responce so the TX + RX should be working, at least until the arduino

The RX part of the arduino and the TX part of the ESP32 are working nicely

With EN high

Code: Select all

clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:3472
load:0x40078000,len:7804
load:0x40080000,len:252
entry 0x40080034
[0;32mI (43) boot: ESP-IDF v2.0 2nd stage bootloader[0m
[0;32mI (43) boot: compile time 03:23:43[0m
[0;32mI (49) boot: Enabling RNG early entropy source...[0m
[0;32mI (59) boot: SPI Speed      : 40MHz[0m
[0;32mI (72) boot: SPI Mode       : DIO[0m
[0;32mI (84) boot: SPI Flash Size : 4MB[0m
[0;32mI (97) boot: Partition Table:[0m
[0;32mI (108) boot: ## Label            Usage          Type ST Offset   Length[0m
[0;32mI (130) boot:  0 phy_init         RF data          01 01 0000f000 00001000[0m
[0;32mI (154) boot:  1 otadata          OTA data         01 00 00010000 00002000[0m
[0;32mI (177) boot:  2 nvs              WiFi data        01 02 00012000 0000e000[0m
[0;32mI (200) boot:  3 at_customize     unknown          40 00 00020000 000e0000[0m
[0;32mI (223) boot:  4 ota_0            OTA app          00 10 00100000 00180000[0m
[0;32mI (247) boot:  5 ota_1            OTA app          00 11 00280000 00180000[0m
[0;32mI (270) boot: End of partition table[0m
[0;32mI (283) boot: Disabling RNG early entropy source...[0m
[0;32mI (300) boot: Loading app partition at offset 00100000[0m
[0;32mI (1475) boot: segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512) [0m
[0;32mI (1476) boot: segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5d0 (116176) map[0m
[0;32mI (1493) boot: segment 2: paddr=0x0012c5e0 vaddr=0x3ffb0000 size=0x0215c (  8540) load[0m
[0;32mI (1523) boot: segment 3: paddr=0x0012e744 vaddr=0x40080000 size=0x00400 (  1024) load[0m
[0;32mI (1546) boot: segment 4: paddr=0x0012eb4c vaddr=0x40080400 size=0x1b028 (110632) load[0m
[0;32mI (1625) boot: segment 5: paddr=0x00149b7c vaddr=0x400c0000 size=0x00034 (    52) load[0m
[0;32mI (1626) boot: segment 6: paddr=0x00149bb8 vaddr=0x00000000 size=0x06450 ( 25680) [0m
[0;32mI (1642) boot: segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a544 (501060) map[0m
[0;32mI (1670) heap_alloc_caps: Initializing. RAM available for dynamic allocation:[0m
[0;32mI (1692) heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM[0m
[0;32mI (1713) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM[0m
[0;32mI (1735) heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM[0m
[0;32mI (1756) cpu_start: Pro cpu up.[0m
[0;32mI (1767) cpu_start: Single core mode[0m
[0;32mI (1780) cpu_start: Pro cpu start user code[0m
[0;32mI (1841) cpu_start: Starting scheduler on PRO CPU.[0m
[0;32mI (2045) uart: queue free spaces: 10[0m
I (2046) wifi: wifi firmware version: c604573
I (2047) wifi: config NVS flash: enabled
I (2047) wifi: config nano formating: disabled
I (2056) wifi: Init dynamic tx buffer num: 32
I (2057) wifi: wifi driver task: 3ffc4e2c, prio:23, stack:3584
I (2060) wifi: Init static rx buffer num: 10
I (2064) wifi: Init dynamic rx buffer num: 0
I (2068) wifi: Init rx ampdu len mblock:7
I (2072) wifi: Init lldesc rx ampdu entry mblock:4
I (2076) wifi: wifi power manager task: 0x3ffca1d4 prio: 21 stack: 2560
I (2083) wifi: wifi timer task: 3ffcb254, prio:22, stack:3584
[0;31mE (2088) phy_init: PHY data partition validated[0m
[0;32mI (2109) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0[0m
I (2109) wifi: mode : softAP (24:0a:c4:12:bf:ad)
I (2112) wifi: mode : sta (24:0a:c4:12:bf:ac) + softAP (24:0a:c4:12:bf:ad)
I (2116) wifi: mode : softAP (24:0a:c4:12:bf:ad)
With EN floating

Code: Select all

rst:0x1 (POWERON_RESET),boot:0x33 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x⸮ets Jun  8 2016 00:22:57
With EN high and IO0 low
rst:0x1 (POWERON_RESET),boot:0x23 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download
The TX goes from the arduino to 150 Ohm resistor to a 300 Ohm resistor with the cable in the middle going to the RX of the ESP32 as a voltage divider (the resistors in the photo do not have the correct value but i have replaced them since)

**keep in mind that when i send a command from terminal the green light of the TX on the arduino lights up.

Looking forward to your advice

Geocheats2
Posts: 3
Joined: Fri May 04, 2018 8:10 pm

Re: ESP32-WROVER-V4 won't recieve commands over uart

Postby Geocheats2 » Mon May 14, 2018 4:09 pm

I just received a proper CP2102 USB to UART but I still have the same problem ESP32 won't even reply to the AT command :(

WiFive
Posts: 3529
Joined: Tue Dec 01, 2015 7:35 am

Re: ESP32-WROVER-V4 won't recieve commands over uart

Postby WiFive » Mon May 14, 2018 10:51 pm

At command by default is on uart1 but debug you show is on uart0

Who is online

Users browsing this forum: No registered users and 150 guests