• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 199 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.

IWR6843ISK-ODS: Program to Slow because i print?

max mannesse
Intellectual 340 points
Part Number: IWR6843ISK-ODS

Hello,

I'm using the People counting demo code to create a Fall detection program.

I started by copying the sensor values from the DSP values and sending these to my own methods.

But my code is a little slow because i use quite prints.

My question is: How long does a single print method take in milliseconds?

Because i think i'm really slowing down my program.

Regards,

Max

  • 0
    Intellectual 340 points

    I meant "I use quite a few" not just "quite"

  • 0 in reply to max mannesse
    TI__Mastermind 28055 points

    Hi Max,

    Print statements take quite a bit of time - you can benchmark it using the Cycleprofiler - search for this in the code and you will see examples of use. Cycleprofiler_getTimeStamp will return a counter value (counter has same frequency as core clock). So you call one before the print and one after then find the difference.

    To avoid print statements, you can try a few things:

    1. Use the CCS debugger, it can be clunky at first, but once you get the hang of it it is quite powerful and you will be able to examine variable values at any point in time.
    2. Output data you need to see every frame over UART. Typically you can append one or two values to the header TLV.

    Regards,

    Justin