Open kuligs2 opened 3 months ago
I'm having the same issue on a brand-new device. My settings are identical to https://github.com/esphome/firmware/blob/main/voice-assistant/m5stack-atom-echo.yaml (except for api and wifi settings ofc)
logs:
[19:57:42]I (57) boot: ESP-IDF 4.4.7 2nd stage bootloader
[19:57:42]I (57) boot: compile time 18:44:21
[19:57:42]I (58) boot: Multicore bootloader
[19:57:42]I (61) boot: chip revision: v1.1
[19:57:42]I (65) boot.esp32: SPI Speed : 40MHz
[19:57:42]I (70) boot.esp32: SPI Mode : DIO
[19:57:42]I (74) boot.esp32: SPI Flash Size : 4MB
[19:57:42]I (79) boot: Enabling RNG early entropy source...
[19:57:42]I (84) boot: Partition Table:
[19:57:42]I (88) boot: ## Label Usage Type ST Offset Length
[19:57:42]I (95) boot: 0 otadata OTA data 01 00 00009000 00002000
[19:57:42]I (103) boot: 1 phy_init RF data 01 01 0000b000 00001000
[19:57:42]I (110) boot: 2 app0 OTA app 00 10 00010000 001c0000
[19:57:42]I (118) boot: 3 app1 OTA app 00 11 001d0000 001c0000
[19:57:42]I (125) boot: 4 nvs WiFi data 01 02 00390000 0006d000
[19:57:42]I (133) boot: End of partition table
[19:57:42]I (137) boot: No factory image, trying OTA 0
[19:57:42]I (142) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=65914h (416020) map
[19:57:42]I (301) esp_image: segment 1: paddr=0007593c vaddr=3ffbdb60 size=051bch ( 20924) load
[19:57:42]I (310) esp_image: segment 2: paddr=0007ab00 vaddr=40080000 size=05518h ( 21784) load
[19:57:42]I (319) esp_image: segment 3: paddr=00080020 vaddr=400d0020 size=1369dch (1272284) map
[19:57:42]I (779) esp_image: segment 4: paddr=001b6a04 vaddr=40085518 size=19a6ch (105068) load
[19:57:42]E (823) esp_image: Image length 1836192 doesn't fit in partition length 1835008
[19:57:42]E (823) boot: OTA app partition slot 0 is not bootable
[19:57:42]E (825) esp_image: image at 0x1d0000 has invalid magic byte (nothing flashed here?)
[19:57:42]E (834) boot: OTA app partition slot 1 is not bootable
[19:57:42]E (839) boot: No bootable app partitions in the partition table
[19:57:42]ets Jun 8 2016 00:22:57
[19:57:42]
[19:57:42]rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[19:57:42]configsip: 188777542, SPIWP:0xee
[19:57:42]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[19:57:42]mode:DIO, clock div:2
[19:57:42]load:0x3fff0030,len:6652
[19:57:42]ho 0 tail 12 room 4
[19:57:42]load:0x40078000,len:15052
[19:57:42]load:0x40080400,len:3836
[19:57:42]entry 0x4008069c
[19:57:42]I (57) boot: ESP-IDF 4.4.7 2nd stage bootloader
[19:57:42]I (57) boot: compile time 18:44:21
[19:57:42]I (57) boot: Multicore bootloader
[19:57:42]I (61) boot: chip revision: v1.1
[19:57:42]I (65) boot.esp32: SPI Speed : 40MHz
[19:57:42]I (70) boot.esp32: SPI Mode : DIO
[19:57:42]I (74) boot.esp32: SPI Flash Size : 4MB
[19:57:42]I (79) boot: Enabling RNG early entropy source...
[19:57:42]I (84) boot: Partition Table:
[19:57:42]I (88) boot: ## Label Usage Type ST Offset Length
[19:57:42]I (95) boot: 0 otadata OTA data 01 00 00009000 00002000
[19:57:42]I (103) boot: 1 phy_init RF data 01 01 0000b000 00001000
[19:57:42]I (110) boot: 2 app0 OTA app 00 10 00010000 001c0000
[19:57:42]I (118) boot: 3 app1 OTA app 00 11 001d0000 001c0000
[19:57:42]I (125) boot: 4 nvs WiFi data 01 02 00390000 0006d000
[19:57:42]I (133) boot: End of partition table
[19:57:42]I (137) boot: No factory image, trying OTA 0
[19:57:42]I (142) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=65914h (416020) map
[19:57:42]I (301) esp_image: segment 1: paddr=0007593c vaddr=3ffbdb60 size=051bch ( 20924) load
[19:57:42]I (310) esp_image: segment 2: paddr=0007ab00 vaddr=40080000 size=05518h ( 21784) load
[19:57:42]I (319) esp_image: segment 3: paddr=00080020 vaddr=400d0020 size=1369dch (1272284) map
[19:57:42]I (779) esp_image: segment 4: paddr=001b6a04 vaddr=40085518 size=19a6ch (105068) load
[19:57:43]E (823) esp_image: Image length 1836192 doesn't fit in partition length 1835008
[19:57:43]E (823) boot: OTA app partition slot 0 is not bootable
[19:57:43]E (825) esp_image: image at 0x1d0000 has invalid magic byte (nothing flashed here?)
[19:57:43]E (834) boot: OTA app partition slot 1 is not bootable
[19:57:43]E (839) boot: No bootable app partitions in the partition table
[19:57:43]ets Jun 8 2016 00:22:57
[19:57:43]
[19:57:43]rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[19:57:43]configsip: 188777542, SPIWP:0xee
[19:57:43]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[19:57:43]mode:DIO, clock div:2
[19:57:43]load:0x3fff0030,len:6652
[19:57:43]ho 0 tail 12 room 4
[19:57:43]load:0x40078000,len:15052
[19:57:43]load:0x40080400,len:3836
[19:57:43]entry 0x4008069c
I'm having the same issue on a brand-new device. My settings are identical to https://github.com/esphome/firmware/blob/main/voice-assistant/m5stack-atom-echo.yaml (except for api and wifi settings ofc)
logs:
[19:57:42]I (57) boot: ESP-IDF 4.4.7 2nd stage bootloader [19:57:42]I (57) boot: compile time 18:44:21 [19:57:42]I (58) boot: Multicore bootloader [19:57:42]I (61) boot: chip revision: v1.1 [19:57:42]I (65) boot.esp32: SPI Speed : 40MHz [19:57:42]I (70) boot.esp32: SPI Mode : DIO [19:57:42]I (74) boot.esp32: SPI Flash Size : 4MB [19:57:42]I (79) boot: Enabling RNG early entropy source... [19:57:42]I (84) boot: Partition Table: [19:57:42]I (88) boot: ## Label Usage Type ST Offset Length [19:57:42]I (95) boot: 0 otadata OTA data 01 00 00009000 00002000 [19:57:42]I (103) boot: 1 phy_init RF data 01 01 0000b000 00001000 [19:57:42]I (110) boot: 2 app0 OTA app 00 10 00010000 001c0000 [19:57:42]I (118) boot: 3 app1 OTA app 00 11 001d0000 001c0000 [19:57:42]I (125) boot: 4 nvs WiFi data 01 02 00390000 0006d000 [19:57:42]I (133) boot: End of partition table [19:57:42]I (137) boot: No factory image, trying OTA 0 [19:57:42]I (142) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=65914h (416020) map [19:57:42]I (301) esp_image: segment 1: paddr=0007593c vaddr=3ffbdb60 size=051bch ( 20924) load [19:57:42]I (310) esp_image: segment 2: paddr=0007ab00 vaddr=40080000 size=05518h ( 21784) load [19:57:42]I (319) esp_image: segment 3: paddr=00080020 vaddr=400d0020 size=1369dch (1272284) map [19:57:42]I (779) esp_image: segment 4: paddr=001b6a04 vaddr=40085518 size=19a6ch (105068) load [19:57:42]E (823) esp_image: Image length 1836192 doesn't fit in partition length 1835008 [19:57:42]E (823) boot: OTA app partition slot 0 is not bootable [19:57:42]E (825) esp_image: image at 0x1d0000 has invalid magic byte (nothing flashed here?) [19:57:42]E (834) boot: OTA app partition slot 1 is not bootable [19:57:42]E (839) boot: No bootable app partitions in the partition table [19:57:42]ets Jun 8 2016 00:22:57 [19:57:42] [19:57:42]rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) [19:57:42]configsip: 188777542, SPIWP:0xee [19:57:42]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 [19:57:42]mode:DIO, clock div:2 [19:57:42]load:0x3fff0030,len:6652 [19:57:42]ho 0 tail 12 room 4 [19:57:42]load:0x40078000,len:15052 [19:57:42]load:0x40080400,len:3836 [19:57:42]entry 0x4008069c [19:57:42]I (57) boot: ESP-IDF 4.4.7 2nd stage bootloader [19:57:42]I (57) boot: compile time 18:44:21 [19:57:42]I (57) boot: Multicore bootloader [19:57:42]I (61) boot: chip revision: v1.1 [19:57:42]I (65) boot.esp32: SPI Speed : 40MHz [19:57:42]I (70) boot.esp32: SPI Mode : DIO [19:57:42]I (74) boot.esp32: SPI Flash Size : 4MB [19:57:42]I (79) boot: Enabling RNG early entropy source... [19:57:42]I (84) boot: Partition Table: [19:57:42]I (88) boot: ## Label Usage Type ST Offset Length [19:57:42]I (95) boot: 0 otadata OTA data 01 00 00009000 00002000 [19:57:42]I (103) boot: 1 phy_init RF data 01 01 0000b000 00001000 [19:57:42]I (110) boot: 2 app0 OTA app 00 10 00010000 001c0000 [19:57:42]I (118) boot: 3 app1 OTA app 00 11 001d0000 001c0000 [19:57:42]I (125) boot: 4 nvs WiFi data 01 02 00390000 0006d000 [19:57:42]I (133) boot: End of partition table [19:57:42]I (137) boot: No factory image, trying OTA 0 [19:57:42]I (142) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=65914h (416020) map [19:57:42]I (301) esp_image: segment 1: paddr=0007593c vaddr=3ffbdb60 size=051bch ( 20924) load [19:57:42]I (310) esp_image: segment 2: paddr=0007ab00 vaddr=40080000 size=05518h ( 21784) load [19:57:42]I (319) esp_image: segment 3: paddr=00080020 vaddr=400d0020 size=1369dch (1272284) map [19:57:42]I (779) esp_image: segment 4: paddr=001b6a04 vaddr=40085518 size=19a6ch (105068) load [19:57:43]E (823) esp_image: Image length 1836192 doesn't fit in partition length 1835008 [19:57:43]E (823) boot: OTA app partition slot 0 is not bootable [19:57:43]E (825) esp_image: image at 0x1d0000 has invalid magic byte (nothing flashed here?) [19:57:43]E (834) boot: OTA app partition slot 1 is not bootable [19:57:43]E (839) boot: No bootable app partitions in the partition table [19:57:43]ets Jun 8 2016 00:22:57 [19:57:43] [19:57:43]rst:0x3 (SW_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) [19:57:43]configsip: 188777542, SPIWP:0xee [19:57:43]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 [19:57:43]mode:DIO, clock div:2 [19:57:43]load:0x3fff0030,len:6652 [19:57:43]ho 0 tail 12 room 4 [19:57:43]load:0x40078000,len:15052 [19:57:43]load:0x40080400,len:3836 [19:57:43]entry 0x4008069c
yeah i bought it too few days ago, At first it flashed somewhat ok, but when i unplug it, it reverts back to the default state (no lights, does nothing). Then i had to flash it several times to get it to work with voice assist, but still when i unplug it reverts back to default state.. and in the ESP home i always have multiple configurations showing up and the "adopt" button for the atom device with default ESP32 configuration/yaml. The adopt thing never go away even if i press it.
The ESP32 box 3 didnt had so many problems, flashed voice assistant on second try. The first one was blank white screen and voice assist didnt work. The screen turn on/off worked but whenever it is triggered the speaker would pop. This popping is still present even with correct voice assist on the box3 (with that smiley face, not the blank white screen).
Anyways.. is there a way to maybe not use these low powered devices but use android phone instead? I got many layin - e-wasting. It would be nice to put them to a good use.
My main gripe is that i want hands free experience with the assist cuz of disabilities.
I flashed an Atom Echo yesterday through https://esphome.io/projects/ and it resulted in a boot loop problem - at least I guess so from the lights. It wasn't possible to activate it by saying "ok nabu", nor through the button on the top and often lighted in red for half a second.
I flashed an Atom Echo yesterday through https://esphome.io/projects/ and it resulted in a boot loop problem - at least I guess so from the lights. It wasn't possible to activate it by saying "ok nabu", nor through the button on the top and often lighted in red for half a second.
I dont know exactly what i did but i got it working somehow.. Steps i took involved:
Install fw for first time use, COnnect to wifi Create the new yaml for voice assistant, using the template from github install it wirelessly from esphome page in homeassistant If it fails repeat the process..
Same happens for me. It occured, after the update which could not be installed ota, because of the new partition size. Then updated with "Plug into the computer running ESPHome Dashboard" Config:
substitutions:
name: echo1-238c04
friendly_name: Atom Echo 1 238c04
packages:
m5stack.atom-echo-voice-assistant: github://esphome/firmware/voice-assistant/m5stack-atom-echo.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
friendly_name: ${friendly_name}
api:
encryption:
key: xxx
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Turns out, it is already fixed in #227. Use the m5stack-atom-echo.adopted.yaml config
Turns out, it is already fixed in #227. Use the m5stack-atom-echo.adopted.yaml config
how can it be fixed if this happened to me last week?
how can it be fixed if this happened to me last week?
Just use the new config and write it via usb.
I was able to get my m5stack working again by using the yaml file included in this repository (normal, not adopdted) and esphome docker container.
In contrast to what is written on https://esphome.io/projects/?type=voice I got the impression that the following firmware is used https://github.com/esphome/wake-word-voice-assistants/blob/main/m5stack-atom-echo/m5stack-atom-echo.yaml , not the one from this repository. Because in this repository, there is no on-device wake-word engine on the latest main branch, but a set up device from https://esphome.io/projects/?type=voice contains the wake word engine -> This seems like a bug to me, even though having a local wake word on the device is desireable. Is it possible to fix this somehow? So that https://esphome.io/projects/?type=voice installs the latest firmware from this repository, not a firmware from some other repo, which is broken.
After install its looping.. Logs:
Yaml that i tried to flash using usb on web.esphome.io