• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 670 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:

IWR1443BOOST: send config to IWR1443 without using visualizer

IWR1443BOOST: pre-set configuration on boot

jason Anderson
Expert 1080 points
Part Number: IWR1443BOOST

Hi,

i have seen several posts about wanting to start the IWR1443BOOST up, and immediatly start receiving data. the linked post has a few additional files to use. Isn't there an easier way to accomplish a pre-set configuration, while keeping the flexibility to adjust the paramaters via UART?

What i want is to start the sensor, load a pre-set configuration on the board itself, so without receiving data via UART. If i want new values for the parameters, i want these to be able to read via UART as it is already.

What i am asking is: i want to have an additional file with the pre-set configuration, which gets loaded on bootup of the device, everytime it boots up. 

I am thinking of calling the functions to set the parameters at the beginning of the task that tells the  sensor to keep waiting for a first communication. So to skip this waiting, and replace it with my configuration. My question is: where in the code does this happen? and which functions do i call to set the parameters?

cheers

  • 0
    TI__Mastermind 21295 points
    Hello Jason,

    I'm not sure which E2E threads you have already looked at. But I think the following thread may contain exactly what you are looking for. It provides a couple of file modifications that allow the mmWave SDK out-of-box (mmw) demo to use a hard-coded configuration automatically upon powerup but also continues to accept the standard UART CLI commands after the configuration is running.

    e2e.ti.com/.../2616079

    Note: In general it is possible to reconfigure the mmWave sensor after a configuration has already been started but there is a restriction on the new config: The new config must use the same number of TX and RX antennas as the original config. In order to use a different number of TX or RX antennas the mmWave sensor must be rebooted/power-cycled.

    Please mark the thread as answered if the question is resolved or reply if more support is required.

    Regards,
    John
  • 0 in reply to JohnH
    Expert 1080 points
    Hello,

    Thank you very much for your reply. However i am hoping there is an "easier" way to accomplish this as i do not want to make these changes in my entire SDK. Any other suggestions are very much appreciated. Thanks in advance

    cheers
  • 0 in reply to jason Anderson
    TI__Mastermind 21295 points
    Hi Jason,

    Unfortunately, since the mmWave SDK demo does not support automatic configuration upon boot the provided file changes and instructions in the referenced thread are the most straightforward and simplest way to add that support to the demo. Please tell me if there was anything else you were looking for.

    Regards,
    John
  • 0 in reply to JohnH
    Expert 1080 points
    Hi John,
    Thank you very much for your replies.
    I would like to know how this is implemented in the mmwave_demo, as this does support automatic configuration on boot via a simple .txt file.
    Would it be hard to implement it from the mmwave_demo onto the high accuracy lab ?

    cheers
  • 0 in reply to jason Anderson
    TI__Mastermind 21295 points
    Hi Jason,

    It should be very easy as you can use the exact same solution that the mmWave SDK demo uses for the high-accuracy demo. The file modification given in the thread mentioned above is for the CLI library that is part of the mmWave SDK. This same CLI library is used by both the mmWave SDK demo and the high-accuracy 1443 demo. So, you should be able to use the same modification for the high-accuracy demo.

    NOTE: Since the high-accuracy demo only supports a subset of the mmWave SDK demo CLI commands you will need to make sure the hard-coded config that you put in the code only uses the commands that are used in the sample config files provided with the high-accuracy demo.

    Please mark the thread as answered if the question is resolved or reply if more support is required.

    Regards,
    John