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/MMWAVE-DFP: What does the handle mean in mmwavelink callbacks?

Part Number: MMWAVE-DFP
Other Parts Discussed in Thread: MMWAVE-STUDIO

Tool/software: TI C/C++ Compiler

Hi there

I’m now working on porting mmwavelink framework to a nonos MCU ,implementing the callbacks it needed. And I found most of the callbacks need to return or input A HANDLE. What does it mean? For example, in comm. interface callbacks, what does the handle mean if the comm. interface is SPI? Is it the SPI module adress of the nonos MCU I'm using?

Regards

Junzhe 

  • Hi Junzhe,

    HANDLE can be address pointer or any other unique value with which SPI module driver can recognize it's instance while communicating with SPI interface. But it must be non-null value which every callback will return.

    mmWaveLink doesn't use any of these HANDLEs internally but uses it while calling any of the related callback functions.

    You can refer the non-OS reference example provided in the mmwave DFP 

    C:\ti\mmwave_dfp_01_02_05_01\ti\example\mmwavelink_example_nonos

    and the FTDI library source code for any interface callback implementation

    '<mmwave-studio installation path>\mmWaveStudio\ReferenceCode\FTDILib\SourceCode'

    Regards,

    Jitendra