• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 1191 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.

TDA2E: psdk0304 PVR:(Error): PVRSRVBridgeCall: Failed to access device. Function ID:3223086921

user5335884
Intellectual 600 points

Part Number: TDA2E

Hello, expert

TDA2ex sdk: psdk0304

drm] Initialized pvr 1.14.3699939 20110701 on minor 1

PVR_K: UM DDK-(3699939) and KM DDK-(3699939) match. [ OK ]

Now I have a problem like this. Sometimes the startup will report the following errors, which will cause the display failure. Not every time, the following errors will be reported

PVR:(Error): PVRSRVBridgeCall: Failed to access device. Function ID:3223086921 (strerror returns no value.). [0, ]

[09:09:41:382]PVR:(Error): OSEventObjectWait: BridgeCall failed [0, ]

[09:09:41:391]bvs_sgx3dRender: eurasiacon/wsegl/gbm/gbm_ws.c:156: WaitForOpsComplete: Assertion `eError == PVRSRV_ERROR_TIMEOUT' failed.

kmscube -c 36 display ok.

What is the cause?

  • 0
    TI__Mastermind 30480 points

    Hi ,

    Is this issue observed only for vision-SDK usecase involving sgxframecpy link? and not seen with kmscube?

    How long it takes normally to get this reproduced?

    What is the visionSDK version used?

    I will have a look at sgx driver on this error.

    Thanks

    RamPrasad

  • 0 in reply to Ramprasad
    Intellectual 600 points

    Hi.

    1. This is in ti-processor-sdk-linux-automotive-dra7xx-evm-03_04_00_03 ,not in visionsdk.

    2. It usually appears within 100 times.

    i used Branch for PSDKLA 3.x with K4.4 is ti-img-sgx/rocko/1.14.3699939 

  • 0 in reply to Ramprasad
    Intellectual 600 points

    In case of exception, it will print：

    [ 4.552400] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:590][ 4.552417] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:599][ 4.552429] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:599][ 4.552443] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:605][ 4.552455] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:617][ 4.552466] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:617][ 4.552476] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:635][ 4.552485] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:636][ 4.552495] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000
    [09:21:16:644][ 4.552504] [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000

  • 0 in reply to user5335884
    TI__Mastermind 30480 points

    Hi,

    This error tells there is a sync lost error with DSS. Are you using HDMI here?

    >>i used Branch for PSDKLA 3.x with K4.4 is ti-img-sgx/rocko/1.14.3699939 (This is for k4.14)

    This is not correct. For 4.4k kernel you need to use the branch ti-img-sgx/1.14.3699939_k4.4

    Thanks

    RamPrasad

  • 0 in reply to Ramprasad
    Intellectual 600 points

    My device has HDMI and RGB, but it is not displayed with hmdi, it is displayed with DPI RGB。

    [drm:omap_crtc_error_irq] *ERROR* tv: errors: 00008000 

    this log does not exist every time, sometimes it is normal, but sometimes it is not necessarily abnormal。

  • 0 in reply to user5335884
    TI__Mastermind 30480 points

    Hi,

    Can you update to latest commit-id of omap5-sgx-ddk-um-linux/ and give a try?

    There many bug fixes since 3.04 PSDKLA release.

    Thanks

    RamPrasad