libcamera_sama5d27_som1_ek1.X

Defining the Architecture

This application demonstrates the use of ISC and LCDC peripherals. The camera module used in this application is ov5640 or ov2640 and PDA TM5000 LCD display. This application capture raw video frames from ov5640 or ov2640 camera module using parallel interface and display the captured frames on the TM5000 display using SAMA5D27-SOM1-EK1 target board.

Demonstration Features

• Reference application for the SAMA5D27-SOM1-EK1 development Board
• Image Sensor Controller (ISC) driver
• Time system service, RTT peripheral library and driver
• Graphics Acceleration using integrated display controller (LCDC)
• I2C and Image sensor driver

Creating the Project Graph

The Project Graph diagram shows the Harmony components that are included in this application. Lines between components are drawn to satisfy components that depend on a capability that another component provides.

The I2C driver in this project is used for communication with the image sensor.

The pins are configured as follows through the MCC Pin Configuration tool:

Clock Configuration

The peripheral clocks need to be turned on for “UART1” “TWIHS1”, “ISC”, “LCDC”, “PIO” and “TC0”.

The ISC clock need to be Enabled.

Interrupts Configuration

Interrupts Configuration ————————– The interrupts should be enabled in the “Interrupt for

• Enable 30 – Two Wire Interface 1
• Enable 35 – TC(0, 1, 2)
• Enable 41 – USB High Speed
• Enable 45 – LCD Controller
• Enable 46 – Camera Inerface
• Enable 68 – Parallel IO Controller

Note: The ov2640 or ov5640 image sensor is an off-the-shelf module and is not officially supported by MPLAB Harmony 3. While a driver for this module is included as part of this demo, it is not guaranteed to be complete. Nor are the ov2640 or ov5640 configuration values guaranteed to be optimal. The primary purpose of this application is to demonstrate the functionality of the Image Sensor Controller (ISC) on the SSAMA5D27-SOM1-EK1 board.

Project Configurations

MPU32”s do not have an internal flash memory to boot from. Hence the boot process for these mpu’s is different than for flash based MCUs. The boot process is described in detail in the device datasheets, but the general flow is as follows:

1. On power-up the device executes the first stage bootloader from internal ROM. This looks for an second stage bootloader on external non-volatile memory such as eMMC, SD, NAND flash, NOR-SPI and QSPI as second stage boot devices. For SD and eMMC, ROM bootloader expects a file named “boot.bin” to reside in the root directory of a FAT file system.
2. The second stage bootloader is copied to on-chip SRAM and executed. The second stage boot loader initialize the external DRAM and its controller, then load other program from external non-volatile memory into DRAM and execute it. The second stage bootloader must be configured for the board in use and for the external NVM containing the application. A comprehensive description of the boot process for the Microchip MPU’s can be found in this application note: https://ww1.microchip.com/downloads/en/AppNotes/AN2791-Booting-from-External-Non-Volatile-Memory-on-SAMA5D2-MPU-Application-Note-DS00002791A.pdf
3. The vision application is linked to run/debug on the external DRAM. During a debug process, MPLAB X will first run (load) the at91bootstrap program and this file can be found in the .X folder whose function is to initialize the chip, its clocks, debug port to view log messages and initialize the external DRAM.

Below are Project configuration steps to Debug or Run Vision application. On the MPLAB X IDE, right click on the project and click “Properties”.

1. In “Connected Hardware Tool”, select JLink or J-Tag, and in “Compiler Toolchain”, select XC32 and click apply.
2. Under Categories, click on “Bootstrap”, ensure that “Use bootstrap” is checked and the path to the bootstrap.elf file is set.
3. The harmony.bin should be generated as a post-build command. Under Categories, click on “Building”, ensure that “Execute this line after build” is checked and set “${MP_CC_DIR}/xc32-objcopy -O binary ${DISTDIR}\/${PROJECTNAME}.${IMAGE_TYPE}.elf ${DISTDIR}\/harmony.bin”

Building the Application

The parent directory for this application is in vision/apps/ibcamera_display. To build this application, use MPLAB X IDE to open the vision/apps/libcamera_display/firmware/libcamera_sama5d27_som1_ek1.X project and press F11.

If the build is successfull, then a harmony.bin file is generate in vision/apps/libcamera_display/firmware/libcamera_sama5d27_som1_ek1.X/dist/isc_sama5d27_som1_ek1_tm5000/production folder.

The following table lists configuration properties:

Prebuilt binaries

Latest release prebuilt binaries are available for a SAMA5D27-SOM1-EK1 board is here

Configuring the Hardware

Configure the hardware as follows:

• The OV5640 or OV2640 camera module is wired to the ISC header (J27) on the SAMA5D27-SOM1-EK1 board using the following wiring diagram:

Note: For 8-bit image sensor data D[7:0] is aligned to ISC_D[4:11]. For 10-bit image sensor data D[9:0] is aligned to ISC_D[2:11]. For 12-bit image sensor data D[11:0] is aligned to ISC_D[0:11].

• Connect the ribbon cable from the display to the LCD connector on the SAMA5D27-SOM1-EK1 board.

• Take an SD Card formatted with the FAT32 file system and copy the boot.bin binary file from vision/apps/libcamera_display/firmware/libcamera_sama5d27_som1_ek1.X/bootstrap/som1_ek1 folder. and copy the harmony.bin file generated from the “Building the Application” section.

• Insert the SD card to J12 of the SAMA5D27-SOM1-EK1 board and power up the board by connecting a powered USB cable to either J17 or J10 USB port on the SSAMA5D27-SOM1-EK1 board.

• optionally you can capture debug messages on serial console such as teraterm or Putty on host machine by connecting an USB cable to J10 port on the SSAMA5D27-SOM1-EK1 board.

Running the Demonstration

The LCD should display a Live camera feed on successful power-on. See reference image.

---

---