• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 823 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.

Compiler/AWR1642: BPM Scheme and API Question

George Denove
Expert 1435 points
Part Number: AWR1642

Tool/software: TI C/C++ Compiler

Hi there,

How is the BPM scheme (and bpmConstantValue) written in software in the mss_main applied to the chirps? I ask this because of the below scenario... Let's take a look at this CLI script:

Given that the BPM works with the out of the box demo (not with the above cli script since there is the error in the bpmCfg API line), I change the bpmCfg line above to index chirp0Idx as 0 and chirp1Idx as 2. There is not a chirp 2 defined in chirpCfg as well as not referenced in frameCfg (loop over 0 and 1). Why does this run through? Shouldn't there be an error thrown because the chirp Index that I reference as <chirp1Idx> in bpm is actually this imaginary chirp 2 rather than chirpCfg 1 1? 

Since it does run through, is it just looping over a bpm chirp 0 and a normal chip 1 (since there is no bpm chirp 1 referenced)?

I hope that makes sense, I look forward to hearing your answer... thanks!

George

  • 0
    TI__Mastermind 40025 points

    HI,  George:

    You can search "bpmCfg" inside C:\ti\mmwave_sdk_03_04_00_03\docs\mmwave_sdk_user_guide.pdf to understand this CLI command. 

    You can also find an example configuration for xwr1642 at:

    C:\ti\mmwave_sdk_03_04_00_03\packages\ti\demo\xwr16xx\mmw\profiles\profile_2d_bpm.cfg

    With your change, this is not a valid BPM mode that OOB demo support any more.  But you can always search the source code to understand what will actually happen.    

    Best,

    Zigang 

  • 0
    TI__Expert 5320 points

    >>is it just looping over a bpm chirp 0 and a normal chip 1 (since there is no bpm chirp 1 referenced)?

    Yes, BPM config for chirp#2 is ignored silently.

    The system only cares about the chirps that are being used in the frameCfg and ignores any other chirps that are defined. Similar to what you have tried, you can try adding a chirpCfg for chirp#2 and that will be ignored too as far as frameCfg doesn't use chirp#2.

    Hope this answers your question.

  • 0 in reply to Madhvi
    Expert 1435 points

    Awesome, this helped me understand the situation! Thanks so much!

    George