This is a quick getting started guide for the Freenove ESP32-Wrover CAM board. This board features an OV2640 camera, several GPIOs to connect peripherals, and a built-in programmer with a USB connector, which makes it easy to upload code to the board. We’ll take a quick look at the board and show you some examples of how to program it using the Arduino core for the ESP32.
For detailed overview of the Freenove ESP32-Wrover CAM features, check this post: Freenove ESP32-Wrover CAM Board: Overview and Pinout
Where to Buy?
You can go to the following link to check the camera in different stores:
Introducing the Freenove ESP32-Wrover CAM Board
The Freenove ESP32-Wrover CAM board is an ESP32 development board with the ESP32-Wrover-E chip (with 4 MB PSRAM) and an OV2640 camera.
It has a USB-to-UART converter so it’s straightforward to upload code to the board. You just need to
connect a USB cable to the board and connect it to your computer to upload code or apply power. There’s no need for extra circuitry or an FTDI programmer (contrary to the ESP32-CAM AI-Thinker board).
It comes with several exposed GPIOs if you want to connect other peripherals like sensors and outputs (many more GPIOs than the ESP32-CAM AI-Thinker). Additionally, if you’re not using the camera, you can use it as a regular ESP32 with a wide number of available GPIOs. The GPIOs with a slash above the numbers are the ones used by the camera.
There are RESET and BOOT buttons, which makes it easy to reset the board or put it in flashing mode if needed.
There are four onboard LEDs:
- ON: when lit, it means the board is being powered on.
- RX/TX: will blink when you’re using serial communication.
- IO2: it’s a built-in LED connected to GPIO 2—useful for debugging purposes.
This board is very practical, the only downside is that it doesn’t come with a microSD card slot. However, it comes with available GPIOs that you can use to connect an external microSD card module if needed.
Freenove ESP32-Wrover CAM Board Features
Here’s a summary of the Freenove ESP32-Wrover CAM board features:
- ESP32-Wrover-E Chip with 4MB PSRAM
- Built-in USB-to-UART (CH340C drivers) — no need for an FTDI programmer
- Camera OV2640 2 Megapixel
- BOOT and RST buttons
- LED indicators (RX/TX ON/OFF, and built-in LED (GPIO2))
- Onboard antenna
Freenove ESP32-Wrover CAM Board Pinout
The following diagram shows the pinout for the ESP32-Wrover CAM board. You can click on the image to see it in full-size.
There are labels indicating the features of each pin. You can clearly see which pins are being used by the camera, the power pins, PWM pins, ADC pins, etc.
Freenove ESP32-Wrover CAM Board – Camera Pin Definition
Here’s a table with the connections between the ESP32 and the camera:
| OV2640 Camera | ESP32 |
| XCLK | GPIO 21 |
| SIOD | GPIO 26 |
| SIOC | GPIO 27 |
| Y9 | GPIO 35 |
| Y8 | GPIO 34 |
| Y7 | GPIO 39 |
| Y6 | GPIO 36 |
| Y5 | GPIO 19 |
| Y4 | GPIO 18 |
| Y3 | GPIO 5 |
| Y2 | GPIO 4 |
| VSYNC | GPIO 25 |
| HREF | GPIO 23 |
| PCLK | GPIO 22 |
Note that when you’re using the camera, you can’t connect peripherals to the GPIOs used by the camera. Otherwise, the camera won’t work properly. When you’re not using the camera, you can use this ESP32 board as a “regular” ESP32 and you can use the camera pins for other purposes.
The pin definition for the ESP32-Wrover CAM board (Freenove brand) in your Arduino sketches should be as follows (in some of the Arduino examples, this pin definition is under the CAMERA_MODEL_WROVER_KIT definition).
#define PWDN_GPIO_NUM -1
#define RESET_GPIO_NUM -1
#define XCLK_GPIO_NUM 21
#define SIOD_GPIO_NUM 26
#define SIOC_GPIO_NUM 27
#define Y9_GPIO_NUM 35
#define Y8_GPIO_NUM 34
#define Y7_GPIO_NUM 39
#define Y6_GPIO_NUM 36
#define Y5_GPIO_NUM 19
#define Y4_GPIO_NUM 18
#define Y3_GPIO_NUM 5
#define Y2_GPIO_NUM 4
#define VSYNC_GPIO_NUM 25
#define HREF_GPIO_NUM 23
#define PCLK_GPIO_NUM 22Because this board uses the same camera used in the ESP32-CAM board, the examples for the ESP32-CAM (that don’t use microSD card) should also work with the Freenove ESP32 Camera board by changing the pin definition. The examples that use a microSD card, should also be compatible if using an external microSD card module and adjusting the pin definition on the code.
Freenove ESP32-Wrover CAM vs ESP32-CAM Ai-Thinker
Which one is better? The ESP32-CAM AI-Thinker of the Freenove ESP32-Wrover Cam? It will depend on your project requirements, let’s compare those boards.
Both the ESP32-CAM Ai-Thinker and the Freenove ESP32 Camera come with an ESP32 chip. The AI-Thinker boards usually come with the ESP32-S chip, and the Freenove brand comes with the ESP32-Wrover-E. Both chips are similar in terms of performance.
They both have the same camera model, an OV2640 camera. This means that most projects for the ESP32 Ai-Thinker will also work with the Freenove board and vice-versa by just changing the pin assignment in the code.
The ESP32-CAM Ai-Thinker comes with a built-in microSD card slot, while the Freenove doesn’t. The Freenove comes with more accessible GPIOs than the Ai-Thinker, including GPIOs being used by the camera. This means that when you’re not using the camera, you have more GPIOs to use, almost as in a regular ESP32 board. If you intend to use a microSD card in your projects, maybe the ESP32-CAM is a better idea. However, you can easily connect a microSD card module to the Freenove because it comes with several available GPIOs.
The Freenove comes with BOOT, and RESET buttons, while most ESP32-CAM Ai-Thinker boards only come with RESET button.
The Freenove comes with built-in indicator LEDs, and the Ai-Tinker doesn’t. This makes me think that the ESP32-CAM Ai-Thinker is better in terms of power consumption, even though I haven’t tested it.
The Freenove comes with a built-in USB to TTL converter, which means you can easily upload code to the board and provide power through the USB socket. The AI-Thinker board doesn’t come with this feature, which is a big drawback when you’re experimenting with code and debugging—uploading code can become a tedious task.
The Freenove comes with an onboard antenna, while the Ai-Tinker is available with an onboard antenna and with the possibility to connect an external antenna to increase the wi-fi range.
For a better comparison between the ESP32-CAM AI-Thinker and the Freenove ESP32-Wrover CAM, check the table below.
| Freenove ESP32-Wrover CAM | ESP32-CAM AI-Thinker | |
 |  | |
