• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 916 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.

AWR1243: Question about migrating mmwavelink

Annie Liu
Genius 10295 points
Part Number: AWR1243

Hi Team,

The customer is experiencing below issue and needs your help.


1. According to the Porting Guide in DFP, the migration is divided into 7 steps. The mmWaveLink client callback structure in the first step contains different structures. Is it necessary to define and initialize all structures after migration, such as OS structure?
2. In the second step, only statements such as rls_studio.h are included. Customer is unable to find the definition of the function. He would like to know how to migrate?
3. In the MSP430 project, can mmwlstudio.lib, rls_osi.h, rls_studio.h be directly quoted?

Thanks.

  • 0
    TI__Guru*** 148124 points

    Hi,

    We will be able to get back to you by end of the week

    thank you

    Cesae

  • 0
    TI__Guru 69960 points

    Hi Annie,

    1. mmWaveLInk functionalities depend on all the callbacks it asks from the application to implement even OS callbacks (semaphore/mutex). As mmWaveLInk is OS agnostic so application using no OS needs to provide equivalent of semaphore/mutex implementation to mmWaveLink.

    2. rl_studio.h and mmwavestudio.lib is being used to communicate to AWR1243 device over SPI which is done on PC through DevPack;s FTDI chip. This library provides the abstract/function to communicate to FTDI SPI interface.

    3. This library and header files are meant to work with FTDI SPI chip, so it won't work with MSP430. Here is the related e2e thread which will be helpful for porting mmwavelink on MSP430 platform.

    https://e2e.ti.com/support/sensors/f/1023/p/839686/3105534#3105534

    And refer mmwave DFP Non-OS example

    C:\ti\mmwave_dfp_01_02_05\ti\example\mmwavelink_example_nonos

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    TI__Genius 10295 points

    Hi Jitendra,

    Thanks for your support and I apologize for any delay in responding to you due to National Day in China.

    Customer would like to know:

    There are four function pointers on the communication interface in the rlClientCbs_t structure in mmWaveLInk. They are rlComIfOpen，rlComIfRead，rlComIfWrite and rlComIfClose. The return value of rlComIfOpen is written as an interface handle in the comment. Is this the register address of the SPI module?

    Thanks.

  • 0 in reply to Annie Liu
    TI__Guru 69960 points

    Hi Annie,

    It can be any void pointer pointing to the address of SPI module or driver handle to identify which SPI module (in case using multiple interfaces for cascade).

    In single device it can be any non-null value, as long as these rlComIf*** function callbacks handle those return handle value.

    Regards,

    Jitendra