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

AWR1642BOOST: AWR1642BOOST

AWR1642BOOST: AWR1642BOOST

nalini singh
Intellectual 260 points
Part Number: AWR1642BOOST

Hi,

This is related to the Error faced in running the occupancy detection GUI (od_demo.m). The error was " Not enough input arguments".

While putting some random values for the variables defined in the 1st line of the function i.e. ( comportSnum, comportCliNum, cliCfgFileName, polarPlotMode, decisionByMatlab ), I am not getting any error but the GUI displayed is blank with only two check boxes. I am attaching a screenshot of GUI on putting the values as (5,6,0,0,0).

What would be the correct values of the above variables to get the complete GUI displayed on system? 

I am using the Automotive toolbox 2.0.0 with ES 1.0 EVM.

Thanks

- Nalini

  • 0
    TI__Mastermind 24955 points
    Nalini,

    The Occupancy Detection lab in automotive toolbox v2.0.0 is compatible only with ES 2.0 devices. This information is provided in the release notes. There, your device would not work with this release. Please download an earlier version of the automotive toolbox that contains a release of the occupancy detection lab that is compatible with ES 1.0 devices.

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

    Hi,

    Thanks for replying. But I have been using the automotive toolbox 2.0.0 for "Driver Health monitoring" with the same chip and everything runs successfully. Also as I mentioned earlier "Vehicle occupancy detection" was also running successfully using the same toolbox and same chip. But all of a sudden this problem occurred with Occupancy Detection. Driver health monitoring is still running fine, problem is being faced with occupancy detection. Also if I try a toolbox version higher than this at least the GUI appears completely although it doesn't give any output. Why is the GUI not appearing completely now, though it did so earlier and also gave the output.

    -Nalini

  • 0 in reply to nalini singh
    TI__Mastermind 24955 points

    Nalini,

    If you look at the release notes for the Driver Vital Signs Lab in automotive toolbox 2.0.0, you will see that this release is based on mmWave SDK v1.1 which is compatible with ES 1.0 devices. Please refer to the release notes for each respective lab to determine if your ES 1.0 device is compatible or not.

    Regards,
    Kyle

  • 0 in reply to Kyle Cousino
    Intellectual 260 points

    Hi, 

    As I said, I ran the "vehicle occupancy detection" completely and successfully using this ES 1.0 chip and automotive toolbox 2.0.0. So most probably the device is compatible. But few days back I started facing the problem,screenshot of which I've sent to you in the first message. I tried it on separate systems as well but the error still remains the same,

    Not enough input arguments

     Have you ever come across such error? 

    I had a great deal of discussion with db_woodall about this, the link to which I am mentioning here.

    e2e.ti.com/.../2711763

    Thanks

    Nalini

  • 0 in reply to nalini singh
    TI__Mastermind 24955 points
    Nalini,

    As previously stated, because you are using an ES 1.0 device, you will need to use labs that were released under SDK 1.x. You need to check the release notes for each lab.

    If a particular lab states that it was developed for SDK 2.0 or higher, your device will not be compatible. There is no way around this issue other than to obtain a new ES 2.0 EVM.

    This is not a question related to error messages, but rather to using labs developed under an SDK for which your ES 1.0 device is supported.

    Please use releases of the automotive toolbox that correspond to SDK 1.x that are compatible with your device.

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

    Hi kyle,

    Thanks for pointing this out. I was using the mmwave sdk v.2.0. I think this was one of the problems. I installed the mmwave sdk according to a previous version of automotive toolbox. The program was flashed to the chip successfully and  Now I am able to get the heatmap GUI by typing commands in the CMD. But running the GUI through od_demo.exe still gives the same error.

     

    Please support.

    Thanks.

    Nalini

  • 0 in reply to nalini singh
    TI__Mastermind 24955 points
    Nalini,

    There appears to be an issue with the screenshot that you attempted to upload. I cannot see the picture. For reference, this demo is designed to be invoked from the command line and not by clicking on the od_demo.exe file. Please read the User's Guide to understand why this is the case.

    Regards,
    Kyle