Skip to content

Simple driver program exposing a file structure for controlling an ESP32-CAM running this firmware: https://github.com/adameus03/uart-cam

Notifications You must be signed in to change notification settings

adameus03/uart_cam_driver

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

How to prepare for using this software and how to interface with the abstraction provided by this driver

  • Create tmpfs filesystem in RAM and mount it under path /custom : $ mount -t tmpfs -o size=16m tmpfs /custom

  • Set appropriate permissions for /custom

  • The driver control files will be present inside the /custom/ucdX driver provided device directory which is created upon running the driver executable for a given serial port and device index (see below)

  • A serial port file has to be provided as an argument to the driver executable, together with a device index, for example $ ucd /dev/ttyUSB0 0 will attach the driver to the serial port /dev/ttyUSB0 and create a driver-provided device directory /custom/ucd0.

  • Writing f to /custom/ucdX/request will request a frame from an ESP32-CAM running the uart-cam firmware. To check if the frame is ready, you can read from /custom/ucdX/state. 1 means ready and 0 means not ready.

  • To perform an OTA update over UART, the driver user writes the new firmware to /custom/ucdX/firmware (for example $ cat /path/to/firmware | tee /custom/ucdX/firmware), then triggers the update by writing u to /custom/ucdX/request.

UPDATE

In the newest version of the program there is an additional paramter - 0 or 1 indicating whether to drain the serial input before handling communications

About

Simple driver program exposing a file structure for controlling an ESP32-CAM running this firmware: https://github.com/adameus03/uart-cam

Resources

Stars

Watchers

Forks

Packages

No packages published