running codes in parallel or more PSRAM?

[josef2600]

so, let’s talk about OV5640 camera.
running codes in parallel or using more PSRAM is more important?
in readme, it says:

Recordable frame rates for the OV5460 highest framesizes on an ESP32S3 are:
FHD = 6 FPS

and in datasheet we have: 1080p: 30 fps
so, what are the main causes that drop the frame rate? i know the 5MP is 5M*2 byte in 16bit. meaning 10MByte per frame for reading per frame from camera. now, if we have a 16MB PSRAM, does it fix the frame rate or it is mostly caused by CPU? because we have ESP32-S3R16V with 16MB PSRAM.
but in processing, what if we add another ESP32-S3 to it? let’s say one connected to camera and runs the code for that only and another one runs everything else and connect them via SPI.
my question is, can ESP32-S3 handle the speed of processing of that frame rate or not and this is not feasible?
please don't think about the hardware or how to connect them, only from coding point and the power of ESP32-s3.
thank you.

[s60sc]

30fps requires 24MHz clock, ESP32 can only reliably generate 20MHz. Whether ESP32S3 can reliably generate 24MHz clock is something you could try.

[josef2600]

that i can! i have it all. except my camera board hasn't arrived yet! but i will test it on other boards.

[josef2600]

I'm back!
i didn't know it myself, but since the board version 3 , they fucked up so many things. in board version 2.14 , i could easily use arduino drivers to get 40MHz on esp32 and esp32-s3. but since version 3, it is no longer going to work. so, i changed the driver and use the IDF driver version. and now we have it working. the weirdness is the long cables. and the output in high frequency's are sin wave and it is OK. the input clock has schmitt trigger input and fixes it. and it is reliable up to 40MHz.

/*
  Just some helpfull info:
  
  1. in the code it already sets up the LEDC, we should get the timer number and channel off of it.
  2. For ESP32-S3, all timers share one clock source. In other words, it is impossible to use different clock sources for different timers.
  3. since we only need 50% duty, we set the resolution to 1.
  4. the maximum available frequency is 40 MHz with duty resolution of 1 bit. This means that the duty cycle is fixed at 50% and cannot be adjusted.
  5. Number of LEDC channels: ESP32 = 16 - ESP32-S3 or ESP32-S2 = 8
*/

#include <Arduino.h>
#include <stdio.h>
#include "driver/ledc.h"


#define MY_LEDC_PIN     1
#define LEDC_CHANNEL    LEDC_CHANNEL_0
#define LEDC_TIMER      LEDC_TIMER_0
#define LEDC_FREQUENCY  24000000
#define LEDC_RESOLUTION LEDC_TIMER_1_BIT  // Resolution in bits (1-bit PWM)

void setup() {
  Serial.begin(115200);
  delay(500);

  // Configure the LEDC timer
  ledc_timer_config_t ledc_timer =
  {
    .speed_mode = LEDC_LOW_SPEED_MODE,
    .duty_resolution = LEDC_RESOLUTION,
    .timer_num = LEDC_TIMER,
    .freq_hz = LEDC_FREQUENCY,
    .clk_cfg = LEDC_AUTO_CLK
  };
  
  if (ledc_timer_config(&ledc_timer) != ESP_OK)
  {
    Serial.println("LEDC timer configuration failed");
    while (1);  // Halt execution
  }

  // Configure the LEDC channel
  ledc_channel_config_t ledc_channel =
  {
    .gpio_num = MY_LEDC_PIN,
    .speed_mode = LEDC_LOW_SPEED_MODE,
    .channel = LEDC_CHANNEL,
    .intr_type = LEDC_INTR_DISABLE,
    .timer_sel = LEDC_TIMER,
    .duty = 1,  // 50% duty cycle for 1-bit resolution
    .hpoint = 0
  };

  if (ledc_channel_config(&ledc_channel) != ESP_OK)
  {
    Serial.println("LEDC channel configuration failed");
    while (true);  // Halt execution
  }
}

void loop()
{
  delay(500);
}

[josef2600]

