A bug is found in H.264 encoder test app.

Yulin

Hi there,

Packages involved:
   - xdctools_3_15_01_59
   - framework_components_2_25_02_06
   - dm365_h264enc_02_10_00_06_production.bin

I think it is a bug in the following tracing:

HDVICPSYNC_start
   --> VICP_register(vicp=VICP_HDVICP0=4/*VICP_ResourceType,a scalar*/,...)
       {
          g_handle = (IRES_HDVICP_Handle) resource (=VICP_HDVICP0);
          g_fnPtr = HDVICPSYNC_done;
       }

INT triggers Host_int_handler
   --> HDVICPSYNC_done(hdvicpHandle=g_handle(=VICP_HDVICP0))
       {
          ...
          if (hdvicpHandle->id == IRES_HDVICP_ID_0) { //<-------- FAIL !!!
              vicp = VICP_HDVICP0;
          }
          else {
              return (HDVICPSYNC_ENORESOURCE);
         }
          ...
       }

BR,
Yulin

over 14 years ago

0 Gunjan over 14 years ago

TI__Expert 7415 points

What device are you running your app on ?

Could you also tell me what the contents of your hdvicpHandle are ? You can either step through the code for that, or enable trace that would print out what id has been granted to your algorithm.

Gunjan.

0 Yulin over 14 years ago in reply to Gunjan

Expert 1625 points

Gunjan,

I run the app on a DM365-297MHz.

As the trace (done by steps) I posted, the value of hdvicpHandle is 4(VICP_HDVICP0) to HDVICPSYNC_done().

hdvicpHandle(=4)->id is not guaranteed to be a valid value

Since I have some NDA with TI, please email to yulin.huang@flexmedia.com.tw in case more information is required.

Yulin.

Processors

Processors forum

A bug is found in H.264 encoder test app.