esp32 wroom and camera ov7670

Gaston1980
Posts: 28
Joined: Sun Oct 06, 2024 10:26 am

esp32 wroom and camera ov7670

Postby Gaston1980 » Mon Oct 14, 2024 3:57 pm

Hi to all, Im using the camera ov7670 with the esp32 wroom kit and finally I'm able to get the frame data in 320x240 *2 framebytes.....153600 bytes I got in frame....and now the question...how do I send this frame to uart? I'm using ESP_LOGI to send it to terminal and is tooooo slowww.
I only got an ftdi board connected to uart2 of the esp32 board but I'm unable to send each char of the frame, how can I get those bytes and send it to uart2?
Maybe is the dumbest question but right now I'm unable to see it
Regards
Gastón

ESP_Sprite
Posts: 9757
Joined: Thu Nov 26, 2015 4:08 am

Re: esp32 wroom and camera ov7670

Postby ESP_Sprite » Tue Oct 15, 2024 3:31 am

You'd use the uart driver. Don't expect great performance, though: if you have good hardware, you may be able to get it working at 4Mbaud, meaning a frame rate of ((4000000/10)/153600)=2.6fps.

Gaston1980
Posts: 28
Joined: Sun Oct 06, 2024 10:26 am

Re: esp32 wroom and camera ov7670

Postby Gaston1980 » Tue Oct 15, 2024 10:25 am

Hi @ESP_Sprite thanks for your reply, I'm trying to understand and play with the camera ov7670 and I was able to get it working in the esp32 wroom 32E board, now I 'm trying to get out those bytes in the frame buffer. For this I create a task in which I use the uart driver to send to cutecom the data to then get the image. At frist I was thinking in sending the bytes but a lot of garbage is send it too like this:

Code: Select all

+<break x 002>
+<break x 002>
i guess is the problem of the cutecom......
I tried to use:

Code: Select all

ESP_LOG_BUFFER_HEXDUMP(TAG,frame,153600,ESP_LOG_DEBUG);
But the watchdog reset the output, and here's the question_

1) how can I do the hexdump without been rest by the watchdog?

this is the task I used:

Code: Select all

void send_data(void *arg)
{
    while (1) {
    ESP_LOG_BUFFER_HEXDUMP(TAG,frame,153600,ESP_LOG_DEBUG);
    vTaskDelay(1 / portTICK_PERIOD_MS);
    } 
}
I read about the watchdog reset but I guess it can't be used in this case due to the hexdump function.
Regards
Gastón

nopnop2002
Posts: 111
Joined: Thu Oct 03, 2019 10:52 pm
Contact:

Re: esp32 wroom and camera ov7670

Postby nopnop2002 » Tue Oct 15, 2024 9:16 pm

>At frist I was thinking in sending the bytes but a lot of garbage is send it too like this:


This appears to be real data, not garbage.


>how can I do the hexdump without been rest by the watchdog?

Disable task watchdog timer using menuconfig.
Attachments
TWDT.jpg
TWDT.jpg (124.58 KiB) Viewed 1311 times

Gaston1980
Posts: 28
Joined: Sun Oct 06, 2024 10:26 am

Re: esp32 wroom and camera ov7670

Postby Gaston1980 » Tue Oct 15, 2024 10:40 pm

Thanks nopnop2002 for your help, I was able to make the hexdump but...(theres always a but....) is there a way to save this dump to txt because I'm unable to check the first lines of the hexdump ( missed 9000 lines).
Thanks again
Gastón

nopnop2002
Posts: 111
Joined: Thu Oct 03, 2019 10:52 pm
Contact:

Re: esp32 wroom and camera ov7670

Postby nopnop2002 » Tue Oct 15, 2024 11:00 pm

> is there a way to save this dump to txt

Code: Select all

idf.py flash monitor -p /dev/ttyUSB0 > hoge.txt

Gaston1980
Posts: 28
Joined: Sun Oct 06, 2024 10:26 am

Re: esp32 wroom and camera ov7670

Postby Gaston1980 » Wed Oct 16, 2024 10:20 am

