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

IWR6843ISK: Configuring and controlling mm-wave radar via SPI GPIO connectors

u3344
Prodigy 70 points
Part Number: IWR6843ISK
Other Parts Discussed in Thread: MMWAVEICBOOST,

Hi there, 

We would like to configure and control the IWR6843ISK radar from external MCU via GPIO connectors (Launchpad J5 and J6 on MMWAVEICBOOST). Could you please suggest what modifications should we make to Demo project for it to work? Specifically, I have the following questions:

  1. In my understanding, the default setup utilizes UART protocol over USB connector with FTDI drivers to configure and control radar via serial commands. In the modified setup with SPI GPIO, would we need any driver for radar to understand the commands? 
  2. Would we need to change the commands for SPI communication?
  3. From my research into this modification, I believe we'll need to use the SPI for "External MCU interface" in the image shown below and this SPI connects to SPI pins on LaunchPad connectors J5, J6. Is that correct? 

Thank you

Arvind

  • 0
    TI__Mastermind 25795 points

    Arvind,

        Could you please explain briefly how the end system you are envisioning? It would be good if you could provide details with block diagram. 

    Currently in our demo framework, mmWave device is controlled through UART interface. Are you planning to reuse TI demo frame work or Are you planning to write controlling software by yourself. 

    Thanks and regards,

    CHETHAN KUMAR Y.B.

  • 0 in reply to CHETHAN KUMAR Y.B.
    Prodigy 70 points

    Hi Chethan, 

    Thank you for replying. I've attached a block diagram of our implementation. Essentially, we want to bypass the UART + FTDI driver setup and control the radar from a Linux MCU via SPI connection instead, which, in my opinion is supported via the connectors J5, J6 at the MMWAVEICBOOST.  

    We don't want to make significant modifications to the demo project - we just want to replace the UART USB cable via SPI GPIO connectors and keep everything same. It'd be great if you could let me know what modifications would that require and reply to the questions listed in original post. 

    Thank you
    Arvind 

  • 0 in reply to u3344
    TI__Mastermind 25795 points

    Arvind,

         Thank you for sharing the block diagram. In the current implementation for the control interface UART is the port used (RX232 Tx and Rx lines) from this interface firmware would be downloaded into MSS and BSS processors, and SPI interface (through the FTDI chip) on DCA1000 would use for issuing APIs. Are you planning to use mmWave studio for this framework or something else? Is the end goal is to get the ADC samples into Linux MCU? Which demo project you are considering for porting?

    It's not clear how these operations would be targeted through above block diagram. However, It would be preferable to use the UART interface as is for the control interface on the linux MCU otherwise, I think there is significant effort would be need to port existing UART interface to SPI peripheral. On the J5 connector RS232 UART lines are brought out. 

    Thanks and regards,

    CHETHAN KUMAR Y.B.

  • 0 in reply to CHETHAN KUMAR Y.B.
    Prodigy 70 points

    Hi Chethan,

    Yes, we are targeting to get the raw data on the Linux MCU using the TI demo project. I looked schematic details and it makes sense to use the UART interface, thanks for clarifying. However, the block diagram (please see attachment with the original post) mentions UART as "For debug" and SPI as "External MCU control," which is confounding. 

    So, to confirm, we can send the same radar configuration commands over GPIO UART pins (at J5 connector) at same baud rate (115200 bauds/s) and configure and control the radar from external MCU, right? Also, could you please describe the utility of SPI? 

    Thanks a lot for the help.

    Regards,
    Arvind

  • 0 in reply to u3344
    TI__Mastermind 25795 points

    Arvind,

        Thanks for confirming on raw data capture. Yes it is understandable source of confusion from the block diagram, As device has multiple UART ports which could be pin multiplexed to have different functionality. In the above block diagram internal firmware logs could be brought out for debug purpose on the UART ports. 

    mmWave control interface has two ports UART port (RS232_RX and RS232_TX) and SPI (Along with Host_interrupt pin) ports and RAW ADC data on LVDS ports.

    For raw ADC data capture a specific firmware binary (BSS, MSS) are loaded through the UART interface using mmWave studio in SOP2 boot configuration mode. For this one need to ensure device is powered up in this boot configuration and nRESET is issued to register the boot mode for the bootloader, then bootloader in the device wait for firmware images in UART port (RS232). This could be doable J5 connector with appropriate switch settings on the mmWaveIcboost board.  

    Once the firmware is downloaded then mmWave studio APIs are issued through the SPI interface. For this DCA1000 hardware is used, In DCA1000 hardware there exist USB to SPI interface from this interface SPI lines are interfaced to mmWave device. mmWave studio's API command and response is captured through this interface and bi-directional communication logs are also provided in this interface on the mmWave studio console. It is recommended to use this interface as is in the host platform which simplifies development effort on the host side. 

    Thanks and regards,

    CHETHAN KUMAR Y.B.