• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 506 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.

AWR1843BOOST: AWR1843 reconfigure sensor during runtime

Aleksa Anicic
Prodigy 230 points
Part Number: AWR1843BOOST

Hi guys,

I am developing a code based on your high-accuracy lab. I need the code to be able to receive a configuration, run it for a while, then start receiving a new configuration. 

However when I try to send a new configuration, I receive two types of errors:

Error: MMWDemoMSS mmWave Configuration failed [Error code -203816626]

Error: MMWDemoMSS mmWave Stop failed [Error code -203227134]

Here is what I get when I decode them:

-203816626:
-3110 => MMWAVE_EFRAMECFG
83 => RL_RET_CODE_FRAME_IS_ONGOING

-203227134:
-3101 => MMWAVE_EINVAL
0 => RL_RET_CODE_OK

The first one makes sense, however, I have implemented an event, where sensorStop waits for the DSS to notify MSS about the frame completion before it tries to perform sensorStop actions.

sensorStop actions are the following ones:

And there is a task in main that pends on MMWDEMO_SENSOR_STOP_EVT, that works as follows:

In the end eventHandleNotify is used only to set isSensorStarted bool value to false, once the sensorStop has been completed.

What am I missing here?

Cheers,

Aleksa

  • 0
    TI__Guru*** 149154 points

    Hi,

    Unfortunately it is difficult to provide feedback based on this information.

    Sensorstop command works if it is sent from the cli.

    You need to identify ways to test your changes step by step.

    Maybe you can use a timer or a GPIO interrupt to trigger an event to send the sensorStop command

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 230 points

    I guess the main issue here is that I am unsure of what needs to happen on a sensorStop command?

    The code in high accuracy lab was terrible for runtime reconfiguration, so I've found another one that did this thing properly and basically copied to procedure over to my code. 

    Anyway, my end goal here is only to change profileCfg and chircpCfg. Do I even need to stop the sensor to reconfigure it, or can I just send these two commands somehow? 

  • 0 in reply to Aleksa Anicic
    TI__Guru*** 149154 points

    Hi,

    Let me assign this thread to the team that supports the high resolution demo

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 230 points

    Hi guys,

    Any update on this from the team that supports the high resolution demo?

    Thanks,

    Aleksa

  • 0 in reply to Aleksa Anicic
    Prodigy 230 points

    I've just tested the lab itself(industrial_toolbox/labs/level_sensing/16xx_high_accuracy), both from the SDK 4.5.1(from which I've started), and the newest 4.7.0. Neither of them supported runtime reconfiguration. 

    So it's not done well definitely. 

    I know for a fact that this can work on your chips, but I can't find info on what is missing here. I often get this assertion failure: "platform/mmwave_xwr16xx.c", line 1342: assertion failure. 

    I've tried removing DebugP_ASSERT_ENABLED from predefines, it doesn't help. Do you think importing the whole mmwave in a project(and building it together with the project, instead of using it as lib), without DebugP_ASSERT_ENABLED could help? 

  • 0 in reply to Aleksa Anicic
    TI__Mastermind 23725 points

    Hello

    Have you been issuing a stop before sending the new configuration?

    Also can you please make sure if the sensor stop ; resend old configuration works.

    Thank you,

    Vaibhav