Part Number: AWR1642BOOST
While running the Occupancy detection GUI for my AWR1642BOOST error is coming as :
Not enough input arguments.
Error in od_demo line (14)
Although I've run the gui many times, i am facing this problem for the very first time. Please support.
In reply to nalini singh:
It is possible that the command line is too long and so Matlab is not seeing the last few parameters and throwing the error. For Matlab, make the default folder the one containing od_demo.m, then doing this command:
od_demo.m 5 6 chirp_configs\od_demo_car_0318_3p0.cfg 1 0
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to db_woodall:
Why are we getting this "not enough input arguments" when the program is itself downloaded from TI website and no modification has been made by us??
How can this error be corrected??
And this occurs in every version of automotive toolbox for Vehicle Occupancy Detection.
Did you try my suggestion to shorten your command line? Also, what version of Matlab are you running? Version R2017a is required.
I tried running my copy with fewer and fewer arguments (this is the 2.x automotive toolbox version). It only throws the error if the third argument (the config filename) is not present, as it should. I don't believe there's a problem with the code.
I would check your Matlab version, and if correct, try setting a breakpoint on the first line of od_demo(), and step through the code, examining each variable along the way until it throws the error.
Yes I've tried to shorten the command line but it still throws the same error. And I am using MATLAB version 2017b, is that a problem?I also tried running an older version of automotive toolbox i.e. 1_2_0 but still getting the same error.
Not enough input arguments.Error in od_demo (line14)MATLAB:minrhs
Your original post says you've run the demo many times. What changed when it stopped working?
We don't have 2017b so I can't try it. I googled the difference between 2017a/b and didn't find anything to explain differences in command line handling.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.