• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 374 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.

DM365 H264 Codec Error

rulphie
Prodigy 110 points

DM365 board using DVSDK 2_10_01_18 for  Appro 2.0

We have an in-house camera board where at times H264 encoding fails following a quick power cycle on the board (remove power and apply power within 2 seconds). The log failure, aside from no video on GUI is as follows:

               SPS not found

               In Grab Image, the source stop being readable!!!

The problem goes away with a slow power cycle ( > 10 seconds).

When the problem occurs, we found that VIDENC1_process blocks indefinitely. We are still in the process of identifying the root cause. We have verified frame data (created fix frame contents) prior to calling h264 encoder under normal and erroneous states. Has anyone in the community encountered the same problem or have any insight? Your response is greatly appreciated.

  • 0
    TI__Genius 11000 points

    Hi,

    V2.0 is two year old release, can you please use the latest v3.0 release and check for this issue on your board.

    Also, if you can share the complete log from POWER ON will help us to know the issue better.

    One more check is, can you check your setup by only using UBL from v3.0, we have some sync reset fixes deon for VPSS, HDVICP added there

    Regards,

    Raghu

  • 0 in reply to Raghu Kudva
    Prodigy 110 points

    Hi Raghu,

    In addition to  "SPS not found" and  "In Grab Image, the source stop being readable!!!", a "WaitStreamReady fail". Enabling debug on irq kernel module, it was found that interrupt 10 never fires which is  HDVICP_ARMINT.  Below is the log for when it was working, no irq#10 on a the error condition.

    Volume ID is fac21430, no volume label.
    IRQK Debug: REQUESTIRQ ioctl received for resource 4 (irq #10)
    IRQK Debug: REQUESTIRQ: waiting for resource semaphore...
    IRQK Debug: REQUESTIRQ: ... got it
    IRQK Debug: REQUESTIRQ: not registered, requesting irq...
    davinci_unmask_irq: enabling interrupt 10
    IRQK Debug: REQUESTIRQ: ... got it
    IRQK Debug: writing ARM_INTMUX register ...
    IRQK Debug: REQUESTIRQ: adding filp c0541f00 to user list
    IRQK Debug: WAIT ioctl received for irq 10
    IRQK Debug: ...got it
    IRQK Debug: REQUESTIRQ ioctl received for resource 2 (irq #9)
    IRQK Debug: REQUESTIRQ: waiting for resource semaphore...
    IRQK Debug: REQUESTIRQ: ... got it
    IRQK Debug: REQUESTIRQ: not registered, requesting irq...
    IRQK Debug: REQUESTIRQ: ... got it
    IRQK Debug: REQUESTIRQ: adding filp c0541f00 to user list
    IRQK Debug: WAIT ioctl received for irq 9
    IRQK Debug: ...got it
    IRQK Debug: irqHandler: servicing irq #9
    IRQK Debug: WAIT ioctl received for irq 10
    IRQK Debug: ...got it
    davinci_ack_irq: ARCK IRQ - interrupt 10
    davinci_ack_irq: current interrupts 0x2c0f0751
    davinci_ack_irq: current interrupts 0x2c0f0751
    IRQK Debug: irqHandler: servicing irq #10

    Using UBL from V3.0, which have some sync reset fixex for VPSS, HDVICP as outlined above fixes the issue.

    Thanks you for your response.