• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 5 answers
  • Subscribers 31 subscribers
  • Views 747 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.

Original question:

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

IWR1642BOOST: Problems with the occupancy demo

user5894843
Prodigy 235 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1642,

Hi,

there was this old thread about getting time outs while sending the configuration in Occupancy Detection Demo on IWR1642, and the thread is marked as resolved. However, I am facing exactly the same problem, even though using mmwave_automotive_toolbox_2_5_0 The symptoms are exactly the same as in the previous thread. First few commands go through, and the console shows "Done" reply. Then it starts outputting Warning: Unexpected Warning: A timeout occurred before the Terminator was reached messages.

Is there any remedy to this?

Best regards,

Marko Leppänen

  • 0
    TI__Mastermind 24955 points

    Marko,

    Can you provide a screenshot of what exactly you are encountering? This post needs more information to try and debug this issue.

    Can you also provide a picture of your physical setup?

    Please make sure that you are using an IWR1642 ES 2.0 device with this lab.

    Regards,
    Kyle

  • 0 in reply to Kyle Cousino
    Prodigy 235 points

    Hi,

    as stated, it's exactly the same situation as in the linked question. I have double checked the configured ports, and the board runs other demos flawlessly. I have successfully flashed it with the Automotive toolbox 2.5.0 prebuilt binaries.

    The command is C:\ti\mmwave_automotive_toolbox_2_5_0\labs\lab0003_occupancy_detection\gui>od_demo.exe 10 11 ..\chirp_configs\od_demo_car_0318_1p0.cfg 0 0

    The GUI comes only up as a grey box, as in the original question.

    The output is exactly the same as in the original question, too. After the adcbuf command the device only responses with timeouts.

    My setup is pretty basic, just the device on the table. Its IWR1642BOOST board, 5449600283

  • 0 in reply to user5894843
    TI__Mastermind 24955 points

    It looks like you need to replace your power supply. The cable is severely frayed and could be damaging the IWR1642BOOST EVM. 

    Please replace the power supply cord and try again.

    Regards,
    Kyle

  • 0 in reply to Kyle Cousino
    Prodigy 235 points

    Hi Kyle,

    The power supply is perfectly ok, see photo attached. The cable is in excellent condition and the unloaded voltage is 5.2 V, loaded 5.1 V and the spec is up to 2250 mA. I have tested other power supplies, for example one with exactly 5V unloaded and up to 1500 mA but the result is exactly the same. Tried a few USB cables too, all of which work on other demos. The first lines are quickly sent and "Done" replies come in a quick succession, but then adcbufCfg -1 0 0 1 1 line stops and finally timeouts. Then each successive command also timeouts.

  • 0 in reply to user5894843
    TI__Mastermind 24955 points

    This is not the same power supply cable that was used in your previous post. The cables are noticeably different.

    A similar E2E posts notes that "This kind of response usually does indicate that there is an issue with the communication either the COM ports or the SOP mode."

    Please make sure that your COM ports show up properly in Windows Device Manager. If not, you should reinstall the XDS110 emulation software that is found here: 

    Also, you should set the Display Type value in the CLI commands to Polar (1) instead of Rectangular (0).

    Regards,
    Kyle

  • 0 in reply to Kyle Cousino
    Prodigy 235 points

    Hi,

    the cable in both photos is definitely the same, as I have only two clearly distinguishable and electrically differently specified power supplies easily available here. I have tried them both in relation to this demo, but to no avail. Even that white paper in both photos is the same, as I took the photo by just removing the connector from the device.

    I tried "od_demo.exe 10 11 ..\chirp_configs\od_demo_car_0318_1p0.cfg 1 0" for polar coordinates, but the result is the same.

    Both virtual com ports come up in the device manager and work with, for example, People Counting demo and exactly the same board. And the cmd line parameters are as specified in the documentation, Data port first (COM10) and then the User port (COM11)

  • 0 in reply to user5894843
    TI__Mastermind 24955 points

    Make sure your power supply is providing up to 3A of current the device is not current starved during initial configuration.

    Regards,

    Kyle

  • 0 in reply to Kyle Cousino
    Prodigy 235 points

    Hi,

    providing 5 V from a 3 A power supply did not change the results, it still timeouts in adcbufCfg command. The board draws 0.34A of current during CLI operation.

    Marko

  • 0
    Intellectual 800 points

    Found solution：

    [Resolved] IWR1642BOOST: adcbufCfg command doesn't respond in occupancy detection demo - Sensors forum - Sensors - TI E2E support forums  e2e.ti.com/.../2743538

    Marking it resolved.

  • 0 in reply to SimonWong
    Prodigy 235 points

    Hi,

    and thanks for the solution! When I was in process of building this, I noticed that the new automotive toolbox version 2.7.1 already has this fixed in the prebuild binaries, so no need to build anything.