ESP-EYE DevKit v2.2 (AIV-652)

[embertsolutions]

I have just bought a couple of ESP-EYE DevKit v2.2 All of the examples I have tried, have failed initialisation The logs below, are for the motion_detection example, but the same error occurs for all

I can get past this initial error, by changing the frame buffer to use DRAM, and reducing the number of frames to 1, but then I get the error related to the SPI

Is the ESP-EYE platform still supported? If not, what was the last Release/Tag that supported it?

Executing action: monitor Serial port /dev/ttyUSB0 Connecting.... Detecting chip type... Unsupported detection protocol, switching and trying again... Connecting...... Detecting chip type... ESP32 Running idf_monitor in directory /home/dha65/espeye/esp-who/examples/motion_detection/lcd Executing "/home/dha65/.espressif/python_env/idf4.4_py3.10_env/bin/python /home/dha65/esp/esp-idf/tools/idf_monitor.py -p /dev/ttyUSB0 -b 115200 --toolchain-prefix xtensa-esp32-elf- --target esp32 --revision 0 /home/dha65/espeye/esp-who/examples/motion_detection/lcd/build/motion_detection_lcd.elf -m '/home/dha65/.espressif/python_env/idf4.4_py3.10_env/bin/python' '/home/dha65/esp/esp-idf/tools/idf.py'"... --- 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:1 load:0x3fff0030,len:7012 load:0x40078000,len:15792 ho 0 tail 12 room 4 load:0x40080400,len:4536 0x40080400: _init at ??:?

entry 0x400806bc I (28) boot: ESP-IDF v4.4.5-402-ge9d442d2b7 2nd stage bootloader I (28) boot: compile time 21:27:41 I (28) boot: Multicore bootloader I (33) boot: chip revision: v1.0 I (36) qio_mode: Enabling default flash chip QIO I (42) boot.esp32: SPI Speed : 80MHz I (46) boot.esp32: SPI Mode : QIO I (51) boot.esp32: SPI Flash Size : 4MB I (55) boot: Enabling RNG early entropy source... I (61) boot: Partition Table: I (64) boot: ## Label Usage Type ST Offset Length I (72) boot: 0 nvs WiFi data 01 02 00009000 00006000 I (79) boot: 1 phy_init RF data 01 01 0000f000 00001000 I (87) boot: 2 factory factory app 00 00 00010000 00100000 I (94) boot: End of partition table I (98) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=3d868h (252008) map I (176) esp_image: segment 1: paddr=0004d890 vaddr=3ffb0000 size=02788h ( 10120) load I (180) esp_image: segment 2: paddr=00050020 vaddr=400d0020 size=50c48h (330824) map I (273) esp_image: segment 3: paddr=000a0c70 vaddr=3ffb2788 size=00780h ( 1920) load I (274) esp_image: segment 4: paddr=000a13f8 vaddr=40080000 size=0f180h ( 61824) load I (307) boot: Loaded app from partition at offset 0x10000 I (307) boot: Disabling RNG early entropy source... I (318) cpu_start: Multicore app I (318) cpu_start: Pro cpu up. I (318) cpu_start: Starting app cpu, entry point is 0x400813d0 0x400813d0: call_start_cpu1 at /home/dha65/esp/esp-idf/components/esp_system/port/cpu_start.c:151

I (0) cpu_start: App cpu up. I (336) cpu_start: Pro cpu start user code I (336) cpu_start: cpu freq: 160000000 I (336) cpu_start: Application information: I (341) cpu_start: Project name: motion_detection_lcd I (347) cpu_start: App version: v0.9.3-171-gb454739 I (353) cpu_start: Compile time: Sep 26 2023 21:27:36 I (359) cpu_start: ELF file SHA256: 1c0776d94af7a79c... I (365) cpu_start: ESP-IDF: v4.4.5-402-ge9d442d2b7 I (371) cpu_start: Min chip rev: v0.0 I (376) cpu_start: Max chip rev: v3.99 I (381) cpu_start: Chip rev: v1.0 I (386) heap_init: Initializing. RAM available for dynamic allocation: I (393) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (399) heap_init: At 3FFB5030 len 0002AFD0 (171 KiB): DRAM I (405) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM I (411) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (418) heap_init: At 4008F180 len 00010E80 (67 KiB): IRAM I (425) spi_flash: detected chip: generic I (429) spi_flash: flash io: qio I (435) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (443) who_camera: Camera module is ESP-EYE I (453) gpio: GPIO[13]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 I (453) gpio: GPIO[14]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 I (463) gpio: GPIO[5]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:2 I (473) cam_hal: cam init ok I (483) sccb: pin_sda 18 pin_scl 23 I (493) camera: Detected camera at address=0x3c I (493) camera: Detected OV3660 camera I (493) camera: Camera PID=0x3660 VER=0x00 MIDL=0x00 MIDH=0x00 I (833) esp32 ll_cam: node_size: 3840, nodes_per_line: 1, lines_per_node: 2, dma_half_buffer_min: 3840, dma_half_buffer: 15360, lines_per_half_buffer: 8, dma_buffer_size: 30720, image_size: 115200 I (833) cam_hal: buffer_size: 30720, half_buffer_size: 15360, node_buffer_size: 3840, node_cnt: 8, total_cnt: 7 I (843) cam_hal: Allocating 115200 Byte frame buffer in PSRAM E (853) cam_hal: cam_dma_config(292): frame buffer malloc failed E (863) cam_hal: cam_config(376): cam_dma_config failed E (863) camera: Camera config failed with error 0xffffffff E (873) who_camera: Camera init failed with error 0xffffffff E (873) spi: spicommon_bus_initialize_io(540): mosi not valid E (883) spi_bus: /home/dha65/espeye/esp-who/components/bus/spi_bus.c:78 (spi_bus_create):spi bus create failed E (893) screen interface: /home/dha65/espeye/esp-who/components/screen/interface_driver/scr_interface_driver.c:189 (spi_lcd_driver_init):gpio cs invalid E (913) screen interface: /home/dha65/espeye/esp-who/components/screen/interface_driver/scr_interface_driver.c:332 (scr_interface_create):screen spi interface create failed E (923) screen driver: Not support screen controller, it may not be enabled in menuconfig

[Sandra-lol]

Hi, ESP-EYE is still in support, and according to the readme, ESP-EYE is not suitable for motion detection/lcd example.