• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 100 subscribers
  • Views 438 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SYS/Bios Logging

Ed Hildebrandt
Expert 1035 points

Can someone help me better understand the SYS/BIOS Logging options?  Specifically the Hwi Logging option in the Agent Module.  I had enabled this option a while back while trying to debug a problem.  I left the option on as at the time it didn’t seem to adversely affect the operation of my code.  That is until I started running some timer and capture interrupts.  It seems that the option can cause a timer to be 4 to 5 times the correct length (a bit random) and would cause my watchdog to trigger intermittently when the timers was used. 

 

Turning the option off has fixed my issue but I’d like to understand why.  Also is it best practice to turn all the logging (Hwi, Swi, Task & Application) off when not needed?

 

Thanks

Ed

  • 0
    TI__Mastermind 45025 points

    Hi Ed,

    Yes, logging will affect performance.  Hwi logging is known to be the most expensive.  If you're not using logging, you should disable it in order to increase your performance.

    Have you seen the SYS/BIOS User Guide?  I'd highly recommend giving it a read.  It should be included with your SYS/BIOS installation.  For example, I see it here on my machine:

    C:\ti\BIOS\SYS-BIOS\bios_6_34_01_14\docs\Bios_User_Guide.pdf

    Section 8.7 "Performance Optimization" covers logging.  Specifically from that section:

    "For example, Hwi logging tends to be the most expensive in terms of performance due to the frequency
    of hardware interrupts. Two Hwi events are logged on every Clock tick when the Clock's timer expires"

    Steve