[Solved] ESP-WROOM-32 boots but does not respond to commands

[Miek770]

<r>Hi,<br/>
<br/>
I followed this thread (<URL url="viewtopic.php?t=3417"><LINK_TEXT text="viewtopic.php?t=3417">viewtopic.php?t=3417</LINK_TEXT></URL>) and this blog post (<URL url="https://www.cnx-software.com/2017/10/16 ... <LINK_TEXT text="https://www.cnx-software.com/2017/10/16 ... tutorials/">https://www.cnx-software.com/2017/10/16 ... TEXT></URL>) to flash the latest MicroPython image to my ESP-WROOM-32 (on a hackerbox ESP32_Core_board_V2). It looked like everything went fine. There were no error messages and after a hard reset I get (on minicom):<br/>
<br/>
ets Jun 8 2016 00:22:57<br/>
<br/>
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)<br/>
ets Jun 8 2016 00:22:57<br/>
<br/>
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)<br/>
configsip: 0, SPIWP:0xee<br/>
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00<br/>
mode:DIO, clock div:2<br/>
load:0x3fff0018,len:4<br/>
load:0x3fff001c,len:4436<br/>
load:0x40078000,len:0<br/>
load:0x40078000,len:11816<br/>
entry 0x4007a9fc<br/>
I (213) cpu_start: Pro cpu up.<br/>
I (213) cpu_start: Single core mode<br/>
I (213) heap_init: Initializing. RAM available for dynamic allocation:<br/>
I (217) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM<br/>
I (223) heap_init: At 3FFC4E78 len 0001B188 (108 KiB): DRAM<br/>
I (229) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM<br/>
I (236) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM<br/>
I (242) heap_init: At 4008DE34 len 000121CC (72 KiB): IRAM<br/>
I (248) cpu_start: Pro cpu start user code<br/>
I (42) cpu_start: Starting scheduler on PRO CPU.<br/>
OSError: [Errno 2] ENOENT<br/>
MicroPython v1.9.3-397-g0acf868b on 2018-03-04; ESP32 module with ESP32<br/>
Type "help()" for more information.<br/>
>>> <br/>
<br/>
I read in another thread that the OSError was cause by the absence of main.py. It doesn't, however, respond to my inputs. If I type "help()" + ENTER it doesn't do anything (doesn't matter what I type).<br/>
<br/>
The serial port configuration appears to be fine; I can read the boot messages from the ESP and I tried checking all minicom options (ex.: add carriage return). Didn't help. I read about bad solders causing problems for these boards but I find it curious that it would've been able to flash correctly with a bad connection. I am missing something? Should I still try to measure every voltage on the board to look for errors?<br/>
<br/>
Thank you!</r>

[Miek770]

Hum there seems to be a bug with the forum's draft feature, I didn't add those <br/> manually in the original post..

Still, I wanted to share that I solved this simply by using screen instead of minicom. I tried other things but that's what made a difference. I now looks like an awesome little board ready to do some mischief!

[pythoncoder]

You might like to try Dave Hylands' rshell.

[Miek770]

Thanks, I'll give it a try. I used vim custom commands to upload files but rshell seems nice.