(r3) Esp32-cam < IoT_Course

Tags: view all tags

---+ The ESP32-CAM module
---++ Introduction

The ESP32-CAM module is dedicated to camera readout. It provides
   * an ESP32-S CPU
   * a 2 mega pixel <a href="https://www.uctronics.com/download/OV2640_DS.pdf" target="_blank">OV2640 camera <img alt="" border="0" height="12" src="http://localhost/pub/TWiki/TWikiDocGraphics/external-link.gif" width="13" /></a>and its interface.
   * a very bright LED used as a flashlight connected to GPIO 4
   * a user LED connected to GPIO 33
   * an SD cardholder for SD card with up to 4GBytes capacity
---++ The pinout

<img alt="esp32-cam.png" height="431" src="%ATTACHURL%/esp32-cam.png" title="esp32-cam.png" width="848" />

The interface for the SD card:

| *GPIO* | *SD-card interface* |
| SCK | GPIO 14 |
| MISO | GPIO 2 |
| MOSI | GPIO 15 |
| CS (SS) | GPIO 13 |

---++ Board Variants

The ESP32-CAM comes in a number of variants.
---+++++ <a name="The original ESP32-CAM"></a> The original ESP32-CAM

The original version has no USB connector and can only be controlled with a USB to serial adapter.

<img alt="esp32-cam-standard.png" height="352" src="%ATTACHURL%/esp32-cam-standard.png" title="esp32-cam-standard.png" width="451" />

The connections to the USB to serial adapter are as follows:<br /><br /><br />
| *ESP32-CAM* | *USB to serial* |
| 5V | 5V |
| GND | GND |
| UOR | Tx |
| UOT | Rx |
In order to flash the board, GPIO 0 (marked IO0) must be jumpered to GND and the board must be reset. This sets the ESP32 to flash mode. Once flashing is finished, the jumper must be removed and the board reset. Thereafter, the board can be accessed with the USB to serial connection and a virtual terminal like minicom or gtkterm.
---+++++ The ESP32-CAM-MB

The second variant comes with the ESP32-CAM-MB main board, which provides a micro USB connector.

<img alt="esp32-cam-mb.png" height="364" src="%ATTACHURL%/esp32-cam-mb.png" title="esp32-cam-mb.png" width="445" />

The ESB32-CAM board, to be used with this main board, is slightly modified with respect to the original one:

| <img alt="esp32-cam-gnd.png" height="270" src="%ATTACHURL%/esp32-cam-gnd.png" title="esp32-cam-gnd.png" width="447" /> | <img alt="esp32-cam-gnd-r.png" height="300" src="%ATTACHURL%/esp32-cam-gnd-r.png" title="esp32-cam-gnd-r.png" width="453" /> |
| The original ESP32-CAM | The ESP32-CAM modified to work with the main board |
On the modified ESP32 cam board, the pin marked GND/R (just GND, on the original board) is connected to the ESP32 reset pin on the camera board and to the RTS line of the serial port on the ESP32-CAM-MB board. GPIO 0 is connected to serial DTR. Since the Unix serial driver sets RTS and DTR when connecting, the board is always in flash programming mode.

In order to access REPL you must pull both DTR and RTS low. This can be done with gtkterm, which has buttons to toogle these lines, or you can use rshell with DTR and RTS set to "false":

export RSHELL_RTS="false"<br />export RSHELL_DTR="false"<br /><br />

When trying to run thonny you will hit the same problem. The new version of thonny (I use version 4.0.0-dev) however allows you to disable DTR and RTS in the file<br />$HOME/config/Thonny/configuration.ini. Just add the 2 lines setting DTR and RTS to False at the end of the file.

<img alt="thonny_mods.png" height="121" src="%ATTACHURL%/thonny_mods.png" title="thonny_mods.png" width="708" />
---+++++ The esp32-cam model with the micro USB connector installed

This model works similarly to the original version, but with the micro USB connector and a "flash button" already installed. A simple micro USB cable is needed for communication. In order to set the module to flash mode, hold the flash button while pushing the RST button.

