UFO failed

[sygrosjean]

I have my UFO freeze : only one white light is switch on (see in attached file)

I tried to reset but it doesn’t work and wifi isn’t accessible.

Can you help me ?

[helmut-s]

Is there any reaction if you press the button? (guess not)
What happened before the freeze. Did you update/program the UFO?

[sygrosjean]

Hello Helmut,
no reaction when i press button
and before the freeze nothing like update/upgrade
UFO was associated with dynatrace.

[helmut-s]

This means it showed some colors and suddenly it just showed the white dot, correct? So if a reset (unplug) doesn't solve the problem it looks like the processor is not starting up at all.
You could try to re-flash it (see #26 for instructions) but I am afraid that something might be broken...

[sygrosjean]

On terminal i saw reboot continually
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_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:4288
load:0x40078000,len:10216
load:0x40080000,len:252
entry 0x40080034
I (45) boot: ESP-IDF v2.0-rc1-935-ge7db29b2-dirty 2nd stage bootloader
I (46) boot: compile time 10:28:46
I (49) boot: Enabling RNG early entropy source...
I (65) boot: SPI Speed : 40MHz
I (78) boot: SPI Mode : DIO
I (90) boot: SPI Flash Size : 4MB
I (103) boot: Partition Table:
I (114) boot: ## Label Usage Type ST Offset Length
I (137) boot: 0 nvs WiFi data 01 02 00009000 00005000
I (160) boot: 1 otadata OTA data 01 00 0000e000 00002000
I (183) boot: 2 ota_0 OTA app 00 10 00010000 00190000
I (206) boot: 3 ota_1 OTA app 00 11 001a0000 00190000
I (230) boot: 4 data Unknown data 01 81 00330000 000c0000
I (253) boot: 5 coredump Unknown data 01 03 003f0000 00010000
I (276) boot: End of partition table
I (289) boot: Disabling RNG early entropy source...
I (306) boot: Loading app partition at offset 00010000
I (1651) boot: segment 0: paddr=0x00010018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (1651) boot: segment 1: paddr=0x00020008 vaddr=0x3f400010 size=0x2b6bc (177852) map
I (1668) boot: segment 2: paddr=0x0004b6cc vaddr=0x3ffb0000 size=0x02bd4 ( 11220) load
I (1699) boot: segment 3: paddr=0x0004e2a8 vaddr=0x40080000 size=0x00400 ( 1024) load
I (1721) boot: segment 4: paddr=0x0004e6b0 vaddr=0x40080400 size=0x12528 ( 75048) load
I (1783) boot: segment 5: paddr=0x00060be0 vaddr=0x400c0000 size=0x00000 ( 0) load
I (1784) boot: segment 6: paddr=0x00060be8 vaddr=0x00000000 size=0x0f420 ( 62496)
I (1806) boot: segment 7: paddr=0x00070010 vaddr=0x400d0018 size=0x9e510 (648464) map
I (1832) cpu_start: Pro cpu up.
I (1844) cpu_start: Starting app cpu, entry point is 0x40080de4
I (0) cpu_start: App cpu up.
I (1876) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1899) heap_alloc_caps: At 3FFAE2A0 len 00001D60 (7 KiB): DRAM
I (1919) heap_alloc_caps: At 3FFBA630 len 000259D0 (150 KiB): DRAM
I (1940) heap_alloc_caps: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM
I (1962) heap_alloc_caps: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (1983) heap_alloc_caps: At 40092928 len 0000D6D8 (53 KiB): IRAM
I (2004) cpu_start: Pro cpu start user code
I (2065) DTMon: Start
I (2075) Dynatrace: Start
I (2076) AWS: Start
I (2080) cpu_start: Starting scheduler on PRO CPU.
I (244) cpu_start: Starting scheduler on APP CPU.
assertion "false && "item should have been present in cache"" failed: file "C:/esp32/esp-idf/components/nvs_flash/src/nvs_item_hash_list.cpp", line 85, function: void nvs::HashList::erase(size_t)
abort() was called at PC 0x400fbb2f on core 0
Guru Meditation Error: Core 0 panic'ed (abort)

Backtrace: 0x40008155:0x3ffbb3e0 0x40007d16:0x3ffbb400 0x4010badf:0x3ffbb430 0x4010bfae:0x3ffbb450 0x4010c1a5:0x3ffbb490 0x4010b398:0x3ffbb4f0 0x4010b238:0x3ffbb540 0x4010b282:0x3ffbb560 0x40110706:0x3ffbb590 0x400d0985:0x3ffbb5b0

Rebooting...

[helmut-s]

ok - so erasing and re-programming the flash might help (but I have no idea what happened) - please have a look at the linked issue (#26)

[sygrosjean]

Rebooting...
ets Jun 8 2016 00:22:57

When i press reset i have
"rst:0x10 (RTCWDT_RTC_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download"

But i can't have access on console
I installed "flash_download_tools_v3.6.8" but Com is failed with this tool.
With putty communication is OK

[sygrosjean]

I had network issue it's OK now ! Thanks you