• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 31 subscribers
  • Views 3126 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.

IWR1642BOOST: issue of running Occupancy Detection Demo (automotive toolbox 1.2.0)

Hayden Kim
Genius 15580 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: AWR1642, UNIFLASH, IWR1642, AWR1642BOOST

Champs,

With IWR1642BOOST EVM, I am trying to run "lab0003_occupancy_detection" that is included in "mmwave_automotive_toolbox_1_2_0".

I followed the user's guide PDF document.

When running the GUI (od_demo.exe), the GUI did not run properly with below "timeout" warning messages.

(Only a blank Visualization Window GUI pop-up happened, with no heat map update..)

The same issue happened with pre-built binary image too.

[DOS console messages]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\a0967799>cd C:\ti\mmwave_automotive_toolbox_1_2_0\labs\lab0003_occupancy_detection\gui

C:\ti\mmwave_automotive_toolbox_1_2_0\labs\lab0003_occupancy_detection\gui>od_demo.exe 24 25 C:\ti\mmwave_automotive_toolbox_1_2_0\labs\lab0003_occupancy_detection\chirp_configs\od_demo_car_0318_1p0.cfg 1 0
Starting UI for Occupancy Detection Demo ....
Opening configuration file C:\ti\mmwave_automotive_toolbox_1_2_0\labs\lab0003_occupancy_detection\chirp_configs\od_demo_car_0318_1p0.cfg ...

comportnum_str =

'COM24'


comportnum_str =

'COM25'

Sending configuration to XWR1xxx C:\ti\mmwave_automotive_toolbox_1_2_0\labs\lab0003_occupancy_detection\chirp_configs\od_demo_car_0318_1p0.cfg ...
sensorStop
Done
flushCfg
Done
dfeDataOutputMode 1
Done
channelCfg 15 3 0
Done
adcCfg 2 1
Done
adcbufCfg -1 0 0 1 1
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
profileCfg 0 77 250 10 40 0 0 98 1 64 2200 0 0 40
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
chirpCfg 0 0 0 0 0 0 0 1
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
chirpCfg 1 1 0 0 0 0 0 2
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
chirpCfg 2 2 0 0 0 0 0 1
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
chirpCfg 3 3 0 0 0 0 0 2
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
frameCfg 0 3 128 0 160 1 0
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
lowPower 0 0
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
guiMonitor -1 0 1 1
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
calibDcRangeSig -1 0 -5 8 256
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
zoneDef 2 13 16 9 15 13 16 27 15
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
coeffMatrixRow 0 -14.409613 -8.187467 -8.019457 3.833826 4.045485 -0.539210
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
coeffMatrixRow 1 -12.465002 -2.228748 -5.612140 4.324446 -7.912656 0.528747
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
coeffMatrixRow 2 -9.210626 -3.004206 -0.082298 -2.949700 7.538751 0.246658
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
coeffMatrixRow 3 -1.917373 2.299849 2.389683 7.035545 6.675194 -0.099186
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
meanVector 23.992751 23.689970 -3.388539 -3.691319 0.816150
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
stdVector 8.495360 8.497394 2.198640 2.432388 0.196337
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
oddemoParms 12 0.001
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
sensorStart
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.
Warning: Unexpected Warning: A timeout occurred before the Terminator was reached.

So, can you check if the ODdemo can run properly on your side?

Best regards,

