Added by Udi Fuchs about 6 years ago
I'm trying to setup a development environment for the MityDSP-L138 to write DSP code.
I got the DSP HelloWorld test to work, but with a few blocking issues:
1. I had to use the HelloWorld program downloaded from the website. My own compiled program fails to run with the message:
root@mityomapl138:~# LD_LIBRARY_PATH=$HOME/MDK_2014-01-13/lib/ARM/Release ./MyHelloWorld HelloWorldDSP.out
./MyHelloWorld: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.14' not found (required by ./MyHelloWorld)
It seems that the version of libstdc++ required by MDK_2014-01-13 is newer than the one on the MityDSP. "opkg install libstdc++6" tells me that:
Package libstdc++6 (4.3.3-r24.2.6) installed in root is up to date.
2. Trying to load the DSP kernel module from the MDK fails:
root@mityomapl138:~# insmod dsplinkk.ko
insmod: error inserting 'dsplinkk.ko': -1 Invalid module format
What I did instead is "modprobe dsplinkk", which I assume loaded the module from /lib/modules/2.6.34-rc1/extra/dsplinkk.ko
3. When running the DSP test, it never exits the application. What I see is:
root@mityomapl138:~# LD_LIBRARY_PATH=$HOME/MDK_2014-01-13/lib/ARM/Release ./HelloWorld HelloWorldDSP.out
Loading file HelloWorldDSP.out
Msgq <debug> open: 0x00008000
PROC Load successful
Msgq <GPPMSGQ1> open: 0x00008000
DSP loaded. Type 'q' to quit...
ARM received a message from the DSP:
DSP Message = "DSP Initialization finished."
Any help would be appreciated.
RE: DSP HelloWorld - Added by Jonathan Cormier about 6 years ago
The filesystem and kernel that ship preprogrammed on the L138 is quite old. You should have more luck if you flash the u-boot, kernel, and filesystem included in the 2014-01-13 MDK.
RE: DSP HelloWorld - Added by Udi Fuchs about 6 years ago
Flashing the 2014 MDK files solved all the problems. For some reason installing the U-boot bricked my board, but following the wiki on "reprogramming a dead board" fixed it.
I have another question. Is there a sample Makefile for building HelloWorldDSP using CGT? I saw that someone tried it in this message:
but he didn't seem to succeed.