• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 31 subscribers
  • Views 1844 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.

AWR1843BOOST: Running the Vital Signs Lab

No Onon
Prodigy 20 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843, , IWR1443, AWR1642

My end goal here is to get the Vital Signs Lab designed for the IWR1443 working on the AWR1843BOOST EVM that I currently have. I have gone through the code and made many changes, but haven't been able to successfully compile the project. Would someone be so kind as to list out everything that needs to be changed to get this lab to run on the AWR1843?

Thanks,

Adam

  • 0
    TI__Guru*** 149044 points

    Hi

    We recommend you run the Vital Signs Lab designed for the AWR1642 on the AWR1843BOOST EVM.

    Porting the  Vital Signs IWR1443 implementation on the AWR1843 will require more effort and it is beyond the support our team can provide

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 20 points

    Hi Cesar,

    I looked in the industrial toolbox and couldn't find the project built for the AWR1642, are you possibly referring to the Automotive Toolbox Occupancy and Vital Signs Detection Lab? I haven't looked into detail about this lab but I don't think it fits our use case quite as well. Here is what I can see in the industrial toolbox:

    EDIT: I believe you are talking about the Driver Vital Signs Lab? Please let me know if this is the case, I will look into it further. But again, I would like to know what I need to change to get it to run on the 1843.

    Thanks,

    Adam

  • 0
    TI__Guru*** 149044 points
    Yes, it is in the Automotive toolbox

    Thank you
    Cesar
  • 0 in reply to Cesar
    Prodigy 20 points

    Hi Cesar,

    Right, I found the Driver Vital Signs lab in the automotive toolbox, but what changes do I need to make to compile and run it on the AWR1843BOOST?

    Thank you,

    Adam

  • 0
    TI__Guru*** 149044 points
    It should not need any change

    You can flash the binaries and run it

    Thank you
    Cesar
  • 0 in reply to Cesar
    Prodigy 10 points

    Wow, I can't say I expected that to work...I'd appreciate a short explanation as to why a binary built for the 1642 runs on the 1843.

    Also perhaps a more pressing issue, the code included in the 2.9 automotive toolbox for the "Driver Vital Signs" lab does not seem to be building, even though I haven't changed anything. Is this something wrong with what I have installed or something wrong with the toolbox itself? Build log attached.

    Thanks,

    Adam

    Fullscreen vitalSigns_16xx_mss_build_log.txt Download 
    **** Build of configuration Debug for project vitalSigns_16xx_mss ****

"C:\\ti\\ccs920\\ccs\\utils\\bin\\gmake" -k -j 12 all -O 
 
rm -f C:/Users/Gallium/workspace_v9_2/vitalSigns_16xx_mss/vitalSigns_16xx_mss.bin
makefile:186: recipe for target 'pre-build' failed
process_begin: CreateProcess(NULL, rm -f C:/Users/Gallium/workspace_v9_2/vitalSigns_16xx_mss/vitalSigns_16xx_mss.bin, ...) failed.
 
gmake[1]: [pre-build] Error 2 (ignored)
 
