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.

CCS/IWR6843ISK: Porting ODOC demo on IWR6843

Part Number: IWR6843ISK
Other Parts Discussed in Thread: IWR6843, AWR1642BOOST, AWR6843

Tool/software: Code Composer Studio

Hi,

  I am trying to work ODOC demo on IWR6843. For that, I am using the latest automotive tool Box (3.2.0), lab05(ODOC).

But it is having pre-built-binaries and ccs project for AWR1642BOOST board.

Can you please provide the procedure to compile ODOC demo on IWR6843?

Thanks,

Vijay.

  • Hi Vijay,

    Please follow the migration guide given below and look under section 2.3 Migrating From xWR1642 to xWR6843 ES2.0.

    Migrating to xWR68xx and xWR18xx Millimeter Wave (Rev. B)

    As an example, look at the Occupancy and Vital Signs Detection demo in the Automotive toolbox which supports both 16xx and 68xx devices. After understanding the information in the above Migration guide, you can refer to this demo and compare the differences between

    1. The 16xx and 68xx projectspec files to understand the required build related changes
    2. and the source related differences for the two devices and make the corresponding changes in the desired demo.

    Regards

    -Nitin

  • Hi Nitin,

       Thank you for the reply.

    With the help of migration document, i am able to port from xwr1642 to xwr6843, but when I try to build the dss, I get an error.

    Kindly find the attachment file for error log.

    Thanks and regards,

    Vijaya Krishna.

    **** Build of configuration Debug for project odoc_68xx_dss ****
    
    "C:\\ti\\ccs930\\ccs\\utils\\bin\\gmake" -k -j 4 all -O 
     
    rm -f C:/CCS_Wrk_Spc/CANFD_68/odoc_68xx_dss/xwr68xx_odoc_dss.bin
    makefile:194: recipe for target 'pre-build' failed
    process_begin: CreateProcess(NULL, rm -f C:/CCS_Wrk_Spc/CANFD_68/odoc_68xx_dss/xwr68xx_odoc_dss.bin, ...) failed.
     
    gmake[1]: [pre-build] Error 2 (ignored)
     
    Building file: "../dss_mmw.cfg"
    Invoking: XDCtools
    "C:/ti/xdctools_3_50_04_43_core/xs" --xdcpath="C:/ti/bios_6_73_01_01/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C674 -p ti.platforms.c6x:AWR68XX:false:600 -r release -c "C:/ti/ccs930/ccs/tools/compiler/ti-cgt-c6000_8.3.5" "../dss_mmw.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring dss_mmw.xe674 from package/cfg/dss_mmw_pe674.cfg ...
    The AWR68XX device is not currently supported.
    The following devices are supported for the C674 target:
    	TMS320C6670
    	TMS320DA830
    	DM37XX
    	TMS320TI816X
    	DRA7XX
    	AWR16XX
    	J7ES
    	Kepler
    	TMS320TCI6634
    	TMS320TCI6636
    	TMS320TCI6638
    	TMS320TCI6608
    	TMS320TCI6614
    	TMS320TCI6616
    	TMS320TCI6618
    	TMS320TCI6630K2L
    	TMS320C66AK2H06
    	TMS320C66AK2H12
    	TMS320C66AK2E02
    	TMS320C66AK2E05
    	TCI66AK2G02
    	TMS320C6654
    	TMS320C6655
    	TMS320C6657
    	TMS320C6671
    	TMS320C6672
    	TMS320C6674
    	TMS320C6678
    	TMS320CDM740
    	TMS320C6A8149
    	TMS320C6A8168
    	TMS320TI811X
    	TMS320TI814X
    	TMS320DM8148
    	TMS320DM8168
    	Arctic
    	TMS320DA802
    	TMS320DA803
    	TMS320DA804
    	TMS320DA805
    	TMS320DA807
    	TMS320DA808
    	TMS320DA810
    	TMS320DA828
    	TMS320C6747
    	TMS320C6745
    	TMS320C6743
    	OMAPL137
    	OMAPL108
    	OMAPL118
    	OMAPL138
    	TMS320DA840
    	TMS320DA850
    	TMS320C6742
    	TMS320C6746
    	TMS320C6748
    	Vayu
    	TDA3XX
    	IWR16XX
    	AWR18XX
    	IWR18XX
    	IWR68XX
    subdir_rules.mk:19: recipe for target 'build-436091585-inproc' failed
    js: "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c64p/Settings.xs", line 210: Error: Unsupported device!
        "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c64p/Settings.xs", line 236
        "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/Settings.xs", line 174
        "C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/Settings.xs", line 126
        "C:/CCS_Wrk_Spc/CANFD_68/odoc_68xx_dss/dss_mmw.cfg", line 15
        "./package/cfg/dss_mmw_pe674.cfg", line 184
    gmake.exe: *** [package/cfg/dss_mmw_pe674.xdl] Error 1
    js: "C:/ti/xdctools_3_50_04_43_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake[2]: *** [build-436091585-inproc] Error 1
    gmake[1]: *** [build-436091585] Error 2
    gmake[1]: Target 'main-build' not remade because of errors.
    gmake: *** [all] Error 2
    subdir_rules.mk:16: recipe for target 'build-436091585' failed
    makefile:160: recipe for target 'all' failed
    
    **** Build Finished ****

  • Hi Vijay,

    Please compare your DSS projectspec with the one given in the Occupancy and Vital Signs Detection demo referenced above and check that the device ID matches as given below.

    device="IWR6843"

    Additionally, please make sure you are using CCS 8.3.1 or above.

    Regards

    -Nitin

  • Vijay,

    Confirming what I mentioned above, I notice in your error log that you are using AWR6843. Please change it to IWR6843 as mentioned above and this error should be resolved.

    Thanks

    -Nitin

  • Nitin,

    I can able to build DSS project after changing platform from AWR6843 to IWR6843,

    but still facing build issues in MSS project. I have attached the screenshot, build hangs at 41%.

  • Hi Vijay,

    There appears to be a typo in your mss projectspec postbuild steps. The RadarSS firmware filename is incorrect as highlighted below which causes the metaimage generator to hang. This should be xwr6xxx_radarss_rprc.bin. Please double check the rest of the post build step commands to make sure there are no errors in those.

    -Nitin

  • Nitin,

    Thanks, I am able to build MSS project and running demo application in debug mode but encounter the below error.

    Regards,

    Vijay

  • Hi Vijay,

    You can decode this error by following the instructions in the following training.

    Easy evaluation and development of mmWave systems with software development kit - Section "Software Development and Debugging". Look at slide 46 (mmWave Errors)

    Please note that since the demo you're porting does not print out the mmWave and Subsystem errors separately, but the bitmap is still the same as given in this slide so you can extract the error accordngly. You can also call MMWave_decodeError on this error in the code to print out the error components separately and then follow the example provided in the above slide. Yyou can refer to the out of box demo code to understand how to call MMWave_decodeError.

    Thanks

    -Nitin