• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 1728 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.

AWR1642BOOST: Tracking algorithm

Rabah Abilmona
Intellectual 350 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: MMWAVE-SDK, TIDEP-0090, SYSBIOS

Hello,

   I have recently bought the AWR1642boost and cannot find the tracking algorithm anywhere in the mmwave sdk version 1.01. I have seen from a post that a ".c " file called RADARDEMO_clusterTracker_priv.c should be included in the sdk, but it is not. 

  I need this Target tracking id to be sent through the uart so i know its one same target but with different velocities or angles but can't seem to find the tracking algo!

Can anyone help me with this issue?

Best Wishes 

  • 0
    TI__Mastermind 22155 points
    Hello Rabah Abilmona,
    The SDK is still evolving and demos with tracking algorithms are not yet included in the MMWAVE-SDK.
    The upcoming releases of the SDK may include the demos with tracking and clustering algorithm .


    -Raghu
  • 0 in reply to Raghunandan Kamath
    Intellectual 350 points
    Hello Raghu,

    I am trying to run the TIDEP-0090 package (following the user guide).
    Will the TIDEP-0090 Tracking package work for my app fine? Will i be able to extract the Target Object list with Tracking id and so forth?

    Rabah
  • 0 in reply to Rabah Abilmona
    Intellectual 350 points
    Hello again,

    I am getting these errors while trying to build from the command prompt.


    C:\ti\Trackingdemo\mmwave_demo_dev\radarDemo\chains\RadarReceiverEDMA_mmwSDK\mmw_TMDemo>gmake all
    Configuring RTSC packages...
    c:/ti/xdctools_3_50_00_10_core/xs --xdcpath="c:/ti/bios_6_52_00_12/packages;C:/ti/mmwave_sdk_01_01_00_02/packages" xdc.tools.configuro -t ti.targets.arm.elf.R4Ft -p ti.platforms.cortexR:IWR16XX:false:200 -r release -c C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.6.LTS -o mss/mmw_configPkg_xwr16xx mss/mss_mmw.cfg
    making package.mak (because of package.bld) ...
    generating interfaces for package mmw_configPkg_xwr16xx (because package/package.xdc.inc is older than package.xdc) ...
    configuring mss_mmw.xer4ft from package/cfg/mss_mmw_per4ft.cfg ...
    generating custom ti.sysbios library makefile ...
    Starting build of library sources ...
    making C:/ti/Trackingdemo/mmwave_demo_dev/radarDemo/chains/RadarReceiverEDMA_mmwSDK/mmw_TMDemo/mss/mmw_configPkg_xwr16xx/package/cfg/mss_mmw_per4ft.src/sysbios/sysbios.aer4ft ...
    gmake[1]: Entering directory `C:/ti/Trackingdemo/mmwave_demo_dev/radarDemo/chains/RadarReceiverEDMA_mmwSDK/mmw_TMDemo/mss/mmw_configPkg_xwr16xx/package/cfg/mss_mmw_per4ft.src/sysbios'
    cler4ft C:/ti/bios_6_52_00_12/packages/ti/sysbios/BIOS.c ...
    asmer4ft C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/arm/IntrinsicsSupport_asm.asm ...
    asmer4ft C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/arm/TaskSupport_asm.asm ...
    asmer4ft C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/arm/v7r/vim/Hwi_asm.sv7R ...
    asmer4ft C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/arm/v7r/vim/Hwi_asm_switch.sv7R ...
    asmer4ft C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/arm/exc/Exception_asm.asm ...
    asmer4ft C:/ti/bios_6_52_00_12/packages/ti/sysbios/family/arm/v7r/tms570/Core_asm.sv7R ...
    arer4ft BIOS.obj arm_IntrinsicsSupport_asm.obj arm_TaskSupport_asm.obj vim_Hwi_asm.obj vim_Hwi_asm_switch.obj exc_Exception_asm.obj tms570_Core_asm.obj ...
    gmake[1]: Leaving directory `C:/ti/Trackingdemo/mmwave_demo_dev/radarDemo/chains/RadarReceiverEDMA_mmwSDK/mmw_TMDemo/mss/mmw_configPkg_xwr16xx/package/cfg/mss_mmw_per4ft.src/sysbios'
    Build of libraries done.
    cler4ft package/cfg/mss_mmw_per4ft.c ...
    Finished configuring packages

    [R4 Device/Type: iwr16xx/xwr16xx] Building file: mss/mss_main.c
    "mss/mss_main.c", line 513: error: struct "MMWave_CtrlCfg_t" has no field "freqLimitLow"
    "mss/mss_main.c", line 514: error: struct "MMWave_CtrlCfg_t" has no field "freqLimitHigh"
    "mss/mss_main.c", line 562: error: union "<unnamed>" has no field "fullControlCfg"
    "mss/mss_main.c", line 630: error: struct "MMWave_CalibrationCfg_t" has no field "enableCalibration"
    "mss/mss_main.c", line 631: error: struct "MMWave_CalibrationCfg_t" has no field "enablePeriodicity"
    "mss/mss_main.c", line 632: error: struct "MMWave_CalibrationCfg_t" has no field "periodicTimeInFrames"
    "mss/mss_main.c", line 908: error: a value of type "void (*)(uint16_t, uint16_t, uint16_t, uint8_t *)" cannot be assigned to an entity of type "MMWave_eventFxn"
    "mss/mss_main.c", line 914: error: a value of type "void (*)(void)" cannot be assigned to an entity of type "MMWave_startFxn"
    8 errors detected in the compilation of "mss/mss_main.c".

    >> Compilation failure
    gmake: *** [obj_xwr16xx/mss_main.oer4f] Error 1

    Can you help with these Raghu?
  • 0 in reply to Rabah Abilmona
    Intellectual 350 points
    Hi,
    The last post was resolved when selecting the correct sdk. But i can not seem to make the mmw_demo function to work on either the CMD prompt or on the Matlab 2017a.

    On the cmd the error is always unable to locate the runtime 9.1.
    On the Matlab 2017a , the error is Undefined variable "mmw_tm_demo" or class "mmw_tm_demo.cfg".

    Can i have some pointers here?

    Regards again

    Rabah
  • 0 in reply to Rabah Abilmona
    TI__Mastermind 22155 points

    Hello Rabah,

    Please refer to TIDEP-0092 .

    There is SRR TI Design which is updated with clustering and tracking algorithms.

    Hope this helps your understanding and development.

    Thanks,

    -Raghu

  • 0 in reply to Raghunandan Kamath
    Intellectual 350 points
    Hi Raghu,

    My question is about finding the new data structure sent over the uart after adding the tracking algorithm. I will be using the TIDEP-0090 since its not for short range. Finding the data sent over uart in the sdk from "C:\ti\mmwave_sdk_01_00_00_05\packages\ti\demo\xwr16xx\mmw\docs\doxygen\html " does not contain the tracking information.

    How can i find the new data structure sent to the UART for the TIDEP-0090 with the tracking info ?

    Rabah