This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/EK-TM4C1294XL: CCS7.3 fails to print UIA Live Session data from seleceted COM port

Guru 55913 points
Part Number: EK-TM4C1294XL

Tool/software: Code Composer Studio

Have difficult time with System Analyzer UIA2.0.5.50 Live Session with idle logger prints to COM4 (115,200BPS) and CPU load, execution print graphs are blank of course. ROV suspend shows the records are being produced though not being printed to Live Session preview pane. Sometimes it skips thousands of records then prints a few lines with error and stops for good. Yet press debug suspend and ROV record count has increased by a few hundred or so records.

COM4 idle logger captured data sent to terminal emulator (115200) has consistent binary data flow pattern, typical of printing Live Session details. The target has 256B buffer and logger has same 256B buffer, there seems a handshake issue with serial data rate but not out to terminal emulator and 9600 is ridiculously slow for UART0. Logging is not pushing the envelope, simple configurations should not be having this data flow issue. Used to be able to get logging to synchronize with Live Session clicking on stop and start few times in row to get it printing, flush the buffer. What could be happening, 115200BPS is fairly slow data rate and worked with CCS7.0 at one time.

  • UIA Logging setup logger buffers setting is internally constraining LoggerIdle buffers setting to 1/4 fraction the MAU's set as (Logger Buffer Sizes) taken from the targets total SRAM space.

    LoggerIdle will not accept smaller buffer setting than what is set in Logging Setup. Yet a larger value over 1/4 say 32k will automatically increase RTOS configuration files (LoggerIdle.bufferSize = 32768;) but revert the GUII setting back to 1/4 of 32k or 8192 bytes.

    The UIA help info for Logger Idle is out of date and shows (LoggerIdle.bufferSize = 1024;) and says nothing about automatic memory proportioning in this area even as far back the text was last updated.

  • Odd thing is UIA LoggerIdel was previously working with very little Logger System buffers (2048Bytes) in earlier version of RTOS Analyzer.
  • What version of TI-RTOS are you using? Or more specifically, what version of UIA?
  • System Analyzer UIA2.0.5.50 & TI-RTOS 2.16.1.14 seems ok 32KB target and idle mode UART logger auto sizes back to 8192KB. Also had to kick the loggers UARTutils.c buffer threshold from 32 Bytes up to 256 Bytes. I don't know how it was even working previously 6 months or even 2 weeks ago with logger 256B & target 1024Byte buffers.

  • Were you logging less previously?
  • Hi Todd,

    No even less being a much longer sleep duration 1000 between Log_print2 cycles, could have been two print task functions 1000 sleep duration. Recall making the target buffer 4096KB then reverting back to 1024KB, nothing seemed to help.

  • I refer to the task being static as Main module is supposed to create dynamic tasks for all other functions in an application. In my mind that means all other functions that are not specifically assigned to a task instance. I don't/have not ever see that occurring in RTOS analyzer other than several HWI entries indicate 20% CPU loading. Was expecting the Load module to detect the applications dynamic loaded tasks as separate execution/CPU load line graphs.

  • These like these topics are a separate issue. If you want to discuss them, please open a new thread.

    Todd
  • Ok no problem, Added graph here as to show working very good and producing very consistent RTOS analyzer graphs, Yea!

    How many end up doing exactly like (second post up) and think it is a CCS7.0 issue. Live Session/Graphing issues first occurred after online updating UIA graphic drawing parts of CCSv7.0. Another FE this forum advised issue seems to act like a know behavior, CCSv7.3 would correct it. Odd thing is that the graphs started printing after moving to v7.3, a week later would no longer output RTOS Live Session data only like the first post shows, very sporadic.