Other Parts Discussed in Thread: OMAPL138
Hi,
I have a board with the OMAPL138. The ARM core is running a custom linux (kernel 3.0.23)
I am validating the use of SYSLINK on our system for ARM<->DSP communication.
The board has 128Mbytes of RAM, of which 96 are reserved to Linux ("mem=96M" in uboot) the rest will be for DSP and syslink.
I am using: bios_6_35_01_29; ipc_1_25_02_12; syslink_2_21_01_05; TI_CGT_C6000_7.4.2; xdctools_3_25_00_48.
I have built SYSLINK and I can load the driver without errors on my board.
I can also use ‘slaveloader’ from the ARM to load and run a simple program on the DSP.
However, If I try to run any of the SYSLINK examples, I see that the code hangs on both cores. On the ARM it hangs when calling Ipc_control(Ipc_CONTROLCMD_STARTCALLBACK), while on the DSP is stuck on Ipc_start().
I am (rightly or wrongly) suspecting something wrong with interrupts.
On the ARM I would expect to see an interrupt registered to the SYSLINK driver, while looking at /proc/interrupts I don't see anything.
I load the driver with insmod syslink.ko TRACE=1 TRACEFAILURE=1 TRACECLASS=3, but I don't see any error message printed by dmesg. If I also set TRACEENTER=1, the kmsg log is overrun by all the calls and I can see only the end of the sequence (I cannot see any that seems an error there).
Has anyone got any suggestions?
Thanks