thanks for ur help nopnop2002 and ESP_Sprite I was able to do it. A final question about the port been used to do the dump, how do I close it? I tried Ctrl + C but that didn't work.
Thanks again
Cheers
Gastón

nopnop2002
Posts: 111
Joined: Thu Oct 03, 2019 10:52 pm
Contact:

Re: esp32 wroom and camera ov7670

Postby nopnop2002 » Wed Oct 16, 2024 10:23 am

>how do I close it?

Crl+]

Gaston1980
Posts: 28
Joined: Sun Oct 06, 2024 10:26 am

Re: esp32 wroom and camera ov7670

Postby Gaston1980 » Wed Oct 16, 2024 12:17 pm

nopnop2002 thanks, I tried and is not working. I need to restart vscode to be able to use again the port.

Gaston1980
Posts: 28
Joined: Sun Oct 06, 2024 10:26 am

Re: esp32 wroom and camera ov7670

Postby Gaston1980 » Wed Oct 16, 2024 1:31 pm

well something start to going wrong....

Code: Select all

I (285) efuse_init: Min chip rev:     v0.0
I (290) efuse_init: Max chip rev:     v3.99 
I (295) efuse_init: Chip rev:         v3.1
D (300) cpu_start: calling init function: 0x400d2fc8 on core: 0
--- 0x400d2fc8: __esp_system_init_fn_init_heap at /home/gaston/esp/v5.3.1/esp-idf/components/heap/heap_caps_init.c:25

V (306) memory_layout: reserved range is 0x3f40d444 - 0x3f40d48c
D (312) memory_layout: Checking 9 reserved memory ranges:
D (317) memory_layout: Reserved memory range 0x3ff82000 - 0x3ff82000
D (324) memory_layout: Reserved memory range 0x3ffae000 - 0x3ffae6e0
D (330) memory_layout: Reserved memory range 0x3ffb0000 - 0x3ffb2e30
D (337) memory_layout: Reserved memory range 0x3ffe0000 - 0x3ffe0440
D (343) memory_layout: Reserved memory range 0x3ffe3f20 - 0x3ffe4350
D (350) memory_layout: Reserved memory range 0x40070000 - 0x40078000
D (356) memory_layout: Reserved memory range 0x40078000 - 0x40080000
--- 0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

D (362) memory_layout: Reserved memory range 0x40080000 - 0x4008e338
--- 0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

