Hi Kyle,
Thank you for the answer.
yet ,I'll be more precise, I need the system to run without any uart communication or any cli interface.
Just as a standalone device.
I want to debug at ccs the detected track points.

Can you direct me on how to accomplish this ?
Thank you
Gil

Hi Kyle.for the purpose of debugging is there an issue with using conventional break point ?
Or because it's a task there will be obstacles ?
BR
Gil

Hi Kyle.
How are you?
following last question.

I want to run the people counting at debug mode.
and view the number of detect targets during running at debug mode.

1.Setup:
1.1. environment at c:\ti
bios_6_53_02_00
bios_6_73_01_01
ccsv8
ccs_base
dsplib_c64Px_3_4_0_0
dsplib_c674x_3_4_0_0
install_logs
mathlib_c674x_3_1_2_1
mmwave_automotive_toolbox_2_4_3
mmwave_industrial_toolbox_2_3_0
mmwave_industrial_toolbox_2_5_2
mmwave_industrial_toolbox_3_0_0
mmwave_sdk_01_00_00_05
mmwave_sdk_01_01_00_02
mmwave_sdk_01_02_00_05
mmwave_sdk_02_00_00_04
mmwave_sdk_02_01_00_04
mmwave_sdk_03_00_00_08
ti-cgt-arm_16.9.6.LTS
ti-cgt-c6000_8.1.3
uniflash_4.5.0
uninstallers
xdctools_3_32_02_25_core
xdctools_3_50_04_43_core
xdctools_3_50_08_24_core

1.2. people counting project at industrial_toolbox_2_3_0 (also tried 2_5_2)
using the cfg file at toolbox_2_3_0
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg 0 1 1 1
profileCfg 0 77 30 7 62 0 0 60 1 128 2500 0 0 30
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
frameCfg 0 1 128 0 50 1 0
lowPower 0 0
guiMonitor 1 1 0 0
cfarCfg 6 4 4 0 0 16 16 4 4 50 62 0
doaCfg 600 1875 30 1
SceneryParam -6 6 0.05 4
GatingParam 4 3 2 0
StateParam 10 5 10 100 5
AllocationParam 250 0.01 5 1 2
VariationParam 0.289 0.289 1.0
trackingCfg 1 2 250 20 200 50 90
sensorStart



2. Operation
2.1. optimization level:3 ,on both projects(mss,dss)
compilation passed on both projects.
!! The optimization level you suggested of OFF on both projects caused a malfunction.

2.2.(placed the jumper on SOP2->power cycle)->then,I've flashed the debug bin and then to target configuration file.
then ->turned off the device->removed SOP2 jumper->turn on.

2.3.launched the target configuration file->loaded the required ->connected the target to the group

2.4. per project loaded the required files
pplcount_16xx_mss\Debug\xwr16xx_pplcount_mss.xer4f /dss

2.5.set a hardware breakpoint at the function:void MmwDemo_appTask(UArg arg0, UArg arg1)
after
gtrack_moduleStep(gMmwMssMCB.gtrackHandle, points, variances, mNum, targetDescr, &tNum, targetIndex->index, benchmarks);

I used a volatile global variables to copy the value of
volatile int GtNum=0,GmNum=0;
void MmwDemo_appTask(UArg arg0, UArg arg1)
{
....
// Execute tracking
gtrack_moduleStep(gMmwMssMCB.gtrackHandle, points, variances, mNum, targetDescr, &tNum, targetIndex->index, benchmarks);

GtNum=tNum;
GmNum=mNum;

and added watch on GtNum GmNum which is updated by the ccs on continuous refresh.
2.6. clicked on the mss project and then on the Resume button (F8)
2.7. clicked on the dss project and then on the Resume button (F8)
2.8. connected the terminal of the CCS (view->terminal) which was already assigned to the Uart port (as appears in the device manager)
2.9. loaded manually the cfg file of the lab project (i got the word "done" replied per legal commands from the cfg file)
2.10.I managed to observe variables and more.
2.11. the number of targets at function MmwDemo_appTask allways remained ZERO (GtNum=tNum).also when the code was running without any break point-> continuously.

3. Problem
What is missing ? is it required to open another port for the uart of data ?
I only want to see the number of tracked targets.

Thank you for the cooperation .
Gil

Hello Gil,

Follow the mention thread it's may be help you to Hard-code Configuration e2e.ti.com/.../741521

Thanks,
Rahul

Hi Rahul.
I've noticed that when loading the device with the provided people_counting lab.bin file that came with the industrial toolbox 2.3.0
and the matlab exe file, there are point clouds on the screen.
BUT when compiling the project(dss and mss) for release and flashing the merged bin file (lab.bin), there are no point clounds on the matlab gui.
(also as in the debug.bin and running at debug mode)
Also the size of the release lab.bin file is around 5k[B] bigger than the toolbox lab.bin file.

please verify at your side and direct me.
Thank you
Gil