Skip to main content
Martin.Sergio
Martin.Sergio
Associate III
February 17, 2017
Question

STM32479I-EVAL Camara to USB Aplication

  • February 17, 2017
  • 14 replies
  • 2880 views
Posted on February 17, 2017 at 13:00

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 #stm32f479xx
This topic has been closed for replies.

14 replies

Martin.Sergio
Martin.SergioAuthor
Associate III
February 20, 2017
Posted on February 20, 2017 at 07:50

Hi,

   Anyone with this evaluation board could try this example to verify that it is not a hardware failure?

Thanks in advance,

Sergio

Martin.Sergio
Martin.SergioAuthor
Associate III
February 20, 2017
Posted on February 20, 2017 at 14:22

Hi,

   Reading information about the differences between STM32469I-Eval Board and STM32479I-Eval Board (

schematics, 

BOM...

), I think the difference is only the Micro STM32F469I and

STM32F467I

 and I think they are exactly the same except for the cryptographic module (Diferences between Datasheets and the same User manual), so I would not have to touch anything in the application to work correctly. This is correct?

  Any idea how to run the example application correctly?

Thanks in advance,

Sergio

Martin.Sergio
Martin.SergioAuthor
Associate III
February 21, 2017
Posted on February 21, 2017 at 14:37

No one knows why this happens?

Amel NASRI
Amel NASRI
ST Technical Moderator
February 21, 2017
Posted on February 21, 2017 at 17:08

Hi

Martin.Sergio

,

There is no difference between both boards: same schematic is used.

As you already noted it, the only difference iswithin the STM32 chip where HW crypto is supported for STM32F479 compared to STM32F4

I'll check again the example from my side and come back to you if I have more insights.

-Amel

To give better visibility on the answered topics, please click on "Best Answer" on the reply which solved your issue or answered your question.
Martin.Sergio
Martin.SergioAuthor
Associate III
February 22, 2017

Posted on February 22, 2017 at 09:28

Thank you very much st.mcu,

 

I attach a video in case you see something wrong

(Jumpers, connections...)

Also I attach a photo with all informtation of the Evaluation Board

Thanks in advance,

Sergio

________________

Attachments :

VID_20170222_085934.mp4 : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HyrV&d=%2Fa%2F0X0000000bDh%2F.hPorO7mIWQLJx02PqoQHFSUUEg2yec9k.sXET0wfYY&asPdf=false

IMG_20170222_092439.jpg : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006Hype&d=%2Fa%2F0X0000000bDc%2FLhh_SwteL8AELhQVXP996xDwpnU5zuF4divtk3WBB2A&asPdf=false

Martin.Sergio
Martin.SergioAuthor
Associate III
March 21, 2017
Posted on March 21, 2017 at 14:56

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

Amel NASRI
Amel NASRI
ST Technical Moderator
March 22, 2017
Posted on March 22, 2017 at 09:47

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 "Best Answer" on the reply which solved your issue or answered your question.
Martin.Sergio
Martin.SergioAuthor
Associate III
March 22, 2017
Posted on March 22, 2017 at 12:21

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

Terms & ConditionsAccessibility statement