D (369) memory_layout: Reserved memory range 0x50001fe8 - 0x50002000
D (375) memory_layout: Building list of available memory regions:
V (381) memory_layout: Examining memory region 0x3ffae000 - 0x3ffb0000
V (388) memory_layout: Start of region 0x3ffae000 - 0x3ffb0000 overlaps reserved 0x3ffae000 - 0x3ffae6e0
D (398) memory_layout: Available memory region 0x3ffae6e0 - 0x3ffb0000
V (404) memory_layout: Examining memory region 0x3ffb0000 - 0x3ffb8000
V (411) memory_layout: Start of region 0x3ffb0000 - 0x3ffb8000 overlaps reserved 0x3ffb0000 - 0x3ffb2e30
D (420) memory_layout: Available memory region 0x3ffb2e30 - 0x3ffb8000
V (427) memory_layout: Examining memory region 0x3ffb8000 - 0x3ffc0000
D (434) memory_layout: Available memory region 0x3ffb8000 - 0x3ffc0000
V (440) memory_layout: Examining memory region 0x3ffc0000 - 0x3ffc2000
D (447) memory_layout: Available memory region 0x3ffc0000 - 0x3ffc2000
V (453) memory_layout: Examining memory region 0x3ffc2000 - 0x3ffc4000
D (460) memory_layout: Available memory region 0x3ffc2000 - 0x3ffc4000
V (467) memory_layout: Examining memory region 0x3ffc4000 - 0x3ffc6000
D (473) memory_layout: Available memory region 0x3ffc4000 - 0x3ffc6000
V (480) memory_layout: Examining memory region 0x3ffc6000 - 0x3ffc8000
D (486) memory_layout: Available memory region 0x3ffc6000 - 0x3ffc8000
V (493) memory_layout: Examining memory region 0x3ffc8000 - 0x3ffca000
D (499) memory_layout: Available memory region 0x3ffc8000 - 0x3ffca000
V (506) memory_layout: Examining memory region 0x3ffca000 - 0x3ffcc000
D (513) memory_layout: Available memory region 0x3ffca000 - 0x3ffcc000
V (519) memory_layout: Examining memory region 0x3ffcc000 - 0x3ffce000
D (526) memory_layout: Available memory region 0x3ffcc000 - 0x3ffce000
V (532) memory_layout: Examining memory region 0x3ffce000 - 0x3ffd0000
D (539) memory_layout: Available memory region 0x3ffce000 - 0x3ffd0000
V (546) memory_layout: Examining memory region 0x3ffd0000 - 0x3ffd2000
D (552) memory_layout: Available memory region 0x3ffd0000 - 0x3ffd2000
V (559) memory_layout: Examining memory region 0x3ffd2000 - 0x3ffd4000
D (565) memory_layout: Available memory region 0x3ffd2000 - 0x3ffd4000
V (572) memory_layout: Examining memory region 0x3ffd4000 - 0x3ffd6000
D (579) memory_layout: Available memory region 0x3ffd4000 - 0x3ffd6000
V (585) memory_layout: Examining memory region 0x3ffd6000 - 0x3ffd8000
D (592) memory_layout: Available memory region 0x3ffd6000 - 0x3ffd8000
V (598) memory_layout: Examining memory region 0x3ffd8000 - 0x3ffda000
D (605) memory_layout: Available memory region 0x3ffd8000 - 0x3ffda000
V (612) memory_layout: Examining memory region 0x3ffda000 - 0x3ffdc000
D (618) memory_layout: Available memory region 0x3ffda000 - 0x3ffdc000
V (625) memory_layout: Examining memory region 0x3ffdc000 - 0x3ffde000
D (631) memory_layout: Available memory region 0x3ffdc000 - 0x3ffde000
V (638) memory_layout: Examining memory region 0x3ffde000 - 0x3ffe0000
D (645) memory_layout: Available memory region 0x3ffde000 - 0x3ffe0000
V (651) memory_layout: Examining memory region 0x3ffe0000 - 0x3ffe4000
V (658) memory_layout: Start of region 0x3ffe0000 - 0x3ffe4000 overlaps reserved 0x3ffe0000 - 0x3ffe0440
V (667) memory_layout: End of region 0x3ffe0440 - 0x3ffe4000 overlaps reserved 0x3ffe3f20 - 0x3ffe4350
D (677) memory_layout: Available memory region 0x3ffe0440 - 0x3ffe3f20
V (683) memory_layout: Examining memory region 0x3ffe4000 - 0x3ffe8000
V (690) memory_layout: Start of region 0x3ffe4000 - 0x3ffe8000 overlaps reserved 0x3ffe3f20 - 0x3ffe4350
D (699) memory_layout: Available memory region 0x3ffe4350 - 0x3ffe8000
V (706) memory_layout: Examining memory region 0x3ffe8000 - 0x3fff0000
D (713) memory_layout: Available memory region 0x3ffe8000 - 0x3fff0000
V (719) memory_layout: Examining memory region 0x3fff0000 - 0x3fff8000
D (726) memory_layout: Available memory region 0x3fff0000 - 0x3fff8000
V (732) memory_layout: Examining memory region 0x3fff8000 - 0x3fffc000
D (739) memory_layout: Available memory region 0x3fff8000 - 0x3fffc000
V (746) memory_layout: Examining memory region 0x3fffc000 - 0x40000000
--- 0x40000000: _WindowOverflow4 in ROM

D (752) memory_layout: Available memory region 0x3fffc000 - 0x40000000
--- 0x40000000: _WindowOverflow4 in ROM