| Chip | ESP32-Wrover-E | ESP32-S |
| PSRAM | 4MB | 4MB |
| Exposed GPIOs | 30 | 6 |
| Built-in programmer | ✓ | x |
| Antenna | Onboard | Onboard and external |
| Indicator LEDs | ✓ | x |
| Where to buy? | Check best price | Check best price |
Programming the ESP32-Wrover CAM board with Arduino IDE
In this getting started guide, we’ll show you a quick example to demonstrate how to program your board using Arduino IDE. Before proceeding, you must have Arduino IDE installed on your computer, as well as the ESP32 add-on for the Arduino IDE.
We recommend following the next tutorial to install the Arduino IDE and add support for the ESP32 boards if you haven’t already:
Freenove ESP32-Wrover CAM Video Streaming Web Server Example
In this section, we’ll upload an example that creates a video streaming web server that you can access on your local network.
In the Arduino IDE, go to Tools > Board > ESP32 Arduino, and then select ESP32 Wrover Module.
Go to File > Examples > ESP32 > Camera and open the CameraWebServer example.
Make sure you select the right board on the code (remove the // on the CAMERA_MODEL_WROVER_KIT and make sure all the other board selections have //), as shown below:
// ===================
// Select camera model
// ===================
#define CAMERA_MODEL_WROVER_KIT // Has PSRAM
//#define CAMERA_MODEL_ESP_EYE // Has PSRAM
//#define CAMERA_MODEL_ESP32S3_EYE // Has PSRAM
//#define CAMERA_MODEL_M5STACK_PSRAM // Has PSRAM
//#define CAMERA_MODEL_M5STACK_V2_PSRAM // M5Camera version B Has PSRAM
//#define CAMERA_MODEL_M5STACK_WIDE // Has PSRAM
//#define CAMERA_MODEL_M5STACK_ESP32CAM // No PSRAM
//#define CAMERA_MODEL_M5STACK_UNITCAM // No PSRAM
//#define CAMERA_MODEL_AI_THINKER // Has PSRAM
//#define CAMERA_MODEL_TTGO_T_JOURNAL // No PSRAM
// ** Espressif Internal Boards **
//#define CAMERA_MODEL_ESP32_CAM_BOARD
//#define CAMERA_MODEL_ESP32S2_CAM_BOARD
//#define CAMERA_MODEL_ESP32S3_CAM_LCDThen, scroll down the code a bit and insert your network credentials on the ssid and password variables so that the board can connect to your network.
const char* ssid = "REPLACE_WITH_YOUR_SSID";
const char* password = "REPLACE_WITH_YOUR_PASSWORD";After selecting the right board and inserting your network credentials, you can upload the code to the board.
Upload Code to the Freenove ESP32-Wrover CAM Board
Uploading code to the Freenove ESP32-Wrover CAM is straightforward, there’s no need for extra circuitry or an FTDI programmer. You just need to connect a USB cable (with data wires—USB cables that are charge-only won’t work to upload code) to the board USB connector and connect it to your computer.
Then, in the Arduino IDE, go to Tools > Port and select the COM port it is connected to.
Don’t see the COM port, or it is greyed out? It means you might not have the required drivers installed. This specific board uses the CH340 drivers. So, do a quick search to install those drivers on your operating system. After installing the drivers, try to upload the code again.
Then, you need to select a board model in the Tools menu.
Select the following settings:
- Board: ESP32 Wrover Module
- Partition Scheme: Huge APP (3MB No OTA) (or different, depending on your project requirements).
Finally, you just need to click the upload button.
After a few seconds, the code should be successfully uploaded to the board.
Demonstration
After uploading the code, open the Arduino IDE Serial Monitor at a baud rate of 115200.
Press the board RST button. The ESP32 IP address will be printed on the Serial Monitor.
Open a browser on your local network, and type the ESP32 IP address. In my case:
http://192.168.1.142
You should get access to a page where you can start video streaming and get pictures from the camera.
Press the Start Streaming button to start video streaming or the Get Still button to take photos.
There are also several menus that you can play with to adjust the camera settings.
For higher resolutions, the picture is pretty good. However, video streaming in higher resolutions with this board is a bit slow if you’re not right next to the router.
Currently, this example doesn’t have face recognition enabled for this board, but face detection works for CIF or lower resolutions.
Wrapping Up
This tutorial was a quick introduction to the Freenove ESP32-Wrover CAM board. Depending on your project requirements, this can be a good alternative to the most popular ESP32-CAM AI-Thinker.
We have other projects that you can try with the Freenove ESP32-Wrover CAM board. The following tutorials are compatible, just make sure you adjust the pin assignment in the code:
- ESP32-CAM Remote Controlled Car Robot Web Server
- ESP32-CAM Save Picture in Firebase Storage
- ESP32-CAM Pan and Tilt Video Streaming Web Server (2 Axis)
- Telegram: ESP32-CAM Take and Send Photo (Arduino IDE)
- ESP32-CAM: Take and Send Photos via Email using an SMTP Server
If you want to learn more about the ESP32-CAM, check out our resources:
We hope you found this tutorial useful.
Thanks for reading.
Great content, great resource as always. I minor note there is an error in your board comparison table, the board photos are reversed.
Unrelated but I would be interested if you do more on ESP32 using BLE, for example how to connect to a radar module like the Hi-Link LD2410B or C? Found only info on this for ESPHome/Python. Thanks
I have an “original” Freenove ESP32-Wrover CAM board” and it works perfectly with Micropython. I have 2 fake ” ESP32-Wrover CAM board” I bought from AliExpress( who refused a refund) and do not work. Anyone knows the setting for the AliExpress fakes?
Hi.
What’s exactly the issue with the fake clones?
Regards,
Sraa
” ESP32-Wrover CAM board” I bought from AliExpress – Stabilizers 1.2v and 2.8v are mixed in places, everything works perfectly when resoldered
Reply
yup, a just test now esp32 wrover clone work normal.
thanks you and a love youuu.
How did you manage that?
Which MicroPython do you use? Can you stream using MP or “just” capture still images?
Hello, i got some fake too, you need to inverse the transistors on the back( 54fi <=> 65bx).
Bisous
Thank you very much. You made my life easier and helped solve the problem.
Hello,
On my board 54FK is the nearest of the USB plug, should I invert with 65bx ?
Thanks
” ESP32-Wrover CAM board” I bought from AliExpress – Stabilizers 1.2v and 2.8v are mixed in places, everything works perfectly when resoldered
I get this error message when compiling… HELP…
Sketch uses 1495649 bytes (114%) of program storage space. Maximum is 1310720 bytes.
Global variables use 71360 bytes (21%) of dynamic memory, leaving 256320 bytes for local variables. Maximum is 327680 bytes.
Sketch too big; see https://support.arduino.cc/hc/en-us/articles/360013825179 for tips on reducing it.
text section exceeds available space in board
Compilation error: text section exceeds available space in board
Hi.
Are you using this settings: https://i0.wp.com/randomnerdtutorials.com/wp-content/uploads/2023/01/upload-settings-arduino-ide-freenove.png
Regards,
Sara
Thank you very much Sara.
I had not set the partition scheme. I would never have gotten that one without your help.
Over a year later but this saved me banging rocks together. Thanks!
I get the same error
How about the Flash-LED ?
It doesn’t have one.
How about the Flash-Led? How big is the flash-memory?
Hi, is there any other example of cam usage a part from the CameraWebServer.ino ? I would like to use the camera to take still picture and send them to some FTP or an HTTP endpoint (POST). thanks a lot !
Hi sara
I get this error message in serial monitor
I changed the cable and the USB port
[E][camera.c:1113] camera_probe(): Detected camera not supported.
[E][camera.c:1379] esp_camera_init(): Camera probe failed with error 0x20004
I need help pleas.
Hi.
What camera board are you using?
Are you sure it’s the same one we’re using in this tutorial?
Regard,s
Sara
yes it’s the same one
I have same issue with two of five boards. Other 3 boards works fine. Ov2640 cameras are ok.
I have the same problem. Some weeks ago it was working but now without changing anything appeared that error. Has someone solved it?
i used Freenove ESP32-Wrover-dev cam bord
I have the same problem bro
have you found any solution plz?
Is it possible to use the camera-gpios while the camera is connected but not >actively< in use?
E.g. if I were to use the camera for single pictures only and not video capture – could I use the gpios for sensors and stuff “between the frames”? I intend to only take a few photos per day.
I apologise if this is a stupid question to ask – I’m pretty new to esp32 / arduino and currently still exploring and planning a project.
Thanks in advance and best regards!
Andrew
Hi.
that’s a great question.
In theory that is possible. I never tried it, but it should work. But you really need to try it to make sure.
Regards,
Sara
Hi Sara,
thank you very much for the quick reply! My freenove esp cams are still on their way to me, so it will be a while until I get to try it out.
But I will make sure to post an update here to contribute something to the great community.
Regards,
Andrew
That’s great.
Thank you.
As Sara says, theoreticaly you can. But be aware that the camera components are always connected to the Gpio’s and tey are not always tolerant to “external” signals/voltages, and they can influence your “extra” connected input/output signals (they are connected in parallel that way).
Thanks very much JPe!
I will try it out and keep you updated. Maybe the camera specifications give some insight about pins that might be more tolerable. (Like pins that not only send data to the esp but also receive signals under certain circumstances.)
Or do you think one might use a cable extension module to get the actual pins exposed and then use diodes to protect the camera from incoming current?
Regards,
Andrew
Never tried something like that, I think it is wiser to use a Port-Expander when you need more I/O pins. Have a look at:
http://www.esp32learning.com/code/esp32-and-pcf8575-i-o-expander-example.php
Yes, thanks! For an actual use-case I would/will use an port-expander. I am just curious about the functional principle.
Hi sara,
After opening the browser to take me to the page to start streaming, while i can get photos on the camera by selecting the get still button, when i click start streaming nothing happens, i just get a black screen. Any idea of why this is and how to get it working?
Thanks
The picture can can be very small on your display, have a look in the left/upper corner and there zoom in.
I keep getting error message esp_core_dump_flash: No core dump partition found! in the serial monitor can anyone help
Hi.
What board did you select in Tools > Board?
Regards,
Sara
this is a warning and you can ignore it.
Yes went through all the steps several times and the same error comes up
ESP32 WROVER BORD
Hi.
Try the following settings in the Tools menu.
Flash mode “DIO”. Partition Scheme “Huge APP (3Mb…)
Regards,
Sara
Hi, I followed the instructions, all clear and well written.
The Esp32-Wrover is right next to the router. I tried powering the device from the laptop USB and from a 2amp power pack.
Unfortunately, the snap shots (QVGA(320×24) take about 2-5 seconds after the onboard led flash shows its received the request.
Streaming is pretty impossible.
Could it be that I need the antenna, or a manufacture fault?
Found a solution.
Placed an insulator between the camera cable and earthing screen of the chipset, and a ground ane and the video works fine.
Could have been a dogy cable
Hello!
Great tutorial, but I have an issue.
After the code is uploaded (default camera web server), after I press the RST button, ESP WROVER keeps reseting like this:
22:35:38.934 ->
22:35:38.934 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
22:35:38.934 -> configsip: 0, SPIWP:0xee
22:35:38.934 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
22:35:38.934 -> mode:DOUT, clock div:1
22:35:38.934 -> load:0x3fff0030,len:1184
22:35:38.934 -> load:0x5557d555,len:1431664629
22:35:38.980 -> 1150 mmu set 00010000, pos 00010000
22:35:38.980 -> 1150 mmu set 00020000, pos 00020000
22:35:39.014 -> 1150 mmu set 00030000, pos 00030000
22:35:39.048 -> 1150 mmu set 00040000, pos 00040000
22:35:39.048 -> 1150 mmu set 00050000, pos 00050000
22:35:39.083 -> 1150 mmu set 00060000, pos 00060000
22:35:39.115 -> 1150 mmu set 00070000, pos 00070000
22:35:39.151 -> 1150 mmu set 00080000, pos 00080000
22:35:39.151 -> 1150 mmu set 00090000, pos 00090000
22:35:39.187 -> 1150 mmu set 000a0000, pos 000a0000
22:35:39.221 -> 1150 mmu set 000b0000, pos 000b0000
22:35:39.221 -> 1150 mmu set 000c0000, pos 000c0000
22:35:39.267 -> 1150 mmu set 000d0000, pos 000d0000
22:35:39.313 -> 1150 mmu set 000e0000, pos 000e0000
22:35:39.313 -> ets Jul 29 2019 12:21:46
22:35:39.313 ->
22:35:39.313 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
22:35:39.313 -> configsip: 0, SPIWP:0xee
22:35:39.313 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
22:35:39.313 -> mode:DOUT, clock div:1
22:35:39.313 -> load:0x3fff0030,len:1184
22:35:39.313 -> load:0x5557d555,len:1431664629
22:35:39.351 -> 1150 mmu set 00010000, pos 00010000
22:35:39.400 -> 1150 mmu set 00020000, pos 00020000
22:35:39.400 -> 1150 mmu set 00030000, pos 00030000
22:35:39.445 -> 1150 mmu set 00040000, pos 00040000
22:35:39.445 -> 1150 mmu set 00050000, pos 00050000
22:35:39.491 -> 1150 mmu set 00060000, pos 00060000
22:35:39.491 -> 1150 mmu set 00070000, pos 00070000
22:35:39.538 -> 1150 mmu set 00080000, pos 00080000
22:35:39.538 -> 1150 mmu set 00090000, pos 00090000
22:35:39.580 -> 1150 mmu set 000a0000, pos 000a0000
22:35:39.580 -> 1150 mmu set 000b0000, pos 000b0000
22:35:39.616 -> 1150 mmu set 000c0000, pos 000c0000
22:35:39.663 -> 1150 mmu set 000d0000, pos 000d0000
22:35:39.663 -> 1150 mmu set 000e0000, pos 000e0000
22:35:39.716 -> ets Jul 29 2019 12:21:46
22:35:39.716 ->
22:35:39.716 -> rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
22:35:39.716 -> configsip: 0, SPIWP:0xee
22:35:39.716 -> clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
22:35:39.716 -> mode:DOUT, clock div:1
22:35:39.716 -> load:0x3fff0030,len:1184
22:35:39.716 -> load:0x5557d555,len:1431664629
22:35:39.716 -> 1150 mmu set 00010000, pos 00010000
22:35:39.764 -> 1150 mmu set 00020000, pos 00020000
22:35:39.764 -> 1150 mmu set 00030000, pos 00030000
22:35:39.798 -> 1150 mmu set 00040000, pos 00040000
22:35:39.851 -> 1150 mmu set 00050000, pos 00050000
22:35:39.851 -> 1150 mmu set 00060000, pos 00060000
And so on…
What should I do in this situation?
Hi.
What board did you select in Tools > Board?
Are you using the Freenove pins in that code you’re using?
Regards,
Sara
Hello Roman,
I’m having an experience with errors on the card like yours. I can’t get any sketches to work. Did you solve the problem?
SOLVED: look at the bottom
E (493) esp_core_dump_fl�.Kr��core dump partition found!
E (493) esp_core_dump_flash: No core dump partition found!
E (496) sccb: SCCB_Write Failed addr:0x30, reg:0x3e, data:0x00, ret:263
E (497) camera: Camera probe failed with error 0xffffffff(ESP_FAIL)
Camera init failed with error 0xffffffff
I have this errer i use camera OV2640
I am getting the following error.
camera type: OV2640
board : ESPRESSIF ESP32
WiFi connected
Camera Ready! Use ‘http://192.168.1.176’ to connect
E (7116) ledc: ledc_set_duty(720): LEDC is not initialized
E (7116) ledc: ledc_update_duty(648): LEDC is not initialized
E (15678) ledc: ledc_set_duty(720): LEDC is not initialized
E (15678) ledc: ledc_update_duty(648): LEDC is not initialized
E (103063) ledc: ledc_set_duty(720): LEDC is not initialized
E (103063) ledc: ledc_update_duty(648): LEDC is not initialized
E (108679) ledc: ledc_set_duty(720): LEDC is not initialized
E (108679) ledc: ledc_update_duty(648): LEDC is not initialized
Hi Sara, I have an esp32 card as in the article, but without the FREENOVE logo.
I’ve followed the instructions and double-checked each step several times, but I always get a bunch of errors (below). Anyone have any ideas? I tried to load a simple sketch like SCANWIFI but I always get similar errors.
Maybe I’m doing something wrong in the upload procedure?
Thank you
rst:0x7 (TG0WDT_SYS_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:1344
load:0x40078000,len:13960
load:0x00008134,len:0
csum err:0x7f!=0x00
ets_main.c 384
ets Jul 29 2019 12:21:46
entry 0x400805f0
ets Jul 29 2019 12:21:46
rst:0x3 (SW_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:1344
load:0x40078000,len:9864
load:0x88507700,len:2146336
1150 mmu set 00010000, pos 00010000
1150 mmu set 00020000, pos 00020000
…..
rst:0x10 (RTCWDT_RTC_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:1344
load:0x40078000,len:13964
load:0x40080400,len:3600
entry 0x400805f0
ets Jul 29 2019 12:21:46
SOLVED:
My card is not freenove and any sketch I tried to install always gave the same error. Made the following changes:
Tools -> Erase all flash before upload [select: enabled]
Tools -> flash mode [select: DIO]
It works now but I’ll tell you more: after having done only one installation with new settings I put the parameters back as in “original”:
Tools -> Erase all flash before upload [select: disabled]
Tools -> flash mode [select: QIO]
Now the card works always. I can install any sketch without any more errors.
It probably comes from the factory in a certain condition but I don’t know why.
Thanks for sharing that solution.
Regards,
Sara
Does anyone know the prefe
rences settings for Additional Boards Manager URLs mine doesnt seem to pick up the correct one for esp 32
I have these set
http://arduino.esp8266.com/stable/package_esp8266com_index.json
https://github.com/espressif/arduino-esp32/package.json
This setting is for a particular development board for RF tramsmissions and is correct
https://rfzero.net/packages/package_rfzero_release_index.json
Can anyone help for esp32 wrover cam
Mike
Hi Sara,
I have followed your tutorial and it worked on my “Freenove esp32 wrover”.
in the end I can stream on a local website.
The problem is: I can not see the ‘face detection/recoginition’ works.
I was using the same resolution “QVGA(320X240)” as you and have tried even smaller format.
with “Face Detection” and “Face Recognition” enabled, cliking “Enroll Face” doesn’t show the block on the face neither in the video, or on the still picture.
is there a missing configuration?
Hi.
Please read the demonstration section:
“Currently, this example doesn’t have face recognition enabled for this board, but face detection works for CIF or lower resolutions.”
Regards,
Sara
I did everything got the IP address but when i enter it into google, it says site cant be reached. the device is connected to same network, it pinged the IP address and it sees it. Why cant page be reached.