2017-02-17 04:00 AM
Hi,
I recently bought the STM32479I-Eval board and now I'm testing the sample applications included in STM32Cube_FW_F4_V1.14.0
The application 'STM32469I_EVAL\Applications\Camera\Camera_To_USBDisk' does not work as expected, the LCD screen shows the messages:
USB Init...
Camera Init...
and then:
Press TAMPER button to take a snapshot
Camera Play
but only a fully blank image on the LCD. When I press the tamper button to save the image:
Camera stopped...
Picture Prepared...
Saving Picture in File image_x.bmp...
Header BMP written...
BMP data Pixed save ongoing...
the LED1 is on to indicate the end of saving operation and a message is displayed:
File image_x.bmp saved in USB Disk...
but the image that is saved (Attach file) is completely blank.
Should I need to modify the position of some other* jumper or even modify the code of the example to run this application in STM32479I-Eval?
* Note:
JP3 of STM32479I-EVAL board is on position PC0.
USB key into the STM32479I-EVAL board through 'USB micro A-Male to A-Female' cable (connector CN8).
Thanks in advance,
Sergio
#stm32479i-eval #stm32469i-eval #camera #stm32f479xx2017-03-01 12:22 AM
Hi
st.mcu
,Debugging the code I have come to the conclusion that the problem is in the initialization of the camera
/* Initialize the Camera */
BSP_CAMERA_Init(RESOLUTION_R480x272);Inside this function it seems that the camera does not respond to the command
/* Read ID of Camera module via I2C */
if (s5k5cag_ReadID(CAMERA_I2C_ADDRESS) == S5K5CAG_ID){And status return:
/* Return CAMERA_NOT_SUPPORTED status */
status = CAMERA_NOT_SUPPORTED;In the main file the return of the function is not checked, so it seems to be running correctly
Thanks in advance,
Sergio
2017-03-01 01:10 AM
Hi,
I have connected a logic analyzer to the PB8 (SCL) and PB9 (SDA) pins in the CN6 Connector to monitor the I2C that controls the camera and it seems that it is not responding
Thanks in advance,
Sergio
________________ Attachments : LA.png : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HypZ&d=%2Fa%2F0X0000000bDI%2FFZHgjw65JUJ9Fg8j86HGD6.tD3cI0WByfDfMMiFiAuc&asPdf=false2017-03-21 06:56 AM
Finally got the camera working... the problem was in the BSP Driver provided by ST
STM32Cube_FW_F4_V1.15.0\Drivers\BSP\STM32469I_EVAL
2017-03-22 02:47 AM
Hi
Martin.Sergio
,I am curious to know about your findings. If you confirm that this is a bug on the firmware side, so it should be fixed.
From our side, we continued investigation and made some tests which confirm that the module camera is functional.
With same example, I reproduced issue for one of the camera modules that I have (that is why I suggested to replace this module by another one).
Now, as you suspect it is a firmware issue, I would like to know more about it in order to check the fix with other similar modules.
-Amel
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2017-03-22 04:21 AM
Hi,
To operate correctly with the examples used by the camera module I had to reduce the speed of operation of the I2C from 400Khz to 100Khz
Drivers\BSP\STM32469I_EVAL\stm32469i_eval.h
#define I2C_SCL_FREQ_KHZ 100000 // ST: 400000 // /*!< f(I2C_SCL) = 400 kHz */
Reviewing the changes between the different version of STM32Cube_FW I can see that always [STM32469I_EVAL included in version 1.8.0] the define I2C_SCL_FREQ_KHZ is set to 400Khz but in all other boards the I2C_SPEED is set to 100Khz
In the Aplication directory of each Camera App the readme.txt file include:
1.8.0
<<
- This application has been tested with STM32469I-EVAL revB board which includes
the KoD DSI LCD and S5K5CAG camera module.>>
1.15.0
<<
- This application has been tested with STM32469I-EVAL RevC board which includes
the KoD DSI LCD and S5K5CAG camera module.>>
My ST Hardware:
STM32479I-EVAL (MCU STM32F479NI) . The Board serigraphy is STM32469I-EVAL MB1165 Rev.C
Camera module serigraphy is MB1183 Rev.C
Any idea why the camera does not work at 400Khz? Camera problem? PCB problem? or the Camera_To_USBDisk, DCMI_CaptureMode and DCMI_SnapshotMode codes has never been tested with this Evaluation Board?
-Sergio