<img alt="esp32-cam-usb.png" height="326" src="http://localhost/pub/UCC_Course_2021/Esp32-cam/esp32-cam-usb.png" title="esp32-cam-usb.png" width="379" />

---++ Testing with esp32-who

The github repository <a href="https://github.com/espressif/esp-who" target="_blank">esp32-who<img alt="" border="0" height="12" src="http://localhost/pub/TWiki/TWikiDocGraphics/external-link.gif" width="13" /></a> provides the esp32-cam driver, as well as a number of example programs. Before trying to integrate the driver into !MicroPython I build the camera_web_server example and check that the hardware works correctly:

First configure the application with

<pre>idf.py menuconfig</pre>

In the Kconfig menu coming up you must
   * specify your !WiFi setup (SSID and password)
   * select the camera type (AI Thinker)
This results in the following GPIO settings:

<img alt="esp32-who.png" height="335" src="%ATTACHURL%/esp32-who.png" title="esp32-who.png" width="363" />

With these settings, we can build the application and flash it to the board.
<pre>idf.py build
idf.py flash</pre>

After successful flashing connect minicom (or rshell in the case of the esp32-cam-mb) to the camera module and reset the machine.
---++ Integration into !MicroPython

Espressif provides an [[https://github.com/espressif/esp32-camera][esp32-camera]] driver, which must be installed in the _components_ folder of esp-idf. I downloaded it to the same level as esp-idf and micrropython and created a symbolic link to it in esp-idf/components. In order to make sure that the correct esp-idf is used for compilation, I wrote a little shell script setting up the correction environment:

<img alt="setupForCamera.png" height="99" src="%ATTACHURL%/setupForCamera.png" title="setupForCamera.png" width="666" />

As you can see, it points to the esp-idf to be used, and it makes sure that the correct idf.py, which is stored in esp-idf/tools, is found in the execution path.
---+++++ Reserving some space in SPIRAM for the image buffer

Standard !MicroPython uses all the SPIRAM for its heap. This results in an error when the esp32 camera driver tries to allocate space in SPIRAM for its image buffer. I therefore modified the !MicroPython sources to keep some free space for the camera driver. Here is the part I modified in main.c. As you can see, 256 kBytes are reserved.

<img alt="esp32-cam_imgbuf.png" height="350" src="%ATTACHURL%/esp32-cam_imgbuf.png" title="esp32-cam_imgbuf.png" width="1017" />

After this modification, you may follow the description in [[https://lemariva.com/blog/2020/06/micropython-support-cameras-m5camera-esp32-cam-etc][https://lemariva.com/blog/2020/06/micropython-support-cameras-m5camera-esp32-cam-etc ]](DIY from Scratch) for the modifications to lv_micropython needed in order to produce an interpreter with the camera driver included.

-- %USERSIG{UliRaich - 2021-10-21}%

---++ Comments

%COMMENT%

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who
png	esp32-cam-gnd-r.png	r1	manage	257.5 K	2021-10-21 - 08:54	UliRaich
png	esp32-cam-gnd.png	r1	manage	147.0 K	2021-10-21 - 08:54	UliRaich
png	esp32-cam-mb.png	r1	manage	163.0 K	2021-10-21 - 09:03	UliRaich
png	esp32-cam-standard.png	r1	manage	227.4 K	2021-10-21 - 08:54	UliRaich
EXT	esp32-cam-usb	r1	manage	124.6 K	2021-10-21 - 08:54	UliRaich
png	esp32-cam-usb.png	r1	manage	246.4 K	2021-10-21 - 08:54	UliRaich
png	esp32-cam.png	r1	manage	358.6 K	2021-10-21 - 08:54	UliRaich
png	esp32-cam_imgbuf.png	r1	manage	70.3 K	2021-11-15 - 20:42	UliRaich
png	esp32-who.png	r1	manage	25.3 K	2021-10-21 - 09:09	UliRaich
png	setupForCamera.png	r1	manage	22.4 K	2021-10-21 - 09:57	UliRaich
png	thonny_mods.png	r1	manage	13.2 K	2021-10-21 - 08:54	UliRaich

Topic revision: r3 - 2021-11-15 - UliRaich