• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 4 answers
  • Subscribers 30 subscribers
  • Views 1042 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.

AWR1642: ODS Visualizer - CONFIG page vs. "Load Config from PC"

John Whittaker
Intellectual 440 points
Part Number: AWR1642

Hi All!

I have a question on the ODS Visualizer.

When I run the ODS Visualizer using 'Load Config from PC and Send, with the configuration file coming from the LAB0004 in the Automotive toolkit, it works just fine.

Previously I had been using the SEND CONFIG TO MMWAVE DEVICE button on the 'Configure" page, and would get a version mismatch regardless of whether I set the SDK version to 2.0 or 1.2.

I would still like to use the Configure page to do things like enable the range azimuth heatmap.

Here is the error message screenshot.  I have tried changing the SDK version to 1.2 and the error message persists:

ODS - Version Mismatch.jpg

  • 0
    TI__Mastermind 24955 points
    John,

    You should only be using SDK 2.0 or later for the AWR1642BOOST-ODS. The AWR1642BOOST-ODS uses ES 2.0 silicon and as a result is only compatible with SDK 2.0 or higher.

    You can compare to the two configuration (.cfg) files and see if there are any differences between the included configuration and the configuration that you are attempting to send to the device.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Intellectual 440 points

    Hi Kyle,

    I am using SDK 2.0.0.  Are you able to see the screen shot?  DO I have the wrong version of the XDS110 firmware?

    When I "load config from PC" on the PLOTS page it works fine, using the lab_0004 configuration file.

    But when I launch ODS Visualizer 1.0.0, set the serial ports correctly, then send the defaults from the CONFIG page, that is where I get the error message.  Am I running the older version of the ODS visualizer?

    I get the SDK INput Version [major,minor] = [1,2] not matching [2,0] reported by target.

  • 0 in reply to John Whittaker
    TI__Mastermind 24955 points
    John,

    If you try the "Load Config from PC" option, make sure to click "Sensor Stop" before attempting to use the "Configure" tab to send a new configuration to the device.

    It is not immediately clear why you would be seeing this particular error message given that all AWR1642BOOST EVMs use ES 2.0 silicon and would therefore only be compatible with SDK 2.0 or higher.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Intellectual 440 points

    Hi Kyle,

    The one thing I thought of, this isn't a TI eval board, it is our design.  I designed 2 boards, identical in every other respect but one uses the traditional antenna design and the other uses the OBJ DET antenna design.

    I have no problems running the traditional antenna design, the board is running well.  I only have trouble with the ODS.  Could it be that the ODS Visualizer is checking for a valid serial number for the board?  The traditional boards don't do this, but maybe the ODS Visualier does?  I know how to program the serial number into the XDS110.  however I don't have an OBJ DET eval board so I don't know what a valid serial number would be.

    My sequence is to launch the ODS Visualizer, configura the serial ports, then [with the defaults shown] click SEND CONFIG TO MMWAVE DEVICE.

    That is when I get the error message about the 1.2 vs 2.0 version mismatch.  I am using ODS Demo Visualizer 1.0.0.  This is frustrating because I can't run the heat map, etc. although maybe I can manually edit the cfg file - but this should work, I don't get it.

    The other possibility is the XDS110 firmware or bootloader, maybe that is the wrong version.

  • 0 in reply to John Whittaker
    TI__Mastermind 24955 points
    John,

    The only difference between AWR1642BOOST and AWR1642BOOST-ODS is the configuration of the antenna pattern. The silicon on these two EVMs is exactly the same. So it would not be an issue with the serial numbers.

    An issue could arise if one of your chips is an AWR1642 ES 1.0 and the other device is an AWR1642 ES 2.0 device. This would certainly present an issue since the binary image that is designed for the ODS Visualizer is compatible only with ES 2.0 devices.

    Please double check the physical markings on the packaging of the AWR1642 to determine which revision of silicon your devices are. You can search through this forum on how to determine the silicon revision of your device.

    Regards,
    Kyle
  • 0 in reply to Kyle Cousino
    Intellectual 440 points

    Hi Kyle,

    Up to this point I had been using my own design.  So I got an AWR1642BOOST-ODS and I am having the same problem.  The only way I can run is to load config from PC.  Also, I am getting notices about performance degradation and "Missing command lowPower" when I load a config from PC, then switch to the CONFIGURE tab.

    This is happening on both a desktop and laptop, my design and the AWR1642B))ST-ODS.  One thing in common is the ODS Visualizer link I am using for ODS 1.0.0.

    Kyle - it really does seem like there is an issue here. Should the Send Config TO mmWave Device automatically send the lowPower command?

  • 0 in reply to John Whittaker
    Intellectual 440 points

    I am doing some outdoor testing tomorrow, it is frustrating that I can't get the ODS configured the way I need to.  Here is the test bed I built:

  • 0 in reply to John Whittaker
    TI__Mastermind 24955 points
    John,

    We have just released up an update to the Obstacle Detection Lab on TI's Resource Explorer. You can find this lab here: dev.ti.com/.../

    The binaries included in this lab release feature a new ODS processing chain and a new MATLAB visualizer. I would recommend using the new binary and visualizer.

    Regards,
    Kyle