Eclipse build of main_helloworld.cpp

[javaben]

I've been working through Kolban's videl (https://www.youtube.com/watch?v=-ttiPfm ... poUUE7QMOo) and everything appears to work OK, but I'm getting this strange output at make flash monitor:

This is the end of the make flash, then it just sits there waiting. If I hit anything on the keyboard, it appears that it is being forwarded to the ESP32 device. Ultimately, I do Ctrl+] to exit. I've tried it with several devices, and all have the same problem. I also tested to the device using Arduino IDE, and it works properly.


===============================make monitor output
esptool.py v2.3.1
Flashing binaries to serial port /dev/ttyUSB0 (app at offset 0x10000)...
esptool.py v2.3.1
Connecting.....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0220
Compressed 17856 bytes to 10678...
Wrote 17856 bytes (10678 compressed) at 0x00001000 in 0.9 seconds (effective 151.0 kbit/s)...
Hash of data verified.
Compressed 144208 bytes to 70524...
Wrote 144208 bytes (70524 compressed) at 0x00010000 in 6.2 seconds (effective 185.6 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.0 seconds (effective 1866.5 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
MONITOR
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_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:4572
load:0x40078000,len:0
load:0x40078000,len:13184
entry 0x40078d38
I (86) cpu_start: Pro cpu up.
I (87) cpu_start: Single core mode
I (87) heap_init: Initializing. RAM available for dynamic allocation:
I (90) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (96) heap_init: At 3FFB1E78 len 0002E188 (184 KiB): DRAM
I (102) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (109) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (115) heap_init: At 40088040 len 00017FC0 (95 KiB): IRAM
I (121) cpu_start: Pro cpu start user code
I (139) cpu_start: Starting scheduler on PRO CPU.

[kolban]

What does your application do? What should we expect to see on the output? If you are using ESP_LOG macros, then by default, the logging level is set to warning. If you are logging at DEBUG or VERBOSE, you would want to switch the flags to log at lower levels. It may be that the app is working perfectly and you haven't enabled enough log info for it to appear.

[javaben]

Well, until you poked me ("wake up, what's the code doing?"), I had just assumed it was doing a 'cout'. That, of course, would be wrong. I guess I took the video too literally where it says the debug level is just a personal preference, and had it running at a higher level.

Changing the log level to debug appears to work.

Being new to C++, Eclipse, and ESP32, guess I was just unexperienced and confused.

Thanks for the 'poke!'.

Poked awake by a Texan with an accent....sheesh.

At least my BBQ is better than yours.

JavaBen