Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

RTOS/66AK2H12: Identify preempting or blocking task

$
0
0

Part Number:66AK2H12

Tool/software: TI-RTOS

XDCtools 3.32, SYS/BIOS 6.46, CCS 7.4, PDK 4.0.7, NDK 2.25

I have an ARM application with a bunch of tasks. One of the tasks is responsible for receiving TCP data from a connected client and processing this data as 'commands'. I seem to have an issue in which this receiving task (priority 7) is getting preempted or blocked while the NDK continues to receive and buffer data from the attached client. The NDK is running at priority 12. The other tasks on the ARM are running at various priorities but all below the NDK and for the most part at or above the server receiving task. 

I believe the receiver is blocked temporarily because after a short time (several seconds), I get a burst of messages over the stream from the network buffer that I am unable to process in a timely fashion. The data from the client is relatively small (<300bytes) and infrequent (5/sec).

I am having a hard time identifying what is blocking the receiver. I'm assuming that it is one of my other tasks. I don't know the situation is occurring until it has cleared and I get prints that I am unable to process this burst of incoming data.

I am looking for debugging tips or hints. Is there a way to problematically recorded the last thing that blocked or preempted a task so that once I identify the problem has occurred I can display that collected info? (I do not have access to the CCS debugger but have a flash log that I can log to and can send debug message out a udp port). 

Mike


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>