TI OpenMAX's jpegenc_sn.dll64P needs FIXING!

Peter Nemeth

Other Parts Discussed in Thread: DM3730

Dear All,

With the help of Felipe Contreras, we have come to the bitter realization that jpegenc_sn.dll64P is not working in the L23.i3.3 / L23.i3.8 versions of the TI OpenMAX public binaries, all as a result of a compilation error from TI's side (node creation - NODE_CREATE - fails). All that needs to be done to fix this issue is to recompile the JPEG encoding binary without PPLIB support. As far as I know, at the moment there is no working public binary that would be capable of JPEG encoding through the DSP.

Please, anyone from TI who could recompile the binary without PPLIB let me know; either fix the public release, or just send me the working binary. It would be quite urgent, as so far I have been mailing some TI engineers for more than a week without getting any results.

Thank you,

Peter

over 14 years ago

0 Peter Nemeth over 14 years ago

Prodigy 30 points

...

0 Bin Liu over 14 years ago in reply to Peter Nemeth

TI__Guru**** 167581 points

What is your platform?

This is OMAP35xx forum. AFAIK, OMAP35xx does not use OpenMAX, and has no relation to L23 or similar.

0 Felipe Contreras over 14 years ago in reply to Bin Liu

Prodigy 10 points

First of all, this issue is not dependent of the patforms, it happens in all platforms, including OMAP 3630 (where I tested).

As I already explained to your colleague Jayabharath, Goluguri:

---

The omx source code released has the __JPEG_OMX_PPLIB_ENABLED__ flag
enabled. With that flag the code would try to load
"/lib/dsp/postprocessor_dualout.dll64P", which is not present on the
binary release.

I have tried to narrow the error I get from the tidspbridge driver,
and it fails on dcd_get_library_name(), which can't find the relevant
library. If I print the uuid of the SN, I get
"FC8CF948_D3E9_4B65_BCA7_082EA0AD86F0", which matches the one in the
omx source code:

static const struct DSP_UUID PPLIB_UUID = {
0xFC8CF948, 0xD3E9, 0x4B65, 0xBC, 0xA7, {
0x08, 0x2E, 0xA0, 0xAD, 0x86, 0xF0
}
};

Now, can we agree that the release has a broken JPEG encoder? Or shall
I compile all the omx stuff to demonstrate it?

All you need to do is to recompile a SN without this "PPLIB" support,
just like the one Nokia got for the Nokia N9, and update the release
with it.

---

Obviously, the problem is in the DSP socket-node binary itself.

Moreover, these binaries work perfectly fine on Beagleboard (OMAP 3530), and Beagleboard-xm (DM3730), because they have exactly the same DSP; TMS320C64x+.

0 Peter Nemeth over 14 years ago in reply to Felipe Contreras

Prodigy 30 points

Is there any chance of applying the above solution by the end of this week, and releasing/sending the new binary?

0 Bin Liu over 14 years ago in reply to Peter Nemeth

TI__Guru**** 167581 points

Like I mentioned in my last post, the devices supported in this forum do not use TI OpenMAX at all. You probably need to find out how to get support for the device you use, maybe contact the local FAEs?

Processors

Processors forum

TI OpenMAX's jpegenc_sn.dll64P needs FIXING!