From the TMS320C55x [documentation][1] it's clear that the chip supports multiple memory modes. Therefore, a function such as malloc could have different definitions for each one. I think that the smartest thing to do is to identify the memory mode and figure out how a malloc can be implemented in that mode.

Given that your binary file is fully stripped and most functions seem to be inlined, all you can do is pattern matching. If you want to be smart, figure out a way to build a CFG and try to identify where a malloc could be necessary and check if your target pattern is redundant enough.

Hope this helps. [1]: http://www.ti.com/lit/ug/spru280i/spru280i.pdf

From the TMS320C55x documentation it's clear that the chip supports multiple memory modes. Therefore, a function such as malloc could have different definitions for each one. I think that the smartest thing to do is to identify the memory mode and figure out how a malloc can be implemented in that mode.

Given that your binary file is fully stripped and most functions seem to be inlined, all you can do is pattern matching. If you want to be smart, figure out a way to build a CFG and try to identify where a malloc could be necessary and check if your target pattern is redundant enough.

Hope this helps.