This seems to be pointing to a cache related issue that has been seen in the past when loading and running different slave core application that run DSPLink.
DSPLink's Proc module allows the user to load/start/stop the DSP core but doesn't completely power down (and reset) the DSP. Because of this there is usually stale data in the cache when re-loading the slave core. This isn't much of a problem if the same slave core app si reloaded. When loading a different salve application, the stale cache data can cause unexpected results which is what I suspect is happening here.
Solution is to completely power the the DSP domain on the device. If you are using TI DVSDK 4.x for the OMAP3530, you can use the Local Power Management (LPM) package included in the kit which contains a kernel utility module to help with powering on/off the DSP core on the OMAP3530.
LPM is also part of the Multimedia Framework Products (MFP aka Codec Engine).
You can find both TI's DVDSK 4.x and/or MFP at:
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/index.html