• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 672 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.

H264 codec instance creation fail after deleting h263 encoder

Manisha Agrawal
Mastermind 22946 points


Hi,

H264 encoder instance creation fails after deleting H263 encoder on DM6467. Attached dav36_h264_fail.log corresponds to that.

Is this error because insufficient TCC available to cater encoder  need? Would this mean RMAN_freeResources() API call is missing before  deleting H263?

Regards,

Manisha

[DSP] @686,486,207tk: [+2 T:0x8ba0006c S:0x8ba03614] ti.sdo.fc.edma3 - populateScratchG@302,244,579us: [+0 T:0x467c4490 S:0x467c22cc] OC - Comm_put> Enter(queue=0x0, msg=0x46fd6880)

@302,245,560us: [+0 T:0x467c4490 S:0x467c22cc] OC - Comm_put> return (0)

@302,246,261us: [+0 T:0x467c4490 S:0x467c22c4] OC - Comm_get> Enter(queue=0x10002, msg=0x467c2364, timeout=-1)

@302,248,232us: [+0 T:0x467c4490 S:0x467c22c4] OC - Comm_get> MSGQ_get() status=0x8000, return (0)

roup> Obtained EDMA channel 63 and corresponding Tcc

[DSP] @686,486,286tk: [+7 T:0x8ba0006c S:0x8ba03614] ti.sdo.fc.edma3 - populateScratchGroup> Error allocating tcc 1010

[DSP] @686,486,349tk: [+0 T:0x8ba0006c S:0x8ba03614] ti.sdo.fc.edma3 - populateScratchGroup> Exit (status=0)

[DSP] @686,486,406tk: [+7 T:0x8ba0006c S:0x8ba03704] ti.sdo.fc.edma3 - openRMHandle> Error populating RM scratch groups

[DSP] @686,486,472tk: [+0 T:0x8ba0006c S:0x8ba036ec] ti.sdo.fc.edma3 - closeRMHandle> Enter (handle=0x8fa42368)

[DSP] @686,486,744tk: [+0 T:0x8ba0006c S:0x8ba036ec] ti.sdo.fc.edma3 - closeRMHandle> Exit (status=0x0)

  • 0
    TI__Expert 7415 points

    Manisha,

    You will notice from the entire log that the RMAN_freeResources cal is indeed being made. In fact, the two types of codecs being created are actually in different scratch groups, which means that they should be using different set of resources. Hence whether the first one is deleted or not, shouldn't have a bearing on whether the second one could be created.

    The error code above indicates that a generic request for "Any TCC" has failed (when made to the EDMA3 LLD). Have you ensured that the scratch group #0 (in which the second codec is created) has enough TCCs configured for its purpose ?

    Per the log, the request is for :-

    Allocating 49 tccs 49 edma 0 qdma channels and 384 params

    Are you sure you meant to create the 2 codecs in different scratch groups ? You don't seem to be running them simultaneously ?

     

    Thanks,
    Gunjan

  • 0 in reply to Gunjan
    TI__Mastermind 22946 points

    The test sequence is as below. So deleting H263 and then creating H264 instance is causing this issue.

    [1] Engine open (OK) - dav_01_boot_OK.log

    [2-1] h.264 encoder create (OK) - dav_02_h264_OK.log

        (h.264 encoding …)

    [2-2] h.264 encoder delete (OK)

    [3-1] h.264 encoder create (OK) - dav_03_h264_OK.log

        (h.264 encoding …)

    [3-2] h.264 encoder delete (OK)

    [4-1] h.263 encoder create (OK) - dav_04_h263_OK.log

        (h.263 encoding …)

    [4-2] h.263 encoder delete (OK)

    [5-1] h.263 encoder create (OK) - dav_05_h263_OK.log

        (h.263 encoding …)

    [5-2] h.263 encoder delete (OK)

    [6] h.264 encoder create (FAIL !!!) - dav_06_h264_FAIL.log

  • 0 in reply to Manisha Agrawal
    TI__Expert 7415 points

    Okay, I see. Can you share the .cfg file, it will help in interpreting the log.

  • 0 in reply to Gunjan
    TI__Intellectual 1890 points

    .cfg file is attached. .txt suffix is added to the file name because of upload issue.

     

    WS Yeo

  • 0 in reply to Woo-Seung Yeo35126
    TI__Expert 7415 points

    The configuration of ti.sdo.fc.edma3.Settings module indicated in the .cfg file attached, does not seem to correspond to the log ? Are you certain this .cfg file was used to create the codecs ? Any chance the configuration was overridden by a "C" based configuration ?

    Per the configuration, there should be only 26 Edma channels and Tccs available, however the logs indicate that you were able to grant the (failing) codec upto 47 Edma channels/Tccs ?

    Could you please double check ?

  • 0 in reply to Gunjan
    TI__Intellectual 1890 points

    Hi Gunjan,

     

    Sure, I build the codec server “vcs720pCombo.x64P” with that attached .cfg file.
    And I don’t know well about the “C” based codec server configuration. The configuration was not overridden.

    If the “ti.sdo.fc.edma3.Settings” is not correct, if it has wrong numbers, could you let me know the correct settings?

     

    W.S. Yeo

  • 0 in reply to Woo-Seung Yeo35126
    TI__Expert 7415 points

    I'm not saying the configuration is wrong, just that it doesn't seem to coincide with what I observe in the log.

    Maybe Manisha can check if there is any "C" based configuration that is overriding the contents of the .cfg file.