• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 247 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

AWR1642BOOST: Standalone Vital Sign Alarm System Using AWR1642BOOST – Hardware and Software Requirements

IWRL6432BOOST: IWRL6432BOOST Hard coding

Jules Garsault
Prodigy 50 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: IWRL6432, UNIFLASH, SYSCONFIG

Tool/software:

Hi, 

Could you please guide me on how to hardcode the IWRL6432BOOST for the Vital Signs Lab with people tracking? I found a document in the Resource Explorer that explains the steps for the 68xx series. From my understanding, the process should be similar for the 6432. However, I got confused as the documentation appears to focus on the "Out of the Box" demo, whereas I want to implement Vital Signs hardcoded.

Additionally, could you assist me in locating the necessary files for hardcoding (such as the CLI) for this setup?

Thank you in advance for your help.

Best regards,

  • 0
    TI__Genius 10660 points

    Hi

    You can use the below demo for IWRL6432 Vital signs

    radar_toolbox_2_20_00_05\source\ti\examples\Medical\IWRL6432_Vital_Signs\src

    You can find the configuration file at the below location

    radar_toolbox_2_20_00_05\source\ti\examples\Medical\IWRL6432_Vital_Signs\chirp_configs\Vital_Signs_With_Tracking_BOOST.cfg

    For hardcoding the limits of breath rate and heart rate, you can modify in the file vitalsign.c in 

    radar_toolbox_2_20_00_05\source\ti\examples\Medical\IWRL6432_Vital_Signs\src

    Regards

  • 0 in reply to Abhishek Karkisaval
    Prodigy 50 points

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    /*
    * Copyright (C) 2022-24 Texas Instruments Incorporated
    *
    * Redistribution and use in source and binary forms, with or without
    * modification, are permitted provided that the following conditions
    * are met:
    *
    * Redistributions of source code must retain the above copyright
    * notice, this list of conditions and the following disclaimer.
    *
    * Redistributions in binary form must reproduce the above copyright
    * notice, this list of conditions and the following disclaimer in the
    * documentation and/or other materials provided with the
    * distribution.
    *
    * Neither the name of Texas Instruments Incorporated nor the names of
    * its contributors may be used to endorse or promote products derived
    * from this software without specific prior written permission.
    *
    * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
    * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Dear Abhishek,

    I hope this message finds you well. I am working with the IWRL6432BOOST EVM and have been following the steps outlined in the Hard Coded Config User Guide to implement hardcoded configurations for the radar sensor: https://dev.ti.com/tirex/explore/node?a=1AslXXD__1.00.01.07&node=A__ACJ8xoQdpNpVq3e4C.mnUQ__radar_toolbox__1AslXXD__LATEST&r=1AslXXD__1.00.00.26

    Here are the steps I have followed so far:

    1. I imported the Vital Signs project for the IWRL6432BOOST into CCS from the Radar Toolbox.
      The project path is:
      radar_toolbox_2_20_00_05\source\ti\examples\Medical\IWRL6432_Vital_Signs\src

    2. I modified the mmw_cli.c file to include hardcoded commands from the configuration file and Replaced UART Read 
      radar_toolbox_2_20_00_05\source\ti\examples\Medical\IWRL6432_Vital_Signs\chirp_configs\Vital_Signs_With_Tracking_BOOST.cfg

    3. Build the project, convert the .OUT file to bin using Multicore Image Generator

    4. flash the EVM using uniflash

      My goal is to modify the CLI so the radar sensor can operate autonomously on power on without the need to send configuration commands through a PC every time.

    However, I am encountering issues related to the .out file size and flashing errors in UniFlash. Below is a summary of the problems:

    Issue Faced:

    I encountered errors when trying to flash the .appimage or .bin file generated from the .out file. The .out file size is 1.7 MB, which is much larger than expected, causing issues during flashing. Typically, I expect the .appimage file to be around 220 KB. (as for the vital sign appimage file from the dmo)

    Questions:

    1. Are there any specific settings or steps I might have missed in the hardcoding process for the Vital Signs Lab?

    2. In your previous response, you mentioned modifying the vitalsign.c file to hardcode the limits for breath rate and heart rate. Should these changes in vitalsign.c be made in addition to the modifications I have already made in the mmw_cli.c file, or are they a separate step entirely

    3. Based on the following post, are there any additional steps that are not included in the Hard Coded Config User Guide?specially regarding sysconfig ?? I am a bit confused.  https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1346009/iwrl6432boost-hard-coded-config-for-mmwave_l_sdk_05_04_00_01?tisearch=e2e-sitesearch&keymatch=Hard%2520Coded%2520Config%2520User%2520Guide#

    4. I also find following question regarding hardcoding of the IWRL6432BOOST, however here it is suggested to search for  CLI_BYPASS, to define that variable and set "radarCmdString", this also confused me . I dont know which guid I should follow.
      https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1363575/awrl6432aop-how-to-do-hard-code-config-in-xwrl6432?tisearch=e2e-sitesearch&keymatch=IWRL6432%2525252520hard%2525252520code%2525252520vital#

    5. Could you provide guidance on how to further optimize the build to reduce the .out file size? if it is necessary 

    6. Are there any known issues or limitations with flashing larger .appimage files on the IWRL6432BOOST EVM?

    I have also attached the code in my mmw_cli.c file for your reference. Could you please review it to confirm whether the modifications I made are correct?

    Thank you very much for your time and assistance. I look forward to your guidance on these matters.

    Best regards,
    Jules



    PS:

    Steps Followed to Modify the CLI File for Hardcoded Configuration

    1. Added a Macro:
      Defined a macro at the top of the file to enable the use of hardcoded configuration commands.

    2. Defined Configuration Commands:
      Created a list of configuration parameters (as they appear in the .cfg file) inside the file. This included commands like sensorStop, dfeDataOutputMode, and others.

    3. Initialized Hardcoded Config Index:
      Added code to initialize an index for looping through the configuration commands, with a delay for system initialization. Also included UART prints for better clarity during execution.

    4. Replaced UART Read with Hardcoded Commands:
      Inside the main loop, replaced the standard UART read functionality with a loop that runs through the hardcoded configuration commands and executes them one at a time.

    5. Fallback to UART Communication:
      Added a fallback mechanism that reverts to the standard UART communication if the hardcoded configuration functionality is turned off.

  • 0 in reply to Jules Garsault
    TI__Genius 10660 points

    Hi

    If you want to hard code the configuration then you must modify the  mmw_cli.c. You need to use the CLI bypass function and read the CLI from a file. You can refer to the video doorbell demo(2 pass mode) in radar tool box which stores the configuration and reads all the CLI from a file

    You can find the video doorbell demo at the below location

    radar_toolbox_2_20_00_05\source\ti\examples\Video_Doorbell\source

    You can see the CLI stored in the file below

    radar_toolbox_2_20_00_05\source\ti\examples\Video_Doorbell\source\two_pass_mode_profiles\mode_1_profile.c

    Only if you want to limit the range for HR/BR then you will have to modify vitalsign.c

    appimage will be created by the CCS project itself, you need not manually create it. Appimage created with hard coded config should be less than 250KB. 

    To make sure that hard coded CLI are working properly, you need to debug using CCS before directly flashing the appimage

    If you are able to run it with CCS then appimage created will be correct

    Regards