• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 391 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How to debug m3vpss hang-up issue?

Cai Jin
Prodigy 115 points

hi,

we are tring to intergrate one sensor onto the 8127 IPNC platform. The sensor output is 10-bit bayer parallel(720P). My IPNC version is Beta Release Version 2.8.
I have setup a very simple test case (cameraLink+nullLink). However, once the test case is started, the m3vpss will soon be hanged up. A log is given below. ...

=========================================================================
 [m3vpss ]  7924: CameraLink_tskRun get cmd = 0x0004
 [m3vpss ]  7924: CAMERA: Dequeued 1 frames !!!
 [m3vpss ]  7925: CAMERA: Fields = 1 (fps = 0), Total Resets = 0 (Avg 0 ms per reset)
 [m3vpss ]  7925: NullLink_tskMain get cmd = 0x0004
 [m3vpss ]  8018: NULL   : Received and returning 1 frames !!!
 [m3vpss ]  7925: CAMERA: Queued back 1 frames !!!
 [m3vpss ]  7941: CameraLink_tskRun get cmd = 0x0004
 [m3vpss ]  7941: CAMERA: Dequeued 1 frames !!!
 [m3vpss ]  7941: NullLink_tskMain get cmd = 0x0004
 [m3vpss ]  8035: NULL   : Received and returning 1 frames !!!
 [m3vpss ]  7942: CAMERA: Queued back 1 frames !!!

..................................................................

 [m3vpss ]  9597: CameraLink_tskRun get cmd = 0x0004
 [m3vpss ]  9597: CAMERA: Dequeued 1 frames !!!
 [m3vpss ]  9597: NullLink_tskMain get cmd = 0x0004
 [m3vpss ]  9691: NULL   : Received and returning 1 frames !!!
 [m3vpss ]  9597: CAMERA: Queued back 1 frames !!!

=========================================================================

From the above log, one can found that framebuffer is filled in cameraLink, sent to nullLink, returned by NullLink to CameraLink again. If we call this process as one round, such a simple chain can run up to 100 rounds, sometimes. Once the m3vpss is hanged up, there will no more log can be output from the m3vpss side. And DCC tool cannot communicate with m3vpss.
I don't know what is the root cause of the m3vpss's hang-up. And I have no idea to debug such a mp3vpss system based on my 8127 ipnc platform. Any one can give me some help or advice on it?

Many thanks.

  • 0
    Prodigy 30 points

    Hey,

    I'm having a similar problem. Our sensor is streaming 720p video and after a few rounds the m3vpss hangs. Did you ever find a solution?

    Thanks,
    Robb

  • 0
    Mastermind 8715 points

    Hi Cai Jin,

    1. To get those logs, you added prints in the code? If yes please note that we need to use vps_rprintf() on vpss. otherwise your print can cause this problem.
    2. You can start with simple use case like capture display  mode . Which can give better hands on. (M not sure if capture display mode available in V2.8 but V3.0 and above this use case is available.)
    3. use prints throughout the code, to find out where it is getting stuck.

  • 0 in reply to Robb
    Prodigy 115 points

    I have forgot how to debug this issue.  In my mind, the root cause is the AWB/AE window setting problem. The default setting is for 1080P sensor. You need update the related settings for you 720P case. Otherwise, there is memory access risk which leads to the m3vpss's hang issue.