sieren / Homepoint

Espressif ESP32 Based Smarthome screen for MQTT
MIT License
629 stars 89 forks source link

M5Stack Core2 does not show any files #180

Open DGrebe opened 2 years ago

DGrebe commented 2 years ago

Hi,

this project is great work, I really appreciate your work.

I have two devices: an AZ Touch and a M5Stack Core2.

For the AZ Touch everything works fine but for the M5Stack Core2 I can initialize the system and get the HomePoint screen, but the file area is completely empty. I worked with the binaries from the release as well as with own build binaries and get the same results.

I have also uploaded the individual bin files to the following locations, same result.

esptool.py --port /dev/cu.SLAB_USBtoUART --chip esp32 -b 921600 write_flash --flash_mode dio --flash_freq 80m --flash_size 4MB 0x1000 bootloader.bin esptool.py --port /dev/cu.SLAB_USBtoUART --chip esp32 -b 921600 write_flash --flash_mode dio --flash_freq 80m --flash_size 4MB 0x8000 partition-table.bin esptool.py --port /dev/cu.SLAB_USBtoUART --chip esp32 -b 921600 write_flash --flash_mode dio --flash_freq 80m --flash_size 4MB 0xd000 ota_data_initial.bin esptool.py --port /dev/cu.SLAB_USBtoUART --chip esp32 -b 921600 write_flash --flash_mode dio --flash_freq 80m --flash_size 4MB 0x10000 homepoint.bin esptool.py --port /dev/cu.SLAB_USBtoUART --chip esp32 -b 921600 write_flash --flash_mode dio --flash_freq 80m --flash_size 4MB 0x2b0000 spiffs.bin

When I reload the home page, the M5Stack Core2 restarts, giving the following lines in the serial monitor. It complains about the file system, which is not mounted. Looks like a problem with a wrong or incorrectly mounted SPIFFS.


Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled. Core 1 register dump: PC : 0x400014fd PS : 0x00060030 A0 : 0x800f0505 A1 : 0x3ffd24a0
A2 : 0x80008000 A3 : 0x80007ffc A4 : 0x000000ff A5 : 0x0000ff00
A6 : 0x00ff0000 A7 : 0xff000000 A8 : 0x00000000 A9 : 0x3ffd2470
A10 : 0x3ffd24d0 A11 : 0x00000000 A12 : 0x0000000b A13 : 0x3ffd23a0
A14 : 0x00000003 A15 : 0x00060023 SAR : 0x0000001f EXCCAUSE: 0x0000001c
EXCVADDR: 0x80008000 LBEG : 0x400014fd LEND : 0x4000150d LCOUNT : 0xffffffff

ELF file SHA256: baad76808584ee02

Backtrace: 0x400014fa:0x3ffd24a0 0x400f0502:0x3ffd24b0 0x400f6cd1:0x3ffd24d0 0x400f6da1:0x3ffd2500 0x400f6eb5:0x3ffd2540 0x400f7099:0x3ffd2580 0x40100769:0x3ffd25a0 0x401007e5:0x3ffd25d0 0x40100ef6:0x3ffd25f0

