• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 546 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR1642: Questions about mmwave studio demo (SPI, frameConfig)

Navoda Perera
Prodigy 70 points
Part Number: IWR1642

Hi,

I have two questions regarding the mmWave studio demo. Even though they are not entirely related, i thought of asking both in one post.

1. Where can i find more information about how the SPI/CAN switch works. As in, where it fits in the data path, etc. Because i noticed that it is important to have it in SPI for the mmWave Studio Demo. But works either way for the mmWave SDK Demo. 

2. For the frame configuration, in the SDK user guide, it mentions that the Number of loops value "should be a power of 2". I indeed noticed that i run in to issues when reshaping the acquired raw data (through DCA1000) if the number of loops is not a power of 2. That was on a custom script we wrote. However, it seems to work with any value on mmWave Studio. Does mmWave Studio automatically just mask out the bits and just used the MSB if i give a value like 127?

e.g.127 = 0111 1111b being used as 0100 0000b = 64 ?

Thank you

Regards,

Navoda

  • 0
    TI__Mastermind 25795 points

    Hello,

    1)  SPI/CAN interface are defined in pin mux table.  In case of mmWave Studio  use-case device is booted through the debug mode.

    In this case boot ROM will enable the pin-mux configuration as SPI interface.  In case mmWave SDK  out of box Demo, interface to device is through the UART ports (Control and Data UART ports).  

    Application running on MCU could be modified to enable CAN or SPI ports by writing into pin mux registers.  

    You could refer to datasheet for the pin mux configuration shown below. 

    2) During the post processing every Radar's chirp's echo-signal is down-converted to IF signal and Digitized. On this digitized signal FFT operation is performed.  For the FFT operation within the embedded systems framework (SDK Demo) Radix of 2 helps in optimization FFT operation with in DSP.  

    On the PC framework for the mmWave studio it uses Matlab post processing scripts which are flexible hence this restriction is not present.

    Thanks and regards,

    CHETHAN KUMAR Y.B.

  • 0 in reply to CHETHAN KUMAR Y.B.
    Prodigy 70 points
    Thank you Chethan for the explanation!