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

RTOS/TDA2EXEVM: 4CH AVB Capture + Decode + VPE + Sync + Alg DMA SW Mosaic (IPU1-0) + AVB_Tx/Display can't output

sam hsieh
Expert 1370 points

Part Number: TDA2EXEVM

Tool/software: TI-RTOS

Hi,

I would like to run the usercase of 4CH AVB Capture + Decode + VPE + Sync + Alg DMA SW Mosaic (IPU1-0) + AVB_Tx/Display on TDA2XX EVM board.

Based on VSDK v3_6 package, configured the setting (cfg.mk):

AVB_INCLUDE=yes

NDK_PROC_TO_USE=ipu1_1

DUAL_A15_SMP_BIOS=yes

Then rebuild MLO & AppImage, by the following step:

make depend

make vision_sdk

make sbl

 make appimage

It show that "46.832519 s:  DECODE: ERROR: ALGPROCESS FAILED (status=0x00001421) !!!" when run 4CH AVB capture usercase.

I confirmed that the AVBs sent streaming packets with MJPEG compression successfully from the statistics of AVB_RX Link 

But I observed that there is a tricky message:

[IPU1-0]     52.211584 s:  DECODE: CH0: H264 Decoder flush needed (267297)!!!

[IPU1-0]     52.211675 s:  DECODE: CH0: H264 Decoder Flushing !!!

There is no video displayed on HDMI TV.

Could you help teach me how to solve the issue? Thanks.

BRs,

Sam Hsieh

bios_4ch_avb_dec_display0410.txt

 

  • 0
    TI__Mastermind 42515 points
    Hi Sam,

    a possible reason for " DECODE: ERROR: ALGPROCESS FAILED (status=0x00001421) !!!" error could be mismatch between resolutions of the input file and ENCDEC_MAX_FRAME_WIDTH & ENCDEC_MAX_FRAME_HEIGHT in the usecase, see this thread for the same issue:
    e2e.ti.com/.../693214

    Can you check if this is the case?

    Regards,
    Yordan
  • 0 in reply to Yordan Kamenov
    Expert 1370 points

    Hi Yordan,

    I confirmed that the parameter of UCs 

     #define AVB_TALKER_MAX_FRAME_WIDTH 1280
     #define AVB_TALKER_MAX_FRAME_HEIGHT 720

    The cause should be different.

    BTW, I also the AVB camera could works fine on TDA2X EVM/Linux (A15)

    regards,

    Sam Hsieh 

  • 0 in reply to sam hsieh
    TI__Genius 15985 points
    Hi,

    You can check the decoder error from decoder userguide available with decoder package.

    Regards,
    Anuj
  • 0 in reply to Anuj Gupta
    Expert 1370 points

    Hi Anuj,

    Yes, I observed that the error message output from: File: vision_sdk/links_fw/src/rtos/links_ipu/iva/iva_dec/decLink_common.c

    DecLink_codecProcessTskFxn: Receive format=9
    [IPU1-0]   4534.607027 s:  DECODE: ERROR: ALGPROCESS FAILED (status=0x00001421) !!!
    [IPU1-0]   4534.607179 s:  DEC_LINK: outArgs->viddec3OutArgs.extendedError for channel 3 Error: 0x1421
    [IPU1-0]   4534.607301 s:  DEC_LINK: Sequence called number 129083

    When IVA process task check algObj.algCreateParams.format,

    Declink_h264DecodeFrame() check the H.264 compress stream failure.

    Q1: The AVB camera sent MJPEG frame, Why the DEC_LINK handle with algCreateParams.format (9: SYSTEM_IVIDEO_H264HP) ?

           Does it mean that the algCreateParams made a mistake in the format?

    Q2: Could I just select output HDMI Display only?

    [IPU1-0]  Select Use-case Config,
    [IPU1-0]  --------------------
    [IPU1-0]  1: AVB TX Only
    [IPU1-0]  2: HDMI Display + AVB TX

    regards,

    Sam Hsieh

  • 0 in reply to sam hsieh
    Expert 1370 points

    Hi Anuj,

    From log message,  I observed that there is some error when RTOS System Initialization.

    But it seems that the initialization process  start successfully for the 4 CHs AVB Capture +DEC  usercase.

    Does it result in the problem which couldn't output HDMI Display?

    BTW, the user guide of DECODE just described the data structure and API function.

    I couldn't catch how to find out the root cause of the issue.

    Could you help instruct me how to solve the issue? Thanks.

    [IPU2  ]      9.310437 s:  SYSTEM: Initializing Links !!!
    [IPU2  ]      9.421460 s:  UTILS: PRF: ##### Cannot allocate Object for SYNC1 ####
    [IPU2  ]      9.424540 s:  UTILS: PRF: ##### Cannot allocate Object for SYNC2 ####
    [IPU2  ]      9.427438 s:  UTILS: PRF: ##### Cannot allocate Object for SYNC3 ####
    [IPU2  ]      9.430549 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM0 ####
    [IPU2  ]      9.433538 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM1 ####
    [IPU2  ]      9.436588 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM2 ####
    [IPU2  ]      9.439638 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM3 ####
    [IPU2  ]      9.442658 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM4 ####
    [IPU2  ]      9.445769 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM5 ####
    [IPU2  ]      9.448850 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM6 ####
    [IPU2  ]      9.452022 s:  UTILS: PRF: ##### Cannot allocate Object for ALGORITHM7 ####

    rtos_4CH_AVB_DEC_HDMI_log_20190416.txt

    regards,

    Sam Hsieh

  • 0 in reply to sam hsieh
    TI__Genius 15985 points
    Hi,

    Can you check the incoming data coming from camera.
    You can check this inside avb_rx link using CCS.
    Check whether the data starts with 0x00 0x00 0x00 0x01?
    If yes then its h264 data.

    Please let me know your observation.

    Regards,
    Anuj
  • 0 in reply to Anuj Gupta
    TI__Genius 15985 points
    Hi,

    I haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).


    Regards,
    Anuj