just don't forget to remove or disable the driver from camera, since i think you are using the original driver.
so, what is next?

[s60sc]

the 24MHz clock source would need to integrate with the rest of the espressif camera library or would need to be an espressif approved change to the code

[josef2600]

emm, so, do you want to go to espressif IDF or should i fix the library from them for Arduino? and if i do that, will you integrate it to your code or not?
to be clear, am i doing it for myself or are you in? that was why i ask for connecting. if i can, i like to make this project a lot weirder!
where you where stock at work? you came late! missed you!
i got my new board, i am connecting the SD to 4-bit. just for fun, i am using Freenove_ESP32_S3_WROOM_Board.
well, i have been out too many times! many project managers don't really care about their work nor updating. as probably you know it yourself. i suggested for it because i sow you are really active with your members and don't blow them off. most people don't even read what people say. and i do agree many users don't even read the readme, but some do and even new users sometimes do fined interesting errors or functions. i am very bad at github, but some of my ideas are interesting. i do not ask or want to be a contributor or something like that, since i am very bad at it. but what i am, a resilient sob in electronics! and i am into parallel processing.
now, what i can do, besides the low level coding, is to design almost any board you need. if at any time we get to do GOOD stuff, i will design them and can send to you. and if you are not good with soldering the very small parts, there are 2 options: 1. i design with available modules or 2. i make them and send them to you. but i know the first option wont be very good. for example, i read it, but i didn't know how much ov5620 can get hot when working. so, i am thinking about using external 1.5v for vdd core. but the post is with you!
sorry for being a bitch! sometimes i go on an on and write a novel! but i would like to be clear and not mistake anything or cause it.
currently, what i am thinking is for face recognition on 720P with it. i know it cant even do 380P, but dreaming is not a bad thing!
and by the way, why Motion detection is always enable? it cant even be off in browser, and i did save it, but it always say something about the frame is too high for Motion detection with camera. can you please check it?

[s60sc]

I just write these apps as a hobby for my own use and share the code in case anyone else finds it useful. If other people want to contribute working code (eg RTSP is a recent contribution) then I'm happy to add it.

[josef2600]

ohhhhhhhhh shit! that hearts! i just fined out something horrible. i was bashing my head to the wall, since in the board, the V core was 1.2 volt. i was so confused. because the datasheet for OV5640 say the V core has to be 1.5 +-5% . so, how is it possible that the board is giving it 1.2 volt? i searched and found nothing! and suddenly, i thought, they say both cameras can work on a board. so i said is it possible that OV2640 has a different V core? and to my surprise, yes! the V core for OV2640 is indeed 1.2 volt. now, i am wondering, how can OV5640 possibly work with that?
so lets change the voltage for V core. hope i don't burn this one too!

[s60sc]

Cam boards have a 1.2V ldo for OV2640 but not 1.5V for OV5640, so OV5640 dvdd gets 3.3V which it has to regulate to 1.5V which is why it gets hot

[josef2600]

yes and no!
the VDD-D (supply voltage (digital core)) for OV2640 is 1.2 but for OV5640 is 1.5 volt. and the pin that is connected to 1.2 volt is VDD-D. just check the schematic for boards or the pins for the camera. it is from the old design and to be compatible with both.
AND base on the datasheet, when they give the camera 2.8 volt for VDD-A and VDD-IO , you should NOT use the internal regulator and by default, the internal regulator is off. otherwise, it gets so hot that it might burn. but lets try it! its only 10$ +10 days!
4. DVDD is 1.5V±5% of sensor digital power(clean).

For OV5640 camera module, below two kinds of power supplies are recommended:
A. 2 External Power Supplies
 DOVDD = 1.8V, DVDD generated by internal regulator
 AVDD = 2.8V
 Support both Power Down and Power Off mode for power saving.
B. 3 External Power Supplies
 DOVDD = 2.8V
 DVDD = 1.5V
 AVDD = 2.8V
 Use Power Off mode for power saving. Power Down mode is not supported for power
saving.

as you can see, there is no 1.2 volt available for anything.