Building file: "../mss_mmw.cfg"
Invoking: XDCtools
"C:/ti/xdctools_3_50_08_24_core/xs" --xdcpath="C:/ti/bios_6_73_01_01/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.R4F -p ti.platforms.cortexR:AWR16XX:false:200 -r debug -c "C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS" --compileOptions "--enum_type=int " "../mss_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 mss_mmw.xer4f from package/cfg/mss_mmw_per4f.cfg ...
generating custom ti.sysbios library makefile ... 
Starting build of library sources ...
making C:/Users/Gallium/workspace_v9_2/vitalSigns_16xx_mss/src/sysbios/sysbios.aer4f ...
gmake[1]: Entering directory `C:/Users/Gallium/workspace_v9_2/vitalSigns_16xx_mss/src/sysbios'
cler4f C:/ti/bios_6_73_01_01/packages/ti/sysbios/BIOS.c ...
asmer4f C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/IntrinsicsSupport_asm.asm ...
asmer4f C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/TaskSupport_asm.asm ...
asmer4f C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/v7r/vim/Hwi_asm.sv7R ...
asmer4f C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/v7r/vim/Hwi_asm_switch.sv7R ...
asmer4f C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/exc/Exception_asm.asm ...
asmer4f C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/arm/v7r/tms570/Core_asm.sv7R ...
arer4f 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:/Users/Gallium/workspace_v9_2/vitalSigns_16xx_mss/src/sysbios'
Build of libraries done.
cler4f package/cfg/mss_mmw_per4f.c ...
Finished building: "../mss_mmw.cfg"
 
Building file: "../mss_main.c"
Invoking: ARM Compiler
"C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/bin/armcl" -mv7R4 --code_state=16 --float_support=VFPv3D16 -me -O3 --include_path="C:/Users/Gallium/workspace_v9_2/vitalSigns_16xx_mss" --include_path="C:/ti/mmwave_sdk_03_03_00_03" --include_path="C:/ti/mmwave_sdk_03_03_00_03/packages" --include_path="C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/include" --define=_LITTLE_ENDIAN --define=SOC_XWR16XX --define=SUBSYS_MSS --define=DOWNLOAD_FROM_CCS --define=MMWAVE_L3RAM_SIZE=0x40000 --define=DebugP_ASSERT_ENABLED -g --c99 --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --enum_type=int --abi=eabi --preproc_with_compile --preproc_dependency="mss_main.d_raw" --cmd_file="configPkg/compiler.opt" "../mss_main.c"
 
>> Compilation failure
subdir_rules.mk:9: recipe for target 'mss_main.obj' failed
"../mss_main.c", line 561: warning #169-D: argument of type "int32_t *" is incompatible with parameter of type "rlCalibrationData_t *"
"../mss_main.c", line 561: error #167: too few arguments in function call
1 error detected in the compilation of "../mss_main.c".
gmake[1]: *** [mss_main.obj] Error 1
Building file: "../cli.c"
Invoking: ARM Compiler
"C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/bin/armcl" -mv7R4 --code_state=16 --float_support=VFPv3D16 -me -O3 --include_path="C:/Users/Gallium/workspace_v9_2/vitalSigns_16xx_mss" --include_path="C:/ti/mmwave_sdk_03_03_00_03" --include_path="C:/ti/mmwave_sdk_03_03_00_03/packages" --include_path="C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/include" --define=_LITTLE_ENDIAN --define=SOC_XWR16XX --define=SUBSYS_MSS --define=DOWNLOAD_FROM_CCS --define=MMWAVE_L3RAM_SIZE=0x40000 --define=DebugP_ASSERT_ENABLED -g --c99 --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on --enum_type=int --abi=eabi --preproc_with_compile --preproc_dependency="cli.d_raw" --cmd_file="configPkg/compiler.opt" "../cli.c"
gmake[1]: Target 'main-build' not remade because of errors.
gmake: *** [all] Error 2
Finished building: "../cli.c"
 
makefile:152: recipe for target 'all' failed

**** Build Finished ****

  • 0 in reply to Nony Mous
    TI__Guru*** 149044 points

    "a short explanation as to why a binary built for the 1642 runs on the 1843."

    The reason is that the AWR1843 device is a superset of AWR1642. The main difference between the devices is that the AWR1843 has 3Tx, more memory and higher IF bandwidth. None of these features affect the vital signs since this application uses only 1Tx

    "in the 2.9 automotive toolbox for the "Driver Vital Signs" lab does not seem to be building"

    Please make sure that the mmwave SDK mentioned in the release notes is installed"

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 20 points

    Hi Cesar,

    Thanks for clearing that up, I downloaded the required SDK and am able to currently able to build the project now. My last question is what are the main differences between the Industrial Vital Signs Lab and the Driver Vital Signs Lab?

    Thanks,

    Adam

  • 0 in reply to Adam Ali
    TI__Guru*** 149044 points

    The Driver Vital Signs supports sensor in front or back.

    The DVS is implemented on the DSP, so the code is easier to understand

    Closing the thread now

    Thank you

    Cesar