My esp32 get hot when just plugged into usb

zawijaski
Posts: 1
Joined: Sat Jul 29, 2017 6:23 pm

My esp32 get hot when just plugged into usb

Postby zawijaski » Sat Jul 29, 2017 6:27 pm

Hello, i ve been running my ESP 32 Thing, with the code to manipulate 1 servo over wifi script in python.
Everything was working perfectly for some time (hours). Today I discovered there is no wifi connection (esp was a router) and its gettting painfully hot (to my finger at one second)!

I tried to flash it again with the same code (make flash monitor) and i get this: :(
(those signs keeps repeating randomly and esp is about to melt ... almost)
https://www.dropbox.com/s/v45v6ngi7dw7dm0/Screen%20Shot%202017-07-29%20at%2020.13.45.png?dl=0

what is wrong?

ESP_Sprite
Posts: 1182
Joined: Thu Nov 26, 2015 4:08 am

Re: My esp32 get hot when just plugged into usb

Postby ESP_Sprite » Mon Jul 31, 2017 6:39 am

Hard to say, but there may be something that killed(part of) the ESP32... do you run your servos from the same power supply as you run the ESP32? If so, do you have any decoupling in place?

f.h-f.s.
Posts: 178
Joined: Thu Dec 08, 2016 2:53 pm

Re: My esp32 get hot when just plugged into usb

Postby f.h-f.s. » Mon Jul 31, 2017 7:30 pm

The esp32 thing from sparkfun gets really hot.
I fried mine. The ones with a EMI shield are a little less hot.

razvan_mihai
Posts: 3
Joined: Wed Aug 02, 2017 9:24 pm

Re: My esp32 get hot when just plugged into usb

Postby razvan_mihai » Wed Aug 02, 2017 9:44 pm

zawijaski wrote:Hello, i ve been running my ESP 32 Thing, with the code to manipulate 1 servo over wifi script in python.
Everything was working perfectly for some time (hours). Today I discovered there is no wifi connection (esp was a router) and its gettting painfully hot (to my finger at one second)!

I tried to flash it again with the same code (make flash monitor) and i get this: :(
(those signs keeps repeating randomly and esp is about to melt ... almost)
https://www.dropbox.com/s/v45v6ngi7dw7dm0/Screen%20Shot%202017-07-29%20at%2020.13.45.png?dl=0

what is wrong?


Today I got the same problem after a period of normal run. I don't have large current loads connect. Only some ambiental (temperature, humidity, pressure ) sensors.
I belive I need to erase the entire flash and reprogram it...hope it will work.

razvan_mihai
Posts: 3
Joined: Wed Aug 02, 2017 9:24 pm

Re: My esp32 get hot when just plugged into usb

Postby razvan_mihai » Thu Aug 03, 2017 4:08 pm

I run out of ideas in order to make my wifi working.
Here I am trying to connect to an open network using the provided http_example code. I have inserted some "printfs" to see if it goes to the entire code.
I must admit this situation is beyond my current knowledge....

Code: Select all

Leaving...
Hard resetting...
MONITOR
--- idf_monitor on COM5 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
et�����������LS�����:*2*���iA�eAQ���ER�������������A�emAQ���_F���������%�u�UjR�et�������
����LS�����:*6(���ia�eaAQ�T����������Q�U�I��K�A�emAQ���_����������%�u�UjR���������t ����
���������C�,k�E��ia�aaY��d��������������������.�E��iA�aaY��_d���������E��iA�aa���e�������
���-$V��I5      ����:������������YK�j����ia�e��f�����������L��        ����AeaA��o��������
��������������ieeamelo���������������YK���*"�����Aa�ia`8������I (30) boot: ESP-IDF v2.0-rc
1-1089-g3bd3640d 2nd stage bootloader
I (31) boot: compile time 18:44:18
I (58) boot: Enabling RNG early entropy source...
I (58) boot: SPI Speed      : 40MHz
I (60) boot: SPI Mode       : DIO
I (73) boot: SPI Flash Size : 4MB
I (85) boot: Partition Table:
I (96) boot: ## Label            Usage          Type ST Offset   Length
I (119) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (142) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (165) boot:  2 factory          factory app      00 00 00010000 00100000
I (188) boot: End of partition table
I (201) boot: Disabling RNG early entropy source...
I (218) boot: Loading app partition at offset 00010000
I (920) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (921) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x09d08 ( 40200) map
I (937) boot: segment 2: paddr=0x00029d18 vaddr=0x3ffb0000 size=0x02b0c ( 11020) load
I (968) boot: segment 3: paddr=0x0002c82c vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _iram_start at ??:?

I (990) boot: segment 4: paddr=0x0002cc34 vaddr=0x40080400 size=0x12e00 ( 77312) load
I (1052) boot: segment 5: paddr=0x0003fa3c vaddr=0x400c0000 size=0x00000 (     0) load
I (1053) boot: segment 6: paddr=0x0003fa44 vaddr=0x00000000 size=0x005c4 (  1476)
I (1074) boot: segment 7: paddr=0x00040010 vaddr=0x400d0018 size=0x476f4 (292596) map
0x400d0018: _flash_cache_start at ??:?

I (1100) cpu_start: Pro cpu up.
I (1112) cpu_start: Starting app cpu, entry point is 0x40080e78
0x40080e78: call_start_cpu1 at C:/esp32/msys32/home/Admin/esp/esp-idf/components/esp32/cpu_s
tart.c:186

I (0) cpu_start: App cpu up.
I (1145) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1167) heap_alloc_caps: At 3FFAE2A0 len 00001D60 (7 KiB): DRAM
I (1188) heap_alloc_caps: At 3FFB7C20 len 000283E0 (160 KiB): DRAM
I (1209) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (1230) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (1252) heap_alloc_caps: At 40093200 len 0000CE00 (51 KiB): IRAM
I (1273) cpu_start: Pro cpu start user code
I (1330) cpu_start: Starting scheduler on PRO CPU.
I (202) cpu_start: Starting scheduler on APP CPU.
I (262) wifi: wifi firmware version: bf86460
I (262) wifi: config NVS flash: enabled
I (262) wifi: config nano formating: disabled
I (262) system_api: Base MAC address is not set, read default base MAC address from BLK0 of
EFUSE
I (272) system_api: Base MAC address is not set, read default base MAC address from BLK0 of
EFUSE
I (312) wifi: Init dynamic tx buffer num: 32
I (312) wifi: Init dynamic rx buffer num: 32
I (312) wifi: wifi driver task: 3ffbddf0, prio:23, stack:4096
I (312) wifi: Init static rx buffer num: 10
I (312) wifi: Init dynamic rx buffer num: 32
I (322) wifi: Init rx ampdu len mblock:7
I (322) wifi: Init lldesc rx ampdu entry mblock:4
I (322) wifi: wifi power manager task: 0x3ffc31b8 prio: 21 stack: 2560
I (332) example: Setting WiFi configuration SSID AndroidAP...
I (342) wifi: wifi timer task: 3ffc4238, prio:22, stack:3584
I (372) phy: phy_version: 355.1, 594���x<�x���x�x�x���������<����x�����I����
�b�b���j5RJB���J�����j���������B����
��������2�Jj����+�k+RH�U�V�k�k+RH�I (492) wifi: n:11 0, o:1 0, ap:255 255, sta:11 0, p
rof:1
I (1472) w�����x<��x����������x����<x�<�������
����B�Jj��I (2472) wifi: state: ������������~����������������
B����J�����r����bz����b
��������b�������b������j��I (2602) wif����������������� H���
�82}�����������b��������������������!|�
��������������4��������x���J������������
����B�Jj��I (3602) wifi: stat���������������| ����������������(
i�&�JHW-V-'HK���bz����b
��������b�������b������j��I (3722) wif?���������������� ����
@��������������������1���r�������I�����)
wifi: state: init ->�����������B������I (4722) wifi: stat����������
����|������B�Jj��
        ���&�JHW-V-'HK���bz����b
��������b�������b������j��ets Jun  8 2016 00:22:57

rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
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:4412
ho 0 tail 12 room 4
load:0x40078000,len:11072
load:0x40080000,len:252
0x40080000: _iram_start at ??:?

entry 0x40080034
0x40080034: _iram_start at ??:?

W (95) boot: PRO CPU has been reset by WDT.
W (95) boot: WDT reset info: PRO CPU PC=0x4008335a
0x4008335a: wDev_ProcessFiq at ??:?

W (96) boot: WDT reset info: APP CPU PC=0x400d15f8 (waiti mode)
0x400d15f8: esp_vApplicationIdleHook at C:/esp32/msys32/home/Admin/esp/esp-idf/components/es
p32/freertos_hooks.c:52

I (118) boot: ESP-IDF v2.0-rc1-1089-g3bd3640d 2nd stage bootloader
I (139) boot: compile time 18:44:18
I (179) boot: Enabling RNG early entropy source...
I (179) boot: SPI Speed      : 40MHz
I (182) boot: SPI Mode       : DIO
I (194) boot: SPI Flash Size : 4MB
I (207) boot: Partition Table:
I (218) boot: ## Label            Usage          Type ST Offset   Length
I (241) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (264) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (288) boot:  2 factory          factory app      00 00 00010000 00100000
I (311) boot: End of partition table
I (324) boot: Disabling RNG early entropy source...
I (341) boot: Loading app partition at offset 00010000
I (1042) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (1043) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x09d08 ( 40200) map
I (1059) boot: segment 2: paddr=0x00029d18 vaddr=0x3ffb0000 size=0x02b0c ( 11020) load
I (1090) boot: segment 3: paddr=0x0002c82c vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _iram_start at ??:?

I (1113) boot: segment 4: paddr=0x0002cc34 vaddr=0x40080400 size=0x12e00 ( 77312) load
I (1175) boot: segment 5: paddr=0x0003fa3c vaddr=0x400c0000 size=0x00000 (     0) load
I (1176) boot: segment 6: paddr=0x0003fa44 vaddr=0x00000000 size=0x005c4 (  1476)
I (1197) boot: segment 7: paddr=0x00040010 vaddr=0x400d0018 size=0x476f4 (292596) map
0x400d0018: _flash_cache_start at ??:?

I (1224) cpu_start: Pro cpu up.
I (1235) cpu_start: Starting app cpu, entry point is 0x40080e78
0x40080e78: call_start_cpu1 at C:/esp32/msys32/home/Admin/esp/esp-idf/components/esp32/cpu_s
tart.c:186

I (0) cpu_start: App cpu up.
I (1268) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1290) heap_alloc_caps: At 3FFAE2A0 len 00001D60 (7 KiB): DRAM
I (1311) heap_alloc_caps: At 3FFB7C20 len 000283E0 (160 KiB): DRAM
I (1332) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (1353) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (1375) heap_alloc_caps: At 40093200 len 0000CE00 (51 KiB): IRAM
I (1396) cpu_start: Pro cpu start user code


The module I am using is an ESP32 thing (sparkfun). It worked 3 days ago.
I put the oscilloscope and the 3.23 V are stable. So the current is enough (as expected, because it worked).
I verified to not have short circuit. I did a "make erase_flash" and " make flash monitor" cycle.
This is very annoying....
Should it be something related to OTA or something related to the esp internal circuitry stopped to work correct?
It is very odd because blinking an led works fine.

In addition I attached an image with the arduino serial monitor message after I run another wifi program that worked perfectly until now...

Does anybody faced this behavior?

Thank you!
Attachments
WIFI_pb.png
WIFI_pb.png (22.21 KiB) Viewed 686 times

sukeshak
Posts: 32
Joined: Sat Aug 19, 2017 10:20 am

Re: My esp32 get hot when just plugged into usb

Postby sukeshak » Fri Sep 22, 2017 9:33 am

I have noticed if WiFi credentials have problem and the program runs continuously trying to connect Wi-Fi and fail, my module also gets hot.

Check to see if this is the case.

Who is online

Users browsing this forum: Yahoo [Bot] and 3 guests