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-ODS: People Counting ES2.0

Part Number: IWR6843ISK-ODS
Other Parts Discussed in Thread: IWR6843, IWR1642

Hi there,

I've acquired a IWR6843ISK-ODS ES 2.0, and as I understand the Overhead People Detection Lab has not been updated to run on ES 2.0.

Some E2E posts point towards the 3D People Counting Lab, but the specified position for the radars in this lab is wall mounted.

Is there any way to modify this example to allow ceiling mount? maybe altering the parameters of dynamicRangeAngleCfg or dynamic2DAngleCfg ?

Also, is it possible to port the Overhead People Detection Lab available for ES 1.0 to the ES 2.0 boards?

Kind regards,

João Gomes

  • Hi João,

    The 3D People Counting Lab (ISK and ODS) is optimized for wall mount scenario so it is not recommended to use it for overhead applications. You can port the existing overhead people counting lab to ES2.0 using the instructions provided in the following migration guide.

    Migrating to IWR68xx and IWR18xx Millimeter Wave Sensors

    IWR6843 ES1.0 to ES2.0 migration is covered in section 2.

    Depending upon your application, if your goal is to track people (but accurate counting is not of concern), you can also look at the 68xx ISK_ODS - Area Scanner lab which works on IWR6843 ES2.0 and provides tracking and static object detection capabilities. 

    Regards

    -Nitin

  • Thanks for your reply.

    We have a need for a ceiling mounted application. Is there any way to recompile the Area Scanner Project or the 3D people counting in order to support a ceiling mounted IWR6843?

    What code should be changed in order to acheive this?

    Thanks

  • Also, I wasn't able to sucessfully run the application compiled for IWR6843 ES 2.0.

    When building ods_pplcount_dss_68xx I get the following warnings, although it finishes building:

    "../dss_mmw_linker.cmd", line 48: warning #10068-D: no matching section
    warning #10370-D: Possible codesize or performance degradation. Section ".text:MmwDemo_interFrameProcessing:dss_data_path.oe674" has calls to rts routines, but rts is placed out of range from call site at 0xe013e0, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.
    warning #10370-D: Possible codesize or performance degradation. Section ".text:MmwDemo_interFrameProcessing:dss_data_path.oe674" has calls to rts routines, but rts is placed out of range from call site at 0xe026a0, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.
    warning #10370-D: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr16xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x20002fa4, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.
    warning #10370-D: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr16xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x20002e80, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.

    If I try to run the GUI it outputs an error:

  • Hello,

    It appears that you have not followed some/all of the instructions provided in the migration guide for porting the application from IWR1642 to IWR6843. This is shown by your build log which still shows the 16xx libraries being linked .

    warning #10370-D: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr16xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x20002fa4, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.

    warning #10370-D: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr16xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x20002e80, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.
    Please make sure you carefully follow all the instructions provided in section 2.3.4 (table 5 which lists the changes required to port existing IWR1642 application code to IWR6843 ES2.0), including fixing the above mismatch which is mentioned in item 5 in this table (you'll need to modify the lib names to use the xwr68xx versions in the CCS projectspec as mentioned).
    Thanks
    -Nitin 
  • Thank you for the fast reply.

    Well I though the previous project didn't link IWR16xx libs, so I followed the 6843 ES 1.0 to 2.0 Migration Guide.

    After following the guide for porting IWR1642 application code to IWR6843 ES2.0 I am still getting some errors.

    Description	Resource	Path	Location	Type
    #10010 null: errors encountered during linking; "ods_pplcount_dss_68xx.xe674" not built	ods_pplcount_dss_68xx		 	C/C++ Problem
    <a href="processors.wiki.ti.com/.../10234">  null: unresolved symbols remain	ods_pplcount_dss_68xx		 	C/C++ Problem
    gmake: *** [all] Error 2	ods_pplcount_dss_68xx		 	C/C++ Problem
    gmake[1]: *** [main-build] Error 2	ods_pplcount_dss_68xx		 	C/C++ Problem
    gmake[2]: *** [ods_pplcount_dss_68xx.xe674] Error 1	ods_pplcount_dss_68xx		 	C/C++ Problem
    unresolved symbol _MmwDemo_fastCode_L1PSRAM_copy_table, first referenced in ./dss_main.oe674	ods_pplcount_dss_68xx		 	C/C++ Problem
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 11217	C/C++ Problem
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 11580	C/C++ Problem
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 11862	C/C++ Problem
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 12105	C/C++ Problem
    #10247-D null: creating output section ".demoSharedMem" without a SECTIONS specification	ods_pplcount_dss_68xx		 	C/C++ Problem
    #10247-D null: creating output section ".l1data" without a SECTIONS specification	ods_pplcount_dss_68xx		 	C/C++ Problem
    #10247-D null: creating output section ".l2data" without a SECTIONS specification	ods_pplcount_dss_68xx		 	C/C++ Problem
    #10247-D null: creating output section ".l3data" without a SECTIONS specification	ods_pplcount_dss_68xx		 	C/C++ Problem
    #10247-D null: creating output section "systemHeap" without a SECTIONS specification	ods_pplcount_dss_68xx		 	C/C++ Problem
    #179-D function "MmwDemo_rxChanPhaseBiasCompensationAzimElev" was declared but never referenced	dss_data_path.c	/ods_pplcount_dss_68xx	line 2627	C/C++ Problem
    #179-D variable "txOrder" was declared but never referenced	dss_data_path.c	/ods_pplcount_dss_68xx	line 2704	C/C++ Problem
    #552-D variable "firstMaxVal" was set but never used	dss_data_path.c	/ods_pplcount_dss_68xx	line 4196	C/C++ Problem
    

    I tried to follow all applicable steps in the guide, but something must still be wrongly configured.

    Is TI planning to release an updated vesion of this lab?

  • And from the MSS project there is a include that path that is incorrect:

    Invalid project path: Include path not found (C:\ti\mmwave_industrial_toolbox_4_1_0\radarDemo).	ods_pplcount_mss_68xx		pathentry	Path Entry Problem
    

    Which should be related to the error in DSS, am I correct?

    Thanks in advance

  • It seems there is some confusion. To port the 6843 ODS people counting lab from ES1.0 to ES2.0 silicon, you need to follow the instructions in the IWR6843 ES1.0 to ES2.0 migration section as I indicated originally. However, I saw the xWR16xx libs being linked in your build log, so thought you were working with IWR1642. Something doesn't seem right in your build environment or projects.

    Could you please create a new CCS workspace, start with a fresh install of mmWave Industrial Toolbox 4.1.0 and follow the migration steps to move from 6843 ES1.0 to 6843 ES2.0 and provide your build log?

    Regards

    -Nitin

     

  • Hi,

    I have reinstalled TI's Industrial Toolbok 4.0.1,started a new Workspace on another folder and re-imported the ods_pplcount_dss_68xx and ods_pplcount_,mss_68xx projects.

    First of all, when importing two DSS projects showup, I tested with both without noticing any difference.

    As said in the previous comment, these projects are effectively linking iwr16xx libraries, which is strange.

    First I changed the versions of mmWaveSDK and SYS/BYOS to versions 3.0.3.03 and 6.73.1.01, respectively.

    Even if I proceed to change the libraries to point to xwr68xx libs,it still outputs:

    Description	Resource	Path	Location	Type
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 11217	C/C++ Problem
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 11580	C/C++ Problem
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 11862	C/C++ Problem
     warning: statement is unreachable	.xdchelp	/ods_pplcount_dss_68xx	line 12105	C/C++ Problem
    #10068-D no matching section	dss_mmw_linker.cmd	/ods_pplcount_dss_68xx	line 48	C/C++ Problem
    #10370-D null: Possible codesize or performance degradation. Section ".text:MmwDemo_interFrameProcessing:dss_data_path.oe674" has calls to rts routines, but rts is placed out of range from call site at 0xe013e0, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.	ods_pplcount_dss_68xx		 	C/C++ Problem
    #10370-D null: Possible codesize or performance degradation. Section ".text:MmwDemo_interFrameProcessing:dss_data_path.oe674" has calls to rts routines, but rts is placed out of range from call site at 0xe026a0, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.	ods_pplcount_dss_68xx		 	C/C++ Problem
    #10370-D null: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr68xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x20002e80, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.	ods_pplcount_dss_68xx		 	C/C++ Problem
    #10370-D null: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr68xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x20002fa4, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.	ods_pplcount_dss_68xx		 	C/C++ Problem
    #179-D function "MmwDemo_rxChanPhaseBiasCompensationAzimElev" was declared but never referenced	dss_data_path.c	/ods_pplcount_dss_68xx	line 2627	C/C++ Problem
    #179-D variable "txOrder" was declared but never referenced	dss_data_path.c	/ods_pplcount_dss_68xx	line 2704	C/C++ Problem
    #552-D variable "firstMaxVal" was set but never used	dss_data_path.c	/ods_pplcount_dss_68xx	line 4196	C/C++ Problem
    

    Most of the other steps in the guide do not seem to apply.

    Can you confirm this or replicate the error,I think the DSS project is still linking to IWR1642 devices.

    Thanks

  • Any updates?

    Thanks

  • Hello,

    You are correct, the existing 68xx overhead people counting projects seem to be linking xwr16xx libraries which is incorrect and needs to be fixed. However, it still works on 6843 ES1.0 as the two devices are compatible on the ARM and DSP side.

    However, for ES2.0, you must link the xwr68xx libs to be compatible with the ES2.0 device.

    Thanks for bringing this to our attention, we will correct this in a future update.

    Please list the changes, referring to the corresponding items from the 6843 ES1.0 to ES2.0 migration guide. List all changes, the ones you've made as well as the ones you feel are not applicable.

    Thanks

    -Nitin 

  • However, for ES2.0, you must link the xwr68xx libs to be compatible with the ES2.0 device.
    
    

    Sorry, but can you describe how to properly do it?

    Thanks

  • Hi,

    All of the libraries are linked in CCS. Open CCS and do the following:

    1. Right click on the project -> Properties

    2. From properites, go to ARM Linker -> File Search Path

    3. The dialog box will show as below:

    4. Replace the library names with the 68xx version.

    Regards,

    Justin