Hayden

  • 0
    TI__Guru*** 148514 points
    Hi,

    Have you been able to run any other demo on this EVM before?

    It seems that there is a problem with the UART communication

    thank you
    Cesar
  • 0
    TI__Genius 15580 points
    Hi,
     
    Yes, other demos are working well.
    Thank you.
     
    Best regards,
    Hayden Kim
     
  • 0
    TI__Mastermind 21025 points

    Hi Hayden,

    The VOD demo has been tested on several machines.  It should run on any reasonable Windows 7 or 10 PC/laptop.

    Have you flashed oddemo_16xx.bin to the AWR1642 with Uniflash?

    The AWR1642 is connected to the PC with the USB cable?

    Have you checked that your COM port numbers are correct?

    These messages indicate there is some kind of communication issue with the board's UART.

     -dave

  • 0 in reply to db_woodall
    TI__Genius 15580 points
    Hi Dave,

    I am running the demo on IWR1642BOOST not AWRxxx.
    As I know, it can run on IWRxxx also, right?
    Anyway, I will check VOD demo again with my EVM.
    Thank you.

    Best regards,
    Hayden
  • 0 in reply to Hayden Kim
    TI__Mastermind 21025 points

    An IWR1642 will work as well.

     -dave

  • 0 in reply to db_woodall
    TI__Genius 9270 points
    Hi,
    I run the demo on my IWR1642 BOOST, faced the same issue.
    My board has run the mmw demo, people counting, SRR and vital demo successfully, double confirmed the port is correct. OS is windows 7.
    Need your help to fix the issue, thanks.
    Andy
  • 0 in reply to Andy Yin
    TI__Genius 15580 points
    Hi,

    Actually, I still have the issue with my IWR1642 board.
    I have plan to try with AWR1642BOOST board.

    Best regards,
    Hayden
  • 0 in reply to Hayden Kim
    TI__Genius 9270 points

    Hi,

    I tried on AR1642 BOOST, the cfg can be sent to the EVM well as below, and the LED DS3 is lighten which should indicate the application run well, but nothing display shown as below figure~. Can anyone help check why it is different for IWR and AWR1642 EVM, and how to fix the below no display issue, thanks.

    Microsoft Windows [Version 6.1.7601]

    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\a0220231>cd C:\Work_AndyYin\Device\Radar\Software\REX\mmwave_automotive

    _toolbox_1_2_0\labs\lab0003_occupancy_detection\gui

    C:\Work_AndyYin\Device\Radar\Software\REX\mmwave_automotive_toolbox_1_2_0\labs\l

    ab0003_occupancy_detection\gui>od_demo.exe 13 12 C:\Work_AndyYin\Device\Radar\So

    ftware\REX\mmwave_automotive_toolbox_1_2_0\labs\lab0003_occupancy_detection\chir

    p_configs\od_demo_car_0318_1p0.cfg 1 0

    Starting UI for Occupancy Detection Demo ....

    Opening configuration file C:\Work_AndyYin\Device\Radar\Software\REX\mmwave_auto

    motive_toolbox_1_2_0\labs\lab0003_occupancy_detection\chirp_configs\od_demo_car_

    0318_1p0.cfg ...

    comportnum_str =

       'COM13'

    comportnum_str =

       'COM12'

    Sending configuration to XWR1xxx C:\Work_AndyYin\Device\Radar\Software\REX\mmwav

    e_automotive_toolbox_1_2_0\labs\lab0003_occupancy_detection\chirp_configs\od_dem

    o_car_0318_1p0.cfg ...

    sensorStop

    Done

    flushCfg

    Done

    dfeDataOutputMode 1

    Done

    channelCfg 15 3 0

    Done

    adcCfg 2 1

    Done

    adcbufCfg -1 0 0 1 1

    Done

    profileCfg 0 77 250 10 40 0 0 98 1 64 2200 0 0 40

    Done

    chirpCfg 0 0 0 0 0 0 0 1

    Done

    chirpCfg 1 1 0 0 0 0 0 2

    Done

    chirpCfg 2 2 0 0 0 0 0 1

    Done

    chirpCfg 3 3 0 0 0 0 0 2

    Done

    frameCfg 0 3 128 0 160 1 0

    Done

    lowPower 0 0

    Done

    guiMonitor -1 0 1 1

    Done

    calibDcRangeSig -1 0 -5 8 256

    Done

    zoneDef 2 13 16 9 15 13 16 27 15

    Done

    coeffMatrixRow  0  -14.409613   -8.187467   -8.019457    3.833826    4.045485

    -0.539210

    Done

    coeffMatrixRow  1  -12.465002   -2.228748   -5.612140    4.324446   -7.912656

    0.528747

    Done

    coeffMatrixRow  2  -9.210626   -3.004206   -0.082298   -2.949700    7.538751

    0.246658

    Done

    coeffMatrixRow  3  -1.917373    2.299849    2.389683    7.035545    6.675194   -

    0.099186

    Done

    meanVector  23.992751   23.689970   -3.388539   -3.691319    0.816150

    Done

    stdVector   8.495360    8.497394    2.198640    2.432388    0.196337

    Done

    oddemoParms  12  0.001

    Done

    sensorStart

  • 0 in reply to Andy Yin
    TI__Genius 9270 points

    Some update, test on AWR1642 BOOST there is result display on the visualizer only with the od_demo_car_0318_3p0.cfg, and lots of buffer overflow warning, while no result display if using the other two cfg files. Look forward to your help make the demo more robustness.

  • 0 in reply to Andy Yin
    TI__Genius 15580 points
    That's a good progress.
    Thanks for your update.

    Best regards,
    Hayden
  • 0 in reply to Andy Yin
    TI__Guru*** 148514 points

    Hi,

    I think this issue is related to the performance of the WIndows Laptop.

    The matlab GUI requires certain processing power. If the Windows Laptop is not powerful enough, frames will be dropped because the Windows Laptop Host can't keep up with the target

    thank you

    Cesar

  • 0 in reply to Andy Yin
    TI__Mastermind 21025 points

    With respect to IWR1642 vs. AWR1642, the only difference I'm aware of is the CAN interface. This demo does not use CAN.  An interesting experiment would be to edit the DSS and MSS projectspecs, replacing AWR with IWR (there are multiple occurances), then reimporting, rebuilding and reflashing the resulting .bin on the IWR1642.

    On the error packet topic, this is a real-time demo, and the GUI requires a fair amount of the CPU's time.  If you have several other programs running simultaneously you can starve the GUI of the CPU time it needs.  You can also cause this to happen by resizing the GUI window.  It is not a matter or robustness, it is a matter giving it the resources it requires, and it having to play within the limitations of Windows.

     -dave

  • 0 in reply to db_woodall
    TI__Genius 9270 points

    Dave,
    I agree with u about the difference between IWR AND AWR1642, and cannot understand the issue. Have u ever tried the demo on IWR1642, if not pls try and fix it as lots of customers maybe get the IWR1642 EVM.

    Another issue mentioned in my last post that only running od_demo_car_0318_3p0.cfg can get visualizer output, while no output if using other two default cfg, have u ever faced same issue and how to fix it? Is it also caused as CPU power or performance is not strong?
    Andy

  • 0 in reply to Andy Yin
    TI__Mastermind 21025 points

    >Another issue mentioned in my last post that only running od_demo_car_0318_3p0.cfg can get visualizer output, while no output if using other two default cfg,

    If you diff the .cfg files, you will see that the chirp parameters are identical.  The only difference is that the training coefficients are tuned a bit differently. This could not be the cause of no output.  If you haven't made any changes to the config (like changing what is output via the guiMonitor command) my guess is that maybe you aren't giving it enough time to start up.  If you have Matlab 2017a installed, you could try running the demo interactively by giving the same command in Matlab's command prompt.  It seems to startup faster in Matlab.

    If it still doesn't seem to start, you can send the config file directly to the AWR1642 via a UART terminal, and have a second terminal open to respond to the data COM port.  If you get bursts of data on the data COM port, it will confirm whether or not the AWR1642 is sending frames once started.