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: Printing Output from Sensor

Part Number: IWR6843ISK

Hi,

I would like to know what the easiest way is to print to the sensor console the output from the sensor. For example, say I have a few detections in the message body for point cloud data, how do I view this in the console to get a sense of what the output is. I have seen the documentation for debugging using the System_printf, however its not very intuitive how this applies when you have buffered streams of object detections. I am using the vital signs demo as my reference, I will appreciate if the response given can be provided based on this. Basically, I believe that the data from the sensor is processed in the method called MmwDemo_mboxReadTask. Thanks.

  • Hi Odera,

    What sort of data are you hoping to print out? Where are you hoping to print out the data (CLI or the CCS console?)

    If I am debugging using CCS and the data is on the MSS side I usually use a breakpoint and the ccs debug capabilities to move through the code and determine a variable value. I can step you through this.

    It is possible to use system_printf as well. The can take a lot of processing time, so depending on where you want to do this and what data you want to output I can step you through the process.

    Thank you,

    Angie

  • Hi Angie,

    I think both CLI and CCS console could be equally useful for me. I am on the MSS side for now. In theory, I understand what the MSS and DSS are but practically I don't know what advantages I will have working with either or the both. That aside, referring to the example I mentioned (i.e. vital signs) I would like to print or view some of the data related to the distance, velocity information as is obtained by the sensor antenna. In the method I mentioned earlier (i.e. MmwDemo_mboxReadTask). I can see that that we can access a 'data type' called TLV. This data should contain type, length and value. I am somewhat certain that the value will contain bytes or bits that represent the point cloud. I am not 100% sure what these values are but I will assume that this is some point cloud information that was received thy Rx antenna on the sensor. At this point my hope is to be able to convert these values to decimal and make sense of what I see based on the physical position of the sensor.

    There is another aspect I have some questions regarding how to pass data between FFT's and if this happens automatically or the programmer has control over it. However, I will reserve these questions for later. Thanks Angie.

  • Hi Odera,

    There is so much you can learn about our MSS and DSS, how they communicate and how to communicate over CLI and CCS. I'll try to keep it brief here for what you need but to go in depth I suggest going to mmwave_sdk_03_06_00_00\docs and reading sections of the User's Guide and looking at our doxygen.

    Which vital signs lab are you working with at the moment? When debugging an implementation I stick to using the CCS console and running in CCS debug. Once you let me know which vital signs lab this is I can walk you through that process. 

    Here is a document for understanding the TLVs. The TLVs are usually built during the UART task by the MSS but it may be built by the MmwDemo_mboxReadTask in this lab. They can be modified but our visualizers are usually made for a specific TLV format so modifying these can cause pre-built visualizers to break. However, if the visualizer parsing source code is modified, you can use the TLVs to get additional information to our visualizers. This can be good when testing an algorithm. 

    For additional questions on the FFTs feel free to make a new thread so we can keep one topic per thread. 

    Thank you,

    Angie

  • Hi Angie,

    Thanks for the information. I Will try to keep with the CCS console but will need further guidance doing so. I don't know that there is more than one vital sign lab. I am working on the regular vital signs lab not the people counting one.

    I think once I am able to view the data contained in the TLV it will make things more meaningful to me and help with developing a workflow.

  • Hi Odera,

    To print out data here use the "System_printf" function within the MmwDemo_mboxReadTask in mss_main.c. The TLVs are also detailed in the developer's guide section of the user's guide.

    Thank you,

    Angie

  • Thanks Angie,

    I had mentioned using System_printf in my earlier question as I realize that it could be an easy way to view output from a running code. However, could you please give an example of how you would print out the contents of a detected object in a frame using System_printf? 

    For example: 

    message.body.detObj.tlv[itemIdx].address

    the above is the address of the indexed tlv in the frame. How do I use System_printf to see that. There is a SOC_translateAddress which seems to take that address and return the bytes of data contained in that address (I am not sure this is correct). But if this is the case then how do I print the bytes SOC_translateAddress returns?

  • Hi Odera,

    The SOC_translateAddress is used to translate an address from the way addresses are used by the MSS to the way addresses are used by the DSS and vice versa.

    I would first run your code in ccs debug and inspect this element by placing a breakpoint in this function and using the "expressions" view. In that view you can test how to reference an object in the pointed and understand the structure of the object. 

    Thank you,

    Angie

  • Thanks Angie,

    I appreciate your patience. Your advice, suggestions and information shared were very useful. Cheers.

  • Hi Odera,

    I appreciate yours as well! There are many options in ccs and if you have any additional questions please feel free to make a new thread. 

    Thanks again,

    Angie