Rebooting... ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x17 (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:1 load:0x3fff0018,len:4 load:0x3fff001c,len:6680 load:0x40078000,len:12636 load:0x40080400,len:3792 entry 0x40080684 I (61) boot: Chip Revision: 3 I (65) boot_comm: chip revision: 3, min. bootloader chip revision: 0 I (39) boot: ESP-IDF v4.0.3-dirty 2nd stage bootloader I (40) boot: compile time 21:33:16 I (40) boot: Enabling RNG early entropy source... I (45) boot: SPI Speed : 80MHz I (49) boot: SPI Mode : DIO I (53) boot: SPI Flash Size : 4MB I (57) boot: Partition Table: I (61) boot: ## Label Usage Type ST Offset Length I (68) boot: 0 nvs WiFi data 01 02 00009000 00004000 I (75) boot: 1 otadata OTA data 01 00 0000d000 00002000 I (83) boot: 2 phy_init RF data 01 01 0000f000 00001000 I (90) boot: 3 ota_0 OTA app 00 10 00010000 00150000 I (98) boot: 4 ota_1 OTA app 00 11 00160000 00150000 I (105) boot: 5 spiffs Unknown data 01 82 002b0000 000fa000 I (113) boot: End of partition table I (117) boot_comm: chip revision: 3, min. application chip revision: 0 I (124) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x4754c (292172) map I (228) esp_image: segment 1: paddr=0x00057574 vaddr=0x3ffb0000 size=0x03784 ( 14212) load I (233) esp_image: segment 2: paddr=0x0005ad00 vaddr=0x40080000 size=0x00400 ( 1024) load I (235) esp_image: segment 3: paddr=0x0005b108 vaddr=0x40080400 size=0x04f08 ( 20232) load I (251) esp_image: segment 4: paddr=0x00060018 vaddr=0x400d0018 size=0xdbea8 (900776) map I (544) esp_image: segment 5: paddr=0x0013bec8 vaddr=0x40085308 size=0x0fa60 ( 64096) load I (581) boot: Loaded app from partition at offset 0x10000 I (581) boot: Disabling RNG early entropy source... I (582) cpu_start: Pro cpu up. I (585) cpu_start: Application information: I (590) cpu_start: Project name: homepoint I (595) cpu_start: App version: v0.07.2-10-g9948fc4-dirty I (602) cpu_start: Compile time: Dec 13 2021 21:33:43 I (608) cpu_start: ELF file SHA256: baad76808584ee02... I (614) cpu_start: ESP-IDF: v4.0.3-dirty I (619) cpu_start: Starting app cpu, entry point is 0x4008135c I (606) cpu_start: App cpu up. I (630) heap_init: Initializing. RAM available for dynamic allocation: I (637) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (643) heap_init: At 3FFBB150 len 00024EB0 (147 KiB): DRAM I (649) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (655) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (662) heap_init: At 40094D68 len 0000B298 (44 KiB): IRAM I (668) cpu_start: Pro cpu start user code I (688) spi_flash: detected chip: generic I (689) spi_flash: flash io: dio W (689) spi_flash: Detected size(16384k) larger than the size in the binary image header(4096k). Using the size in the binary image header. I (699) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. [E][esp32-hal-cpu.c:125] removeApbChangeCallback(): not found func=400F34A0 arg=3FFB13A8 [E][vfs_api.cpp:22] open(): File system is not mounted Jpeg file not found [E][vfs_api.cpp:22] open(): File system is not mounted Jpeg file not found E (2013) example: Failed to find Font I (2043) wifi:wifi driver task: 3ffde7fc, prio:23, stack:6656, core=0 I (2043) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE I (2048) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE I (2069) wifi:wifi firmware version: 52d2120 I (2069) wifi:config NVS flash: enabled I (2069) wifi:config nano formating: disabled I (2071) wifi:Init data frame dynamic rx buffer num: 32 I (2076) wifi:Init management frame dynamic rx buffer num: 32 I (2081) wifi:Init management short buffer num: 32 I (2086) wifi:Init dynamic tx buffer num: 32 I (2090) wifi:Init static rx buffer size: 1600 I (2094) wifi:Init static rx buffer num: 10 I (2098) wifi:Init dynamic rx buffer num: 32 I (2103) wifi_init: rx ba win: 6 I (2107) wifi_init: tcpip mbox: 32 I (2111) wifi_init: udp mbox: 6 I (2115) wifi_init: tcp mbox: 6 I (2119) wifi_init: tcp tx win: 5744 I (2123) wifi_init: tcp rx win: 5744 I (2127) wifi_init: tcp mss: 1436 I (2131) wifi_init: WiFi IRAM OP enabled I (2135) wifi_init: WiFi RX IRAM OP enabled I (2143) phy_init: phy_version 4660,0162888,Dec 23 2020 I (2227) wifi:mode : sta (b8:f0:09:c6:1f:c0) E (2228) event: system event loop not initialized via esp_event_loop_init I (2228) wifi station: wifi_init_sta finished. I (2234) wifi station: connect to ap SSID: password: I (2267) wifi:new:<11,0>, old:<1,0>, ap:<255,255>, sta:<11,0>, prof:1 I (2268) wifi:state: init -> auth (b0) I (2278) wifi:state: auth -> assoc (0) I (2285) wifi:state: assoc -> run (10) I (2309) wifi:connected with HOMELAN, aid = 4, channel 11, BW20, bssid = 08:96:d7:80:dc:c6 I (2310) wifi:security: WPA2-PSK, phy: bgn, rssi: -54 I (2314) wifi:pm start, type: 1

E (2314) event: system event loop not initialized via esp_event_loop_init I (2471) wifi:AP's beacon interval = 102400 us, DTIM period = 1 E (2527) event: system event loop not initialized via esp_event_loop_init I (2527) tcpip_adapter: sta ip: 192.168.123.10, mask: 255.255.255.0, gw: 192.168.123.254 I (2532) wifi station: got ip:192.168.123.10


What can I do?

Kind Regards

Dirk

Next9999 commented 2 years ago

Hello

i am looking to use a M5 Core 2 .... is it working on your end?

DGrebe commented 2 years ago

Hi,

I am not sure anymore, how far I came, as I worked on this last winter. I think I got it running on the M5 Core 2, but it might be unstable. I have tried to extend the navigation to include folders / hierachies but was not successful, then I stopped working on this topic. I don't have Homepoint active at the moment.

I will check, when I have time to look into it again.

Regards Dirk