CCS/IWR1642BOOST: Sensors forum

Miroslav Rujzl

Part Number: IWR1642BOOST
Other Parts Discussed in Thread: MATHLIB, UNIFLASH

Tool/software: Code Composer Studio

Hi guys,

I still solve my problem with People Counting Demo (PCD). I'm trying to compile source codes that were available at TI-REX. Project pplcount_16xx_dss can build succesfully. The second project pplcount_16xx_mss can't build. CCS says:

#167 too few arguments in function call mss_main.c /pplcount_16xx_mss line 407 C/C++ Problem
gmake: *** [all] Error 2 pplcount_16xx_mss C/C++ Problem
gmake[1]: *** [mss_main.oer4f] Error 1 pplcount_16xx_mss C/C++ Problem
gmake[1]: Target 'main-build' not remade because of errors. pplcount_16xx_mss C/C++ Problem

There is a command which is on the line 407.

if (MMWave_open(gMmwMssMCB.ctrlHandle, &gMmwMssMCB.cfg.openCfg, &errCode) < 0)

Last time when I asked, I gave the suggestion to check all components from PCD User Guide. There are my components.

bios_6_73_01_01
Code Composer Studio
dsplib_c64Px_3_4_0_0
dsplib_c674x_3_4_0_0
Folder with projects DSS and MSS
mathlib_c674x_3_1_2_1
mmwave_industrial_toolbox_4_1_0
mmwave_sdk_03_02_01_02
ti-cgt-arm_16.9.6.LTS
ti-cgt-c6000_7.4.16
tirex-product-tree
uniflash_5.1.0
xdctools_3_50_08_24

All components are deposited in same folder C:\ti.

My question is where I find working projects DSS and MSS or how to repair source codes for succesfull build.

Thank you for answer,

Mirek

over 5 years ago

0 Justin Curewitz over 5 years ago

TI__Mastermind 28055 points

Hi Mirek,

MMWave_Open is defined in the SDK. You have a newer version of the SDK which has more arguments in this function call then previous versions. Please download version 1.2.0.5 of the SDK as listed in the user's guide. http://software-dl.ti.com/ra-processors/esd/MMWAVE-SDK/01_02_00_05/index_FDS.html

Regards,

Justin

0 Miroslav Rujzl over 5 years ago in reply to Justin Curewitz

Prodigy 70 points

Hi Justin,

thank you for your recommendation. Version 1.2.05 doesn't work, but version 2.0.0.4 is correct.

Now, I'm trying to modify the sensorStop command for correct using. After the sending this command, console in CCS debugger says:

[Cortex_R4_0] Debug: MMWDemoMSS Received CLI sensorStop Event
Error: Asynchronous Event SB Id 15 not handled
[C674X_0] Debug: MMWDemoDSS Received STOP Event
Error: Asynchronous Event SB Id 15 not handled
Debug: MMWDemoDSS Data Path stop succeeded

What this error means?

Thank you for your answer,

Mirek

0 Justin Curewitz over 5 years ago in reply to Miroslav Rujzl

TI__Mastermind 28055 points

Hi Mirek,

Basically, when you send sensorStop, the cli.c file receives this command, and posts an event. In mss_main.c, this event is received, and the mss calls MmwDemo_mssDataPathStop(). This uses the mmwave api to call MMWave_stop(), which stops the device. The BSS sends out the SB ID 15 when it stops, (see AWR1xxx_Radar_Interface_Control.pdf) in the mmWave DFP.

Simply search the mss_main.c for the phrase "Error: Asynchronous Event" and you will see that this is a mailbox message from the BSS that is not getting handled - but BSS has stoppped.

Regards,

Justin

0 Justin Curewitz over 5 years ago in reply to Justin Curewitz

TI__Mastermind 28055 points

Hi Mirek,

Since you are now compiling the demo, your original question has been answered so I am closing this thread.

Regards,

Justin