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

IWR1443: Using mmWave SDK 3.0

Kevin Lannen
Intellectual 260 points
Part Number: IWR1443

Hi,

I am starting code development for a custom board using an IWR1443 ES3.0 revision. I have prototyped some of the functionality that I need using the old 1.2 mmWave SDK on the IWR1443BOOST rev A devkit and now I need to move to an updated SDK due to the new silicon.

The release notes for the 3.0 SDK indicate that the IWR1443 ES3.0 is supported and the new data processing layers look like a good improvement. However, there is no example for the IWR1443. Is it recommended to move to the 3.0 SDK or to use the older 2.1 SDK for the IWR1443?

Are there plans to release a demo application for the 3.0 SDK in the future and if so, when is it expected to be available?

As an aside, if the 3.0 SDK is not ready for the IWR1443 then maybe it should not be listed as compatible in the release notes. (I saw a couple of forum responses that indicated it was not compatible only after I had spent considerable time reading the 3.0 SDK guide which also indicates the the IWR1443 is compatible)

Thanks,

Kevin

  • 0
    TI__Mastermind 30405 points

    Hi Kevin,

    SDK 3.0 does support IWR1443 but the support is limited to drivers/legacy code only. The new scalable architecture is not recommended/supported for IWR1443 given the memory limitations.

    In context of IWR1443, the decision to use SDK 2.1.0.4 vs SDK 3.0.0.x depends upon :

    1. 77GHz End application
      1. Whether 14xx is the target device
      2. Or 16xx/18xx is the target device

    2. 60GHz End application
      1. Did the customer use 77GHz/14xx for early development and will move to 68xx as the target device.
      2. Developing straight on 60GHz/68xx

    Case 1 (77GHz end application):

    1. If 14xx is your target device, use SDK 2.1. There is no benefit to using SDK 3.0 for this scenario as the new scalable architecture is not supported on 14xx and no new features will be added to SDK 3.0 for 14xx. This is the reason we don't have a 14xx OOB demo in SDK 3.0
    2. If the end goal is to use 16xx/18xx as the final device, you have a choice to migrate your code to SDK 3.0 and eventually move to the new software architecture for those devices.  

    Case 2: 60GHz end application

    1. If 77GHz/14xx was used for early development, and the end goal is to move to 68xx then you have a choice to migrate your existing code to SDK 3.0 and gradually move to the new software architecture.
    2. If you don't have an application on 77GHz device and are developing straight on 68xx, use SDK 3.0 and the new software architecture.

    Hope the above provides some clarification.

    Please mark this thread resolved if your question was answered otherwise get back if you have more questions on this topic.

    Regards

    -Nitin

     

  • 0 in reply to Nitin Sakhuja
    Intellectual 260 points

    Hi Nitin,

    Thanks for the overview. I will stick with SDK 2.1 for my application. 

    This overview should really be included in at least the release notes for SDK 3.0 since I was unable to find any info of which SDK I should be using and why I would choose one over another.

    Thanks,

    Kevin