AWR6843ISK: how to estimate cod execution time and where to get the log value

Part Number: AWR6843ISK
Other Parts Discussed in Thread: AWR6843, MMWAVEICBOOST

Tool/software:

Dear sir/madam

  we are using AWR6843ISk + mmwave booseter setup . and able to run the "AWR6843_CPD_with_Classification"  example  project  on  debug mode on code composure studio .

i see part of the code there is logic to estimate time taken for the logic to execute,(screenshot attached for reference)

my question:

 1.where i can find the estimated time value "processInst->benchmarkPtr->buffer[processInst->benchmarkPtr->bufferIdx].dynHeatmpGenCycles"?

    if its get stored in this variable then how to get this value to visulaise?

  2. does it stored in any log file ,if yes where can i check it?

  regards,

  mani

  • Hi Mani,

    Thank you for reaching out, please allow me a few days to look into this and follow up. 

    Best,

    Vignesh K.

  • Hey Mani,

    1.where i can find the estimated time value "processInst->benchmarkPtr->buffer[processInst->benchmarkPtr->bufferIdx].dynHeatmpGenCycles"?

    The estimated time value can be retrieved either by reading the value through the Variable window of the CCS debugger - the MMWAVEICBOOST is required for debugging - or printing it out over UART if you don't have an MMWAVEICBOOST.

      2. does it stored in any log file ,if yes where can i check it?

    The log data is not stored anywhere, but you can add file functions for opening and writing the cycle data to a file if needed. I'd recommend adding the fopen call at the start of the DPU_radarProcess_process function, add fwrite calls at each of the cycle measurements - i.e., after any TSCL - t1 operations, and make sure to close out the file at the end of DPU_radarProcess_process. Note: These file operations should be done for debugging purposes only.

    Hopefully this helps, but let me know if you have any other questions.

    Cheers,

    Kristien

  • hi kristien 

      thanks for your reply.

    1.where i can find the estimated time value "processInst->benchmarkPtr->buffer[processInst->benchmarkPtr->bufferIdx].dynHeatmpGenCycles"?
    kristien reply:
    The estimated time value can be retrieved either by reading the value through the Variable window of the CCS debugger - the MMWAVEICBOOST is required for debugging - or printing it out over UART if you don't have an MMWAVEICBOOST.
    my reply:
      1.   i run the example with AWR6843ISK +mmwavebooster in CCS debugger.I just added one printf statement to the existing code to diplay the code estimated time. But console is not printing any result. Screenshot are  attached for your reference.
    screenshot1(printf statement added to existing code)
    screenshot2(console is not printing the value )
    2.  As you suggested  "to  read the value through the Variable window of the CCS debugger" ,i have kept a breakpoint as shown in below screenshot3 but it throws the error and stop the execution of code(screenshot 4 attached) 
    screenshot3(executed with breakpoint as added  ):
    screenshot4(variable window from ccs debugger after breakpoint  ):
    please check and provide the solution to visualize/print the code estimation time.
    regards,
    mani 
  • Hey Mani,

    You can use the System_printf function instead of the printf function to print directly to the debug console if you are using the MMWAVEICBOOST.

    Regards,

    Kristien

  • hi kristien,

     thanks for your reply.

    As you suggested, i used system_printf instead of printf statement, It prints the value but terminate further execution of code(screenshot is attached for your reference).

    how to fix the issue of code termination issue and also print the execution time ?

    regards,

    Mani

  • Hey Mani,

    Are you resetting both the R4F and C674 cores before loading the individual .out files for each core? I would also recommend grouping the cores as mentioned in the CCS Debug User Guide from the Radar Toolbox so that you can start both programs at the same time. The program should execute, even if the two cores are started at different times, as long as they're both running prior to sending a configuration. Failing to run the DSP core and code could be causing this issue.

    Regards,

    Kristien

  • Hi kristien,

    thanks for your reply.the info shared "CCS Debug User Guide from the Radar Toolbox"  very much useful to run the debugging process faster.

    i  have increased frame time to 800 ms (from existing 200 ms) in the configuration file (.cfg) and i could able to print and run the application continuously.

    regards,

    Mani

  • Hey Mani,

    Nice! I'm glad you found the guide useful and were able to resolve the debugging issue by increasing the frame time. I'll close out this thread for now, but feel free to post any new questions you have.

    Cheers,

    Kristien