115 lines
5.5 KiB
Plaintext
115 lines
5.5 KiB
Plaintext
/**
|
||
@page Camera_To_USBDisk Camera to USB Disk application
|
||
|
||
@verbatim
|
||
******************************************************************************
|
||
* @file Camera/Camera_To_USBDisk/readme.txt
|
||
* @author MCD Application Team
|
||
* @brief Description of the Camera to USB Disk application.
|
||
******************************************************************************
|
||
*
|
||
* @attention
|
||
*
|
||
* Copyright (c) 2017 STMicroelectronics.
|
||
* All rights reserved.
|
||
*
|
||
* This software is licensed under terms that can be found in the LICENSE file
|
||
* in the root directory of this software component.
|
||
* If no LICENSE file comes with this software, it is provided AS-IS.
|
||
*
|
||
******************************************************************************
|
||
@endverbatim
|
||
|
||
@par Application Description
|
||
|
||
This application provides a short description of how to use the DCMI to interface with
|
||
camera module and display in continuous mode the picture on LCD and to save a picture
|
||
in USB device.
|
||
|
||
At the beginning of the main program the HAL_Init() function is called to reset
|
||
all the peripherals, initialize the Flash interface and the systick.
|
||
Then the SystemClock_Config() function is used to configure the system
|
||
clock (SYSCLK) to run at 200 MHz.
|
||
|
||
The Digital camera interface is configured to receive the capture from
|
||
the camera module mounted on STM327x6G_EVAL evaluation board.
|
||
DMA2 Stream1 channel1 is configured to transfer the picture from DCMI peripheral
|
||
to an external RAM used by the LCD as a frame buffer.
|
||
|
||
The camera module is configured to generate (480x272) image resolution
|
||
and the LCD is configured to display (480x272) image resolution
|
||
|
||
When the tamper button is pressed an image is saved under USBdisk.
|
||
- LED1 is on to indicate the end of saving operation and a message is displayed
|
||
on LCD to indicate the beginning and the end of the saving operation.
|
||
- LED2 is ON when any error occurs.
|
||
|
||
@note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)
|
||
based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from
|
||
a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)
|
||
than the peripheral interrupt. Otherwise the caller ISR process will be blocked.
|
||
To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.
|
||
|
||
@note The application needs to ensure that the SysTick time base is always set to 1 millisecond
|
||
to have correct HAL operation.
|
||
|
||
@note The STM32F7xx devices can reach a maximum clock frequency of 216MHz but as this application uses SDRAM,
|
||
the system clock is limited to 200MHz. Indeed proper functioning of the SDRAM is only guaranteed
|
||
at a maximum system clock frequency of 200MHz.
|
||
|
||
|
||
@par Keywords
|
||
|
||
Display, Camera, USB Disk, DCMI, LCD, DMA, Frame buffer, WVGA
|
||
|
||
@Note<74>If the user code size exceeds the DTCM-RAM size or starts from internal cacheable memories (SRAM1 and SRAM2),that is shared between several processors,
|
||
<20><><EFBFBD><EFBFBD><EFBFBD>then it is highly recommended to enable the CPU cache and maintain its coherence at application level.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>The address and the size of cacheable buffers (shared between CPU and other masters) must be properly updated to be aligned to cache line size (32 bytes).
|
||
|
||
@Note It is recommended to enable the cache and maintain its coherence, but depending on the use case
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD> It is also possible to configure the MPU as "Write through", to guarantee the write access coherence.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>In that case, the MPU must be configured as Cacheable/Bufferable/Not Shareable.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Even though the user must manage the cache coherence for read accesses.
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Please refer to the AN4838 <20>Managing memory protection unit (MPU) in STM32 MCUs<55>
|
||
<EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Please refer to the AN4839 <20>Level 1 cache on STM32F7 Series<65>
|
||
|
||
@par Directory contents
|
||
|
||
- Camera/Camera_To_USBDisk/Inc/stm32f7xx_hal_conf.h HAL configuration file
|
||
- Camera/Camera_To_USBDisk/Inc/main.h Main program header file
|
||
- Camera/Camera_To_USBDisk/Inc/stm32f7xx_it.h Interrupt handlers header file
|
||
- Camera/Camera_To_USBDisk/Inc/ffconf.h FAT file system module configuration file
|
||
- Camera/Camera_To_USBDisk/Inc/usbh_conf.h Header for usbh_conf.c
|
||
- Camera/Camera_To_USBDisk/Inc/usbh_diskio.h Header for usbh_diskio.c
|
||
- Camera/Camera_To_USBDisk/Src/main.c Main program
|
||
- Camera/Camera_To_USBDisk/Src/stm32f7xx_it.c Interrupt handlers
|
||
- Camera/Camera_To_USBDisk/Src/system_stm32f7xx.c STM32F7xx system clock configuration file
|
||
- Camera/Camera_To_USBDisk/Src/usbh_conf.c USB configuration file.
|
||
- Camera/Camera_To_USBDisk/Src/usbh_diskio.c USB host diskio file
|
||
|
||
|
||
@par Hardware and Software environment
|
||
|
||
- This application runs on STM32F756xx/STM32F746xx devices.
|
||
|
||
- This application has been tested with STM327x6G-EVAL board which includes
|
||
the AMPIRE480272 LCD and S5K5CAG camera module.
|
||
|
||
- STM327x6G-EVAL Set-up
|
||
- Plug the USB key into the STM327x6G-EVAL board through 'USB micro A-Male
|
||
to A-Female' cable (HS mode: connector CN8).
|
||
- Ensure that JP23 is in position 1-2 (CAMERA)
|
||
- Ensure that JP24 is in position 2-3 to use LED1.
|
||
|
||
|
||
@par How to use it ?
|
||
|
||
In order to make the program work, you must do the following :
|
||
- Open your preferred toolchain
|
||
- Rebuild all files and load your image into target memory
|
||
- Run the application
|
||
|
||
|
||
*/
|
||
|