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.

AWR2243BOOST: What tool to use configure this to enable MIPI output on 60-pin HD connector

Part Number: AWR2243BOOST
Other Parts Discussed in Thread: AWR2243

I purchased AWR2243BOOST recently for evaluating if the raw ADC MIPI output can be captured by our CPU board MIPI receiver. We would be making  a cable to connect the 60-pin HD connector to our board's PCIe connector for MIPI.

I want to know what tool should I use to configure the board to enable MIPI output on the HD connector?

I tried using mmWave Studio as apparently it has options to do that in the "RadarAPI" tab. But it is not able to detect the device even though I have connected the board and the two COM ports are enumerated correctly. It says:

No. of Devices Detected: 0

I do not have any other TI capture board connected as that is not our objective.

  • Hi,

    You would need a DCA1000 capture card to configure the AWR2243BOOST board.

    thank you

    Cesar

  • Hi,

    If I use the DCA1000 capture card, then I won't be able to connect the 60 pin HD connector to my board. Is that right? As I mentioned, I am not interested in getting processed output in the form of point cloud from DCA1000, so why should I need that?

    Nadeem

  • What is the default raw data format coming out of  AWR2243BOOST board? If it is already CSI and not LVDS, then maybe I do no need configuration. But if need to configure and DCA1000 is needed, can we do following:

    - For configuration purpose, connect DCA1000. I assume the configuration would be saved in the AWR2243BOOST flash. Is that right?

    - Remove DCA1000 and connect our board instead.

  • Hello Nadeem,

    All the configurations of the AWR2243 device are done over the SPI interface. So your CPU board should be able to send the mmwave link APIs to the AWR2243 over this SPI interface to powerup, configuring and enable the AWR2243 device. Part of the configuration also includes the CSI interface enabling & configurations. Please refer to the   Interface Control Document (https://dr-download.ti.com/software-development/firmware/MD-074SwD074J/02.02.03.01/mmWave-Radar-Interface-Control.pdf) to know the details about the SPI interface protocol and the commands or APIs the AWr2243 supports.

    Regards,

    Vivek

  • Hello Vivek,

    My expectation was that if I use the AWR2243BOOST kit, I would be able to do all SPI configuration from a FT4222 interface on a PC using some TI provided tool and I only use our CPU for MIPI capture.

    I understand that if we are integrating AWR2243 directly in our board, then we have to do all configurations from our CPU. Bu at this time, we just want to evaluate the kit to see if we can capture the MIPI output from our CPU.

    Regards

    Nadeem

  • Hello Nadeem,

    The TI tool (mmwve studio) is designed to use the FT4232 on the DCA1000 to control/configure  the AWR2243 . You would have to figure out a way to connect the SPI, Host Int, nReset and RS232 lines between the DCA1000 and 2243 board, while the CSI lines need to be connected to your CPU. 

    Regards,

    vivek

  • Hi Vivek,

    Is it possible that I connect DCA1000 just for doing the configuration (like enabling CSI) and if that configuration is saved in AWR2243BOOST flash, then I take out the DCA1000 and instead connect our CPU for MIPI capture?

    Nadeem

  • Hello Nadeem,

    That could be problematic. The control includes starting the framing, so as soon as you issue that command the frames would start and CSI data would be sent out. So you might not be able to disconnect the DCA and connect CPU within time to avoid missing out any CSI data. Also in general "hot" is not recommended, it could cause damage. 

    I would recommend you either separate out the connections for control and CSI data , OR perform both control and receive the CSI data from your CPU. If you have a reasonable CPU  , it should be able to run the mmwave link and control commands.

    regards,

    Vivek

  • Hello Vivek,

    I have following questions/comments:

    1. The AWR2243BOOST kit already has some demo flashed. Is that by default sending out CSI or LVDS? If it is already sending out CSI, then I may not need to configure it with SPI.

    2. If the demo flashed is not enabling CSI, is there a way to reflash with something which enables CSI? If yes, what tool should we use to reflash?

    3. I was not talking about live swap of DCA1000 with our CPU board. I thought that we could configure AWR2243 using DCA1000 connected to AWR2243BOOST and it will write updated settings to flash. So on next power on, updated settings would be used and I could then connect our CPU board. From your reply, it seems like this is not possible - right?

    4. If at all we need to configure using SPI from our CPU, I am assuming that I do not to do full configuration as the demo pre-flashed must have done basic configuration. So basically I am mostly interested in the additional commands to configure for CSI. Is that right?

    Regards

    Nadeem

  • Hello Nadeem,

    There is no demo flashed on the AWR2243 EVM. 2243 is a front end only device, it cannot execute on its own, it needs host processor to configure . Every single configuration (including powerup) needs to sent from the host.

    Regards,
    Vivek 

  • Hello Vivek,

    I see following in AWR2243BOOST user guide:

    1.3.2 mmWave Proximity Demo
    TI provides sample demo codes to easily get started with the AWR2243 evaluation module and experience the
    functionality of the AWR2243 mmWave sensor. For details on getting started with these demos, see the
    mmWave SDK User Guide

    I see following in mmWave SDK User Guide:

    3. Getting started
    The best way to get started with the mmWave SDK is to start running one of the various demos that are provided as part of the package. TI mmWave
    EVM comes pre-flashed with the mmWave demo. However, the version of the pre-flashed demo maybe older than the SDK version mentioned in this
    document. Users can follow this section and upgrade/run the flashed demo version. The demos (source and pre-built binaries) are placed at mmwave_
    sdk_<ver>/packages/ti/demo/<platform> folder.

    According to the above, EVM comes pre-flashed with the mmWave demo. So is the documentation not correct?

    Regards

    Nadeem

  • Hello Nadeem,

    The mmWave SDK cannot be used for AWR2243, it can be used for the mmwave devices that have a internal core that can be programmed by the user (like 1642, 1843 6843 etc.) . You can refer to the mmWave SDK user guide for the details on the devices it supports. AWR2243 is a front end device, so it needs an external host to enable and control it or SPI or I2C interface. You can refer to the mmWave DFP example code, which uses the PC as the host to control the 2243 device.

    The mention of proximity demo in the AWR2243BOOST user guide is a mistake, thanks for pointing it out. We will correct the documentation.

    Regards,

    Vivek 

  • Hi Vivek,

    This is very helpful information. I saw examples in mmWave DFP like "mmWaveLink_SingleChip_Example" which seems relevant to me and I can use that to adapt for our CPU. I was misled by the mention of mmWave SDK in the AWR2243BOOST user guide spruit8d.pdf.

    One confirmation I want: The document mmWave-Radar-Interface-Control.pdf mentions only SPI:

    The radar device is configured and controlled from the external host processor by
    sending commands to AWR2243/xWR6243 device over SPI.

    But I can I also use I2C - right? Using I2C might be easier on our system.

    Regards

    Nadeem

  • Hello Nadeem,

    AWR2243 does support over I2C also (you need to set the appropriate SOP mode). But this would be much slower than SPI. If you just need to do one time configuration and then leave it running, then it might be OK.

    Regards,

    Vivek