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

AWR2944: The Issue of conflict between the host command and BSS report in rlDriverHostIrqHandler()

wu bin
Prodigy 140 points
Part Number: AWR2944

Tool/software:

Hi Expert,

We configured the reportMode in rlDigMonPeriodicConf_t to 0 (Report is sent every monitoring period), and then after each frame start, we called rlSetProfileConfig to configure a new profile.

This caused a issue : rlOsiSemSignal being called one extra time per period, while rlOsiSpawn was not called(it should be called one time per period).

The reason for this is as follows: After calling the interface rlSetProfileConfig, either isCmdRespWaited or isRespWriteWaited is set to 1. Then, when the interrupt triggered by the bss async report period monitor occurs, since tempVar is TRUE, it does not call rlOsiSpawn.

Are the BSS async report period monitors always after frame start? Do we need to wait until the async report is received before calling rlSetProfileConfig?

The SDK version is mmwave_mcuplus_sdk_04_04_01_02 and dfp firmware verion is mmwave_dfp_02_04_14_00.

 

Regards,

Wu Bin

  • 0
    TI__Mastermind 32555 points

    Hi,

    Please find my comments below. 

    wu bin said:
    Are the BSS async report period monitors always after frame start? Do we need to wait until the async report is received before calling rlSetProfileConfig?

    The Monitoring report are always sent out after the frame end async end event. It is recommended to collect all the monitoring reports and then proceed with the next set of reconfigurations and framing. 

    Thanks,

    Pradipta.