V (759) memory_layout: Examining memory region 0x40070000 - 0x40078000
V (765) memory_layout: Region 0x40070000 - 0x40078000 inside of reserved 0x40070000 - 0x40078000
V (774) memory_layout: Examining memory region 0x40078000 - 0x40080000
--- 0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (781) memory_layout: Region 0x40078000 - 0x40080000 inside of reserved 0x40078000 - 0x40080000
--- 0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (790) memory_layout: Examining memory region 0x40080000 - 0x40082000
--- 0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027
0x40082000: heap_caps_malloc_default at /home/gaston/esp/v5.3.1/esp-idf/components/heap/heap_caps.c:129

V (796) memory_layout: Region 0x40080000 - 0x40082000 inside of reserved 0x40080000 - 0x4008e338
--- 0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027
0x40082000: heap_caps_malloc_default at /home/gaston/esp/v5.3.1/esp-idf/components/heap/heap_caps.c:129
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (805) memory_layout: Examining memory region 0x40082000 - 0x40084000
--- 0x40082000: heap_caps_malloc_default at /home/gaston/esp/v5.3.1/esp-idf/components/heap/heap_caps.c:129
0x40084000: flash_end_flush_cache at /home/gaston/esp/v5.3.1/esp-idf/components/spi_flash/esp_flash_api.c:241

V (812) memory_layout: Region 0x40082000 - 0x40084000 inside of reserved 0x40080000 - 0x4008e338
--- 0x40082000: heap_caps_malloc_default at /home/gaston/esp/v5.3.1/esp-idf/components/heap/heap_caps.c:129
0x40084000: flash_end_flush_cache at /home/gaston/esp/v5.3.1/esp-idf/components/spi_flash/esp_flash_api.c:241
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (821) memory_layout: Examining memory region 0x40084000 - 0x40086000
--- 0x40084000: flash_end_flush_cache at /home/gaston/esp/v5.3.1/esp-idf/components/spi_flash/esp_flash_api.c:241
0x40086000: prvInitializeNewRingbuffer at /home/gaston/esp/v5.3.1/esp-idf/components/esp_ringbuf/ringbuf.c:245

V (827) memory_layout: Region 0x40084000 - 0x40086000 inside of reserved 0x40080000 - 0x4008e338
--- 0x40084000: flash_end_flush_cache at /home/gaston/esp/v5.3.1/esp-idf/components/spi_flash/esp_flash_api.c:241
0x40086000: prvInitializeNewRingbuffer at /home/gaston/esp/v5.3.1/esp-idf/components/esp_ringbuf/ringbuf.c:245
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (836) memory_layout: Examining memory region 0x40086000 - 0x40088000
--- 0x40086000: prvInitializeNewRingbuffer at /home/gaston/esp/v5.3.1/esp-idf/components/esp_ringbuf/ringbuf.c:245
0x40088000: prvSelectHighestPriorityTaskSMP at /home/gaston/esp/v5.3.1/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:3635

V (843) memory_layout: Region 0x40086000 - 0x40088000 inside of reserved 0x40080000 - 0x4008e338
--- 0x40086000: prvInitializeNewRingbuffer at /home/gaston/esp/v5.3.1/esp-idf/components/esp_ringbuf/ringbuf.c:245
0x40088000: prvSelectHighestPriorityTaskSMP at /home/gaston/esp/v5.3.1/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:3635
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (852) memory_layout: Examining memory region 0x40088000 - 0x4008a000
--- 0x40088000: prvSelectHighestPriorityTaskSMP at /home/gaston/esp/v5.3.1/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:3635
0x4008a000: ledc_ll_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/esp32/include/hal/ledc_ll.h:313
 (inlined by) ledc_hal_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/ledc_hal_iram.c:31

V (858) memory_layout: Region 0x40088000 - 0x4008a000 inside of reserved 0x40080000 - 0x4008e338
--- 0x40088000: prvSelectHighestPriorityTaskSMP at /home/gaston/esp/v5.3.1/esp-idf/components/freertos/FreeRTOS-Kernel/tasks.c:3635
0x4008a000: ledc_ll_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/esp32/include/hal/ledc_ll.h:313
 (inlined by) ledc_hal_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/ledc_hal_iram.c:31
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (867) memory_layout: Examining memory region 0x4008a000 - 0x4008c000
--- 0x4008a000: ledc_ll_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/esp32/include/hal/ledc_ll.h:313
 (inlined by) ledc_hal_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/ledc_hal_iram.c:31
