{"id":4726,"date":"2019-06-25T20:13:40","date_gmt":"2019-06-26T03:13:40","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=4726"},"modified":"2019-06-25T20:14:30","modified_gmt":"2019-06-26T03:14:30","slug":"using-the-esp32-camera-interface-from-arduino-projects","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/tutorials\/esp32\/camera\/","title":{"rendered":"Using the ESP32 Camera Interface from Arduino-based Projects"},"content":{"rendered":"

This tutorial shows how to create a basic project for the ESP32-CAM<\/a> module and use the JTAG interface to debug it.<\/p>\n

We will use VisualGDB to clone the ESP32 Arduino Camera example and then modify it to automatically take pictures in a loop and upload them via HTTP to a specified server. Before you begin, ensure you have installed Visual Studio and VisualGDB 5.4.<\/p>\n

Wiring<\/h1>\n

In order to get JTAG debugging to work, we would need to connect the following pins of the ESP32-CAM module to a compatible JTAG debugger (e.g. Olimex ARM-USB-OCD-H or Segger J-Link):<\/p>\n\n\n\n\n\n\n\n\n\n
ESP-CAM Pin<\/td>\nJTAG signal<\/td>\nJTAG20 pin<\/td>\n<\/tr>\n
3.3V<\/td>\n+3.3V<\/td>\n1<\/td>\n<\/tr>\n
GND<\/td>\nGND<\/td>\n4<\/td>\n<\/tr>\n
GPIO12<\/td>\nTDI<\/td>\n5<\/td>\n<\/tr>\n
GPIO14<\/td>\nTMS<\/td>\n7<\/td>\n<\/tr>\n
GPIO13<\/td>\nTCK<\/td>\n9<\/td>\n<\/tr>\n
GPIO15<\/td>\nTDO<\/td>\n13<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

See the picture below for details (courtesy of Seeed Studio):\"\"<\/a>As the ESP32-CAM board does not come with a USB connector, you would need to use an external 5V power source. In this tutorial we will use a Nucleo board from ST Microelectronics as a 5V source and will also use its 3.3V UART interface provided by the on-board ST-Link to receive the text output from the ESP32-CAM module. If you are using the Nucleo board, remove the JP5 jumper (powering the STM32 microcontroler on the board) and connect the GND, +5V and RX signals to the ESP32-CAM module as shown below:\"\"<\/a><\/p>\n

Note that due to the limitations of the ST-Link programmer, you won’t be able to use it to debug the ESP32 device and hence will need a low-level debug probe.<\/p>\n

The final wiring setup used in this tutorial is shown below:\"\"<\/a>Note that the ST Nucleo board is used to provide the 5V signal and the Olimex ARM-USB-OCD-H debugger is used for the actual JTAG debugging.<\/p>\n

Software Setup<\/h1>\n

Now that we are done with the wiring, we can start with the software configuration necessary to debug the ESP32-CAM board. Follow the steps below to create a basic project, step through it and modify it to automatically upload the taken pictures:<\/p>\n

    \n
  1. The best ready-to-use ESP32 camera example is included in the ESP32 Arduino package, so we will use the Arduino workflow in this tutorial. As long as you are using VisualGDB 5.4 or later, it will automatically install the necessary tools and packages for you as you create the project. Hence start Visual Studio and open the VisualGDB Arduino Project Wizard:\"\"<\/a><\/li>\n
  2. As we will be starting with an existing camera example, select “Clone one of the sample sketches from Arduino platform”:\"\"<\/a><\/li>\n
  3. The ESP32 Arduino platform does not have a special target for the ESP32-CAM module, however it is compatible with the ESP32 Wrover module. Simply select it from the list:\"\"<\/a><\/li>\n
  4. If you have not created ESP32 Arduino projects before, click “Install” and VisualGDB will automatically download and install the necessary packages:\"\"<\/a><\/li>\n
  5. In this tutorial we will clone the CameraWebServer sample provided by Espressif, so simply select it from the list:\"\"<\/a><\/li>\n
  6. Connect your JTAG debugger via USB and select it on the Debug Method page. Then click “Test” to verify the wiring:\"\"<\/a><\/li>\n
  7. OpenOCD should confirm that it’s able to communicate to the ESP32 chip:\"\"<\/a>Once the wiring is verified, press “Finish” to create the project.<\/li>\n
  8. Before you can build the project, comment out the CAMERA_MODEL_WROVER_KIT definition and uncomment the CAMERA_MODEL_AI_THINKER line to enable the pinout specific to the board you are using: \"\"<\/a><\/li>\n
  9. If you try building the project now, the Arduino tools will fail stating that the sketch is too big:\"\"<\/a><\/li>\n
  10. This happens because the default partition configuration is too small to fit the camera example. Open VisualGDB Project Properties and change the Partition Scheme to Huge APP:\"\"<\/a>If you have connected the serial output of the ESP32-CAM module to the ST Nucleo board (or another UART-to-USB adapter), select its COM port in the “COM port for uploading the sketch” field. If not, leave the field empty. As ESP32 projects are programmed via JTAG, the COM port is not actually necessary, although it’s useful for viewing the diagnostic output.<\/li>\n
  11. If you have connected the serial port, go to the Arduino Serial Terminal page of VisualGDB Project Properties and check the “Open a raw terminal” checkbox:\"\"<\/a><\/li>\n
  12. Finally, set the ssid<\/strong> and password<\/strong> variables at the beginning of the sketch to match your network configuration. Then press Ctrl-Shift-B to build the project:\"\"<\/a><\/li>\n
  13. Start debugging by pressing F5. VisualGDB will automatically program the FLASH memory and start the program. If you have connected the serial output of the module, you will see the IP address of the camera displayed there:\"\"<\/a>If you are not using a serial port, set a breakpoint inside the WiFiSTAClass::localIP()<\/strong> function before starting the debugger and then evaluate the “ip” expression to check the IP address assigned to the board.<\/li>\n
  14. Go to the IP address of the board in your browser. You will see a basic web interface provided by the Arduino sample that lets you set various parameters and take pictures:\"\"<\/a><\/li>\n
  15. Now we will use the code navigation functions of VisulaGDB and the debugger to understand the components involved in taking the pictures and sending them to the browser. First of all, go to the definition of the startCameraServer()<\/strong> function: \"\"<\/a><\/li>\n
  16. The startCameraServer()<\/strong> function defines several handlers for various pages of the built-in web server. Opening the “\/capture” page results in capturing one frame from the camera and outputting it via HTTP. Select the capture_handler<\/strong> function and click “Go to definition” to view its source: \"\"<\/a><\/li>\n
  17. Set a breakpoint inside the capture_handler()<\/strong> function and try capturing a single frame from the browser. The breakpoint will trigger, allowing you to check the captured frame parameters:\"\"<\/a><\/li>\n
  18. You can use the Memory window to verify that the bb->buf<\/strong> buffer contains a properly encoded JPEG image (see the JFIF signature):\"\"<\/a>From the code of the capture_handler()<\/strong> function we can reconstruct the steps involved in capturing pictures from the camera:\n