• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 322 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.

IWR6843ISK-ODS: Can't change profile configuration at runtime using mmWave control module.

HUANPU YIN
Prodigy 100 points
Part Number: IWR6843ISK-ODS


Hi, 

   Here's the context, I want to change profileCfg (specificly, the tx phaseshift) dynamicly after sensor start, I'm developing on top of the 68xx vitalsigns lab, the toolbox version is 4.10.1, the sdk version is 3.5.0.4. In my reconfig_function, I sequentially called MmwDemo_mssDataPathStop -> MMWave_getProfileHandle -> MMWave_getProfileCfg to stop sensor and get profileCfg,  and then MMWave_getChirpHandle -> MMWave_getChirpCfg to get chirp configuration bound to it, and then modify phaseshift in profileCfg, then MMWave_delProfile-> MMWave_addProfile -> MMWave_addChirp, then finally MMWave_config.

    Something went wrong when I call MMWave_config(),  the decodeError() API give me 'mmWaveError -3110, subSysError 83', I can see mmWaveError is well defined in mmWave API document, ' mmWaveError -3110 ' is defined as MMWAVE_EFRAMECFG, and I can see it's frameCfg related, but I only changed profileCfg,  the frameCfg is same as the first time the sensor is started, and there's no problem with the first startup.

    What does 'subSysError 83' mean? How can I locate the error using the subSysError code? Am I doing this (reconfig profile at runtime) in the right way?  If not, what am I supposed to do? 

Best regards. 

  • +1
    TI__Genius 17265 points

    Hi,

    I believe the subSysError 83 refers to the codes found in <mmwave_sdk>\packages\ti\control\mmwavelink\mmwavelink which would mean the error is RL_RET_CODE_FRAME_IS_ONGOING. This would likely indicate that the process hasnt fully stopped before you tried to configure and restart it. Based on what you have said, it seems like you are stopping the data path, but are not stopping the rf front end. If you take a look at the CLISensorStop function in the cli source file in your project, you will likely see that a different stop function is called, which stops both the RF front end as well as the datapath. In this same vein, if you are looking to stop and reconfigure the sensor and are still using the CLI connection, you may want to try doing this via CLI by issuing the sensorStop command and then issuing the new configuration commands. This would leverage already existing code which may save you time. Let me know if you have any further questions.

    Best Regards,
    Alec