0x4008c000: align_ptr at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:234 (discriminator 1)
 (inlined by) tlsf_memalign_offs at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:1151 (discriminator 1)

V (874) memory_layout: Region 0x4008a000 - 0x4008c000 inside of reserved 0x40080000 - 0x4008e338
--- 0x4008a000: ledc_ll_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/esp32/include/hal/ledc_ll.h:313
 (inlined by) ledc_hal_set_hpoint at /home/gaston/esp/v5.3.1/esp-idf/components/hal/ledc_hal_iram.c:31
0x4008c000: align_ptr at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:234 (discriminator 1)
 (inlined by) tlsf_memalign_offs at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:1151 (discriminator 1)
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (882) memory_layout: Examining memory region 0x4008c000 - 0x4008e000
--- 0x4008c000: align_ptr at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:234 (discriminator 1)
 (inlined by) tlsf_memalign_offs at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:1151 (discriminator 1)
0x4008e000: xthal_window_spill_nw at /Users/igrokhotkov/e/esp32/hal/hal/windowspill_asm.S:212

V (889) memory_layout: Region 0x4008c000 - 0x4008e000 inside of reserved 0x40080000 - 0x4008e338
--- 0x4008c000: align_ptr at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:234 (discriminator 1)
 (inlined by) tlsf_memalign_offs at /home/gaston/esp/v5.3.1/esp-idf/components/heap/tlsf/tlsf.c:1151 (discriminator 1)
0x4008e000: xthal_window_spill_nw at /Users/igrokhotkov/e/esp32/hal/hal/windowspill_asm.S:212
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

V (898) memory_layout: Examining memory region 0x4008e000 - 0x40090000
--- 0x4008e000: xthal_window_spill_nw at /Users/igrokhotkov/e/esp32/hal/hal/windowspill_asm.S:212

V (905) memory_layout: Start of region 0x4008e000 - 0x40090000 overlaps reserved 0x40080000 - 0x4008e338
--- 0x4008e000: xthal_window_spill_nw at /Users/igrokhotkov/e/esp32/hal/hal/windowspill_asm.S:212
0x40080000: _WindowOverflow4 at /home/gaston/esp/v5.3.1/esp-idf/components/xtensa/xtensa_vectors.S:2027

D (914) memory_layout: Available memory region 0x4008e338 - 0x40090000
V (921) memory_layout: Examining memory region 0x40090000 - 0x40092000
D (927) memory_layout: Available memory region 0x40090000 - 0x40092000
V (934) memory_layout: Examining memory region 0x40092000 - 0x40094000
D (940) memory_layout: Available memory region 0x40092000 - 0x40094000
V (947) memory_layout: Examining memory region 0x40094000 - 0x40096000
D (954) memory_layout: Available memory region 0x40094000 - 0x40096000
V (960) memory_layout: Examining memory region 0x40096000 - 0x40098000
D (967) memory_layout: Available memory region 0x40096000 - 0x40098000
V (973) memory_layout: Examining memory region 0x40098000 - 0x4009a000
D (980) memory_layout: Available memory region 0x40098000 - 0x4009a000
V (987) memory_layout: Examining memory region 0x4009a000 - 0x4009c000
D (993) memory_layout: Available memory region 0x4009a000 - 0x4009c000
V (1000) memory_layout: Examining memory region 0x4009c000 - 0x4009e000
D (1007) memory_layout: Available memory region 0x4009c000 - 0x4009e000
V (1013) memory_layout: Examining memory region 0x4009e000 - 0x400a0000
D (1020) memory_layout: Available memory region 0x4009e000 - 0x400a0000
I (1027) heap_init: Initializing. RAM available for dynamic allocation:
D (1034) heap_init: New heap initialised at 0x3ffae6e0
I (1039) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
D (1045) heap_init: New heap initialised at 0x3ffb2e30
I (1050) heap_init: At 3FFB2E30 len 0002D1D0 (180 KiB): DRAM
I (1057) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (1063) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
D (1070) heap_init: New heap initialised at 0x4008e338
I (1075) heap_init: At 4008E338 len 00011CC8 (71 KiB): IRAM
D (1081) cpu_start: calling init function: 0x400d4540 on core: 0
--- 0x400d4540: __esp_system_init_fn_esp_timer_init_nonos at /home/gaston/esp/v5.3.1/esp-idf/components/esp_timer/src/esp_timer_init.c:28

