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.

AWR6843AOPEVM: DSP demo for this evm

Part Number: AWR6843AOPEVM
Other Parts Discussed in Thread: AWR1843BOOST, AWR6843AOP, , UNIFLASH

Hi, I get the awr6843aop and I just figure out that unlike the awr1843boost it does not have demo utilizing DSP of awr6843aop I load the ISK demo and its worked but the data is not in correct direction I read the question which asked in this community and they said the antenna geometry is different My QUSTION IS how could I find the antenna configuration in demo code and more how could I change it?

I import this project from industrial toolbox and compile it

Thank you

  • Hello

    You may want to look at the  Angle of Arrival  or DoA blocks in the  OOB (DSP) demo to understand how it is being computed for ISK  antenna type array and change to ODS type.

    Things to review and understand:

    OOB demo doxygen files under sdk installation  for details of various processing blocks

    Concepts of Antenna array and how angle is computed for FMCW data.

    Antenna  array and phase  orientation on Antenna/EVM of interest

    If you would like to see DSP based point cloud you may want to try Area scanner demo as these utilize the DSP on xWR6843 devices :

    Is there any specific reason you have been looking for DSP usage on AWR6843AOPEVM
    Thank you,
    Vaibhav

  • Hi, thank you for your reply

    I need to have the all point cloud, without group picking base on snr and do clustering by other algorithm like k means ( some modified one of it)  but as number of points increase the CPU load increase and in some situation especially when there is tall building with reflective facades( I am not sure about "facades" word what I mean is the face of building) the number of point increases and SOC stop sending any information even I could not connect it again until I power cycle it ( I believe it maybe  because of the stack (unlikely) or because of  MCU limitation which delay in calculation  cusec RTOS stop everything and enter in error).

    I will check the Area scanner ( I did not pay attention to it thank you for point to this), what I want is like demo code there be a CLI I cloud configure the sensor RF front end and get the 
    whole point cloud I do my calculation ( JPDA tracker and clustering ) in other MCU.

    again (very very very very)*e^(e^(inf!)) ... thank you for your reply.
  • Hi,

    If you are looking for the exact out of box demo but with the DSP on the AOP device, I would reccomend you approach this by comparing the HWA version of 68xx with the HWA version of AOP, then implement similar changes to the DSP version of 68xx in order to create an AOP+DSP version. Let me know if you have any specific issues.

    Best Regards,
    Alec

  • Hi, Thank you for reply 

    yes , I'm working on that I trying to find the flow inside the code( I mean I know what is the logic and flow of software(code) but I'm trying to find it in code) just please don't close the question in case of a question about the code change because it will take a while.

    very very very thank you!

  • Hi, 

    Understood, will leave this thread open for additional queries you may have.

    Best Regards,
    Alec

  • Hi 

    I just could check the code and I finished it I figure out these things:

    /*************************Things I Figure Out*************************************************************************************************************************

    1: the "static void MmwDemo_transmitProcessedOutput" is the function of task which is responsible to send the data to USART  with polling mode ( line1352 of code mss_main in area scanner ).

    2: unlike the demo code have two type of object 1 : static object. 2 : dynamic object

    2': static objects are in cartesian (x y z) which is easy to understand by human and easy to represent.

    2'': dynamic  objects  are in spherical and it make sense because later code will pass this objects to gtracker ( it is code by TI which implement EKF(extended kalman filter ) and some method for association in EKF we need to have objects in  spherical  because the model is base on this detail are in document name is "Tracking radar targets with multiple reflection points") .

    3: It have CLI code and code use this to get the configuration for tracking and RF front.

    /**************************************************************************************************************************************************************************

    /**************************The Problem *********************************************************************************************************************************

    so base on the above I have everything I want but there is a problem in cfg file (screenshot below)

    CFG file

    we send the boundary boxes (bins) and more we have static detection cfg I do not know each parameter meaning I mean from 'TRACKING COMMANDS' to end of 'STATIC DETECTION COMMANDS' is mystery for me.

    /**************************************************************************************************************************************************************************

    /***************************My Questions******************************************************************************************************************************** 

    __Is this parameter effect the static and dynamic objects data (in other word do they effect sensor detection)?

    __Where could I find the  meaning of each parameter from mystery part?

    __And how could I bypass the tracker ? because after that I will have pure unaffected point cloud that I need?

    /************************End Of My Questions***************************************************************************************************************************

     excuse me for writing detail (and that long story) I did because of two reason  first : show how much I'm intermediated in this and second :if anyone like me read this to understand the whole story.

    Thank you for your replies 'Alec' and 'Vaibhav' they was very helpful and just solved half of my problem.  

    I will research this problem  but if anyone know about this question PLEASE help about them thank you. 

  • An update I compiled the area scanner code from the Industrial toolbox with CCS but when I upload it to AWR6843AOP its not working.

    I upload the precompiled binary and it works. I did attach the code and binary that I get from compiling this lab in CCS.

    I tired just upload the mss binary (as I do for other mmwave sensor) but I upload(to internet not to sensor) dss binary too.(In other word I just give mss binary to uniflash)

    I did not change anything in code I just import it and compile it.  I upload a screenshot about software I use the CCS version is 11.

    binary.rar is binary file and whole code is the code I have it in my CCS workspace.

    binary.rarwhole code.rar

    The software information screenshot :

  • Hi,

    Just to confirm, did you build the DSS project before building the MSS project? When using the DSP, the final binary is formed in a post-build step which combines both the DSS and MSS binaries, so the DSS project must be built beforehand.

    Best Regards,
    Alec

  • Hi, Thank you for reply

    Yes I did I upload video in here that show the step I take.

    I don't have debugger for this EVM and I do not know where the code is stuck.

    My COM ports are like this:

  • Hi,

    There may be an issue with Area Scanner in the mmWave Industrial Toolbox 4.9.0, could you please try with Industrial Toolbox 4.8.0? Functionality should be the same.

    Best Regards,
    Alec

  • Hi,

    Sure I will try it and write the result here.

    Thank you Alec.

  • Hi,

    Additionally, we have just made a post regarding this issue for Industrial Toolbox 4.9.0 and how to fix it, so feel free to take a look at the following post if that solution is preferable.

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1060254/faq-iwr6843-industrial-toolbox-version-4-9-0---lab-fails-to-run-after-building


    Best Regards,
    Alec

  • Hi,

    Yes that was the problem I can  get data from EVM easily now.

    Thank you very much you are a life saver!

  • Hi ,again just a small question do you know any document that describe demo code? I mean the lines of code things happens? I could not find the gtracker in code.

  • Hi,

    If you are looking for information specifically on GTrack, take a look at the documentation under <mmwave_industrial_toolbox>/labs/people_counting/docs as these labs rely heavily on the tracker. You can also look under <mmWave SDK>\packages\ti\alg\gtrack\docs . If you are just trying to understand the processing for Area Scanner better, I would recommend that you start with the following two files, as they coordinate most of the processing:

    <mmwave Industrial Toolbox>/labs/common/src/dpc/objectdetectionandtracking/objdetrangehwa/src/objdetrangehwa.c

    <mmwave Industrial Toolbox>/labs/common/src/dpc/objectdetectionandtracking/staticobjdetdsp/src/objectdetection.c

    Best Regards,
    Alec

  • Hi, Thank you for reply

    I just had brief view to the code you suggest they are complicated and just if it possible give me time to figure it out. for Gtrack document I read that it has very good documented  but nothing about code even no flowchart for that. something in TI codes is missing and it is logic diagram (flowchart like) for demo there is one and it is very useful even there is a video that talk about the SDK (I have not seen it yet) but the document (that first html page) was very good.

    just if it is possible keep this thread open I really need that. Thank you.