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.

DM6437: CE/FC v1.20.03 build instructions

Hi,

My customer is using DM6437 DVSDK v1.01.00.15 using CE v1.20.02 and FC v1.20.03. They have units in production in 1000's of quantity. However, there find couple of units out of 100's are failing randomly, reason they can't use emulator. The error they see are -

AlgMem_create> Granting DMA channels to algorithm through DMAN3 FAILED (0xffffffff).

The 0xffffffff return code looks to be from a failed malloc in DMAN3, but there is plenty of free memory available. I’m trying to find out what params are being passed to that malloc to help identify why it might be failing.

They are requesting build instructions for CE and FC source code so that they can put this debug code to know what parameters can be passed. Is it possible to get build instructions for CE/FC source code or if there is another way to do this, please let me know? Thanks.

Prateek


  • Prateek,

    FC 1.20.03 is quite an old release, as far as I know they weren't even full source releases, not sure if they were intended for rebuild.

    There is an FC 1.20.04 release that fixes some issues (You may want to go through release notes of FC 1.20.04 to see if any of those issues might be relevant).

    Gunjan.

  • Gunjan,

    I dont see FC v1.20.04 on the page below -

    http://software-dl.ti.com/dsps/dsps_registered_sw/sdo_sb/targetcontent/FC/index.html

    Can you send me a link to download it along with release notes?

     

    Thanks,

    Prateek

     

  • Looks like the customer was able to build CE/FC using new package.bld and makefile from CE 2.x versions.

     

    Further, the customer was able to find the  isssue, here are the details -

    Looks like the problem we are having with codec loads is indeed caused by a malloc failure in DSKT2. The H.264 codec we are using requests one very large memory section. The problem is that occasionally, depending on what is running or in use, memory can get segmented and a contiguous block of memory that is large enough does not exist.

     

    The customer is planning to port their own memory manager on DSKT2. Do we have any existing solution that they can use?

     

    Thanks,

    Prateek