cancel
Showing results for 
Search instead for 
Did you mean: 

Does STM32N6 CSI need Frame Start and Stops

Brenden_PLUS
Senior

I'm using a 

* STM32N6-DK

* Brightsense VD56G3

I've made 2 camera drivers so far and the only difference i can see from the cameras is that my first camera module has MIPI short packets start and stop.  I'm making this observation from the scope.  So i know it's sending the data it's just receiving black messages.  

 

Question

* Do you need short packets frame start and end for it to grab images.   

 

Other info

* I'm using Zephyr, but i just want to make sure from the hardware i don't need short packets because i don't think VD56G3 can generate short packets.   

 

Screenshot from 2026-03-23 11-04-56.png

1 ACCEPTED SOLUTION

Accepted Solutions
Brenden_PLUS
Senior

So it does have a frame start.  The problem is that i think it's too close to the actual data.  

 

Captured from my driver.  Last packet is the short packet

MyDriver.jpeg

 

 

Capture from ST's camera dev board.  The far left is the start packet and 2 meta data lines.  

ST_devboard.jpeg

 

So it is sending the frame start packets.  So this issue is done

View solution in original post

3 REPLIES 3
Brenden_PLUS
Senior

You have a driver for the STM32N6 with camera

* VD55g1 

Which i also think can't do start and stop frame.

 

Brenden_PLUS
Senior

What i'm currently trying to figure out is in

HAL_DCMIPP_PIPE_FrameEventCallback

I call

HAL_DCMIPP_PIPE_GetDataCounter

I get a number i'm not expecting.

I'm grabbing a 640x480 image and what i receive from getDataCounter is 154880, when it should be 307200.  With my other camera it gets the proper amount of data captured?

 

But i do get the number of FPS i'm expecting

Brenden_PLUS
Senior

So it does have a frame start.  The problem is that i think it's too close to the actual data.  

 

Captured from my driver.  Last packet is the short packet

MyDriver.jpeg

 

 

Capture from ST's camera dev board.  The far left is the start packet and 2 meta data lines.  

ST_devboard.jpeg

 

So it is sending the frame start packets.  So this issue is done