D (1087) cpu_start: calling init function: 0x400d40a0 on core: 0
--- 0x400d40a0: __esp_system_init_fn_init_newlib at /home/gaston/esp/v5.3.1/esp-idf/components/newlib/newlib_init.c:162

D (1093) cpu_start: calling init function: 0x400d162c on core: 0
--- 0x400d162c: __esp_system_init_fn_init_brownout at /home/gaston/esp/v5.3.1/esp-idf/components/esp_system/startup_funcs.c:67

V (1099) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (1106) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0x40E
D (1114) intr_alloc: Connected src 46 to int 1 (cpu 0)
D (1119) cpu_start: calling init function: 0x400d1638 on core: 0
--- 0x400d1638: __esp_system_init_fn_init_newlib_time at /home/gaston/esp/v5.3.1/esp-idf/components/esp_system/startup_funcs.c:81

D (1125) cpu_start: calling init function: 0x400d5670 on core: 0
--- 0x400d5670: __esp_system_init_fn_init_vfs_uart at /home/gaston/esp/v5.3.1/esp-idf/components/esp_driver_uart/src/uart_vfs.c:1080

D (1132) cpu_start: calling init function: 0x400d768c on core: 0
--- 0x400d768c: __esp_system_init_fn_init_vfs_console at /home/gaston/esp/v5.3.1/esp-idf/components/esp_vfs_console/vfs_console.c:222

D (1138) cpu_start: calling init function: 0x400d410c on core: 0
--- 0x400d410c: __esp_system_init_fn_init_newlib_stdio at /home/gaston/esp/v5.3.1/esp-idf/components/newlib/newlib_init.c:207

D (1144) cpu_start: calling init function: 0x400d4470 on core: 0
--- 0x400d4470: __esp_system_init_fn_init_pthread at /home/gaston/esp/v5.3.1/esp-idf/components/pthread/pthread.c:76

D (1150) cpu_start: calling init function: 0x400d1644 on core: 0
--- 0x400d1644: __esp_system_init_fn_init_flash at /home/gaston/esp/v5.3.1/esp-idf/components/esp_system/startup_funcs.c:88

V (1156) memspi: raw_chip_id: 164068

V (1160) memspi: chip_id: 684016

V (1163) memspi: raw_chip_id: 164068

V (1167) memspi: chip_id: 684016

D (1170) spi_flash: trying chip: issi
D (1174) spi_flash: trying chip: gd
D (1178) spi_flash: trying chip: mxic
D (1181) spi_flash: trying chip: winbond
D (1185) spi_flash: trying chip: generic
I (1189) spi_flash: detected chip: generic
I (1194) spi_flash: flash io: dio
W (1198) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
D (1211) cpu_start: calling init function: 0x400d1560 on core: 0
--- 0x400d1560: __esp_system_init_fn_init_efuse at /home/gaston/esp/v5.3.1/esp-idf/components/efuse/src/esp_efuse_startup.c:137

D (1217) cpu_start: calling init function: 0x400857c4
--- 0x400857c4: enable_timer_group0_for_calibration at /home/gaston/esp/v5.3.1/esp-idf/components/esp_hw_support/port/esp32/rtc_time.c:197

D (1223) cpu_start: calling init function: 0x400d26a8
--- 0x400d26a8: esp_ipc_init at /home/gaston/esp/v5.3.1/esp-idf/components/esp_system/esp_ipc.c:113

