NodeMCU ESP32S - Will it work?

I tried to replicate the Getting Started with ESP32 project.
The project compiles and the firmware can be uploaded to the device. From there it wouldn’t work.
I also removed all except the “Interval” and the “GPIO” to see if the LED would blink which also isn’t the case. Any hint?
Below is the log I get when booting the ESP32 after programming with the example project (sorry can’t upload as a new user):

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:6760
load:0x40078000,len:12072
load:0x40080400,len:6708
entry 0x40080778
e[0;32mI (71) boot: Chip Revision: 1e[0m
e[0;32mI (71) boot_comm: chip revision: 1, min. bootloader chip revision: 0e[0m
e[0;32mI (39) boot: ESP-IDF  2nd stage bootloadere[0m
e[0;32mI (39) boot: compile time 10:35:21e[0m
e[0;32mI (39) boot: Enabling RNG early entropy source...e[0m
e[0;32mI (43) boot: SPI Speed      : 40MHze[0m
e[0;32mI (47) boot: SPI Mode       : DIOe[0m
e[0;32mI (51) boot: SPI Flash Size : 4MBe[0m
e[0;32mI (55) boot: Partition Table:e[0m
e[0;32mI (59) boot: ## Label            Usage          Type ST Offset   Lengthe[0m
e[0;32mI (66) boot:  0 nvs              WiFi data        01 02 00009000 00040000e[0m
e[0;32mI (74) boot:  1 otadata          OTA data         01 00 00049000 00002000e[0m
e[0;32mI (81) boot:  2 ota_0            OTA app          00 10 00050000 00177000e[0m
e[0;32mI (88) boot:  3 atmosphere       Unknown data     01 40 001c7000 001c2000e[0m
e[0;32mI (96) boot: End of partition tablee[0m
e[0;31mE (100) boot: ota data partition invalid and no factory, will try all partitionse[0m
e[0;32mI (108) boot_comm: chip revision: 1, min. application chip revision: 0e[0m
e[0;32mI (115) esp_image: segment 0: paddr=0x00050020 vaddr=0x3f400020 size=0x3ea1c (256540) mape[0m
e[0;32mI (214) esp_image: segment 1: paddr=0x0008ea44 vaddr=0x3ffbdb60 size=0x015cc (  5580) loade[0m
e[0;32mI (217) esp_image: segment 2: paddr=0x00090018 vaddr=0x400d0018 size=0xf4168 (999784) mape[0m
e[0;32mI (572) esp_image: segment 3: paddr=0x00184188 vaddr=0x3ffbf12c size=0x024b0 (  9392) loade[0m
e[0;32mI (576) esp_image: segment 4: paddr=0x00186640 vaddr=0x40080000 size=0x00400 (  1024) loade[0m
e[0;32mI (579) esp_image: segment 5: paddr=0x00186a48 vaddr=0x40080400 size=0x1c3a4 (115620) loade[0m
e[0;32mI (652) boot: Loaded app from partition at offset 0x50000e[0m
e[0;32mI (652) boot: Disabling RNG early entropy source...e[0m
e[0;32mI (653) cpu_start: Pro cpu up.e[0m
e[0;32mI (656) cpu_start: Application information:e[0m
e[0;32mI (661) cpu_start: ELF file SHA256:  9bd0c7d9423c3279...e[0m
e[0;32mI (667) cpu_start: ESP-IDF:          e[0m
e[0;32mI (671) cpu_start: Starting app cpu, entry point is 0x40081300e[0m
e[0;32mI (0) cpu_start: App cpu up.e[0m
e[0;32mI (682) heap_init: Initializing. RAM available for dynamic allocation:e[0m
e[0;32mI (689) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAMe[0m
e[0;32mI (695) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAMe[0m
e[0;32mI (701) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAMe[0m
e[0;32mI (707) heap_init: At 3FFBDB5C len 00000004 (0 KiB): DRAMe[0m
e[0;32mI (713) heap_init: At 3FFD12D8 len 0000ED28 (59 KiB): DRAMe[0m
e[0;32mI (719) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAMe[0m
e[0;32mI (725) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAMe[0m
e[0;32mI (732) heap_init: At 4009C7A4 len 0000385C (14 KiB): IRAMe[0m
e[0;32mI (738) cpu_start: Pro cpu start user codee[0m
e[0;32mI (85) cpu_start: Starting scheduler on PRO CPU.e[0m
ハ[UART] Starting ESP32 UART event task[UART] Created UART RX Task for 2
[UART] Waiting for UART Data on 2
Stored Build UUID: c55e71e2-9436-4fd2-8617-8c7e5f3d043a
Current Build UUID: c55e71e2-9436-4fd2-8617-8c7e5f3d043a
Error opening file ota_complete
Uuid Match 1 Boot After OTA: 0
Not Wiping Flash
Initializing config opts
Saving project UUID
Saving build UUID
Saved build UUID project UUID
Device Registered: 0
e[0;32mI (608) ATMO ESP32 BLE: ATMO_ESP32_BLE_PeripheralInit: ATMO_ESP32_BLE_PeripheralInit 753
e[0m

e[0;32mI (608) BTDM_INIT: BT controller compile version [3cd70f2]e[0m

e[0;32mI (608) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSEe[0m

e[0;32mI (998) ATMO ESP32 BLE: event = 0x0 gatts_if = 0x3
e[0m

e[0;32mI (998) ATMO ESP32 BLE: ESP_GATTS_REG_EVT: _ATMO_ESP32_BLE_gatts_event_handler 503
e[0m

e[0;32mI (998) ATMO ESP32 BLE: esp_ble_gatts_create_service: config->gatts_if = 0x3
e[0m

e[0;32mI (998) ATMO ESP32 BLE: event = 0x7 gatts_if = 0x3
e[0m

e[0;32mI (998) ATMO ESP32 BLE: ESP_GATTS_CREATE_EVT: _ATMO_ESP32_BLE_gatts_event_handler 574
e[0m

e[0;32mI (998) ATMO ESP32 BLE: CREATE_SERVICE_EVT, status 0,  service_handle 0x1
e[0m

e[0;31mE (998) BT_GATT: Active Service Found e[0m

e[0;31mE (998) BT_GATT: Duplicate Service start - Service already startede[0m

e[0;32mI (998) ATMO ESP32 BLE: event = 0xC gatts_if = 0x3
e[0m

e[0;32mI (998) ATMO ESP32 BLE: ESP_GATTS_START_EVT: _ATMO_ESP32_BLE_gatts_event_handler 605
e[0m

e[0;32mI (998) ATMO ESP32 BLE: esp_ble_gatts_create_service: serviceEntry->handle = 0x1
e[0m

e[0;32mI (998) ATMO ESP32 BLE: esp_ble_gatts_add_char: serviceHandle = 0x1
e[0m

e[0;31mE (998) BT_BTC: btc_gatts_arg_deep_copy 8, invalid lengthe[0m

e[0;32mI (998) ATMO ESP32 BLE: event = 0x9 gatts_if = 0x3
e[0m

e[0;32mI (998) ATMO ESP32 BLE: ESP_GATTS_ADD_CHAR_EVT: _ATMO_ESP32_BLE_gatts_event_handler 589
e[0m

e[0;32mI (998) ATMO ESP32 BLE: ATMO_ESP32_BLE_GATTSAddCharacteristic: config->numberOfCharacteristicEntries = 0 (1064)
e[0m

e[0;32mI (1008) ATMO ESP32 BLE: ATMO_ESP32_BLE_GATTSAddCharacteristic: config->numberOfCharacteristicEntries = 1 (1070)
e[0m

e[0;32mI (1018) ATMO ESP32 BLE: ATMO_ESP32_BLE_GATTSAddCharacteristic: characteristicEntry->handle = 0x0
e[0m

MAC: A4:CF:12:45:AE:AC
Error opening file wifiCredentials
Starting SNTP...
e[0;31mE (1188) BT_BTC: btc_gatts_arg_deep_copy 8, invalid lengthe[0m

Setting device name: PAEAE
Setting service uuid ad29a0c3-22ea-40a2-8bde-c840e2fefc95
Starting advertising
Updating adv data
esp_ble_gap_start_advertisinge[0;31mE (1308) BT_BTC: btc_gatts_arg_deep_copy 8, invalid lengthe[0m

It does not appear the device was provisioned to Atmosphere IoT. It will not start transmitting data until you connect to the device using the mobile app or a web browser with the Atmosphere IoT Client agent running.

Good day Kieron,

it seems I’m not very lucky connecting devices. :grin: I now did the tutorial you published with a nRF52840 DK. I can program the device (like the ESP32) and I get this serial output from it:

Adding characteristic 2A05 (Handle 1) (Properties 12)
Adding service bfe433cf-6b5e-4368-abab-b0a59666a402 (Handle 2)
Adding characteristic bfe433cf-6b5f-4368-abab-b0a59666a402 (Handle 3) (Properties 1A)
Adding characteristic 2A05 (Handle 1) (Properties 12)
Adding service bfe433cf-6b5e-4368-abab-b0a59666a402 (Handle 2)
Adding characteristic bfe433cf-6b5f-4368-abab-b0a59666a402 (Handle 3) (Properties 1A)
Adding service 9233ce51-0fc0-496a-8a9e-eb32bc5d451d (Handle 4)
Adding characteristic 9233ce51-0fc0-496a-8a9e-eb32bc5d451e (Handle 5) (Properties 0A)
Adding service 9233ce51-0fc0-496a-8a9e-eb32bc5d451d (Handle 4)
Adding characteristic 9233ce51-0fc0-496a-8a9e-eb32bc5d451f (Handle 6) (Properties 0A)
BLE Connected...

Now, I can see the app screen on my mobile showing Temperature:0.00 and Pressure: 0.00.
That’s it. On the ESP32 with the other tutorial I also saw the zeroes output.

So I must be missing something. For both devices I received an email saying they are registered:

New Device Added
Device [Gunter's nRF52840-DK project] has been successfully added to your account.
Device [ESP32 Blink Project] has been successfully added to your account.

Any further ideas?

Any hint please? I guess it must be me. The NXP Rapid IoT Tutorial worked fine.