• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 862 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.

AWR1843: Radar Functional APIs vs. mmWaveLink APIs.

Hitoshi Sugawara
Mastermind 18650 points
Part Number: AWR1843
Other Parts Discussed in Thread: MMWAVE-DFP, AWR1243,

Hi Champs,

Do we have any correspondence table Radar Functional APIs in mmWave-Radar-Interface-Control.pdf vs. mmWaveLink APIs?

( MMWAVE ICD:   Radar Interface control document )

It seems that a customer is familiar with Radar Functional APIs for AWR1243 control.
If this is available, it helps a lot for the program porting to AWR1843.

Am I making sense?
Best regards,
Hitoshi

  • 0
    TI__Guru*** 138349 points

    Hi,

    I understand that the purpose of this question is porting a radar application from a system using AWR1243+External Host to AWR1843 (which has integrated processing ARM + HWA+DSP)

    I think there may be some confusion in terminology.

    The application implemented on AWR1243+External Host runs on the External Host and uses the mmWave Link APIs to communicate with AWR1243. What is called "Radar Functional APIs" in your post is probably the same thing as "mmWave Link API"

    When porting an application implemented on AWR1243+External Host to AWR1843, it is important to understand the SW frameworks available on AWR1843 vs AWR1243.

    AWR1243 is a sensor only device. TI does not provided any SW framework for it since the application is implemented on an External Host.

    For AWR1843, since the processing engine is integrated, TI provides a SW framework example: the mmwave SDK demo

    So, in order to port an application to AWR1843 it is easier to start with the mmWave SDK demo.

    The SDK demo uses a higher level API called the mmWave API. This API calls the mmWave Link API.

    Please see SDK UG - Figure 12,13,14

    C:\ti\mmwave_sdk_03_02_00_04\docs\mmwave_sdk_user_guide.pdf

    Thank you

    Cesar

  • 0 in reply to Cesar
    TI__Mastermind 18650 points

    Hi Cesar,

    Thank you for your prompt reply.
    There seems no document which show the API correspondence table.

    I have compared the Radar Functional APIs, the Radar Monitoring APIs in mmWave-Radar-Interface-Control.pdf  and mmWave Link APIs with file:///C:/ti/mmwave_sdk_03_03_00_03/packages/ti/control/mmwavelink/docs/doxygen/html/modules.html.

    For example, sub block 0x0086 AWR_RF_DEVICE_CHG_SB is supported by rlRfSetDeviceCfg() in mmWave Link. 

    In summary, there seem a few APIs in mmWave-Radar-Interface-Control.pdf are not listed on mmWave Link APIs.
    However, it is searchable for corresponding APIs and data structures.
    Will treat a customer by this procedure.

    Best regards,
    HItoshi

  • 0 in reply to Hitoshi Sugawara
    TI__Guru*** 138349 points

    Closing the thread now

    If there are new questions please open a new thread

    Cesar

  • 0 in reply to Cesar
    TI__Mastermind 18650 points

    Hi Cesar,

    Thank you.

    Best regards,
    Hitoshi