D (1228) cpu_start: calling init function: 0x400d1be8
--- 0x400d1be8: esp_reset_reason_init at /home/gaston/esp/v5.3.1/esp-idf/components/esp_system/port/soc/esp32/reset_reason.c:60

D (1233) cpu_start: calling init function: 0x400d1668 on core: 0
--- 0x400d1668: __esp_system_init_fn_init_disable_rtc_wdt at /home/gaston/esp/v5.3.1/esp-idf/components/esp_system/startup_funcs.c:143

V (1239) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (1245) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0x40E
D (1254) intr_alloc: Connected src 24 to int 2 (cpu 0)
D (1259) app_start: Starting scheduler on CPU0
V (1263) intr_alloc: esp_intr_alloc_intrstatus (cpu 1): checking args
V (1263) intr_alloc: esp_intr_alloc_intrstatus (cpu 1): Args okay. Resulting flags 0x40E
 (1273) intr_alloc: Connected src 25 to int 1 (cpu 1)
D (1283) app_start: Starting scheduler on CPU1
;32mI (1263) main_task: Started on CPU0
D (1293) heap_init: New heap initialised at 0x3ffe0440
D (1293) heap_init: New heap initialised at 0x3ffe4350
V (1293) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (1303) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (1313) intr_alloc: Connected src 16 to int 3 (cpu 0)
I (1313) main_task: Calling app_main()
V (1323) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (1323) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xE
D (1333) intr_alloc: Connected src 36 to int 5 (cpu 0)
E (1343) gpio: GPIO can only be used as input mode
D (1343) ledc: Using clock source 4 (in fast mode), divisor: 0x500
D (1353) ledc: LEDC_PWM CHANNEL 0|GPIO 04|Duty 0000|Time 0
D (1363) i2c.common: new bus(0) at 0x3ffdaf38
W (1363) i2c.master: Please check pull-up resistances whether be connected properly. Otherwise unexpected behavior would happen. For more detailed information, please read docs
I (1383) gpio: GPIO[21]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 0| Pulldown: 0| Intr:0 
I (1393) gpio: GPIO[22]| InputEn: 1| OutputEn: 1| OpenDrain: 1| Pullup: 0| Pulldown: 0| Intr:0 
D (1393) i2c.common: bus clock source frequency: 80000000hz
V (1403) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (1413) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0x10E
D (1423) intr_alloc: Connected src 49 to int 8 (cpu 0)
I (1423) MAIN: write configs
I (1423) gpio: GPIO[19]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1433) gpio: GPIO[18]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1443) gpio: GPIO[23]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1453) gpio: GPIO[15]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1463) gpio: GPIO[2]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1473) gpio: GPIO[27]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1483) gpio: GPIO[26]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1493) gpio: GPIO[25]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1503) gpio: GPIO[33]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1513) gpio: GPIO[32]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
I (1523) gpio: GPIO[35]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 
V (1533) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (1533) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xC02
D (1543) intr_alloc: Connected src 32 to int 9 (cpu 0)
I (1553) MAIN: camera configure and init
I (1553) MAIN: Initializing VSYNC... 
V (1563) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): checking args
V (1563) intr_alloc: esp_intr_alloc_intrstatus (cpu 0): Args okay. Resulting flags 0xC0E
D (1573) intr_alloc: Connected src 22 to int 12 (cpu 0)
I (1583) MAIN: done initVsync
I (1583) MAIN: start
I (1583) MAIN: I2S Run
I (1593) MAIN: end I2SRun
I (1593) MAIN: stop
E (6433) task_wdt: Task watchdog got triggered. The following tasks/users did not reset the watchdog in time:
E (6433) task_wdt:  - IDLE0 (CPU 0)
E (6433) task_wdt: Tasks currently running:
E (6433) task_wdt: CPU 0: main
E (6433) task_wdt: CPU 1: IDLE1
E (6433) task_wdt: Print CPU 0 (current core) backtrace
this was never shown before and now the watchdog is been called. 'till yesterday I was able to send to uart the hexdump

Who is online

Users browsing this forum: Baidu [Spider] and 338 guests