2.7 power up sequence
If 1.8V is used for I/O power, using
the internal DVDD is preferred. If 2.8V is used for I/O power, due to a high voltage drop at the internal DVDD regulator,
there is a potential heat issue. 

did you check the motion detection camera? why is it always enable?
thanks.

[guece1]

did you check the motion detection camera? why is it always enable? thanks.

I second that question

[s60sc]

need more info, what did you do and what does the log say

[josef2600]

hi, sorry for delay, but had few problems. this is the motion:

[19:46:11.224 showLocalTime] Got current time from browser: 13/01/2025 19:46:11 with tz: GMT0
[19:46:23.915 WARN updateAppStatus] Motion detection disabled as frame size P_FHD is too large 
[19:46:25.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:27.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:29.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:31.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:33.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:35.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:37.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:37.432 updateAppStatus] Disabling motion detection
[19:46:39.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:40.156 savePrefs] Saved preferences
[19:46:40.176 saveConfigVect] Config file saved 
[19:46:41.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:43.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:45.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:47.327 WARN checkMotion] Frame size P_FHD too large for motion detection 
[19:46:49.327 WARN checkMotion] Frame size P_FHD too large for motion detection 

i put the camera to full HD, and Disabling motion detection , as you can see it say it, but it still running. it is bad.

[josef2600]

and i checked the setting for clock. from web page, if i set the clock bellow 20mhz, it still send 20mhz. and if i set it to higher clock, it send a very wrong clock. for example, i set the clock to 24 MHz, but it sends 26.5 MHz . it is weird! i will check it.
hey check my board!






i am really crazy!!!

[josef2600]

i cut the ws LED and the ams1117 should be shorted. the case is not connected to pins. weird!

[s60sc]

Motion detection is disabled but the misleading error message is because the app is unable to decode the image to determine the light level. As per readme the app is not intended for high resolutions. I will modify the error message

[josef2600]

i am getting you high too! thank you for your project and being fast!

[josef2600]

funny, i tested few things. all on HD and 20FPS (trying at least!) , ov5640.
so, if i use only stream i get this:

[05:07:55.555 checkFreeStorage] Storage free space: 29.7GB
[05:09:02.116 showStream] MJPEG: 168 frames, total 18.9MB in 46.5s @ 3.6fps
[05:09:02.505 wsHandler] Websocket connection: 52

but if i only record it, i get this:

[05:07:55.480 closeAvi] ******** AVI recording stats ********
[05:07:55.480 closeAvi] Recorded /20250121/20250121_050726_HD_14_29.avi 
[05:07:55.490 closeAvi] AVI duration: 29 secs
[05:07:55.491 closeAvi] Number of frames: 405
[05:07:55.491 closeAvi] Required FPS: 20
[05:07:55.501 closeAvi] Actual FPS: 14.2
[05:07:55.502 closeAvi] File size: 44.8MB
[05:07:55.502 closeAvi] Average frame length: 115979 bytes
[05:07:55.513 closeAvi] Average frame monitoring time: 40 ms
[05:07:55.513 closeAvi] Average frame buffering time: 0 ms
[05:07:55.523 closeAvi] Average frame storage time: 29 ms
[05:07:55.523 closeAvi] Average SD write speed: 3779 kB/s
[05:07:55.534 closeAvi] File open / completion times: 2 ms / 68 ms
[05:07:55.534 closeAvi] Busy: 100%
[05:07:55.534 checkMemory]  Free: heap 167172, block: 98292, min: 156640, pSRAM 2776276
[05:07:55.544 closeAvi] *************************************

3.6fps ? i have heard there is a big problem in the source code, about LCD. it is always enable and has a big conflict with WIFI.
besides, in HD resolution it only gets 14.2 , but it should be much higher.
in another matter, i did see the effect of camera temperature. if it is under 50 degree, it is great. but if it goes higher than 50, the picture gets noisy. the higher temp, the noisier the picture gets. it is said in the datasheet too, but it only say under 50 for stable , no mention of noise.
also i am trying to turn off the internal regulator. i don't know if i was successful or not yet.