• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 328 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.

AWR1843 The function of Log

Hiroyuki Kanematu
Expert 2975 points
Other Parts Discussed in Thread: AWR1843

Hi, I'm using AWR1843 Boost.

I currently want to log and record that data in a text file on my computer.
The application is created with the SDK.

The contents of the log are divided into the following according to the level.
(1) Notice
(1.1) Hardware configuration
Record the contents of whether each device is configured

(1.2) Recording speed and distance results
Record after Doppler FFT

(2) Error
(2.1) Hardware configuration failure
(2.2) Data transfer failure
(2.3) Calculation result output failure

The flow of recording such contents in a text file is as follows.
Do you have the idea of symbolizing what you need to log, transferring that data to the MSS, communicating to your PC on a regular basis, and writing it to a text file?

postscript
Maybe there is a function to log in the SDK?

  • +1
    TI__Genius 15046 points

    Hi,

    I am not sure if I fully understand what it is that you need. Does UART not satisfy this need? On the PC side, a program can write the data received over UART to a file.

    To add to this, if you are using CCS to debug, you can actually use fopen, fread and fwrite. There are many examples of testcases in the SDK using fopen and fread, and some using fwrite too. With CCS debug, these functions are capable of reading/writing to files on your PC.

    Please let me know I misinterpreted your question, or didn't answer it in full.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Expert 2975 points

    Hi, Asyush.

    Thank you for your answer.

    >I am not sure if I fully understand what it is that you need.

    >Does UART not satisfy this need?

    >On the PC side, a program can write the data received over UART to a file.

    For the time being, data is sent to CP via UART.
    By the way, what I want to know the most is that if you want to log the error or notice, it is via UART, but I would like to know the specific route to the CP. (I thought I was transferring the data recorded in MSS to CP.)

    > To add to this, if you are using CCS to debug, you can actually use fopen, fread and fwrite.

    >There are many examples of testcases in the SDK using fopen and fread, and some using fwrite too.

    >With CCS debug , these functions are capable of reading / writing to files on your PC.

    If you write the debug function of CCS, you can easily record it in a CP file.

    OK. Since this debug function does not exist in the SDK, is it okay to consider using the CCS debug function?

  • +1 in reply to Hiroyuki Kanematu
    TI__Genius 15046 points

    Hi,

    Hiroyuki Kanematu said:
    I want to know the most is that if you want to log the error or notice, it is via UART, but I would like to know the specific route to the CP.

    If you receive the text on PC in the console window in CCS, it is not over UART, but rather over JTAG.

    Could you point me to a particular code example where I can explain the mechanism of error logging? It would be helpful to discuss this with an example.

    Aniket Mahajan said:
    To add to this, if you are using CCS to debug, you can actually use fopen, fread and fwrite.

    To clarify: fopen, fread, fwrite can be used in application code after using #include <stdio.h>. It's just that the application would need to run in CCS debug mode for these functions to work.

    You can search for usage of fopen, fread and fwrite in the SDK. However, I haven't really seen this be used for error logging, but rather to read input data for testcases.

    Regards,

    Aayush