Sorry about the length of this post but I have tried to keep it as concise as possible.
The steps I have taken (described below) are by no means necessarily correct.
I have run out of ideas on what to try next. Any suggestions as to the best place to
look next would be appreciated. Has anyone else been down this path?
My objective: to build a DSPLink application, using a supplied example as a starting point.
The documents I refer to are from http://wiki.davincidsp.com.
Using 'Example DSPLIB/DSPLink Application on OMAP-L1x' I can get the application to
work using the supplied files, notably call_dsplib, dsplib_server.out, cmemk.ko and
dsplinkk.ko.
When I rebuild the ARM binary, using
make -f arm_makefile
I can create a new version of call_dsplib but when I try to run it I get an error
concerning cmemk.ko versions.
I rebuild the Linux kernel according to 'Building the OMAP-L137 Linux Kernel' - this
results in a new version of uImage. The new uImage can successfully be downloaded
and run on the L137. I'm not entirely sure that this step was useful - the next step may well have been more critical.
I successfully rebuild cmemk.ko according to 'Building the OMAP-L137 SDK'. The new
version of cmemk.ko is roughly the same size as the supplied version - approx 25kB.
Now, I can run the application again successfully, using my new call_dsplib binary.
The only changes to the program are that I have added further diagnostic printf()
statements to arm_main.c.
Next I try to rebuild dsplib_server.out, as per 'Example DSPLIB/DSPLink
Application on OMAP-L1x' using
make -f dsp_makefile
This is successful in so far as a new executable file dsplib_server.out is created.
Its size is very slightly different from that of the supplied version - approx 440kB.
(If I fire up CCS under Windows for the C6747 side of the L137, I can load either of the dsplib_server.out files
and find that the c_int00 addresses (and others) are different.)
Back on the ARM, when I try and run the application it now hangs in function PROC_start(). Function
PROC_load() has apparently executed successfully.
I try and rebuild dsplinkk.ko according to 'Building the OMAP-L137 SDK'. This creates
a new version of dsplinkk.ko that is over ten times larger than the supplied version.
1.3MB vs. 120kB. (?)
It is still apparently possible to load this module, using loadmodules.sh but the
application still hangs in PROC_start(), after PROC_load() has apparently executed
successfully.
According to 'Troubleshooting DSPLink configuration issues', this must be a
configuration issue. I've looked at dsplink-omapl1xxgem-base.tci and at
CFG_OMAPL1XXGEM-SHMEM.c and while I cannot claim to understand everything about them,
the apparent settings for reset vector, dsp code, shared memory and POOL memory
appear to match.
Regards,
Donald
