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

MMWAVE-DFP: Confusion with deviceIndex and deviceMap for connection between AWR2243BOOST and Raspberry Pi

Jordan Francis
Prodigy 150 points
Part Number: MMWAVE-DFP

Hello, can I get a clear explanation for the variables deviceIndex and deviceMap within the mmwave DFP with context of connecting to a single device(raspberry pi). For example I know some of the functions I am implementing have deviceIndex as a argument but if my functions (say Spiopen and enablenReset) just enable a GPIO that I specify, do I need to do something with the deviceIndex argument? Currently for the two functions I have mentioned deviceIndex is not being used.

  • 0
    TI__Guru*** 138349 points

    Hi,

    Please give us some time to review your question

    thank you

    Cesar

  • +1
    TI__Guru 68160 points

    Hi,

    DeviceMap is bit mapping of the all AWR device connected with the mmwavelink (host application), each bit in deviceMap stands for one AWR device.

    deviceIndex is instance of one AWR device, it is location of bit in the deviceMap. This is mainly used within the mmwavelink library. Application needs to pass deviceMap while invoking any mmwavelink API.

    For more understanding refer C:\ti\mmwave_dfp_02_xx\ti\control\mmwavelink\src\rl_driver.c : rlDriverCmdInvoke() function where each of deviceIndex from given deviceMap is being invoked to send SPI message.

    e.g. 2 chip cascade

    deviceMap = 0x3;  /* ( RL_DEVICE_MAP_CASCADED_1 | RL_DEVICE_MAP_CASCADED_2 ) */

    For single chip : deviceMap = 1 /* RL_DEVICE_MAP_CASCADED_1 */

    Regards,

    Jitendra