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 / IWR1443BOOST:IWR1443BOOST Demo: Vital Signs Gui Error

Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1642, IWR1443, MMWAVE-SDK, UNIFLASH

Tool/software: Code Composer Studio

As I open the gui.exe and push the button,  only the range profile has feedback while there is no breathing or heart waveform.

And the LED:DS-1 (NERR_OUT) and DS-3 (GPIO_1) are all brighten.

Also in the CLI command window opened by GUI:

Error using matlab.graphics.chart.primitive.Line/set
The object is invalid or has been deleted.

Error vitalSigns_demo_gui (line 327)


Error vitalSignsDemo_GUI/StartPushed (line 93)


Error appdesigner.internal.service.AppManagementService/tryCallback (line 191)


Error matlab.apps.AppBase>@(source,event)tryCallback(appdesigner.internal.service.AppManagementService.instance(), app, callback, requireEventData, event)

Error using matlab.ui.control.internal.controller.ComponentController/executeUserCallback (line 310)
An error occurred while calculating Button PrivateButtonPushedFcn.

 

 

------------------------------------------------------------------------

Thanks, Vick.

  • Hey,

    Which board are you using? ES1.0 or ES2.0? and what is your SDK and Toolbox version?

  • Thanks for your response, Laxmi:

    I feel embarrassed that I have not yet inquired the Es version, but the LOT is 11342017I3. The other information is as follows:

    CCS Version 7.4;

    mmWave SDK Version1.2.0.5

    Toolbox Version 2.5.1

    And the other codes on  CLI command window are shown below:

    Starting UI for vital Signs Demo ....

    LENGTH_OFFSET_BYTES =

    40


    INDEX_RANGE_PROFILE_START =

    35

    Opening configuration file profile_2d_VitalSigns_20fps.cfg ...

    comportnum_str =

    'COM3'


    comportnum_str =

    'COM4'

    Sending configuration to AR14xx profile_2d_VitalSigns_20fps.cfg ...
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg 0 1 0 1
    profileCfg 0 77 7 6 57 0 0 70 1 200 4000 0 0 48
    chirpCfg 0 0 0 0 0 0 0 1
    frameCfg 0 0 2 0 50 1 0
    guiMonitor 0 0 0 0 1
    vitalSignsCfg 0.3 1.0 256 512 4 0.1 0.05 100000 100000
    motionDetection 1 20 3.0 0
    sensorStart

     

    Thanks,

    Vick.

  • Hey,

    If you don't have a label which says ES2.0 then it is ES1.0. The ES1.0 supports SDK 1.2 and Toolbox version 2.3 so you need to reduce your toolbox version from 2.5 to 2.3. Try this. It should work. Follow steps 1, 2, and 3 in order as shown in the image. 

  • Hey,

    I'm sorry to just find it is ES2.0 because the line 4 of  Marking is 964D, and should I continue change the SDK  Version or do something else?

    Best wishes, 

    Vick.

  • Hi Vick,

    Laxmi's claim is only true for IWR1642 and not for IWR1443. There should not be any ES1.0 IWR1443BOOST's in circulation.

    Your issue is likely a versioning one. Would you confirm you're using the version of Vital Signs in the Industrial Toolbox v2.5.1? You'll also need mmWave-SDK 1.2 installed as per this table: dev.ti.com/.../

    Let us know what error messages you receive if this doesn't work.

    Cheers,
    Akash
  • Hi Aksah,

    The version of Vital Signs is V1.3.

    I try again and here is a noticeable phenomenon:

    After loading program by UniFlash Tool and powering off, removing the jumper  from header SOP2 as the guidelines require,  I power on and the led-DS1 changes to a continuous light.


    Also in the Load Program step,  there is a message

    "Cortex_R4_0: Trouble Removing Breakpoint with the Action "Process CIO" at 0x1589e: (Error -1066 @ 0x1589E) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 7.0.100.0)"

    Finally, there is no data getting into the GUI program, and no waveform or any information displayed.  Same results no matter how many times I've tried and I think there must be some problems because  the led-DS1 changes to a continuous light.

  • Thanks, Akash for correcting me. 

  • Hi Vick,

    This is happening because you haven't selected your COM ports appropriately. You'll need to figure out the numbers corresponding to both the UART and DATA ports for your device in the Windows Device Manager. Then in the GUI you'll need to press the settings button and enter the corresponding numbers for both the UART and DATA ports. After this you can press the start button and your visualizer should start working correctly.

    Let me know if this doesn't fix the problem.

    Cheers,
    Akash
  • Hi Akash,

    I successfully completed the experiment and the real reason is that I don't press the Load Config File bottom.

    And I still don't know why LED DS-1 truns on.

    Thank you and Laxmi.

    Regards,

    Vick.