We are using OMAP L138 and ipc_1_25_03_15, bios_6_35_04_50, xdctools_3_25_03_72, syslink_2_21_02_10.
We have our network driver on the ARM side that talks to syslink and provides the DSP as a node in the network from the ARM side. The driver also strips the network headers when sending over syslink and add then them back when feeding up the network stack.
In the setup the ARM and DSP talk over simplex and duplex channels. For each channel ARM Creates the Heap. No separate Gate is created for each Heap. Each core creates it own Rx MessageQ and registers with the heap. Each Core Opens the remote Tx MessageQ. The Notify Driver and Transport mechanism used are:
With this setup we get a scheduling while atomic fault.
We referred the post: http://e2e.ti.com/support/embedded/tirtos/f/355/t/250517.aspx?pi199400
and changed the NOTIFY driver to use NotifyDriverCirc and Transport to use TransportShmNotify but that also did not make any difference.
Attached is the Dump
We have our arm_dsp_driver that provides read/write abstraction over syslink. The my_network_driv provides the network interface and talk to the arm_dsp_driver.
We are able to create send and receive over TCP and UDP sockets until this fault occurs.
How can we get solve this problem and move ahead?